diff --git a/bugs.po b/bugs.po index 78cd0f4cc..5520655a8 100644 --- a/bugs.po +++ b/bugs.po @@ -34,8 +34,8 @@ msgstr "" #: 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 `." +"Python as it streamlines the process and involves less people. Learn how " +"to :ref:`contribute `." msgstr "" "Bazen hataları kendiniz düzeltmek ve değişikliklerinizi Python'a yama " "yaparak katkı sağlamak süreci daha az insan dahil olduğu için " diff --git a/c-api/abstract.po b/c-api/abstract.po index d3fcee983..8a71ab605 100644 --- a/c-api/abstract.po +++ b/c-api/abstract.po @@ -31,7 +31,7 @@ msgstr "" #: 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." +"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 "" diff --git a/c-api/allocation.po b/c-api/allocation.po index 8b43cf8ba..34f38d618 100644 --- a/c-api/allocation.po +++ b/c-api/allocation.po @@ -41,8 +41,8 @@ msgid "" "Python type object *typeobj* (``PyTypeObject*``). Fields not defined by the " "Python object header are not initialized. The caller will own the only " "reference to the object (i.e. its 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." +"the memory allocation is determined from " +"the :c:member:`~PyTypeObject.tp_basicsize` field of the type object." msgstr "" #: c-api/allocation.rst:43 @@ -60,11 +60,11 @@ msgstr "" #: c-api/allocation.rst:57 msgid "" -"Releases memory allocated to an object using :c:macro:`PyObject_New` or :c:" -"macro:`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." +"Releases memory allocated to an object using :c:macro:`PyObject_New` " +"or :c:macro:`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 "" #: c-api/allocation.rst:66 diff --git a/c-api/arg.po b/c-api/arg.po index 3364d0bad..7ea41fbb1 100644 --- a/c-api/arg.po +++ b/c-api/arg.po @@ -23,17 +23,17 @@ msgstr "" #: 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`." +"methods. Additional information and examples are available " +"in :ref:`extending-index`." msgstr "" #: 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." +"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 "" #: c-api/arg.rst:19 @@ -98,10 +98,10 @@ msgstr "" #: c-api/arg.rst:61 msgid "" -"To ensure that the underlying buffer may be safely borrowed, the object's :c:" -"member:`PyBufferProcs.bf_releasebuffer` field must be ``NULL``. This " -"disallows common mutable objects such as :class:`bytearray`, but also some " -"read-only objects such as :class:`memoryview` of :class:`bytes`." +"To ensure that the underlying buffer may be safely borrowed, the " +"object's :c:member:`PyBufferProcs.bf_releasebuffer` field must be ``NULL``. " +"This disallows common mutable objects such as :class:`bytearray`, but also " +"some read-only objects such as :class:`memoryview` of :class:`bytes`." msgstr "" #: c-api/arg.rst:67 @@ -113,11 +113,11 @@ msgstr "" #: c-api/arg.rst:73 msgid "" -"For all ``#`` variants of formats (``s#``, ``y#``, etc.), the macro :c:macro:" -"`PY_SSIZE_T_CLEAN` must be defined before including :file:`Python.h`. On " -"Python 3.9 and older, the type of the length argument is :c:type:" -"`Py_ssize_t` if the :c:macro:`PY_SSIZE_T_CLEAN` macro is defined, or int " -"otherwise." +"For all ``#`` variants of formats (``s#``, ``y#``, etc.), the " +"macro :c:macro:`PY_SSIZE_T_CLEAN` must be defined before " +"including :file:`Python.h`. On Python 3.9 and older, the type of the length " +"argument is :c:type:`Py_ssize_t` if the :c:macro:`PY_SSIZE_T_CLEAN` macro is " +"defined, or int otherwise." msgstr "" #: c-api/arg.rst:80 @@ -138,8 +138,8 @@ msgstr "" 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*." +"strings, it is preferable to use the ``O&`` format " +"with :c:func:`PyUnicode_FSConverter` as *converter*." msgstr "" #: c-api/arg.rst:96 @@ -162,8 +162,8 @@ msgstr "" #: c-api/arg.rst:106 msgid "" -"``s#`` (:class:`str`, read-only :term:`bytes-like object`) [const char \\*, :" -"c:type:`Py_ssize_t`]" +"``s#`` (:class:`str`, read-only :term:`bytes-like object`) [const char " +"\\*, :c:type:`Py_ssize_t`]" msgstr "" #: c-api/arg.rst:107 @@ -238,8 +238,8 @@ msgstr "" #: c-api/arg.rst:141 msgid "" -"``y#`` (read-only :term:`bytes-like object`) [const char \\*, :c:type:" -"`Py_ssize_t`]" +"``y#`` (read-only :term:`bytes-like object`) [const char " +"\\*, :c:type:`Py_ssize_t`]" msgstr "" #: c-api/arg.rst:142 @@ -266,9 +266,9 @@ msgstr "" #: c-api/arg.rst:151 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:expr:" -"`PyObject*`." +"attempting any conversion. Raises :exc:`TypeError` if the object is not " +"a :class:`bytearray` object. The C variable may also be declared " +"as :c:expr:`PyObject*`." msgstr "" #: c-api/arg.rst:155 @@ -290,8 +290,8 @@ msgstr "" 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." +"The buffer may contain embedded null bytes. The caller have to " +"call :c:func:`PyBuffer_Release` when it is done with the buffer." msgstr "" #: c-api/arg.rst:166 @@ -319,8 +319,8 @@ msgstr "" 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." +"newly allocated storage. The caller is responsible for " +"calling :c:func:`PyMem_Free` to free the allocated buffer after use." msgstr "" #: c-api/arg.rst:183 @@ -338,8 +338,8 @@ msgstr "" #: c-api/arg.rst:188 msgid "" -"``es#`` (:class:`str`) [const char \\*encoding, char \\*\\*buffer, :c:type:" -"`Py_ssize_t` \\*buffer_length]" +"``es#`` (:class:`str`) [const char \\*encoding, char " +"\\*\\*buffer, :c:type:`Py_ssize_t` \\*buffer_length]" msgstr "" #: c-api/arg.rst:189 @@ -419,8 +419,8 @@ msgstr "" #: c-api/arg.rst:233 msgid "" -"Convert a nonnegative Python integer to an unsigned tiny int, stored in a C :" -"c:expr:`unsigned char`." +"Convert a nonnegative Python integer to an unsigned tiny int, stored in a " +"C :c:expr:`unsigned char`." msgstr "" #: c-api/arg.rst:580 @@ -572,9 +572,9 @@ msgstr "" #: c-api/arg.rst:295 msgid "" "Store a Python object (without any conversion) in a C object pointer. The C " -"program thus receives the actual object that was passed. A new :term:" -"`strong reference` to the object is not created (i.e. its reference count is " -"not increased). The pointer stored is not ``NULL``." +"program thus receives the actual object that was passed. A " +"new :term:`strong reference` to the object is not created (i.e. its " +"reference count is not increased). The pointer stored is not ``NULL``." msgstr "" #: c-api/arg.rst:301 @@ -608,12 +608,12 @@ msgstr "" #: c-api/arg.rst:318 msgid "" -"where *object* is the Python object to be converted and *address* is the :c:" -"expr:`void*` argument that was passed to the ``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." +"where *object* is the Python object to be converted and *address* is " +"the :c:expr:`void*` argument that was passed to the ``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 "" #: c-api/arg.rst:324 @@ -711,8 +711,8 @@ msgstr "" #: c-api/arg.rst:378 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." +"as the error message *instead* of the default error message. ``:`` and " +"``;`` mutually exclude each other." msgstr "" #: c-api/arg.rst:382 @@ -763,9 +763,10 @@ msgstr "" 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." +"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 "" #: c-api/arg.rst:425 @@ -874,10 +875,10 @@ 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." +"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 "" #: c-api/arg.rst:521 @@ -1066,9 +1067,9 @@ msgid "" "Pass a Python object untouched but create a new :term:`strong reference` to " "it (i.e. its reference count 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." +"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 "" #: c-api/arg.rst:628 @@ -1093,9 +1094,9 @@ msgstr "" #: 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:expr:" -"`void*`) as its argument and should return a \"new\" Python object, or " -"``NULL`` if an error occurred." +"function is called with *anything* (which should be compatible " +"with :c:expr:`void*`) as its argument and should return a \"new\" Python " +"object, or ``NULL`` if an error occurred." msgstr "" #: c-api/arg.rst:643 diff --git a/c-api/buffer.po b/c-api/buffer.po index fde899100..0fef149b2 100644 --- a/c-api/buffer.po +++ b/c-api/buffer.po @@ -23,10 +23,10 @@ msgstr "" #: 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." +"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 "" #: c-api/buffer.rst:24 @@ -39,8 +39,8 @@ msgstr "" #: 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:" +"Python provides such a facility at the C level in the form of " +"the :ref:`buffer protocol `. This protocol has two sides:" msgstr "" #: c-api/buffer.rst:34 @@ -66,14 +66,14 @@ msgstr "" #: 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." +"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 "" #: c-api/buffer.rst:53 @@ -127,8 +127,8 @@ msgstr "" #: 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`." +"Object Structures `. For obtaining a buffer, " +"see :c:func:`PyObject_GetBuffer`." msgstr "" #: c-api/buffer.rst:94 @@ -155,9 +155,9 @@ msgstr "" #: c-api/buffer.rst:111 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." +"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 "" #: c-api/buffer.rst:118 @@ -172,8 +172,8 @@ msgstr "" 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`." +"most cases such a request will be :c:macro:`PyBUF_SIMPLE` " +"or :c:macro:`PyBUF_WRITABLE`." msgstr "" #: c-api/buffer.rst:129 @@ -184,30 +184,32 @@ msgstr "" #: c-api/buffer.rst:134 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." +"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 "" #: c-api/buffer.rst:137 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." +"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 "" #: c-api/buffer.rst:142 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." +"itemsize == len`` still holds and the consumer can " +"use :c:member:`~Py_buffer.itemsize` to navigate the buffer." msgstr "" #: c-api/buffer.rst:146 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``." +"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 "" #: c-api/buffer.rst:152 @@ -225,17 +227,18 @@ msgstr "" 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``. The maximum " -"number of dimensions is given by :c:macro:`PyBUF_MAX_NDIM`." +"a scalar. In this " +"case, :c:member:`~Py_buffer.shape`, :c:member:`~Py_buffer.strides` " +"and :c:member:`~Py_buffer.suboffsets` MUST be ``NULL``. The maximum number " +"of dimensions is given by :c:macro:`PyBUF_MAX_NDIM`." msgstr "" #: c-api/buffer.rst:168 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`." +"``shape[0] * ... * shape[ndim-1] * itemsize`` MUST be equal " +"to :c:member:`~Py_buffer.len`." msgstr "" #: c-api/buffer.rst:173 @@ -334,9 +337,8 @@ msgstr "" #: c-api/buffer.rst:243 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`." +"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 "" #: c-api/buffer.rst:249 @@ -360,15 +362,16 @@ msgstr "" #: c-api/buffer.rst:264 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." +"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 "" #: c-api/buffer.rst:268 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)." +":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 "" #: c-api/buffer.rst:273 @@ -492,17 +495,18 @@ msgstr "" #: c-api/buffer.rst:357 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`." +"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 "" #: c-api/buffer.rst:360 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``." +"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 "" #: c-api/buffer.rst:364 @@ -607,8 +611,8 @@ msgstr "" #: c-api/buffer.rst:449 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 :exc:" -"`BufferError`, set ``view->obj`` to ``NULL`` and return ``-1``." +"the exporter cannot provide a buffer of the exact type, it MUST " +"raise :exc:`BufferError`, set ``view->obj`` to ``NULL`` and return ``-1``." msgstr "" #: c-api/buffer.rst:454 @@ -622,9 +626,9 @@ msgstr "" #: c-api/buffer.rst:459 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." +"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 "" #: c-api/buffer.rst:467 @@ -637,14 +641,15 @@ msgstr "" #: c-api/buffer.rst:472 msgid "" -"It is an error to call this function on a buffer that was not obtained via :" -"c:func:`PyObject_GetBuffer`." +"It is an error to call this function on a buffer that was not obtained " +"via :c:func:`PyObject_GetBuffer`." msgstr "" #: c-api/buffer.rst:478 msgid "" -"Return the implied :c:member:`~Py_buffer.itemsize` from :c:member:" -"`~Py_buffer.format`. On error, raise an exception and return -1." +"Return the implied :c:member:`~Py_buffer.itemsize` " +"from :c:member:`~Py_buffer.format`. On error, raise an exception and return " +"-1." msgstr "" #: c-api/buffer.rst:486 diff --git a/c-api/bytearray.po b/c-api/bytearray.po index 51f07f90e..2c6581699 100644 --- a/c-api/bytearray.po +++ b/c-api/bytearray.po @@ -53,8 +53,8 @@ msgstr "" #: c-api/bytearray.rst:42 msgid "" -"Return a new bytearray object from any object, *o*, that implements the :ref:" -"`buffer protocol `." +"Return a new bytearray object from any object, *o*, that implements " +"the :ref:`buffer protocol `." msgstr "" #: c-api/bytearray.rst:52 c-api/bytearray.rst:59 diff --git a/c-api/bytes.po b/c-api/bytes.po index 92bad0a1c..153433443 100644 --- a/c-api/bytes.po +++ b/c-api/bytes.po @@ -258,8 +258,8 @@ msgid "" "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`." +"deallocated. If *o* is not a bytes object at " +"all, :c:func:`PyBytes_AsString` returns ``NULL`` and raises :exc:`TypeError`." msgstr "" #: c-api/bytes.rst:151 diff --git a/c-api/call.po b/c-api/call.po index 4b7fbef36..9e5fecb21 100644 --- a/c-api/call.po +++ b/c-api/call.po @@ -50,8 +50,9 @@ msgstr "" #: c-api/call.rst:25 msgid "" -"This convention is not only used by *tp_call*: :c:member:`~PyTypeObject." -"tp_new` and :c:member:`~PyTypeObject.tp_init` also pass arguments this way." +"This convention is not only used by " +"*tp_call*: :c:member:`~PyTypeObject.tp_new` " +"and :c:member:`~PyTypeObject.tp_init` also pass arguments this way." msgstr "" #: c-api/call.rst:29 @@ -74,18 +75,19 @@ msgstr "" msgid "" "As rule of thumb, CPython will prefer the vectorcall for internal calls if " "the callable supports it. However, this is not a hard rule. Additionally, " -"some third-party extensions use *tp_call* directly (rather than using :c:" -"func:`PyObject_Call`). Therefore, a class supporting vectorcall must also " -"implement :c:member:`~PyTypeObject.tp_call`. Moreover, the callable must " -"behave the same regardless of which protocol is used. The recommended way to " -"achieve this is by setting :c:member:`~PyTypeObject.tp_call` to :c:func:" -"`PyVectorcall_Call`. This bears repeating:" +"some third-party extensions use *tp_call* directly (rather than " +"using :c:func:`PyObject_Call`). Therefore, a class supporting vectorcall " +"must also implement :c:member:`~PyTypeObject.tp_call`. Moreover, the " +"callable must behave the same regardless of which protocol is used. The " +"recommended way to achieve this is by " +"setting :c:member:`~PyTypeObject.tp_call` to :c:func:`PyVectorcall_Call`. " +"This bears repeating:" msgstr "" #: c-api/call.rst:57 msgid "" -"A class supporting vectorcall **must** also implement :c:member:" -"`~PyTypeObject.tp_call` with the same semantics." +"A class supporting vectorcall **must** also " +"implement :c:member:`~PyTypeObject.tp_call` with the same semantics." msgstr "" #: c-api/call.rst:62 @@ -108,11 +110,11 @@ msgstr "" #: c-api/call.rst:74 msgid "" -"Classes can implement the vectorcall protocol by enabling the :c:macro:" -"`Py_TPFLAGS_HAVE_VECTORCALL` flag and setting :c:member:`~PyTypeObject." -"tp_vectorcall_offset` to the offset inside the object structure where a " -"*vectorcallfunc* appears. This is a pointer to a function with the following " -"signature:" +"Classes can implement the vectorcall protocol by enabling " +"the :c:macro:`Py_TPFLAGS_HAVE_VECTORCALL` flag and " +"setting :c:member:`~PyTypeObject.tp_vectorcall_offset` to the offset inside " +"the object structure where a *vectorcallfunc* appears. This is a pointer to " +"a function with the following signature:" msgstr "" #: c-api/call.rst:82 @@ -199,8 +201,8 @@ msgstr "" #: c-api/call.rst:134 msgid "" "When using *tp_call*, callees do not need to worry about :ref:`recursion " -"`: CPython uses :c:func:`Py_EnterRecursiveCall` and :c:func:" -"`Py_LeaveRecursiveCall` for calls made using *tp_call*." +"`: CPython uses :c:func:`Py_EnterRecursiveCall` " +"and :c:func:`Py_LeaveRecursiveCall` for calls made using *tp_call*." msgstr "" #: c-api/call.rst:139 @@ -252,10 +254,10 @@ msgstr "" #: c-api/call.rst:177 msgid "" -"This is a specialized function, intended to be put in the :c:member:" -"`~PyTypeObject.tp_call` slot or be used in an implementation of ``tp_call``. " -"It does not check the :c:macro:`Py_TPFLAGS_HAVE_VECTORCALL` flag and it does " -"not fall back to ``tp_call``." +"This is a specialized function, intended to be put in " +"the :c:member:`~PyTypeObject.tp_call` slot or be used in an implementation " +"of ``tp_call``. It does not check the :c:macro:`Py_TPFLAGS_HAVE_VECTORCALL` " +"flag and it does not fall back to ``tp_call``." msgstr "" #: c-api/call.rst:188 @@ -450,8 +452,8 @@ msgstr "" #: c-api/call.rst:289 msgid "" -"Note that if you only pass :c:expr:`PyObject *` args, :c:func:" -"`PyObject_CallFunctionObjArgs` is a faster alternative." +"Note that if you only pass :c:expr:`PyObject *` " +"args, :c:func:`PyObject_CallFunctionObjArgs` is a faster alternative." msgstr "" #: c-api/call.rst:292 @@ -477,8 +479,8 @@ msgstr "" #: c-api/call.rst:310 msgid "" -"Note that if you only pass :c:expr:`PyObject *` args, :c:func:" -"`PyObject_CallMethodObjArgs` is a faster alternative." +"Note that if you only pass :c:expr:`PyObject *` " +"args, :c:func:`PyObject_CallMethodObjArgs` is a faster alternative." msgstr "" #: c-api/call.rst:313 @@ -487,9 +489,9 @@ msgstr "" #: c-api/call.rst:319 msgid "" -"Call a callable Python object *callable*, with a variable number of :c:expr:" -"`PyObject *` arguments. The arguments are provided as a variable number of " -"parameters followed by *NULL*." +"Call a callable Python object *callable*, with a variable number " +"of :c:expr:`PyObject *` arguments. The arguments are provided as a variable " +"number of parameters followed by *NULL*." msgstr "" #: c-api/call.rst:326 @@ -521,9 +523,9 @@ msgstr "" #: c-api/call.rst:366 msgid "" -"Call a callable Python object *callable*. The arguments are the same as for :" -"c:type:`vectorcallfunc`. If *callable* supports vectorcall_, this directly " -"calls the vectorcall function stored in *callable*." +"Call a callable Python object *callable*. The arguments are the same as " +"for :c:type:`vectorcallfunc`. If *callable* supports vectorcall_, this " +"directly calls the vectorcall function stored in *callable*." msgstr "" #: c-api/call.rst:378 @@ -547,10 +549,10 @@ msgid "" "method is given as a Python string *name*. The object whose method is called " "is *args[0]*, and the *args* array starting at *args[1]* represents the " "arguments of the call. There must be at least one positional argument. " -"*nargsf* is the number of positional arguments including *args[0]*, plus :c:" -"macro:`PY_VECTORCALL_ARGUMENTS_OFFSET` if the value of ``args[0]`` may " -"temporarily be changed. Keyword arguments can be passed just like in :c:func:" -"`PyObject_Vectorcall`." +"*nargsf* is the number of positional arguments including *args[0]*, " +"plus :c:macro:`PY_VECTORCALL_ARGUMENTS_OFFSET` if the value of ``args[0]`` " +"may temporarily be changed. Keyword arguments can be passed just like " +"in :c:func:`PyObject_Vectorcall`." msgstr "" #: c-api/call.rst:401 diff --git a/c-api/capsule.po b/c-api/capsule.po index 377d894d2..1ec5d6757 100644 --- a/c-api/capsule.po +++ b/c-api/capsule.po @@ -108,8 +108,8 @@ msgstr "" #: c-api/capsule.rst:76 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." +"``NULL`` return code somewhat ambiguous; use :c:func:`PyCapsule_IsValid` " +"or :c:func:`PyErr_Occurred` to disambiguate." msgstr "" #: c-api/capsule.rst:83 @@ -121,8 +121,8 @@ msgstr "" #: c-api/capsule.rst:86 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." +"return code somewhat ambiguous; use :c:func:`PyCapsule_IsValid` " +"or :c:func:`PyErr_Occurred` to disambiguate." msgstr "" #: c-api/capsule.rst:93 @@ -134,8 +134,8 @@ msgstr "" #: c-api/capsule.rst:96 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." +"return code somewhat ambiguous; use :c:func:`PyCapsule_IsValid` " +"or :c:func:`PyErr_Occurred` to disambiguate." msgstr "" #: c-api/capsule.rst:103 diff --git a/c-api/code.po b/c-api/code.po index 63f6a0453..b24442fd3 100644 --- a/c-api/code.po +++ b/c-api/code.po @@ -35,8 +35,8 @@ msgstr "" #: c-api/code.rst:24 msgid "" -"This is an instance of :c:type:`PyTypeObject` representing the Python :ref:" -"`code object `." +"This is an instance of :c:type:`PyTypeObject` representing the " +"Python :ref:`code object `." msgstr "" #: c-api/code.rst:30 @@ -61,8 +61,9 @@ msgstr "" #: c-api/code.rst:46 msgid "" -"Since the definition of the bytecode changes often, calling :c:func:" -"`PyUnstable_Code_New` directly can bind you to a precise Python version." +"Since the definition of the bytecode changes often, " +"calling :c:func:`PyUnstable_Code_New` directly can bind you to a precise " +"Python version." msgstr "" #: c-api/code.rst:49 @@ -119,8 +120,9 @@ msgstr "" #: c-api/code.rst:93 msgid "" -"For efficiently iterating over the line numbers in a code object, use :pep:" -"`the API described in PEP 626 <0626#out-of-process-debuggers-and-profilers>`." +"For efficiently iterating over the line numbers in a code object, " +"use :pep:`the API described in PEP 626 <0626#out-of-process-debuggers-and-" +"profilers>`." msgstr "" #: c-api/code.rst:98 @@ -180,10 +182,10 @@ msgstr "" #: c-api/code.rst:156 msgid "" -"Clear watcher identified by *watcher_id* previously returned from :c:func:" -"`PyCode_AddWatcher` for the current interpreter. Return ``0`` on success, or " -"``-1`` and set an exception on error (e.g. if the given *watcher_id* was " -"never registered.)" +"Clear watcher identified by *watcher_id* previously returned " +"from :c:func:`PyCode_AddWatcher` for the current interpreter. Return ``0`` " +"on success, or ``-1`` and set an exception on error (e.g. if the given " +"*watcher_id* was never registered.)" msgstr "" #: c-api/code.rst:165 @@ -225,8 +227,8 @@ msgstr "" #: c-api/code.rst:192 msgid "" "If the callback sets an exception, it must return ``-1``; this exception " -"will be printed as an unraisable exception using :c:func:" -"`PyErr_WriteUnraisable`. Otherwise it should return ``0``." +"will be printed as an unraisable exception " +"using :c:func:`PyErr_WriteUnraisable`. Otherwise it should return ``0``." msgstr "" #: c-api/code.rst:196 @@ -270,8 +272,8 @@ msgstr "" #: c-api/code.rst:224 msgid "" "If *free* is not ``NULL``: when a code object is deallocated, *free* will be " -"called on non-``NULL`` data stored under the new index. Use :c:func:" -"`Py_DecRef` when storing :c:type:`PyObject`." +"called on non-``NULL`` data stored under the new index. " +"Use :c:func:`Py_DecRef` when storing :c:type:`PyObject`." msgstr "" #: c-api/code.rst:230 diff --git a/c-api/codec.po b/c-api/codec.po index 526197328..b17ce5a9f 100644 --- a/c-api/codec.po +++ b/c-api/codec.po @@ -51,8 +51,8 @@ msgstr "" 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." +"may be ``NULL`` to use the default method defined for the codec. Raises " +"a :exc:`LookupError` if no encoder can be found." msgstr "" #: c-api/codec.rst:37 @@ -63,8 +63,8 @@ msgstr "" 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." +"may be ``NULL`` to use the default method defined for the codec. Raises " +"a :exc:`LookupError` if no encoder can be found." msgstr "" #: c-api/codec.rst:46 @@ -75,8 +75,8 @@ msgstr "" 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." +"mechanism effectively case-insensitive. If no codec is found, " +"a :exc:`KeyError` is set and ``NULL`` returned." msgstr "" #: c-api/codec.rst:55 @@ -123,9 +123,9 @@ msgstr "" #: c-api/codec.rst:88 msgid "" -"The callback gets a single argument, an instance of :exc:" -"`UnicodeEncodeError`, :exc:`UnicodeDecodeError` or :exc:" -"`UnicodeTranslateError` that holds information about the problematic " +"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 " diff --git a/c-api/complex.po b/c-api/complex.po index b8a7e8fc6..a2f0e5922 100644 --- a/c-api/complex.po +++ b/c-api/complex.po @@ -67,14 +67,14 @@ msgstr "" #: c-api/complex.rst:49 msgid "" -"Return the difference between two complex numbers, using the C :c:type:" -"`Py_complex` representation." +"Return the difference between two complex numbers, using the " +"C :c:type:`Py_complex` representation." msgstr "" #: c-api/complex.rst:55 msgid "" -"Return the negation of the complex number *num*, using the C :c:type:" -"`Py_complex` representation." +"Return the negation of the complex number *num*, using the " +"C :c:type:`Py_complex` representation." msgstr "" #: c-api/complex.rst:61 @@ -91,14 +91,14 @@ msgstr "" #: c-api/complex.rst:70 msgid "" -"If *divisor* is null, this method returns zero and sets :c:data:`errno` to :" -"c:macro:`!EDOM`." +"If *divisor* is null, this method returns zero and sets :c:data:`errno` " +"to :c:macro:`!EDOM`." msgstr "" #: c-api/complex.rst:76 msgid "" -"Return the exponentiation of *num* by *exp*, using the C :c:type:" -"`Py_complex` representation." +"Return the exponentiation of *num* by *exp*, using the " +"C :c:type:`Py_complex` representation." msgstr "" #: c-api/complex.rst:79 @@ -124,8 +124,8 @@ msgstr "" #: c-api/complex.rst:100 msgid "" -"Return true if its argument is a :c:type:`PyComplexObject` or a subtype of :" -"c:type:`PyComplexObject`. This function always succeeds." +"Return true if its argument is a :c:type:`PyComplexObject` or a subtype " +"of :c:type:`PyComplexObject`. This function always succeeds." msgstr "" #: c-api/complex.rst:106 @@ -166,18 +166,18 @@ msgstr "" #: c-api/complex.rst:139 msgid "" -"If *op* is not a Python complex number object but has a :meth:`~object." -"__complex__` method, this method will first be called to convert *op* to a " -"Python complex number object. If :meth:`!__complex__` is not defined then " -"it falls back to :meth:`~object.__float__`. If :meth:`!__float__` is not " -"defined then it falls back to :meth:`~object.__index__`." +"If *op* is not a Python complex number object but has " +"a :meth:`~object.__complex__` method, this method will first be called to " +"convert *op* to a Python complex number object. If :meth:`!__complex__` is " +"not defined then it falls back to :meth:`~object.__float__`. If :meth:`!" +"__float__` is not defined then it falls back to :meth:`~object.__index__`." msgstr "" #: c-api/complex.rst:145 msgid "" -"Upon failure, this method returns :c:type:`Py_complex` with :c:member:" -"`~Py_complex.real` set to ``-1.0`` and with an exception set, so one should " -"call :c:func:`PyErr_Occurred` to check for errors." +"Upon failure, this method returns :c:type:`Py_complex` " +"with :c:member:`~Py_complex.real` set to ``-1.0`` and with an exception set, " +"so one should call :c:func:`PyErr_Occurred` to check for errors." msgstr "" #: c-api/complex.rst:149 diff --git a/c-api/contextvars.po b/c-api/contextvars.po index d255afa19..7b1d2f56e 100644 --- a/c-api/contextvars.po +++ b/c-api/contextvars.po @@ -23,8 +23,9 @@ msgstr "" #: c-api/contextvars.rst:15 msgid "" "In Python 3.7.1 the signatures of all context variables C APIs were " -"**changed** to use :c:type:`PyObject` pointers instead of :c:type:" -"`PyContext`, :c:type:`PyContextVar`, and :c:type:`PyContextToken`, e.g.::" +"**changed** to use :c:type:`PyObject` pointers instead " +"of :c:type:`PyContext`, :c:type:`PyContextVar`, " +"and :c:type:`PyContextToken`, e.g.::" msgstr "" #: c-api/contextvars.rst:20 @@ -177,7 +178,7 @@ msgstr "" #: c-api/contextvars.rst:136 msgid "" -"Reset the state of the *var* context variable to that it was in before :c:" -"func:`PyContextVar_Set` that returned the *token* was called. This function " -"returns ``0`` on success and ``-1`` on error." +"Reset the state of the *var* context variable to that it was in " +"before :c:func:`PyContextVar_Set` that returned the *token* was called. This " +"function returns ``0`` on success and ``-1`` on error." msgstr "" diff --git a/c-api/conversion.po b/c-api/conversion.po index 8c0aea1b4..eab96b5e5 100644 --- a/c-api/conversion.po +++ b/c-api/conversion.po @@ -27,15 +27,15 @@ msgstr "" #: 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(3)`." +"*format* and the extra arguments. See the Unix man " +"page :manpage:`snprintf(3)`." msgstr "" #: 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(3)`." +"*format* and the variable argument list *va*. Unix man " +"page :manpage:`vsnprintf(3)`." msgstr "" #: c-api/conversion.rst:23 @@ -107,9 +107,9 @@ msgstr "" #: c-api/conversion.rst:63 msgid "" "If the converted value falls out of range of corresponding return type, " -"range error occurs (:c:data:`errno` is set to :c:macro:`!ERANGE`) and :c:" -"macro:`!ULONG_MAX` is returned. If no conversion can be performed, ``0`` is " -"returned." +"range error occurs (:c:data:`errno` is set to :c:macro:`!ERANGE`) " +"and :c:macro:`!ULONG_MAX` is returned. If no conversion can be performed, " +"``0`` is returned." msgstr "" #: c-api/conversion.rst:68 @@ -144,9 +144,9 @@ msgstr "" #: c-api/conversion.rst:95 msgid "" -"If ``endptr`` is ``NULL``, convert the whole string. Raise :exc:" -"`ValueError` and return ``-1.0`` if the string is not a valid representation " -"of a floating-point number." +"If ``endptr`` is ``NULL``, convert the whole string. " +"Raise :exc:`ValueError` and return ``-1.0`` if the string is not a valid " +"representation of a floating-point number." msgstr "" #: c-api/conversion.rst:99 diff --git a/c-api/datetime.po b/c-api/datetime.po index 6ea226719..3f60c0c74 100644 --- a/c-api/datetime.po +++ b/c-api/datetime.po @@ -24,11 +24,11 @@ msgstr "" 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." +"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 "" #: c-api/datetime.rst:18 @@ -70,8 +70,8 @@ msgstr "" #: c-api/datetime.rst:49 msgid "" "This instance of :c:type:`PyTypeObject` represents Python type for the " -"difference between two datetime values; it is the same object as :class:" -"`datetime.timedelta` in the Python layer." +"difference between two datetime values; it is the same object " +"as :class:`datetime.timedelta` in the Python layer." msgstr "" #: c-api/datetime.rst:55 @@ -86,8 +86,8 @@ msgstr "" #: c-api/datetime.rst:63 msgid "" -"Returns the time zone singleton representing UTC, the same object as :attr:" -"`datetime.timezone.utc`." +"Returns the time zone singleton representing UTC, the same object " +"as :attr:`datetime.timezone.utc`." msgstr "" #: c-api/datetime.rst:69 @@ -216,9 +216,9 @@ msgstr "" #: c-api/datetime.rst:195 msgid "" "Macros to extract fields from date objects. The argument must be an " -"instance of :c:type:`PyDateTime_Date`, including subclasses (such as :c:type:" -"`PyDateTime_DateTime`). The argument must not be ``NULL``, and the type is " -"not checked:" +"instance of :c:type:`PyDateTime_Date`, including subclasses (such " +"as :c:type:`PyDateTime_DateTime`). The argument must not be ``NULL``, and " +"the type is not checked:" msgstr "" #: c-api/datetime.rst:202 diff --git a/c-api/dict.po b/c-api/dict.po index 2bf9e75bf..eee1a9a38 100644 --- a/c-api/dict.po +++ b/c-api/dict.po @@ -71,32 +71,32 @@ msgstr "" #: c-api/dict.rst:65 msgid "" -"Insert *val* 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. This function *does not* steal a reference " -"to *val*." +"Insert *val* 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. This function *does not* steal a " +"reference to *val*." msgstr "" #: c-api/dict.rst:73 msgid "" -"This is the same as :c:func:`PyDict_SetItem`, but *key* is specified as a :c:" -"expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"This is the same as :c:func:`PyDict_SetItem`, but *key* is specified as " +"a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/dict.rst:80 msgid "" -"Remove the entry in dictionary *p* with key *key*. *key* must be :term:" -"`hashable`; if it isn't, :exc:`TypeError` is raised. If *key* is not in the " -"dictionary, :exc:`KeyError` is raised. Return ``0`` on success or ``-1`` on " -"failure." +"Remove the entry in dictionary *p* with key *key*. *key* must " +"be :term:`hashable`; if it isn't, :exc:`TypeError` is raised. If *key* is " +"not in the dictionary, :exc:`KeyError` is raised. Return ``0`` on success or " +"``-1`` on failure." msgstr "" #: c-api/dict.rst:88 msgid "" -"This is the same as :c:func:`PyDict_DelItem`, but *key* is specified as a :c:" -"expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"This is the same as :c:func:`PyDict_DelItem`, but *key* is specified as " +"a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/dict.rst:95 @@ -107,9 +107,9 @@ msgstr "" #: c-api/dict.rst:100 msgid "" -"Exceptions that occur while this calls :meth:`~object.__hash__` and :meth:" -"`~object.__eq__` methods are silently ignored. Prefer the :c:func:" -"`PyDict_GetItemWithError` function instead." +"Exceptions that occur while this calls :meth:`~object.__hash__` " +"and :meth:`~object.__eq__` methods are silently ignored. Prefer " +"the :c:func:`PyDict_GetItemWithError` function instead." msgstr "" #: c-api/dict.rst:104 @@ -127,17 +127,18 @@ msgstr "" #: c-api/dict.rst:119 msgid "" -"This is the same as :c:func:`PyDict_GetItem`, but *key* is specified as a :c:" -"expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"This is the same as :c:func:`PyDict_GetItem`, but *key* is specified as " +"a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/dict.rst:125 msgid "" -"Exceptions that occur while this calls :meth:`~object.__hash__` and :meth:" -"`~object.__eq__` methods or while creating the temporary :class:`str` object " -"are silently ignored. Prefer using the :c:func:`PyDict_GetItemWithError` " -"function with your own :c:func:`PyUnicode_FromString` *key* instead." +"Exceptions that occur while this calls :meth:`~object.__hash__` " +"and :meth:`~object.__eq__` methods or while creating the " +"temporary :class:`str` object are silently ignored. Prefer using " +"the :c:func:`PyDict_GetItemWithError` function with your " +"own :c:func:`PyUnicode_FromString` *key* instead." msgstr "" #: c-api/dict.rst:134 @@ -174,16 +175,16 @@ msgstr "" #: c-api/dict.rst:168 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:expr:" -"`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." +"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:expr:`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 "" #: c-api/dict.rst:179 @@ -241,10 +242,10 @@ msgstr "" #: c-api/dict.rst:224 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 " +"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 "" @@ -275,15 +276,15 @@ msgstr "" #: c-api/dict.rst:256 msgid "" -"Clear watcher identified by *watcher_id* previously returned from :c:func:" -"`PyDict_AddWatcher`. Return ``0`` on success, ``-1`` on error (e.g. if the " -"given *watcher_id* was never registered.)" +"Clear watcher identified by *watcher_id* previously returned " +"from :c:func:`PyDict_AddWatcher`. Return ``0`` on success, ``-1`` on error " +"(e.g. if the given *watcher_id* was never registered.)" msgstr "" #: c-api/dict.rst:264 msgid "" -"Mark dictionary *dict* as watched. The callback granted *watcher_id* by :c:" -"func:`PyDict_AddWatcher` will be called when *dict* is modified or " +"Mark dictionary *dict* as watched. The callback granted *watcher_id* " +"by :c:func:`PyDict_AddWatcher` will be called when *dict* is modified or " "deallocated. Return ``0`` on success or ``-1`` on error." msgstr "" @@ -349,8 +350,8 @@ msgstr "" #: c-api/dict.rst:316 msgid "" "If the callback sets an exception, it must return ``-1``; this exception " -"will be printed as an unraisable exception using :c:func:" -"`PyErr_WriteUnraisable`. Otherwise it should return ``0``." +"will be printed as an unraisable exception " +"using :c:func:`PyErr_WriteUnraisable`. Otherwise it should return ``0``." msgstr "" #: c-api/dict.rst:320 diff --git a/c-api/exceptions.po b/c-api/exceptions.po index 5af007709..8b75f3c65 100644 --- a/c-api/exceptions.po +++ b/c-api/exceptions.po @@ -91,9 +91,9 @@ msgstr "" msgid "" "If *set_sys_last_vars* is nonzero, the variable :data:`sys.last_exc` is set " "to the printed exception. For backwards compatibility, the deprecated " -"variables :data:`sys.last_type`, :data:`sys.last_value` and :data:`sys." -"last_traceback` are also set to the type, value and traceback of this " -"exception, respectively." +"variables :data:`sys.last_type`, :data:`sys.last_value` " +"and :data:`sys.last_traceback` are also set to the type, value and traceback " +"of this exception, respectively." msgstr "" #: c-api/exceptions.rst:69 @@ -174,8 +174,8 @@ msgstr "" 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." +"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 "" #: c-api/exceptions.rst:143 @@ -207,13 +207,14 @@ 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 :c:macro:`!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." +"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 :c:macro:`!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 "" #: c-api/exceptions.rst:186 @@ -266,9 +267,9 @@ msgstr "" msgid "" "Similar to :c:func:`PyErr_SetFromWindowsErr`, with the additional behavior " "that if *filename* is not ``NULL``, it is decoded from the filesystem " -"encoding (:func:`os.fsdecode`) and passed to the constructor of :exc:" -"`OSError` as a third parameter to be used to define the :attr:`!filename` " -"attribute of the exception instance." +"encoding (:func:`os.fsdecode`) and passed to the constructor " +"of :exc:`OSError` as a third parameter to be used to define the :attr:`!" +"filename` attribute of the exception instance." msgstr "" #: c-api/exceptions.rst:245 @@ -359,53 +360,55 @@ msgid "" "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." +"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 "" #: c-api/exceptions.rst:346 msgid "" -"Warning categories must be subclasses of :c:data:`PyExc_Warning`; :c:data:" -"`PyExc_Warning` is a subclass of :c:data:`PyExc_Exception`; the default " -"warning category is :c:data:`PyExc_RuntimeWarning`. The standard Python " -"warning categories are available as global variables whose names are " -"enumerated at :ref:`standardwarningcategories`." +"Warning categories must be subclasses " +"of :c:data:`PyExc_Warning`; :c:data:`PyExc_Warning` is a subclass " +"of :c:data:`PyExc_Exception`; the default warning category " +"is :c:data:`PyExc_RuntimeWarning`. The standard Python warning categories " +"are available as global variables whose names are enumerated " +"at :ref:`standardwarningcategories`." msgstr "" #: c-api/exceptions.rst:352 msgid "" -"For information about warning control, see the documentation for the :mod:" -"`warnings` module and the :option:`-W` option in the command line " +"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 "" #: c-api/exceptions.rst:359 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." +"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 "" #: c-api/exceptions.rst:370 msgid "" "Similar to :c:func:`PyErr_WarnExplicitObject` except that *message* and " -"*module* are UTF-8 encoded strings, and *filename* is decoded from the :term:" -"`filesystem encoding and error handler`." +"*module* are UTF-8 encoded strings, and *filename* is decoded from " +"the :term:`filesystem encoding and error handler`." msgstr "" #: c-api/exceptions.rst:377 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." +"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 "" #: c-api/exceptions.rst:386 msgid "" -"Function similar to :c:func:`PyErr_WarnFormat`, but *category* is :exc:" -"`ResourceWarning` and it passes *source* to :class:`!warnings." -"WarningMessage`." +"Function similar to :c:func:`PyErr_WarnFormat`, but *category* " +"is :exc:`ResourceWarning` and it passes *source* to :class:`!" +"warnings.WarningMessage`." msgstr "" #: c-api/exceptions.rst:393 @@ -417,8 +420,8 @@ 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 ``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." +"do not own a reference to the return value, so you do not need " +"to :c:func:`Py_DECREF` it." msgstr "" #: c-api/exceptions.rst:403 @@ -427,10 +430,11 @@ msgstr "" #: c-api/exceptions.rst:407 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.)" +"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 "" #: c-api/exceptions.rst:415 @@ -564,9 +568,10 @@ msgstr "" #: c-api/exceptions.rst:532 msgid "" -"This function *does not* implicitly set the :attr:`~BaseException." -"__traceback__` attribute on the exception value. If setting the traceback " -"appropriately is desired, the following additional snippet is needed::" +"This function *does not* implicitly set " +"the :attr:`~BaseException.__traceback__` attribute on the exception value. " +"If setting the traceback appropriately is desired, the following additional " +"snippet is needed::" msgstr "" #: c-api/exceptions.rst:537 @@ -578,10 +583,11 @@ msgstr "" #: c-api/exceptions.rst:544 msgid "" -"Retrieve the active exception instance, as would be returned by :func:`sys." -"exception`. This refers to an exception that was *already caught*, not to an " -"exception that was freshly raised. Returns a new reference to the exception " -"or ``NULL``. Does not modify the interpreter's exception state." +"Retrieve the active exception instance, as would be returned " +"by :func:`sys.exception`. This refers to an exception that was *already " +"caught*, not to an exception that was freshly raised. Returns a new " +"reference to the exception or ``NULL``. Does not modify the interpreter's " +"exception state." msgstr "" #: c-api/exceptions.rst:551 @@ -609,12 +615,12 @@ msgstr "" #: c-api/exceptions.rst:576 msgid "" -"Retrieve the old-style representation of the exception info, as known from :" -"func:`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. This function is kept for backwards compatibility. Prefer " -"using :c:func:`PyErr_GetHandledException`." +"Retrieve the old-style representation of the exception info, as known " +"from :func:`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. This function is kept for backwards " +"compatibility. Prefer using :c:func:`PyErr_GetHandledException`." msgstr "" #: c-api/exceptions.rst:585 @@ -631,8 +637,8 @@ msgid "" "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. This function is " -"kept for backwards compatibility. Prefer using :c:func:" -"`PyErr_SetHandledException`." +"kept for backwards compatibility. Prefer " +"using :c:func:`PyErr_SetHandledException`." msgstr "" #: c-api/exceptions.rst:604 @@ -671,8 +677,8 @@ msgid "" "The function attempts to handle all pending signals, and then returns ``0``. " "However, if a Python signal handler raises an exception, the error indicator " "is set and the function returns ``-1`` immediately (such that other pending " -"signals may not have been handled yet: they will be on the next :c:func:" -"`PyErr_CheckSignals()` invocation)." +"signals may not have been handled yet: they will be on the " +"next :c:func:`PyErr_CheckSignals()` invocation)." msgstr "" #: c-api/exceptions.rst:642 @@ -689,8 +695,8 @@ msgstr "" #: c-api/exceptions.rst:649 msgid "" -"The default Python signal handler for :c:macro:`!SIGINT` raises the :exc:" -"`KeyboardInterrupt` exception." +"The default Python signal handler for :c:macro:`!SIGINT` raises " +"the :exc:`KeyboardInterrupt` exception." msgstr "" #: c-api/exceptions.rst:660 @@ -701,15 +707,15 @@ msgstr "" #: c-api/exceptions.rst:691 msgid "" -"This function is async-signal-safe. It can be called without the :term:" -"`GIL` and from a C signal handler." +"This function is async-signal-safe. It can be called without " +"the :term:`GIL` and from a C signal handler." msgstr "" #: c-api/exceptions.rst:674 msgid "" -"Simulate the effect of a signal arriving. The next time :c:func:" -"`PyErr_CheckSignals` is called, the Python signal handler for the given " -"signal number will be called." +"Simulate the effect of a signal arriving. The next " +"time :c:func:`PyErr_CheckSignals` is called, the Python signal handler for " +"the given signal number will be called." msgstr "" #: c-api/exceptions.rst:678 @@ -722,8 +728,9 @@ msgstr "" #: c-api/exceptions.rst:683 msgid "" -"If the given signal isn't handled by Python (it was set to :py:const:`signal." -"SIG_DFL` or :py:const:`signal.SIG_IGN`), it will be ignored." +"If the given signal isn't handled by Python (it was set " +"to :py:const:`signal.SIG_DFL` or :py:const:`signal.SIG_IGN`), it will be " +"ignored." msgstr "" #: c-api/exceptions.rst:686 @@ -848,11 +855,11 @@ msgid "" "Implement part of the interpreter's implementation of :keyword:`!except*`. " "*orig* is the original exception that was caught, and *excs* is the list of " "the exceptions that need to be raised. This list contains the unhandled part " -"of *orig*, if any, as well as the exceptions that were raised from the :" -"keyword:`!except*` clauses (so they have a different traceback from *orig*) " -"and those that were reraised (and have the same traceback as *orig*). Return " -"the :exc:`ExceptionGroup` that needs to be reraised in the end, or ``None`` " -"if there is nothing to reraise." +"of *orig*, if any, as well as the exceptions that were raised from " +"the :keyword:`!except*` clauses (so they have a different traceback from " +"*orig*) and those that were reraised (and have the same traceback as " +"*orig*). Return the :exc:`ExceptionGroup` that needs to be reraised in the " +"end, or ``None`` if there is nothing to reraise." msgstr "" #: c-api/exceptions.rst:814 @@ -970,9 +977,9 @@ msgstr "" #: c-api/exceptions.rst:918 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. " +"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 "" @@ -986,8 +993,9 @@ msgstr "" 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 ``[...]``." +"should return a string object indicating a cycle. As " +"examples, :class:`dict` objects return ``{...}`` and :class:`list` objects " +"return ``[...]``." msgstr "" #: c-api/exceptions.rst:935 @@ -999,14 +1007,14 @@ msgstr "" #: c-api/exceptions.rst:939 msgid "" -"Otherwise, the function returns zero and the :c:member:`~PyTypeObject." -"tp_repr` implementation can continue normally." +"Otherwise, the function returns zero and " +"the :c:member:`~PyTypeObject.tp_repr` implementation can continue normally." msgstr "" #: c-api/exceptions.rst:944 msgid "" -"Ends a :c:func:`Py_ReprEnter`. Must be called once for each invocation of :" -"c:func:`Py_ReprEnter` that returns zero." +"Ends a :c:func:`Py_ReprEnter`. Must be called once for each invocation " +"of :c:func:`Py_ReprEnter` that returns zero." msgstr "" #: c-api/exceptions.rst:951 @@ -1016,9 +1024,9 @@ msgstr "" #: c-api/exceptions.rst:953 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:expr:`PyObject*`; they are all class objects. For completeness, here are " -"all the variables:" +"are ``PyExc_`` followed by the Python exception name. These have the " +"type :c:expr:`PyObject*`; they are all class objects. For completeness, " +"here are all the variables:" msgstr "" #: c-api/exceptions.rst:1147 c-api/exceptions.rst:1192 @@ -1464,14 +1472,8 @@ msgstr "" #: c-api/exceptions.rst:1123 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`." +":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 "" #: c-api/exceptions.rst:1133 diff --git a/c-api/file.po b/c-api/file.po index 2fafda9b4..7fa29db30 100644 --- a/c-api/file.po +++ b/c-api/file.po @@ -24,12 +24,12 @@ msgstr "" 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:expr:`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." +"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 "" #: c-api/file.rst:22 @@ -56,23 +56,23 @@ msgstr "" #: c-api/file.rst:41 msgid "" "Return the file descriptor associated with *p* as an :c:expr:`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." +"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 "" #: 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." +"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 "" #: c-api/file.rst:65 diff --git a/c-api/float.po b/c-api/float.po index 8a677c385..a697679ed 100644 --- a/c-api/float.po +++ b/c-api/float.po @@ -33,8 +33,8 @@ msgstr "" #: c-api/float.rst:24 msgid "" -"Return true if its argument is a :c:type:`PyFloatObject` or a subtype of :c:" -"type:`PyFloatObject`. This function always succeeds." +"Return true if its argument is a :c:type:`PyFloatObject` or a subtype " +"of :c:type:`PyFloatObject`. This function always succeeds." msgstr "" #: c-api/float.rst:30 @@ -57,11 +57,11 @@ msgstr "" #: c-api/float.rst:47 msgid "" "Return a C :c:expr:`double` representation of the contents of *pyfloat*. If " -"*pyfloat* is not a Python floating-point object but has a :meth:`~object." -"__float__` method, this method will first be called to convert *pyfloat* " -"into a float. If :meth:`!__float__` is not defined then it falls back to :" -"meth:`~object.__index__`. This method returns ``-1.0`` upon failure, so one " -"should call :c:func:`PyErr_Occurred` to check for errors." +"*pyfloat* is not a Python floating-point object but has " +"a :meth:`~object.__float__` method, this method will first be called to " +"convert *pyfloat* into a float. If :meth:`!__float__` is not defined then it " +"falls back to :meth:`~object.__index__`. This method returns ``-1.0`` upon " +"failure, so one should call :c:func:`PyErr_Occurred` to check for errors." msgstr "" #: c-api/float.rst:54 @@ -83,8 +83,8 @@ msgstr "" #: c-api/float.rst:73 msgid "" -"Return the maximum representable finite float *DBL_MAX* as C :c:expr:" -"`double`." +"Return the maximum representable finite float *DBL_MAX* as " +"C :c:expr:`double`." msgstr "" #: c-api/float.rst:78 @@ -100,9 +100,9 @@ msgstr "" msgid "" "The pack and unpack functions provide an efficient platform-independent way " "to store floating-point values as byte strings. The Pack routines produce a " -"bytes string from a C :c:expr:`double`, and the Unpack routines produce a C :" -"c:expr:`double` from such a bytes string. The suffix (2, 4 or 8) specifies " -"the number of bytes in the bytes string." +"bytes string from a C :c:expr:`double`, and the Unpack routines produce a " +"C :c:expr:`double` from such a bytes string. The suffix (2, 4 or 8) " +"specifies the number of bytes in the bytes string." msgstr "" #: c-api/float.rst:90 @@ -131,12 +131,13 @@ msgstr "" #: c-api/float.rst:109 msgid "" -"The pack routines write 2, 4 or 8 bytes, starting at *p*. *le* is an :c:expr:" -"`int` argument, non-zero if you want the bytes string in little-endian " -"format (exponent last, at ``p+1``, ``p+3``, or ``p+6`` ``p+7``), zero if you " -"want big-endian format (exponent first, at *p*). The :c:macro:" -"`PY_BIG_ENDIAN` constant can be used to use the native endian: it is equal " -"to ``1`` on big endian processor, or ``0`` on little endian processor." +"The pack routines write 2, 4 or 8 bytes, starting at *p*. *le* is " +"an :c:expr:`int` argument, non-zero if you want the bytes string in little-" +"endian format (exponent last, at ``p+1``, ``p+3``, or ``p+6`` ``p+7``), zero " +"if you want big-endian format (exponent first, at *p*). " +"The :c:macro:`PY_BIG_ENDIAN` constant can be used to use the native endian: " +"it is equal to ``1`` on big endian processor, or ``0`` on little endian " +"processor." msgstr "" #: c-api/float.rst:116 @@ -175,19 +176,19 @@ msgstr "" #: c-api/float.rst:140 msgid "" -"The unpack routines read 2, 4 or 8 bytes, starting at *p*. *le* is an :c:" -"expr:`int` argument, non-zero if the bytes string is in little-endian format " -"(exponent last, at ``p+1``, ``p+3`` or ``p+6`` and ``p+7``), zero if big-" -"endian (exponent first, at *p*). The :c:macro:`PY_BIG_ENDIAN` constant can " -"be used to use the native endian: it is equal to ``1`` on big endian " +"The unpack routines read 2, 4 or 8 bytes, starting at *p*. *le* is " +"an :c:expr:`int` argument, non-zero if the bytes string is in little-endian " +"format (exponent last, at ``p+1``, ``p+3`` or ``p+6`` and ``p+7``), zero if " +"big-endian (exponent first, at *p*). The :c:macro:`PY_BIG_ENDIAN` constant " +"can be used to use the native endian: it is equal to ``1`` on big endian " "processor, or ``0`` on little endian processor." msgstr "" #: c-api/float.rst:147 msgid "" -"Return value: The unpacked double. On error, this is ``-1.0`` and :c:func:" -"`PyErr_Occurred` is true (and an exception is set, most likely :exc:" -"`OverflowError`)." +"Return value: The unpacked double. On error, this is ``-1.0`` " +"and :c:func:`PyErr_Occurred` is true (and an exception is set, most " +"likely :exc:`OverflowError`)." msgstr "" #: c-api/float.rst:151 diff --git a/c-api/frame.po b/c-api/frame.po index 89b34e55a..d731cb1f6 100644 --- a/c-api/frame.po +++ b/c-api/frame.po @@ -46,8 +46,8 @@ msgstr "" #: c-api/frame.rst:24 msgid "" -"The type of frame objects. It is the same object as :py:class:`types." -"FrameType` in the Python layer." +"The type of frame objects. It is the same object " +"as :py:class:`types.FrameType` in the Python layer." msgstr "" #: c-api/frame.rst:29 @@ -61,8 +61,8 @@ msgstr "" #: c-api/frame.rst:38 msgid "" -"Previously, this function was only available after including ````." +"Previously, this function was only available after including " +"````." msgstr "" #: c-api/frame.rst:43 diff --git a/c-api/function.po b/c-api/function.po index 455b19286..4f3a939be 100644 --- a/c-api/function.po +++ b/c-api/function.po @@ -31,15 +31,15 @@ msgstr "" #: 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``." +"function type. It is exposed to Python programmers as " +"``types.FunctionType``." msgstr "" #: 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``. This function " -"always succeeds." +"Return true if *o* is a function object (has " +"type :c:data:`PyFunction_Type`). The parameter must not be ``NULL``. This " +"function always succeeds." msgstr "" #: c-api/function.rst:34 @@ -51,19 +51,20 @@ msgstr "" #: c-api/function.rst:37 msgid "" -"The function's docstring and name are retrieved from the code object. :attr:" -"`~function.__module__` is retrieved from *globals*. The argument defaults, " -"annotations and closure are set to ``NULL``. :attr:`~function.__qualname__` " -"is set to the same value as the code object's :attr:`~codeobject." -"co_qualname` field." +"The function's docstring and name are retrieved from the code " +"object. :attr:`~function.__module__` is retrieved from *globals*. The " +"argument defaults, annotations and closure are set to " +"``NULL``. :attr:`~function.__qualname__` is set to the same value as the " +"code object's :attr:`~codeobject.co_qualname` field." msgstr "" #: c-api/function.rst:46 msgid "" -"As :c:func:`PyFunction_New`, but also allows setting the function object's :" -"attr:`~function.__qualname__` attribute. *qualname* should be a unicode " -"object or ``NULL``; if ``NULL``, the :attr:`!__qualname__` attribute is set " -"to the same value as the code object's :attr:`~codeobject.co_qualname` field." +"As :c:func:`PyFunction_New`, but also allows setting the function " +"object's :attr:`~function.__qualname__` attribute. *qualname* should be a " +"unicode object or ``NULL``; if ``NULL``, the :attr:`!__qualname__` attribute " +"is set to the same value as the code " +"object's :attr:`~codeobject.co_qualname` field." msgstr "" #: c-api/function.rst:57 @@ -147,10 +148,10 @@ msgstr "" #: c-api/function.rst:138 msgid "" -"Clear watcher identified by *watcher_id* previously returned from :c:func:" -"`PyFunction_AddWatcher` for the current interpreter. Return ``0`` on " -"success, or ``-1`` and set an exception on error (e.g. if the given " -"*watcher_id* was never registered.)" +"Clear watcher identified by *watcher_id* previously returned " +"from :c:func:`PyFunction_AddWatcher` for the current interpreter. Return " +"``0`` on success, or ``-1`` and set an exception on error (e.g. if the " +"given *watcher_id* was never registered.)" msgstr "" #: c-api/function.rst:148 @@ -168,9 +169,9 @@ msgstr "" #: c-api/function.rst:162 msgid "" "If *event* is ``PyFunction_EVENT_CREATE`` or ``PyFunction_EVENT_DESTROY`` " -"then *new_value* will be ``NULL``. Otherwise, *new_value* will hold a :term:" -"`borrowed reference` to the new value that is about to be stored in *func* " -"for the attribute that is being modified." +"then *new_value* will be ``NULL``. Otherwise, *new_value* will hold " +"a :term:`borrowed reference` to the new value that is about to be stored in " +"*func* for the attribute that is being modified." msgstr "" #: c-api/function.rst:167 @@ -202,8 +203,8 @@ msgstr "" #: c-api/function.rst:184 msgid "" "If the callback sets an exception, it must return ``-1``; this exception " -"will be printed as an unraisable exception using :c:func:" -"`PyErr_WriteUnraisable`. Otherwise it should return ``0``." +"will be printed as an unraisable exception " +"using :c:func:`PyErr_WriteUnraisable`. Otherwise it should return ``0``." msgstr "" #: c-api/function.rst:188 diff --git a/c-api/gcsupport.po b/c-api/gcsupport.po index bc9542c4d..6aee35a82 100644 --- a/c-api/gcsupport.po +++ b/c-api/gcsupport.po @@ -74,8 +74,8 @@ msgstr "" #: c-api/gcsupport.rst:37 msgid "" -"Before fields which refer to other containers are invalidated, :c:func:" -"`PyObject_GC_UnTrack` must be called." +"Before fields which refer to other containers are " +"invalidated, :c:func:`PyObject_GC_UnTrack` must be called." msgstr "" #: c-api/gcsupport.rst:40 @@ -85,32 +85,32 @@ msgstr "" #: c-api/gcsupport.rst:43 msgid "" -"If a type adds the Py_TPFLAGS_HAVE_GC, then it *must* implement at least a :" -"c:member:`~PyTypeObject.tp_traverse` handler or explicitly use one from its " -"subclass or subclasses." +"If a type adds the Py_TPFLAGS_HAVE_GC, then it *must* implement at least " +"a :c:member:`~PyTypeObject.tp_traverse` handler or explicitly use one from " +"its subclass or subclasses." msgstr "" #: c-api/gcsupport.rst:47 msgid "" "When calling :c:func:`PyType_Ready` or some of the APIs that indirectly call " "it like :c:func:`PyType_FromSpecWithBases` or :c:func:`PyType_FromSpec` the " -"interpreter will automatically populate the :c:member:`~PyTypeObject." -"tp_flags`, :c:member:`~PyTypeObject.tp_traverse` and :c:member:" -"`~PyTypeObject.tp_clear` fields if the type inherits from a class that " -"implements the garbage collector protocol and the child class does *not* " -"include the :c:macro:`Py_TPFLAGS_HAVE_GC` flag." +"interpreter will automatically populate " +"the :c:member:`~PyTypeObject.tp_flags`, :c:member:`~PyTypeObject.tp_traverse` " +"and :c:member:`~PyTypeObject.tp_clear` fields if the type inherits from a " +"class that implements the garbage collector protocol and the child class " +"does *not* include the :c:macro:`Py_TPFLAGS_HAVE_GC` flag." msgstr "" #: c-api/gcsupport.rst:57 msgid "" -"Analogous to :c:macro:`PyObject_New` but for container objects with the :c:" -"macro:`Py_TPFLAGS_HAVE_GC` flag set." +"Analogous to :c:macro:`PyObject_New` but for container objects with " +"the :c:macro:`Py_TPFLAGS_HAVE_GC` flag set." msgstr "" #: c-api/gcsupport.rst:62 msgid "" -"Analogous to :c:macro:`PyObject_NewVar` but for container objects with the :" -"c:macro:`Py_TPFLAGS_HAVE_GC` flag set." +"Analogous to :c:macro:`PyObject_NewVar` but for container objects with " +"the :c:macro:`Py_TPFLAGS_HAVE_GC` flag set." msgstr "" #: c-api/gcsupport.rst:67 @@ -131,8 +131,8 @@ msgstr "" msgid "" "The function is marked as unstable because the final mechanism for reserving " "extra data after an instance is not yet decided. For allocating a variable " -"number of fields, prefer using :c:type:`PyVarObject` and :c:member:" -"`~PyTypeObject.tp_itemsize` instead." +"number of fields, prefer using :c:type:`PyVarObject` " +"and :c:member:`~PyTypeObject.tp_itemsize` instead." msgstr "" #: c-api/gcsupport.rst:88 @@ -191,18 +191,18 @@ msgstr "" #: c-api/gcsupport.rst:136 msgid "" -"Releases memory allocated to an object using :c:macro:`PyObject_GC_New` or :" -"c:macro:`PyObject_GC_NewVar`." +"Releases memory allocated to an object using :c:macro:`PyObject_GC_New` " +"or :c:macro:`PyObject_GC_NewVar`." msgstr "" #: c-api/gcsupport.rst:142 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." +"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 "" #: c-api/gcsupport.rst:151 @@ -219,12 +219,12 @@ msgstr "" #: c-api/gcsupport.rst:159 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." +"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 "" #: c-api/gcsupport.rst:166 @@ -245,10 +245,10 @@ msgstr "" #: c-api/gcsupport.rst:178 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*:" +"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 "" #: c-api/gcsupport.rst:185 @@ -271,8 +271,8 @@ msgstr "" #: c-api/gcsupport.rst:198 msgid "" -"The :c:member:`~PyTypeObject.tp_clear` handler must be of the :c:type:" -"`inquiry` type, or ``NULL`` if the object is immutable." +"The :c:member:`~PyTypeObject.tp_clear` handler must be of " +"the :c:type:`inquiry` type, or ``NULL`` if the object is immutable." msgstr "" #: c-api/gcsupport.rst:204 @@ -305,8 +305,8 @@ msgstr "" msgid "" "Returns the number of collected + unreachable objects which cannot be " "collected. If the garbage collector is disabled or already collecting, " -"returns ``0`` immediately. Errors during garbage collection are passed to :" -"data:`sys.unraisablehook`. This function does not raise exceptions." +"returns ``0`` immediately. Errors during garbage collection are passed " +"to :data:`sys.unraisablehook`. This function does not raise exceptions." msgstr "" #: c-api/gcsupport.rst:233 @@ -358,9 +358,9 @@ msgstr "" #: c-api/gcsupport.rst:278 msgid "" -"Type of the visitor function to be passed to :c:func:" -"`PyUnstable_GC_VisitObjects`. *arg* is the same as the *arg* passed to " -"``PyUnstable_GC_VisitObjects``. Return ``0`` to continue iteration, return " -"``1`` to stop iteration. Other return values are reserved for now so " -"behavior on returning anything else is undefined." +"Type of the visitor function to be passed " +"to :c:func:`PyUnstable_GC_VisitObjects`. *arg* is the same as the *arg* " +"passed to ``PyUnstable_GC_VisitObjects``. Return ``0`` to continue " +"iteration, return ``1`` to stop iteration. Other return values are reserved " +"for now so behavior on returning anything else is undefined." msgstr "" diff --git a/c-api/gen.po b/c-api/gen.po index f818bd8b2..115f57b67 100644 --- a/c-api/gen.po +++ b/c-api/gen.po @@ -24,8 +24,8 @@ msgstr "" 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`." +"rather than explicitly calling :c:func:`PyGen_New` " +"or :c:func:`PyGen_NewWithQualName`." msgstr "" #: c-api/gen.rst:15 diff --git a/c-api/import.po b/c-api/import.po index 15e5e8c97..b1c978c8a 100644 --- a/c-api/import.po +++ b/c-api/import.po @@ -22,8 +22,8 @@ msgstr "" #: c-api/import.rst:16 msgid "" -"This is a wrapper around :c:func:`PyImport_Import()` which takes a :c:expr:" -"`const char *` as an argument instead of a :c:expr:`PyObject *`." +"This is a wrapper around :c:func:`PyImport_Import()` which takes " +"a :c:expr:`const char *` as an argument instead of a :c:expr:`PyObject *`." msgstr "" #: c-api/import.rst:21 @@ -47,15 +47,16 @@ msgstr "" #: c-api/import.rst:53 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." +"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 "" #: c-api/import.rst:43 msgid "" -"Failing imports remove incomplete module objects, like with :c:func:" -"`PyImport_ImportModule`." +"Failing imports remove incomplete module objects, like " +"with :c:func:`PyImport_ImportModule`." msgstr "" #: c-api/import.rst:49 @@ -105,10 +106,10 @@ msgstr "" #: c-api/import.rst:95 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." +"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 "" #: c-api/import.rst:105 @@ -124,11 +125,11 @@ msgid "" "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 :data:`sys.modules` in error cases, even if *name* " -"was already in :data:`sys.modules` on entry to :c:func:" -"`PyImport_ExecCodeModule`. Leaving incompletely initialized modules in :" -"data:`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." +"was already in :data:`sys.modules` on entry " +"to :c:func:`PyImport_ExecCodeModule`. Leaving incompletely initialized " +"modules in :data:`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 "" #: c-api/import.rst:123 @@ -142,14 +143,14 @@ msgstr "" #: c-api/import.rst:128 msgid "" "The module's :attr:`~module.__file__` attribute will be set to the code " -"object's :attr:`~codeobject.co_filename`. If applicable, :attr:`~module." -"__cached__` will also be set." +"object's :attr:`~codeobject.co_filename`. If " +"applicable, :attr:`~module.__cached__` will also be set." msgstr "" #: c-api/import.rst:132 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." +"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 "" #: c-api/import.rst:135 @@ -160,8 +161,8 @@ msgstr "" #: c-api/import.rst:138 msgid "" -"See also :c:func:`PyImport_ExecCodeModuleEx` and :c:func:" -"`PyImport_ExecCodeModuleWithPathnames`." +"See also :c:func:`PyImport_ExecCodeModuleEx` " +"and :c:func:`PyImport_ExecCodeModuleWithPathnames`." msgstr "" #: c-api/import.rst:141 @@ -189,8 +190,8 @@ msgstr "" #: c-api/import.rst:163 msgid "" -"Setting :attr:`~module.__cached__` is deprecated. See :class:`~importlib." -"machinery.ModuleSpec` for alternatives." +"Setting :attr:`~module.__cached__` is deprecated. " +"See :class:`~importlib.machinery.ModuleSpec` for alternatives." msgstr "" #: c-api/import.rst:170 @@ -231,8 +232,8 @@ msgstr "" #: c-api/import.rst:203 msgid "" -"Return the dictionary used for the module administration (a.k.a. ``sys." -"modules``). Note that this is a per-interpreter variable." +"Return the dictionary used for the module administration (a.k.a. " +"``sys.modules``). Note that this is a per-interpreter variable." msgstr "" #: c-api/import.rst:208 @@ -249,17 +250,18 @@ msgid "" "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." +"finder for this path item. Cache the result " +"in :data:`sys.path_importer_cache`. Return a new reference to the finder " +"object." msgstr "" #: c-api/import.rst:227 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.)" +"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 "" #: c-api/import.rst:235 @@ -276,8 +278,8 @@ msgstr "" 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::" +"Python source distribution). Its definition, found in :file:`Include/" +"import.h`, is::" msgstr "" #: c-api/import.rst:254 @@ -334,12 +336,12 @@ msgstr "" #: c-api/import.rst:302 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 :c:" -"member:`~_inittab.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 must be called " -"before :c:func:`Py_Initialize`." +"array must end with a sentinel entry which contains ``NULL`` for " +"the :c:member:`~_inittab.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 must be " +"called before :c:func:`Py_Initialize`." msgstr "" #: c-api/import.rst:309 diff --git a/c-api/index.po b/c-api/index.po index 263c52168..293657443 100644 --- a/c-api/index.po +++ b/c-api/index.po @@ -23,9 +23,9 @@ msgstr "Python/C API Referans Kılavuzu" #: 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." +"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 "" "Bu kılavuz, genişletme modülleri yazmak veya Python'u gömmek isteyen C ve C+" "+ programcıları tarafından kullanılan API'yi belgelemektedir. Uzantı " diff --git a/c-api/init.po b/c-api/init.po index e5fceca7a..b5111444b 100644 --- a/c-api/init.po +++ b/c-api/init.po @@ -163,11 +163,9 @@ msgstr "" #: c-api/init.rst:64 msgid "" -"The following functions **should not be called** before :c:func:" -"`Py_Initialize`: :c:func:`Py_EncodeLocale`, :c:func:`Py_GetPath`, :c:func:" -"`Py_GetPrefix`, :c:func:`Py_GetExecPrefix`, :c:func:" -"`Py_GetProgramFullPath`, :c:func:`Py_GetPythonHome`, :c:func:" -"`Py_GetProgramName` and :c:func:`PyEval_InitThreads`." +"The following functions **should not be called** " +"before :c:func:`Py_Initialize`: :c:func:`Py_EncodeLocale`, :c:func:`Py_GetPath`, :c:func:`Py_GetPrefix`, :c:func:`Py_GetExecPrefix`, :c:func:`Py_GetProgramFullPath`, :c:func:`Py_GetPythonHome`, :c:func:`Py_GetProgramName` " +"and :c:func:`PyEval_InitThreads`." msgstr "" #: c-api/init.rst:74 @@ -177,30 +175,30 @@ msgstr "" #: c-api/init.rst:76 msgid "" "Python has variables for the global configuration to control different " -"features and options. By default, these flags are controlled by :ref:" -"`command line options `." +"features and options. By default, these flags are controlled " +"by :ref:`command line options `." msgstr "" #: c-api/init.rst:80 msgid "" "When a flag is set by an option, the value of the flag is the number of " -"times that the option was set. For example, ``-b`` sets :c:data:" -"`Py_BytesWarningFlag` to 1 and ``-bb`` sets :c:data:`Py_BytesWarningFlag` to " -"2." +"times that the option was set. For example, ``-b`` " +"sets :c:data:`Py_BytesWarningFlag` to 1 and ``-bb`` " +"sets :c:data:`Py_BytesWarningFlag` to 2." msgstr "" #: c-api/init.rst:86 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"bytes_warning` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.bytes_warning` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:90 msgid "" -"Issue a warning when comparing :class:`bytes` or :class:`bytearray` with :" -"class:`str` or :class:`bytes` with :class:`int`. Issue an error if greater " -"or equal to ``2``." +"Issue a warning when comparing :class:`bytes` or :class:`bytearray` " +"with :class:`str` or :class:`bytes` with :class:`int`. Issue an error if " +"greater or equal to ``2``." msgstr "" #: c-api/init.rst:94 @@ -209,9 +207,9 @@ msgstr "" #: c-api/init.rst:100 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"parser_debug` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.parser_debug` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:104 @@ -228,9 +226,9 @@ msgstr "" #: c-api/init.rst:114 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"write_bytecode` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.write_bytecode` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:118 @@ -247,15 +245,15 @@ msgstr "" #: c-api/init.rst:128 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"pathconfig_warnings` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.pathconfig_warnings` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:132 msgid "" -"Suppress error messages when calculating the module search path in :c:func:" -"`Py_GetPath`." +"Suppress error messages when calculating the module search path " +"in :c:func:`Py_GetPath`." msgstr "" #: c-api/init.rst:135 @@ -264,8 +262,9 @@ msgstr "" #: c-api/init.rst:141 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"hash_seed` and :c:member:`PyConfig.use_hash_seed` should be used instead, " +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.hash_seed` " +"and :c:member:`PyConfig.use_hash_seed` should be used instead, " "see :ref:`Python Initialization Configuration `." msgstr "" @@ -283,15 +282,15 @@ msgstr "" #: c-api/init.rst:156 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"use_environment` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.use_environment` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:160 msgid "" -"Ignore all :envvar:`!PYTHON*` environment variables, e.g. :envvar:" -"`PYTHONPATH` and :envvar:`PYTHONHOME`, that might be set." +"Ignore all :envvar:`!PYTHON*` environment variables, " +"e.g. :envvar:`PYTHONPATH` and :envvar:`PYTHONHOME`, that might be set." msgstr "" #: c-api/init.rst:163 @@ -300,9 +299,9 @@ msgstr "" #: c-api/init.rst:169 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"inspect` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.inspect` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:173 @@ -320,9 +319,9 @@ msgstr "" #: c-api/init.rst:184 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"interactive` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.interactive` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:188 @@ -331,9 +330,9 @@ msgstr "" #: c-api/init.rst:194 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"isolated` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.isolated` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:198 @@ -348,9 +347,9 @@ msgstr "" #: c-api/init.rst:209 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyPreConfig." -"legacy_windows_fs_encoding` should be used instead, see :ref:`Python " -"Initialization Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyPreConfig.legacy_windows_fs_encoding` should be used " +"instead, see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:213 @@ -376,15 +375,15 @@ msgstr "" #: c-api/init.rst:228 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"legacy_windows_stdio` should be used instead, see :ref:`Python " -"Initialization Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.legacy_windows_stdio` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:232 msgid "" -"If the flag is non-zero, use :class:`io.FileIO` instead of :class:`!io." -"_WindowsConsoleIO` for :mod:`sys` standard streams." +"If the flag is non-zero, use :class:`io.FileIO` instead of :class:`!" +"io._WindowsConsoleIO` for :mod:`sys` standard streams." msgstr "" #: c-api/init.rst:235 @@ -399,17 +398,17 @@ msgstr "" #: c-api/init.rst:246 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"site_import` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.site_import` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:250 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)." +"manipulations if :mod:`site` is explicitly imported later " +"(call :func:`site.main` if you want them to be triggered)." msgstr "" #: c-api/init.rst:255 @@ -418,28 +417,28 @@ msgstr "" #: c-api/init.rst:261 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"user_site_directory` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.user_site_directory` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:265 msgid "" -"Don't add the :data:`user site-packages directory ` to :data:" -"`sys.path`." +"Don't add the :data:`user site-packages directory ` " +"to :data:`sys.path`." msgstr "" #: c-api/init.rst:268 msgid "" -"Set by the :option:`-s` and :option:`-I` options, and the :envvar:" -"`PYTHONNOUSERSITE` environment variable." +"Set by the :option:`-s` and :option:`-I` options, and " +"the :envvar:`PYTHONNOUSERSITE` environment variable." msgstr "" #: c-api/init.rst:275 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"optimization_level` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.optimization_level` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:279 @@ -450,9 +449,9 @@ msgstr "" #: c-api/init.rst:286 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"quiet` should be used instead, see :ref:`Python Initialization Configuration " -"`." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.quiet` should be used instead, see :ref:`Python " +"Initialization Configuration `." msgstr "" #: c-api/init.rst:290 @@ -466,9 +465,9 @@ msgstr "" #: c-api/init.rst:300 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"buffered_stdio` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.buffered_stdio` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:304 @@ -483,9 +482,9 @@ msgstr "" #: c-api/init.rst:313 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"verbose` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.verbose` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:317 @@ -509,8 +508,9 @@ msgstr "" #: c-api/init.rst:347 msgid "" "Initialize the Python interpreter. In an application embedding Python, " -"this should be called before using any other Python/C API functions; see :" -"ref:`Before Python Initialization ` for the few exceptions." +"this should be called before using any other Python/C API functions; " +"see :ref:`Before Python Initialization ` for the few " +"exceptions." msgstr "" #: c-api/init.rst:351 @@ -525,8 +525,8 @@ msgstr "" #: c-api/init.rst:373 msgid "" -"Use the :c:func:`Py_InitializeFromConfig` function to customize the :ref:" -"`Python Initialization Configuration `." +"Use the :c:func:`Py_InitializeFromConfig` function to customize " +"the :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:363 @@ -552,19 +552,20 @@ msgstr "" #: c-api/init.rst:386 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)." +"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)." msgstr "" #: c-api/init.rst:393 msgid "" "Since this is the reverse of :c:func:`Py_Initialize`, it should be called in " "the same thread with the same interpreter active. That means the main " -"thread and the main interpreter. This should never be called while :c:func:" -"`Py_RunMain` is running." +"thread and the main interpreter. This should never be called " +"while :c:func:`Py_RunMain` is running." msgstr "" #: c-api/init.rst:398 @@ -601,8 +602,8 @@ msgstr "" #: c-api/init.rst:421 msgid "" -"Raises an :ref:`auditing event ` ``cpython." -"_PySys_ClearAuditHooks`` with no arguments." +"Raises an :ref:`auditing event ` " +"``cpython._PySys_ClearAuditHooks`` with no arguments." msgstr "" #: c-api/init.rst:427 @@ -617,9 +618,10 @@ msgstr "" #: c-api/init.rst:442 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"stdio_encoding` and :c:member:`PyConfig.stdio_errors` should be used " -"instead, see :ref:`Python Initialization Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.stdio_encoding` " +"and :c:member:`PyConfig.stdio_errors` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:447 @@ -661,9 +663,9 @@ msgstr "" #: c-api/init.rst:479 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"program_name` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.program_name` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:483 @@ -682,8 +684,8 @@ msgstr "" #: c-api/init.rst:494 msgid "" -"Use :c:func:`Py_DecodeLocale` to decode a bytes string to get a :c:expr:" -"`wchar_t *` string." +"Use :c:func:`Py_DecodeLocale` to decode a bytes string to get " +"a :c:expr:`wchar_t *` string." msgstr "" #: c-api/init.rst:504 @@ -724,11 +726,11 @@ msgid "" "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." +"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 "" #: c-api/init.rst:546 @@ -756,10 +758,10 @@ msgstr "" #: c-api/init.rst:563 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." +"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 "" #: c-api/init.rst:581 @@ -786,35 +788,35 @@ msgstr "" #: c-api/init.rst:627 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"module_search_paths` and :c:member:`PyConfig.module_search_paths_set` should " -"be used instead, see :ref:`Python Initialization Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.module_search_paths` " +"and :c:member:`PyConfig.module_search_paths_set` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:632 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 macOS, ``';'`` " -"on Windows." +"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 macOS, " +"``';'`` on Windows." msgstr "" #: c-api/init.rst:640 msgid "" "This also causes :data:`sys.executable` to be set to the program full path " -"(see :c:func:`Py_GetProgramFullPath`) 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`." +"(see :c:func:`Py_GetProgramFullPath`) 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 "" #: c-api/init.rst:760 c-api/init.rst:822 msgid "" -"Use :c:func:`Py_DecodeLocale` to decode a bytes string to get a :c:expr:" -"`wchar_*` string." +"Use :c:func:`Py_DecodeLocale` to decode a bytes string to get " +"a :c:expr:`wchar_*` string." msgstr "" #: c-api/init.rst:648 @@ -844,8 +846,8 @@ msgid "" "The first word (up to the first space character) is the current Python " "version; the first 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`." +"not modify its value. The value is available to Python code " +"as :data:`sys.version`." msgstr "" #: c-api/init.rst:672 @@ -908,10 +910,10 @@ msgstr "" #: c-api/init.rst:735 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"argv`, :c:member:`PyConfig.parse_argv` and :c:member:`PyConfig.safe_path` " -"should be used instead, see :ref:`Python Initialization Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.argv`, :c:member:`PyConfig.parse_argv` " +"and :c:member:`PyConfig.safe_path` should be used instead, see :ref:`Python " +"Initialization Configuration `." msgstr "" #: c-api/init.rst:740 @@ -935,8 +937,8 @@ msgstr "" #: c-api/init.rst:752 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`." +"path of the directory where the script is located is prepended " +"to :data:`sys.path`." msgstr "" #: c-api/init.rst:755 @@ -962,8 +964,8 @@ msgstr "" #: c-api/init.rst:772 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::" +"popping the first :data:`sys.path` element after having " +"called :c:func:`PySys_SetArgv`, for example using::" msgstr "" #: c-api/init.rst:776 @@ -972,16 +974,17 @@ msgstr "" #: c-api/init.rst:788 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"argv` and :c:member:`PyConfig.parse_argv` should be used instead, see :ref:" -"`Python Initialization Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.argv` and :c:member:`PyConfig.parse_argv` should " +"be used instead, see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/init.rst:792 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`." +"``1`` unless the :program:`python` interpreter was started with " +"the :option:`-I`." msgstr "" #: c-api/init.rst:802 @@ -990,9 +993,9 @@ msgstr "" #: c-api/init.rst:809 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"home` should be used instead, see :ref:`Python Initialization Configuration " -"`." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.home` should be used instead, see :ref:`Python " +"Initialization Configuration `." msgstr "" #: c-api/init.rst:813 @@ -1012,8 +1015,8 @@ msgstr "" #: c-api/init.rst:830 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` " +"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 "" @@ -1035,12 +1038,13 @@ msgstr "" #: c-api/init.rst:861 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." +"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 "" #: c-api/init.rst:871 @@ -1128,10 +1132,10 @@ msgstr "" #: c-api/init.rst:936 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 " +"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 "" @@ -1171,9 +1175,9 @@ msgstr "" msgid "" "Note that the ``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 " -"``PyGILState_*`` API is unsupported." +"supports the creation of additional interpreters " +"(using :c:func:`Py_NewInterpreter`), but mixing multiple interpreters and " +"the ``PyGILState_*`` API is unsupported." msgstr "" #: c-api/init.rst:975 @@ -1199,11 +1203,11 @@ msgid "" "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_Child` tries to reset the necessary " -"locks, but is not always able to." +"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_Child` tries to reset the " +"necessary locks, but is not always able to." msgstr "" #: c-api/init.rst:998 @@ -1341,21 +1345,21 @@ msgid "" "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." +"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 "" #: c-api/init.rst:1129 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`." +"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 "" #: c-api/init.rst:1136 @@ -1367,15 +1371,15 @@ msgstr "" #: c-api/init.rst:1148 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)." +"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 "" #: c-api/init.rst:1153 msgid "" -"Every call to :c:func:`PyGILState_Ensure` must be matched by a call to :c:" -"func:`PyGILState_Release` on the same thread." +"Every call to :c:func:`PyGILState_Ensure` must be matched by a call " +"to :c:func:`PyGILState_Release` on the same thread." msgstr "" #: c-api/init.rst:1159 @@ -1405,30 +1409,30 @@ msgstr "" #: c-api/init.rst:1185 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." +"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." msgstr "" #: c-api/init.rst:1193 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." +"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." msgstr "" #: c-api/init.rst:1201 msgid "" -"This macro expands to ``PyEval_RestoreThread(_save);``: it is equivalent to :" -"c:macro:`Py_END_ALLOW_THREADS` without the closing brace." +"This macro expands to ``PyEval_RestoreThread(_save);``: it is equivalent " +"to :c:macro:`Py_END_ALLOW_THREADS` without the closing brace." msgstr "" #: c-api/init.rst:1207 msgid "" -"This macro expands to ``_save = PyEval_SaveThread();``: it is equivalent to :" -"c:macro:`Py_BEGIN_ALLOW_THREADS` without the opening brace and variable " +"This macro expands to ``_save = PyEval_SaveThread();``: it is equivalent " +"to :c:macro:`Py_BEGIN_ALLOW_THREADS` without the opening brace and variable " "declaration." msgstr "" @@ -1454,8 +1458,8 @@ msgstr "" #: c-api/init.rst:1227 msgid "" -"Raises an :ref:`auditing event ` ``cpython." -"PyInterpreterState_New`` with no arguments." +"Raises an :ref:`auditing event ` " +"``cpython.PyInterpreterState_New`` with no arguments." msgstr "" #: c-api/init.rst:1232 @@ -1466,8 +1470,8 @@ msgstr "" #: c-api/init.rst:1235 msgid "" -"Raises an :ref:`auditing event ` ``cpython." -"PyInterpreterState_Clear`` with no arguments." +"Raises an :ref:`auditing event ` " +"``cpython.PyInterpreterState_Clear`` with no arguments." msgstr "" #: c-api/init.rst:1240 @@ -1499,16 +1503,16 @@ msgstr "" #: c-api/init.rst:1264 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`." +"held. The thread state must have been reset with a previous call " +"to :c:func:`PyThreadState_Clear`." msgstr "" #: c-api/init.rst:1271 msgid "" "Destroy the current thread state and release the global interpreter lock. " "Like :c:func:`PyThreadState_Delete`, the global interpreter lock must be " -"held. The thread state must have been reset with a previous call to :c:func:" -"`PyThreadState_Clear`." +"held. The thread state must have been reset with a previous call " +"to :c:func:`PyThreadState_Clear`." msgstr "" #: c-api/init.rst:1279 @@ -1645,8 +1649,8 @@ msgstr "" #: c-api/init.rst:1411 msgid "" -"The type of the *id* parameter changed from :c:expr:`long` to :c:expr:" -"`unsigned long`." +"The type of the *id* parameter changed from :c:expr:`long` " +"to :c:expr:`unsigned long`." msgstr "" #: c-api/init.rst:1417 @@ -1658,9 +1662,10 @@ msgstr "" #: c-api/init.rst:1466 msgid "" -"Updated to be consistent with :c:func:`PyEval_RestoreThread`, :c:func:" -"`Py_END_ALLOW_THREADS`, and :c:func:`PyGILState_Ensure`, and terminate the " -"current thread if called while the interpreter is finalizing." +"Updated to be consistent " +"with :c:func:`PyEval_RestoreThread`, :c:func:`Py_END_ALLOW_THREADS`, " +"and :c:func:`PyGILState_Ensure`, and terminate the current thread if called " +"while the interpreter is finalizing." msgstr "" #: c-api/init.rst:1433 @@ -1692,8 +1697,8 @@ msgstr "" #: c-api/init.rst:1454 msgid "" -"This function does not update the current thread state. Please use :c:func:" -"`PyEval_RestoreThread` or :c:func:`PyEval_AcquireThread` instead." +"This function does not update the current thread state. Please " +"use :c:func:`PyEval_RestoreThread` or :c:func:`PyEval_AcquireThread` instead." msgstr "" #: c-api/init.rst:1460 @@ -1713,8 +1718,8 @@ msgstr "" #: c-api/init.rst:1476 msgid "" -"This function does not update the current thread state. Please use :c:func:" -"`PyEval_SaveThread` or :c:func:`PyEval_ReleaseThread` instead." +"This function does not update the current thread state. Please " +"use :c:func:`PyEval_SaveThread` or :c:func:`PyEval_ReleaseThread` instead." msgstr "" #: c-api/init.rst:1485 @@ -1742,9 +1747,9 @@ msgstr "" #: c-api/init.rst:1499 msgid "" -"You can switch between sub-interpreters using the :c:func:" -"`PyThreadState_Swap` function. You can create and destroy them using the " -"following functions:" +"You can switch between sub-interpreters using " +"the :c:func:`PyThreadState_Swap` function. You can create and destroy them " +"using the following functions:" msgstr "" #: c-api/init.rst:1505 @@ -1766,10 +1771,10 @@ msgstr "" #: c-api/init.rst:1519 msgid "" -"If this is ``0`` then :c:member:`~PyInterpreterConfig." -"check_multi_interp_extensions` must be ``1`` (non-zero). If this is ``1`` " -"then :c:member:`~PyInterpreterConfig.gil` must not be :c:macro:" -"`PyInterpreterConfig_OWN_GIL`." +"If this is ``0`` " +"then :c:member:`~PyInterpreterConfig.check_multi_interp_extensions` must be " +"``1`` (non-zero). If this is ``1`` then :c:member:`~PyInterpreterConfig.gil` " +"must not be :c:macro:`PyInterpreterConfig_OWN_GIL`." msgstr "" #: c-api/init.rst:1527 @@ -1805,23 +1810,23 @@ msgstr "" #: c-api/init.rst:1552 msgid "" "If this is ``0`` then the sub-interpreter's :mod:`threading` module won't " -"create daemon threads. Otherwise daemon threads are allowed (as long as :c:" -"member:`~PyInterpreterConfig.allow_threads` is non-zero)." +"create daemon threads. Otherwise daemon threads are allowed (as long " +"as :c:member:`~PyInterpreterConfig.allow_threads` is non-zero)." msgstr "" #: c-api/init.rst:1559 msgid "" "If this is ``0`` then all extension modules may be imported, including " "legacy (single-phase init) modules, in any thread where the sub-interpreter " -"is currently active. Otherwise only multi-phase init extension modules (see :" -"pep:`489`) may be imported. (Also see :c:macro:" -"`Py_mod_multiple_interpreters`.)" +"is currently active. Otherwise only multi-phase init extension modules " +"(see :pep:`489`) may be imported. (Also " +"see :c:macro:`Py_mod_multiple_interpreters`.)" msgstr "" #: c-api/init.rst:1566 msgid "" -"This must be ``1`` (non-zero) if :c:member:`~PyInterpreterConfig." -"use_main_obmalloc` is ``0``." +"This must be ``1`` (non-zero) " +"if :c:member:`~PyInterpreterConfig.use_main_obmalloc` is ``0``." msgstr "" #: c-api/init.rst:1571 @@ -1844,8 +1849,8 @@ msgstr "" #: c-api/init.rst:1588 msgid "" -"If this is :c:macro:`PyInterpreterConfig_OWN_GIL` then :c:member:" -"`PyInterpreterConfig.use_main_obmalloc` must be ``0``." +"If this is :c:macro:`PyInterpreterConfig_OWN_GIL` " +"then :c:member:`PyInterpreterConfig.use_main_obmalloc` must be ``0``." msgstr "" #: c-api/init.rst:1602 @@ -1853,12 +1858,12 @@ 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)." +"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 "" #: c-api/init.rst:1612 @@ -1913,9 +1918,9 @@ msgstr "" #: c-api/init.rst:1649 msgid "" "Note that the config is used only briefly and does not get modified. During " -"initialization the config's values are converted into various :c:type:" -"`PyInterpreterState` values. A read-only copy of the config may be stored " -"internally on the :c:type:`PyInterpreterState`." +"initialization the config's values are converted into " +"various :c:type:`PyInterpreterState` values. A read-only copy of the config " +"may be stored internally on the :c:type:`PyInterpreterState`." msgstr "" #: c-api/init.rst:1658 @@ -1924,41 +1929,42 @@ msgstr "" #: c-api/init.rst:1660 msgid "" -"For modules using multi-phase initialization, e.g. :c:func:" -"`PyModule_FromDefAndSpec`, a separate module object is created and " -"initialized for each interpreter. Only C-level static and global variables " -"are shared between these module objects." +"For modules using multi-phase initialization, " +"e.g. :c:func:`PyModule_FromDefAndSpec`, a separate module object is created " +"and initialized for each interpreter. Only C-level static and global " +"variables are shared between these module objects." msgstr "" #: c-api/init.rst:1666 msgid "" -"For modules using single-phase initialization, e.g. :c:func:" -"`PyModule_Create`, 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. Objects in " -"the module's dictionary thus end up shared across (sub-)interpreters, which " -"might cause unwanted behavior (see `Bugs and caveats`_ below)." +"For modules using single-phase initialization, " +"e.g. :c:func:`PyModule_Create`, 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. " +"Objects in the module's dictionary thus end up shared across " +"(sub-)interpreters, which might cause unwanted behavior (see `Bugs and " +"caveats`_ below)." msgstr "" #: c-api/init.rst:1677 msgid "" "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. As with multi-phase " -"initialization, this means that only C-level static and global variables are " -"shared between these modules." +"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. As with multi-" +"phase initialization, this means that only C-level static and global " +"variables are shared between these modules." msgstr "" #: c-api/init.rst:1697 msgid "" -"Create a new sub-interpreter. This is essentially just a wrapper around :c:" -"func:`Py_NewInterpreterFromConfig` with a config that preserves the existing " -"behavior. The result is an unisolated sub-interpreter that shares the main " -"interpreter's GIL, allows fork/exec, allows daemon threads, and allows " -"single-phase init modules." +"Create a new sub-interpreter. This is essentially just a wrapper " +"around :c:func:`Py_NewInterpreterFromConfig` with a config that preserves " +"the existing behavior. The result is an unisolated sub-interpreter that " +"shares the main interpreter's GIL, allows fork/exec, allows daemon threads, " +"and allows single-phase init modules." msgstr "" #: c-api/init.rst:1709 @@ -2057,10 +2063,10 @@ msgid "" "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." +"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 "" #: c-api/init.rst:1790 @@ -2126,8 +2132,8 @@ msgid "" "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`." +"calling Python code from arbitrary C threads. Instead, use " +"the :ref:`PyGILState API`." msgstr "" #: c-api/init.rst:1834 @@ -2164,11 +2170,9 @@ 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 :c:data:`PyTrace_CALL`, :c:" -"data:`PyTrace_EXCEPTION`, :c:data:`PyTrace_LINE`, :c:data:`PyTrace_RETURN`, :" -"c:data:`PyTrace_C_CALL`, :c:data:`PyTrace_C_EXCEPTION`, :c:data:" -"`PyTrace_C_RETURN`, or :c:data:`PyTrace_OPCODE`, and *arg* depends on the " -"value of *what*:" +"event pertains, *what* is one of the " +"constants :c:data:`PyTrace_CALL`, :c:data:`PyTrace_EXCEPTION`, :c:data:`PyTrace_LINE`, :c:data:`PyTrace_RETURN`, :c:data:`PyTrace_C_CALL`, :c:data:`PyTrace_C_EXCEPTION`, :c:data:`PyTrace_C_RETURN`, " +"or :c:data:`PyTrace_OPCODE`, and *arg* depends on the value of *what*:" msgstr "" #: c-api/init.rst:1871 @@ -2253,8 +2257,8 @@ msgstr "" msgid "" "The value passed as the *what* parameter to a :c:type:`Py_tracefunc` " "function (but not a profiling function) when a line-number event is being " -"reported. It may be disabled for a frame by setting :attr:`~frame." -"f_trace_lines` to *0* on that frame." +"reported. It may be disabled for a frame by " +"setting :attr:`~frame.f_trace_lines` to *0* on that frame." msgstr "" #: c-api/init.rst:1922 @@ -2285,8 +2289,8 @@ msgstr "" msgid "" "The value for the *what* parameter to :c:type:`Py_tracefunc` functions (but " "not profiling functions) when a new opcode is about to be executed. This " -"event is not emitted by default: it must be explicitly requested by setting :" -"attr:`~frame.f_trace_opcodes` to *1* on the frame." +"event is not emitted by default: it must be explicitly requested by " +"setting :attr:`~frame.f_trace_opcodes` to *1* on the frame." msgstr "" #: c-api/init.rst:1954 @@ -2295,8 +2299,9 @@ msgid "" "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 :c:data:" -"`PyTrace_LINE` :c:data:`PyTrace_OPCODE` and :c:data:`PyTrace_EXCEPTION`." +"it. The profile function is called for all monitored events " +"except :c:data:`PyTrace_LINE` :c:data:`PyTrace_OPCODE` " +"and :c:data:`PyTrace_EXCEPTION`." msgstr "" #: c-api/init.rst:1961 @@ -2322,13 +2327,13 @@ msgstr "" #: c-api/init.rst:1980 msgid "" -"Set the tracing function to *func*. This is similar to :c:func:" -"`PyEval_SetProfile`, except the tracing function does receive line-number " -"events and per-opcode events, but does not receive any event related to C " -"function objects being called. Any trace function registered using :c:func:" -"`PyEval_SetTrace` will not receive :c:data:`PyTrace_C_CALL`, :c:data:" -"`PyTrace_C_EXCEPTION` or :c:data:`PyTrace_C_RETURN` as a value for the " -"*what* parameter." +"Set the tracing function to *func*. This is similar " +"to :c:func:`PyEval_SetProfile`, except the tracing function does receive " +"line-number events and per-opcode events, but does not receive any event " +"related to C function objects being called. Any trace function registered " +"using :c:func:`PyEval_SetTrace` will not " +"receive :c:data:`PyTrace_C_CALL`, :c:data:`PyTrace_C_EXCEPTION` " +"or :c:data:`PyTrace_C_RETURN` as a value for the *what* parameter." msgstr "" #: c-api/init.rst:1987 @@ -2413,10 +2418,10 @@ msgstr "" #: c-api/init.rst:2064 msgid "" -"None of these API functions handle memory management on behalf of the :c:" -"expr:`void*` values. You need to allocate and deallocate them yourself. If " -"the :c:expr:`void*` values happen to be :c:expr:`PyObject*`, these functions " -"don't do refcount operations on them either." +"None of these API functions handle memory management on behalf of " +"the :c:expr:`void*` values. You need to allocate and deallocate them " +"yourself. If the :c:expr:`void*` values happen to be :c:expr:`PyObject*`, " +"these functions don't do refcount operations on them either." msgstr "" #: c-api/init.rst:2072 @@ -2467,8 +2472,9 @@ msgstr "" #: c-api/init.rst:2110 msgid "" -"Return a value which is the same state as a value initialized with :c:macro:" -"`Py_tss_NEEDS_INIT`, or ``NULL`` in the case of dynamic allocation failure." +"Return a value which is the same state as a value initialized " +"with :c:macro:`Py_tss_NEEDS_INIT`, or ``NULL`` in the case of dynamic " +"allocation failure." msgstr "" #: c-api/init.rst:2117 @@ -2491,8 +2497,8 @@ msgstr "" msgid "" "The parameter *key* of these functions must not be ``NULL``. Moreover, the " "behaviors of :c:func:`PyThread_tss_set` and :c:func:`PyThread_tss_get` are " -"undefined if the given :c:type:`Py_tss_t` has not been initialized by :c:" -"func:`PyThread_tss_create`." +"undefined if the given :c:type:`Py_tss_t` has not been initialized " +"by :c:func:`PyThread_tss_create`." msgstr "" #: c-api/init.rst:2138 @@ -2514,9 +2520,9 @@ msgstr "" msgid "" "Destroy a TSS key to forget the values associated with the key across all " "threads, and change the key's initialization state to uninitialized. A " -"destroyed key is able to be initialized again by :c:func:" -"`PyThread_tss_create`. This function can be called repeatedly on the same " -"key -- calling it on an already destroyed key is a no-op." +"destroyed key is able to be initialized again " +"by :c:func:`PyThread_tss_create`. This function can be called repeatedly on " +"the same key -- calling it on an already destroyed key is a no-op." msgstr "" #: c-api/init.rst:2162 diff --git a/c-api/init_config.po b/c-api/init_config.po index 93c4253a6..3a7c65638 100644 --- a/c-api/init_config.po +++ b/c-api/init_config.po @@ -22,9 +22,9 @@ msgstr "" #: c-api/init_config.rst:11 msgid "" -"Python can be initialized with :c:func:`Py_InitializeFromConfig` and the :c:" -"type:`PyConfig` structure. It can be preinitialized with :c:func:" -"`Py_PreInitialize` and the :c:type:`PyPreConfig` structure." +"Python can be initialized with :c:func:`Py_InitializeFromConfig` and " +"the :c:type:`PyConfig` structure. It can be preinitialized " +"with :c:func:`Py_PreInitialize` and the :c:type:`PyPreConfig` structure." msgstr "" #: c-api/init_config.rst:15 @@ -317,8 +317,8 @@ msgstr "" #: c-api/init_config.rst:249 msgid "" -"``PYMEM_ALLOCATOR_MALLOC_DEBUG`` (``4``): force usage of ``malloc()`` with :" -"ref:`debug hooks `." +"``PYMEM_ALLOCATOR_MALLOC_DEBUG`` (``4``): force usage of ``malloc()`` " +"with :ref:`debug hooks `." msgstr "" #: c-api/init_config.rst:251 @@ -354,8 +354,8 @@ msgstr "" #: c-api/init_config.rst:269 msgid "" -"If equals to ``0``, set :c:member:`~PyPreConfig.coerce_c_locale` and :c:" -"member:`~PyPreConfig.coerce_c_locale_warn` members to ``0``." +"If equals to ``0``, set :c:member:`~PyPreConfig.coerce_c_locale` " +"and :c:member:`~PyPreConfig.coerce_c_locale_warn` members to ``0``." msgstr "" #: c-api/init_config.rst:283 @@ -438,16 +438,16 @@ msgstr "" #: c-api/init_config.rst:324 msgid "" -"If non-zero, :c:func:`Py_PreInitializeFromArgs` and :c:func:" -"`Py_PreInitializeFromBytesArgs` parse their ``argv`` argument the same way " -"the regular Python parses command line arguments: see :ref:`Command Line " -"Arguments `." +"If non-zero, :c:func:`Py_PreInitializeFromArgs` " +"and :c:func:`Py_PreInitializeFromBytesArgs` parse their ``argv`` argument " +"the same way the regular Python parses command line arguments: " +"see :ref:`Command Line Arguments `." msgstr "" #: c-api/init_config.rst:333 msgid "" -"Use :ref:`environment variables `? See :c:member:`PyConfig." -"use_environment`." +"Use :ref:`environment variables `? " +"See :c:member:`PyConfig.use_environment`." msgstr "" #: c-api/init_config.rst:1213 @@ -490,8 +490,8 @@ msgstr "" #: c-api/init_config.rst:359 msgid "" -"Set the :ref:`Python UTF-8 Mode ` (:c:member:`PyPreConfig." -"utf8_mode`)" +"Set the :ref:`Python UTF-8 Mode ` " +"(:c:member:`PyPreConfig.utf8_mode`)" msgstr "" #: c-api/init_config.rst:362 @@ -514,38 +514,38 @@ msgstr "" #: c-api/init_config.rst:377 msgid "" -"Parse *argv* command line arguments (bytes strings) if :c:member:" -"`~PyPreConfig.parse_argv` of *preconfig* is non-zero." +"Parse *argv* command line arguments (bytes strings) " +"if :c:member:`~PyPreConfig.parse_argv` of *preconfig* is non-zero." msgstr "" #: c-api/init_config.rst:386 msgid "" -"Parse *argv* command line arguments (wide strings) if :c:member:" -"`~PyPreConfig.parse_argv` of *preconfig* is non-zero." +"Parse *argv* command line arguments (wide strings) " +"if :c:member:`~PyPreConfig.parse_argv` of *preconfig* is non-zero." msgstr "" #: c-api/init_config.rst:1301 msgid "" -"The caller is responsible to handle exceptions (error or exit) using :c:func:" -"`PyStatus_Exception` and :c:func:`Py_ExitStatusException`." +"The caller is responsible to handle exceptions (error or exit) " +"using :c:func:`PyStatus_Exception` and :c:func:`Py_ExitStatusException`." msgstr "" #: c-api/init_config.rst:394 msgid "" -"For :ref:`Python Configuration ` (:c:func:" -"`PyPreConfig_InitPythonConfig`), if Python is initialized with command line " -"arguments, the command line arguments must also be passed to preinitialize " -"Python, since they have an effect on the pre-configuration like encodings. " -"For example, the :option:`-X utf8 <-X>` command line option enables the :ref:" -"`Python UTF-8 Mode `." +"For :ref:`Python Configuration ` " +"(:c:func:`PyPreConfig_InitPythonConfig`), if Python is initialized with " +"command line arguments, the command line arguments must also be passed to " +"preinitialize Python, since they have an effect on the pre-configuration " +"like encodings. For example, the :option:`-X utf8 <-X>` command line option " +"enables the :ref:`Python UTF-8 Mode `." msgstr "" #: c-api/init_config.rst:401 msgid "" "``PyMem_SetAllocator()`` can be called after :c:func:`Py_PreInitialize` and " "before :c:func:`Py_InitializeFromConfig` to install a custom memory " -"allocator. It can be called before :c:func:`Py_PreInitialize` if :c:member:" -"`PyPreConfig.allocator` is set to ``PYMEM_ALLOCATOR_NOT_SET``." +"allocator. It can be called before :c:func:`Py_PreInitialize` " +"if :c:member:`PyPreConfig.allocator` is set to ``PYMEM_ALLOCATOR_NOT_SET``." msgstr "" #: c-api/init_config.rst:406 @@ -636,8 +636,8 @@ msgstr "" #: c-api/init_config.rst:478 msgid "" "Set command line arguments (:c:member:`~PyConfig.argv` member of *config*) " -"from the *argv* list of bytes strings. Decode bytes using :c:func:" -"`Py_DecodeLocale`." +"from the *argv* list of bytes strings. Decode bytes " +"using :c:func:`Py_DecodeLocale`." msgstr "" #: c-api/init_config.rst:486 @@ -662,16 +662,17 @@ msgstr "" msgid "" "The :c:func:`PyConfig_Read` function only parses :c:member:`PyConfig.argv` " "arguments once: :c:member:`PyConfig.parse_argv` is set to ``2`` after " -"arguments are parsed. Since Python arguments are stripped from :c:member:" -"`PyConfig.argv`, parsing arguments twice would parse the application options " -"as Python options." +"arguments are parsed. Since Python arguments are stripped " +"from :c:member:`PyConfig.argv`, parsing arguments twice would parse the " +"application options as Python options." msgstr "" #: c-api/init_config.rst:507 msgid "" -"The :c:member:`PyConfig.argv` arguments are now only parsed once, :c:member:" -"`PyConfig.parse_argv` is set to ``2`` after arguments are parsed, and " -"arguments are only parsed if :c:member:`PyConfig.parse_argv` equals ``1``." +"The :c:member:`PyConfig.argv` arguments are now only parsed " +"once, :c:member:`PyConfig.parse_argv` is set to ``2`` after arguments are " +"parsed, and arguments are only parsed if :c:member:`PyConfig.parse_argv` " +"equals ``1``." msgstr "" #: c-api/init_config.rst:513 @@ -688,10 +689,10 @@ msgstr "" #: c-api/init_config.rst:523 msgid "" "Most ``PyConfig`` methods :ref:`preinitialize Python ` if needed. " -"In that case, the Python preinitialization configuration (:c:type:" -"`PyPreConfig`) in based on the :c:type:`PyConfig`. If configuration fields " -"which are in common with :c:type:`PyPreConfig` are tuned, they must be set " -"before calling a :c:type:`PyConfig` method:" +"In that case, the Python preinitialization configuration " +"(:c:type:`PyPreConfig`) in based on the :c:type:`PyConfig`. If configuration " +"fields which are in common with :c:type:`PyPreConfig` are tuned, they must " +"be set before calling a :c:type:`PyConfig` method:" msgstr "" #: c-api/init_config.rst:529 @@ -714,8 +715,8 @@ msgstr "" msgid "" "Moreover, if :c:func:`PyConfig_SetArgv` or :c:func:`PyConfig_SetBytesArgv` " "is used, this method must be called before other methods, since the " -"preinitialization configuration depends on command line arguments (if :c:" -"member:`~PyConfig.parse_argv` is non-zero)." +"preinitialization configuration depends on command line arguments " +"(if :c:member:`~PyConfig.parse_argv` is non-zero)." msgstr "" #: c-api/init_config.rst:539 @@ -730,9 +731,10 @@ msgstr "" #: c-api/init_config.rst:550 msgid "" -"Set :c:member:`~PyConfig.parse_argv` to ``1`` to parse :c:member:`~PyConfig." -"argv` the same way the regular Python parses Python command line arguments " -"and then to strip Python arguments from :c:member:`~PyConfig.argv`." +"Set :c:member:`~PyConfig.parse_argv` to ``1`` to " +"parse :c:member:`~PyConfig.argv` the same way the regular Python parses " +"Python command line arguments and then to strip Python arguments " +"from :c:member:`~PyConfig.argv`." msgstr "" #: c-api/init_config.rst:555 @@ -754,8 +756,8 @@ msgstr "" #: c-api/init_config.rst:564 msgid "" -"If equals to zero, ``Py_RunMain()`` prepends a potentially unsafe path to :" -"data:`sys.path` at startup:" +"If equals to zero, ``Py_RunMain()`` prepends a potentially unsafe path " +"to :data:`sys.path` at startup:" msgstr "" #: c-api/init_config.rst:567 @@ -778,8 +780,8 @@ msgstr "" #: c-api/init_config.rst:574 msgid "" -"Set to ``1`` by the :option:`-P` command line option and the :envvar:" -"`PYTHONSAFEPATH` environment variable." +"Set to ``1`` by the :option:`-P` command line option and " +"the :envvar:`PYTHONSAFEPATH` environment variable." msgstr "" #: c-api/init_config.rst:577 @@ -819,8 +821,8 @@ msgstr "" #: c-api/init_config.rst:614 msgid "" -"Set to ``0`` by the :option:`-u` command line option and the :envvar:" -"`PYTHONUNBUFFERED` environment variable." +"Set to ``0`` by the :option:`-u` command line option and " +"the :envvar:`PYTHONUNBUFFERED` environment variable." msgstr "" #: c-api/init_config.rst:617 @@ -833,8 +835,9 @@ msgstr "" #: c-api/init_config.rst:623 msgid "" -"If equals to ``1``, issue a warning when comparing :class:`bytes` or :class:" -"`bytearray` with :class:`str`, or comparing :class:`bytes` with :class:`int`." +"If equals to ``1``, issue a warning when comparing :class:`bytes` " +"or :class:`bytearray` with :class:`str`, or comparing :class:`bytes` " +"with :class:`int`." msgstr "" #: c-api/init_config.rst:627 @@ -849,9 +852,9 @@ msgstr "" #: c-api/init_config.rst:636 msgid "" -"If non-zero, emit a :exc:`EncodingWarning` warning when :class:`io." -"TextIOWrapper` uses its default encoding. See :ref:`io-encoding-warning` for " -"details." +"If non-zero, emit a :exc:`EncodingWarning` warning " +"when :class:`io.TextIOWrapper` uses its default encoding. See :ref:`io-" +"encoding-warning` for details." msgstr "" #: c-api/init_config.rst:645 @@ -869,8 +872,8 @@ msgstr "" #: c-api/init_config.rst:658 msgid "" -"Control the validation behavior of hash-based ``.pyc`` files: value of the :" -"option:`--check-hash-based-pycs` command line option." +"Control the validation behavior of hash-based ``.pyc`` files: value of " +"the :option:`--check-hash-based-pycs` command line option." msgstr "" #: c-api/init_config.rst:661 @@ -928,8 +931,8 @@ msgstr "" #: c-api/init_config.rst:690 msgid "" -"Set to ``1`` by the :option:`-X dev <-X>` option and the :envvar:" -"`PYTHONDEVMODE` environment variable." +"Set to ``1`` by the :option:`-X dev <-X>` option and " +"the :envvar:`PYTHONDEVMODE` environment variable." msgstr "" #: c-api/init_config.rst:697 @@ -958,8 +961,8 @@ msgstr "" #: c-api/init_config.rst:719 msgid "" -"The absolute path of the executable binary for the Python interpreter: :data:" -"`sys.executable`." +"The absolute path of the executable binary for the Python " +"interpreter: :data:`sys.executable`." msgstr "" #: c-api/init_config.rst:728 @@ -972,14 +975,14 @@ msgstr "" #: c-api/init_config.rst:732 msgid "" -"Set to ``1`` by :option:`-X faulthandler <-X>` and the :envvar:" -"`PYTHONFAULTHANDLER` environment variable." +"Set to ``1`` by :option:`-X faulthandler <-X>` and " +"the :envvar:`PYTHONFAULTHANDLER` environment variable." msgstr "" #: c-api/init_config.rst:739 msgid "" -":term:`Filesystem encoding `: :func:" -"`sys.getfilesystemencoding`." +":term:`Filesystem encoding `: :func:`sys.getfilesystemencoding`." msgstr "" #: c-api/init_config.rst:742 @@ -988,9 +991,9 @@ msgstr "" #: c-api/init_config.rst:744 msgid "" -"On Windows: use ``\"utf-8\"`` by default, or ``\"mbcs\"`` if :c:member:" -"`~PyPreConfig.legacy_windows_fs_encoding` of :c:type:`PyPreConfig` is non-" -"zero." +"On Windows: use ``\"utf-8\"`` by default, or ``\"mbcs\"`` " +"if :c:member:`~PyPreConfig.legacy_windows_fs_encoding` " +"of :c:type:`PyPreConfig` is non-zero." msgstr "" #: c-api/init_config.rst:748 @@ -1029,15 +1032,15 @@ msgstr "" #: c-api/init_config.rst:765 msgid "" -":term:`Filesystem error handler `: :" -"func:`sys.getfilesystemencodeerrors`." +":term:`Filesystem error handler `: :func:`sys.getfilesystemencodeerrors`." msgstr "" #: c-api/init_config.rst:768 msgid "" -"On Windows: use ``\"surrogatepass\"`` by default, or ``\"replace\"`` if :c:" -"member:`~PyPreConfig.legacy_windows_fs_encoding` of :c:type:`PyPreConfig` is " -"non-zero." +"On Windows: use ``\"surrogatepass\"`` by default, or ``\"replace\"`` " +"if :c:member:`~PyPreConfig.legacy_windows_fs_encoding` " +"of :c:type:`PyPreConfig` is non-zero." msgstr "" #: c-api/init_config.rst:772 @@ -1108,8 +1111,8 @@ msgstr "" #: c-api/init_config.rst:812 msgid "" -"Set the ``1`` by the :option:`-X importtime <-X>` option and the :envvar:" -"`PYTHONPROFILEIMPORTTIME` environment variable." +"Set the ``1`` by the :option:`-X importtime <-X>` option and " +"the :envvar:`PYTHONPROFILEIMPORTTIME` environment variable." msgstr "" #: c-api/init_config.rst:819 @@ -1126,8 +1129,8 @@ msgstr "" #: c-api/init_config.rst:826 msgid "" -"Incremented by the :option:`-i` command line option. Set to ``1`` if the :" -"envvar:`PYTHONINSPECT` environment variable is non-empty." +"Incremented by the :option:`-i` command line option. Set to ``1`` if " +"the :envvar:`PYTHONINSPECT` environment variable is non-empty." msgstr "" #: c-api/init_config.rst:833 @@ -1150,10 +1153,11 @@ msgstr "" msgid "" "Configures the :ref:`integer string conversion length limitation " "`. An initial value of ``-1`` means the value will be " -"taken from the command line or environment or otherwise default to 4300 (:" -"data:`sys.int_info.default_max_str_digits`). A value of ``0`` disables the " -"limitation. Values greater than zero but less than 640 (:data:`sys.int_info." -"str_digits_check_threshold`) are unsupported and will produce an error." +"taken from the command line or environment or otherwise default to 4300 " +"(:data:`sys.int_info.default_max_str_digits`). A value of ``0`` disables " +"the limitation. Values greater than zero but less than 640 " +"(:data:`sys.int_info.str_digits_check_threshold`) are unsupported and will " +"produce an error." msgstr "" #: c-api/init_config.rst:855 @@ -1164,8 +1168,8 @@ msgstr "" #: c-api/init_config.rst:858 msgid "" -"Default: ``-1`` in Python mode. 4300 (:data:`sys.int_info." -"default_max_str_digits`) in isolated mode." +"Default: ``-1`` in Python mode. 4300 " +"(:data:`sys.int_info.default_max_str_digits`) in isolated mode." msgstr "" #: c-api/init_config.rst:865 @@ -1203,15 +1207,15 @@ msgstr "" #: c-api/init_config.rst:882 msgid "" -"See also the :ref:`Isolated Configuration ` and :c:" -"member:`PyPreConfig.isolated`." +"See also the :ref:`Isolated Configuration ` " +"and :c:member:`PyPreConfig.isolated`." msgstr "" #: c-api/init_config.rst:887 msgid "" -"If non-zero, use :class:`io.FileIO` instead of :class:`!io." -"_WindowsConsoleIO` for :data:`sys.stdin`, :data:`sys.stdout` and :data:`sys." -"stderr`." +"If non-zero, use :class:`io.FileIO` instead of :class:`!" +"io._WindowsConsoleIO` for :data:`sys.stdin`, :data:`sys.stdout` " +"and :data:`sys.stderr`." msgstr "" #: c-api/init_config.rst:891 @@ -1250,9 +1254,9 @@ msgstr "" #: c-api/init_config.rst:919 msgid "" -"Default: value of the ``PLATLIBDIR`` macro which is set by the :option:" -"`configure --with-platlibdir option <--with-platlibdir>` (default: " -"``\"lib\"``, or ``\"DLLs\"`` on Windows)." +"Default: value of the ``PLATLIBDIR`` macro which is set by " +"the :option:`configure --with-platlibdir option <--with-platlibdir>` " +"(default: ``\"lib\"``, or ``\"DLLs\"`` on Windows)." msgstr "" #: c-api/init_config.rst:927 @@ -1265,8 +1269,8 @@ msgstr "" #: c-api/init_config.rst:936 msgid "" -"Module search paths (:data:`sys.path`) as a string separated by ``DELIM`` (:" -"data:`os.pathsep`)." +"Module search paths (:data:`sys.path`) as a string separated by ``DELIM`` " +"(:data:`os.pathsep`)." msgstr "" #: c-api/init_config.rst:939 @@ -1279,10 +1283,10 @@ msgstr "" #: c-api/init_config.rst:950 msgid "" -"If :c:member:`~PyConfig.module_search_paths_set` is equal to ``0``, :c:func:" -"`Py_InitializeFromConfig` will replace :c:member:`~PyConfig." -"module_search_paths` and sets :c:member:`~PyConfig.module_search_paths_set` " -"to ``1``." +"If :c:member:`~PyConfig.module_search_paths_set` is equal to " +"``0``, :c:func:`Py_InitializeFromConfig` will " +"replace :c:member:`~PyConfig.module_search_paths` and " +"sets :c:member:`~PyConfig.module_search_paths_set` to ``1``." msgstr "" #: c-api/init_config.rst:955 @@ -1309,8 +1313,8 @@ msgstr "" #: c-api/init_config.rst:968 msgid "" -"Incremented by the :option:`-O` command line option. Set to the :envvar:" -"`PYTHONOPTIMIZE` environment variable value." +"Incremented by the :option:`-O` command line option. Set to " +"the :envvar:`PYTHONOPTIMIZE` environment variable value." msgstr "" #: c-api/init_config.rst:975 @@ -1321,17 +1325,18 @@ msgstr "" #: c-api/init_config.rst:978 msgid "" -"If :c:member:`~PyConfig.orig_argv` list is empty and :c:member:`~PyConfig." -"argv` is not a list only containing an empty string, :c:func:`PyConfig_Read` " -"copies :c:member:`~PyConfig.argv` into :c:member:`~PyConfig.orig_argv` " -"before modifying :c:member:`~PyConfig.argv` (if :c:member:`~PyConfig." -"parse_argv` is non-zero)." +"If :c:member:`~PyConfig.orig_argv` list is empty " +"and :c:member:`~PyConfig.argv` is not a list only containing an empty " +"string, :c:func:`PyConfig_Read` copies :c:member:`~PyConfig.argv` " +"into :c:member:`~PyConfig.orig_argv` before " +"modifying :c:member:`~PyConfig.argv` (if :c:member:`~PyConfig.parse_argv` is " +"non-zero)." msgstr "" #: c-api/init_config.rst:985 msgid "" -"See also the :c:member:`~PyConfig.argv` member and the :c:func:" -"`Py_GetArgcArgv` function." +"See also the :c:member:`~PyConfig.argv` member and " +"the :c:func:`Py_GetArgcArgv` function." msgstr "" #: c-api/init_config.rst:1258 c-api/init_config.rst:1277 @@ -1351,8 +1356,8 @@ msgstr "" #: c-api/init_config.rst:1008 msgid "" -"The :c:member:`PyConfig.argv` arguments are now only parsed if :c:member:" -"`PyConfig.parse_argv` equals to ``1``." +"The :c:member:`PyConfig.argv` arguments are now only parsed " +"if :c:member:`PyConfig.parse_argv` equals to ``1``." msgstr "" #: c-api/init_config.rst:1014 @@ -1363,8 +1368,8 @@ msgstr "" #: c-api/init_config.rst:1017 msgid "" -"Incremented by the :option:`-d` command line option. Set to the :envvar:" -"`PYTHONDEBUG` environment variable value." +"Incremented by the :option:`-d` command line option. Set to " +"the :envvar:`PYTHONDEBUG` environment variable value." msgstr "" #: c-api/init_config.rst:1020 @@ -1405,8 +1410,8 @@ msgstr "" #: c-api/init_config.rst:1053 msgid "" -"If the ``WITH_NEXT_FRAMEWORK`` macro is defined, use :envvar:" -"`__PYVENV_LAUNCHER__` environment variable if set." +"If the ``WITH_NEXT_FRAMEWORK`` macro is defined, " +"use :envvar:`__PYVENV_LAUNCHER__` environment variable if set." msgstr "" #: c-api/init_config.rst:1055 @@ -1422,8 +1427,8 @@ msgstr "" #: c-api/init_config.rst:1066 msgid "" -"Directory where cached ``.pyc`` files are written: :data:`sys." -"pycache_prefix`." +"Directory where cached ``.pyc`` files are " +"written: :data:`sys.pycache_prefix`." msgstr "" #: c-api/init_config.rst:1069 @@ -1456,8 +1461,9 @@ msgstr "" #: c-api/init_config.rst:1095 msgid "" -"Filename passed on the command line: trailing command line argument without :" -"option:`-c` or :option:`-m`. It is used by the :c:func:`Py_RunMain` function." +"Filename passed on the command line: trailing command line argument " +"without :option:`-c` or :option:`-m`. It is used by the :c:func:`Py_RunMain` " +"function." msgstr "" #: c-api/init_config.rst:1099 @@ -1510,8 +1516,8 @@ msgstr "" #: c-api/init_config.rst:1137 msgid "" -":data:`sys.flags.no_site ` is set to the inverted value of :c:" -"member:`~PyConfig.site_import`." +":data:`sys.flags.no_site ` is set to the inverted value " +"of :c:member:`~PyConfig.site_import`." msgstr "" #: c-api/init_config.rst:1144 @@ -1532,8 +1538,8 @@ msgstr "" #: c-api/init_config.rst:1157 msgid "" -"Encoding and encoding errors of :data:`sys.stdin`, :data:`sys.stdout` and :" -"data:`sys.stderr` (but :data:`sys.stderr` always uses " +"Encoding and encoding errors of :data:`sys.stdin`, :data:`sys.stdout` " +"and :data:`sys.stderr` (but :data:`sys.stderr` always uses " "``\"backslashreplace\"`` error handler)." msgstr "" @@ -1588,8 +1594,8 @@ msgstr "" #: c-api/init_config.rst:1185 msgid "" -"Set by :option:`-X tracemalloc=N <-X>` command line option and by the :" -"envvar:`PYTHONTRACEMALLOC` environment variable." +"Set by :option:`-X tracemalloc=N <-X>` command line option and by " +"the :envvar:`PYTHONTRACEMALLOC` environment variable." msgstr "" #: c-api/init_config.rst:1192 @@ -1604,8 +1610,8 @@ msgstr "" #: c-api/init_config.rst:1197 msgid "" -"Set by :option:`-X perf <-X>` command line option and by the :envvar:" -"`PYTHONPERFSUPPORT` environment variable." +"Set by :option:`-X perf <-X>` command line option and by " +"the :envvar:`PYTHONPERFSUPPORT` environment variable." msgstr "" #: c-api/init_config.rst:1200 @@ -1675,15 +1681,15 @@ msgstr "" #: c-api/init_config.rst:1251 msgid "" -"The :option:`-W` command line options adds its value to :c:member:`~PyConfig." -"warnoptions`, it can be used multiple times." +"The :option:`-W` command line options adds its value " +"to :c:member:`~PyConfig.warnoptions`, it can be used multiple times." msgstr "" #: c-api/init_config.rst:1254 msgid "" "The :envvar:`PYTHONWARNINGS` environment variable can also be used to add " -"warning options. Multiple options can be specified, separated by commas (``," -"``)." +"warning options. Multiple options can be specified, separated by commas " +"(``,``)." msgstr "" #: c-api/init_config.rst:1262 @@ -1694,14 +1700,14 @@ msgstr "" #: c-api/init_config.rst:1265 msgid "" -"Set to ``0`` by the :option:`-B` command line option and the :envvar:" -"`PYTHONDONTWRITEBYTECODE` environment variable." +"Set to ``0`` by the :option:`-B` command line option and " +"the :envvar:`PYTHONDONTWRITEBYTECODE` environment variable." msgstr "" #: c-api/init_config.rst:1268 msgid "" -":data:`sys.dont_write_bytecode` is initialized to the inverted value of :c:" -"member:`~PyConfig.write_bytecode`." +":data:`sys.dont_write_bytecode` is initialized to the inverted value " +"of :c:member:`~PyConfig.write_bytecode`." msgstr "" #: c-api/init_config.rst:1275 @@ -1712,8 +1718,8 @@ msgstr "" msgid "" "If :c:member:`~PyConfig.parse_argv` is non-zero, :c:member:`~PyConfig.argv` " "arguments are parsed the same way the regular Python parses :ref:`command " -"line arguments `, and Python arguments are stripped from :" -"c:member:`~PyConfig.argv`." +"line arguments `, and Python arguments are stripped " +"from :c:member:`~PyConfig.argv`." msgstr "" #: c-api/init_config.rst:1284 @@ -1740,11 +1746,12 @@ msgstr "" #: c-api/init_config.rst:1304 msgid "" -"If :c:func:`PyImport_FrozenModules`, :c:func:`PyImport_AppendInittab` or :c:" -"func:`PyImport_ExtendInittab` are used, they must be set or called after " -"Python preinitialization and before the Python initialization. If Python is " -"initialized multiple times, :c:func:`PyImport_AppendInittab` or :c:func:" -"`PyImport_ExtendInittab` must be called before each Python initialization." +"If :c:func:`PyImport_FrozenModules`, :c:func:`PyImport_AppendInittab` " +"or :c:func:`PyImport_ExtendInittab` are used, they must be set or called " +"after Python preinitialization and before the Python initialization. If " +"Python is initialized multiple times, :c:func:`PyImport_AppendInittab` " +"or :c:func:`PyImport_ExtendInittab` must be called before each Python " +"initialization." msgstr "" #: c-api/init_config.rst:1311 @@ -1856,9 +1863,10 @@ msgstr "" #: c-api/init_config.rst:1407 msgid "" -":c:func:`PyPreConfig_InitIsolatedConfig` and :c:func:" -"`PyConfig_InitIsolatedConfig` functions create a configuration to isolate " -"Python from the system. For example, to embed Python into an application." +":c:func:`PyPreConfig_InitIsolatedConfig` " +"and :c:func:`PyConfig_InitIsolatedConfig` functions create a configuration " +"to isolate Python from the system. For example, to embed Python into an " +"application." msgstr "" #: c-api/init_config.rst:1412 @@ -1882,9 +1890,9 @@ msgstr "" #: c-api/init_config.rst:1427 msgid "" -":c:func:`PyPreConfig_InitPythonConfig` and :c:func:" -"`PyConfig_InitPythonConfig` functions create a configuration to build a " -"customized Python which behaves as the regular Python." +":c:func:`PyPreConfig_InitPythonConfig` " +"and :c:func:`PyConfig_InitPythonConfig` functions create a configuration to " +"build a customized Python which behaves as the regular Python." msgstr "" #: c-api/init_config.rst:1431 @@ -1896,8 +1904,9 @@ msgstr "" #: c-api/init_config.rst:1434 msgid "" "This function enables C locale coercion (:pep:`538`) and :ref:`Python UTF-8 " -"Mode ` (:pep:`540`) depending on the LC_CTYPE locale, :envvar:" -"`PYTHONUTF8` and :envvar:`PYTHONCOERCECLOCALE` environment variables." +"Mode ` (:pep:`540`) depending on the LC_CTYPE " +"locale, :envvar:`PYTHONUTF8` and :envvar:`PYTHONCOERCECLOCALE` environment " +"variables." msgstr "" #: c-api/init_config.rst:1443 @@ -1938,8 +1947,8 @@ msgstr "" #: c-api/init_config.rst:1455 msgid "" -"``PATH`` environment variable to get the program full path (from :c:member:" -"`PyConfig.program_name`)" +"``PATH`` environment variable to get the program full path " +"(from :c:member:`PyConfig.program_name`)" msgstr "" #: c-api/init_config.rst:1457 @@ -1978,9 +1987,7 @@ msgid ":c:member:`PyConfig.executable`" msgstr "" #: c-api/init_config.rst:1469 -msgid "" -":c:member:`PyConfig.module_search_paths_set`, :c:member:`PyConfig." -"module_search_paths`" +msgid ":c:member:`PyConfig.module_search_paths_set`, :c:member:`PyConfig.module_search_paths`" msgstr "" #: c-api/init_config.rst:1471 @@ -1990,10 +1997,10 @@ msgstr "" #: c-api/init_config.rst:1473 msgid "" "If at least one \"output field\" is not set, Python calculates the path " -"configuration to fill unset fields. If :c:member:`~PyConfig." -"module_search_paths_set` is equal to ``0``, :c:member:`~PyConfig." -"module_search_paths` is overridden and :c:member:`~PyConfig." -"module_search_paths_set` is set to ``1``." +"configuration to fill unset fields. " +"If :c:member:`~PyConfig.module_search_paths_set` is equal to " +"``0``, :c:member:`~PyConfig.module_search_paths` is overridden " +"and :c:member:`~PyConfig.module_search_paths_set` is set to ``1``." msgstr "" #: c-api/init_config.rst:1479 @@ -2015,9 +2022,10 @@ msgstr "" #: c-api/init_config.rst:1489 msgid "" -"If :c:member:`~PyConfig.base_prefix` or :c:member:`~PyConfig." -"base_exec_prefix` fields are not set, they inherit their value from :c:" -"member:`~PyConfig.prefix` and :c:member:`~PyConfig.exec_prefix` respectively." +"If :c:member:`~PyConfig.base_prefix` " +"or :c:member:`~PyConfig.base_exec_prefix` fields are not set, they inherit " +"their value from :c:member:`~PyConfig.prefix` " +"and :c:member:`~PyConfig.exec_prefix` respectively." msgstr "" #: c-api/init_config.rst:1493 @@ -2027,8 +2035,8 @@ msgstr "" #: c-api/init_config.rst:1495 msgid "" "If :c:member:`~PyConfig.run_filename` is set and is a directory which " -"contains a ``__main__.py`` script, prepend :c:member:`~PyConfig." -"run_filename` to :data:`sys.path`." +"contains a ``__main__.py`` script, " +"prepend :c:member:`~PyConfig.run_filename` to :data:`sys.path`." msgstr "" #: c-api/init_config.rst:1498 @@ -2054,10 +2062,10 @@ msgstr "" #: c-api/init_config.rst:1506 msgid "" "If :c:member:`~PyConfig.site_import` is non-zero, :data:`sys.path` can be " -"modified by the :mod:`site` module. If :c:member:`~PyConfig." -"user_site_directory` is non-zero and the user's site-package directory " -"exists, the :mod:`site` module appends the user's site-package directory to :" -"data:`sys.path`." +"modified by the :mod:`site` module. " +"If :c:member:`~PyConfig.user_site_directory` is non-zero and the user's site-" +"package directory exists, the :mod:`site` module appends the user's site-" +"package directory to :data:`sys.path`." msgstr "" #: c-api/init_config.rst:1512 @@ -2098,8 +2106,8 @@ msgstr "" #: c-api/init_config.rst:1525 msgid "" -"The ``__PYVENV_LAUNCHER__`` environment variable is used to set :c:member:" -"`PyConfig.base_executable`" +"The ``__PYVENV_LAUNCHER__`` environment variable is used to " +"set :c:member:`PyConfig.base_executable`" msgstr "" #: c-api/init_config.rst:1530 @@ -2108,9 +2116,10 @@ msgstr "" #: c-api/init_config.rst:1534 msgid "" -"Execute the command (:c:member:`PyConfig.run_command`), the script (:c:" -"member:`PyConfig.run_filename`) or the module (:c:member:`PyConfig." -"run_module`) specified on the command line or in the configuration." +"Execute the command (:c:member:`PyConfig.run_command`), the script " +"(:c:member:`PyConfig.run_filename`) or the module " +"(:c:member:`PyConfig.run_module`) specified on the command line or in the " +"configuration." msgstr "" #: c-api/init_config.rst:1539 @@ -2191,8 +2200,8 @@ msgstr "" #: c-api/init_config.rst:1578 msgid "" -"Finish :mod:`sys` module initialization (ex: create :data:`sys.stdout` and :" -"data:`sys.path`);" +"Finish :mod:`sys` module initialization (ex: create :data:`sys.stdout` " +"and :data:`sys.path`);" msgstr "" #: c-api/init_config.rst:1580 @@ -2214,8 +2223,9 @@ msgstr "" #: c-api/init_config.rst:1586 msgid "" -":c:member:`PyConfig._init_main`: if set to ``0``, :c:func:" -"`Py_InitializeFromConfig` stops at the \"Core\" initialization phase." +":c:member:`PyConfig._init_main`: if set to " +"``0``, :c:func:`Py_InitializeFromConfig` stops at the \"Core\" " +"initialization phase." msgstr "" #: c-api/init_config.rst:1591 diff --git a/c-api/intro.po b/c-api/intro.po index d5c449e39..09e2107a3 100644 --- a/c-api/intro.po +++ b/c-api/intro.po @@ -29,8 +29,8 @@ msgid "" "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." +"larger application; this technique is generally referred to " +"as :dfn:`embedding` Python in an application." msgstr "" #: c-api/intro.rst:20 @@ -83,8 +83,8 @@ msgstr "" #: c-api/intro.rst:54 msgid "" "This implies inclusion of the following standard headers: ````, " -"````, ````, ````, ```` and ```` (if available)." +"````, ````, ````, ```` and " +"```` (if available)." msgstr "" #: c-api/intro.rst:60 @@ -120,13 +120,13 @@ msgstr "" #: c-api/intro.rst:79 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 :option:`prefix <--prefix>` " -"and :option:`exec_prefix <--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 ``prefix`` is the installation directory " -"specified to the installer." +"located in the directories :file:`{prefix}/include/pythonversion/` " +"and :file:`{exec_prefix}/include/pythonversion/`, where :option:`prefix <--" +"prefix>` and :option:`exec_prefix <--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 ``prefix`` is the " +"installation directory specified to the installer." msgstr "" #: c-api/intro.rst:88 @@ -134,9 +134,9 @@ 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 :" -"option:`prefix <--prefix>` include the platform specific headers from :" -"option:`exec_prefix <--exec-prefix>`." +"break on multi-platform builds since the platform independent headers " +"under :option:`prefix <--prefix>` include the platform specific headers " +"from :option:`exec_prefix <--exec-prefix>`." msgstr "" #: c-api/intro.rst:95 @@ -214,9 +214,9 @@ msgstr "" #: c-api/intro.rst:151 msgid "" -"If Python is :ref:`built in debug mode ` (if the :c:macro:" -"`Py_DEBUG` macro is defined), the :c:macro:`Py_ALWAYS_INLINE` macro does " -"nothing." +"If Python is :ref:`built in debug mode ` (if " +"the :c:macro:`Py_DEBUG` macro is defined), the :c:macro:`Py_ALWAYS_INLINE` " +"macro does nothing." msgstr "" #: c-api/intro.rst:154 @@ -272,8 +272,8 @@ msgstr "" #: c-api/intro.rst:202 msgid "" "Disable inlining on a function. For example, it reduces the C stack " -"consumption: useful on LTO+PGO builds which heavily inline code (see :issue:" -"`33720`)." +"consumption: useful on LTO+PGO builds which heavily inline code " +"(see :issue:`33720`)." msgstr "" #: c-api/intro.rst:206 @@ -381,20 +381,20 @@ msgid "" "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:expr:`PyObject*` can " -"be declared. The sole exception are the type objects; since these must " +"live on the heap: you never declare an automatic or static variable of " +"type :c:type:`PyObject`, only pointer variables of type :c:expr:`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 "" #: c-api/intro.rst:301 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, " +"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 "" @@ -423,18 +423,18 @@ msgid "" "Reference counts are always manipulated explicitly. The normal way is to " "use the macro :c:func:`Py_INCREF` to take a new reference to an object (i.e. " "increment its reference count by one), and :c:func:`Py_DECREF` to release " -"that reference (i.e. decrement the reference count 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 releasing references 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." +"that reference (i.e. decrement the reference count 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 releasing references 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 "" #: c-api/intro.rst:347 @@ -462,8 +462,8 @@ msgid "" "conceivably remove the object from the list, releasing that reference, and " "possibly 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." +"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 "" #: c-api/intro.rst:371 @@ -488,13 +488,13 @@ msgid "" "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 releasing 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 :term:" -"`borrowed reference`." +"reference then becomes responsible for eventually releasing 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 :term:`borrowed reference`." msgstr "" #: c-api/intro.rst:397 @@ -508,14 +508,14 @@ msgstr "" #: c-api/intro.rst:407 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)::" +"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 "" #: c-api/intro.rst:415 @@ -540,23 +540,24 @@ msgstr "" 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." +"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 "" #: c-api/intro.rst:432 msgid "" -"Equivalent code for populating a list can be written using :c:func:" -"`PyList_New` and :c:func:`PyList_SetItem`." +"Equivalent code for populating a list can be written " +"using :c:func:`PyList_New` and :c:func:`PyList_SetItem`." msgstr "" #: c-api/intro.rst:435 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)::" +"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 "" #: c-api/intro.rst:441 @@ -696,12 +697,12 @@ msgstr "" #: c-api/intro.rst:563 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:expr:`int`, :c:expr:`long`, :c:expr:" -"`double` and :c:expr:`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." +"API; most are simple C types such " +"as :c:expr:`int`, :c:expr:`long`, :c:expr:`double` and :c:expr:`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 "" #: c-api/intro.rst:573 @@ -744,40 +745,40 @@ msgstr "" 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." +"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 "" #: c-api/intro.rst:617 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." +"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 "" #: c-api/intro.rst:629 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." +"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 "" #: c-api/intro.rst:640 @@ -863,14 +864,14 @@ msgstr "" #: c-api/intro.rst:716 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." +"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 "" #: c-api/intro.rst:730 @@ -895,10 +896,11 @@ msgstr "" #: c-api/intro.rst:750 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, setting :c:member:`PyConfig.argv` and :c:member:`PyConfig.parse_argv` " -"must be set: see :ref:`Python Initialization Configuration `." +":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, setting :c:member:`PyConfig.argv` " +"and :c:member:`PyConfig.parse_argv` must be set: see :ref:`Python " +"Initialization Configuration `." msgstr "" #: c-api/intro.rst:755 @@ -918,8 +920,8 @@ 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 " +"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 "" @@ -930,23 +932,24 @@ msgid "" "``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`)." +"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 "" #: c-api/intro.rst:789 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." +"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 "" #: c-api/intro.rst:803 @@ -962,11 +965,11 @@ msgstr "" #: c-api/intro.rst:809 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 " +"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 "" @@ -974,11 +977,11 @@ msgstr "" msgid "" "Compiling the interpreter with the :c:macro:`!Py_DEBUG` macro defined " "produces what is generally meant by :ref:`a debug build of Python `. :c:macro:`!Py_DEBUG` is enabled in the Unix build by adding :option:" -"`--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." +"build>`. :c:macro:`!Py_DEBUG` is enabled in the Unix build by " +"adding :option:`--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 "" #: c-api/intro.rst:825 @@ -989,12 +992,12 @@ msgstr "" #: c-api/intro.rst:828 msgid "" -"Defining :c:macro:`Py_TRACE_REFS` enables reference tracing (see the :option:" -"`configure --with-trace-refs option <--with-trace-refs>`). 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.)" +"Defining :c:macro:`Py_TRACE_REFS` enables reference tracing (see " +"the :option:`configure --with-trace-refs option <--with-trace-refs>`). 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.)" msgstr "" #: c-api/intro.rst:835 diff --git a/c-api/iter.po b/c-api/iter.po index bd06b346e..6b75b8d7f 100644 --- a/c-api/iter.po +++ b/c-api/iter.po @@ -26,8 +26,9 @@ msgstr "" #: c-api/iter.rst:12 msgid "" -"Return non-zero if the object *o* can be safely passed to :c:func:" -"`PyIter_Next`, and ``0`` otherwise. This function always succeeds." +"Return non-zero if the object *o* can be safely passed " +"to :c:func:`PyIter_Next`, and ``0`` otherwise. This function always " +"succeeds." msgstr "" #: c-api/iter.rst:17 diff --git a/c-api/iterator.po b/c-api/iterator.po index 5909c9634..3bb75cab2 100644 --- a/c-api/iterator.po +++ b/c-api/iterator.po @@ -23,10 +23,10 @@ msgstr "" #: 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:`~object." -"__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." +"iterator, works with an arbitrary sequence supporting " +"the :meth:`~object.__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 "" #: c-api/iterator.rst:17 diff --git a/c-api/list.po b/c-api/list.po index f7203cc03..2cfc1db24 100644 --- a/c-api/list.po +++ b/c-api/list.po @@ -49,9 +49,9 @@ msgstr "" #: 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`." +"``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 "" #: c-api/list.rst:50 @@ -97,9 +97,10 @@ msgstr "" #: c-api/list.rst:91 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." +"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 "" #: c-api/list.rst:99 diff --git a/c-api/long.po b/c-api/long.po index 076f15090..cb5da552f 100644 --- a/c-api/long.po +++ b/c-api/long.po @@ -44,8 +44,8 @@ msgstr "" #: c-api/long.rst:29 msgid "" -"Return true if its argument is a :c:type:`PyLongObject` or a subtype of :c:" -"type:`PyLongObject`. This function always succeeds." +"Return true if its argument is a :c:type:`PyLongObject` or a subtype " +"of :c:type:`PyLongObject`. This function always succeeds." msgstr "" #: c-api/long.rst:35 @@ -119,8 +119,8 @@ msgstr "" #: c-api/long.rst:97 msgid "" -"Python methods :meth:`int.to_bytes` and :meth:`int.from_bytes` to convert a :" -"c:type:`PyLongObject` to/from an array of bytes in base ``256``. You can " +"Python methods :meth:`int.to_bytes` and :meth:`int.from_bytes` to convert " +"a :c:type:`PyLongObject` to/from an array of bytes in base ``256``. You can " "call those from C using :c:func:`PyObject_CallMethod`." msgstr "" @@ -145,8 +145,8 @@ msgstr "" #: c-api/long.rst:127 msgid "" -"Raise :exc:`OverflowError` if the value of *obj* is out of range for a :c:" -"expr:`long`." +"Raise :exc:`OverflowError` if the value of *obj* is out of range for " +"a :c:expr:`long`." msgstr "" #: c-api/long.rst:150 c-api/long.rst:191 c-api/long.rst:214 @@ -163,10 +163,11 @@ msgstr "" #: c-api/long.rst:145 msgid "" -"If the value of *obj* is greater than :c:macro:`LONG_MAX` or less than :c:" -"macro:`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." +"If the value of *obj* is greater than :c:macro:`LONG_MAX` or less " +"than :c:macro:`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 "" #: c-api/long.rst:182 @@ -178,16 +179,17 @@ msgstr "" #: c-api/long.rst:168 msgid "" -"Raise :exc:`OverflowError` if the value of *obj* is out of range for a :c:" -"expr:`long long`." +"Raise :exc:`OverflowError` if the value of *obj* is out of range for " +"a :c:expr:`long long`." msgstr "" #: c-api/long.rst:186 msgid "" -"If the value of *obj* is greater than :c:macro:`LLONG_MAX` or less than :c:" -"macro:`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." +"If the value of *obj* is greater than :c:macro:`LLONG_MAX` or less " +"than :c:macro:`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 "" #: c-api/long.rst:208 @@ -198,8 +200,8 @@ msgstr "" #: c-api/long.rst:211 msgid "" -"Raise :exc:`OverflowError` if the value of *pylong* is out of range for a :c:" -"type:`Py_ssize_t`." +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for " +"a :c:type:`Py_ssize_t`." msgstr "" #: c-api/long.rst:223 @@ -210,8 +212,8 @@ msgstr "" #: c-api/long.rst:226 msgid "" -"Raise :exc:`OverflowError` if the value of *pylong* is out of range for a :c:" -"expr:`unsigned long`." +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for " +"a :c:expr:`unsigned long`." msgstr "" #: c-api/long.rst:229 @@ -228,8 +230,8 @@ msgstr "" #: c-api/long.rst:242 msgid "" -"Raise :exc:`OverflowError` if the value of *pylong* is out of range for a :c:" -"type:`size_t`." +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for " +"a :c:type:`size_t`." msgstr "" #: c-api/long.rst:245 @@ -246,8 +248,8 @@ msgstr "" #: c-api/long.rst:257 msgid "" -"Raise :exc:`OverflowError` if the value of *pylong* is out of range for an :" -"c:expr:`unsigned long long`." +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for " +"an :c:expr:`unsigned long long`." msgstr "" #: c-api/long.rst:260 @@ -264,8 +266,9 @@ msgstr "" #: c-api/long.rst:269 msgid "" "Return a C :c:expr:`unsigned long` representation of *obj*. If *obj* is not " -"an instance of :c:type:`PyLongObject`, first call its :meth:`~object." -"__index__` method (if present) to convert it to a :c:type:`PyLongObject`." +"an instance of :c:type:`PyLongObject`, first call " +"its :meth:`~object.__index__` method (if present) to convert it to " +"a :c:type:`PyLongObject`." msgstr "" #: c-api/long.rst:273 @@ -283,8 +286,9 @@ msgstr "" #: c-api/long.rst:288 msgid "" "Return a C :c:expr:`unsigned long long` representation of *obj*. If *obj* " -"is not an instance of :c:type:`PyLongObject`, first call its :meth:`~object." -"__index__` method (if present) to convert it to a :c:type:`PyLongObject`." +"is not an instance of :c:type:`PyLongObject`, first call " +"its :meth:`~object.__index__` method (if present) to convert it to " +"a :c:type:`PyLongObject`." msgstr "" #: c-api/long.rst:293 @@ -307,8 +311,8 @@ msgstr "" #: c-api/long.rst:311 msgid "" -"Raise :exc:`OverflowError` if the value of *pylong* is out of range for a :c:" -"expr:`double`." +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for " +"a :c:expr:`double`." msgstr "" #: c-api/long.rst:314 @@ -320,8 +324,8 @@ msgstr "" msgid "" "Convert a Python integer *pylong* to a C :c:expr:`void` pointer. If *pylong* " "cannot be converted, an :exc:`OverflowError` will be raised. This is only " -"assured to produce a usable :c:expr:`void` pointer for values created with :" -"c:func:`PyLong_FromVoidPtr`." +"assured to produce a usable :c:expr:`void` pointer for values created " +"with :c:func:`PyLong_FromVoidPtr`." msgstr "" #: c-api/long.rst:324 @@ -347,9 +351,9 @@ msgstr "" #: c-api/long.rst:342 msgid "" "This function makes it possible for performance-critical code to implement a " -"“fast path” for small integers. For compact values use :c:func:" -"`PyUnstable_Long_CompactValue`; for others fall back to a :c:func:" -"`PyLong_As* ` function or :c:func:`calling " +"“fast path” for small integers. For compact values " +"use :c:func:`PyUnstable_Long_CompactValue`; for others fall back to " +"a :c:func:`PyLong_As* ` function or :c:func:`calling " "` :meth:`int.to_bytes`." msgstr "" diff --git a/c-api/mapping.po b/c-api/mapping.po index 1f38d656b..c0355518a 100644 --- a/c-api/mapping.po +++ b/c-api/mapping.po @@ -22,8 +22,8 @@ msgstr "" #: c-api/mapping.rst:8 msgid "" -"See also :c:func:`PyObject_GetItem`, :c:func:`PyObject_SetItem` and :c:func:" -"`PyObject_DelItem`." +"See also :c:func:`PyObject_GetItem`, :c:func:`PyObject_SetItem` " +"and :c:func:`PyObject_DelItem`." msgstr "" #: c-api/mapping.rst:14 @@ -43,16 +43,16 @@ msgstr "" #: c-api/mapping.rst:31 msgid "" -"This is the same as :c:func:`PyObject_GetItem`, but *key* is specified as a :" -"c:expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"This is the same as :c:func:`PyObject_GetItem`, but *key* is specified as " +"a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/mapping.rst:38 msgid "" -"This is the same as :c:func:`PyObject_SetItem`, but *key* is specified as a :" -"c:expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"This is the same as :c:func:`PyObject_SetItem`, but *key* is specified as " +"a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/mapping.rst:45 @@ -61,9 +61,9 @@ msgstr "" #: c-api/mapping.rst:50 msgid "" -"This is the same as :c:func:`PyObject_DelItem`, but *key* is specified as a :" -"c:expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"This is the same as :c:func:`PyObject_DelItem`, but *key* is specified as " +"a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/mapping.rst:57 @@ -76,15 +76,15 @@ msgstr "" #: c-api/mapping.rst:63 msgid "" "Exceptions which occur when this calls :meth:`~object.__getitem__` method " -"are silently ignored. For proper error handling, use :c:func:" -"`PyObject_GetItem()` instead." +"are silently ignored. For proper error handling, " +"use :c:func:`PyObject_GetItem()` instead." msgstr "" #: c-api/mapping.rst:70 msgid "" -"This is the same as :c:func:`PyMapping_HasKey`, but *key* is specified as a :" -"c:expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"This is the same as :c:func:`PyMapping_HasKey`, but *key* is specified as " +"a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/mapping.rst:76 diff --git a/c-api/marshal.po b/c-api/marshal.po index 5f5244885..cebf699d9 100644 --- a/c-api/marshal.po +++ b/c-api/marshal.po @@ -50,8 +50,8 @@ msgstr "" #: c-api/marshal.rst:36 msgid "" -"This function can fail, in which case it sets the error indicator. Use :c:" -"func:`PyErr_Occurred` to check for that." +"This function can fail, in which case it sets the error indicator. " +"Use :c:func:`PyErr_Occurred` to check for that." msgstr "" #: c-api/marshal.rst:33 diff --git a/c-api/memory.po b/c-api/memory.po index 79940f62c..033ddd29b 100644 --- a/c-api/memory.po +++ b/c-api/memory.po @@ -60,13 +60,14 @@ msgstr "" #: 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::" +"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 "" #: c-api/memory.rst:58 @@ -136,8 +137,8 @@ msgid "" "allocation functions belonging to a given domain for only the purposes " "hinted by that domain (although this is the recommended practice). For " "example, one could use the memory returned by :c:func:`PyMem_RawMalloc` for " -"allocating Python objects or the memory returned by :c:func:" -"`PyObject_Malloc` for allocating memory for buffers." +"allocating Python objects or the memory returned " +"by :c:func:`PyObject_Malloc` for allocating memory for buffers." msgstr "" #: c-api/memory.rst:112 @@ -234,9 +235,9 @@ msgstr "" #: c-api/memory.rst:176 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`." +"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 "" #: c-api/memory.rst:180 @@ -248,9 +249,9 @@ msgstr "" #: c-api/memory.rst:186 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_RawFree(p)`` has been " -"called before, undefined behavior occurs." +"previous call to :c:func:`PyMem_RawMalloc`, :c:func:`PyMem_RawRealloc` " +"or :c:func:`PyMem_RawCalloc`. Otherwise, or if ``PyMem_RawFree(p)`` has " +"been called before, undefined behavior occurs." msgstr "" #: c-api/memory.rst:261 c-api/memory.rst:369 @@ -270,8 +271,8 @@ msgstr "" #: c-api/memory.rst:203 msgid "" -"The :ref:`default memory allocator ` uses the :" -"ref:`pymalloc memory allocator `." +"The :ref:`default memory allocator ` uses " +"the :ref:`pymalloc memory allocator `." msgstr "" #: c-api/memory.rst:320 @@ -308,8 +309,8 @@ msgstr "" #: c-api/memory.rst:247 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`." +"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 "" #: c-api/memory.rst:250 @@ -321,9 +322,9 @@ msgstr "" #: c-api/memory.rst:256 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." +"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 "" #: c-api/memory.rst:263 @@ -403,8 +404,8 @@ msgstr "" #: c-api/memory.rst:315 msgid "" -"The :ref:`default object allocator ` uses the :" -"ref:`pymalloc memory allocator `." +"The :ref:`default object allocator ` uses " +"the :ref:`pymalloc memory allocator `." msgstr "" #: c-api/memory.rst:328 @@ -430,9 +431,9 @@ msgstr "" #: c-api/memory.rst:355 msgid "" -"Unless *p* is ``NULL``, it must have been returned by a previous call to :c:" -"func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or :c:func:" -"`PyObject_Calloc`." +"Unless *p* is ``NULL``, it must have been returned by a previous call " +"to :c:func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` " +"or :c:func:`PyObject_Calloc`." msgstr "" #: c-api/memory.rst:358 @@ -444,9 +445,9 @@ msgstr "" #: c-api/memory.rst:364 msgid "" "Frees the memory block pointed to by *p*, which must have been returned by a " -"previous call to :c:func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or :c:" -"func:`PyObject_Calloc`. Otherwise, or if ``PyObject_Free(p)`` has been " -"called before, undefined behavior occurs." +"previous call to :c:func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` " +"or :c:func:`PyObject_Calloc`. Otherwise, or if ``PyObject_Free(p)`` has " +"been called before, undefined behavior occurs." msgstr "" #: c-api/memory.rst:375 @@ -535,8 +536,9 @@ msgstr "" #: c-api/memory.rst:391 msgid "" -"``malloc``: system allocators from the standard C library, C functions: :c:" -"func:`malloc`, :c:func:`calloc`, :c:func:`realloc` and :c:func:`free`." +"``malloc``: system allocators from the standard C library, C " +"functions: :c:func:`malloc`, :c:func:`calloc`, :c:func:`realloc` " +"and :c:func:`free`." msgstr "" #: c-api/memory.rst:393 @@ -613,8 +615,8 @@ msgstr "" #: c-api/memory.rst:425 msgid "" -"The :c:type:`!PyMemAllocator` structure was renamed to :c:type:" -"`PyMemAllocatorEx` and a new ``calloc`` field was added." +"The :c:type:`!PyMemAllocator` structure was renamed " +"to :c:type:`PyMemAllocatorEx` and a new ``calloc`` field was added." msgstr "" #: c-api/memory.rst:432 @@ -720,20 +722,20 @@ msgstr "" #: c-api/memory.rst:494 msgid "" -"It can be called after :c:func:`Py_PreInitialize` and before :c:func:" -"`Py_InitializeFromConfig` to install a custom memory allocator. There are no " -"restrictions over the installed allocator other than the ones imposed by the " -"domain (for instance, the Raw Domain allows the allocator to be called " -"without the GIL held). See :ref:`the section on allocator domains ` for more information." +"It can be called after :c:func:`Py_PreInitialize` and " +"before :c:func:`Py_InitializeFromConfig` to install a custom memory " +"allocator. There are no restrictions over the installed allocator other than " +"the ones imposed by the domain (for instance, the Raw Domain allows the " +"allocator to be called without the GIL held). See :ref:`the section on " +"allocator domains ` for more information." msgstr "" #: c-api/memory.rst:502 msgid "" -"If called after Python has finish initializing (after :c:func:" -"`Py_InitializeFromConfig` has been called) the allocator **must** wrap the " -"existing allocator. Substituting the current allocator for some other " -"arbitrary one is **not supported**." +"If called after Python has finish initializing " +"(after :c:func:`Py_InitializeFromConfig` has been called) the allocator " +"**must** wrap the existing allocator. Substituting the current allocator for " +"some other arbitrary one is **not supported**." msgstr "" #: c-api/memory.rst:507 @@ -752,8 +754,8 @@ msgstr "" #: c-api/memory.rst:522 msgid "" -"When :ref:`Python is built in debug mode `, the :c:func:" -"`PyMem_SetupDebugHooks` function is called at the :ref:`Python " +"When :ref:`Python is built in debug mode `, " +"the :c:func:`PyMem_SetupDebugHooks` function is called at the :ref:`Python " "preinitialization ` to setup debug hooks on Python memory " "allocators to detect memory errors." msgstr "" @@ -921,10 +923,11 @@ msgstr "" #: c-api/memory.rst:607 msgid "" "The :c:func:`PyMem_SetupDebugHooks` 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:macro:" -"`PYMEM_DOMAIN_OBJ` and :c:macro:`PYMEM_DOMAIN_MEM` domains are called." +"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:macro:`PYMEM_DOMAIN_OBJ` and :c:macro:`PYMEM_DOMAIN_MEM` domains are " +"called." msgstr "" #: c-api/memory.rst:615 @@ -944,15 +947,15 @@ 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 either 256 KiB on 32-bit platforms or 1 MiB " -"on 64-bit platforms. It falls back to :c:func:`PyMem_RawMalloc` and :c:func:" -"`PyMem_RawRealloc` for allocations larger than 512 bytes." +"on 64-bit platforms. It falls back to :c:func:`PyMem_RawMalloc` " +"and :c:func:`PyMem_RawRealloc` for allocations larger than 512 bytes." msgstr "" #: c-api/memory.rst:633 msgid "" "*pymalloc* is the :ref:`default allocator ` of " -"the :c:macro:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) and :c:macro:" -"`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) domains." +"the :c:macro:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) " +"and :c:macro:`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) domains." msgstr "" #: c-api/memory.rst:637 @@ -974,8 +977,9 @@ msgstr "" #: c-api/memory.rst:643 msgid "" "This allocator is disabled if Python is configured with the :option:`--" -"without-pymalloc` option. It can also be disabled at runtime using the :" -"envvar:`PYTHONMALLOC` environment variable (ex: ``PYTHONMALLOC=malloc``)." +"without-pymalloc` option. It can also be disabled at runtime using " +"the :envvar:`PYTHONMALLOC` environment variable (ex: " +"``PYTHONMALLOC=malloc``)." msgstr "" #: c-api/memory.rst:648 @@ -1105,8 +1109,9 @@ msgstr "" #: c-api/memory.rst:743 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:macro:" -"`PyObject_New`, :c:macro:`PyObject_NewVar` and :c:func:`PyObject_Del`." +"Python heap, objects in Python are allocated and released " +"with :c:macro:`PyObject_New`, :c:macro:`PyObject_NewVar` " +"and :c:func:`PyObject_Del`." msgstr "" #: c-api/memory.rst:747 diff --git a/c-api/memoryview.po b/c-api/memoryview.po index dca40d931..6208b6d72 100644 --- a/c-api/memoryview.po +++ b/c-api/memoryview.po @@ -87,9 +87,10 @@ msgstr "" #: c-api/memoryview.rst:73 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." +"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 "" #: c-api/memoryview.rst:5 diff --git a/c-api/method.po b/c-api/method.po index 8edfc49f7..19b303517 100644 --- a/c-api/method.po +++ b/c-api/method.po @@ -35,9 +35,9 @@ msgstr "" #: 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``. This function " -"always succeeds." +"Return true if *o* is an instance method object (has " +"type :c:data:`PyInstanceMethod_Type`). The parameter must not be ``NULL``. " +"This function always succeeds." msgstr "" #: c-api/method.rst:30 diff --git a/c-api/module.po b/c-api/module.po index 3669cf476..baf7ed455 100644 --- a/c-api/module.po +++ b/c-api/module.po @@ -34,17 +34,18 @@ msgstr "" #: c-api/module.rst:27 msgid "" -"Return true if *p* is a module object, but not a subtype of :c:data:" -"`PyModule_Type`. This function always succeeds." +"Return true if *p* is a module object, but not a subtype " +"of :c:data:`PyModule_Type`. This function always succeeds." msgstr "" #: c-api/module.rst:40 msgid "" "Return a new module object with :attr:`module.__name__` set to *name*. The " -"module's :attr:`!__name__`, :attr:`~module.__doc__`, :attr:`~module." -"__package__` and :attr:`~module.__loader__` attributes are filled in (all " -"but :attr:`!__name__` are set to ``None``). The caller is responsible for " -"setting a :attr:`~module.__file__` attribute." +"module's :attr:`!" +"__name__`, :attr:`~module.__doc__`, :attr:`~module.__package__` " +"and :attr:`~module.__loader__` attributes are filled in (all but :attr:`!" +"__name__` are set to ``None``). The caller is responsible for setting " +"a :attr:`~module.__file__` attribute." msgstr "" #: c-api/module.rst:272 c-api/module.rst:447 @@ -74,8 +75,8 @@ msgstr "" #: c-api/module.rst:70 msgid "" "It is recommended extensions use other ``PyModule_*`` and ``PyObject_*`` " -"functions rather than directly manipulate a module's :attr:`~object." -"__dict__`." +"functions rather than directly manipulate a " +"module's :attr:`~object.__dict__`." msgstr "" #: c-api/module.rst:81 @@ -94,8 +95,8 @@ msgstr "" #: c-api/module.rst:95 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`." +"memory allocated at module creation time, or ``NULL``. " +"See :c:member:`PyModuleDef.m_size`." msgstr "" #: c-api/module.rst:102 @@ -106,10 +107,10 @@ msgstr "" #: c-api/module.rst:112 msgid "" -"Return the name of the file from which *module* was loaded using *module*'s :" -"attr:`~module.__file__` attribute. If this is not defined, or if it is not " -"a string, raise :exc:`SystemError` and return ``NULL``; otherwise return a " -"reference to a Unicode object." +"Return the name of the file from which *module* was loaded using " +"*module*'s :attr:`~module.__file__` attribute. If this is not defined, or " +"if it is not a string, raise :exc:`SystemError` and return ``NULL``; " +"otherwise return a reference to a Unicode object." msgstr "" #: c-api/module.rst:122 @@ -138,9 +139,10 @@ msgstr "" #: c-api/module.rst:140 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." +"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 "" #: c-api/module.rst:146 @@ -160,8 +162,8 @@ msgstr "" #: c-api/module.rst:160 msgid "" -"Docstring for the module; usually a docstring variable created with :c:macro:" -"`PyDoc_STRVAR` is used." +"Docstring for the module; usually a docstring variable created " +"with :c:macro:`PyDoc_STRVAR` is used." msgstr "" #: c-api/module.rst:165 @@ -174,8 +176,8 @@ msgstr "" #: c-api/module.rst:169 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:" -"`~PyModuleDef.m_free` function has been called, if present." +"freed when the module object is deallocated, after " +"the :c:member:`~PyModuleDef.m_free` function has been called, if present." msgstr "" #: c-api/module.rst:173 @@ -198,8 +200,9 @@ msgstr "" #: c-api/module.rst:185 msgid "" -"A pointer to a table of module-level functions, described by :c:type:" -"`PyMethodDef` values. Can be ``NULL`` if no functions are present." +"A pointer to a table of module-level functions, described " +"by :c:type:`PyMethodDef` values. Can be ``NULL`` if no functions are " +"present." msgstr "" #: c-api/module.rst:190 @@ -227,8 +230,8 @@ msgid "" "allocated yet. This is the case immediately after the module is created and " "before the module is executed (:c:data:`Py_mod_exec` function). More " "precisely, this function is not called if :c:member:`~PyModuleDef.m_size` is " -"greater than 0 and the module state (as returned by :c:func:" -"`PyModule_GetState`) is ``NULL``." +"greater than 0 and the module state (as returned " +"by :c:func:`PyModule_GetState`) is ``NULL``." msgstr "" #: c-api/module.rst:234 c-api/module.rst:249 @@ -270,8 +273,8 @@ msgstr "" #: c-api/module.rst:261 msgid "" "Create a new module object, given the definition in *def*. This behaves " -"like :c:func:`PyModule_Create2` with *module_api_version* set to :c:macro:" -"`PYTHON_API_VERSION`." +"like :c:func:`PyModule_Create2` with *module_api_version* set " +"to :c:macro:`PYTHON_API_VERSION`." msgstr "" #: c-api/module.rst:268 @@ -290,8 +293,8 @@ msgstr "" #: c-api/module.rst:279 msgid "" "Before it is returned from in the initialization function, the resulting " -"module object is typically populated using functions like :c:func:" -"`PyModule_AddObjectRef`." +"module object is typically populated using functions " +"like :c:func:`PyModule_AddObjectRef`." msgstr "" #: c-api/module.rst:285 @@ -316,9 +319,10 @@ msgid "" "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:`~object." -"__dict__` or individual classes created with :c:func:`PyType_FromSpec`)." +"specific to the module object (using e.g. " +"using :c:func:`PyModule_GetState`), or its contents (such as the " +"module's :attr:`~object.__dict__` or individual classes created " +"with :c:func:`PyType_FromSpec`)." msgstr "" #: c-api/module.rst:304 @@ -331,9 +335,9 @@ msgstr "" #: c-api/module.rst:308 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:" +"(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 "" #: c-api/module.rst:315 @@ -405,12 +409,12 @@ msgstr "" #: c-api/module.rst:368 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``." +"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 "" #: c-api/module.rst:377 @@ -601,10 +605,10 @@ msgstr "" msgid "" "The number of different *name* strings passed to this function should be " "kept small, usually by only using statically allocated strings as *name*. " -"For names that aren't known at compile time, prefer calling :c:func:" -"`PyUnicode_FromString` and :c:func:`PyObject_SetAttr` directly. For more " -"details, see :c:func:`PyUnicode_InternFromString`, which may be used " -"internally to create a key object." +"For names that aren't known at compile time, prefer " +"calling :c:func:`PyUnicode_FromString` and :c:func:`PyObject_SetAttr` " +"directly. For more details, see :c:func:`PyUnicode_InternFromString`, which " +"may be used internally to create a key object." msgstr "" #: c-api/module.rst:544 @@ -616,8 +620,8 @@ msgstr "" #: c-api/module.rst:547 msgid "" "The new :c:func:`PyModule_AddObjectRef` function is recommended, since it is " -"easy to introduce reference leaks by misusing the :c:func:" -"`PyModule_AddObject` function." +"easy to introduce reference leaks by misusing " +"the :c:func:`PyModule_AddObject` function." msgstr "" #: c-api/module.rst:553 @@ -628,8 +632,8 @@ msgstr "" #: c-api/module.rst:556 msgid "" -"This means that its return value must be checked, and calling code must :c:" -"func:`Py_DECREF` *value* manually on error." +"This means that its return value must be checked, and calling code " +"must :c:func:`Py_DECREF` *value* manually on error." msgstr "" #: c-api/module.rst:561 @@ -676,8 +680,8 @@ msgstr "" #: c-api/module.rst:603 msgid "" -"This is a convenience function that calls :c:func:`PyLong_FromLong` and :c:" -"func:`PyModule_AddObjectRef`; see their documentation for details." +"This is a convenience function that calls :c:func:`PyLong_FromLong` " +"and :c:func:`PyModule_AddObjectRef`; see their documentation for details." msgstr "" #: c-api/module.rst:609 @@ -690,9 +694,9 @@ msgstr "" #: c-api/module.rst:614 msgid "" -"This is a convenience function that calls :c:func:" -"`PyUnicode_InternFromString` and :c:func:`PyModule_AddObjectRef`; see their " -"documentation for details." +"This is a convenience function that " +"calls :c:func:`PyUnicode_InternFromString` " +"and :c:func:`PyModule_AddObjectRef`; see their documentation for details." msgstr "" #: c-api/module.rst:621 @@ -745,8 +749,8 @@ msgstr "" #: c-api/module.rst:661 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`." +"This allows the module object to be accessible " +"via :c:func:`PyState_FindModule`." msgstr "" #: c-api/module.rst:664 diff --git a/c-api/number.po b/c-api/number.po index d9322e8a2..312de6672 100644 --- a/c-api/number.po +++ b/c-api/number.po @@ -256,8 +256,8 @@ msgstr "" #: c-api/number.rst:257 msgid "" -"Returns the *o* converted to a Python int on success or ``NULL`` with a :exc:" -"`TypeError` exception raised on failure." +"Returns the *o* converted to a Python int on success or ``NULL`` with " +"a :exc:`TypeError` exception raised on failure." msgstr "" #: c-api/number.rst:260 @@ -271,8 +271,8 @@ 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." +"respectively. If *n* is not a Python int, it is converted " +"with :c:func:`PyNumber_Index` first." msgstr "" #: c-api/number.rst:276 @@ -284,12 +284,12 @@ msgstr "" #: c-api/number.rst:279 msgid "" -"If *o* can be converted to a Python int but the attempt to convert to a :c:" -"type:`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." +"If *o* can be converted to a Python int but the attempt to convert to " +"a :c:type:`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 "" #: c-api/number.rst:289 diff --git a/c-api/objbuffer.po b/c-api/objbuffer.po index ae4d6f8b5..8629ba8cf 100644 --- a/c-api/objbuffer.po +++ b/c-api/objbuffer.po @@ -33,9 +33,10 @@ msgstr "" #: 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." +"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 "" #: c-api/objbuffer.rst:23 @@ -43,8 +44,8 @@ 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." +"and *buffer_len* to the buffer length. Returns ``-1`` and sets " +"a :exc:`TypeError` on error." msgstr "" #: c-api/objbuffer.rst:32 @@ -52,8 +53,8 @@ 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." +"and *buffer_len* to the buffer length. Returns ``-1`` and sets " +"a :exc:`TypeError` on error." msgstr "" #: c-api/objbuffer.rst:41 diff --git a/c-api/object.po b/c-api/object.po index 90f26d646..08a49c637 100644 --- a/c-api/object.po +++ b/c-api/object.po @@ -29,15 +29,16 @@ msgstr "" #: c-api/object.rst:17 msgid "" "Properly handle returning :c:data:`Py_NotImplemented` from within a C " -"function (that is, create a new :term:`strong reference` to :const:" -"`NotImplemented` and return it)." +"function (that is, create a new :term:`strong reference` " +"to :const:`NotImplemented` and return it)." msgstr "" #: c-api/object.rst:24 msgid "" -"Flag to be used with multiple functions that print the object (like :c:func:" -"`PyObject_Print` and :c:func:`PyFile_WriteObject`). If passed, these " -"function would use the :func:`str` of the object instead of the :func:`repr`." +"Flag to be used with multiple functions that print the object " +"(like :c:func:`PyObject_Print` and :c:func:`PyFile_WriteObject`). If passed, " +"these function would use the :func:`str` of the object instead of " +"the :func:`repr`." msgstr "" #: c-api/object.rst:32 @@ -57,24 +58,24 @@ msgstr "" #: c-api/object.rst:46 msgid "" -"Exceptions that occur when this calls :meth:`~object.__getattr__` and :meth:" -"`~object.__getattribute__` methods are silently ignored. For proper error " -"handling, use :c:func:`PyObject_GetAttr` instead." +"Exceptions that occur when this calls :meth:`~object.__getattr__` " +"and :meth:`~object.__getattribute__` methods are silently ignored. For " +"proper error handling, use :c:func:`PyObject_GetAttr` instead." msgstr "" #: c-api/object.rst:53 msgid "" "This is the same as :c:func:`PyObject_HasAttr`, but *attr_name* is specified " -"as a :c:expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"as a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/object.rst:59 msgid "" -"Exceptions that occur when this calls :meth:`~object.__getattr__` and :meth:" -"`~object.__getattribute__` methods or while creating the temporary :class:" -"`str` object are silently ignored. For proper error handling, use :c:func:" -"`PyObject_GetAttrString` instead." +"Exceptions that occur when this calls :meth:`~object.__getattr__` " +"and :meth:`~object.__getattribute__` methods or while creating the " +"temporary :class:`str` object are silently ignored. For proper error " +"handling, use :c:func:`PyObject_GetAttrString` instead." msgstr "" #: c-api/object.rst:67 @@ -87,18 +88,19 @@ msgstr "" #: c-api/object.rst:74 msgid "" "This is the same as :c:func:`PyObject_GetAttr`, but *attr_name* is specified " -"as a :c:expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"as a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/object.rst:81 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." +"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 "" #: c-api/object.rst:91 @@ -118,8 +120,8 @@ msgstr "" #: c-api/object.rst:103 msgid "" "This is the same as :c:func:`PyObject_SetAttr`, but *attr_name* is specified " -"as a :c:expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"as a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/object.rst:107 @@ -132,10 +134,10 @@ msgstr "" msgid "" "The number of different attribute names passed to this function should be " "kept small, usually by using a statically allocated string as *attr_name*. " -"For attribute names that aren't known at compile time, prefer calling :c:" -"func:`PyUnicode_FromString` and :c:func:`PyObject_SetAttr` directly. For " -"more details, see :c:func:`PyUnicode_InternFromString`, which may be used " -"internally to create a key object." +"For attribute names that aren't known at compile time, prefer " +"calling :c:func:`PyUnicode_FromString` and :c:func:`PyObject_SetAttr` " +"directly. For more details, see :c:func:`PyUnicode_InternFromString`, which " +"may be used internally to create a key object." msgstr "" #: c-api/object.rst:120 @@ -159,18 +161,18 @@ msgstr "" #: c-api/object.rst:138 msgid "" "This is the same as :c:func:`PyObject_DelAttr`, but *attr_name* is specified " -"as a :c:expr:`const char*` UTF-8 encoded bytes string, rather than a :c:expr:" -"`PyObject*`." +"as a :c:expr:`const char*` UTF-8 encoded bytes string, rather than " +"a :c:expr:`PyObject*`." msgstr "" #: c-api/object.rst:142 msgid "" "The number of different attribute names passed to this function should be " "kept small, usually by using a statically allocated string as *attr_name*. " -"For attribute names that aren't known at compile time, prefer calling :c:" -"func:`PyUnicode_FromString` and :c:func:`PyObject_DelAttr` directly. For " -"more details, see :c:func:`PyUnicode_InternFromString`, which may be used " -"internally to create a key object for lookup." +"For attribute names that aren't known at compile time, prefer " +"calling :c:func:`PyUnicode_FromString` and :c:func:`PyObject_DelAttr` " +"directly. For more details, see :c:func:`PyUnicode_InternFromString`, which " +"may be used internally to create a key object for lookup." msgstr "" #: c-api/object.rst:153 @@ -214,12 +216,12 @@ msgstr "" #: c-api/object.rst:187 msgid "" "Compare the values of *o1* and *o2* using the operation specified by *opid*, " -"which must be one of :c:macro:`Py_LT`, :c:macro:`Py_LE`, :c:macro:`Py_EQ`, :" -"c:macro:`Py_NE`, :c:macro:`Py_GT`, or :c:macro:`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." +"which must be one " +"of :c:macro:`Py_LT`, :c:macro:`Py_LE`, :c:macro:`Py_EQ`, :c:macro:`Py_NE`, :c:macro:`Py_GT`, " +"or :c:macro:`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 "" #: c-api/object.rst:197 @@ -265,10 +267,10 @@ msgstr "" #: c-api/object.rst:230 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." +"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 "" #: c-api/object.rst:241 @@ -305,8 +307,8 @@ msgstr "" msgid "" "If *cls* has a :meth:`~type.__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 :attr:`cls.__mro__ `." +"*derived* is a subclass of *cls* if it is a direct or indirect subclass, " +"i.e. contained in :attr:`cls.__mro__ `." msgstr "" #: c-api/object.rst:276 @@ -331,8 +333,8 @@ msgstr "" #: c-api/object.rst:294 msgid "" -"An instance *inst* can override what is considered its class by having a :" -"attr:`~object.__class__` attribute." +"An instance *inst* can override what is considered its class by having " +"a :attr:`~object.__class__` attribute." msgstr "" #: c-api/object.rst:297 @@ -435,8 +437,8 @@ msgid "" "(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." +"case, if no execution frame is active then ``NULL`` is returned " +"but :c:func:`PyErr_Occurred` will return false." msgstr "" #: c-api/object.rst:407 @@ -449,11 +451,11 @@ msgstr "" #: c-api/object.rst:415 msgid "" -"This is the equivalent to the Python expression ``aiter(o)``. Takes an :" -"class:`AsyncIterable` object and returns an :class:`AsyncIterator` for it. " -"This is typically a new iterator but if the argument is an :class:" -"`AsyncIterator`, this returns itself. Raises :exc:`TypeError` and returns " -"``NULL`` if the object cannot be iterated." +"This is the equivalent to the Python expression ``aiter(o)``. Takes " +"an :class:`AsyncIterable` object and returns an :class:`AsyncIterator` for " +"it. This is typically a new iterator but if the argument is " +"an :class:`AsyncIterator`, this returns itself. Raises :exc:`TypeError` and " +"returns ``NULL`` if the object cannot be iterated." msgstr "" #: c-api/object.rst:425 @@ -480,14 +482,14 @@ msgstr "" #: c-api/object.rst:440 msgid "" "This may be larger than requested using :c:member:`-PyType_Spec.basicsize " -"`; it is safe to use this larger size (e.g. with :c:" -"func:`!memset`)." +"`; it is safe to use this larger size (e.g. " +"with :c:func:`!memset`)." msgstr "" #: c-api/object.rst:443 msgid "" -"The type *cls* **must** have been created using negative :c:member:" -"`PyType_Spec.basicsize`. Python does not check this." +"The type *cls* **must** have been created using " +"negative :c:member:`PyType_Spec.basicsize`. Python does not check this." msgstr "" #: c-api/object.rst:447 @@ -496,8 +498,8 @@ msgstr "" #: c-api/object.rst:453 msgid "" -"Get a pointer to per-item data for a class with :c:macro:" -"`Py_TPFLAGS_ITEMS_AT_END`." +"Get a pointer to per-item data for a class " +"with :c:macro:`Py_TPFLAGS_ITEMS_AT_END`." msgstr "" #: c-api/object.rst:456 diff --git a/c-api/perfmaps.po b/c-api/perfmaps.po index 7596a5a47..5d6d59cbc 100644 --- a/c-api/perfmaps.po +++ b/c-api/perfmaps.po @@ -24,12 +24,12 @@ msgstr "" msgid "" "On supported platforms (as of this writing, only Linux), the runtime can " "take advantage of *perf map files* to make Python functions visible to an " -"external profiling tool (such as `perf `_). A running process may create a file in the ``/tmp`` " +"external profiling tool (such as `perf `_). A running process may create a file in the ``/tmp`` " "directory, which contains entries that can map a section of executable code " "to a name. This interface is described in the `documentation of the Linux " -"Perf tool `_." +"Perf tool `_." msgstr "" #: c-api/perfmaps.rst:16 @@ -49,9 +49,9 @@ msgid "" "Open the ``/tmp/perf-$pid.map`` file, unless it's already opened, and create " "a lock to ensure thread-safe writes to the file (provided the writes are " "done through :c:func:`PyUnstable_WritePerfMapEntry`). Normally, there's no " -"need to call this explicitly; just use :c:func:" -"`PyUnstable_WritePerfMapEntry` and it will initialize the state on first " -"call." +"need to call this explicitly; just " +"use :c:func:`PyUnstable_WritePerfMapEntry` and it will initialize the state " +"on first call." msgstr "" #: c-api/perfmaps.rst:29 diff --git a/c-api/refcounting.po b/c-api/refcounting.po index a11509b38..27453492f 100644 --- a/c-api/refcounting.po +++ b/c-api/refcounting.po @@ -74,8 +74,8 @@ msgstr "" #: c-api/refcounting.rst:52 msgid "" -"This function is usually used to convert a :term:`borrowed reference` to a :" -"term:`strong reference` in-place. The :c:func:`Py_NewRef` function can be " +"This function is usually used to convert a :term:`borrowed reference` to " +"a :term:`strong reference` in-place. The :c:func:`Py_NewRef` function can be " "used to create a new :term:`strong reference`." msgstr "" @@ -91,8 +91,8 @@ msgstr "" #: c-api/refcounting.rst:61 msgid "" -"Do not expect this function to actually modify *o* in any way. For at least :" -"pep:`some objects <0683>`, this function has no effect." +"Do not expect this function to actually modify *o* in any way. For at " +"least :pep:`some objects <0683>`, this function has no effect." msgstr "" #: c-api/refcounting.rst:71 @@ -180,14 +180,14 @@ msgstr "" #: c-api/refcounting.rst:127 msgid "" -"Do not expect this function to actually modify *o* in any way. For at least :" -"pep:`some objects <683>`, this function has no effect." +"Do not expect this function to actually modify *o* in any way. For at " +"least :pep:`some objects <683>`, this function has no effect." msgstr "" #: c-api/refcounting.rst:133 msgid "" -"The deallocation function can cause arbitrary Python code to be invoked (e." -"g. when a class instance with a :meth:`~object.__del__` method is " +"The deallocation function can cause arbitrary Python code to be invoked " +"(e.g. when a class instance with a :meth:`~object.__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 " @@ -235,8 +235,9 @@ msgstr "" #: c-api/refcounting.rst:180 msgid "" -"Release a :term:`strong reference` to object *o*. A function version of :c:" -"func:`Py_XDECREF`. It can be used for runtime dynamic embedding of Python." +"Release a :term:`strong reference` to object *o*. A function version " +"of :c:func:`Py_XDECREF`. It can be used for runtime dynamic embedding of " +"Python." msgstr "" #: c-api/refcounting.rst:187 diff --git a/c-api/reflection.po b/c-api/reflection.po index c34ebef53..2f10f1157 100644 --- a/c-api/reflection.po +++ b/c-api/reflection.po @@ -58,6 +58,6 @@ msgstr "" 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*." +"and \" object\". Concatenated with the result " +"of :c:func:`PyEval_GetFuncName`, the result will be a description of *func*." msgstr "" diff --git a/c-api/sequence.po b/c-api/sequence.po index 095b65fd3..1b3095098 100644 --- a/c-api/sequence.po +++ b/c-api/sequence.po @@ -23,10 +23,10 @@ msgstr "" #: c-api/sequence.rst:11 msgid "" "Return ``1`` if the object provides the sequence protocol, and ``0`` " -"otherwise. Note that it returns ``1`` for Python classes with a :meth:" -"`~object.__getitem__` method, unless they are :class:`dict` subclasses, " -"since in general it is impossible to determine what type of keys the class " -"supports. This function always succeeds." +"otherwise. Note that it returns ``1`` for Python classes with " +"a :meth:`~object.__getitem__` method, unless they are :class:`dict` " +"subclasses, since in general it is impossible to determine what type of keys " +"the class supports. This function always succeeds." msgstr "" #: c-api/sequence.rst:23 @@ -164,17 +164,18 @@ msgstr "" #: c-api/sequence.rst:148 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 " -"retrieved 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." +"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 retrieved 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 "" #: c-api/sequence.rst:157 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." +"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 "" #: c-api/sequence.rst:163 @@ -192,10 +193,10 @@ msgstr "" #: c-api/sequence.rst:173 msgid "" -"Return the *i*\\ th element of *o* or ``NULL`` on failure. Faster form of :c:" -"func:`PySequence_GetItem` but without checking that :c:func:" -"`PySequence_Check` on *o* is true and without adjustment for negative " -"indices." +"Return the *i*\\ th element of *o* or ``NULL`` on failure. Faster 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 "" #: c-api/sequence.rst:123 diff --git a/c-api/set.po b/c-api/set.po index 2a560e3ce..22867b140 100644 --- a/c-api/set.po +++ b/c-api/set.po @@ -24,38 +24,35 @@ msgstr "" msgid "" "This section details the public API for :class:`set` and :class:`frozenset` " "objects. Any functionality not listed below is best accessed using 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`)." +"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 "" #: 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 all are subject to change. " -"All access should be done through the documented API rather than by " +"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 all are subject to " +"change. All access should be done through the documented API rather than by " "manipulating the values in the structure." msgstr "" #: c-api/set.rst:40 msgid "" -"This is an instance of :c:type:`PyTypeObject` representing the Python :class:" -"`set` type." +"This is an instance of :c:type:`PyTypeObject` representing the " +"Python :class:`set` type." msgstr "" #: c-api/set.rst:46 msgid "" -"This is an instance of :c:type:`PyTypeObject` representing the Python :class:" -"`frozenset` type." +"This is an instance of :c:type:`PyTypeObject` representing the " +"Python :class:`frozenset` type." msgstr "" #: c-api/set.rst:49 @@ -113,21 +110,21 @@ msgstr "" 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." +"Return the new set on success or ``NULL`` on failure. " +"Raise :exc:`TypeError` if *iterable* is not actually iterable." msgstr "" #: c-api/set.rst:104 msgid "" -"The following functions and macros are available for instances of :class:" -"`set` or :class:`frozenset` or instances of their subtypes." +"The following functions and macros are available for instances " +"of :class:`set` or :class:`frozenset` or instances of their subtypes." msgstr "" #: c-api/set.rst:112 msgid "" "Return the length of a :class:`set` or :class:`frozenset` object. Equivalent " -"to ``len(anyset)``. Raises a :exc:`SystemError` if *anyset* is not a :class:" -"`set`, :class:`frozenset`, or an instance of a subtype." +"to ``len(anyset)``. Raises a :exc:`SystemError` if *anyset* is not " +"a :class:`set`, :class:`frozenset`, or an instance of a subtype." msgstr "" #: c-api/set.rst:119 @@ -139,9 +136,9 @@ msgid "" "Return ``1`` if found, ``0`` if not found, and ``-1`` if an error is " "encountered. Unlike the Python :meth:`~object.__contains__` method, this " "function does not automatically convert unhashable sets into temporary " -"frozensets. Raise a :exc:`TypeError` if the *key* is unhashable. Raise :exc:" -"`SystemError` if *anyset* is not a :class:`set`, :class:`frozenset`, or an " -"instance of a subtype." +"frozensets. Raise a :exc:`TypeError` if the *key* is unhashable. " +"Raise :exc:`SystemError` if *anyset* is not " +"a :class:`set`, :class:`frozenset`, or an instance of a subtype." msgstr "" #: c-api/set.rst:133 @@ -151,8 +148,8 @@ msgid "" "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." +"grow. Raise a :exc:`SystemError` if *set* is not an instance " +"of :class:`set` or its subtype." msgstr "" #: c-api/set.rst:142 @@ -167,8 +164,9 @@ msgid "" "``-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:`~frozenset.discard` method, this function does not " -"automatically convert unhashable sets into temporary frozensets. Raise :exc:" -"`SystemError` if *set* is not an instance of :class:`set` or its subtype." +"automatically convert unhashable sets into temporary frozensets. " +"Raise :exc:`SystemError` if *set* is not an instance of :class:`set` or its " +"subtype." msgstr "" #: c-api/set.rst:158 @@ -182,8 +180,8 @@ msgstr "" #: c-api/set.rst:166 msgid "" "Empty an existing set of all elements. Return ``0`` on success. Return " -"``-1`` and raise :exc:`SystemError` if *set* is not an instance of :class:" -"`set` or its subtype." +"``-1`` and raise :exc:`SystemError` if *set* is not an instance " +"of :class:`set` or its subtype." msgstr "" #: c-api/set.rst:11 diff --git a/c-api/slice.po b/c-api/slice.po index 67cd8a81a..c93edcac7 100644 --- a/c-api/slice.po +++ b/c-api/slice.po @@ -85,8 +85,8 @@ msgstr "" #: c-api/slice.rst:60 msgid "" "This function is considered not safe for resizable sequences. Its invocation " -"should be replaced by a combination of :c:func:`PySlice_Unpack` and :c:func:" -"`PySlice_AdjustIndices` where ::" +"should be replaced by a combination of :c:func:`PySlice_Unpack` " +"and :c:func:`PySlice_AdjustIndices` where ::" msgstr "" #: c-api/slice.rst:64 @@ -157,9 +157,9 @@ msgstr "" #: c-api/slice.rst:123 msgid "" -"The Python ``Ellipsis`` object. This object has no methods. Like :c:data:" -"`Py_None`, it is an `immortal `_. " -"singleton object." +"The Python ``Ellipsis`` object. This object has no methods. " +"Like :c:data:`Py_None`, it is an `immortal `_. singleton object." msgstr "" #: c-api/slice.rst:127 diff --git a/c-api/stable.po b/c-api/stable.po index 492e001d8..780a77169 100644 --- a/c-api/stable.po +++ b/c-api/stable.po @@ -31,10 +31,10 @@ msgstr "" #: c-api/stable.rst:15 msgid "" "CPython's Application Binary Interface (ABI) is forward- and backwards-" -"compatible across a minor release (if these are compiled the same way; see :" -"ref:`stable-abi-platform` below). So, code compiled for Python 3.10.0 will " -"work on 3.10.8 and vice versa, but will need to be compiled separately for " -"3.9.x and 3.11.x." +"compatible across a minor release (if these are compiled the same way; " +"see :ref:`stable-abi-platform` below). So, code compiled for Python 3.10.0 " +"will work on 3.10.8 and vice versa, but will need to be compiled separately " +"for 3.9.x and 3.11.x." msgstr "" #: c-api/stable.rst:21 @@ -62,9 +62,9 @@ msgstr "" msgid "" "Names prefixed by an underscore, such as ``_Py_InternalState``, are private " "API that can change without notice even in patch releases. If you need to " -"use this API, consider reaching out to `CPython developers `_ to discuss adding public API for your use " -"case." +"use this API, consider reaching out to `CPython developers `_ to discuss adding public API for " +"your use case." msgstr "" #: c-api/stable.rst:40 @@ -161,8 +161,8 @@ msgstr "" #: c-api/stable.rst:103 msgid "" "On Windows, extensions that use the Stable ABI should be linked against " -"``python3.dll`` rather than a version-specific library such as ``python39." -"dll``." +"``python3.dll`` rather than a version-specific library such as " +"``python39.dll``." msgstr "" #: c-api/stable.rst:107 @@ -223,9 +223,10 @@ msgstr "" #: c-api/stable.rst:146 msgid "" "Note that compiling with ``Py_LIMITED_API`` is *not* a complete guarantee " -"that code conforms to the :ref:`Limited API ` or the :ref:" -"`Stable ABI `. ``Py_LIMITED_API`` only covers definitions, but " -"an API also includes other issues, such as expected semantics." +"that code conforms to the :ref:`Limited API ` or " +"the :ref:`Stable ABI `. ``Py_LIMITED_API`` only covers " +"definitions, but an API also includes other issues, such as expected " +"semantics." msgstr "" #: c-api/stable.rst:151 @@ -274,9 +275,9 @@ msgstr "" #: c-api/stable.rst:181 msgid "" "ABI stability depends not only on Python, but also on the compiler used, " -"lower-level libraries and compiler options. For the purposes of the :ref:" -"`Stable ABI `, these details define a “platform”. They usually " -"depend on the OS type and processor architecture" +"lower-level libraries and compiler options. For the purposes of " +"the :ref:`Stable ABI `, these details define a “platform”. They " +"usually depend on the OS type and processor architecture" msgstr "" #: c-api/stable.rst:186 diff --git a/c-api/structures.po b/c-api/structures.po index a9f816dfe..723fa3632 100644 --- a/c-api/structures.po +++ b/c-api/structures.po @@ -55,11 +55,11 @@ msgstr "" #: c-api/structures.rst:38 msgid "" -"This is an extension of :c:type:`PyObject` that adds the :c:member:" -"`~PyVarObject.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`." +"This is an extension of :c:type:`PyObject` that adds " +"the :c:member:`~PyVarObject.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 "" #: c-api/structures.rst:47 @@ -162,8 +162,8 @@ msgstr "" #: c-api/structures.rst:145 msgid "" -"This is a macro which expands to initialization values for a new :c:type:" -"`PyObject` type. This macro expands to::" +"This is a macro which expands to initialization values for a " +"new :c:type:`PyObject` type. This macro expands to::" msgstr "" #: c-api/structures.rst:148 @@ -174,9 +174,9 @@ msgstr "" #: c-api/structures.rst:154 msgid "" -"This is a macro which expands to initialization values for a new :c:type:" -"`PyVarObject` type, including the :c:member:`~PyVarObject.ob_size` field. " -"This macro expands to::" +"This is a macro which expands to initialization values for a " +"new :c:type:`PyVarObject` type, including " +"the :c:member:`~PyVarObject.ob_size` field. This macro expands to::" msgstr "" #: c-api/structures.rst:158 @@ -312,21 +312,22 @@ msgstr "" #: c-api/structures.rst:264 msgid "" -"This is the typical calling convention, where the methods have the type :c:" -"type:`PyCFunction`. The function expects two :c:expr:`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`." +"This is the typical calling convention, where the methods have the " +"type :c:type:`PyCFunction`. The function expects two :c:expr:`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 "" #: c-api/structures.rst:274 msgid "" -"Can only be used in certain combinations with other flags: :ref:" -"`METH_VARARGS | METH_KEYWORDS `, :ref:" -"`METH_FASTCALL | METH_KEYWORDS ` and :ref:" -"`METH_METHOD | METH_FASTCALL | METH_KEYWORDS `." +"Can only be used in certain combinations with other " +"flags: :ref:`METH_VARARGS | METH_KEYWORDS `, :ref:`METH_FASTCALL | METH_KEYWORDS ` and :ref:`METH_METHOD | METH_FASTCALL | METH_KEYWORDS " +"`." msgstr "" #: c-api/structures.rst:282 @@ -407,16 +408,16 @@ msgstr "" #: c-api/structures.rst:350 msgid "" -"The function must have 2 parameters. Since the second parameter is unused, :" -"c:macro:`Py_UNUSED` can be used to prevent a compiler warning." +"The function must have 2 parameters. Since the second parameter is " +"unused, :c:macro:`Py_UNUSED` can be used to prevent a compiler warning." msgstr "" #: c-api/structures.rst:356 msgid "" -"Methods with a single object argument can be listed with the :c:macro:" -"`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:expr:`PyObject*` parameter representing the " +"Methods with a single object argument can be listed with " +"the :c:macro:`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:expr:`PyObject*` parameter representing the " "single argument." msgstr "" @@ -453,12 +454,12 @@ 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:" -"`~object.__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." +"*sq_contains* slot, for example, would generate a wrapped method " +"named :meth:`~object.__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 "" #: c-api/structures.rst:404 @@ -550,18 +551,18 @@ msgstr "" msgid "" "By default (when :c:member:`~PyMemberDef.flags` is ``0``), members allow " "both read and write access. Use the :c:macro:`Py_READONLY` flag for read-" -"only access. Certain types, like :c:macro:`Py_T_STRING`, imply :c:macro:" -"`Py_READONLY`. Only :c:macro:`Py_T_OBJECT_EX` (and legacy :c:macro:" -"`T_OBJECT`) members can be deleted." +"only access. Certain types, like :c:macro:`Py_T_STRING`, " +"imply :c:macro:`Py_READONLY`. Only :c:macro:`Py_T_OBJECT_EX` (and " +"legacy :c:macro:`T_OBJECT`) members can be deleted." msgstr "" #: c-api/structures.rst:484 msgid "" "For heap-allocated types (created using :c:func:`PyType_FromSpec` or " "similar), ``PyMemberDef`` may contain a definition for the special member " -"``\"__vectorcalloffset__\"``, corresponding to :c:member:`~PyTypeObject." -"tp_vectorcall_offset` in type objects. These must be defined with " -"``Py_T_PYSSIZET`` and ``Py_READONLY``, for example::" +"``\"__vectorcalloffset__\"``, corresponding " +"to :c:member:`~PyTypeObject.tp_vectorcall_offset` in type objects. These " +"must be defined with ``Py_T_PYSSIZET`` and ``Py_READONLY``, for example::" msgstr "" #: c-api/structures.rst:490 @@ -579,9 +580,9 @@ msgstr "" #: c-api/structures.rst:498 msgid "" -"The legacy offsets :c:member:`~PyTypeObject.tp_dictoffset` and :c:member:" -"`~PyTypeObject.tp_weaklistoffset` can be defined similarly using " -"``\"__dictoffset__\"`` and ``\"__weaklistoffset__\"`` members, but " +"The legacy offsets :c:member:`~PyTypeObject.tp_dictoffset` " +"and :c:member:`~PyTypeObject.tp_weaklistoffset` can be defined similarly " +"using ``\"__dictoffset__\"`` and ``\"__weaklistoffset__\"`` members, but " "extensions are strongly encouraged to use :c:macro:`Py_TPFLAGS_MANAGED_DICT` " "and :c:macro:`Py_TPFLAGS_MANAGED_WEAKREF` instead." msgstr "" @@ -644,16 +645,18 @@ msgstr "" #: c-api/structures.rst:553 msgid "" -"Can only be used as part of :c:member:`Py_tp_members ` :c:type:`slot ` when creating a class using " -"negative :c:member:`~PyType_Spec.basicsize`. It is mandatory in that case." +"Can only be used as part of :c:member:`Py_tp_members " +"` :c:type:`slot ` when creating a " +"class using negative :c:member:`~PyType_Spec.basicsize`. It is mandatory in " +"that case." msgstr "" #: c-api/structures.rst:558 msgid "" -"This flag is only used in :c:type:`PyType_Slot`. When setting :c:member:" -"`~PyTypeObject.tp_members` during class creation, Python clears it and sets :" -"c:member:`PyMemberDef.offset` to the offset from the ``PyObject`` struct." +"This flag is only used in :c:type:`PyType_Slot`. When " +"setting :c:member:`~PyTypeObject.tp_members` during class creation, Python " +"clears it and sets :c:member:`PyMemberDef.offset` to the offset from the " +"``PyObject`` struct." msgstr "" #: c-api/structures.rst:570 @@ -667,9 +670,9 @@ msgstr "" #: c-api/structures.rst:581 msgid "" -"The :c:macro:`!READONLY` macro was renamed to :c:macro:`Py_READONLY`. The :c:" -"macro:`!PY_AUDIT_READ` macro was renamed with the ``Py_`` prefix. The new " -"names are now always available. Previously, these required ``#include " +"The :c:macro:`!READONLY` macro was renamed to :c:macro:`Py_READONLY`. " +"The :c:macro:`!PY_AUDIT_READ` macro was renamed with the ``Py_`` prefix. The " +"new names are now always available. Previously, these required ``#include " "\"structmember.h\"``. The header is still available and it provides the old " "names." msgstr "" @@ -689,8 +692,8 @@ msgstr "" #: c-api/structures.rst:600 msgid "" -"Unless marked (D), attributes defined this way cannot be deleted using e.g. :" -"keyword:`del` or :py:func:`delattr`." +"Unless marked (D), attributes defined this way cannot be deleted using " +"e.g. :keyword:`del` or :py:func:`delattr`." msgstr "" #: c-api/structures.rst:604 diff --git a/c-api/sys.po b/c-api/sys.po index 5f11b18c9..60123041f 100644 --- a/c-api/sys.po +++ b/c-api/sys.po @@ -22,12 +22,12 @@ msgstr "" #: c-api/sys.rst:11 msgid "" -"Return the file system representation for *path*. If the object is a :class:" -"`str` or :class:`bytes` object, then a new :term:`strong reference` is " -"returned. 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." +"Return the file system representation for *path*. If the object is " +"a :class:`str` or :class:`bytes` object, then a new :term:`strong reference` " +"is returned. 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 "" #: c-api/sys.rst:24 @@ -94,8 +94,8 @@ msgstr "" #: c-api/sys.rst:83 msgid "" ":func:`os.register_at_fork` allows registering custom Python functions to be " -"called by :c:func:`PyOS_BeforeFork()`, :c:func:`PyOS_AfterFork_Parent` and :" -"c:func:`PyOS_AfterFork_Child`." +"called by :c:func:`PyOS_BeforeFork()`, :c:func:`PyOS_AfterFork_Parent` " +"and :c:func:`PyOS_AfterFork_Child`." msgstr "" #: c-api/sys.rst:90 @@ -129,22 +129,22 @@ msgstr "" #: c-api/sys.rst:122 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!" +"handler. This is a thin wrapper around either :c:func:`!sigaction` " +"or :c:func:`!signal`. Do not call those functions directly!" msgstr "" #: c-api/sys.rst:129 msgid "" "This function should not be called directly: use the :c:type:`PyConfig` API " -"with the :c:func:`PyConfig_SetBytesString` function which ensures that :ref:" -"`Python is preinitialized `." +"with the :c:func:`PyConfig_SetBytesString` function which ensures " +"that :ref:`Python is preinitialized `." msgstr "" #: c-api/sys.rst:200 msgid "" "This function must not be called before :ref:`Python is preinitialized ` and so that the LC_CTYPE locale is properly configured: see the :c:" -"func:`Py_PreInitialize` function." +"preinit>` and so that the LC_CTYPE locale is properly configured: see " +"the :c:func:`Py_PreInitialize` function." msgstr "" #: c-api/sys.rst:137 @@ -159,9 +159,10 @@ msgstr "" #: c-api/sys.rst:144 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``" +"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 "" #: c-api/sys.rst:148 @@ -173,9 +174,9 @@ msgstr "" #: c-api/sys.rst:192 msgid "" -"The :term:`filesystem encoding and error handler` are selected by :c:func:" -"`PyConfig_Read`: see :c:member:`~PyConfig.filesystem_encoding` and :c:member:" -"`~PyConfig.filesystem_errors` members of :c:type:`PyConfig`." +"The :term:`filesystem encoding and error handler` are selected " +"by :c:func:`PyConfig_Read`: see :c:member:`~PyConfig.filesystem_encoding` " +"and :c:member:`~PyConfig.filesystem_errors` members of :c:type:`PyConfig`." msgstr "" #: c-api/sys.rst:156 @@ -191,8 +192,8 @@ msgstr "" #: c-api/sys.rst:164 msgid "" -"The :c:func:`PyUnicode_DecodeFSDefaultAndSize` and :c:func:" -"`PyUnicode_DecodeLocaleAndSize` functions." +"The :c:func:`PyUnicode_DecodeFSDefaultAndSize` " +"and :c:func:`PyUnicode_DecodeLocaleAndSize` functions." msgstr "" #: c-api/sys.rst:211 @@ -203,8 +204,8 @@ msgstr "" #: c-api/sys.rst:173 msgid "" -"The function now uses the UTF-8 encoding on Windows if :c:member:" -"`PyPreConfig.legacy_windows_fs_encoding` is zero;" +"The function now uses the UTF-8 encoding on Windows " +"if :c:member:`PyPreConfig.legacy_windows_fs_encoding` is zero;" msgstr "" #: c-api/sys.rst:180 @@ -242,8 +243,8 @@ msgstr "" #: c-api/sys.rst:215 msgid "" -"The function now uses the UTF-8 encoding on Windows if :c:member:" -"`PyPreConfig.legacy_windows_fs_encoding` is zero." +"The function now uses the UTF-8 encoding on Windows " +"if :c:member:`PyPreConfig.legacy_windows_fs_encoding` is zero." msgstr "" #: c-api/sys.rst:223 @@ -279,9 +280,9 @@ msgstr "" #: c-api/sys.rst:258 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"warnoptions` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.warnoptions` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/sys.rst:251 @@ -297,25 +298,25 @@ msgstr "" #: c-api/sys.rst:264 msgid "" "Note: this function is not currently usable from outside the CPython " -"implementation, as it must be called prior to the implicit import of :mod:" -"`warnings` in :c:func:`Py_Initialize` to be effective, but can't be called " -"until enough of the runtime has been initialized to permit the creation of " -"Unicode objects." +"implementation, as it must be called prior to the implicit import " +"of :mod:`warnings` in :c:func:`Py_Initialize` to be effective, but can't be " +"called until enough of the runtime has been initialized to permit the " +"creation of Unicode objects." msgstr "" #: c-api/sys.rst:274 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"module_search_paths` and :c:member:`PyConfig.module_search_paths_set` should " -"be used instead, see :ref:`Python Initialization Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.module_search_paths` " +"and :c:member:`PyConfig.module_search_paths_set` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/sys.rst:279 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)." +"be a list of paths separated with the platform's search path delimiter " +"(``:`` on Unix, ``;`` on Windows)." msgstr "" #: c-api/sys.rst:287 @@ -349,9 +350,9 @@ msgstr "" #: c-api/sys.rst:308 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." +"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 "" #: c-api/sys.rst:316 @@ -362,9 +363,9 @@ msgstr "" #: c-api/sys.rst:323 msgid "" -"This API is kept for backward compatibility: setting :c:member:`PyConfig." -"xoptions` should be used instead, see :ref:`Python Initialization " -"Configuration `." +"This API is kept for backward compatibility: " +"setting :c:member:`PyConfig.xoptions` should be used instead, " +"see :ref:`Python Initialization Configuration `." msgstr "" #: c-api/sys.rst:327 @@ -376,8 +377,9 @@ msgstr "" #: c-api/sys.rst:337 msgid "" -"Return the current dictionary of :option:`-X` options, similarly to :data:" -"`sys._xoptions`. On error, ``NULL`` is returned and an exception is set." +"Return the current dictionary of :option:`-X` options, similarly " +"to :data:`sys._xoptions`. On error, ``NULL`` is returned and an exception " +"is set." msgstr "" #: c-api/sys.rst:346 @@ -399,8 +401,9 @@ msgstr "" #: c-api/sys.rst:357 msgid "" -"Note that ``#`` format characters should always be treated as :c:type:" -"`Py_ssize_t`, regardless of whether ``PY_SSIZE_T_CLEAN`` was defined." +"Note that ``#`` format characters should always be treated " +"as :c:type:`Py_ssize_t`, regardless of whether ``PY_SSIZE_T_CLEAN`` was " +"defined." msgstr "" #: c-api/sys.rst:360 @@ -432,8 +435,8 @@ msgstr "" msgid "" "This function is safe to call before :c:func:`Py_Initialize`. When called " "after runtime initialization, existing audit hooks are notified and may " -"silently abort the operation by raising an error subclassed from :class:" -"`Exception` (other errors will not be silenced)." +"silently abort the operation by raising an error subclassed " +"from :class:`Exception` (other errors will not be silenced)." msgstr "" #: c-api/sys.rst:387 @@ -461,8 +464,9 @@ msgstr "" #: c-api/sys.rst:406 msgid "" "The type of the hook function. *event* is the C string event argument passed " -"to :c:func:`PySys_Audit`. *args* is guaranteed to be a :c:type:" -"`PyTupleObject`. *userData* is the argument passed to PySys_AddAuditHook()." +"to :c:func:`PySys_Audit`. *args* is guaranteed to be " +"a :c:type:`PyTupleObject`. *userData* is the argument passed to " +"PySys_AddAuditHook()." msgstr "" #: c-api/sys.rst:417 @@ -475,8 +479,8 @@ msgid "" "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." +"library function :c:func:`!abort` is called which will attempt to produce " +"a :file:`core` file." msgstr "" #: c-api/sys.rst:431 @@ -493,8 +497,8 @@ msgstr "" #: c-api/sys.rst:445 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." +"the standard C library function ``exit(status)``. " +"If :c:func:`Py_FinalizeEx` indicates an error, the exit status is set to 120." msgstr "" #: c-api/sys.rst:449 diff --git a/c-api/tuple.po b/c-api/tuple.po index 3d8cab8f8..2e135689e 100644 --- a/c-api/tuple.po +++ b/c-api/tuple.po @@ -69,16 +69,16 @@ msgstr "" #: c-api/tuple.rst:61 msgid "" "Return the object at position *pos* in the tuple pointed to by *p*. If " -"*pos* is negative or out of bounds, return ``NULL`` and set an :exc:" -"`IndexError` exception." +"*pos* is negative or out of bounds, return ``NULL`` and set " +"an :exc:`IndexError` exception." msgstr "" #: c-api/tuple.rst:64 msgid "" "The returned reference is borrowed from the tuple *p* (that is: it is only " "valid as long as you hold a reference to *p*). To get a :term:`strong " -"reference`, use :c:func:`Py_NewRef(PyTuple_GetItem(...)) ` or :c:" -"func:`PySequence_GetItem`." +"reference`, use :c:func:`Py_NewRef(PyTuple_GetItem(...)) ` " +"or :c:func:`PySequence_GetItem`." msgstr "" #: c-api/tuple.rst:73 @@ -118,9 +118,10 @@ msgstr "" #: c-api/tuple.rst:104 msgid "" -"This function \"steals\" a reference to *o*, and, unlike :c:func:" -"`PyTuple_SetItem`, does *not* discard a reference to any item that is being " -"replaced; any reference in the tuple at position *pos* will be leaked." +"This function \"steals\" a reference to *o*, and, " +"unlike :c:func:`PyTuple_SetItem`, does *not* discard a reference to any item " +"that is being replaced; any reference in the tuple at position *pos* will be " +"leaked." msgstr "" #: c-api/tuple.rst:112 @@ -134,8 +135,8 @@ msgid "" "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`." +"and sets ``*p`` to ``NULL``, and raises :exc:`MemoryError` " +"or :exc:`SystemError`." msgstr "" #: c-api/tuple.rst:127 @@ -144,17 +145,17 @@ msgstr "" #: c-api/tuple.rst:129 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." +"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 "" #: c-api/tuple.rst:136 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`." +"Instances of the resulting type can be created " +"with :c:func:`PyStructSequence_New`." msgstr "" #: c-api/tuple.rst:208 @@ -196,16 +197,16 @@ msgstr "" #: c-api/tuple.rst:179 msgid "" "Describes a field of a struct sequence. As a struct sequence is modeled as a " -"tuple, all fields are typed as :c:expr:`PyObject*`. The index in the :c:" -"member:`~PyStructSequence_Desc.fields` array of the :c:type:" -"`PyStructSequence_Desc` determines which field of the struct sequence is " -"described." +"tuple, all fields are typed as :c:expr:`PyObject*`. The index in " +"the :c:member:`~PyStructSequence_Desc.fields` array of " +"the :c:type:`PyStructSequence_Desc` determines which field of the struct " +"sequence is described." msgstr "" #: c-api/tuple.rst:187 msgid "" -"Name for the field or ``NULL`` to end the list of named fields, set to :c:" -"data:`PyStructSequence_UnnamedField` to leave unnamed." +"Name for the field or ``NULL`` to end the list of named fields, set " +"to :c:data:`PyStructSequence_UnnamedField` to leave unnamed." msgstr "" #: c-api/tuple.rst:192 @@ -222,8 +223,8 @@ msgstr "" #: c-api/tuple.rst:205 msgid "" -"Creates an instance of *type*, which must have been created with :c:func:" -"`PyStructSequence_NewType`." +"Creates an instance of *type*, which must have been created " +"with :c:func:`PyStructSequence_NewType`." msgstr "" #: c-api/tuple.rst:213 diff --git a/c-api/type.po b/c-api/type.po index e1315de41..5614fd115 100644 --- a/c-api/type.po +++ b/c-api/type.po @@ -26,8 +26,8 @@ msgstr "" #: 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." +"This is the type object for type objects; it is the same object " +"as :class:`type` in the Python layer." msgstr "" #: c-api/type.rst:24 @@ -52,9 +52,9 @@ msgstr "" 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 :ref:`limited " -"API `." +"flag bits are guaranteed to be stable across Python releases, but access " +"to :c:member:`~PyTypeObject.tp_flags` itself is not part of " +"the :ref:`limited API `." msgstr "" #: c-api/type.rst:49 @@ -99,26 +99,26 @@ msgstr "" #: c-api/type.rst:90 msgid "" -"Clear watcher identified by *watcher_id* (previously returned from :c:func:" -"`PyType_AddWatcher`). Return ``0`` on success, ``-1`` on error (e.g. if " -"*watcher_id* was never registered.)" +"Clear watcher identified by *watcher_id* (previously returned " +"from :c:func:`PyType_AddWatcher`). Return ``0`` on success, ``-1`` on error " +"(e.g. if *watcher_id* was never registered.)" msgstr "" #: c-api/type.rst:94 msgid "" "An extension should never call ``PyType_ClearWatcher`` with a *watcher_id* " -"that was not returned to it by a previous call to :c:func:" -"`PyType_AddWatcher`." +"that was not returned to it by a previous call " +"to :c:func:`PyType_AddWatcher`." msgstr "" #: c-api/type.rst:103 msgid "" -"Mark *type* as watched. The callback granted *watcher_id* by :c:func:" -"`PyType_AddWatcher` will be called whenever :c:func:`PyType_Modified` " -"reports a change to *type*. (The callback may be called only once for a " -"series of consecutive modifications to *type*, if :c:func:`!_PyType_Lookup` " -"is not called on *type* between the modifications; this is an implementation " -"detail and subject to change.)" +"Mark *type* as watched. The callback granted *watcher_id* " +"by :c:func:`PyType_AddWatcher` will be called " +"whenever :c:func:`PyType_Modified` reports a change to *type*. (The callback " +"may be called only once for a series of consecutive modifications to *type*, " +"if :c:func:`!_PyType_Lookup` is not called on *type* between the " +"modifications; this is an implementation detail and subject to change.)" msgstr "" #: c-api/type.rst:110 @@ -156,9 +156,10 @@ msgstr "" #: c-api/type.rst:143 msgid "" -"This function only checks for actual subtypes, which means that :meth:`~type." -"__subclasscheck__` is not called on *b*. Call :c:func:`PyObject_IsSubclass` " -"to do the same check that :func:`issubclass` would do." +"This function only checks for actual subtypes, which means " +"that :meth:`~type.__subclasscheck__` is not called on *b*. " +"Call :c:func:`PyObject_IsSubclass` to do the same check " +"that :func:`issubclass` would do." msgstr "" #: c-api/type.rst:151 @@ -171,8 +172,8 @@ msgstr "" #: c-api/type.rst:157 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." +"object. Create a new instance using the " +"type's :c:member:`~PyTypeObject.tp_alloc` slot." msgstr "" #: c-api/type.rst:162 @@ -188,22 +189,22 @@ msgid "" "If some of the base classes implements the GC protocol and the provided type " "does not include the :c:macro:`Py_TPFLAGS_HAVE_GC` in its flags, then the GC " "protocol will be automatically implemented from its parents. On the " -"contrary, if the type being created does include :c:macro:" -"`Py_TPFLAGS_HAVE_GC` in its flags then it **must** implement the GC protocol " -"itself by at least implementing the :c:member:`~PyTypeObject.tp_traverse` " -"handle." +"contrary, if the type being created does " +"include :c:macro:`Py_TPFLAGS_HAVE_GC` in its flags then it **must** " +"implement the GC protocol itself by at least implementing " +"the :c:member:`~PyTypeObject.tp_traverse` handle." msgstr "" #: c-api/type.rst:178 msgid "" -"Return the type's name. Equivalent to getting the type's :attr:`~type." -"__name__` attribute." +"Return the type's name. Equivalent to getting the " +"type's :attr:`~type.__name__` attribute." msgstr "" #: c-api/type.rst:185 msgid "" -"Return the type's qualified name. Equivalent to getting the type's :attr:" -"`~type.__qualname__` attribute." +"Return the type's qualified name. Equivalent to getting the " +"type's :attr:`~type.__qualname__` attribute." msgstr "" #: c-api/type.rst:192 @@ -244,15 +245,15 @@ msgid "" "not return the intended result. ``Py_TYPE(self)`` may be a *subclass* of the " "intended class, and subclasses are not necessarily defined in the same " "module as their superclass. See :c:type:`PyCMethod` to get the class that " -"defines the method. See :c:func:`PyType_GetModuleByDef` for cases when :c:" -"type:`!PyCMethod` cannot be used." +"defines the method. See :c:func:`PyType_GetModuleByDef` for cases " +"when :c:type:`!PyCMethod` cannot be used." msgstr "" #: c-api/type.rst:227 msgid "" "Return the state of the module object associated with the given type. This " -"is a shortcut for calling :c:func:`PyModule_GetState()` on the result of :c:" -"func:`PyType_GetModule`." +"is a shortcut for calling :c:func:`PyModule_GetState()` on the result " +"of :c:func:`PyType_GetModule`." msgstr "" #: c-api/type.rst:234 @@ -263,8 +264,8 @@ msgstr "" #: c-api/type.rst:241 msgid "" -"Find the first superclass whose module was created from the given :c:type:" -"`PyModuleDef` *def*, and return that module." +"Find the first superclass whose module was created from the " +"given :c:type:`PyModuleDef` *def*, and return that module." msgstr "" #: c-api/type.rst:244 @@ -274,11 +275,12 @@ msgstr "" #: c-api/type.rst:246 msgid "" -"This function is intended to be used together with :c:func:" -"`PyModule_GetState()` to get module state from slot methods (such as :c:" -"member:`~PyTypeObject.tp_init` or :c:member:`~PyNumberMethods.nb_add`) and " -"other places where a method's defining class cannot be passed using the :c:" -"type:`PyCMethod` calling convention." +"This function is intended to be used together " +"with :c:func:`PyModule_GetState()` to get module state from slot methods " +"(such as :c:member:`~PyTypeObject.tp_init` " +"or :c:member:`~PyNumberMethods.nb_add`) and other places where a method's " +"defining class cannot be passed using the :c:type:`PyCMethod` calling " +"convention." msgstr "" #: c-api/type.rst:256 @@ -303,8 +305,8 @@ msgstr "" #: c-api/type.rst:272 msgid "" -"Create and return a :ref:`heap type ` from the *spec* (see :c:" -"macro:`Py_TPFLAGS_HEAPTYPE`)." +"Create and return a :ref:`heap type ` from the *spec* " +"(see :c:macro:`Py_TPFLAGS_HEAPTYPE`)." msgstr "" #: c-api/type.rst:275 @@ -336,8 +338,8 @@ msgstr "" msgid "" "The *module* argument can be used to record the module in which the new " "class is defined. It must be a module object or ``NULL``. If not ``NULL``, " -"the module is associated with the new type and can later be retrieved with :" -"c:func:`PyType_GetModule`. The associated module is not inherited by " +"the module is associated with the new type and can later be retrieved " +"with :c:func:`PyType_GetModule`. The associated module is not inherited by " "subclasses; it must be specified for each class individually." msgstr "" @@ -347,10 +349,10 @@ msgstr "" #: c-api/type.rst:301 msgid "" -"Note that this function does *not* fully match the behavior of calling :py:" -"class:`type() ` or using the :keyword:`class` statement. With user-" -"provided base types or metaclasses, prefer :ref:`calling ` :py:" -"class:`type` (or the metaclass) over ``PyType_From*`` functions. " +"Note that this function does *not* fully match the behavior of " +"calling :py:class:`type() ` or using the :keyword:`class` statement. " +"With user-provided base types or metaclasses, prefer :ref:`calling ` :py:class:`type` (or the metaclass) over ``PyType_From*`` functions. " "Specifically:" msgstr "" @@ -421,8 +423,8 @@ msgstr "" #: c-api/type.rst:390 msgid "" -"If positive, specifies the size of the instance in bytes. It is used to set :" -"c:member:`PyTypeObject.tp_basicsize`." +"If positive, specifies the size of the instance in bytes. It is used to " +"set :c:member:`PyTypeObject.tp_basicsize`." msgstr "" #: c-api/type.rst:393 @@ -434,9 +436,9 @@ msgstr "" #: c-api/type.rst:396 msgid "" "If negative, the absolute value specifies how much space instances of the " -"class need *in addition* to the superclass. Use :c:func:" -"`PyObject_GetTypeData` to get a pointer to subclass-specific memory reserved " -"this way." +"class need *in addition* to the superclass. " +"Use :c:func:`PyObject_GetTypeData` to get a pointer to subclass-specific " +"memory reserved this way." msgstr "" #: c-api/type.rst:403 @@ -445,8 +447,9 @@ msgstr "" #: c-api/type.rst:407 msgid "" -"Size of one element of a variable-size type, in bytes. Used to set :c:member:" -"`PyTypeObject.tp_itemsize`. See ``tp_itemsize`` documentation for caveats." +"Size of one element of a variable-size type, in bytes. Used to " +"set :c:member:`PyTypeObject.tp_itemsize`. See ``tp_itemsize`` documentation " +"for caveats." msgstr "" #: c-api/type.rst:411 @@ -485,8 +488,8 @@ msgstr "" #: c-api/type.rst:431 msgid "" -"If the ``Py_TPFLAGS_HEAPTYPE`` flag is not set, :c:func:" -"`PyType_FromSpecWithBases` sets it automatically." +"If the ``Py_TPFLAGS_HEAPTYPE`` flag is not " +"set, :c:func:`PyType_FromSpecWithBases` sets it automatically." msgstr "" #: c-api/type.rst:436 @@ -511,10 +514,9 @@ msgstr "" #: c-api/type.rst:456 msgid "" -"Slot IDs are named like the field names of the structures :c:type:" -"`PyTypeObject`, :c:type:`PyNumberMethods`, :c:type:`PySequenceMethods`, :c:" -"type:`PyMappingMethods` and :c:type:`PyAsyncMethods` with an added ``Py_`` " -"prefix. For example, use:" +"Slot IDs are named like the field names of the " +"structures :c:type:`PyTypeObject`, :c:type:`PyNumberMethods`, :c:type:`PySequenceMethods`, :c:type:`PyMappingMethods` " +"and :c:type:`PyAsyncMethods` with an added ``Py_`` prefix. For example, use:" msgstr "" #: c-api/type.rst:462 @@ -536,14 +538,14 @@ msgstr "" #: c-api/type.rst:468 msgid "" -":c:member:`~PyTypeObject.tp_weaklistoffset` (use :c:macro:" -"`Py_TPFLAGS_MANAGED_WEAKREF` instead if possible)" +":c:member:`~PyTypeObject.tp_weaklistoffset` " +"(use :c:macro:`Py_TPFLAGS_MANAGED_WEAKREF` instead if possible)" msgstr "" #: c-api/type.rst:470 msgid "" -":c:member:`~PyTypeObject.tp_dictoffset` (use :c:macro:" -"`Py_TPFLAGS_MANAGED_DICT` instead if possible)" +":c:member:`~PyTypeObject.tp_dictoffset` " +"(use :c:macro:`Py_TPFLAGS_MANAGED_DICT` instead if possible)" msgstr "" #: c-api/type.rst:472 @@ -555,9 +557,9 @@ msgstr "" #: c-api/type.rst:476 msgid "" "If it is not possible to switch to a ``MANAGED`` flag (for example, for " -"vectorcall or to support Python older than 3.12), specify the offset in :c:" -"member:`Py_tp_members `. See :ref:`PyMemberDef " -"documentation ` for details." +"vectorcall or to support Python older than 3.12), specify the offset " +"in :c:member:`Py_tp_members `. " +"See :ref:`PyMemberDef documentation ` for details." msgstr "" #: c-api/type.rst:482 @@ -566,22 +568,23 @@ msgstr "" #: c-api/type.rst:484 msgid "" -":c:member:`~PyTypeObject.tp_vectorcall` (use :c:member:`~PyTypeObject." -"tp_new` and/or :c:member:`~PyTypeObject.tp_init`)" +":c:member:`~PyTypeObject.tp_vectorcall` " +"(use :c:member:`~PyTypeObject.tp_new` and/" +"or :c:member:`~PyTypeObject.tp_init`)" msgstr "" #: c-api/type.rst:488 msgid "" -"Internal fields: :c:member:`~PyTypeObject.tp_dict`, :c:member:`~PyTypeObject." -"tp_mro`, :c:member:`~PyTypeObject.tp_cache`, :c:member:`~PyTypeObject." -"tp_subclasses`, and :c:member:`~PyTypeObject.tp_weaklist`." +"Internal " +"fields: :c:member:`~PyTypeObject.tp_dict`, :c:member:`~PyTypeObject.tp_mro`, :c:member:`~PyTypeObject.tp_cache`, :c:member:`~PyTypeObject.tp_subclasses`, " +"and :c:member:`~PyTypeObject.tp_weaklist`." msgstr "" #: c-api/type.rst:495 msgid "" "Setting :c:data:`Py_tp_bases` or :c:data:`Py_tp_base` may be problematic on " -"some platforms. To avoid issues, use the *bases* argument of :c:func:" -"`PyType_FromSpecWithBases` instead." +"some platforms. To avoid issues, use the *bases* argument " +"of :c:func:`PyType_FromSpecWithBases` instead." msgstr "" #: c-api/type.rst:502 @@ -590,9 +593,9 @@ msgstr "" #: c-api/type.rst:504 msgid "" -":c:member:`~PyBufferProcs.bf_getbuffer` and :c:member:`~PyBufferProcs." -"bf_releasebuffer` are now available under the :ref:`limited API `." +":c:member:`~PyBufferProcs.bf_getbuffer` " +"and :c:member:`~PyBufferProcs.bf_releasebuffer` are now available under " +"the :ref:`limited API `." msgstr "" #: c-api/type.rst:511 diff --git a/c-api/typehints.po b/c-api/typehints.po index 92fc1bd12..6bff024d9 100644 --- a/c-api/typehints.po +++ b/c-api/typehints.po @@ -32,14 +32,14 @@ msgid "" "Create a :ref:`GenericAlias ` object. Equivalent to " "calling the Python class :class:`types.GenericAlias`. The *origin* and " "*args* arguments set the ``GenericAlias``\\ 's ``__origin__`` and " -"``__args__`` attributes respectively. *origin* should be a :c:expr:" -"`PyTypeObject*`, and *args* can be a :c:expr:`PyTupleObject*` or any " -"``PyObject*``. If *args* passed is not a tuple, a 1-tuple is automatically " -"constructed and ``__args__`` is set to ``(args,)``. Minimal checking is done " -"for the arguments, so the function will succeed even if *origin* is not a " -"type. The ``GenericAlias``\\ 's ``__parameters__`` attribute is constructed " -"lazily from ``__args__``. On failure, an exception is raised and ``NULL`` " -"is returned." +"``__args__`` attributes respectively. *origin* should be " +"a :c:expr:`PyTypeObject*`, and *args* can be a :c:expr:`PyTupleObject*` or " +"any ``PyObject*``. If *args* passed is not a tuple, a 1-tuple is " +"automatically constructed and ``__args__`` is set to ``(args,)``. Minimal " +"checking is done for the arguments, so the function will succeed even if " +"*origin* is not a type. The ``GenericAlias``\\ 's ``__parameters__`` " +"attribute is constructed lazily from ``__args__``. On failure, an exception " +"is raised and ``NULL`` is returned." msgstr "" #: c-api/typehints.rst:28 diff --git a/c-api/typeobj.po b/c-api/typeobj.po index 43276425f..2df46157c 100644 --- a/c-api/typeobj.po +++ b/c-api/typeobj.po @@ -44,8 +44,8 @@ msgstr "" #: c-api/typeobj.rst:23 msgid "" "In addition to the following quick reference, the :ref:`typedef-examples` " -"section provides at-a-glance insight into the meaning and use of :c:type:" -"`PyTypeObject`." +"section provides at-a-glance insight into the meaning and use " +"of :c:type:`PyTypeObject`." msgstr "" #: c-api/typeobj.rst:29 @@ -1116,8 +1116,8 @@ msgstr "" #: c-api/typeobj.rst:475 msgid "" -"The structure definition for :c:type:`PyTypeObject` can be found in :file:" -"`Include/object.h`. For convenience of reference, this repeats the " +"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 "" @@ -1217,11 +1217,12 @@ msgstr "" #: c-api/typeobj.rst:487 msgid "" -"The type object structure extends the :c:type:`PyVarObject` structure. The :" -"c:member:`~PyVarObject.ob_size` field is used for dynamic types (created by :" -"c: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 type object structure extends the :c:type:`PyVarObject` structure. " +"The :c:member:`~PyVarObject.ob_size` field is used for dynamic types " +"(created by :c: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 :c:member:`~PyVarObject.ob_size` field." msgstr "" @@ -1229,10 +1230,10 @@ msgstr "" msgid "" "This is the type object's reference count, initialized to ``1`` by the " "``PyObject_HEAD_INIT`` macro. Note that for :ref:`statically allocated type " -"objects `, the type's instances (objects whose :c:member:" -"`~PyObject.ob_type` points back to the type) do *not* count as references. " -"But for :ref:`dynamically allocated type objects `, the " -"instances *do* count as references." +"objects `, the type's instances (objects " +"whose :c:member:`~PyObject.ob_type` points back to the type) do *not* count " +"as references. But for :ref:`dynamically allocated type objects `, the instances *do* count as references." msgstr "" #: c-api/typeobj.rst:526 c-api/typeobj.rst:562 c-api/typeobj.rst:649 @@ -1271,10 +1272,11 @@ msgstr "" #: c-api/typeobj.rst:521 msgid "" -"This should be done before any instances of the type are created. :c:func:" -"`PyType_Ready` checks if :c:member:`~PyObject.ob_type` is ``NULL``, and if " -"so, initializes it to the :c:member:`~PyObject.ob_type` field of the base " -"class. :c:func:`PyType_Ready` will not change this field if it is non-zero." +"This should be done before any instances of the type are " +"created. :c:func:`PyType_Ready` checks if :c:member:`~PyObject.ob_type` is " +"``NULL``, and if so, initializes it to the :c:member:`~PyObject.ob_type` " +"field of the base class. :c:func:`PyType_Ready` will not change this field " +"if it is non-zero." msgstr "" #: c-api/typeobj.rst:723 c-api/typeobj.rst:932 c-api/typeobj.rst:1629 @@ -1301,8 +1303,8 @@ msgstr "" msgid "" "This could be used for various debugging purposes; currently the only uses " "are the :func:`sys.getobjects` function and to print the objects that are " -"still alive at the end of a run when the environment variable :envvar:" -"`PYTHONDUMPREFS` is set." +"still alive at the end of a run when the environment " +"variable :envvar:`PYTHONDUMPREFS` is set." msgstr "" #: c-api/typeobj.rst:550 @@ -1328,8 +1330,9 @@ msgstr "" msgid "" "Each slot has a section describing inheritance. If :c:func:`PyType_Ready` " "may set a value when the field is set to ``NULL`` then there will also be a " -"\"Default\" section. (Note that many fields set on :c:data:" -"`PyBaseObject_Type` and :c:data:`PyType_Type` effectively act as defaults.)" +"\"Default\" section. (Note that many fields set " +"on :c:data:`PyBaseObject_Type` and :c:data:`PyType_Type` effectively act as " +"defaults.)" msgstr "" #: c-api/typeobj.rst:577 @@ -1339,9 +1342,9 @@ msgid "" "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\"``." +"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 "" #: c-api/typeobj.rst:585 @@ -1362,18 +1365,18 @@ msgstr "" #: c-api/typeobj.rst:596 msgid "" "If no dot is present, the entire :c:member:`~PyTypeObject.tp_name` field is " -"made accessible as the :attr:`~type.__name__` attribute, and the :attr:" -"`~type.__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." +"made accessible as the :attr:`~type.__name__` attribute, and " +"the :attr:`~type.__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 "" #: c-api/typeobj.rst:602 msgid "" -"This field must not be ``NULL``. It is the only required field in :c:func:" -"`PyTypeObject` (other than potentially :c:member:`~PyTypeObject." -"tp_itemsize`)." +"This field must not be ``NULL``. It is the only required field " +"in :c:func:`PyTypeObject` (other than " +"potentially :c:member:`~PyTypeObject.tp_itemsize`)." msgstr "" #: c-api/typeobj.rst:614 @@ -1383,8 +1386,8 @@ msgstr "" #: c-api/typeobj.rst:616 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 " +"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`." @@ -1392,41 +1395,42 @@ msgstr "" #: c-api/typeobj.rst:621 msgid "" -"For a type with variable-length instances, the instances must have an :c:" -"member:`~PyVarObject.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 :c:member:`~PyVarObject.ob_size` field. " -"There are exceptions: for example, ints use a negative :c:member:" -"`~PyVarObject.ob_size` to indicate a negative number, and N is " -"``abs(ob_size)`` there. Also, the presence of an :c:member:`~PyVarObject." -"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 :c:member:" -"`~PyVarObject.ob_size` field)." +"For a type with variable-length instances, the instances must have " +"an :c:member:`~PyVarObject.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 :c:member:`~PyVarObject.ob_size` field. There are exceptions: " +"for example, ints use a negative :c:member:`~PyVarObject.ob_size` to " +"indicate a negative number, and N is ``abs(ob_size)`` there. Also, the " +"presence of an :c:member:`~PyVarObject.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 :c:member:`~PyVarObject.ob_size` field)." msgstr "" #: c-api/typeobj.rst:632 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 :c:member:" -"`~PyObject._ob_prev` and :c:member:`~PyObject._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." +"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 :c:member:`~PyObject._ob_prev` and :c:member:`~PyObject._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 "" #: c-api/typeobj.rst:640 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``)." +"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 "" #: c-api/typeobj.rst:647 @@ -1456,27 +1460,29 @@ msgstr "" #: c-api/typeobj.rst:665 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 " -"call the type's :c:member:`~PyTypeObject.tp_free` function. If the type is " -"not subtypable (doesn't have the :c:macro:`Py_TPFLAGS_BASETYPE` flag bit " -"set), it is permissible to call the object deallocator directly instead of " +"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 call the type's :c:member:`~PyTypeObject.tp_free` " +"function. If the type is not subtypable (doesn't have " +"the :c:macro:`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:macro:`PyObject_New` or :c:macro:" -"`PyObject_NewVar`, or :c:func:`PyObject_GC_Del` if the instance was " -"allocated using :c:macro:`PyObject_GC_New` or :c:macro:`PyObject_GC_NewVar`." +"if the instance was allocated using :c:macro:`PyObject_New` " +"or :c:macro:`PyObject_NewVar`, or :c:func:`PyObject_GC_Del` if the instance " +"was allocated using :c:macro:`PyObject_GC_New` " +"or :c:macro:`PyObject_GC_NewVar`." msgstr "" #: c-api/typeobj.rst:680 msgid "" -"If the type supports garbage collection (has the :c:macro:" -"`Py_TPFLAGS_HAVE_GC` flag bit set), the destructor should call :c:func:" -"`PyObject_GC_UnTrack` before clearing any member fields." +"If the type supports garbage collection (has " +"the :c:macro:`Py_TPFLAGS_HAVE_GC` flag bit set), the destructor should " +"call :c:func:`PyObject_GC_UnTrack` before clearing any member fields." msgstr "" #: c-api/typeobj.rst:684 @@ -1491,9 +1497,9 @@ msgstr "" #: c-api/typeobj.rst:692 msgid "" "Finally, if the type is heap allocated (:c:macro:`Py_TPFLAGS_HEAPTYPE`), the " -"deallocator should release the owned reference to its type object (via :c:" -"func:`Py_DECREF`) after calling the type deallocator. In order to avoid " -"dangling pointers, the recommended way to achieve this is:" +"deallocator should release the owned reference to its type object " +"(via :c:func:`Py_DECREF`) after calling the type deallocator. In order to " +"avoid dangling pointers, the recommended way to achieve this is:" msgstr "" #: c-api/typeobj.rst:698 @@ -1515,8 +1521,9 @@ msgid "" "calls, since the thread on which :c:member:`!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 :c:" -"member:`!tp_dealloc` will not violate any assumptions of the library." +"taken to ensure that destroying those objects on the thread which " +"called :c:member:`!tp_dealloc` will not violate any assumptions of the " +"library." msgstr "" #: c-api/typeobj.rst:728 @@ -1542,10 +1549,10 @@ msgstr "" #: c-api/typeobj.rst:741 msgid "" -"Any class that sets ``Py_TPFLAGS_HAVE_VECTORCALL`` must also set :c:member:" -"`~PyTypeObject.tp_call` and make sure its behaviour is consistent with the " -"*vectorcallfunc* function. This can be done by setting *tp_call* to :c:func:" -"`PyVectorcall_Call`." +"Any class that sets ``Py_TPFLAGS_HAVE_VECTORCALL`` must also " +"set :c:member:`~PyTypeObject.tp_call` and make sure its behaviour is " +"consistent with the *vectorcallfunc* function. This can be done by setting " +"*tp_call* to :c:func:`PyVectorcall_Call`." msgstr "" #: c-api/typeobj.rst:748 @@ -1557,19 +1564,19 @@ msgstr "" #: c-api/typeobj.rst:754 msgid "" "Before version 3.12, it was not recommended for :ref:`mutable heap types " -"` to implement the vectorcall protocol. When a user sets :attr:" -"`~object.__call__` in Python code, only *tp_call* is updated, likely making " -"it inconsistent with the vectorcall function. Since 3.12, setting " -"``__call__`` will disable vectorcall optimization by clearing the :c:macro:" -"`Py_TPFLAGS_HAVE_VECTORCALL` flag." +"` to implement the vectorcall protocol. When a user " +"sets :attr:`~object.__call__` in Python code, only *tp_call* is updated, " +"likely making it inconsistent with the vectorcall function. Since 3.12, " +"setting ``__call__`` will disable vectorcall optimization by clearing " +"the :c:macro:`Py_TPFLAGS_HAVE_VECTORCALL` flag." msgstr "" #: c-api/typeobj.rst:764 msgid "" -"This field is always inherited. However, the :c:macro:" -"`Py_TPFLAGS_HAVE_VECTORCALL` flag is not always inherited. If it's not set, " -"then the subclass won't use :ref:`vectorcall `, except when :c:" -"func:`PyVectorcall_Call` is explicitly called." +"This field is always inherited. However, " +"the :c:macro:`Py_TPFLAGS_HAVE_VECTORCALL` flag is not always inherited. If " +"it's not set, then the subclass won't use :ref:`vectorcall `, " +"except when :c:func:`PyVectorcall_Call` is explicitly called." msgstr "" #: c-api/typeobj.rst:773 @@ -1585,18 +1592,17 @@ msgid "" msgstr "" #: c-api/typeobj.rst:973 -msgid "" -"Group: :c:member:`~PyTypeObject.tp_getattr`, :c:member:`~PyTypeObject." -"tp_getattro`" +msgid "Group: :c:member:`~PyTypeObject.tp_getattr`, :c:member:`~PyTypeObject.tp_getattro`" msgstr "" #: c-api/typeobj.rst:783 msgid "" -"This field is inherited by subtypes together with :c:member:`~PyTypeObject." -"tp_getattro`: a subtype inherits both :c:member:`~PyTypeObject.tp_getattr` " +"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``." +"subtype's :c:member:`~PyTypeObject.tp_getattr` " +"and :c:member:`~PyTypeObject.tp_getattro` are both ``NULL``." msgstr "" #: c-api/typeobj.rst:986 @@ -1613,18 +1619,17 @@ msgid "" msgstr "" #: c-api/typeobj.rst:999 -msgid "" -"Group: :c:member:`~PyTypeObject.tp_setattr`, :c:member:`~PyTypeObject." -"tp_setattro`" +msgid "Group: :c:member:`~PyTypeObject.tp_setattr`, :c:member:`~PyTypeObject.tp_setattro`" msgstr "" #: c-api/typeobj.rst:800 msgid "" -"This field is inherited by subtypes together with :c:member:`~PyTypeObject." -"tp_setattro`: a subtype inherits both :c:member:`~PyTypeObject.tp_setattr` " +"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``." +"subtype's :c:member:`~PyTypeObject.tp_setattr` " +"and :c:member:`~PyTypeObject.tp_setattro` are both ``NULL``." msgstr "" #: c-api/typeobj.rst:807 @@ -1646,8 +1651,8 @@ msgstr "" #: c-api/typeobj.rst:824 msgid "" -"An optional pointer to a function that implements the built-in function :" -"func:`repr`." +"An optional pointer to a function that implements the built-in " +"function :func:`repr`." msgstr "" #: c-api/typeobj.rst:827 @@ -1721,8 +1726,8 @@ msgstr "" #: c-api/typeobj.rst:889 msgid "" -"An optional pointer to a function that implements the built-in function :" -"func:`hash`." +"An optional pointer to a function that implements the built-in " +"function :func:`hash`." msgstr "" #: c-api/typeobj.rst:892 @@ -1743,9 +1748,9 @@ msgstr "" #: c-api/typeobj.rst:900 msgid "" "When this field is not set (*and* :c:member:`~PyTypeObject.tp_richcompare` " -"is not set), an attempt to take the hash of the object raises :exc:" -"`TypeError`. This is the same as setting it to :c:func:" -"`PyObject_HashNotImplemented`." +"is not set), an attempt to take the hash of the object " +"raises :exc:`TypeError`. This is the same as setting it " +"to :c:func:`PyObject_HashNotImplemented`." msgstr "" #: c-api/typeobj.rst:904 @@ -1755,23 +1760,22 @@ msgid "" "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`." +"the Python level will result in the ``tp_hash`` slot being set " +"to :c:func:`PyObject_HashNotImplemented`." msgstr "" #: c-api/typeobj.rst:1568 -msgid "" -"Group: :c:member:`~PyTypeObject.tp_hash`, :c:member:`~PyTypeObject." -"tp_richcompare`" +msgid "Group: :c:member:`~PyTypeObject.tp_hash`, :c:member:`~PyTypeObject.tp_richcompare`" msgstr "" #: c-api/typeobj.rst:916 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``." +"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 "" #: c-api/typeobj.rst:924 @@ -1787,11 +1791,11 @@ msgstr "" #: c-api/typeobj.rst:937 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.)" +"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 "" #: c-api/typeobj.rst:942 @@ -1830,18 +1834,19 @@ msgstr "" #: c-api/typeobj.rst:968 msgid "" -"It is usually convenient to set this field to :c:func:" -"`PyObject_GenericGetAttr`, which implements the normal way of looking for " -"object attributes." +"It is usually convenient to set this field " +"to :c:func:`PyObject_GenericGetAttr`, which implements the normal way of " +"looking for object attributes." msgstr "" #: c-api/typeobj.rst:975 msgid "" -"This field is inherited by subtypes together with :c:member:`~PyTypeObject." -"tp_getattr`: a subtype inherits both :c:member:`~PyTypeObject.tp_getattr` " +"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``." +"subtype's :c:member:`~PyTypeObject.tp_getattr` " +"and :c:member:`~PyTypeObject.tp_getattro` are both ``NULL``." msgstr "" #: c-api/typeobj.rst:981 @@ -1859,18 +1864,19 @@ msgstr "" #: c-api/typeobj.rst:992 msgid "" "In addition, setting *value* 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." +"supported. It is usually convenient to set this field " +"to :c:func:`PyObject_GenericSetAttr`, which implements the normal way of " +"setting object attributes." msgstr "" #: c-api/typeobj.rst:1001 msgid "" -"This field is inherited by subtypes together with :c:member:`~PyTypeObject." -"tp_setattr`: a subtype inherits both :c:member:`~PyTypeObject.tp_setattr` " +"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``." +"subtype's :c:member:`~PyTypeObject.tp_setattr` " +"and :c:member:`~PyTypeObject.tp_setattro` are both ``NULL``." msgstr "" #: c-api/typeobj.rst:1007 @@ -1894,12 +1900,12 @@ msgstr "" 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." +"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 "" #: c-api/typeobj.rst:1034 @@ -1911,11 +1917,11 @@ msgid "" "type's value of the flag bit is copied into the subtype together with a " "pointer to the extension structure. The :c:macro:`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 :c:macro:" -"`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. .. XXX are most flag bits " -"*really* inherited individually?" +"and :c:member:`~PyTypeObject.tp_clear` fields, i.e. if " +"the :c:macro:`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. .. XXX are most flag bits *really* inherited individually?" msgstr "" #: c-api/typeobj.rst:1048 @@ -1931,10 +1937,10 @@ msgstr "" #: c-api/typeobj.rst:1055 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." +"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 "" #: c-api/typeobj.rst:1062 @@ -1945,9 +1951,9 @@ msgid "" "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). Heap types should also :ref:" -"`support garbage collection ` as they can form a " -"reference cycle with their own module object." +"instance's ob_type gets INCREF'ed or DECREF'ed). Heap types should " +"also :ref:`support garbage collection ` as they " +"can form a reference cycle with their own module object." msgstr "" #: c-api/typeobj.rst:1084 c-api/typeobj.rst:1104 c-api/typeobj.rst:1136 @@ -1963,8 +1969,8 @@ msgstr "" #: c-api/typeobj.rst:1089 msgid "" -"This bit is set when the type object has been fully initialized by :c:func:" -"`PyType_Ready`." +"This bit is set when the type object has been fully initialized " +"by :c:func:`PyType_Ready`." msgstr "" #: c-api/typeobj.rst:1099 @@ -1977,26 +1983,25 @@ msgstr "" msgid "" "This bit is set when the object supports garbage collection. If this bit is " "set, instances must be created using :c:macro:`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." +"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 "" #: c-api/typeobj.rst:1439 c-api/typeobj.rst:1507 -msgid "" -"Group: :c:macro:`Py_TPFLAGS_HAVE_GC`, :c:member:`~PyTypeObject." -"tp_traverse`, :c:member:`~PyTypeObject.tp_clear`" +msgid "Group: :c:macro:`Py_TPFLAGS_HAVE_GC`, :c:member:`~PyTypeObject.tp_traverse`, :c:member:`~PyTypeObject.tp_clear`" msgstr "" #: c-api/typeobj.rst:1120 msgid "" -"The :c:macro:`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 :c:macro:`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." +"The :c:macro:`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 :c:macro:`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 "" #: c-api/typeobj.rst:1130 @@ -2028,16 +2033,16 @@ msgstr "" #: c-api/typeobj.rst:1151 msgid "" -"This flag enables an optimization for typical method calls like ``obj." -"meth()``: it avoids creating a temporary \"bound method\" object for ``obj." -"meth``." +"This flag enables an optimization for typical method calls like " +"``obj.meth()``: it avoids creating a temporary \"bound method\" object for " +"``obj.meth``." msgstr "" #: c-api/typeobj.rst:1159 msgid "" -"This flag is never inherited by types without the :c:macro:" -"`Py_TPFLAGS_IMMUTABLETYPE` flag set. For extension types, it is inherited " -"whenever :c:member:`~PyTypeObject.tp_descr_get` is inherited." +"This flag is never inherited by types without " +"the :c:macro:`Py_TPFLAGS_IMMUTABLETYPE` flag set. For extension types, it " +"is inherited whenever :c:member:`~PyTypeObject.tp_descr_get` is inherited." msgstr "" #: c-api/typeobj.rst:1165 @@ -2064,14 +2069,14 @@ msgstr "" #: c-api/typeobj.rst:1187 msgid "" -"This flag is inherited unless the :c:member:`~PyTypeObject." -"tp_weaklistoffset` field is set in a superclass." +"This flag is inherited unless " +"the :c:member:`~PyTypeObject.tp_weaklistoffset` field is set in a superclass." msgstr "" #: c-api/typeobj.rst:1193 msgid "" -"Only usable with variable-size types, i.e. ones with non-zero :c:member:" -"`~PyTypeObject.tp_itemsize`." +"Only usable with variable-size types, i.e. ones with non-" +"zero :c:member:`~PyTypeObject.tp_itemsize`." msgstr "" #: c-api/typeobj.rst:1196 @@ -2096,9 +2101,10 @@ 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." +"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 "" #: c-api/typeobj.rst:1234 @@ -2109,8 +2115,9 @@ msgstr "" #: c-api/typeobj.rst:1239 msgid "" -"This flag isn't necessary anymore, as the interpreter assumes the :c:member:" -"`~PyTypeObject.tp_finalize` slot is always present in the type structure." +"This flag isn't necessary anymore, as the interpreter assumes " +"the :c:member:`~PyTypeObject.tp_finalize` slot is always present in the type " +"structure." msgstr "" #: c-api/typeobj.rst:1247 @@ -2127,8 +2134,8 @@ msgstr "" #: c-api/typeobj.rst:1260 msgid "" -"This flag is now removed from a class when the class's :py:meth:`~object." -"__call__` method is reassigned." +"This flag is now removed from a class when the " +"class's :py:meth:`~object.__call__` method is reassigned." msgstr "" #: c-api/typeobj.rst:1263 @@ -2153,8 +2160,9 @@ msgstr "" #: c-api/typeobj.rst:1280 msgid "" -"Disallow creating instances of the type: set :c:member:`~PyTypeObject." -"tp_new` to NULL and don't create the ``__new__`` key in the type dictionary." +"Disallow creating instances of the type: " +"set :c:member:`~PyTypeObject.tp_new` to NULL and don't create the " +"``__new__`` key in the type dictionary." msgstr "" #: c-api/typeobj.rst:1284 @@ -2165,9 +2173,9 @@ msgstr "" #: c-api/typeobj.rst:1287 msgid "" -"The flag is set automatically on :ref:`static types ` if :c:" -"member:`~PyTypeObject.tp_base` is NULL or ``&PyBaseObject_Type`` and :c:" -"member:`~PyTypeObject.tp_new` is NULL." +"The flag is set automatically on :ref:`static types ` " +"if :c:member:`~PyTypeObject.tp_base` is NULL or ``&PyBaseObject_Type`` " +"and :c:member:`~PyTypeObject.tp_new` is NULL." msgstr "" #: c-api/typeobj.rst:1293 @@ -2200,8 +2208,8 @@ msgstr "" #: c-api/typeobj.rst:1323 msgid "" -"This flag is inherited by types that do not already set :c:macro:" -"`Py_TPFLAGS_SEQUENCE`." +"This flag is inherited by types that do not already " +"set :c:macro:`Py_TPFLAGS_SEQUENCE`." msgstr "" #: c-api/typeobj.rst:1348 @@ -2218,8 +2226,8 @@ msgstr "" #: c-api/typeobj.rst:1345 msgid "" -"This flag is inherited by types that do not already set :c:macro:" -"`Py_TPFLAGS_MAPPING`." +"This flag is inherited by types that do not already " +"set :c:macro:`Py_TPFLAGS_MAPPING`." msgstr "" #: c-api/typeobj.rst:1355 @@ -2265,11 +2273,11 @@ msgstr "" #: c-api/typeobj.rst:1384 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 that the instance " -"owns. For example, this is function :c:func:`!local_traverse` from the :mod:" -"`!_thread` extension module::" +"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 that the instance owns. For example, this is function :c:func:`!" +"local_traverse` from the :mod:`!_thread` extension module::" msgstr "" #: c-api/typeobj.rst:1390 @@ -2314,18 +2322,19 @@ msgstr "" #: c-api/typeobj.rst:1419 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." +"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 "" #: c-api/typeobj.rst:1423 msgid "" "Instances of :ref:`heap-allocated types ` hold a reference to " -"their type. Their traversal function must therefore either visit :c:func:" -"`Py_TYPE(self) `, or delegate this responsibility by calling " -"``tp_traverse`` of another heap-allocated type (such as a heap-allocated " -"superclass). If they do not, the type object may not be garbage-collected." +"their type. Their traversal function must therefore either " +"visit :c:func:`Py_TYPE(self) `, or delegate this responsibility by " +"calling ``tp_traverse`` of another heap-allocated type (such as a heap-" +"allocated superclass). If they do not, the type object may not be garbage-" +"collected." msgstr "" #: c-api/typeobj.rst:1432 @@ -2337,10 +2346,12 @@ msgstr "" #: c-api/typeobj.rst:1441 msgid "" -"This field is inherited by subtypes together with :c:member:`~PyTypeObject." -"tp_clear` and the :c:macro:`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." +"This field is inherited by subtypes together " +"with :c:member:`~PyTypeObject.tp_clear` and " +"the :c:macro:`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 "" #: c-api/typeobj.rst:1449 @@ -2363,10 +2374,11 @@ msgid "" "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`." +"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 "" #: c-api/typeobj.rst:1464 @@ -2393,9 +2405,9 @@ msgstr "" #: c-api/typeobj.rst:1478 msgid "" "The :c:func:`Py_CLEAR` macro should be used, because clearing references is " -"delicate: the reference to the contained object must not be released (via :" -"c:func:`Py_DECREF`) until after the pointer to the contained object is set " -"to ``NULL``. This is because releasing the reference may cause the " +"delicate: the reference to the contained object must not be released " +"(via :c:func:`Py_DECREF`) until after the pointer to the contained object is " +"set to ``NULL``. This is because releasing the reference 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 " @@ -2425,10 +2437,12 @@ msgstr "" #: c-api/typeobj.rst:1509 msgid "" -"This field is inherited by subtypes together with :c:member:`~PyTypeObject." -"tp_traverse` and the :c:macro:`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." +"This field is inherited by subtypes together " +"with :c:member:`~PyTypeObject.tp_traverse` and " +"the :c:macro:`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 "" #: c-api/typeobj.rst:1517 @@ -2456,8 +2470,9 @@ msgstr "" #: c-api/typeobj.rst:1529 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`:" +"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 "" #: c-api/typeobj.rst:1535 @@ -2515,19 +2530,21 @@ msgstr "" #: c-api/typeobj.rst:1570 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``." +"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 "" #: c-api/typeobj.rst:1577 msgid "" -":c:data:`PyBaseObject_Type` provides a :c:member:`~PyTypeObject." -"tp_richcompare` implementation, which may be inherited. However, if only :c:" -"member:`~PyTypeObject.tp_hash` is defined, not even the inherited function " -"is used and instances of the type will not be able to participate in any " -"comparisons." +":c:data:`PyBaseObject_Type` provides " +"a :c:member:`~PyTypeObject.tp_richcompare` implementation, which may be " +"inherited. However, if only :c:member:`~PyTypeObject.tp_hash` is defined, " +"not even the inherited function is used and instances of the type will not " +"be able to participate in any comparisons." msgstr "" #: c-api/typeobj.rst:1586 @@ -2542,8 +2559,8 @@ msgid "" "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 ``PyWeakref_*`` " -"functions. The instance structure needs to include a field of type :c:expr:" -"`PyObject*` which is initialized to ``NULL``." +"functions. The instance structure needs to include a field of " +"type :c:expr:`PyObject*` which is initialized to ``NULL``." msgstr "" #: c-api/typeobj.rst:1596 @@ -2569,17 +2586,18 @@ msgstr "" #: c-api/typeobj.rst:1611 msgid "" -"If the :c:macro:`Py_TPFLAGS_MANAGED_WEAKREF` bit is set in the :c:member:" -"`~PyTypeObject.tp_flags` field, then :c:member:`~PyTypeObject." -"tp_weaklistoffset` will be set to a negative value, to indicate that it is " -"unsafe to use this field." +"If the :c:macro:`Py_TPFLAGS_MANAGED_WEAKREF` bit is set in " +"the :c:member:`~PyTypeObject.tp_flags` field, " +"then :c:member:`~PyTypeObject.tp_weaklistoffset` will be set to a negative " +"value, to indicate that it is unsafe to use this field." msgstr "" #: c-api/typeobj.rst:1619 msgid "" "An optional pointer to a function that returns an :term:`iterator` for the " -"object. Its presence normally signals that the instances of this type are :" -"term:`iterable` (although sequences may be iterable without this function)." +"object. Its presence normally signals that the instances of this type " +"are :term:`iterable` (although sequences may be iterable without this " +"function)." msgstr "" #: c-api/typeobj.rst:1623 @@ -2592,8 +2610,8 @@ msgstr "" #: c-api/typeobj.rst:1634 msgid "" -"An optional pointer to a function that returns the next item in an :term:" -"`iterator`. The signature is::" +"An optional pointer to a function that returns the next item in " +"an :term:`iterator`. The signature is::" msgstr "" #: c-api/typeobj.rst:1637 @@ -2602,10 +2620,10 @@ msgstr "" #: c-api/typeobj.rst:1639 msgid "" -"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." +"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 "" #: c-api/typeobj.rst:1644 @@ -2621,8 +2639,8 @@ msgstr "" #: c-api/typeobj.rst:1657 msgid "" -"An optional pointer to a static ``NULL``-terminated array of :c:type:" -"`PyMethodDef` structures, declaring regular methods of this type." +"An optional pointer to a static ``NULL``-terminated array " +"of :c:type:`PyMethodDef` structures, declaring regular methods of this type." msgstr "" #: c-api/typeobj.rst:1660 @@ -2639,9 +2657,9 @@ msgstr "" #: c-api/typeobj.rst:1671 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." +"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 "" #: c-api/typeobj.rst:1675 @@ -2658,9 +2676,9 @@ msgstr "" #: c-api/typeobj.rst:1686 msgid "" -"An optional pointer to a static ``NULL``-terminated array of :c:type:" -"`PyGetSetDef` structures, declaring computed attributes of instances of this " -"type." +"An optional pointer to a static ``NULL``-terminated array " +"of :c:type:`PyGetSetDef` structures, declaring computed attributes of " +"instances of this type." msgstr "" #: c-api/typeobj.rst:1689 @@ -2693,10 +2711,10 @@ msgstr "" #: c-api/typeobj.rst:1713 msgid "" -"However, the unary '&' operator applied to a non-static variable like :c:" -"data:`PyBaseObject_Type` is not required to produce an address constant. " -"Compilers may support this (gcc does), MSVC does not. Both compilers are " -"strictly standard conforming in this particular behavior." +"However, the unary '&' operator applied to a non-static variable " +"like :c:data:`PyBaseObject_Type` is not required to produce an address " +"constant. Compilers may support this (gcc does), MSVC does not. Both " +"compilers are strictly standard conforming in this particular behavior." msgstr "" #: c-api/typeobj.rst:1719 @@ -2725,22 +2743,23 @@ msgid "" "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:`~object." -"__add__`). Once initialization for the type has finished, this field should " -"be treated as read-only." +"they don't correspond to overloaded operations " +"(like :meth:`~object.__add__`). Once initialization for the type has " +"finished, this field should be treated as read-only." msgstr "" #: c-api/typeobj.rst:1744 msgid "" -"Some types may not store their dictionary in this slot. Use :c:func:" -"`PyType_GetDict` to retrieve the dictionary for an arbitrary type." +"Some types may not store their dictionary in this slot. " +"Use :c:func:`PyType_GetDict` to retrieve the dictionary for an arbitrary " +"type." msgstr "" #: c-api/typeobj.rst:1750 msgid "" "Internals detail: For static builtin types, this is always ``NULL``. " -"Instead, the dict for such types is stored on ``PyInterpreterState``. Use :c:" -"func:`PyType_GetDict` to get the dict for an arbitrary type." +"Instead, the dict for such types is stored on ``PyInterpreterState``. " +"Use :c:func:`PyType_GetDict` to get the dict for an arbitrary type." msgstr "" #: c-api/typeobj.rst:1756 @@ -2757,8 +2776,8 @@ msgstr "" #: c-api/typeobj.rst:1766 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." +"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 "" #: c-api/typeobj.rst:1772 @@ -2797,8 +2816,8 @@ msgstr "" 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`." +"of the type of the instance variable dictionary; this offset is used " +"by :c:func:`PyObject_GenericGetAttr`." msgstr "" #: c-api/typeobj.rst:1813 @@ -2816,10 +2835,11 @@ msgstr "" #: c-api/typeobj.rst:1818 msgid "" "The :c:member:`~PyTypeObject.tp_dictoffset` should be regarded as write-" -"only. To get the pointer to the dictionary call :c:func:" -"`PyObject_GenericGetDict`. Calling :c:func:`PyObject_GenericGetDict` may " -"need to allocate memory for the dictionary, so it is may be more efficient " -"to call :c:func:`PyObject_GetAttr` when accessing an attribute on the object." +"only. To get the pointer to the dictionary " +"call :c:func:`PyObject_GenericGetDict`. " +"Calling :c:func:`PyObject_GenericGetDict` may need to allocate memory for " +"the dictionary, so it is may be more efficient to " +"call :c:func:`PyObject_GetAttr` when accessing an attribute on the object." msgstr "" #: c-api/typeobj.rst:1824 @@ -2832,8 +2852,8 @@ msgstr "" msgid "" "This field is inherited by subtypes. A subtype should not override this " "offset; doing so could be unsafe, if C code tries to access the dictionary " -"at the previous offset. To properly support inheritance, use :c:macro:" -"`Py_TPFLAGS_MANAGED_DICT`." +"at the previous offset. To properly support inheritance, " +"use :c:macro:`Py_TPFLAGS_MANAGED_DICT`." msgstr "" #: c-api/typeobj.rst:1836 @@ -2845,9 +2865,10 @@ msgstr "" #: c-api/typeobj.rst:1839 msgid "" -"If the :c:macro:`Py_TPFLAGS_MANAGED_DICT` bit is set in the :c:member:" -"`~PyTypeObject.tp_dict` field, then :c:member:`~PyTypeObject.tp_dictoffset` " -"will be set to ``-1``, to indicate that it is unsafe to use this field." +"If the :c:macro:`Py_TPFLAGS_MANAGED_DICT` bit is set in " +"the :c:member:`~PyTypeObject.tp_dict` field, " +"then :c:member:`~PyTypeObject.tp_dictoffset` will be set to ``-1``, to " +"indicate that it is unsafe to use this field." msgstr "" #: c-api/typeobj.rst:1847 @@ -2869,20 +2890,20 @@ msgstr "" #: c-api/typeobj.rst:1858 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:" -"`~object.__init__`." +"arguments represent positional and keyword arguments of the call " +"to :meth:`~object.__init__`." msgstr "" #: c-api/typeobj.rst:1862 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." +"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 "" #: c-api/typeobj.rst:1869 @@ -2910,15 +2931,16 @@ msgstr "" #: c-api/typeobj.rst:1895 msgid "" -"For dynamic subtypes, this field is always set to :c:func:" -"`PyType_GenericAlloc`, to force a standard heap allocation strategy." +"For dynamic subtypes, this field is always set " +"to :c:func:`PyType_GenericAlloc`, to force a standard heap allocation " +"strategy." msgstr "" #: c-api/typeobj.rst:1899 msgid "" -"For static subtypes, :c:data:`PyBaseObject_Type` uses :c:func:" -"`PyType_GenericAlloc`. That is the recommended value for all statically " -"defined types." +"For static subtypes, :c:data:`PyBaseObject_Type` " +"uses :c:func:`PyType_GenericAlloc`. That is the recommended value for all " +"statically defined types." msgstr "" #: c-api/typeobj.rst:1906 @@ -2934,9 +2956,9 @@ msgstr "" 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)." +"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 "" #: c-api/typeobj.rst:1918 @@ -2946,9 +2968,9 @@ msgid "" "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`." +"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 "" #: c-api/typeobj.rst:1926 @@ -2959,9 +2981,10 @@ msgstr "" #: c-api/typeobj.rst:1931 msgid "" -"This field is inherited by subtypes, except it is not inherited by :ref:" -"`static types ` whose :c:member:`~PyTypeObject.tp_base` is " -"``NULL`` or ``&PyBaseObject_Type``." +"This field is inherited by subtypes, except it is not inherited " +"by :ref:`static types ` " +"whose :c:member:`~PyTypeObject.tp_base` is ``NULL`` or " +"``&PyBaseObject_Type``." msgstr "" #: c-api/typeobj.rst:1937 @@ -2983,8 +3006,8 @@ msgstr "" #: c-api/typeobj.rst:1949 msgid "" -"An initializer that is compatible with this signature is :c:func:" -"`PyObject_Free`." +"An initializer that is compatible with this signature " +"is :c:func:`PyObject_Free`." msgstr "" #: c-api/typeobj.rst:1953 @@ -2995,9 +3018,9 @@ msgstr "" #: c-api/typeobj.rst:1958 msgid "" -"In dynamic subtypes, this field is set to a deallocator suitable to match :c:" -"func:`PyType_GenericAlloc` and the value of the :c:macro:" -"`Py_TPFLAGS_HAVE_GC` flag bit." +"In dynamic subtypes, this field is set to a deallocator suitable to " +"match :c:func:`PyType_GenericAlloc` and the value of " +"the :c:macro:`Py_TPFLAGS_HAVE_GC` flag bit." msgstr "" #: c-api/typeobj.rst:1962 @@ -3013,12 +3036,12 @@ msgstr "" 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 :c:macro:" -"`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::" +"type's :c:member:`~PyTypeObject.tp_flags` field, and check " +"the :c:macro:`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 "" #: c-api/typeobj.rst:1977 @@ -3027,15 +3050,15 @@ msgstr "" #: c-api/typeobj.rst:1979 msgid "" -"(The only example of this are types themselves. The metatype, :c:data:" -"`PyType_Type`, defines this function to distinguish between statically and :" -"ref:`dynamically allocated types `.)" +"(The only example of this are types themselves. The " +"metatype, :c:data:`PyType_Type`, defines this function to distinguish " +"between statically and :ref:`dynamically allocated types `.)" msgstr "" #: c-api/typeobj.rst:1989 msgid "" -"This slot has no default. If this field is ``NULL``, :c:macro:" -"`Py_TPFLAGS_HAVE_GC` is used as the functional equivalent." +"This slot has no default. If this field is " +"``NULL``, :c:macro:`Py_TPFLAGS_HAVE_GC` is used as the functional equivalent." msgstr "" #: c-api/typeobj.rst:1995 @@ -3051,8 +3074,8 @@ msgstr "" #: c-api/typeobj.rst:2000 msgid "" "For dynamically created classes, the ``Py_tp_bases`` :c:type:`slot " -"` can be used instead of the *bases* argument of :c:func:" -"`PyType_FromSpecWithBases`. The argument form is preferred." +"` can be used instead of the *bases* argument " +"of :c:func:`PyType_FromSpecWithBases`. The argument form is preferred." msgstr "" #: c-api/typeobj.rst:2007 @@ -3074,8 +3097,8 @@ msgstr "" #: c-api/typeobj.rst:2026 msgid "" -"This field is not inherited; it is calculated fresh by :c:func:" -"`PyType_Ready`." +"This field is not inherited; it is calculated fresh " +"by :c:func:`PyType_Ready`." msgstr "" #: c-api/typeobj.rst:2032 @@ -3089,8 +3112,8 @@ msgstr "" #: c-api/typeobj.rst:2043 msgid "" -"To get a list of subclasses, call the Python method :py:meth:`~type." -"__subclasses__`." +"To get a list of subclasses, call the Python " +"method :py:meth:`~type.__subclasses__`." msgstr "" #: c-api/typeobj.rst:2048 @@ -3167,9 +3190,9 @@ msgstr "" #: c-api/typeobj.rst:2125 msgid "" -"Before version 3.8 it was necessary to set the :c:macro:" -"`Py_TPFLAGS_HAVE_FINALIZE` flags bit in order for this field to be used. " -"This is no longer required." +"Before version 3.8 it was necessary to set " +"the :c:macro:`Py_TPFLAGS_HAVE_FINALIZE` flags bit in order for this field to " +"be used. This is no longer required." msgstr "" #: c-api/typeobj.rst:2129 @@ -3180,8 +3203,8 @@ msgstr "" msgid "" "Vectorcall function to use for calls of this type object. In other words, it " "is used to implement :ref:`vectorcall ` for ``type.__call__``. " -"If ``tp_vectorcall`` is ``NULL``, the default call implementation using :" -"meth:`~object.__new__` and :meth:`~object.__init__` is used." +"If ``tp_vectorcall`` is ``NULL``, the default call implementation " +"using :meth:`~object.__new__` and :meth:`~object.__init__` is used." msgstr "" #: c-api/typeobj.rst:2142 @@ -3202,9 +3225,9 @@ msgstr "" #: c-api/typeobj.rst:2159 msgid "" -"Traditionally, types defined in C code are *static*, that is, a static :c:" -"type:`PyTypeObject` structure is defined directly in code and initialized " -"using :c:func:`PyType_Ready`." +"Traditionally, types defined in C code are *static*, that is, a " +"static :c:type:`PyTypeObject` structure is defined directly in code and " +"initialized using :c:func:`PyType_Ready`." msgstr "" #: c-api/typeobj.rst:2163 @@ -3246,15 +3269,15 @@ msgstr "" msgid "" "An alternative to :ref:`static types ` is *heap-allocated " "types*, or *heap types* for short, which correspond closely to classes " -"created by Python's ``class`` statement. Heap types have the :c:macro:" -"`Py_TPFLAGS_HEAPTYPE` flag set." +"created by Python's ``class`` statement. Heap types have " +"the :c:macro:`Py_TPFLAGS_HEAPTYPE` flag set." msgstr "" #: c-api/typeobj.rst:2188 msgid "" -"This is done by filling a :c:type:`PyType_Spec` structure and calling :c:" -"func:`PyType_FromSpec`, :c:func:`PyType_FromSpecWithBases`, :c:func:" -"`PyType_FromModuleAndSpec`, or :c:func:`PyType_FromMetaclass`." +"This is done by filling a :c:type:`PyType_Spec` structure and " +"calling :c:func:`PyType_FromSpec`, :c:func:`PyType_FromSpecWithBases`, :c:func:`PyType_FromModuleAndSpec`, " +"or :c:func:`PyType_FromMetaclass`." msgstr "" #: c-api/typeobj.rst:2196 @@ -3347,24 +3370,25 @@ msgstr "" #: c-api/typeobj.rst:2322 msgid "" -"This function is used by :c:func:`PyMapping_Size` and :c:func:" -"`PyObject_Size`, and has the same signature. This slot may be set to " -"``NULL`` if the object has no defined length." +"This function is used by :c:func:`PyMapping_Size` " +"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 "" #: c-api/typeobj.rst:2328 msgid "" -"This function is used by :c:func:`PyObject_GetItem` and :c:func:" -"`PySequence_GetSlice`, and has the same signature as :c:func:`!" -"PyObject_GetItem`. This slot must be filled for the :c:func:" -"`PyMapping_Check` function to return ``1``, it can be ``NULL`` otherwise." +"This function is used by :c:func:`PyObject_GetItem` " +"and :c:func:`PySequence_GetSlice`, and has the same signature as :c:func:`!" +"PyObject_GetItem`. This slot must be filled for " +"the :c:func:`PyMapping_Check` function to return ``1``, it can be ``NULL`` " +"otherwise." msgstr "" #: c-api/typeobj.rst:2336 msgid "" -"This function is used by :c:func:`PyObject_SetItem`, :c:func:" -"`PyObject_DelItem`, :c:func:`PySequence_SetSlice` and :c:func:" -"`PySequence_DelSlice`. It has the same signature as :c:func:`!" +"This function is used " +"by :c:func:`PyObject_SetItem`, :c:func:`PyObject_DelItem`, :c:func:`PySequence_SetSlice` " +"and :c:func:`PySequence_DelSlice`. 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." @@ -3382,10 +3406,10 @@ msgstr "" #: c-api/typeobj.rst:2359 msgid "" -"This function is used by :c:func:`PySequence_Size` and :c:func:" -"`PyObject_Size`, and has the same signature. It is also used for handling " -"negative indices via the :c:member:`~PySequenceMethods.sq_item` and the :c:" -"member:`~PySequenceMethods.sq_ass_item` slots." +"This function is used by :c:func:`PySequence_Size` " +"and :c:func:`PyObject_Size`, and has the same signature. It is also used " +"for handling negative indices via the :c:member:`~PySequenceMethods.sq_item` " +"and the :c:member:`~PySequenceMethods.sq_ass_item` slots." msgstr "" #: c-api/typeobj.rst:2366 @@ -3413,20 +3437,21 @@ msgstr "" #: c-api/typeobj.rst:2384 msgid "" -"Negative indexes are handled as follows: if the :c:member:" -"`~PySequenceMethods.sq_length` slot is filled, it is called and the sequence " -"length is used to compute a positive index which is passed to :c:member:" -"`~PySequenceMethods.sq_item`. If :c:member:`!sq_length` is ``NULL``, the " -"index is passed as is to the function." +"Negative indexes are handled as follows: if " +"the :c:member:`~PySequenceMethods.sq_length` slot is filled, it is called " +"and the sequence length is used to compute a positive index which is passed " +"to :c:member:`~PySequenceMethods.sq_item`. If :c:member:`!sq_length` is " +"``NULL``, the index is passed as is to the function." msgstr "" #: c-api/typeobj.rst:2391 msgid "" "This function is used by :c:func:`PySequence_SetItem` and has the same " -"signature. It is also used by :c:func:`PyObject_SetItem` and :c:func:" -"`PyObject_DelItem`, after trying the item assignment and deletion via the :c:" -"member:`~PyMappingMethods.mp_ass_subscript` slot. This slot may be left to " -"``NULL`` if the object does not support item assignment and deletion." +"signature. It is also used by :c:func:`PyObject_SetItem` " +"and :c:func:`PyObject_DelItem`, after trying the item assignment and " +"deletion via the :c:member:`~PyMappingMethods.mp_ass_subscript` slot. This " +"slot may be left to ``NULL`` if the object does not support item assignment " +"and deletion." msgstr "" #: c-api/typeobj.rst:2400 @@ -3442,8 +3467,8 @@ msgid "" "signature. It should modify its first operand, and return it. This slot " "may be left to ``NULL``, in this case :c:func:`!PySequence_InPlaceConcat` " "will fall back to :c:func:`PySequence_Concat`. It is also used by the " -"augmented assignment ``+=``, after trying numeric in-place addition via the :" -"c:member:`~PyNumberMethods.nb_inplace_add` slot." +"augmented assignment ``+=``, after trying numeric in-place addition via " +"the :c:member:`~PyNumberMethods.nb_inplace_add` slot." msgstr "" #: c-api/typeobj.rst:2416 @@ -3484,8 +3509,8 @@ msgstr "" #: c-api/typeobj.rst:2449 msgid "" -"Check if the request can be met. If not, raise :exc:`BufferError`, set :c:" -"expr:`view->obj` to ``NULL`` and return ``-1``." +"Check if the request can be met. If not, raise :exc:`BufferError`, " +"set :c:expr:`view->obj` to ``NULL`` and return ``-1``." msgstr "" #: c-api/typeobj.rst:2452 @@ -3513,8 +3538,8 @@ msgstr "" #: c-api/typeobj.rst:2463 msgid "" -"Re-export: Each member of the tree acts as the exporting object and sets :c:" -"expr:`view->obj` to a new reference to itself." +"Re-export: Each member of the tree acts as the exporting object and " +"sets :c:expr:`view->obj` to a new reference to itself." msgstr "" #: c-api/typeobj.rst:2466 @@ -3534,10 +3559,9 @@ msgstr "" #: c-api/typeobj.rst:2475 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." +"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 "" #: c-api/typeobj.rst:2482 @@ -3599,8 +3623,8 @@ msgstr "" #: c-api/typeobj.rst:2530 msgid "" -"This structure holds pointers to the functions required to implement :term:" -"`awaitable` and :term:`asynchronous iterator` objects." +"This structure holds pointers to the functions required to " +"implement :term:`awaitable` and :term:`asynchronous iterator` objects." msgstr "" #: c-api/typeobj.rst:2535 @@ -3634,8 +3658,8 @@ msgstr "" #: c-api/typeobj.rst:2559 msgid "" -"Must return an :term:`asynchronous iterator` object. See :meth:`~object." -"__anext__` for details." +"Must return an :term:`asynchronous iterator` object. " +"See :meth:`~object.__anext__` for details." msgstr "" #: c-api/typeobj.rst:2562 @@ -3672,20 +3696,21 @@ 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 :c:member:`~PyObject.ob_refcnt` set to ``1`` and :c:member:`~PyObject." -"ob_type` set to the type argument. If the type's :c:member:`~PyTypeObject." -"tp_itemsize` is non-zero, the object's :c:member:`~PyVarObject.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`." +"with :c:member:`~PyObject.ob_refcnt` set to ``1`` " +"and :c:member:`~PyObject.ob_type` set to the type argument. If the " +"type's :c:member:`~PyTypeObject.tp_itemsize` is non-zero, the " +"object's :c:member:`~PyVarObject.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 "" #: c-api/typeobj.rst:2604 msgid "" "This function should not do any other instance initialization, not even to " -"allocate additional memory; that should be done by :c:member:`~PyTypeObject." -"tp_new`." +"allocate additional memory; that should be done " +"by :c:member:`~PyTypeObject.tp_new`." msgstr "" #: c-api/typeobj.rst:2611 @@ -3867,8 +3892,8 @@ msgstr "" #: c-api/typeobj.rst:2792 msgid "" "A str subclass that cannot be subclassed and cannot be called to create " -"instances (e.g. uses a separate factory func) using :c:macro:" -"`Py_TPFLAGS_DISALLOW_INSTANTIATION` flag::" +"instances (e.g. uses a separate factory func) " +"using :c:macro:`Py_TPFLAGS_DISALLOW_INSTANTIATION` flag::" msgstr "" #: c-api/typeobj.rst:2796 diff --git a/c-api/unicode.po b/c-api/unicode.po index 3b5a166f0..f55fa16b2 100644 --- a/c-api/unicode.po +++ b/c-api/unicode.po @@ -124,8 +124,8 @@ msgstr "" 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 function." +"canonical representation has the correct character size; " +"use :c:func:`PyUnicode_KIND` to select the right function." msgstr "" #: c-api/unicode.rst:122 @@ -152,25 +152,25 @@ msgstr "" #: c-api/unicode.rst:150 msgid "" -"Write into a canonical representation *data* (as obtained with :c:func:" -"`PyUnicode_DATA`). This function performs no sanity checks, and is intended " -"for usage in loops. The caller should cache the *kind* value and *data* " -"pointer as obtained from other 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." +"Write into a canonical representation *data* (as obtained " +"with :c:func:`PyUnicode_DATA`). This function performs no sanity checks, " +"and is intended for usage in loops. The caller should cache the *kind* " +"value and *data* pointer as obtained from other 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 "" #: c-api/unicode.rst:163 msgid "" -"Read a code point from a canonical representation *data* (as obtained with :" -"c:func:`PyUnicode_DATA`). No checks or ready calls are performed." +"Read a code point from a canonical representation *data* (as obtained " +"with :c:func:`PyUnicode_DATA`). No checks or ready calls are performed." msgstr "" #: c-api/unicode.rst:171 msgid "" "Read a character from a Unicode object *unicode*, which must be in the " -"\"canonical\" representation. This is less efficient than :c:func:" -"`PyUnicode_READ` if you do multiple consecutive reads." +"\"canonical\" representation. This is less efficient " +"than :c:func:`PyUnicode_READ` if you do multiple consecutive reads." msgstr "" #: c-api/unicode.rst:180 @@ -352,18 +352,19 @@ msgstr "" #: c-api/unicode.rst:356 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." +"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 "" #: c-api/unicode.rst:361 msgid "" "If necessary, the input *buffer* is copied and transformed into the " -"canonical representation. For example, if the *buffer* is a UCS4 string (:c:" -"macro:`PyUnicode_4BYTE_KIND`) and it consists only of codepoints in the UCS1 " -"range, it will be transformed into UCS1 (:c:macro:`PyUnicode_1BYTE_KIND`)." +"canonical representation. For example, if the *buffer* is a UCS4 string " +"(:c:macro:`PyUnicode_4BYTE_KIND`) and it consists only of codepoints in the " +"UCS1 range, it will be transformed into UCS1 " +"(:c:macro:`PyUnicode_1BYTE_KIND`)." msgstr "" #: c-api/unicode.rst:372 @@ -424,9 +425,9 @@ msgstr "" #: c-api/unicode.rst:409 msgid "" "Minimum field width (optional). If specified as an ``'*'`` (asterisk), the " -"actual width is given in the next argument, which must be of type :c:expr:" -"`int`, and the object to convert comes after the minimum field width and " -"optional precision." +"actual width is given in the next argument, which must be of " +"type :c:expr:`int`, and the object to convert comes after the minimum field " +"width and optional precision." msgstr "" #: c-api/unicode.rst:414 @@ -805,8 +806,8 @@ msgstr "" #: c-api/unicode.rst:625 msgid "" -"Fill a string with a character: write *fill_char* into ``unicode[start:" -"start+length]``." +"Fill a string with a character: write *fill_char* into " +"``unicode[start:start+length]``." msgstr "" #: c-api/unicode.rst:628 @@ -823,9 +824,9 @@ msgstr "" #: c-api/unicode.rst:640 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." +"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 "" #: c-api/unicode.rst:644 @@ -842,8 +843,8 @@ msgstr "" #: c-api/unicode.rst:655 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 :c:func:" -"`PyUnicode_READ_CHAR`, which performs no error checking." +"Unicode object and the index is not out of bounds, in contrast " +"to :c:func:`PyUnicode_READ_CHAR`, which performs no error checking." msgstr "" #: c-api/unicode.rst:659 @@ -867,10 +868,10 @@ msgstr "" #: c-api/unicode.rst:687 msgid "" -"Copy the string *unicode* 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." +"Copy the string *unicode* 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 "" #: c-api/unicode.rst:696 @@ -894,8 +895,8 @@ msgstr "" #: c-api/unicode.rst:712 msgid "" -"Use :c:func:`PyUnicode_DecodeFSDefaultAndSize` to decode a string from the :" -"term:`filesystem encoding and error handler`." +"Use :c:func:`PyUnicode_DecodeFSDefaultAndSize` to decode a string from " +"the :term:`filesystem encoding and error handler`." msgstr "" #: c-api/unicode.rst:750 @@ -909,9 +910,9 @@ msgstr "" #: c-api/unicode.rst:723 msgid "" "The function now also uses the current locale encoding for the " -"``surrogateescape`` error handler, except on Android. Previously, :c:func:" -"`Py_DecodeLocale` was used for the ``surrogateescape``, and the current " -"locale encoding was used for ``strict``." +"``surrogateescape`` error handler, except on Android. " +"Previously, :c:func:`Py_DecodeLocale` was used for the ``surrogateescape``, " +"and the current locale encoding was used for ``strict``." msgstr "" #: c-api/unicode.rst:732 @@ -925,14 +926,14 @@ msgid "" "Encode a Unicode object to UTF-8 on Android and VxWorks, or to the current " "locale encoding on other platforms. 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." +"``\"strict\"`` error handler if *errors* is ``NULL``. Return " +"a :class:`bytes` object. *unicode* cannot contain embedded null characters." msgstr "" #: c-api/unicode.rst:747 msgid "" -"Use :c:func:`PyUnicode_EncodeFSDefault` to encode a string to the :term:" -"`filesystem encoding and error handler`." +"Use :c:func:`PyUnicode_EncodeFSDefault` to encode a string to " +"the :term:`filesystem encoding and error handler`." msgstr "" #: c-api/unicode.rst:847 @@ -942,9 +943,9 @@ msgstr "" #: c-api/unicode.rst:758 msgid "" "The function now also uses the current locale encoding for the " -"``surrogateescape`` error handler, except on Android. Previously, :c:func:" -"`Py_EncodeLocale` was used for the ``surrogateescape``, and the current " -"locale encoding was used for ``strict``." +"``surrogateescape`` error handler, except on Android. " +"Previously, :c:func:`Py_EncodeLocale` was used for the ``surrogateescape``, " +"and the current locale encoding was used for ``strict``." msgstr "" #: c-api/unicode.rst:767 @@ -967,10 +968,10 @@ msgstr "" #: c-api/unicode.rst:778 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:expr:`PyBytesObject*` which must be released when it " -"is no longer used." +"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:expr:`PyBytesObject*` which must be released " +"when it is no longer used." msgstr "" #: c-api/unicode.rst:803 @@ -987,10 +988,11 @@ msgstr "" #: c-api/unicode.rst:795 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:expr:`PyUnicodeObject*` " -"which must be released when it is no longer used." +"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:expr:`PyUnicodeObject*` which must be " +"released when it is no longer used." msgstr "" #: c-api/unicode.rst:809 @@ -999,8 +1001,8 @@ msgstr "" #: c-api/unicode.rst:811 msgid "" -"If you need to decode a string from the current locale encoding, use :c:func:" -"`PyUnicode_DecodeLocaleAndSize`." +"If you need to decode a string from the current locale encoding, " +"use :c:func:`PyUnicode_DecodeLocaleAndSize`." msgstr "" #: c-api/unicode.rst:831 c-api/unicode.rst:851 @@ -1017,8 +1019,8 @@ msgstr "" #: c-api/unicode.rst:828 msgid "" -"If the string length is known, use :c:func:" -"`PyUnicode_DecodeFSDefaultAndSize`." +"If the string length is known, " +"use :c:func:`PyUnicode_DecodeFSDefaultAndSize`." msgstr "" #: c-api/unicode.rst:838 @@ -1030,8 +1032,8 @@ msgstr "" #: c-api/unicode.rst:842 msgid "" -"If you need to encode a string to the current locale encoding, use :c:func:" -"`PyUnicode_EncodeLocale`." +"If you need to encode a string to the current locale encoding, " +"use :c:func:`PyUnicode_EncodeLocale`." msgstr "" #: c-api/unicode.rst:856 @@ -1054,8 +1056,8 @@ msgstr "" msgid "" "Copy the Unicode object contents into the :c:type:`wchar_t` buffer *wstr*. " "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." +"trailing null termination character). Return the number " +"of :c:type:`wchar_t` characters copied or ``-1`` in case of an error." msgstr "" #: c-api/unicode.rst:875 @@ -1067,9 +1069,9 @@ msgstr "" #: c-api/unicode.rst:878 msgid "" "Note that the resulting :c:expr:`wchar_t*` string may or may not be null-" -"terminated. It is the responsibility of the caller to make sure that the :c:" -"expr:`wchar_t*` string is null-terminated in case this is required by the " -"application. Also, note that the :c:expr:`wchar_t*` string might contain " +"terminated. It is the responsibility of the caller to make sure that " +"the :c:expr:`wchar_t*` string is null-terminated in case this is required by " +"the application. Also, note that the :c:expr:`wchar_t*` string might contain " "null characters, which would cause the string to be truncated when used with " "most C functions." msgstr "" @@ -1081,8 +1083,9 @@ msgid "" "number of wide characters (excluding the trailing null termination " "character) into *\\*size*. 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. If *size* is ``NULL`` and the :c:expr:" -"`wchar_t*` string contains null characters a :exc:`ValueError` is raised." +"when used with most C functions. If *size* is ``NULL`` and " +"the :c:expr:`wchar_t*` string contains null characters a :exc:`ValueError` " +"is raised." msgstr "" #: c-api/unicode.rst:896 @@ -1568,8 +1571,8 @@ msgstr "" #: c-api/unicode.rst:1314 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:macro:`!CP_ACP` code page to get the MBCS encoder." +"bytes object. Return ``NULL`` if an exception was raised by the codec. " +"Use :c:macro:`!CP_ACP` code page to get the MBCS encoder." msgstr "" #: c-api/unicode.rst:1322 @@ -1669,8 +1672,8 @@ msgstr "" #: c-api/unicode.rst:1416 msgid "" -"This function returns ``-1`` upon failure, so one should call :c:func:" -"`PyErr_Occurred` to check for errors." +"This function returns ``-1`` upon failure, so one should " +"call :c:func:`PyErr_Occurred` to check for errors." msgstr "" #: c-api/unicode.rst:1422 @@ -1703,8 +1706,9 @@ msgstr "" #: c-api/unicode.rst:1438 msgid "" -"Possible values for *op* are :c:macro:`Py_GT`, :c:macro:`Py_GE`, :c:macro:" -"`Py_EQ`, :c:macro:`Py_NE`, :c:macro:`Py_LT`, and :c:macro:`Py_LE`." +"Possible values for *op* " +"are :c:macro:`Py_GT`, :c:macro:`Py_GE`, :c:macro:`Py_EQ`, :c:macro:`Py_NE`, :c:macro:`Py_LT`, " +"and :c:macro:`Py_LE`." msgstr "" #: c-api/unicode.rst:1444 @@ -1729,11 +1733,11 @@ msgstr "" msgid "" "Intern the argument :c:expr:`*p_unicode` 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 :c:expr:" -"`*p_unicode`, it sets :c:expr:`*p_unicode` to it (releasing the reference to " -"the old string object and creating a new :term:`strong reference` to the " -"interned string object), otherwise it leaves :c:expr:`*p_unicode` alone and " -"interns it." +"If there is an existing interned string that is the same " +"as :c:expr:`*p_unicode`, it sets :c:expr:`*p_unicode` to it (releasing the " +"reference to the old string object and creating a new :term:`strong " +"reference` to the interned string object), otherwise it " +"leaves :c:expr:`*p_unicode` alone and interns it." msgstr "" #: c-api/unicode.rst:1466 @@ -1752,9 +1756,9 @@ msgstr "" #: c-api/unicode.rst:1474 msgid "" -"Instances of subclasses of :py:class:`str` may not be interned, that is, :c:" -"expr:`PyUnicode_CheckExact(*p_unicode)` must be true. If it is not, then -- " -"as with any other error -- the argument is left unchanged." +"Instances of subclasses of :py:class:`str` may not be interned, that " +"is, :c:expr:`PyUnicode_CheckExact(*p_unicode)` must be true. If it is not, " +"then -- as with any other error -- the argument is left unchanged." msgstr "" #: c-api/unicode.rst:1478 @@ -1765,8 +1769,9 @@ msgstr "" #: c-api/unicode.rst:1484 msgid "" -"A combination of :c:func:`PyUnicode_FromString` and :c:func:" -"`PyUnicode_InternInPlace`, meant for statically allocated strings." +"A combination of :c:func:`PyUnicode_FromString` " +"and :c:func:`PyUnicode_InternInPlace`, meant for statically allocated " +"strings." msgstr "" #: c-api/unicode.rst:1487 @@ -1780,6 +1785,7 @@ msgstr "" msgid "" "Python may keep a reference to the result, or prevent it from being garbage-" "collected promptly. For interning an unbounded number of different strings, " -"such as ones coming from user input, prefer calling :c:func:" -"`PyUnicode_FromString` and :c:func:`PyUnicode_InternInPlace` directly." +"such as ones coming from user input, prefer " +"calling :c:func:`PyUnicode_FromString` and :c:func:`PyUnicode_InternInPlace` " +"directly." msgstr "" diff --git a/c-api/veryhigh.po b/c-api/veryhigh.po index e6ea5d7a1..34f6990cd 100644 --- a/c-api/veryhigh.po +++ b/c-api/veryhigh.po @@ -30,16 +30,17 @@ msgstr "" #: 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 :c:data:`Py_eval_input`, :c:data:" -"`Py_file_input`, and :c:data:`Py_single_input`. These are described " -"following the functions which accept them as parameters." +"parameter. The available start symbols " +"are :c:data:`Py_eval_input`, :c:data:`Py_file_input`, " +"and :c:data:`Py_single_input`. These are described following the functions " +"which accept them as parameters." msgstr "" #: c-api/veryhigh.rst:19 msgid "" "Note also that several of these functions take :c:expr:`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 " +"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:expr:`FILE*` parameters are only passed to these functions if " @@ -63,8 +64,8 @@ msgstr "" #: 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 :c:member:" -"`PyConfig.inspect` is zero." +"function will not return ``1``, but exit the process, as long " +"as :c:member:`PyConfig.inspect` is zero." msgstr "" #: c-api/veryhigh.rst:47 @@ -92,12 +93,12 @@ msgstr "" #: c-api/veryhigh.rst:72 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. If *closeit* is true, the file is closed " -"before ``PyRun_SimpleFileExFlags()`` returns." +"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. If *closeit* is true, the " +"file is closed before ``PyRun_SimpleFileExFlags()`` returns." msgstr "" #: c-api/veryhigh.rst:84 @@ -118,8 +119,8 @@ msgstr "" #: c-api/veryhigh.rst:96 msgid "" "Note that if an otherwise unhandled :exc:`SystemExit` is raised, this " -"function will not return ``-1``, but exit the process, as long as :c:member:" -"`PyConfig.inspect` is zero." +"function will not return ``-1``, but exit the process, as long " +"as :c:member:`PyConfig.inspect` is zero." msgstr "" #: c-api/veryhigh.rst:103 @@ -160,17 +161,17 @@ msgstr "" 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 :" -"term:`filesystem encoding and error handler`." +"prompted using ``sys.ps1`` and ``sys.ps2``. *filename* is decoded from " +"the :term:`filesystem encoding and error handler`." msgstr "" #: c-api/veryhigh.rst:139 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.)" +"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 "" #: c-api/veryhigh.rst:148 @@ -216,15 +217,15 @@ msgstr "" #: c-api/veryhigh.rst:186 msgid "" -"The result must be a string allocated by :c:func:`PyMem_RawMalloc` or :c:" -"func:`PyMem_RawRealloc`, or ``NULL`` if an error occurred." +"The result must be a string allocated by :c:func:`PyMem_RawMalloc` " +"or :c:func:`PyMem_RawRealloc`, or ``NULL`` if an error occurred." msgstr "" #: c-api/veryhigh.rst:189 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`." +"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 "" #: c-api/veryhigh.rst:200 @@ -271,8 +272,8 @@ 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 :term:`filesystem encoding and error " -"handler`. If *closeit* is true, the file is closed before :c:func:" -"`PyRun_FileExFlags` returns." +"handler`. If *closeit* is true, the file is closed " +"before :c:func:`PyRun_FileExFlags` returns." msgstr "" #: c-api/veryhigh.rst:245 @@ -291,11 +292,12 @@ msgstr "" 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 :c:data:" -"`Py_eval_input`, :c:data:`Py_file_input`, or :c:data:`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." +"constrain the code which can be compiled and should " +"be :c:data:`Py_eval_input`, :c:data:`Py_file_input`, " +"or :c:data:`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 "" #: c-api/veryhigh.rst:265 @@ -331,8 +333,8 @@ msgstr "" #: c-api/veryhigh.rst:299 msgid "" -"Evaluate an execution frame. This is a simplified interface to :c:func:" -"`PyEval_EvalFrameEx`, for backward compatibility." +"Evaluate an execution frame. This is a simplified interface " +"to :c:func:`PyEval_EvalFrameEx`, for backward compatibility." msgstr "" #: c-api/veryhigh.rst:305 @@ -387,9 +389,9 @@ msgstr "" #: c-api/veryhigh.rst:356 msgid "" -"Whenever ``PyCompilerFlags *flags`` is ``NULL``, :c:member:`~PyCompilerFlags." -"cf_flags` is treated as equal to ``0``, and any modification due to ``from " -"__future__ import`` is discarded." +"Whenever ``PyCompilerFlags *flags`` is " +"``NULL``, :c:member:`~PyCompilerFlags.cf_flags` is treated as equal to " +"``0``, and any modification due to ``from __future__ import`` is discarded." msgstr "" #: c-api/veryhigh.rst:362 diff --git a/deprecations/c-api-pending-removal-in-3.14.po b/deprecations/c-api-pending-removal-in-3.14.po index 7e0454485..59af90a01 100644 --- a/deprecations/c-api-pending-removal-in-3.14.po +++ b/deprecations/c-api-pending-removal-in-3.14.po @@ -59,8 +59,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:21 #: deprecations/c-api-pending-removal-in-3.14.rst:71 msgid "" -"The :c:func:`Py_InitializeFromConfig` API should be used with :c:type:" -"`PyConfig` instead." +"The :c:func:`Py_InitializeFromConfig` API should be used " +"with :c:type:`PyConfig` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:24 @@ -122,8 +122,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:48 msgid "" -":c:var:`Py_NoUserSiteDirectory`: Use :c:member:`PyConfig." -"user_site_directory` instead." +":c:var:`Py_NoUserSiteDirectory`: " +"Use :c:member:`PyConfig.user_site_directory` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:50 @@ -144,36 +144,36 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:57 msgid "" -":c:var:`Py_LegacyWindowsFSEncodingFlag`: Use :c:member:`PyPreConfig." -"legacy_windows_fs_encoding` instead." +":c:var:`Py_LegacyWindowsFSEncodingFlag`: " +"Use :c:member:`PyPreConfig.legacy_windows_fs_encoding` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:59 msgid "" -":c:var:`Py_LegacyWindowsStdioFlag`: Use :c:member:`PyConfig." -"legacy_windows_stdio` instead." +":c:var:`Py_LegacyWindowsStdioFlag`: " +"Use :c:member:`PyConfig.legacy_windows_stdio` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:61 msgid "" -":c:var:`!Py_FileSystemDefaultEncoding`: Use :c:member:`PyConfig." -"filesystem_encoding` instead." +":c:var:`!Py_FileSystemDefaultEncoding`: " +"Use :c:member:`PyConfig.filesystem_encoding` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:63 msgid "" -":c:var:`!Py_HasFileSystemDefaultEncoding`: Use :c:member:`PyConfig." -"filesystem_encoding` instead." +":c:var:`!Py_HasFileSystemDefaultEncoding`: " +"Use :c:member:`PyConfig.filesystem_encoding` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:65 msgid "" -":c:var:`!Py_FileSystemDefaultEncodeErrors`: Use :c:member:`PyConfig." -"filesystem_errors` instead." +":c:var:`!Py_FileSystemDefaultEncodeErrors`: " +"Use :c:member:`PyConfig.filesystem_errors` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:67 msgid "" -":c:var:`!Py_UTF8Mode`: Use :c:member:`PyPreConfig.utf8_mode` instead. (see :" -"c:func:`Py_PreInitialize`)" +":c:var:`!Py_UTF8Mode`: Use :c:member:`PyPreConfig.utf8_mode` instead. " +"(see :c:func:`Py_PreInitialize`)" msgstr "" diff --git a/deprecations/c-api-pending-removal-in-3.15.po b/deprecations/c-api-pending-removal-in-3.15.po index d8fa169b2..e478ba840 100644 --- a/deprecations/c-api-pending-removal-in-3.15.po +++ b/deprecations/c-api-pending-removal-in-3.15.po @@ -27,20 +27,20 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:5 msgid "" -"The :c:func:`PyImport_ImportModuleNoBlock`: Use :c:func:" -"`PyImport_ImportModule` instead." +"The :c:func:`PyImport_ImportModuleNoBlock`: " +"Use :c:func:`PyImport_ImportModule` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:7 msgid "" -":c:func:`PyWeakref_GetObject` and :c:func:`PyWeakref_GET_OBJECT`: Use :c:" -"func:`!PyWeakref_GetRef` instead." +":c:func:`PyWeakref_GetObject` and :c:func:`PyWeakref_GET_OBJECT`: " +"Use :c:func:`!PyWeakref_GetRef` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:9 msgid "" -":c:type:`Py_UNICODE` type and the :c:macro:`!Py_UNICODE_WIDE` macro: Use :c:" -"type:`wchar_t` instead." +":c:type:`Py_UNICODE` type and the :c:macro:`!Py_UNICODE_WIDE` macro: " +"Use :c:type:`wchar_t` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:11 @@ -75,6 +75,6 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:25 msgid "" -":c:func:`Py_GetPythonHome`: Get :c:member:`PyConfig.home` or the :envvar:" -"`PYTHONHOME` environment variable instead." +":c:func:`Py_GetPythonHome`: Get :c:member:`PyConfig.home` or " +"the :envvar:`PYTHONHOME` environment variable instead." msgstr "" diff --git a/deprecations/c-api-pending-removal-in-future.po b/deprecations/c-api-pending-removal-in-future.po index c9afaff8a..ea065bbf5 100644 --- a/deprecations/c-api-pending-removal-in-future.po +++ b/deprecations/c-api-pending-removal-in-future.po @@ -58,8 +58,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-future.rst:19 msgid "" -":c:func:`PySlice_GetIndicesEx`: Use :c:func:`PySlice_Unpack` and :c:func:" -"`PySlice_AdjustIndices` instead." +":c:func:`PySlice_GetIndicesEx`: Use :c:func:`PySlice_Unpack` " +"and :c:func:`PySlice_AdjustIndices` instead." msgstr "" #: deprecations/c-api-pending-removal-in-future.rst:21 diff --git a/deprecations/index.po b/deprecations/index.po index 8a7e89b57..5a3a9e7e3 100644 --- a/deprecations/index.po +++ b/deprecations/index.po @@ -203,10 +203,10 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:6 msgid "" -"Setting :attr:`~module.__loader__` on a module while failing to set :attr:" -"`__spec__.loader ` is deprecated. In " -"Python 3.14, :attr:`!__loader__` will cease to be set or taken into " -"consideration by the import system or the standard library." +"Setting :attr:`~module.__loader__` on a module while failing to " +"set :attr:`__spec__.loader ` is " +"deprecated. In Python 3.14, :attr:`!__loader__` will cease to be set or " +"taken into consideration by the import system or the standard library." msgstr "" #: deprecations/pending-removal-in-3.14.rst:11 @@ -245,8 +245,8 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:26 msgid "" -"Use :class:`ast.Constant` instead. (Contributed by Serhiy Storchaka in :gh:" -"`90953`.)" +"Use :class:`ast.Constant` instead. (Contributed by Serhiy Storchaka " +"in :gh:`90953`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:29 @@ -255,18 +255,18 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:31 msgid "" -"The child watcher classes :class:`~asyncio.MultiLoopChildWatcher`, :class:" -"`~asyncio.FastChildWatcher`, :class:`~asyncio.AbstractChildWatcher` and :" -"class:`~asyncio.SafeChildWatcher` are deprecated and will be removed in " +"The child watcher " +"classes :class:`~asyncio.MultiLoopChildWatcher`, :class:`~asyncio.FastChildWatcher`, :class:`~asyncio.AbstractChildWatcher` " +"and :class:`~asyncio.SafeChildWatcher` are deprecated and will be removed in " "Python 3.14. (Contributed by Kumar Aditya in :gh:`94597`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:37 msgid "" -":func:`asyncio.set_child_watcher`, :func:`asyncio.get_child_watcher`, :meth:" -"`asyncio.AbstractEventLoopPolicy.set_child_watcher` and :meth:`asyncio." -"AbstractEventLoopPolicy.get_child_watcher` are deprecated and will be " -"removed in Python 3.14. (Contributed by Kumar Aditya in :gh:`94597`.)" +":func:`asyncio.set_child_watcher`, :func:`asyncio.get_child_watcher`, :meth:`asyncio.AbstractEventLoopPolicy.set_child_watcher` " +"and :meth:`asyncio.AbstractEventLoopPolicy.get_child_watcher` are deprecated " +"and will be removed in Python 3.14. (Contributed by Kumar Aditya " +"in :gh:`94597`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:43 @@ -281,14 +281,16 @@ msgstr "" msgid "" ":mod:`collections.abc`: Deprecated :class:`~collections.abc.ByteString`. " "Prefer :class:`!Sequence` or :class:`~collections.abc.Buffer`. For use in " -"typing, prefer a union, like ``bytes | bytearray``, or :class:`collections." -"abc.Buffer`. (Contributed by Shantanu Jain in :gh:`91896`.)" +"typing, prefer a union, like ``bytes | bytearray``, " +"or :class:`collections.abc.Buffer`. (Contributed by Shantanu Jain " +"in :gh:`91896`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:54 msgid "" -":mod:`email`: Deprecated the *isdst* parameter in :func:`email.utils." -"localtime`. (Contributed by Alan Williams in :gh:`72346`.)" +":mod:`email`: Deprecated the *isdst* parameter " +"in :func:`email.utils.localtime`. (Contributed by Alan Williams " +"in :gh:`72346`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:57 @@ -343,15 +345,16 @@ msgid "" "on Linux, BSDs, and other non-macOS POSIX platforms where ``'fork'`` is " "currently the default (:gh:`84559`). Adding a runtime warning about this was " "deemed too disruptive as the majority of code is not expected to care. Use " -"the :func:`~multiprocessing.get_context` or :func:`~multiprocessing." -"set_start_method` APIs to explicitly specify when your code *requires* " -"``'fork'``. See :ref:`multiprocessing-start-methods`." +"the :func:`~multiprocessing.get_context` " +"or :func:`~multiprocessing.set_start_method` APIs to explicitly specify when " +"your code *requires* ``'fork'``. See :ref:`multiprocessing-start-methods`." msgstr "" #: deprecations/pending-removal-in-3.14.rst:87 msgid "" -":mod:`pathlib`: :meth:`~pathlib.PurePath.is_relative_to` and :meth:`~pathlib." -"PurePath.relative_to`: passing additional arguments is deprecated." +":mod:`pathlib`: :meth:`~pathlib.PurePath.is_relative_to` " +"and :meth:`~pathlib.PurePath.relative_to`: passing additional arguments is " +"deprecated." msgstr "" #: deprecations/pending-removal-in-3.14.rst:91 @@ -383,15 +386,15 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:105 msgid "" -":meth:`~sqlite3.Cursor.execute` and :meth:`~sqlite3.Cursor.executemany` if :" -"ref:`named placeholders ` are used and *parameters* is " -"a sequence instead of a :class:`dict`." +":meth:`~sqlite3.Cursor.execute` and :meth:`~sqlite3.Cursor.executemany` " +"if :ref:`named placeholders ` are used and " +"*parameters* is a sequence instead of a :class:`dict`." msgstr "" #: deprecations/pending-removal-in-3.14.rst:109 msgid "" -"date and datetime adapter, date and timestamp converter: see the :mod:" -"`sqlite3` documentation for suggested replacement recipes." +"date and datetime adapter, date and timestamp converter: see " +"the :mod:`sqlite3` documentation for suggested replacement recipes." msgstr "" #: deprecations/pending-removal-in-3.14.rst:112 @@ -411,8 +414,8 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:122 msgid "" ":mod:`urllib`: :class:`!urllib.parse.Quoter` is deprecated: it was not " -"intended to be a public API. (Contributed by Gregory P. Smith in :gh:" -"`88168`.)" +"intended to be a public API. (Contributed by Gregory P. Smith " +"in :gh:`88168`.)" msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:2 @@ -432,16 +435,17 @@ msgstr "" msgid "" ":class:`locale`: :func:`locale.getdefaultlocale` was deprecated in Python " "3.11 and originally planned for removal in Python 3.13 (:gh:`90817`), but " -"removal has been postponed to Python 3.15. Use :func:`locale.setlocale`, :" -"func:`locale.getencoding` and :func:`locale.getlocale` instead. (Contributed " -"by Hugo van Kemenade in :gh:`111187`.)" +"removal has been postponed to Python 3.15. " +"Use :func:`locale.setlocale`, :func:`locale.getencoding` " +"and :func:`locale.getlocale` instead. (Contributed by Hugo van Kemenade " +"in :gh:`111187`.)" msgstr "" #: deprecations/pending-removal-in-3.15.rst:16 msgid "" ":mod:`pathlib`: :meth:`pathlib.PurePath.is_reserved` is deprecated and " -"scheduled for removal in Python 3.15. From Python 3.13 onwards, use ``os." -"path.isreserved`` to detect reserved paths on Windows." +"scheduled for removal in Python 3.15. From Python 3.13 onwards, use " +"``os.path.isreserved`` to detect reserved paths on Windows." msgstr "" #: deprecations/pending-removal-in-3.15.rst:21 @@ -485,20 +489,21 @@ msgstr "" #: deprecations/pending-removal-in-3.15.rst:47 msgid "" -":class:`typing.TypedDict`: When using the functional syntax to create a :" -"class:`!TypedDict` class, failing to pass a value to the *fields* parameter " -"(``TD = TypedDict(\"TD\")``) is deprecated. Passing ``None`` to the *fields* " -"parameter (``TD = TypedDict(\"TD\", None)``) is also deprecated. Both will " -"be disallowed in Python 3.15. To create a :class:`!TypedDict` class with 0 " -"fields, use ``class TD(TypedDict): pass`` or ``TD = TypedDict(\"TD\", {})``." +":class:`typing.TypedDict`: When using the functional syntax to create " +"a :class:`!TypedDict` class, failing to pass a value to the *fields* " +"parameter (``TD = TypedDict(\"TD\")``) is deprecated. Passing ``None`` to " +"the *fields* parameter (``TD = TypedDict(\"TD\", None)``) is also " +"deprecated. Both will be disallowed in Python 3.15. To create a :class:`!" +"TypedDict` class with 0 fields, use ``class TD(TypedDict): pass`` or ``TD = " +"TypedDict(\"TD\", {})``." msgstr "" #: deprecations/pending-removal-in-3.15.rst:54 msgid "" ":mod:`wave`: Deprecate the ``getmark()``, ``setmark()`` and ``getmarkers()`` " "methods of the :class:`wave.Wave_read` and :class:`wave.Wave_write` classes. " -"They will be removed in Python 3.15. (Contributed by Victor Stinner in :gh:" -"`105096`.)" +"They will be removed in Python 3.15. (Contributed by Victor Stinner " +"in :gh:`105096`.)" msgstr "" #: deprecations/pending-removal-in-3.16.rst:2 @@ -563,10 +568,10 @@ msgid "" "for example ``0in x``, ``1or x``, ``0if 1else 2``. It allows confusing and " "ambiguous expressions like ``[0x1for x in y]`` (which can be interpreted as " "``[0x1 for x in y]`` or ``[0x1f or x in y]``). A syntax warning is raised " -"if the numeric literal is immediately followed by one of keywords :keyword:" -"`and`, :keyword:`else`, :keyword:`for`, :keyword:`if`, :keyword:`in`, :" -"keyword:`is` and :keyword:`or`. In a future release it will be changed to a " -"syntax error. (:gh:`87999`)" +"if the numeric literal is immediately followed by one of " +"keywords :keyword:`and`, :keyword:`else`, :keyword:`for`, :keyword:`if`, :keyword:`in`, :keyword:`is` " +"and :keyword:`or`. In a future release it will be changed to a syntax " +"error. (:gh:`87999`)" msgstr "" #: deprecations/pending-removal-in-future.rst:26 @@ -578,16 +583,16 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:29 msgid "" -"Support for ``__float__()`` method returning a strict subclass of :class:" -"`float`: these methods will be required to return an instance of :class:" -"`float`." +"Support for ``__float__()`` method returning a strict subclass " +"of :class:`float`: these methods will be required to return an instance " +"of :class:`float`." msgstr "" #: deprecations/pending-removal-in-future.rst:32 msgid "" -"Support for ``__complex__()`` method returning a strict subclass of :class:" -"`complex`: these methods will be required to return an instance of :class:" -"`complex`." +"Support for ``__complex__()`` method returning a strict subclass " +"of :class:`complex`: these methods will be required to return an instance " +"of :class:`complex`." msgstr "" #: deprecations/pending-removal-in-future.rst:35 @@ -596,17 +601,18 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:36 msgid "" -"Passing a complex number as the *real* or *imag* argument in the :func:" -"`complex` constructor is now deprecated; it should only be passed as a " -"single positional argument. (Contributed by Serhiy Storchaka in :gh:" -"`109218`.)" +"Passing a complex number as the *real* or *imag* argument in " +"the :func:`complex` constructor is now deprecated; it should only be passed " +"as a single positional argument. (Contributed by Serhiy Storchaka " +"in :gh:`109218`.)" msgstr "" #: deprecations/pending-removal-in-future.rst:41 msgid "" ":mod:`calendar`: ``calendar.January`` and ``calendar.February`` constants " -"are deprecated and replaced by :data:`calendar.JANUARY` and :data:`calendar." -"FEBRUARY`. (Contributed by Prince Roshan in :gh:`103636`.)" +"are deprecated and replaced by :data:`calendar.JANUARY` " +"and :data:`calendar.FEBRUARY`. (Contributed by Prince Roshan " +"in :gh:`103636`.)" msgstr "" #: deprecations/pending-removal-in-future.rst:46 @@ -621,14 +627,14 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:51 msgid "" -":meth:`~datetime.datetime.utcnow`: use ``datetime.datetime.now(tz=datetime." -"UTC)``." +":meth:`~datetime.datetime.utcnow`: use " +"``datetime.datetime.now(tz=datetime.UTC)``." msgstr "" #: deprecations/pending-removal-in-future.rst:53 msgid "" -":meth:`~datetime.datetime.utcfromtimestamp`: use ``datetime.datetime." -"fromtimestamp(timestamp, tz=datetime.UTC)``." +":meth:`~datetime.datetime.utcfromtimestamp`: use " +"``datetime.datetime.fromtimestamp(timestamp, tz=datetime.UTC)``." msgstr "" #: deprecations/pending-removal-in-future.rst:56 @@ -708,8 +714,8 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:92 msgid "" -":class:`ssl.SSLContext`: :meth:`~ssl.SSLContext.set_npn_protocols` and :meth:" -"`!selected_npn_protocol` are deprecated: use ALPN instead." +":class:`ssl.SSLContext`: :meth:`~ssl.SSLContext.set_npn_protocols` " +"and :meth:`!selected_npn_protocol` are deprecated: use ALPN instead." msgstr "" #: deprecations/pending-removal-in-future.rst:95 @@ -764,8 +770,8 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:111 msgid "" -":meth:`!threading.Condition.notifyAll`: use :meth:`~threading.Condition." -"notify_all`." +":meth:`!threading.Condition.notifyAll`: " +"use :meth:`~threading.Condition.notify_all`." msgstr "" #: deprecations/pending-removal-in-future.rst:112 @@ -774,14 +780,14 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:113 msgid "" -":meth:`!threading.Thread.isDaemon`, :meth:`threading.Thread.setDaemon`: use :" -"attr:`threading.Thread.daemon` attribute." +":meth:`!threading.Thread.isDaemon`, :meth:`threading.Thread.setDaemon`: " +"use :attr:`threading.Thread.daemon` attribute." msgstr "" #: deprecations/pending-removal-in-future.rst:115 msgid "" -":meth:`!threading.Thread.getName`, :meth:`threading.Thread.setName`: use :" -"attr:`threading.Thread.name` attribute." +":meth:`!threading.Thread.getName`, :meth:`threading.Thread.setName`: " +"use :attr:`threading.Thread.name` attribute." msgstr "" #: deprecations/pending-removal-in-future.rst:117 @@ -854,9 +860,9 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:139 msgid "" -":mod:`urllib.request`: :class:`~urllib.request.URLopener` and :class:" -"`~urllib.request.FancyURLopener` style of invoking requests is deprecated. " -"Use newer :func:`~urllib.request.urlopen` functions and methods." +":mod:`urllib.request`: :class:`~urllib.request.URLopener` " +"and :class:`~urllib.request.FancyURLopener` style of invoking requests is " +"deprecated. Use newer :func:`~urllib.request.urlopen` functions and methods." msgstr "" #: deprecations/pending-removal-in-future.rst:143 @@ -867,16 +873,16 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:146 msgid "" -":mod:`xml.etree.ElementTree`: Testing the truth value of an :class:`~xml." -"etree.ElementTree.Element` is deprecated. In a future release it will always " -"return ``True``. Prefer explicit ``len(elem)`` or ``elem is not None`` tests " -"instead." +":mod:`xml.etree.ElementTree`: Testing the truth value of " +"an :class:`~xml.etree.ElementTree.Element` is deprecated. In a future " +"release it will always return ``True``. Prefer explicit ``len(elem)`` or " +"``elem is not None`` tests instead." msgstr "" #: deprecations/pending-removal-in-future.rst:151 msgid "" -":meth:`zipimport.zipimporter.load_module` is deprecated: use :meth:" -"`~zipimport.zipimporter.exec_module` instead." +":meth:`zipimport.zipimporter.load_module` is deprecated: " +"use :meth:`~zipimport.zipimporter.exec_module` instead." msgstr "" #: deprecations/index.rst:15 @@ -921,8 +927,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:21 #: deprecations/c-api-pending-removal-in-3.14.rst:71 msgid "" -"The :c:func:`Py_InitializeFromConfig` API should be used with :c:type:" -"`PyConfig` instead." +"The :c:func:`Py_InitializeFromConfig` API should be used " +"with :c:type:`PyConfig` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:24 @@ -984,8 +990,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:48 msgid "" -":c:var:`Py_NoUserSiteDirectory`: Use :c:member:`PyConfig." -"user_site_directory` instead." +":c:var:`Py_NoUserSiteDirectory`: " +"Use :c:member:`PyConfig.user_site_directory` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:50 @@ -1006,38 +1012,38 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:57 msgid "" -":c:var:`Py_LegacyWindowsFSEncodingFlag`: Use :c:member:`PyPreConfig." -"legacy_windows_fs_encoding` instead." +":c:var:`Py_LegacyWindowsFSEncodingFlag`: " +"Use :c:member:`PyPreConfig.legacy_windows_fs_encoding` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:59 msgid "" -":c:var:`Py_LegacyWindowsStdioFlag`: Use :c:member:`PyConfig." -"legacy_windows_stdio` instead." +":c:var:`Py_LegacyWindowsStdioFlag`: " +"Use :c:member:`PyConfig.legacy_windows_stdio` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:61 msgid "" -":c:var:`!Py_FileSystemDefaultEncoding`: Use :c:member:`PyConfig." -"filesystem_encoding` instead." +":c:var:`!Py_FileSystemDefaultEncoding`: " +"Use :c:member:`PyConfig.filesystem_encoding` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:63 msgid "" -":c:var:`!Py_HasFileSystemDefaultEncoding`: Use :c:member:`PyConfig." -"filesystem_encoding` instead." +":c:var:`!Py_HasFileSystemDefaultEncoding`: " +"Use :c:member:`PyConfig.filesystem_encoding` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:65 msgid "" -":c:var:`!Py_FileSystemDefaultEncodeErrors`: Use :c:member:`PyConfig." -"filesystem_errors` instead." +":c:var:`!Py_FileSystemDefaultEncodeErrors`: " +"Use :c:member:`PyConfig.filesystem_errors` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:67 msgid "" -":c:var:`!Py_UTF8Mode`: Use :c:member:`PyPreConfig.utf8_mode` instead. (see :" -"c:func:`Py_PreInitialize`)" +":c:var:`!Py_UTF8Mode`: Use :c:member:`PyPreConfig.utf8_mode` instead. " +"(see :c:func:`Py_PreInitialize`)" msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:4 @@ -1046,20 +1052,20 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:5 msgid "" -"The :c:func:`PyImport_ImportModuleNoBlock`: Use :c:func:" -"`PyImport_ImportModule` instead." +"The :c:func:`PyImport_ImportModuleNoBlock`: " +"Use :c:func:`PyImport_ImportModule` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:7 msgid "" -":c:func:`PyWeakref_GetObject` and :c:func:`PyWeakref_GET_OBJECT`: Use :c:" -"func:`!PyWeakref_GetRef` instead." +":c:func:`PyWeakref_GetObject` and :c:func:`PyWeakref_GET_OBJECT`: " +"Use :c:func:`!PyWeakref_GetRef` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:9 msgid "" -":c:type:`Py_UNICODE` type and the :c:macro:`!Py_UNICODE_WIDE` macro: Use :c:" -"type:`wchar_t` instead." +":c:type:`Py_UNICODE` type and the :c:macro:`!Py_UNICODE_WIDE` macro: " +"Use :c:type:`wchar_t` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:11 @@ -1094,8 +1100,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:25 msgid "" -":c:func:`Py_GetPythonHome`: Get :c:member:`PyConfig.home` or the :envvar:" -"`PYTHONHOME` environment variable instead." +":c:func:`Py_GetPythonHome`: Get :c:member:`PyConfig.home` or " +"the :envvar:`PYTHONHOME` environment variable instead." msgstr "" #: deprecations/c-api-pending-removal-in-future.rst:4 @@ -1135,8 +1141,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-future.rst:19 msgid "" -":c:func:`PySlice_GetIndicesEx`: Use :c:func:`PySlice_Unpack` and :c:func:" -"`PySlice_AdjustIndices` instead." +":c:func:`PySlice_GetIndicesEx`: Use :c:func:`PySlice_Unpack` " +"and :c:func:`PySlice_AdjustIndices` instead." msgstr "" #: deprecations/c-api-pending-removal-in-future.rst:21 diff --git a/deprecations/pending-removal-in-3.14.po b/deprecations/pending-removal-in-3.14.po index 8fb8bec31..c0dc90d58 100644 --- a/deprecations/pending-removal-in-3.14.po +++ b/deprecations/pending-removal-in-3.14.po @@ -27,10 +27,10 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:6 msgid "" -"Setting :attr:`~module.__loader__` on a module while failing to set :attr:" -"`__spec__.loader ` is deprecated. In " -"Python 3.14, :attr:`!__loader__` will cease to be set or taken into " -"consideration by the import system or the standard library." +"Setting :attr:`~module.__loader__` on a module while failing to " +"set :attr:`__spec__.loader ` is " +"deprecated. In Python 3.14, :attr:`!__loader__` will cease to be set or " +"taken into consideration by the import system or the standard library." msgstr "" #: deprecations/pending-removal-in-3.14.rst:11 @@ -69,8 +69,8 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:26 msgid "" -"Use :class:`ast.Constant` instead. (Contributed by Serhiy Storchaka in :gh:" -"`90953`.)" +"Use :class:`ast.Constant` instead. (Contributed by Serhiy Storchaka " +"in :gh:`90953`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:29 @@ -79,18 +79,18 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:31 msgid "" -"The child watcher classes :class:`~asyncio.MultiLoopChildWatcher`, :class:" -"`~asyncio.FastChildWatcher`, :class:`~asyncio.AbstractChildWatcher` and :" -"class:`~asyncio.SafeChildWatcher` are deprecated and will be removed in " +"The child watcher " +"classes :class:`~asyncio.MultiLoopChildWatcher`, :class:`~asyncio.FastChildWatcher`, :class:`~asyncio.AbstractChildWatcher` " +"and :class:`~asyncio.SafeChildWatcher` are deprecated and will be removed in " "Python 3.14. (Contributed by Kumar Aditya in :gh:`94597`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:37 msgid "" -":func:`asyncio.set_child_watcher`, :func:`asyncio.get_child_watcher`, :meth:" -"`asyncio.AbstractEventLoopPolicy.set_child_watcher` and :meth:`asyncio." -"AbstractEventLoopPolicy.get_child_watcher` are deprecated and will be " -"removed in Python 3.14. (Contributed by Kumar Aditya in :gh:`94597`.)" +":func:`asyncio.set_child_watcher`, :func:`asyncio.get_child_watcher`, :meth:`asyncio.AbstractEventLoopPolicy.set_child_watcher` " +"and :meth:`asyncio.AbstractEventLoopPolicy.get_child_watcher` are deprecated " +"and will be removed in Python 3.14. (Contributed by Kumar Aditya " +"in :gh:`94597`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:43 @@ -105,14 +105,16 @@ msgstr "" msgid "" ":mod:`collections.abc`: Deprecated :class:`~collections.abc.ByteString`. " "Prefer :class:`!Sequence` or :class:`~collections.abc.Buffer`. For use in " -"typing, prefer a union, like ``bytes | bytearray``, or :class:`collections." -"abc.Buffer`. (Contributed by Shantanu Jain in :gh:`91896`.)" +"typing, prefer a union, like ``bytes | bytearray``, " +"or :class:`collections.abc.Buffer`. (Contributed by Shantanu Jain " +"in :gh:`91896`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:54 msgid "" -":mod:`email`: Deprecated the *isdst* parameter in :func:`email.utils." -"localtime`. (Contributed by Alan Williams in :gh:`72346`.)" +":mod:`email`: Deprecated the *isdst* parameter " +"in :func:`email.utils.localtime`. (Contributed by Alan Williams " +"in :gh:`72346`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:57 @@ -167,15 +169,16 @@ msgid "" "on Linux, BSDs, and other non-macOS POSIX platforms where ``'fork'`` is " "currently the default (:gh:`84559`). Adding a runtime warning about this was " "deemed too disruptive as the majority of code is not expected to care. Use " -"the :func:`~multiprocessing.get_context` or :func:`~multiprocessing." -"set_start_method` APIs to explicitly specify when your code *requires* " -"``'fork'``. See :ref:`multiprocessing-start-methods`." +"the :func:`~multiprocessing.get_context` " +"or :func:`~multiprocessing.set_start_method` APIs to explicitly specify when " +"your code *requires* ``'fork'``. See :ref:`multiprocessing-start-methods`." msgstr "" #: deprecations/pending-removal-in-3.14.rst:87 msgid "" -":mod:`pathlib`: :meth:`~pathlib.PurePath.is_relative_to` and :meth:`~pathlib." -"PurePath.relative_to`: passing additional arguments is deprecated." +":mod:`pathlib`: :meth:`~pathlib.PurePath.is_relative_to` " +"and :meth:`~pathlib.PurePath.relative_to`: passing additional arguments is " +"deprecated." msgstr "" #: deprecations/pending-removal-in-3.14.rst:91 @@ -207,15 +210,15 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:105 msgid "" -":meth:`~sqlite3.Cursor.execute` and :meth:`~sqlite3.Cursor.executemany` if :" -"ref:`named placeholders ` are used and *parameters* is " -"a sequence instead of a :class:`dict`." +":meth:`~sqlite3.Cursor.execute` and :meth:`~sqlite3.Cursor.executemany` " +"if :ref:`named placeholders ` are used and " +"*parameters* is a sequence instead of a :class:`dict`." msgstr "" #: deprecations/pending-removal-in-3.14.rst:109 msgid "" -"date and datetime adapter, date and timestamp converter: see the :mod:" -"`sqlite3` documentation for suggested replacement recipes." +"date and datetime adapter, date and timestamp converter: see " +"the :mod:`sqlite3` documentation for suggested replacement recipes." msgstr "" #: deprecations/pending-removal-in-3.14.rst:112 @@ -235,6 +238,6 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:122 msgid "" ":mod:`urllib`: :class:`!urllib.parse.Quoter` is deprecated: it was not " -"intended to be a public API. (Contributed by Gregory P. Smith in :gh:" -"`88168`.)" +"intended to be a public API. (Contributed by Gregory P. Smith " +"in :gh:`88168`.)" msgstr "" diff --git a/deprecations/pending-removal-in-3.15.po b/deprecations/pending-removal-in-3.15.po index 2074d7f0f..14315ffe0 100644 --- a/deprecations/pending-removal-in-3.15.po +++ b/deprecations/pending-removal-in-3.15.po @@ -33,16 +33,17 @@ msgstr "" msgid "" ":class:`locale`: :func:`locale.getdefaultlocale` was deprecated in Python " "3.11 and originally planned for removal in Python 3.13 (:gh:`90817`), but " -"removal has been postponed to Python 3.15. Use :func:`locale.setlocale`, :" -"func:`locale.getencoding` and :func:`locale.getlocale` instead. (Contributed " -"by Hugo van Kemenade in :gh:`111187`.)" +"removal has been postponed to Python 3.15. " +"Use :func:`locale.setlocale`, :func:`locale.getencoding` " +"and :func:`locale.getlocale` instead. (Contributed by Hugo van Kemenade " +"in :gh:`111187`.)" msgstr "" #: deprecations/pending-removal-in-3.15.rst:16 msgid "" ":mod:`pathlib`: :meth:`pathlib.PurePath.is_reserved` is deprecated and " -"scheduled for removal in Python 3.15. From Python 3.13 onwards, use ``os." -"path.isreserved`` to detect reserved paths on Windows." +"scheduled for removal in Python 3.15. From Python 3.13 onwards, use " +"``os.path.isreserved`` to detect reserved paths on Windows." msgstr "" #: deprecations/pending-removal-in-3.15.rst:21 @@ -86,18 +87,19 @@ msgstr "" #: deprecations/pending-removal-in-3.15.rst:47 msgid "" -":class:`typing.TypedDict`: When using the functional syntax to create a :" -"class:`!TypedDict` class, failing to pass a value to the *fields* parameter " -"(``TD = TypedDict(\"TD\")``) is deprecated. Passing ``None`` to the *fields* " -"parameter (``TD = TypedDict(\"TD\", None)``) is also deprecated. Both will " -"be disallowed in Python 3.15. To create a :class:`!TypedDict` class with 0 " -"fields, use ``class TD(TypedDict): pass`` or ``TD = TypedDict(\"TD\", {})``." +":class:`typing.TypedDict`: When using the functional syntax to create " +"a :class:`!TypedDict` class, failing to pass a value to the *fields* " +"parameter (``TD = TypedDict(\"TD\")``) is deprecated. Passing ``None`` to " +"the *fields* parameter (``TD = TypedDict(\"TD\", None)``) is also " +"deprecated. Both will be disallowed in Python 3.15. To create a :class:`!" +"TypedDict` class with 0 fields, use ``class TD(TypedDict): pass`` or ``TD = " +"TypedDict(\"TD\", {})``." msgstr "" #: deprecations/pending-removal-in-3.15.rst:54 msgid "" ":mod:`wave`: Deprecate the ``getmark()``, ``setmark()`` and ``getmarkers()`` " "methods of the :class:`wave.Wave_read` and :class:`wave.Wave_write` classes. " -"They will be removed in Python 3.15. (Contributed by Victor Stinner in :gh:" -"`105096`.)" +"They will be removed in Python 3.15. (Contributed by Victor Stinner " +"in :gh:`105096`.)" msgstr "" diff --git a/deprecations/pending-removal-in-future.po b/deprecations/pending-removal-in-future.po index d65a890d5..945760114 100644 --- a/deprecations/pending-removal-in-future.po +++ b/deprecations/pending-removal-in-future.po @@ -58,10 +58,10 @@ msgid "" "for example ``0in x``, ``1or x``, ``0if 1else 2``. It allows confusing and " "ambiguous expressions like ``[0x1for x in y]`` (which can be interpreted as " "``[0x1 for x in y]`` or ``[0x1f or x in y]``). A syntax warning is raised " -"if the numeric literal is immediately followed by one of keywords :keyword:" -"`and`, :keyword:`else`, :keyword:`for`, :keyword:`if`, :keyword:`in`, :" -"keyword:`is` and :keyword:`or`. In a future release it will be changed to a " -"syntax error. (:gh:`87999`)" +"if the numeric literal is immediately followed by one of " +"keywords :keyword:`and`, :keyword:`else`, :keyword:`for`, :keyword:`if`, :keyword:`in`, :keyword:`is` " +"and :keyword:`or`. In a future release it will be changed to a syntax " +"error. (:gh:`87999`)" msgstr "" #: deprecations/pending-removal-in-future.rst:26 @@ -73,16 +73,16 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:29 msgid "" -"Support for ``__float__()`` method returning a strict subclass of :class:" -"`float`: these methods will be required to return an instance of :class:" -"`float`." +"Support for ``__float__()`` method returning a strict subclass " +"of :class:`float`: these methods will be required to return an instance " +"of :class:`float`." msgstr "" #: deprecations/pending-removal-in-future.rst:32 msgid "" -"Support for ``__complex__()`` method returning a strict subclass of :class:" -"`complex`: these methods will be required to return an instance of :class:" -"`complex`." +"Support for ``__complex__()`` method returning a strict subclass " +"of :class:`complex`: these methods will be required to return an instance " +"of :class:`complex`." msgstr "" #: deprecations/pending-removal-in-future.rst:35 @@ -91,17 +91,18 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:36 msgid "" -"Passing a complex number as the *real* or *imag* argument in the :func:" -"`complex` constructor is now deprecated; it should only be passed as a " -"single positional argument. (Contributed by Serhiy Storchaka in :gh:" -"`109218`.)" +"Passing a complex number as the *real* or *imag* argument in " +"the :func:`complex` constructor is now deprecated; it should only be passed " +"as a single positional argument. (Contributed by Serhiy Storchaka " +"in :gh:`109218`.)" msgstr "" #: deprecations/pending-removal-in-future.rst:41 msgid "" ":mod:`calendar`: ``calendar.January`` and ``calendar.February`` constants " -"are deprecated and replaced by :data:`calendar.JANUARY` and :data:`calendar." -"FEBRUARY`. (Contributed by Prince Roshan in :gh:`103636`.)" +"are deprecated and replaced by :data:`calendar.JANUARY` " +"and :data:`calendar.FEBRUARY`. (Contributed by Prince Roshan " +"in :gh:`103636`.)" msgstr "" #: deprecations/pending-removal-in-future.rst:46 @@ -116,14 +117,14 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:51 msgid "" -":meth:`~datetime.datetime.utcnow`: use ``datetime.datetime.now(tz=datetime." -"UTC)``." +":meth:`~datetime.datetime.utcnow`: use " +"``datetime.datetime.now(tz=datetime.UTC)``." msgstr "" #: deprecations/pending-removal-in-future.rst:53 msgid "" -":meth:`~datetime.datetime.utcfromtimestamp`: use ``datetime.datetime." -"fromtimestamp(timestamp, tz=datetime.UTC)``." +":meth:`~datetime.datetime.utcfromtimestamp`: use " +"``datetime.datetime.fromtimestamp(timestamp, tz=datetime.UTC)``." msgstr "" #: deprecations/pending-removal-in-future.rst:56 @@ -203,8 +204,8 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:92 msgid "" -":class:`ssl.SSLContext`: :meth:`~ssl.SSLContext.set_npn_protocols` and :meth:" -"`!selected_npn_protocol` are deprecated: use ALPN instead." +":class:`ssl.SSLContext`: :meth:`~ssl.SSLContext.set_npn_protocols` " +"and :meth:`!selected_npn_protocol` are deprecated: use ALPN instead." msgstr "" #: deprecations/pending-removal-in-future.rst:95 @@ -259,8 +260,8 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:111 msgid "" -":meth:`!threading.Condition.notifyAll`: use :meth:`~threading.Condition." -"notify_all`." +":meth:`!threading.Condition.notifyAll`: " +"use :meth:`~threading.Condition.notify_all`." msgstr "" #: deprecations/pending-removal-in-future.rst:112 @@ -269,14 +270,14 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:113 msgid "" -":meth:`!threading.Thread.isDaemon`, :meth:`threading.Thread.setDaemon`: use :" -"attr:`threading.Thread.daemon` attribute." +":meth:`!threading.Thread.isDaemon`, :meth:`threading.Thread.setDaemon`: " +"use :attr:`threading.Thread.daemon` attribute." msgstr "" #: deprecations/pending-removal-in-future.rst:115 msgid "" -":meth:`!threading.Thread.getName`, :meth:`threading.Thread.setName`: use :" -"attr:`threading.Thread.name` attribute." +":meth:`!threading.Thread.getName`, :meth:`threading.Thread.setName`: " +"use :attr:`threading.Thread.name` attribute." msgstr "" #: deprecations/pending-removal-in-future.rst:117 @@ -349,9 +350,9 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:139 msgid "" -":mod:`urllib.request`: :class:`~urllib.request.URLopener` and :class:" -"`~urllib.request.FancyURLopener` style of invoking requests is deprecated. " -"Use newer :func:`~urllib.request.urlopen` functions and methods." +":mod:`urllib.request`: :class:`~urllib.request.URLopener` " +"and :class:`~urllib.request.FancyURLopener` style of invoking requests is " +"deprecated. Use newer :func:`~urllib.request.urlopen` functions and methods." msgstr "" #: deprecations/pending-removal-in-future.rst:143 @@ -362,14 +363,14 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:146 msgid "" -":mod:`xml.etree.ElementTree`: Testing the truth value of an :class:`~xml." -"etree.ElementTree.Element` is deprecated. In a future release it will always " -"return ``True``. Prefer explicit ``len(elem)`` or ``elem is not None`` tests " -"instead." +":mod:`xml.etree.ElementTree`: Testing the truth value of " +"an :class:`~xml.etree.ElementTree.Element` is deprecated. In a future " +"release it will always return ``True``. Prefer explicit ``len(elem)`` or " +"``elem is not None`` tests instead." msgstr "" #: deprecations/pending-removal-in-future.rst:151 msgid "" -":meth:`zipimport.zipimporter.load_module` is deprecated: use :meth:" -"`~zipimport.zipimporter.exec_module` instead." +":meth:`zipimport.zipimporter.load_module` is deprecated: " +"use :meth:`~zipimport.zipimporter.exec_module` instead." msgstr "" diff --git a/distributing/index.po b/distributing/index.po index 87083a52c..faec1d0fc 100644 --- a/distributing/index.po +++ b/distributing/index.po @@ -108,9 +108,9 @@ msgstr "" #~ 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 " +#~ "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)." @@ -125,11 +125,12 @@ msgstr "" #~ 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." +#~ "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 "" #~ "`setuptools`_ ilk olarak 2004'te yayınlanan :mod:`distutils` için (büyük " #~ "ölçüde) bir eklentidir. Değiştirilmemiş :mod:`distutils` araçlarına göre " @@ -314,8 +315,8 @@ msgstr "" #~ "bilgi ve öneriler için Python Paketleme Kullanıcı Kılavuzuna bakın." #~ msgid "" -#~ "`Python Packaging User Guide: Binary Extensions `__" +#~ "`Python Packaging User Guide: Binary Extensions `__" #~ msgstr "" -#~ "`Python Paketleme Kullanıcı Kılavuzu: İkili Uzantılar `__" +#~ "`Python Paketleme Kullanıcı Kılavuzu: İkili Uzantılar `__" diff --git a/extending/building.po b/extending/building.po index 52a8fbc90..9275b62c8 100644 --- a/extending/building.po +++ b/extending/building.po @@ -28,10 +28,10 @@ msgstr "" #: 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 setuptools, the correct filename is generated " -"automatically." +"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 setuptools, the correct filename is " +"generated automatically." msgstr "" #: extending/building.rst:16 diff --git a/extending/embedding.po b/extending/embedding.po index 6c91190d5..6816e38c9 100644 --- a/extending/embedding.po +++ b/extending/embedding.po @@ -62,10 +62,10 @@ msgstr "" 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." +"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 "" "Yani Python'u gömüyorsanız, kendi ana programınızı sağlıyorsunuz demektir. " "Bu ana programın yapması gereken şeylerden biri Python yorumlayıcısını " @@ -85,10 +85,10 @@ msgid "" msgstr "" "Yorumlayıcıyı çağırmanın birkaç farklı yolu vardır: Python deyimlerini " "içeren bir dizeyi :c:func:`PyRun_SimpleString` öğesine veya bir stdio dosya " -"işaretçisini ve bir dosya adını (yalnızca hata mesajlarında tanımlama için) :" -"c:func:`PyRun_SimpleFile` 'a iletebilirsiniz. Python nesnelerini oluşturmak " -"ve kullanmak için önceki bölümlerde açıklanan alt düzey işlemleri de " -"çağırabilirsiniz." +"işaretçisini ve bir dosya adını (yalnızca hata mesajlarında tanımlama " +"için) :c:func:`PyRun_SimpleFile` 'a iletebilirsiniz. Python nesnelerini " +"oluşturmak ve kullanmak için önceki bölümlerde açıklanan alt düzey işlemleri " +"de çağırabilirsiniz." #: extending/embedding.rst:41 msgid ":ref:`c-api-index`" @@ -145,29 +145,29 @@ msgstr "" #: extending/embedding.rst:78 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." +"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 "" ":c:func:`Py_SetProgramName` işlevi, yorumlayıcıyı Python çalışma zamanı " -"kütüphanelerine giden yollar hakkında bilgilendirmek için :c:func:" -"`Py_Initialize` öncesinde çağrılmalıdır. Ardından, Python yorumlayıcısı :c:" -"func:`Py_Initialize` ile başlatılır, ardından tarih ve saati yazdıran sabit " -"kodlanmış bir Python betiği yürütülür. Daha sonra, :c:func:`Py_FinalizeEx` " -"çağrısı yorumlayıcıyı kapatır ve ardından programın sonu gelir. Gerçek bir " -"programda, Python betiğini başka bir kaynaktan, belki bir metin düzenleyici " -"rutininden, bir dosyadan veya bir veri tabanından almak isteyebilirsiniz. " -"Python kodunu bir dosyadan almak, sizi bellek alanı ayırma ve dosya " -"içeriğini yükleme zahmetinden kurtaran :c:func:`PyRun_SimpleFile` işlevi " -"kullanılarak daha iyi yapılabilir." +"kütüphanelerine giden yollar hakkında bilgilendirmek " +"için :c:func:`Py_Initialize` öncesinde çağrılmalıdır. Ardından, Python " +"yorumlayıcısı :c:func:`Py_Initialize` ile başlatılır, ardından tarih ve " +"saati yazdıran sabit kodlanmış bir Python betiği yürütülür. Daha " +"sonra, :c:func:`Py_FinalizeEx` çağrısı yorumlayıcıyı kapatır ve ardından " +"programın sonu gelir. Gerçek bir programda, Python betiğini başka bir " +"kaynaktan, belki bir metin düzenleyici rutininden, bir dosyadan veya bir " +"veri tabanından almak isteyebilirsiniz. Python kodunu bir dosyadan almak, " +"sizi bellek alanı ayırma ve dosya içeriğini yükleme zahmetinden " +"kurtaran :c:func:`PyRun_SimpleFile` işlevi kullanılarak daha iyi yapılabilir." #: extending/embedding.rst:93 msgid "Beyond Very High Level Embedding: An overview" @@ -409,15 +409,15 @@ msgstr "" #: extending/embedding.rst:178 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 " +"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 "" "Yorumlayıcıyı başlattıktan sonra komut dosyası :c:func:`PyImport_Import` " -"kullanılarak yüklenir. Bu rutin, argümanı olarak :c:func:" -"`PyUnicode_FromString` veri dönüştürme rutini kullanılarak oluşturulan bir " -"Python dizesine ihtiyaç duyar. ::" +"kullanılarak yüklenir. Bu rutin, argümanı " +"olarak :c:func:`PyUnicode_FromString` veri dönüştürme rutini kullanılarak " +"oluşturulan bir Python dizesine ihtiyaç duyar. ::" #: extending/embedding.rst:183 msgid "" @@ -432,17 +432,17 @@ msgstr "" #: extending/embedding.rst:191 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::" +"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 "" -"Komut dosyası yüklendikten sonra, aradığımız ad :c:func:" -"`PyObject_GetAttrString` kullanılarak alınır. Ad varsa ve döndürülen nesne " -"çağrılabilirse bunun bir fonksiyon olduğunu güvenle varsayabilirsiniz. " -"Program daha sonra normal olarak bir dizi argüman oluşturarak devam eder. " -"Python işlevine yapılan çağrı şu şekilde yapılır:" +"Komut dosyası yüklendikten sonra, aradığımız " +"ad :c:func:`PyObject_GetAttrString` kullanılarak alınır. Ad varsa ve " +"döndürülen nesne çağrılabilirse bunun bir fonksiyon olduğunu güvenle " +"varsayabilirsiniz. Program daha sonra normal olarak bir dizi argüman " +"oluşturarak devam eder. Python işlevine yapılan çağrı şu şekilde yapılır:" #: extending/embedding.rst:197 msgid "pValue = PyObject_CallObject(pFunc, pArgs);" @@ -518,8 +518,9 @@ 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 "" -"Yukarıdaki kodu :c:func:`main` fonksiyonunun hemen üstüne ekleyin. Ayrıca, :" -"c:func:`Py_Initialize`: çağrısından önce aşağıdaki iki ifadeyi ekleyin::" +"Yukarıdaki kodu :c:func:`main` fonksiyonunun hemen üstüne ekleyin. " +"Ayrıca, :c:func:`Py_Initialize`: çağrısından önce aşağıdaki iki ifadeyi " +"ekleyin::" #: extending/embedding.rst:249 msgid "" @@ -582,14 +583,14 @@ msgid "" msgstr "" "Python yorumlayıcısını uygulamanıza gömmek için derleyicinize (ve " "bağlayıcınıza) iletilecek doğru bayrakları bulmak mutlaka önemli değildir, " -"özellikle Python'un C dinamik uzantıları buna karşı bağlatılı olan (:file:`." -"so` dosyaları) olarak uygulanan kütüphane modüllerini yüklemesi " +"özellikle Python'un C dinamik uzantıları buna karşı bağlatılı olan " +"(:file:`.so` dosyaları) olarak uygulanan kütüphane modüllerini yüklemesi " "gerektiğinden." #: extending/embedding.rst:290 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 " +"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:" @@ -625,8 +626,8 @@ msgstr "" #: extending/embedding.rst:307 msgid "" "$ /opt/bin/python3.11-config --ldflags --embed\n" -"-L/opt/lib/python3.11/config-3.11-x86_64-linux-gnu -L/opt/lib -lpython3.11 -" -"lpthread -ldl -lutil -lm" +"-L/opt/lib/python3.11/config-3.11-x86_64-linux-gnu -L/opt/lib -lpython3.11 " +"-lpthread -ldl -lutil -lm" msgstr "" #: extending/embedding.rst:313 @@ -645,11 +646,11 @@ 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:" +"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 "" "Bu prosedür sizin için işe yaramazsa (tüm Unix benzeri platformlar için " "çalışması garanti edilmez; ancak, memnuniyetle karşılıyoruz: :ref:`hata " diff --git a/extending/extending.po b/extending/extending.po index 00f71bb50..b4430009a 100644 --- a/extending/extending.po +++ b/extending/extending.po @@ -77,9 +77,9 @@ msgstr "" #: extending/extending.rst:53 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`.)" +"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 "" #: extending/extending.rst:58 @@ -115,11 +115,11 @@ msgstr "" 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." +"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 "" #: extending/extending.rst:83 @@ -215,19 +215,19 @@ msgstr "" 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." +"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 "" #: extending/extending.rst:152 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." +"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 "" #: extending/extending.rst:158 @@ -264,10 +264,11 @@ msgstr "" #: extending/extending.rst:180 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." +"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 "" #: extending/extending.rst:186 @@ -280,8 +281,8 @@ msgstr "" #: extending/extending.rst:190 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 " +"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 "" @@ -291,11 +292,12 @@ msgid "" "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_OSError`). 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." +"to mean that a file couldn't be opened (that should probably " +"be :c:data:`PyExc_OSError`). 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 "" #: extending/extending.rst:204 @@ -428,8 +430,8 @@ msgstr "" #: extending/extending.rst:292 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`. ::" +"a Python object. This is done using the " +"function :c:func:`PyLong_FromLong`. ::" msgstr "" #: extending/extending.rst:295 @@ -446,8 +448,8 @@ msgstr "" msgid "" "If you have a C function that returns no useful argument (a function " "returning :c:expr:`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)::" +"``None``. You need this idiom to do so (which is implemented by " +"the :c:macro:`Py_RETURN_NONE` macro)::" msgstr "" #: extending/extending.rst:305 @@ -496,8 +498,9 @@ msgstr "" #: extending/extending.rst:334 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." +"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 "" #: extending/extending.rst:338 @@ -529,9 +532,9 @@ msgstr "" #: extending/extending.rst:355 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::" +"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 "" #: extending/extending.rst:360 @@ -552,24 +555,25 @@ msgstr "" #: extending/extending.rst:370 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``." +"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 "" #: extending/extending.rst:381 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::" +"table. To add the module to the initialization table, " +"use :c:func:`PyImport_AppendInittab`, optionally followed by an import of " +"the module::" msgstr "" #: extending/extending.rst:386 @@ -646,9 +650,10 @@ 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." +"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 "" #: extending/extending.rst:455 @@ -747,10 +752,10 @@ msgstr "" #: extending/extending.rst:529 msgid "" -"This function must be registered with the interpreter using the :c:macro:" -"`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`." +"This function must be registered with the interpreter using " +"the :c:macro:`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 "" #: extending/extending.rst:534 @@ -763,14 +768,15 @@ msgstr "" #: extending/extending.rst:541 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::" +"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 "" #: extending/extending.rst:550 @@ -792,8 +798,9 @@ 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." +"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 "" #: extending/extending.rst:568 @@ -859,9 +866,10 @@ msgstr "" #: extending/extending.rst:610 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. ::" +"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 "" #: extending/extending.rst:614 @@ -1008,21 +1016,21 @@ msgstr "" #: extending/extending.rst:729 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." +"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 "" #: extending/extending.rst:739 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." +"parameters passed in which are not present in the *kwlist* will " +"cause :exc:`TypeError` to be raised." msgstr "" #: extending/extending.rst:745 @@ -1101,10 +1109,10 @@ msgstr "" #: extending/extending.rst:807 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." +"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 "" #: extending/extending.rst:812 @@ -1161,16 +1169,16 @@ msgstr "" #: extending/extending.rst:854 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 reuse 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." +"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 reuse 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 "" #: extending/extending.rst:865 @@ -1234,9 +1242,9 @@ msgstr "" #: extending/extending.rst:909 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 :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." msgstr "" #: extending/extending.rst:918 @@ -1246,12 +1254,12 @@ msgstr "" #: extending/extending.rst:920 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." +"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 "" #: extending/extending.rst:927 @@ -1289,11 +1297,11 @@ msgstr "" #: extending/extending.rst:950 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)." +"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 "" #: extending/extending.rst:960 @@ -1313,20 +1321,20 @@ msgid "" "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." +"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 "" #: extending/extending.rst:974 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." +"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 "" #: extending/extending.rst:981 @@ -1341,10 +1349,11 @@ 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.\")" +"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 "" #: extending/extending.rst:993 @@ -1501,8 +1510,8 @@ msgstr "" #: extending/extending.rst:1099 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." +"``NULL`` pointers --- however, their variants :c:func:`Py_XINCREF` " +"and :c:func:`Py_XDECREF` do." msgstr "" #: extending/extending.rst:1103 @@ -1813,9 +1822,9 @@ msgstr "" #: extending/extending.rst:1334 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::" +"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 "" #: extending/extending.rst:1338 @@ -1858,8 +1867,8 @@ msgstr "" #: extending/extending.rst:1365 msgid "" -"An interface for this function already exists in the standard module :mod:" -"`os` --- it was chosen as a simple and straightforward example." +"An interface for this function already exists in the standard " +"module :mod:`os` --- it was chosen as a simple and straightforward example." msgstr "" #: extending/extending.rst:1368 diff --git a/extending/index.po b/extending/index.po index 33f653e64..9e29fd35e 100644 --- a/extending/index.po +++ b/extending/index.po @@ -55,8 +55,8 @@ msgstr "" #: extending/index.rst:21 msgid "" -"For a detailed description of the whole Python/C API, see the separate :ref:" -"`c-api-index`." +"For a detailed description of the whole Python/C API, see the " +"separate :ref:`c-api-index`." msgstr "" "Tüm Python/C API'sinin ayrıntılı açıklaması için ayrı :ref:`c-api-index`'a " "bakın." @@ -69,24 +69,25 @@ msgstr "Önerilen üçüncü taraf araçları" 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." +"cython.org/>`_, `cffi `_, `SWIG `_ and `Numba `_ offer both simpler " +"and more sophisticated approaches to creating C and C++ extensions for " +"Python." msgstr "" "Bu kılavuz, yalnızca CPython'un bu sürümünün bir parçası olarak sağlanan " -"uzantıları oluşturmak için temel araçları kapsar. `Cython `_, `cffi `_, `SWIG `_ ve `Numba `_ gibi üçüncü taraf araçlar, " -"Python için C ve C++ uzantıları oluşturmaya yönelik hem daha basit hem de " -"daha karmaşık yaklaşımlar sunar." +"uzantıları oluşturmak için temel araçları kapsar. `Cython `_, `cffi `_, `SWIG `_ ve `Numba `_ gibi üçüncü taraf " +"araçlar, Python için C ve C++ uzantıları oluşturmaya yönelik hem daha basit " +"hem de daha karmaşık yaklaşımlar sunar." #: extending/index.rst:37 msgid "" -"`Python Packaging User Guide: Binary Extensions `_" +"`Python Packaging User Guide: Binary Extensions `_" msgstr "" -"`Python Paketleme Kullanıcı Kılavuzu: İkili Uzantılar `_" +"`Python Paketleme Kullanıcı Kılavuzu: İkili Uzantılar `_" #: extending/index.rst:38 msgid "" diff --git a/extending/newtypes.po b/extending/newtypes.po index 8d88ed95b..9630aaeb5 100644 --- a/extending/newtypes.po +++ b/extending/newtypes.po @@ -158,9 +158,9 @@ msgstr "" 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, tuples) which is where the :c:member:" -"`~PyTypeObject.tp_itemsize` field comes in. This will be dealt with " -"later. ::" +"length structures (think: strings, tuples) which is where " +"the :c:member:`~PyTypeObject.tp_itemsize` field comes in. This will be " +"dealt with later. ::" msgstr "" #: extending/newtypes.rst:44 @@ -208,8 +208,8 @@ msgstr "" #: extending/newtypes.rst:79 msgid "" -"If your type supports garbage collection, the destructor should call :c:func:" -"`PyObject_GC_UnTrack` before clearing any member fields::" +"If your type supports garbage collection, the destructor should " +"call :c:func:`PyObject_GC_UnTrack` before clearing any member fields::" msgstr "" #: extending/newtypes.rst:82 @@ -235,8 +235,8 @@ msgid "" "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::" +"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 "" #: extending/newtypes.rst:107 @@ -271,14 +271,16 @@ msgstr "" #: extending/newtypes.rst:134 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." +"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 "" #: extending/newtypes.rst:143 @@ -299,8 +301,9 @@ msgstr "" #: extending/newtypes.rst:157 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." +"object: the :func:`repr` function, and the :func:`str` function. " +"(The :func:`print` function just calls :func:`str`.) These handlers are " +"both optional." msgstr "" #: extending/newtypes.rst:163 @@ -329,19 +332,20 @@ msgstr "" #: extending/newtypes.rst:177 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." +"interpreter will supply a representation that uses the " +"type's :c:member:`~PyTypeObject.tp_name` and a uniquely identifying value " +"for the object." msgstr "" #: extending/newtypes.rst:181 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." +"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 "" #: extending/newtypes.rst:188 @@ -376,9 +380,10 @@ msgstr "" 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:expr:" -"`char\\*`, while the other accepts a :c:expr:`PyObject*`. Each type can use " -"whichever pair makes more sense for the implementation's convenience. ::" +"difference is that one pair takes the name of the attribute as " +"a :c:expr:`char\\*`, while the other accepts a :c:expr:`PyObject*`. Each " +"type can use whichever pair makes more sense for the implementation's " +"convenience. ::" msgstr "" #: extending/newtypes.rst:214 @@ -436,9 +441,10 @@ msgid "" "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." +"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 "" #: extending/newtypes.rst:253 @@ -473,8 +479,8 @@ msgstr "" 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 :c:" -"member:`~PyMethodDef.ml_name` field of the sentinel must be ``NULL``." +"needed at the end; it is a sentinel that marks the end of the array. " +"The :c:member:`~PyMethodDef.ml_name` field of the sentinel must be ``NULL``." msgstr "" #: extending/newtypes.rst:275 @@ -502,10 +508,10 @@ msgid "" "added to the type which will be able to extract a value from the instance " "structure. The :c:member:`~PyMemberDef.type` field should contain a type " "code like :c:macro:`Py_T_INT` or :c:macro:`Py_T_DOUBLE`; the value will be " -"used to determine how to convert Python values to and from C values. The :c:" -"member:`~PyMemberDef.flags` field is used to store flags which control how " -"the attribute can be accessed: you can set it to :c:macro:`Py_READONLY` to " -"prevent Python code from setting it." +"used to determine how to convert Python values to and from C values. " +"The :c:member:`~PyMemberDef.flags` field is used to store flags which " +"control how the attribute can be accessed: you can set it " +"to :c:macro:`Py_READONLY` to prevent Python code from setting it." msgstr "" #: extending/newtypes.rst:295 @@ -514,8 +520,8 @@ msgid "" "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:" -"`~type.__doc__` attribute." +"the descriptor from the class object, and get the doc string using " +"its :attr:`~type.__doc__` attribute." msgstr "" #: extending/newtypes.rst:301 @@ -531,8 +537,8 @@ msgstr "" #: extending/newtypes.rst:317 msgid "" "For simplicity, only the :c:expr:`char\\*` version will be demonstrated " -"here; the type of the name parameter is the only difference between the :c:" -"expr:`char\\*` and :c:expr:`PyObject*` flavors of the interface. This " +"here; the type of the name parameter is the only difference between " +"the :c:expr:`char\\*` and :c:expr:`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 " @@ -569,12 +575,13 @@ msgstr "" #: extending/newtypes.rst:345 msgid "" -"The :c:member:`~PyTypeObject.tp_setattr` handler is called when the :meth:" -"`~object.__setattr__` or :meth:`~object.__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``. ::" +"The :c:member:`~PyTypeObject.tp_setattr` handler is called when " +"the :meth:`~object.__setattr__` or :meth:`~object.__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 "" #: extending/newtypes.rst:351 @@ -599,8 +606,8 @@ msgstr "" 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`." +"methods `, like :meth:`!__lt__`, and also called " +"by :c:func:`PyObject_RichCompare` and :c:func:`PyObject_RichCompareBool`." msgstr "" #: extending/newtypes.rst:370 @@ -685,8 +692,8 @@ msgstr "" 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 " +"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. ::" @@ -747,17 +754,18 @@ msgstr "" #: extending/newtypes.rst:469 msgid "" -"*args* is a tuple containing the arguments to the call. You can use :c:func:" -"`PyArg_ParseTuple` to extract the arguments." +"*args* is a tuple containing the arguments to the call. You can " +"use :c:func:`PyArg_ParseTuple` to extract the arguments." msgstr "" #: extending/newtypes.rst:472 msgid "" "*kwds* 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." +"``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 "" #: extending/newtypes.rst:478 @@ -798,16 +806,17 @@ msgid "" "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``. :c:member:`~PyTypeObject.tp_iter` " -"corresponds to the Python :meth:`~object.__iter__` method, while :c:member:" -"`~PyTypeObject.tp_iternext` corresponds to the Python :meth:`~iterator." -"__next__` method." +"corresponds to the Python :meth:`~object.__iter__` method, " +"while :c:member:`~PyTypeObject.tp_iternext` corresponds to the " +"Python :meth:`~iterator.__next__` method." msgstr "" #: extending/newtypes.rst:511 msgid "" -"Any :term:`iterable` object must implement the :c:member:`~PyTypeObject." -"tp_iter` handler, which must return an :term:`iterator` object. Here the " -"same guidelines apply as for Python classes:" +"Any :term:`iterable` object must implement " +"the :c:member:`~PyTypeObject.tp_iter` handler, which must return " +"an :term:`iterator` object. Here the same guidelines apply as for Python " +"classes:" msgstr "" #: extending/newtypes.rst:515 @@ -820,24 +829,27 @@ msgstr "" #: extending/newtypes.rst:518 msgid "" "Objects which can only be iterated over once (usually due to side effects of " -"iteration, such as file objects) can implement :c:member:`~PyTypeObject." -"tp_iter` by returning a new reference to themselves -- and should also " -"therefore implement the :c:member:`~PyTypeObject.tp_iternext` handler." +"iteration, such as file objects) can " +"implement :c:member:`~PyTypeObject.tp_iter` by returning a new reference to " +"themselves -- and should also therefore implement " +"the :c:member:`~PyTypeObject.tp_iternext` handler." msgstr "" #: extending/newtypes.rst:523 msgid "" -"Any :term:`iterator` object should implement both :c:member:`~PyTypeObject." -"tp_iter` and :c:member:`~PyTypeObject.tp_iternext`. An iterator's :c:member:" -"`~PyTypeObject.tp_iter` handler should return a new reference to the " -"iterator. Its :c:member:`~PyTypeObject.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, :c:member:`~PyTypeObject.tp_iternext` may " -"return ``NULL`` without setting an exception, or it may set :exc:" -"`StopIteration` *in addition* to returning ``NULL``; avoiding the exception " -"can yield slightly better performance. If an actual error occurs, :c:member:" -"`~PyTypeObject.tp_iternext` should always set an exception and return " -"``NULL``." +"Any :term:`iterator` object should implement " +"both :c:member:`~PyTypeObject.tp_iter` " +"and :c:member:`~PyTypeObject.tp_iternext`. An " +"iterator's :c:member:`~PyTypeObject.tp_iter` handler should return a new " +"reference to the iterator. Its :c:member:`~PyTypeObject.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, :c:member:`~PyTypeObject.tp_iternext` may return ``NULL`` without " +"setting an exception, or it may set :exc:`StopIteration` *in addition* to " +"returning ``NULL``; avoiding the exception can yield slightly better " +"performance. If an actual error " +"occurs, :c:member:`~PyTypeObject.tp_iternext` should always set an exception " +"and return ``NULL``." msgstr "" #: extending/newtypes.rst:539 diff --git a/extending/newtypes_tutorial.po b/extending/newtypes_tutorial.po index 6463365c2..e40aa26c9 100644 --- a/extending/newtypes_tutorial.po +++ b/extending/newtypes_tutorial.po @@ -35,14 +35,14 @@ msgstr "" #: extending/newtypes_tutorial.rst:26 msgid "" -"The :term:`CPython` runtime sees all Python objects as variables of type :c:" -"expr:`PyObject*`, which serves as a \"base type\" for all Python objects. " -"The :c:type:`PyObject` structure itself only contains the object's :term:" -"`reference count` and a pointer to the object's \"type object\". This is " -"where the action is; the type object determines which (C) functions get " -"called by the interpreter when, for instance, an attribute gets looked up on " -"an object, a method called, or it is multiplied by another object. These C " -"functions are called \"type methods\"." +"The :term:`CPython` runtime sees all Python objects as variables of " +"type :c:expr:`PyObject*`, which serves as a \"base type\" for all Python " +"objects. The :c:type:`PyObject` structure itself only contains the " +"object's :term:`reference count` and a pointer to the object's \"type " +"object\". This is where the action is; the type object determines which (C) " +"functions get called by the interpreter when, for instance, an attribute " +"gets looked up on an object, a method called, or it is multiplied by another " +"object. These C functions are called \"type methods\"." msgstr "" #: extending/newtypes_tutorial.rst:35 @@ -62,8 +62,8 @@ msgstr "" msgid "" "What we're showing here is the traditional way of defining *static* " "extension types. It should be adequate for most uses. The C API also " -"allows defining heap-allocated extension types using the :c:func:" -"`PyType_FromSpec` function, which isn't covered in this tutorial." +"allows defining heap-allocated extension types using " +"the :c:func:`PyType_FromSpec` function, which isn't covered in this tutorial." msgstr "" #: extending/newtypes_tutorial.rst:48 @@ -251,9 +251,10 @@ msgstr "" 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:`!" -"custom` and the type is :class:`!Custom`, so we set the type name to :class:" -"`!custom.Custom`. Using the real dotted import path is important to make " -"your type compatible with the :mod:`pydoc` and :mod:`pickle` modules. ::" +"custom` and the type is :class:`!Custom`, so we set the type name " +"to :class:`!custom.Custom`. Using the real dotted import path is important " +"to make your type compatible with the :mod:`pydoc` and :mod:`pickle` " +"modules. ::" msgstr "" #: extending/newtypes_tutorial.rst:135 @@ -264,9 +265,9 @@ msgstr "" #: extending/newtypes_tutorial.rst:138 msgid "" -"This is so that Python knows how much memory to allocate when creating new :" -"class:`!Custom` instances. :c:member:`~PyTypeObject.tp_itemsize` is only " -"used for variable-sized objects and should otherwise be zero." +"This is so that Python knows how much memory to allocate when creating " +"new :class:`!Custom` instances. :c:member:`~PyTypeObject.tp_itemsize` is " +"only used for variable-sized objects and should otherwise be zero." msgstr "" #: extending/newtypes_tutorial.rst:144 @@ -309,11 +310,11 @@ msgstr "" #: extending/newtypes_tutorial.rst:166 msgid "" -"To enable object creation, we have to provide a :c:member:`~PyTypeObject." -"tp_new` handler. This is the equivalent of the Python method :meth:`~object." -"__new__`, but has to be specified explicitly. In this case, we can just use " -"the default implementation provided by the API function :c:func:" -"`PyType_GenericNew`. ::" +"To enable object creation, we have to provide " +"a :c:member:`~PyTypeObject.tp_new` handler. This is the equivalent of the " +"Python method :meth:`~object.__new__`, but has to be specified explicitly. " +"In this case, we can just use the default implementation provided by the API " +"function :c:func:`PyType_GenericNew`. ::" msgstr "" #: extending/newtypes_tutorial.rst:171 @@ -322,8 +323,8 @@ msgstr "" #: extending/newtypes_tutorial.rst:173 msgid "" -"Everything else in the file should be familiar, except for some code in :c:" -"func:`!PyInit_custom`::" +"Everything else in the file should be familiar, except for some code " +"in :c:func:`!PyInit_custom`::" msgstr "" #: extending/newtypes_tutorial.rst:176 @@ -351,8 +352,8 @@ msgstr "" #: extending/newtypes_tutorial.rst:190 msgid "" -"This adds the type to the module dictionary. This allows us to create :" -"class:`!Custom` instances by calling the :class:`!Custom` class:" +"This adds the type to the module dictionary. This allows us to " +"create :class:`!Custom` instances by calling the :class:`!Custom` class:" msgstr "" #: extending/newtypes_tutorial.rst:193 @@ -612,13 +613,13 @@ msgstr "" #: extending/newtypes_tutorial.rst:266 msgid "" -"This method first clears the reference counts of the two Python attributes. :" -"c:func:`Py_XDECREF` correctly handles the case where its argument is " -"``NULL`` (which might happen here if ``tp_new`` failed midway). It then " -"calls the :c:member:`~PyTypeObject.tp_free` member of the object's type " -"(computed by ``Py_TYPE(self)``) to free the object's memory. Note that the " -"object's type might not be :class:`!CustomType`, because the object may be " -"an instance of a subclass." +"This method first clears the reference counts of the two Python " +"attributes. :c:func:`Py_XDECREF` correctly handles the case where its " +"argument is ``NULL`` (which might happen here if ``tp_new`` failed midway). " +"It then calls the :c:member:`~PyTypeObject.tp_free` member of the object's " +"type (computed by ``Py_TYPE(self)``) to free the object's memory. Note that " +"the object's type might not be :class:`!CustomType`, because the object may " +"be an instance of a subclass." msgstr "" #: extending/newtypes_tutorial.rst:275 @@ -671,12 +672,13 @@ msgstr "" #: extending/newtypes_tutorial.rst:309 msgid "" "The ``tp_new`` handler is responsible for creating (as opposed to " -"initializing) objects of the type. It is exposed in Python as the :meth:" -"`~object.__new__` method. It is not required to define a ``tp_new`` member, " -"and indeed many extension types will simply reuse :c:func:" -"`PyType_GenericNew` as done in the first version of the :class:`!Custom` " -"type above. In this case, we use the ``tp_new`` handler to initialize the " -"``first`` and ``last`` attributes to non-``NULL`` default values." +"initializing) objects of the type. It is exposed in Python as " +"the :meth:`~object.__new__` method. It is not required to define a " +"``tp_new`` member, and indeed many extension types will simply " +"reuse :c:func:`PyType_GenericNew` as done in the first version of " +"the :class:`!Custom` type above. In this case, we use the ``tp_new`` " +"handler to initialize the ``first`` and ``last`` attributes to non-``NULL`` " +"default values." msgstr "" #: extending/newtypes_tutorial.rst:317 @@ -685,8 +687,8 @@ msgid "" "``CustomType``, if a subclass is instantiated) and any arguments passed when " "the type was called, and is expected to return the instance created. " "``tp_new`` handlers always accept positional and keyword arguments, but they " -"often ignore the arguments, leaving the argument handling to initializer (a." -"k.a. ``tp_init`` in C or ``__init__`` in Python) methods." +"often ignore the arguments, leaving the argument handling to initializer " +"(a.k.a. ``tp_init`` in C or ``__init__`` in Python) methods." msgstr "" #: extending/newtypes_tutorial.rst:325 @@ -707,8 +709,9 @@ msgstr "" #: extending/newtypes_tutorial.rst:333 msgid "" -"Since memory allocation may fail, we must check the :c:member:`~PyTypeObject." -"tp_alloc` result against ``NULL`` before proceeding." +"Since memory allocation may fail, we must check " +"the :c:member:`~PyTypeObject.tp_alloc` result against ``NULL`` before " +"proceeding." msgstr "" #: extending/newtypes_tutorial.rst:337 @@ -722,14 +725,15 @@ msgstr "" #: extending/newtypes_tutorial.rst:343 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:`~object." -"__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`.)" +"that calls a base type's :c:member:`~PyTypeObject.tp_new` " +"or :meth:`~object.__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 "" #: extending/newtypes_tutorial.rst:353 @@ -777,10 +781,10 @@ msgstr "" #: extending/newtypes_tutorial.rst:386 msgid "" -"The :c:member:`~PyTypeObject.tp_init` slot is exposed in Python as the :meth:" -"`~object.__init__` method. It is used to initialize an object after it's " -"created. Initializers always accept positional and keyword arguments, and " -"they should return either ``0`` on success or ``-1`` on error." +"The :c:member:`~PyTypeObject.tp_init` slot is exposed in Python as " +"the :meth:`~object.__init__` method. It is used to initialize an object " +"after it's created. Initializers always accept positional and keyword " +"arguments, and they should return either ``0`` on success or ``-1`` on error." msgstr "" #: extending/newtypes_tutorial.rst:391 @@ -826,15 +830,15 @@ msgstr "" #: extending/newtypes_tutorial.rst:418 msgid "" -"when we know that deallocation of the object [#]_ will neither release the :" -"term:`GIL` nor cause any calls back into our type's code;" +"when we know that deallocation of the object [#]_ will neither release " +"the :term:`GIL` nor cause any calls back into our type's code;" msgstr "" #: extending/newtypes_tutorial.rst:421 msgid "" -"when decrementing a reference count in a :c:member:`~PyTypeObject." -"tp_dealloc` handler on a type which doesn't support cyclic garbage " -"collection [#]_." +"when decrementing a reference count in " +"a :c:member:`~PyTypeObject.tp_dealloc` handler on a type which doesn't " +"support cyclic garbage collection [#]_." msgstr "" #: extending/newtypes_tutorial.rst:424 @@ -908,12 +912,12 @@ msgstr "" #: extending/newtypes_tutorial.rst:469 msgid "" -"The method is implemented as a C function that takes a :class:`!Custom` (or :" -"class:`!Custom` 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:" +"The method is implemented as a C function that takes a :class:`!Custom` " +"(or :class:`!Custom` 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 "" #: extending/newtypes_tutorial.rst:476 @@ -924,11 +928,11 @@ msgstr "" #: extending/newtypes_tutorial.rst:481 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." +"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 "" #: extending/newtypes_tutorial.rst:487 @@ -1005,9 +1009,9 @@ msgstr "" msgid "" "In this section, we'll provide finer control over how the :attr:`!first` " "and :attr:`!last` attributes are set in the :class:`!Custom` 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." +"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 "" #: extending/newtypes_tutorial.rst:540 @@ -1369,9 +1373,10 @@ msgstr "" msgid "" "In the second version of the :class:`!Custom` example, we allowed any kind " "of object to be stored in the :attr:`!first` or :attr:`!last` attributes " -"[#]_. Besides, in the second and third versions, we allowed subclassing :" -"class:`!Custom`, and subclasses may add arbitrary attributes. For any of " -"those two reasons, :class:`!Custom` objects can participate in cycles:" +"[#]_. Besides, in the second and third versions, we allowed " +"subclassing :class:`!Custom`, and subclasses may add arbitrary attributes. " +"For any of those two reasons, :class:`!Custom` objects can participate in " +"cycles:" msgstr "" #: extending/newtypes_tutorial.rst:675 @@ -1616,11 +1621,11 @@ msgstr "" #: extending/newtypes_tutorial.rst:710 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." +"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 "" #: extending/newtypes_tutorial.rst:716 @@ -1688,9 +1693,9 @@ msgstr "" #: extending/newtypes_tutorial.rst:758 msgid "" -"Nevertheless, it is much easier and less error-prone to always use :c:func:" -"`Py_CLEAR` when deleting an attribute. Don't try to micro-optimize at the " -"expense of robustness!" +"Nevertheless, it is much easier and less error-prone to always " +"use :c:func:`Py_CLEAR` when deleting an attribute. Don't try to micro-" +"optimize at the expense of robustness!" msgstr "" #: extending/newtypes_tutorial.rst:762 @@ -1699,8 +1704,8 @@ msgid "" "attributes. It means the circular GC can be triggered inside the function. " "Since the GC assumes reference count is not zero, we need to untrack the " "object from the GC by calling :c:func:`PyObject_GC_UnTrack` before clearing " -"members. Here is our reimplemented deallocator using :c:func:" -"`PyObject_GC_UnTrack` and ``Custom_clear``::" +"members. Here is our reimplemented deallocator " +"using :c:func:`PyObject_GC_UnTrack` and ``Custom_clear``::" msgstr "" #: extending/newtypes_tutorial.rst:769 @@ -1726,9 +1731,10 @@ msgstr "" #: extending/newtypes_tutorial.rst:781 msgid "" -"That's pretty much it. If we had written custom :c:member:`~PyTypeObject." -"tp_alloc` or :c:member:`~PyTypeObject.tp_free` handlers, we'd need to modify " -"them for cyclic garbage collection. Most extensions will use the versions " +"That's pretty much it. If we had written " +"custom :c:member:`~PyTypeObject.tp_alloc` " +"or :c:member:`~PyTypeObject.tp_free` handlers, we'd need to modify them for " +"cyclic garbage collection. Most extensions will use the versions " "automatically provided." msgstr "" @@ -1888,8 +1894,9 @@ msgstr "" #: extending/newtypes_tutorial.rst:841 msgid "" -"This pattern is important when writing a type with custom :c:member:" -"`~PyTypeObject.tp_new` and :c:member:`~PyTypeObject.tp_dealloc` members. " +"This pattern is important when writing a type with " +"custom :c:member:`~PyTypeObject.tp_new` " +"and :c:member:`~PyTypeObject.tp_dealloc` members. " "The :c:member:`~PyTypeObject.tp_new` handler should not actually create the " "memory for the object with its :c:member:`~PyTypeObject.tp_alloc`, but let " "the base class handle it by calling its own :c:member:`~PyTypeObject.tp_new`." @@ -1897,11 +1904,11 @@ msgstr "" #: extending/newtypes_tutorial.rst:847 msgid "" -"The :c:type:`PyTypeObject` struct supports a :c:member:`~PyTypeObject." -"tp_base` specifying the type's concrete base class. Due to cross-platform " -"compiler issues, you can't fill that field directly with a reference to :c:" -"type:`PyList_Type`; it should be done later in the module initialization " -"function::" +"The :c:type:`PyTypeObject` struct supports " +"a :c:member:`~PyTypeObject.tp_base` specifying the type's concrete base " +"class. Due to cross-platform compiler issues, you can't fill that field " +"directly with a reference to :c:type:`PyList_Type`; it should be done later " +"in the module initialization function::" msgstr "" #: extending/newtypes_tutorial.rst:853 @@ -1932,11 +1939,11 @@ msgstr "" #: extending/newtypes_tutorial.rst:875 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 an " -"existing type, it is not necessary to fill out the :c:member:`~PyTypeObject." -"tp_alloc` slot with :c:func:`PyType_GenericNew` -- the allocation function " -"from the base type will be inherited." +"Before calling :c:func:`PyType_Ready`, the type structure must have " +"the :c:member:`~PyTypeObject.tp_base` slot filled in. When we are deriving " +"an existing type, it is not necessary to fill out " +"the :c:member:`~PyTypeObject.tp_alloc` slot with :c:func:`PyType_GenericNew` " +"-- the allocation function from the base type will be inherited." msgstr "" #: extending/newtypes_tutorial.rst:881 diff --git a/extending/windows.po b/extending/windows.po index 90bd2dc54..31f32af41 100644 --- a/extending/windows.po +++ b/extending/windows.po @@ -143,8 +143,8 @@ msgid "" "that object file." msgstr "" "Unix'te, birkaç nesne dosyasından (:file:`.o`) kod içeren yalnızca bir tür " -"kütüphane dosyası (:file:`.a`) vardır. Paylaşılan bir nesne dosyası (:file:" -"`.so`) oluşturmak için bağlantı adımı sırasında, bağlayıcı bir " +"kütüphane dosyası (:file:`.a`) vardır. Paylaşılan bir nesne dosyası " +"(:file:`.so`) oluşturmak için bağlantı adımı sırasında, bağlayıcı bir " "tanımlayıcının nerede tanımlandığını bilmediğini fark edebilir. Bağlayıcı " "bunu kütüphanelerdeki nesne dosyalarında arayacaktır; bulursa, o nesne " "dosyasındaki tüm kodu dahil edecektir." @@ -152,15 +152,15 @@ msgstr "" #: 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." +"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 "" "Windows'ta iki tür kütüphane vardır: statik kütüphane ve içe aktarma " "kütüphanesi (her ikisi de :file:`.lib` olarak adlandırılır). Statik " @@ -179,18 +179,20 @@ msgid "" "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." +"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 "" "Başka bir A kod bloğunu paylaşması gereken B ve C olmak üzere iki dinamik " -"yükleme modülü oluşturduğunuzu varsayalım. Unix'te :file:`B.so` ve :file:`C." -"so` için :file:`A.a` dosyasını bağlayıcıya aktarmazsınız; bu, iki kez dahil " -"edilmesine neden olur, böylece B ve C'nin her biri kendi kopyasına sahip " -"olur. Windows'ta, :file:`A.dll` dosyasını oluşturmak aynı zamanda :file:`A." -"lib` dosyasını da oluşturacaktır. B ve C için bağlayıcıya :file:`A.lib` " -"dosyasını geçirirsiniz. :file:`A.lib` kod içermez; sadece çalışma zamanında " -"A'nın koduna erişmek için kullanılacak bilgileri içerir." +"yükleme modülü oluşturduğunuzu varsayalım. Unix'te :file:`B.so` " +"ve :file:`C.so` için :file:`A.a` dosyasını bağlayıcıya aktarmazsınız; bu, " +"iki kez dahil edilmesine neden olur, böylece B ve C'nin her biri kendi " +"kopyasına sahip olur. Windows'ta, :file:`A.dll` dosyasını oluşturmak aynı " +"zamanda :file:`A.lib` dosyasını da oluşturacaktır. B ve C için " +"bağlayıcıya :file:`A.lib` dosyasını geçirirsiniz. :file:`A.lib` kod içermez; " +"sadece çalışma zamanında A'nın koduna erişmek için kullanılacak bilgileri " +"içerir." #: extending/windows.rst:94 msgid "" @@ -240,20 +242,20 @@ msgid "" "functions (such as :c:func:`PyArg_ParseTuple`), but it does know how to find " "the Python code thanks to :file:`pythonXY.lib`." msgstr "" -"İlk komut üç dosya oluşturdu: :file:`spam.obj`, :file:`spam.dll` ve :file:" -"`spam.lib`. :file:`Spam.dll` herhangi bir Python fonksiyonu içermiyor " -"(örneğin :c:func:`PyArg_ParseTuple`), ancak :file:`pythonXY.lib` sayesinde " -"Python kodunu nasıl bulacağını biliyor." +"İlk komut üç dosya oluşturdu: :file:`spam.obj`, :file:`spam.dll` " +"ve :file:`spam.lib`. :file:`Spam.dll` herhangi bir Python fonksiyonu " +"içermiyor (örneğin :c:func:`PyArg_ParseTuple`), ancak :file:`pythonXY.lib` " +"sayesinde Python kodunu nasıl bulacağını biliyor." #: extending/windows.rst:123 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." +"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 "" "İkinci komut, spam'den ve ayrıca Python çalıştırılabilir dosyasından gerekli " -"işlevleri nasıl bulacağını bilen :file:`ni.dll` (ve :file:`.obj` ve :file:`." -"lib`) oluşturdu." +"işlevleri nasıl bulacağını bilen :file:`ni.dll` (ve :file:`.obj` " +"ve :file:`.lib`) oluşturdu." #: extending/windows.rst:127 msgid "" diff --git a/faq/design.po b/faq/design.po index 1d44b5423..e8ea29f8b 100644 --- a/faq/design.po +++ b/faq/design.po @@ -109,12 +109,13 @@ msgstr "" #: faq/design.rst:65 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." +"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 "" #: faq/design.rst:72 @@ -282,12 +283,12 @@ msgstr "" msgid "" "(b) When I read code that says len(x) I *know* that it is asking for the " "length of something. This tells me two things: the result is an integer, and " -"the argument is some kind of container. To the contrary, when I read x." -"len(), I have to already know that x is some kind of container implementing " -"an interface or inheriting from a class that has a standard len(). Witness " -"the confusion we occasionally have when a class that is not implementing a " -"mapping has a get() or keys() method, or something that isn't a file has a " -"write() method." +"the argument is some kind of container. To the contrary, when I read " +"x.len(), I have to already know that x is some kind of container " +"implementing an interface or inheriting from a class that has a standard " +"len(). Witness the confusion we occasionally have when a class that is not " +"implementing a mapping has a get() or keys() method, or something that isn't " +"a file has a write() method." msgstr "" #: faq/design.rst:189 @@ -336,8 +337,9 @@ msgstr "" 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 ::" +"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 "" #: faq/design.rst:220 @@ -432,8 +434,8 @@ msgstr "" #: faq/design.rst:279 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::" +"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 "" #: faq/design.rst:282 @@ -639,10 +641,10 @@ msgstr "" 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, :func:`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." +"which are operated on one-by-one. For example, :func:`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 "" #: faq/design.rst:423 @@ -750,8 +752,8 @@ msgstr "" msgid "" "would raise a :exc:`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`." +"words, dictionary keys should be compared using ``==``, not " +"using :keyword:`is`." msgstr "" #: faq/design.rst:490 @@ -818,11 +820,11 @@ msgstr "" #: faq/design.rst:534 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." +"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 "" #: faq/design.rst:539 @@ -877,10 +879,10 @@ msgstr "" 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`." +"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 "" #: faq/design.rst:578 @@ -895,10 +897,10 @@ msgid "" "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." +"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 "" #: faq/design.rst:589 @@ -932,9 +934,9 @@ msgid "" "\"spaghetti\" code that was hard to understand and revise. In a high-level " "language, it is also unneeded as long as there are ways to branch (in " "Python, with :keyword:`if` statements and :keyword:`or`, :keyword:`and`, " -"and :keyword:`if`/:keyword:`else` expressions) and loop (with :keyword:" -"`while` and :keyword:`for` statements, possibly containing :keyword:" -"`continue` and :keyword:`break`)." +"and :keyword:`if`/:keyword:`else` expressions) and loop " +"(with :keyword:`while` and :keyword:`for` statements, possibly " +"containing :keyword:`continue` and :keyword:`break`)." msgstr "" #: faq/design.rst:614 @@ -1114,9 +1116,9 @@ msgstr "" msgid "" "For technical reasons, a generator used directly as a context manager would " "not work correctly. When, as is most common, a generator is used as an " -"iterator run to completion, no closing is needed. When it is, wrap it as :" -"func:`contextlib.closing(generator) ` in the :keyword:" -"`with` statement." +"iterator run to completion, no closing is needed. When it is, wrap it " +"as :func:`contextlib.closing(generator) ` in " +"the :keyword:`with` statement." msgstr "" #: faq/design.rst:730 diff --git a/faq/extending.po b/faq/extending.po index 69d77189b..b9145ff2a 100644 --- a/faq/extending.po +++ b/faq/extending.po @@ -32,8 +32,8 @@ msgstr "C'de kendi fonksiyonlarımı oluşturabilir miyim?" #: 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`." +"exceptions and even new types in C. This is explained in the " +"document :ref:`extending-index`." msgstr "" "Evet, C'de fonksiyonlar, değişkenler, istisnalar ve hatta yeni tipler içeren " "yerleşik modüller oluşturabilirsiniz. Bu konu :ref:`extending-index` " @@ -49,13 +49,13 @@ msgstr "C++'da kendi fonksiyonlarımı oluşturabilir miyim?" #: 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." +"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 "" -"Evet, C++'da bulunan C uyumluluk özelliklerini kullanarak. ``extern " -"\"C\" { ... }`` komutunu Python include dosyalarının etrafına yerleştirin ve " +"Evet, C++'da bulunan C uyumluluk özelliklerini kullanarak. ``extern \"C\" " +"{ ... }`` komutunu Python include dosyalarının etrafına yerleştirin ve " "Python yorumlayıcısı tarafından çağrılacak her fonksiyonun önüne ``extern " "\"C\"`` koyun. Yapıcıları olan global veya statik C++ nesneleri muhtemelen " "iyi bir fikir değildir." @@ -75,17 +75,17 @@ msgstr "" #: faq/extending.rst:44 #, fuzzy 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." +"`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 "" -"`Cython `_ ve akrabası `Pyrex `_ Python'un biraz değiştirilmiş " -"bir formunu kabul eden ve karşılık gelen C kodunu üreten derleyicilerdir. " -"Cython ve Pyrex, Python'un C API'ını öğrenmek zorunda kalmadan bir uzantı " -"yazmayı mümkün kılar." +"`Cython `_ ve akrabası `Pyrex `_ Python'un biraz " +"değiştirilmiş bir formunu kabul eden ve karşılık gelen C kodunu üreten " +"derleyicilerdir. Cython ve Pyrex, Python'un C API'ını öğrenmek zorunda " +"kalmadan bir uzantı yazmayı mümkün kılar." #: faq/extending.rst:50 #, fuzzy @@ -101,9 +101,9 @@ msgstr "" "Şu anda Python uzantısı bulunmayan bir C veya C++ kütüphanesine arayüz " "oluşturmanız gerekiyorsa, kütüphanenin veri türlerini ve işlevlerini `SWIG " "`_ gibi bir araçla sarmalamayı deneyebilirsiniz. `SIP " -"`__, `CXX `_ `Boost `_, veya `Weave `_ de C++ " +"`__, `CXX `_ `Boost `_, veya `Weave `_ de C++ " "kütüphanelerini sarmalamak için alternatiflerdir." #: faq/extending.rst:61 @@ -115,16 +115,16 @@ 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 :exc:`SyntaxError`). If you want more control, use :c:" -"func:`PyRun_String`; see the source for :c:func:`PyRun_SimpleString` in " -"``Python/pythonrun.c``." +"occurred (including :exc:`SyntaxError`). If you want more control, " +"use :c:func:`PyRun_String`; see the source for :c:func:`PyRun_SimpleString` " +"in ``Python/pythonrun.c``." msgstr "" "Bunu yapan en üst düzey fonksiyon :c:func:`PyRun_SimpleString` olup, " "``__main__`` modülü bağlamında çalıştırılmak üzere tek bir string argüman " "alır ve başarı için ``0``, bir istisna oluştuğunda (:exc:`SyntaxError` " -"dahil) ``-1`` döndürür. Daha fazla kontrol istiyorsanız, :c:func:" -"`PyRun_String` kullanın; :c:func:`PyRun_SimpleString` için ``Python/" -"pythonrun.c`` içindeki kaynağa bakın." +"dahil) ``-1`` döndürür. Daha fazla kontrol " +"istiyorsanız, :c:func:`PyRun_String` kullanın; :c:func:`PyRun_SimpleString` " +"için ``Python/pythonrun.c`` içindeki kaynağa bakın." #: faq/extending.rst:72 msgid "How can I evaluate an arbitrary Python expression from C?" @@ -149,8 +149,8 @@ msgstr "Bir Python nesnesinden C değerlerini nasıl çıkarabilirim?" 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:`PyList_Size` and :c:" -"func:`PyList_GetItem`." +"specified index. Lists have similar functions, :c:func:`PyList_Size` " +"and :c:func:`PyList_GetItem`." msgstr "" "Bu, nesnenin türüne bağlıdır. Eğer bir tuple ise, :c:func:`PyTuple_Size` " "uzunluğunu döndürür ve :c:func:`PyTuple_GetItem` belirtilen indeksteki öğeyi " @@ -160,25 +160,25 @@ msgstr "" #: faq/extending.rst:87 #, fuzzy 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." +"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 "" -"Baytlar için, :c:func:`PyBytes_Size` uzunluğunu döndürür ve :c:func:" -"`PyBytes_AsStringAndSize` değerine ve uzunluğuna bir işaretçi sağlar. " -"Python bayt nesnelerinin null bayt içerebileceğini unutmayın, bu nedenle " -"C'nin :c:func:`strlen` özelliği kullanılmamalıdır." +"Baytlar için, :c:func:`PyBytes_Size` uzunluğunu döndürür " +"ve :c:func:`PyBytes_AsStringAndSize` değerine ve uzunluğuna bir işaretçi " +"sağlar. Python bayt nesnelerinin null bayt içerebileceğini unutmayın, bu " +"nedenle C'nin :c:func:`strlen` özelliği kullanılmamalıdır." #: 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." +"use :c:func:`PyBytes_Check`, :c:func:`PyTuple_Check`, :c:func:`PyList_Check`, " +"etc." msgstr "" "Bir nesnenin türünü test etmek için, önce ``NULL`` olmadığından emin olun ve " -"ardından :c:func:`PyBytes_Check`, :c:func:`PyTuple_Check`, :c:func:" -"`PyList_Check` vb. kullanın." +"ardından :c:func:`PyBytes_Check`, :c:func:`PyTuple_Check`, :c:func:`PyList_Check` " +"vb. kullanın." #: faq/extending.rst:95 msgid "" @@ -191,11 +191,11 @@ msgid "" msgstr "" "Ayrıca Python nesneleri için 'abstract' arayüzü tarafından sağlanan üst " "düzey bir API de vardır -- daha fazla ayrıntı için ``Include/abstract.h`` " -"dosyasını okuyun. :c:func:`PySequence_Length`, :c:func:" -"`PySequence_GetItem`, vb. gibi çağrıları kullanarak her türlü Python dizisi " -"ile arayüz oluşturmanın yanı sıra sayılar (:c:func:`PyNumber_Index` ve " -"diğerleri) ve PyMapping API'lerindeki eşlemeler gibi diğer birçok yararlı " -"protokolü de sağlar." +"dosyasını " +"okuyun. :c:func:`PySequence_Length`, :c:func:`PySequence_GetItem`, vb. gibi " +"çağrıları kullanarak her türlü Python dizisi ile arayüz oluşturmanın yanı " +"sıra sayılar (:c:func:`PyNumber_Index` ve diğerleri) ve PyMapping " +"API'lerindeki eşlemeler gibi diğer birçok yararlı protokolü de sağlar." #: faq/extending.rst:104 msgid "How do I use Py_BuildValue() to create a tuple of arbitrary length?" @@ -219,8 +219,8 @@ msgid "" "the argument values::" msgstr "" ":c:func:`PyObject_CallMethod` fonksiyonu, bir nesnenin rastgele bir metodunu " -"çağırmak için kullanılabilir. Parametreler nesne, çağrılacak yöntemin adı, :" -"c:func:`Py_BuildValue` ile kullanılan gibi bir string ve değişken " +"çağırmak için kullanılabilir. Parametreler nesne, çağrılacak yöntemin " +"adı, :c:func:`Py_BuildValue` ile kullanılan gibi bir string ve değişken " "değerleridir::" #: faq/extending.rst:117 @@ -344,17 +344,17 @@ msgstr "" #: 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`." +"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 "" "Modül henüz içe aktarılmamışsa (yani :data:`sys.modules` içinde henüz mevcut " -"değilse), bu modülü başlatır; aksi takdirde sadece ``sys." -"modules[\"\"]`` değerini döndürür. Modülü herhangi bir isim " -"alanına girmediğine dikkat edin -- sadece başlatıldığından ve :data:`sys." -"modules` içinde saklandığından emin olur." +"değilse), bu modülü başlatır; aksi takdirde sadece " +"``sys.modules[\"\"]`` değerini döndürür. Modülü herhangi bir " +"isim alanına girmediğine dikkat edin -- sadece başlatıldığından " +"ve :data:`sys.modules` içinde saklandığından emin olur." #: faq/extending.rst:194 msgid "" @@ -514,10 +514,10 @@ msgid "" msgstr "" "Bunu C'de yapmanın en kolay yolu :c:func:`PyRun_InteractiveLoop` çağırmak " "(belki ayrı bir iş parçacığında) ve Python yorumlayıcısının girdiyi sizin " -"için işlemesine izin vermektir. Ayrıca :c:func:" -"`PyOS_ReadlineFunctionPointer` 'ı özel girdi fonksiyonunuza işaret edecek " -"şekilde ayarlayabilirsiniz. Daha fazla ipucu için ``Modules/readline.c`` ve " -"``Parser/myreadline.c`` dosyalarına bakın." +"için işlemesine izin vermektir. " +"Ayrıca :c:func:`PyOS_ReadlineFunctionPointer` 'ı özel girdi fonksiyonunuza " +"işaret edecek şekilde ayarlayabilirsiniz. Daha fazla ipucu için ``Modules/" +"readline.c`` ve ``Parser/myreadline.c`` dosyalarına bakın." #: faq/extending.rst:275 msgid "How do I find undefined g++ symbols __builtin_new or __pure_virtual?" @@ -546,44 +546,45 @@ msgstr "" #: faq/extending.rst:285 msgid "" -"Yes, you can inherit from built-in classes such as :class:`int`, :class:" -"`list`, :class:`dict`, etc." +"Yes, you can inherit from built-in classes such " +"as :class:`int`, :class:`list`, :class:`dict`, etc." msgstr "" "Evet, :class:`int`, :class:`list`, :class:`dict`, vb. gibi yerleşik " "sınıflardan miras alabilirsiniz." #: faq/extending.rst:288 msgid "" -"The Boost Python Library (BPL, https://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)." +"The Boost Python Library (BPL, https://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 "" -"Boost Python Kütüphanesi (BPL, http://www.boost.org/libs/python/doc/index." -"html) bunu C++'dan yapmanın bir yolunu sağlar (yani BPL'yi kullanarak C++'da " -"yazılmış bir uzantı sınıfından miras alabilirsiniz)." +"Boost Python Kütüphanesi (BPL, http://www.boost.org/libs/python/doc/" +"index.html) bunu C++'dan yapmanın bir yolunu sağlar (yani BPL'yi kullanarak " +"C++'da yazılmış bir uzantı sınıfından miras alabilirsiniz)." #~ 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. A 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())::" +#~ "same thread as your rest application and you can't allow " +#~ "the :c:func:`PyRun_InteractiveLoop` to stop while waiting for user input. " +#~ "A 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 "" #~ "Ancak bazen gömülü Python yorumlayıcısını geri kalan uygulamanızla aynı " -#~ "_thread_ (iş parçacığı) içerisinde çalıştırmanız gerekir ve :c:func:" -#~ "`PyRun_InteractiveLoop` 'un kullanıcı girdisini beklerken durmasına izin " -#~ "veremezsiniz. Çözümlerden biri, alınan dizeyi :c:func:`Py_CompileString` " -#~ "ile derlemeye çalışmaktır. Eğer hatasız derlenirse, :c:func:" -#~ "`PyEval_EvalCode` çağrısı ile dönen kod nesnesini çalıştırmayı deneyin. " -#~ "Aksi takdirde girdiyi daha sonrası için saklayın. Derleme başarısız " -#~ "olursa, bunun bir hata mı olduğunu yoksa daha fazla girdi mi gerektiğini " -#~ "öğrenin - istisna tuple'ından mesaj string'ini çıkararak ve \"ayrıştırma " -#~ "sırasında beklenmedik EOF\" dizesiyle karşılaştırarak. İşte GNU readline " -#~ "kütüphanesini kullanan tam bir örnek (readline()'ı çağırırken " -#~ "**SIGINT**'i göz ardı etmek isteyebilirsiniz)::" +#~ "_thread_ (iş parçacığı) içerisinde çalıştırmanız gerekir " +#~ "ve :c:func:`PyRun_InteractiveLoop` 'un kullanıcı girdisini beklerken " +#~ "durmasına izin veremezsiniz. Çözümlerden biri, alınan " +#~ "dizeyi :c:func:`Py_CompileString` ile derlemeye çalışmaktır. Eğer hatasız " +#~ "derlenirse, :c:func:`PyEval_EvalCode` çağrısı ile dönen kod nesnesini " +#~ "çalıştırmayı deneyin. Aksi takdirde girdiyi daha sonrası için saklayın. " +#~ "Derleme başarısız olursa, bunun bir hata mı olduğunu yoksa daha fazla " +#~ "girdi mi gerektiğini öğrenin - istisna tuple'ından mesaj string'ini " +#~ "çıkararak ve \"ayrıştırma sırasında beklenmedik EOF\" dizesiyle " +#~ "karşılaştırarak. İşte GNU readline kütüphanesini kullanan tam bir örnek " +#~ "(readline()'ı çağırırken **SIGINT**'i göz ardı etmek isteyebilirsiniz)::" diff --git a/faq/general.po b/faq/general.po index a4f73ce1a..23ec9c666 100644 --- a/faq/general.po +++ b/faq/general.po @@ -69,8 +69,8 @@ msgstr "" #: faq/general.rst:42 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 `_." +"it helpful, please contribute via `the PSF donation page `_." msgstr "" #: faq/general.rst:48 @@ -336,16 +336,17 @@ 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." +"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 "" #: faq/general.rst:217 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 " +"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 "" @@ -362,9 +363,9 @@ msgstr "" #: faq/general.rst:229 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." +"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 "" #: faq/general.rst:234 @@ -379,8 +380,8 @@ msgstr "" #: faq/general.rst:241 msgid "" -"To report a bug or submit a patch, use the issue tracker at https://github." -"com/python/cpython/issues." +"To report a bug or submit a patch, use the issue tracker at https://" +"github.com/python/cpython/issues." msgstr "" #: faq/general.rst:244 @@ -433,8 +434,8 @@ msgstr "" #: faq/general.rst:274 msgid "" "The Python project's infrastructure is located all over the world and is " -"managed by the Python Infrastructure Team. Details `here `__." +"managed by the Python Infrastructure Team. Details `here `__." msgstr "" #: faq/general.rst:279 @@ -444,8 +445,8 @@ msgstr "" #: faq/general.rst:281 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. " +"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 "" @@ -521,19 +522,19 @@ msgstr "" #: faq/general.rst:333 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 " +"Python. Consulting the proceedings for `past Python conferences `_ will reveal contributions from many " "different companies and organizations." msgstr "" #: faq/general.rst:338 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." +"`_ 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 "" #: faq/general.rst:347 @@ -551,8 +552,8 @@ msgstr "" #: faq/general.rst:355 msgid "" -"New development is discussed on `the python-dev mailing list `_." +"New development is discussed on `the python-dev mailing list `_." msgstr "" #: faq/general.rst:360 diff --git a/faq/gui.po b/faq/gui.po index 2c2c7b7ca..094aaa8bd 100644 --- a/faq/gui.po +++ b/faq/gui.po @@ -39,8 +39,9 @@ msgid "" "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 macOS, Windows, and Unix platforms." +"including pointers to the source, see the `Tcl/Tk home page `_. Tcl/Tk is fully portable to the macOS, Windows, and Unix " +"platforms." msgstr "" "Python'un standart yapıları, :ref:`tkinter ` adlı Tcl/Tk pencere " "öğesi kümesine yönelik nesne yönelimli bir arayüz içerir. Bu muhtemelen " @@ -113,9 +114,9 @@ msgid "" "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 "" -"SAM etkinken Tix oluşturun, Python'un :file:`Modules/tkappinit.c` içindeki :" -"c:func:`Tclsam_init` vb. için uygun çağrıyı yapın ve libtclsam ve libtksam " -"ile bağlantı kurun (Tix kütüphanelerini da dahil edebilirsiniz) )." +"SAM etkinken Tix oluşturun, Python'un :file:`Modules/tkappinit.c` " +"içindeki :c:func:`Tclsam_init` vb. için uygun çağrıyı yapın ve libtclsam ve " +"libtksam ile bağlantı kurun (Tix kütüphanelerini da dahil edebilirsiniz) )." #: faq/gui.rst:61 msgid "Can I have Tk events handled while waiting for I/O?" @@ -131,10 +132,10 @@ msgid "" "file descriptor. See :ref:`tkinter-file-handlers`." msgstr "" "Windows dışındaki platformlarda, evet ve iş parçacığına bile ihtiyacınız " -"yok! Ancak G/Ç kodunuzu tekrardan yapılandırmanız gerekecek. Tk, Xt'nin :c:" -"func:`XtAddInput()` çağrısına eş değerdir; bu, bir dosya tanıtıcısında G/Ç " -"mümkün olduğunda Tk ana döngüsünden çağrılacak bir geri arama işlevini " -"kaydetmenize olanak tanır. Bkz. :ref:`tkinter-file-handlers`." +"yok! Ancak G/Ç kodunuzu tekrardan yapılandırmanız gerekecek. Tk, " +"Xt'nin :c:func:`XtAddInput()` çağrısına eş değerdir; bu, bir dosya " +"tanıtıcısında G/Ç mümkün olduğunda Tk ana döngüsünden çağrılacak bir geri " +"arama işlevini kaydetmenize olanak tanır. Bkz. :ref:`tkinter-file-handlers`." #: faq/gui.rst:71 msgid "I can't get key bindings to work in Tkinter: why?" diff --git a/faq/library.po b/faq/library.po index c3d4f13e1..76a3f6aaf 100644 --- a/faq/library.po +++ b/faq/library.po @@ -41,8 +41,8 @@ msgstr "" #: faq/library.rst:21 msgid "" -"For third-party packages, search the `Python Package Index `_ or try `Google `_ or another web search " +"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 "" @@ -55,9 +55,9 @@ msgstr "" 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)." +"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 "" #: faq/library.rst:35 @@ -391,10 +391,10 @@ msgstr "" #: faq/library.rst:282 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." +"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 "" #: faq/library.rst:290 @@ -483,8 +483,8 @@ msgstr "" #: faq/library.rst:358 msgid "" -"Consult the module's documentation for more details; the :class:`~queue." -"Queue` class provides a featureful interface." +"Consult the module's documentation for more details; " +"the :class:`~queue.Queue` class provides a featureful interface." msgstr "" #: faq/library.rst:363 @@ -544,10 +544,10 @@ msgstr "" #: faq/library.rst:399 msgid "" -"Operations that replace other objects may invoke those other objects' :meth:" -"`~object.__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!" +"Operations that replace other objects may invoke those other " +"objects' :meth:`~object.__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 "" #: faq/library.rst:406 @@ -578,11 +578,11 @@ msgstr "" 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." +"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 "" #: faq/library.rst:431 @@ -590,8 +590,8 @@ 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." +"work done. Some standard library modules such as :mod:`zlib` " +"and :mod:`hashlib` already do this." msgstr "" #: faq/library.rst:437 @@ -631,8 +631,9 @@ msgstr "" #: faq/library.rst:461 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." +"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 "" #: faq/library.rst:465 @@ -652,15 +653,15 @@ msgstr "" 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)." +"There's also ``os.ftruncate(fd, offset)`` for files opened " +"with :func:`os.open`, where *fd* is the file descriptor (a small integer)." msgstr "" #: faq/library.rst:478 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`." +"files including :func:`~shutil.copyfile`, :func:`~shutil.copytree`, " +"and :func:`~shutil.rmtree`." msgstr "" #: faq/library.rst:484 @@ -684,9 +685,9 @@ msgstr "" #: faq/library.rst:499 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." +"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 "" #: faq/library.rst:503 @@ -734,8 +735,8 @@ 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)``." +"function. Thus, to read *n* bytes from a pipe *p* created " +"with :func:`os.popen`, you need to use ``p.read(n)``." msgstr "" #: faq/library.rst:617 @@ -827,8 +828,8 @@ msgstr "" #: faq/library.rst:671 msgid "" "Cameron Laird maintains a useful set of pages about Python web technologies " -"at https://web.archive.org/web/20210224183619/http://phaseit.net/claird/comp." -"lang.python/web_python." +"at https://web.archive.org/web/20210224183619/http://phaseit.net/claird/" +"comp.lang.python/web_python." msgstr "" #: faq/library.rst:676 @@ -971,10 +972,10 @@ msgstr "" #: faq/library.rst:774 msgid "" "You can use the :meth:`~socket.socket.connect_ex` method to avoid creating " -"an exception. It will just return the errno value. To poll, you can call :" -"meth:`~socket.socket.connect_ex` again later -- ``0`` or ``errno.EISCONN`` " -"indicate that you're connected -- or you can pass this socket to :meth:" -"`select.select` to check if it's writable." +"an exception. It will just return the errno value. To poll, you can " +"call :meth:`~socket.socket.connect_ex` again later -- ``0`` or " +"``errno.EISCONN`` indicate that you're connected -- or you can pass this " +"socket to :meth:`select.select` to check if it's writable." msgstr "" #: faq/library.rst:782 @@ -1000,9 +1001,9 @@ msgstr "" #: faq/library.rst:797 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." +"` are also included with standard Python. There is also " +"the :mod:`sqlite3` module, which provides a lightweight disk-based " +"relational database." msgstr "" #: faq/library.rst:802 @@ -1019,8 +1020,8 @@ msgstr "" #: faq/library.rst:810 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 " +"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 "" diff --git a/faq/programming.po b/faq/programming.po index 19a66cad6..bc78ca166 100644 --- a/faq/programming.po +++ b/faq/programming.po @@ -40,8 +40,8 @@ msgstr "" #: faq/programming.rst:19 msgid "" -"Several debuggers for Python are described below, and the built-in function :" -"func:`breakpoint` allows you to drop into any of them." +"Several debuggers for Python are described below, and the built-in " +"function :func:`breakpoint` allows you to drop into any of them." msgstr "" #: faq/programming.rst:22 @@ -441,8 +441,8 @@ msgstr "" #: faq/programming.rst:301 msgid "" -"standard library modules -- e.g. :mod:`sys`, :mod:`os`, :mod:`argparse`, :" -"mod:`re`" +"standard library modules -- " +"e.g. :mod:`sys`, :mod:`os`, :mod:`argparse`, :mod:`re`" msgstr "" #: faq/programming.rst:302 @@ -626,9 +626,9 @@ msgstr "" 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 :term:" -"`kind of arguments ` a function can accept. For example, given " -"the function definition::" +"actually passed to a function when calling it. Parameters define " +"what :term:`kind of arguments ` a function can accept. For " +"example, given the function definition::" msgstr "" #: faq/programming.rst:423 @@ -973,8 +973,8 @@ msgstr "" #: faq/programming.rst:641 msgid "" -"Some objects can be copied more easily. Dictionaries have a :meth:`~dict." -"copy` method::" +"Some objects can be copied more easily. Dictionaries have " +"a :meth:`~dict.copy` method::" msgstr "" #: faq/programming.rst:644 @@ -1291,8 +1291,8 @@ msgstr "" #: faq/programming.rst:850 msgid "" -"Trying to lookup an ``int`` literal attribute in the normal manner gives a :" -"exc:`SyntaxError` because the period is seen as a decimal point::" +"Trying to lookup an ``int`` literal attribute in the normal manner gives " +"a :exc:`SyntaxError` because the period is seen as a decimal point::" msgstr "" #: faq/programming.rst:853 @@ -1358,8 +1358,8 @@ msgid "" "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'``." +"sections, e.g. ``\"{:04d}\".format(144)`` yields ``'0144'`` and ``\"{:.3f}" +"\".format(1.0/3.0)`` yields ``'0.333'``." msgstr "" #: faq/programming.rst:906 @@ -1519,10 +1519,10 @@ msgstr "" 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`. :meth:`!split` supports an optional \"sep\" " -"parameter which is useful if the line uses something other than whitespace " -"as a separator." +"string objects and then convert decimal strings to numeric values " +"using :func:`int` or :func:`float`. :meth:`!split` supports an optional " +"\"sep\" parameter which is useful if the line uses something other than " +"whitespace as a separator." msgstr "" #: faq/programming.rst:1019 @@ -1682,9 +1682,9 @@ 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 " +"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 "" @@ -1861,8 +1861,8 @@ msgstr "" #: faq/programming.rst:1220 msgid "" -"If all elements of the list may be used as set keys (i.e. they are all :term:" -"`hashable`) this is often faster ::" +"If all elements of the list may be used as set keys (i.e. they are " +"all :term:`hashable`) this is often faster ::" msgstr "" #: faq/programming.rst:1223 @@ -2020,8 +2020,8 @@ msgstr "" #: faq/programming.rst:1327 msgid "" -"To call a method or function and accumulate the return values is a list, a :" -"term:`list comprehension` is an elegant solution::" +"To call a method or function and accumulate the return values is a list, " +"a :term:`list comprehension` is an elegant solution::" msgstr "" #: faq/programming.rst:1330 @@ -2266,8 +2266,8 @@ msgstr "" #: faq/programming.rst:1481 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 " +"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 "" @@ -2312,8 +2312,8 @@ msgstr "" #: faq/programming.rst:1511 msgid "" -"Note that :func:`isinstance` also checks for virtual inheritance from an :" -"term:`abstract base class`. So, the test will return ``True`` for a " +"Note that :func:`isinstance` also checks for virtual inheritance from " +"an :term:`abstract base class`. So, the test will return ``True`` for a " "registered class even if hasn't directly or indirectly inherited from it. " "To test for \"true inheritance\", scan the :term:`MRO` of the class:" msgstr "" @@ -2426,19 +2426,19 @@ msgstr "" #: faq/programming.rst:1598 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 :meth:`~object." -"__getattr__` method; consult :ref:`the language reference ` for more information about controlling attribute access." +"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 :meth:`~object.__getattr__` method; consult :ref:`the language reference " +"` for more information about controlling attribute access." msgstr "" #: faq/programming.rst:1605 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:" -"`~object.__setattr__` method too, and it must do so carefully. The basic " -"implementation of :meth:`!__setattr__` is roughly equivalent to the " +"attributes must be set as well as retrieved, the class must define " +"a :meth:`~object.__setattr__` method too, and it must do so carefully. The " +"basic implementation of :meth:`!__setattr__` is roughly equivalent to the " "following::" msgstr "" @@ -2453,8 +2453,9 @@ msgstr "" #: faq/programming.rst:1616 msgid "" -"Many :meth:`~object.__setattr__` implementations call :meth:`!object." -"__setattr__` to set an attribute on self without causing infinite recursion::" +"Many :meth:`~object.__setattr__` implementations call :meth:`!" +"object.__setattr__` to set an attribute on self without causing infinite " +"recursion::" msgstr "" #: faq/programming.rst:1619 @@ -2467,8 +2468,8 @@ msgstr "" #: faq/programming.rst:1624 msgid "" -"Alternatively, it is possible to set attributes by inserting entries into :" -"attr:`self.__dict__ ` directly." +"Alternatively, it is possible to set attributes by inserting entries " +"into :attr:`self.__dict__ ` directly." msgstr "" #: faq/programming.rst:1629 @@ -2711,9 +2712,9 @@ msgstr "" #: faq/programming.rst:1782 msgid "" -"The :keyword:`del` statement does not necessarily call :meth:`~object." -"__del__` -- it simply decrements the object's reference count, and if this " -"reaches zero :meth:`!__del__` is called." +"The :keyword:`del` statement does not necessarily " +"call :meth:`~object.__del__` -- it simply decrements the object's reference " +"count, and if this reaches zero :meth:`!__del__` is called." msgstr "" #: faq/programming.rst:1786 @@ -2911,8 +2912,8 @@ msgstr "" #: faq/programming.rst:1932 msgid "" -"For example, here is the implementation of :meth:`!collections.abc.Sequence." -"__contains__`::" +"For example, here is the implementation of :meth:`!" +"collections.abc.Sequence.__contains__`::" msgstr "" #: faq/programming.rst:1935 @@ -2989,9 +2990,10 @@ msgstr "" #: faq/programming.rst:1995 msgid "" -"The two principal tools for caching methods are :func:`functools." -"cached_property` and :func:`functools.lru_cache`. The former stores results " -"at the instance level and the latter at the class level." +"The two principal tools for caching methods " +"are :func:`functools.cached_property` and :func:`functools.lru_cache`. The " +"former stores results at the instance level and the latter at the class " +"level." msgstr "" #: faq/programming.rst:2000 @@ -3062,8 +3064,9 @@ msgstr "" #: faq/programming.rst:2047 msgid "" "To make the *lru_cache* approach work when the *station_id* is mutable, the " -"class needs to define the :meth:`~object.__eq__` and :meth:`~object." -"__hash__` methods so that the cache can detect relevant attribute updates::" +"class needs to define the :meth:`~object.__eq__` " +"and :meth:`~object.__hash__` methods so that the cache can detect relevant " +"attribute updates::" msgstr "" #: faq/programming.rst:2051 @@ -3128,19 +3131,19 @@ msgstr "" #: faq/programming.rst:2096 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 " +"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 "" #: faq/programming.rst:2103 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." +"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 "" #: faq/programming.rst:2107 @@ -3283,11 +3286,11 @@ msgstr "" #: faq/programming.rst:2176 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 " -"``.``." +"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 "" #: faq/programming.rst:2181 diff --git a/faq/windows.po b/faq/windows.po index 6f90e4381..db5119a93 100644 --- a/faq/windows.po +++ b/faq/windows.po @@ -118,20 +118,20 @@ msgstr "" #: faq/windows.rst:84 msgid "" "Many people use the interactive mode as a convenient yet highly programmable " -"calculator. When you want to end your interactive Python session, call the :" -"func:`exit` function or 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." +"calculator. When you want to end your interactive Python session, call " +"the :func:`exit` function or 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 "" #: faq/windows.rst:90 msgid "" -"You may also find that you have a Start-menu entry such as :menuselection:" -"`Start --> Programs --> Python 3.x --> Python (command line)` that results " -"in you seeing the ``>>>`` prompt in a new window. If so, the window will " -"disappear after you call the :func:`exit` function or enter the :kbd:`Ctrl-" -"Z` character; Windows is running a single \"python\" command in the window, " -"and closes it when you terminate the interpreter." +"You may also find that you have a Start-menu entry such " +"as :menuselection:`Start --> Programs --> Python 3.x --> Python (command " +"line)` that results in you seeing the ``>>>`` prompt in a new window. If " +"so, the window will disappear after you call the :func:`exit` function or " +"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 "" #: faq/windows.rst:97 @@ -246,9 +246,10 @@ msgstr "" 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." +"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 "" #: faq/windows.rst:176 @@ -382,17 +383,17 @@ msgstr "" #: faq/windows.rst:262 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." +"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 "" #: faq/windows.rst:267 msgid "" "Python raises :exc:`IndentationError` or :exc:`TabError` if mixed tabs and " -"spaces are causing problems in leading whitespace. You may also run the :mod:" -"`tabnanny` module to check a directory tree in batch mode." +"spaces are causing problems in leading whitespace. You may also run " +"the :mod:`tabnanny` module to check a directory tree in batch mode." msgstr "" #: faq/windows.rst:274 diff --git a/glossary.po b/glossary.po index 0dae09fa2..a238ee1ec 100644 --- a/glossary.po +++ b/glossary.po @@ -89,23 +89,25 @@ msgid "" "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." +"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 "" "Soyut temel sınıflar :term:`duck-typing` 'i, :func:`hasattr` gibi diğer " "teknikler beceriksiz veya tamamen yanlış olduğunda arayüzleri tanımlamanın " "bir yolunu sağlayarak tamamlar (örneğin :ref:`sihirli yöntemlerle `). ABC'ler, bir sınıftan miras almayan ancak yine de :func:" -"`isinstance` ve :func:`issubclass` tarafından tanınan sınıflar olan sanal " -"alt sınıfları tanıtır; :mod:`abc` modül belgelerine bakın. 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). :" -"mod:`abc` modülü ile kendi ABC'lerinizi oluşturabilirsiniz." +"lookup>`). ABC'ler, bir sınıftan miras almayan ancak yine " +"de :func:`isinstance` ve :func:`issubclass` tarafından tanınan sınıflar olan " +"sanal alt sınıfları tanıtır; :mod:`abc` modül belgelerine bakın. 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). :mod:`abc` modülü ile kendi ABC'lerinizi " +"oluşturabilirsiniz." #: glossary.rst:46 msgid "annotation" @@ -135,8 +137,8 @@ msgstr "" #: glossary.rst:58 msgid "" "See :term:`variable annotation`, :term:`function annotation`, :pep:`484` " -"and :pep:`526`, which describe this functionality. Also see :ref:" -"`annotations-howto` for best practices on working with annotations." +"and :pep:`526`, which describe this functionality. Also " +"see :ref:`annotations-howto` for best practices on working with annotations." msgstr "" "Bu işlevi açıklayan :term:`variable annotation`, :term:`function " "annotation`, :pep:`484` ve :pep:`526`'e bakın. Ek açıklamalarla çalışmaya " @@ -221,12 +223,12 @@ msgstr "asenkron bağlam yöneticisi" #, fuzzy msgid "" "An object which controls the environment seen in an :keyword:`async with` " -"statement by defining :meth:`~object.__aenter__` and :meth:`~object." -"__aexit__` methods. Introduced by :pep:`492`." +"statement by defining :meth:`~object.__aenter__` " +"and :meth:`~object.__aexit__` methods. Introduced by :pep:`492`." msgstr "" -":keyword:`async with` ifadesinde görülen ortamı :meth:`__aenter__` ve :meth:" -"`__aexit__` yöntemlerini tanımlayarak kontrol eden bir nesne. :pep:`492` de " -"anlatıldı." +":keyword:`async with` ifadesinde görülen ortamı :meth:`__aenter__` " +"ve :meth:`__aexit__` yöntemlerini tanımlayarak kontrol eden bir " +"nesne. :pep:`492` de anlatıldı." #: glossary.rst:97 msgid "asynchronous generator" @@ -239,10 +241,10 @@ msgid "" "that it contains :keyword:`yield` expressions for producing a series of " "values usable in an :keyword:`async for` loop." msgstr "" -":term:`asynchronous generator iterator` döndüren bir işlev. Bir :keyword:" -"`async for` döngüsünde kullanılabilen bir dizi değer üretmek için :keyword:" -"`yield` ifadeleri içermesi dışında :keyword:`async def` ile tanımlanmış bir " -"eşyordam işlevine benziyor." +":term:`asynchronous generator iterator` döndüren bir işlev. " +"Bir :keyword:`async for` döngüsünde kullanılabilen bir dizi değer üretmek " +"için :keyword:`yield` ifadeleri içermesi dışında :keyword:`async def` ile " +"tanımlanmış bir eşyordam işlevine benziyor." #: glossary.rst:104 msgid "" @@ -260,8 +262,8 @@ msgid "" "An asynchronous generator function may contain :keyword:`await` expressions " "as well as :keyword:`async for`, and :keyword:`async with` statements." msgstr "" -"Bir asenkron üretici fonksiyonu, :keyword:`await` ifadelerinin yanı sıra :" -"keyword:`async for` ve :keyword:`async with` ifadeleri içerebilir." +"Bir asenkron üretici fonksiyonu, :keyword:`await` ifadelerinin yanı " +"sıra :keyword:`async for` ve :keyword:`async with` ifadeleri içerebilir." #: glossary.rst:111 msgid "asynchronous generator iterator" @@ -275,14 +277,15 @@ msgstr "" #: glossary.rst:115 #, fuzzy msgid "" -"This is an :term:`asynchronous iterator` which when called using the :meth:" -"`~object.__anext__` method returns an awaitable object which will execute " -"the body of the asynchronous generator function until the next :keyword:" -"`yield` expression." +"This is an :term:`asynchronous iterator` which when called using " +"the :meth:`~object.__anext__` method returns an awaitable object which will " +"execute the body of the asynchronous generator function until the " +"next :keyword:`yield` expression." msgstr "" -"Bu, :meth:`__anext__` yöntemi kullanılarak çağrıldığında, bir sonraki :" -"keyword:`yield` ifadesine kadar asynchronous generator işlevinin gövdesini " -"yürütecek, beklenebilir bir nesne döndüren bir :term:`asynchronous iterator`." +"Bu, :meth:`__anext__` yöntemi kullanılarak çağrıldığında, bir " +"sonraki :keyword:`yield` ifadesine kadar asynchronous generator işlevinin " +"gövdesini yürütecek, beklenebilir bir nesne döndüren bir :term:`asynchronous " +"iterator`." #: glossary.rst:120 #, fuzzy @@ -310,9 +313,9 @@ msgid "" "return an :term:`asynchronous iterator` from its :meth:`~object.__aiter__` " "method. Introduced by :pep:`492`." msgstr "" -"Bir :keyword:`async for` ifadesinde kullanılabilen bir nesne. :meth:" -"`__aiter__` yönteminden bir :term:`asynchronous iterator` döndürmelidir. :" -"pep:`492` 'de tanıtıldı." +"Bir :keyword:`async for` ifadesinde kullanılabilen bir " +"nesne. :meth:`__aiter__` yönteminden bir :term:`asynchronous iterator` " +"döndürmelidir. :pep:`492` 'de tanıtıldı." #: glossary.rst:130 msgid "asynchronous iterator" @@ -321,11 +324,12 @@ msgstr "asenkron yineleyici" #: glossary.rst:132 #, fuzzy msgid "" -"An object that implements the :meth:`~object.__aiter__` and :meth:`~object." -"__anext__` methods. :meth:`~object.__anext__` must return an :term:" -"`awaitable` object. :keyword:`async for` resolves the awaitables returned by " -"an asynchronous iterator's :meth:`~object.__anext__` method until it raises " -"a :exc:`StopAsyncIteration` exception. Introduced by :pep:`492`." +"An object that implements the :meth:`~object.__aiter__` " +"and :meth:`~object.__anext__` methods. :meth:`~object.__anext__` must " +"return an :term:`awaitable` object. :keyword:`async for` resolves the " +"awaitables returned by an asynchronous iterator's :meth:`~object.__anext__` " +"method until it raises a :exc:`StopAsyncIteration` exception. Introduced " +"by :pep:`492`." msgstr "" ":meth:`__aiter__` ve :meth:`__anext__` yöntemlerini uygulayan bir nesne. " "``__anext__`` bir :term:`awaitable` nesnesi döndürmelidir. :keyword:`async " @@ -350,10 +354,10 @@ msgstr "" #: glossary.rst:144 msgid "" "It is possible to give an object an attribute whose name is not an " -"identifier as defined by :ref:`identifiers`, for example using :func:" -"`setattr`, if the object allows it. Such an attribute will not be accessible " -"using a dotted expression, and would instead need to be retrieved with :func:" -"`getattr`." +"identifier as defined by :ref:`identifiers`, for example " +"using :func:`setattr`, if the object allows it. Such an attribute will not " +"be accessible using a dotted expression, and would instead need to be " +"retrieved with :func:`getattr`." msgstr "" "Bir nesneye, eğer nesne izin veriyorsa, örneğin :func:`setattr` kullanarak, " "adı :ref:`identifiers` tarafından tanımlandığı gibi tanımlayıcı olmayan bir " @@ -367,13 +371,13 @@ msgstr "beklenebilir" #: glossary.rst:151 #, fuzzy msgid "" -"An object that can be used in an :keyword:`await` expression. Can be a :" -"term:`coroutine` or an object with an :meth:`~object.__await__` method. See " -"also :pep:`492`." +"An object that can be used in an :keyword:`await` expression. Can be " +"a :term:`coroutine` or an object with an :meth:`~object.__await__` method. " +"See also :pep:`492`." msgstr "" ":keyword:`await` ifadesinde kullanılabilen bir nesne. Bir :term:`coroutine` " -"veya :meth:`__await__` yöntemine sahip bir nesne olabilir. Ayrıca bakınız :" -"pep:`492`." +"veya :meth:`__await__` yöntemine sahip bir nesne olabilir. Ayrıca " +"bakınız :pep:`492`." #: glossary.rst:154 msgid "BDFL" @@ -381,8 +385,8 @@ msgstr "BDFL" #: glossary.rst:156 msgid "" -"Benevolent Dictator For Life, a.k.a. `Guido van Rossum `_, Python's creator." +"Benevolent Dictator For Life, a.k.a. `Guido van Rossum `_, Python's creator." msgstr "" "Benevolent Dictator For Life, namı diğer `Guido van Rossum `_, Python'un yaratıcısı." @@ -396,20 +400,20 @@ msgstr "ikili dosya" msgid "" "A :term:`file object` able to read and write :term:`bytes-like objects " "`. Examples of binary files are files opened in binary " -"mode (``'rb'``, ``'wb'`` or ``'rb+'``), :data:`sys.stdin.buffer `, :data:`sys.stdout.buffer `, and instances of :class:`io." -"BytesIO` and :class:`gzip.GzipFile`." +"mode (``'rb'``, ``'wb'`` or ``'rb+'``), :data:`sys.stdin.buffer " +"`, :data:`sys.stdout.buffer `, and instances " +"of :class:`io.BytesIO` and :class:`gzip.GzipFile`." msgstr "" "Bir :term:`dosya nesnesi ` :term:`bayt benzeri nesneler ` okuyabilir ve yazabilir. İkili dosya örnekleri, ikili modda " -"açılan dosyalardır (``'rb'``, ``'wb'`` veya ``'rb+'``), :data:`sys.stdin." -"buffer`, :data:`sys.stdout.buffer` ve :class:`io.BytesIO` ve :class:`gzip." -"GzipFile` örnekleri." +"açılan dosyalardır (``'rb'``, ``'wb'`` veya " +"``'rb+'``), :data:`sys.stdin.buffer`, :data:`sys.stdout.buffer` " +"ve :class:`io.BytesIO` ve :class:`gzip.GzipFile` örnekleri." #: glossary.rst:167 msgid "" -"See also :term:`text file` for a file object able to read and write :class:" -"`str` objects." +"See also :term:`text file` for a file object able to read and " +"write :class:`str` objects." msgstr "" "Ayrıca :class:`str` nesnelerini okuyabilen ve yazabilen bir dosya nesnesi " "için :term:`text file` 'a bakın." @@ -428,15 +432,15 @@ msgid "" msgstr "" "Python'un C API 'sinde ödünç alınan referans, bir nesneye yapılan bir " "referanstır. Nesne referans sayısını değiştirmez. Nesne yok edilirse sarkan " -"bir işaretçi olur. Örneğin, bir çöp toplama, nesneye yapılan son :term:" -"`strong reference` kaldırabilir ve böylece onu yok edebilir." +"bir işaretçi olur. Örneğin, bir çöp toplama, nesneye yapılan " +"son :term:`strong reference` kaldırabilir ve böylece onu yok edebilir." #: glossary.rst:177 msgid "" "Calling :c:func:`Py_INCREF` on the :term:`borrowed reference` is recommended " "to convert it to a :term:`strong reference` in-place, except when the object " -"cannot be destroyed before the last usage of the borrowed reference. The :c:" -"func:`Py_NewRef` function can be used to create a new :term:`strong " +"cannot be destroyed before the last usage of the borrowed reference. " +"The :c:func:`Py_NewRef` function can be used to create a new :term:`strong " "reference`." msgstr "" ":term:`borrowed reference` üzerinde :c:func:`Py_INCREF` çağırmak, nesnenin " @@ -451,27 +455,27 @@ msgstr "bayt benzeri nesne" #: glossary.rst:184 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." +"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 "" ":ref:`bufferobjects` 'i destekleyen ve bir C-:term:`contiguous` arabelleğini " -"dışa aktarabilen bir nesne. Bu, tüm :class:`bytes`, :class:`bytearray` ve :" -"class:`array.array` nesnelerinin yanı sıra birçok yaygın :class:`memoryview` " -"nesnesini içerir. Bayt benzeri nesneler, ikili verilerle çalışan çeşitli " -"işlemler için kullanılabilir; bunlara sıkıştırma, ikili dosyaya kaydetme ve " -"bir soket üzerinden gönderme dahildir." +"dışa aktarabilen bir nesne. Bu, tüm :class:`bytes`, :class:`bytearray` " +"ve :class:`array.array` nesnelerinin yanı sıra birçok " +"yaygın :class:`memoryview` nesnesini içerir. Bayt benzeri nesneler, ikili " +"verilerle çalışan çeşitli işlemler için kullanılabilir; bunlara sıkıştırma, " +"ikili dosyaya kaydetme ve bir soket üzerinden gönderme dahildir." #: glossary.rst:191 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 " +"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 "" "Bazı işlemler, değişken olması için ikili verilere ihtiyaç duyar. Belgeler " @@ -479,8 +483,8 @@ msgstr "" "bulunur. Örnek değiştirilebilir arabellek nesneleri :class:`bytearray` ve " "bir :class:`bytearray` :class:`memoryview` içerir. Diğer işlemler, ikili " "verilerin değişmez nesnelerde (\"salt okunur bayt benzeri nesneler\") " -"depolanmasını gerektirir; bunların örnekleri arasında :class:`bytes` ve bir :" -"class:`bytes` nesnesinin :class:`memoryview` bulunur." +"depolanmasını gerektirir; bunların örnekleri arasında :class:`bytes` ve " +"bir :class:`bytes` nesnesinin :class:`memoryview` bulunur." #: glossary.rst:199 msgid "bytecode" @@ -508,8 +512,8 @@ msgstr "" #: glossary.rst:211 msgid "" -"A list of bytecode instructions can be found in the documentation for :ref:" -"`the dis module `." +"A list of bytecode instructions can be found in the documentation " +"for :ref:`the dis module `." msgstr "" "Bayt kodu talimatlarının bir listesi :ref:`bytecodes` dokümanında " "bulunabilir." @@ -614,9 +618,9 @@ msgid "" "by defining :meth:`~object.__enter__` and :meth:`~object.__exit__` methods. " "See :pep:`343`." msgstr "" -":keyword:`with` ifadesinde görülen ortamı :meth:`__enter__` ve :meth:" -"`__exit__` yöntemlerini tanımlayarak kontrol eden bir nesne. Bakınız :pep:" -"`343`." +":keyword:`with` ifadesinde görülen ortamı :meth:`__enter__` " +"ve :meth:`__exit__` yöntemlerini tanımlayarak kontrol eden bir nesne. " +"Bakınız :pep:`343`." #: glossary.rst:253 msgid "context variable" @@ -673,8 +677,9 @@ msgid "" msgstr "" "Eşyordamlar, altyordamların daha genelleştirilmiş bir biçimidir. Alt " "programlara bir noktada girilir ve başka bir noktada çıkılır. Eşyordamlar " -"birçok farklı noktada girilebilir, çıkılabilir ve devam ettirilebilir. :" -"keyword:`async def` ifadesi ile uygulanabilirler. Ayrıca bakınız :pep:`492`." +"birçok farklı noktada girilebilir, çıkılabilir ve devam " +"ettirilebilir. :keyword:`async def` ifadesi ile uygulanabilirler. Ayrıca " +"bakınız :pep:`492`." #: glossary.rst:281 msgid "coroutine function" @@ -683,14 +688,14 @@ msgstr "eşyordam işlevi" #: glossary.rst:283 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`." +"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 "" -"Bir :term:`coroutine` nesnesi döndüren bir işlev. Bir eşyordam işlevi :" -"keyword:`async def` ifadesiyle tanımlanabilir ve :keyword:`await`, :keyword:" -"`async for` ve :keyword:`async with` anahtar kelimelerini içerebilir. " -"Bunlar :pep:`492` tarafından tanıtıldı." +"Bir :term:`coroutine` nesnesi döndüren bir işlev. Bir eşyordam " +"işlevi :keyword:`async def` ifadesiyle tanımlanabilir " +"ve :keyword:`await`, :keyword:`async for` ve :keyword:`async with` anahtar " +"kelimelerini içerebilir. Bunlar :pep:`492` tarafından tanıtıldı." #: glossary.rst:288 msgid "CPython" @@ -758,15 +763,16 @@ msgstr "tanımlayıcı" #: glossary.rst:316 #, fuzzy msgid "" -"Any object which defines the methods :meth:`~object.__get__`, :meth:`~object." -"__set__`, or :meth:`~object.__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." +"Any object which defines the " +"methods :meth:`~object.__get__`, :meth:`~object.__set__`, " +"or :meth:`~object.__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 "" ":meth:`__get__`, :meth:`__set__` veya :meth:`__delete__` yöntemlerini " "tanımlayan herhangi bir nesne. Bir sınıf özniteliği bir tanımlayıcı " @@ -783,8 +789,9 @@ msgid "" "For more information about descriptors' methods, see :ref:`descriptors` or " "the :ref:`Descriptor How To Guide `." msgstr "" -"Tanımlayıcıların yöntemleri hakkında daha fazla bilgi için, bkz. :ref:" -"`descriptors` veya :ref:`Descriptor How To Guide `." +"Tanımlayıcıların yöntemleri hakkında daha fazla bilgi için, " +"bkz. :ref:`descriptors` veya :ref:`Descriptor How To Guide " +"`." #: glossary.rst:329 msgid "dictionary" @@ -797,9 +804,9 @@ msgid "" "can be any object with :meth:`~object.__hash__` and :meth:`~object.__eq__` " "methods. Called a hash in Perl." msgstr "" -"Rasgele anahtarların değerlerle eşlendiği ilişkisel bir dizi. Anahtarlar, :" -"meth:`__hash__` ve :meth:`__eq__` yöntemleriyle herhangi bir nesne olabilir. " -"Perl'de karma denir." +"Rasgele anahtarların değerlerle eşlendiği ilişkisel bir dizi. " +"Anahtarlar, :meth:`__hash__` ve :meth:`__eq__` yöntemleriyle herhangi bir " +"nesne olabilir. Perl'de karma denir." #: glossary.rst:335 msgid "dictionary comprehension" @@ -823,11 +830,11 @@ msgstr "sözlük görünümü" #: glossary.rst:343 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`." +"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 "" ":meth:`dict.keys`, :meth:`dict.values` ve :meth:`dict.items` 'den döndürülen " "nesnelere sözlük görünümleri denir. Sözlüğün girişleri üzerinde dinamik bir " @@ -865,10 +872,10 @@ msgid "" "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." +"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 "" "Doğru arayüze sahip olup olmadığını belirlemek için bir nesnenin türüne " "bakmayan bir programlama stili; bunun yerine, yöntem veya nitelik basitçe " @@ -897,8 +904,8 @@ msgstr "" "geçerli anahtarların veya niteliklerin varlığını varsayar ve varsayımın " "yanlış çıkması durumunda istisnaları yakalar. Bu temiz ve hızlı stil, " "birçok :keyword:`try` ve :keyword:`except` ifadesinin varlığı ile " -"karakterize edilir. Teknik, C gibi diğer birçok dilde ortak olan :term:" -"`LBYL` stiliyle çelişir." +"karakterize edilir. Teknik, C gibi diğer birçok dilde ortak " +"olan :term:`LBYL` stiliyle çelişir." #: glossary.rst:376 msgid "expression" @@ -966,8 +973,8 @@ msgstr "" "şekline bağlı olarak, bir dosya nesnesi gerçek bir disk üzerindeki dosyaya " "veya başka bir tür depolama veya iletişim aygıtına (örneğin standart giriş/" "çıkış, bellek içi arabellekler, yuvalar, borular vb.) erişime aracılık " -"edebilir. . Dosya nesneleri ayrıca :dfn:`file-like objects` veya :dfn:" -"`streams` olarak da adlandırılır." +"edebilir. . Dosya nesneleri ayrıca :dfn:`file-like objects` " +"veya :dfn:`streams` olarak da adlandırılır." #: glossary.rst:404 msgid "" @@ -1014,9 +1021,9 @@ msgstr "" #: glossary.rst:421 msgid "" -"The :func:`sys.getfilesystemencoding` and :func:`sys." -"getfilesystemencodeerrors` functions can be used to get the filesystem " -"encoding and error handler." +"The :func:`sys.getfilesystemencoding` " +"and :func:`sys.getfilesystemencodeerrors` functions can be used to get the " +"filesystem encoding and error handler." msgstr "" ":func:`sys.getfilesystemencoding` ve :func:`sys.getfilesystemencodeerrors` " "işlevleri, dosya sistemi kodlamasını ve hata işleyicisini almak için " @@ -1025,14 +1032,14 @@ msgstr "" #: glossary.rst:425 msgid "" "The :term:`filesystem encoding and error handler` are configured at Python " -"startup by the :c:func:`PyConfig_Read` function: see :c:member:`~PyConfig." -"filesystem_encoding` and :c:member:`~PyConfig.filesystem_errors` members of :" -"c:type:`PyConfig`." +"startup by the :c:func:`PyConfig_Read` function: " +"see :c:member:`~PyConfig.filesystem_encoding` " +"and :c:member:`~PyConfig.filesystem_errors` members of :c:type:`PyConfig`." msgstr "" -":term:`filesystem encoding and error handler` Python başlangıcında :c:func:" -"`PyConfig_Read` işleviyle yapılandırılır: bkz. :c:member:`~PyConfig." -"filesystem_encoding` ve :c:member:`~PyConfig. filesystem_errors` üyeleri :c:" -"type:`PyConfig`." +":term:`filesystem encoding and error handler` Python " +"başlangıcında :c:func:`PyConfig_Read` işleviyle yapılandırılır: " +"bkz. :c:member:`~PyConfig.filesystem_encoding` ve :c:member:`~PyConfig. " +"filesystem_errors` üyeleri :c:type:`PyConfig`." #: glossary.rst:430 msgid "See also the :term:`locale encoding`." @@ -1058,9 +1065,9 @@ msgid "" "entry finder>` for use with :data:`sys.path_hooks`." msgstr "" "Python 3.3'ten beri, iki çeşit bulucu vardır: :data:`sys.meta_path` ile " -"kullanılmak üzere :term:`meta yol bulucular `, ve :data:" -"`sys.path_hooks` ile kullanılmak üzere :term:`yol girişi bulucular `." +"kullanılmak üzere :term:`meta yol bulucular `, " +"ve :data:`sys.path_hooks` ile kullanılmak üzere :term:`yol girişi bulucular " +"`." #: glossary.rst:440 #, fuzzy @@ -1094,13 +1101,13 @@ msgstr "fonksiyon" 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." +"execution of the body. See also :term:`parameter`, :term:`method`, and " +"the :ref:`function` section." msgstr "" "Bir arayana bir değer döndüren bir dizi ifade. Ayrıca, gövdenin " "yürütülmesinde kullanılabilen sıfır veya daha fazla :term:`argüman " -"` iletilebilir. Ayrıca :term:`parameter`, :term:`method` ve :ref:" -"`function` bölümüne bakın." +"` iletilebilir. Ayrıca :term:`parameter`, :term:`method` " +"ve :ref:`function` bölümüne bakın." #: glossary.rst:454 msgid "function annotation" @@ -1139,8 +1146,8 @@ msgid "" "working with annotations." msgstr "" "Bu işlevi açıklayan :term:`variable annotation` ve :pep:`484` 'e bakın. Ek " -"açıklamalarla çalışmaya ilişkin en iyi uygulamalar için ayrıca :ref:" -"`annotations-howto` konusuna bakın." +"açıklamalarla çalışmaya ilişkin en iyi uygulamalar için " +"ayrıca :ref:`annotations-howto` konusuna bakın." #: glossary.rst:472 msgid "__future__" @@ -1150,19 +1157,19 @@ msgstr "__future__" msgid "" "A :ref:`future statement `, ``from __future__ import ``, " "directs the compiler to compile the current module using syntax or semantics " -"that will become standard in a future release of Python. The :mod:" -"`__future__` module documents the possible values of *feature*. By " +"that will become standard in a future release of Python. " +"The :mod:`__future__` module documents the possible values of *feature*. By " "importing this module and evaluating its variables, you can see when a new " "feature was first added to the language and when it will (or did) become the " "default::" msgstr "" "Bir :ref:`future ifadesi `, ``from __future__ import ``, " "derleyiciyi, Python'un gelecekteki bir sürümünde standart hale gelecek olan " -"sözdizimini veya semantiği kullanarak mevcut modülü derlemeye yönlendirir. :" -"mod:`__future__` modülü, *feature*'ın olası değerlerini belgeler. Bu modülü " -"içe aktararak ve değişkenlerini değerlendirerek, dile ilk kez yeni bir " -"özelliğin ne zaman eklendiğini ve ne zaman varsayılan olacağını (ya da " -"yaptığını) görebilirsiniz:" +"sözdizimini veya semantiği kullanarak mevcut modülü derlemeye " +"yönlendirir. :mod:`__future__` modülü, *feature*'ın olası değerlerini " +"belgeler. Bu modülü içe aktararak ve değişkenlerini değerlendirerek, dile " +"ilk kez yeni bir özelliğin ne zaman eklendiğini ve ne zaman varsayılan " +"olacağını (ya da yaptığını) görebilirsiniz:" #: glossary.rst:482 msgid "" @@ -1271,11 +1278,12 @@ msgstr "" #: glossary.rst:529 msgid "" -"See also the :term:`single dispatch` glossary entry, the :func:`functools." -"singledispatch` decorator, and :pep:`443`." +"See also the :term:`single dispatch` glossary entry, " +"the :func:`functools.singledispatch` decorator, and :pep:`443`." msgstr "" -"Ayrıca :term:`single dispatch` sözlük girdisine, :func:`functools." -"singledispatch` dekoratörüne ve :pep:`443` 'e bakın." +"Ayrıca :term:`single dispatch` sözlük " +"girdisine, :func:`functools.singledispatch` dekoratörüne ve :pep:`443` 'e " +"bakın." #: glossary.rst:531 msgid "generic type" @@ -1284,20 +1292,22 @@ msgstr "genel tip" #: glossary.rst:533 msgid "" "A :term:`type` that can be parameterized; typically a :ref:`container " -"class` such as :class:`list` or :class:`dict`. Used for :" -"term:`type hints ` and :term:`annotations `." +"class` such as :class:`list` or :class:`dict`. Used " +"for :term:`type hints ` and :term:`annotations `." msgstr "" "Parametrelendirilebilen bir :term:`type`; tipik olarak bir :ref:`konteyner " -"sınıfı `, örneğin :class:`list` veya :class:`dict`. :term:" -"`type hint` ve :term:`annotation` için kullanılır." +"sınıfı `, örneğin :class:`list` " +"veya :class:`dict`. :term:`type hint` ve :term:`annotation` için kullanılır." #: glossary.rst:538 msgid "" -"For more details, see :ref:`generic alias types`, :pep:" -"`483`, :pep:`484`, :pep:`585`, and the :mod:`typing` module." +"For more details, see :ref:`generic alias types`, :pep:`483`, :pep:`484`, :pep:`585`, and the :mod:`typing` " +"module." msgstr "" -"Daha fazla ayrıntı için :ref:`generic allias types`, :" -"pep:`483`, :pep:`484`, :pep:`585` ve :mod:`typing` modülüne bakın." +"Daha fazla ayrıntı için :ref:`generic allias types`, :pep:`483`, :pep:`484`, :pep:`585` ve :mod:`typing` modülüne " +"bakın." #: glossary.rst:540 msgid "GIL" @@ -1366,8 +1376,8 @@ msgid "" "invalidation`." msgstr "" "Geçerliliğini belirlemek için ilgili kaynak dosyanın son değiştirilme zamanı " -"yerine karma değerini kullanan bir bayt kodu önbellek dosyası. Bakınız :ref:" -"`pyc-invalidation`." +"yerine karma değerini kullanan bir bayt kodu önbellek dosyası. " +"Bakınız :ref:`pyc-invalidation`." #: glossary.rst:570 msgid "hashable" @@ -1381,8 +1391,8 @@ msgid "" "compared to other objects (it needs an :meth:`~object.__eq__` method). " "Hashable objects which compare equal must have the same hash value." msgstr "" -"Bir nesne, ömrü boyunca asla değişmeyen bir karma değere sahipse (bir :meth:" -"`__hash__` yöntemine ihtiyaç duyar) ve diğer nesnelerle " +"Bir nesne, ömrü boyunca asla değişmeyen bir karma değere sahipse " +"(bir :meth:`__hash__` yöntemine ihtiyaç duyar) ve diğer nesnelerle " "karşılaştırılabilirse (bir :meth:`__eq__` yöntemine ihtiyaç duyar) " "*hashable* olur. . Eşit karşılaştıran Hashable nesneleri aynı karma " "değerine sahip olmalıdır." @@ -1431,8 +1441,8 @@ msgstr "" #: glossary.rst:595 msgid "" -"*Immortal objects* are a CPython implementation detail introduced in :pep:" -"`683`." +"*Immortal objects* are a CPython implementation detail introduced " +"in :pep:`683`." msgstr "" #: glossary.rst:598 @@ -1494,8 +1504,8 @@ msgstr "içe aktarıcı" #: glossary.rst:621 msgid "" -"An object that both finds and loads a module; both a :term:`finder` and :" -"term:`loader` object." +"An object that both finds and loads a module; both a :term:`finder` " +"and :term:`loader` object." msgstr "" "Bir modülü hem bulan hem de yükleyen bir nesne; hem bir :term:`finder` hem " "de :term:`loader` nesnesi." @@ -1537,8 +1547,8 @@ msgstr "" "dosyaların daha sonra çalıştırılacak bir yürütülebilir dosya oluşturmadan " "doğrudan çalıştırılabileceği anlamına gelir. Yorumlanan diller genellikle " "derlenmiş dillerden daha kısa bir geliştirme/hata ayıklama döngüsüne " -"sahiptir, ancak programları genellikle daha yavaş çalışır. Ayrıca bkz. :" -"term:`interactive`." +"sahiptir, ancak programları genellikle daha yavaş çalışır. Ayrıca " +"bkz. :term:`interactive`." #: glossary.rst:640 msgid "interpreter shutdown" @@ -1548,12 +1558,12 @@ msgstr "tercüman kapatma" 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)." +"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 "" "Kapatılması istendiğinde, Python yorumlayıcısı, modüller ve çeşitli kritik " "iç yapılar gibi tahsis edilen tüm kaynakları kademeli olarak serbest " @@ -1581,30 +1591,32 @@ msgstr "yinelenebilir" 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:`~iterator.__iter__` method or with a :meth:`~object.__getitem__` " -"method that implements :term:`sequence` semantics." +"and :class:`tuple`) and some non-sequence types " +"like :class:`dict`, :term:`file objects `, and objects of any " +"classes you define with an :meth:`~iterator.__iter__` method or with " +"a :meth:`~object.__getitem__` method that implements :term:`sequence` " +"semantics." msgstr "" "Üyelerini teker teker döndürebilen bir nesne. Yineleme örnekleri, tüm dizi " -"türlerini (:class:`list`, :class:`str`, ve :class:`tuple` gibi) ve :class:" -"`dict`, :term:`dosya objeleri ` gibi bazı dizi olmayan türleri " -"ve bir :meth:`__iter__` yöntemiyle veya :term:`dizi ` semantiğini " -"uygulayan bir :meth:`__getitem__` yöntemiyle tanımladığınız tüm sınıfların " -"nesnelerini içerir." +"türlerini (:class:`list`, :class:`str`, ve :class:`tuple` gibi) " +"ve :class:`dict`, :term:`dosya objeleri ` gibi bazı dizi " +"olmayan türleri ve bir :meth:`__iter__` yöntemiyle veya :term:`dizi " +"` semantiğini uygulayan bir :meth:`__getitem__` yöntemiyle " +"tanımladığınız tüm sınıfların nesnelerini içerir." #: glossary.rst:663 #, fuzzy msgid "" "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 :" -"keyword:`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`." +"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 :keyword:`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 "" "Yinelenebilirler bir :keyword:`for` döngüsünde ve bir dizinin gerekli olduğu " "diğer birçok yerde kullanılabilir (:func:`zip`, :func:`map`, ...). " @@ -1614,8 +1626,8 @@ msgstr "" "genellikle :func:`iter` çağırmanız veya yineleyici nesnelerle kendiniz " "ilgilenmeniz gerekmez. ``for`` ifadesi bunu sizin için otomatik olarak " "yapar ve yineleyiciyi döngü süresince tutmak için geçici bir adsız değişken " -"oluşturur. Ayrıca bkz. :term:`iterator`, :term:`sequence` ve :term:" -"`generator`." +"oluşturur. Ayrıca bkz. :term:`iterator`, :term:`sequence` " +"ve :term:`generator`." #: glossary.rst:673 msgid "iterator" @@ -1624,36 +1636,38 @@ msgstr "yineleyici" #: glossary.rst:675 #, fuzzy 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:`~iterator.__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 "" -"Bir veri akışını temsil eden bir nesne. Yineleyicinin :meth:`~iterator." -"__next__` yöntemine (veya yerleşik :func:`next` işlevine iletilmesi) " -"yinelenen çağrılar, akıştaki ardışık öğeleri döndürür. Daha fazla veri " -"bulunmadığında, bunun yerine bir :exc:`StopIteration` istisnası " -"oluşturulur. Bu noktada, yineleyici nesnesi tükenir ve :meth:`__next__` " -"yöntemine yapılan diğer çağrılar yalnızca :exc:`StopIteration` öğesini " -"yeniden yükseltir. Yineleyicilerin, yineleyici nesnesinin kendisini " -"döndüren bir :meth:`__iter__` yöntemine sahip olmaları gerekir, böylece her " -"yineleyici de yinelenebilir ve diğer yinelenebilirlerin kabul edildiği çoğu " -"yerde kullanılabilir. Dikkate değer bir istisna, birden çok yineleme " -"geçişini deneyen koddur. Bir kapsayıcı nesnesi (örneğin bir :class:`list`), " -"onu :func:`iter` işlevine her ilettiğinizde veya onu bir :keyword:`for` " -"döngüsünde kullandığınızda yeni bir yineleyici üretir. Bunu bir " -"yineleyiciyle denemek, önceki yineleme geçişinde kullanılan aynı tükenmiş " -"yineleyici nesnesini döndürerek boş bir kap gibi görünmesini sağlar." +"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:`~iterator.__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 "" +"Bir veri akışını temsil eden bir nesne. " +"Yineleyicinin :meth:`~iterator.__next__` yöntemine (veya " +"yerleşik :func:`next` işlevine iletilmesi) yinelenen çağrılar, akıştaki " +"ardışık öğeleri döndürür. Daha fazla veri bulunmadığında, bunun yerine " +"bir :exc:`StopIteration` istisnası oluşturulur. Bu noktada, yineleyici " +"nesnesi tükenir ve :meth:`__next__` yöntemine yapılan diğer çağrılar " +"yalnızca :exc:`StopIteration` öğesini yeniden yükseltir. Yineleyicilerin, " +"yineleyici nesnesinin kendisini döndüren bir :meth:`__iter__` yöntemine " +"sahip olmaları gerekir, böylece her yineleyici de yinelenebilir ve diğer " +"yinelenebilirlerin kabul edildiği çoğu yerde kullanılabilir. Dikkate değer " +"bir istisna, birden çok yineleme geçişini deneyen koddur. Bir kapsayıcı " +"nesnesi (örneğin bir :class:`list`), onu :func:`iter` işlevine her " +"ilettiğinizde veya onu bir :keyword:`for` döngüsünde kullandığınızda yeni " +"bir yineleyici üretir. Bunu bir yineleyiciyle denemek, önceki yineleme " +"geçişinde kullanılan aynı tükenmiş yineleyici nesnesini döndürerek boş bir " +"kap gibi görünmesini sağlar." #: glossary.rst:690 msgid "More information can be found in :ref:`typeiter`." @@ -1662,8 +1676,8 @@ msgstr "Daha fazla bilgi :ref:`typeiter` içinde bulunabilir." #: glossary.rst:694 #, fuzzy msgid "" -"CPython does not consistently apply the requirement that an iterator define :" -"meth:`~iterator.__iter__`." +"CPython does not consistently apply the requirement that an iterator " +"define :meth:`~iterator.__iter__`." msgstr "" "CPython, bir yineleyicinin :meth:`__iter__` tanımlaması gereksinimini " "tutarlı bir şekilde uygulamaz." @@ -1679,42 +1693,42 @@ msgid "" "produce a sort key that is aware of locale specific sort conventions." msgstr "" "Anahtar işlevi veya harmanlama işlevi, sıralama veya sıralama için " -"kullanılan bir değeri döndüren bir çağrılabilir. Örneğin, :func:`locale." -"strxfrm`, yerel ayara özgü sıralama kurallarının farkında olan bir sıralama " -"anahtarı üretmek için kullanılır." +"kullanılan bir değeri döndüren bir çağrılabilir. " +"Örneğin, :func:`locale.strxfrm`, yerel ayara özgü sıralama kurallarının " +"farkında olan bir sıralama anahtarı üretmek için kullanılır." #: glossary.rst:703 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`." +"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 "" "Python'daki bir dizi araç, öğelerin nasıl sıralandığını veya " -"gruplandırıldığını kontrol etmek için temel işlevleri kabul eder. Bunlar :" -"func:`min`, :func:`max`, :func:`sorted`, :meth:`list.sort`, :func:`heapq." -"merge`, :func:`heapq.nsmallest`, :func:`heapq.nlargest` ve :func:`itertools." -"groupby`." +"gruplandırıldığını kontrol etmek için temel işlevleri kabul eder. " +"Bunlar :func:`min`, :func:`max`, :func:`sorted`, :meth:`list.sort`, :func:`heapq.merge`, :func:`heapq.nsmallest`, :func:`heapq.nlargest` " +"ve :func:`itertools.groupby`." #: glossary.rst:709 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, :func:`operator." -"attrgetter`, :func:`operator.itemgetter`, and :func:`operator.methodcaller` " -"are three key function constructors. See the :ref:`Sorting HOW TO " -"` for examples of how to create and use key functions." -msgstr "" -"Bir tuş fonksiyonu oluşturmanın birkaç yolu vardır. Örneğin. :meth:`str." -"lower` yöntemi, büyük/küçük harfe duyarlı olmayan sıralamalar için bir " -"anahtar fonksiyonu işlevi görebilir. Alternatif olarak, ``lambda r: (r[0], " -"r[2])`` gibi bir :keyword:`lambda` ifadesinden bir anahtar işlevi " -"oluşturulabilir. Ayrıca, :func:`~operator.attrgetter`, :func:`~operator." -"itemgetter` ve :func:`~operator.methodcaller` fonksiyonları üç anahtar " -"fonksiyon kurucularıdır. Anahtar işlevlerin nasıl oluşturulacağı ve " -"kullanılacağına ilişkin örnekler için :ref:`Sorting HOW TO ` " -"bölümüne bakın." +"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, :func:`operator.attrgetter`, :func:`operator.itemgetter`, " +"and :func:`operator.methodcaller` are three key function constructors. See " +"the :ref:`Sorting HOW TO ` for examples of how to create and " +"use key functions." +msgstr "" +"Bir tuş fonksiyonu oluşturmanın birkaç yolu vardır. " +"Örneğin. :meth:`str.lower` yöntemi, büyük/küçük harfe duyarlı olmayan " +"sıralamalar için bir anahtar fonksiyonu işlevi görebilir. Alternatif " +"olarak, ``lambda r: (r[0], r[2])`` gibi bir :keyword:`lambda` ifadesinden " +"bir anahtar işlevi oluşturulabilir. " +"Ayrıca, :func:`~operator.attrgetter`, :func:`~operator.itemgetter` " +"ve :func:`~operator.methodcaller` fonksiyonları üç anahtar fonksiyon " +"kurucularıdır. Anahtar işlevlerin nasıl oluşturulacağı ve kullanılacağına " +"ilişkin örnekler için :ref:`Sorting HOW TO ` bölümüne bakın." #: glossary.rst:716 msgid "keyword argument" @@ -1808,13 +1822,14 @@ msgstr "yükleyici" #: glossary.rst:751 #, fuzzy 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 also:" +"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 also:" msgstr "" "Modül yükleyen bir nesne. :meth:`load_module` adında bir yöntem " "tanımlamalıdır. Bir yükleyici genellikle bir :term:`finder` ile döndürülür. " -"Ayrıntılar için :pep:`302` ve bir :term:`soyut temel sınıf` için :class:" -"`importlib.abc.Loader` bölümüne bakın." +"Ayrıntılar için :pep:`302` ve bir :term:`soyut temel sınıf` " +"için :class:`importlib.abc.Loader` bölümüne bakın." #: glossary.rst:755 msgid ":ref:`finders-and-loaders`" @@ -1835,11 +1850,13 @@ msgstr "yerel kodlama" #: glossary.rst:760 msgid "" -"On Unix, it is the encoding of the LC_CTYPE locale. It can be set with :func:" -"`locale.setlocale(locale.LC_CTYPE, new_locale) `." +"On Unix, it is the encoding of the LC_CTYPE locale. It can be set " +"with :func:`locale.setlocale(locale.LC_CTYPE, new_locale) " +"`." msgstr "" -"Unix'te, LC_CTYPE yerel ayarının kodlamasıdır. :func:`locale." -"setlocale(locale.LC_CTYPE, new_locale) ` ile ayarlanabilir." +"Unix'te, LC_CTYPE yerel ayarının " +"kodlamasıdır. :func:`locale.setlocale(locale.LC_CTYPE, new_locale) " +"` ile ayarlanabilir." #: glossary.rst:763 msgid "On Windows, it is the ANSI code page (ex: ``\"cp1252\"``)." @@ -1875,17 +1892,18 @@ msgstr "haritalama" #: glossary.rst:777 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`." +"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 "" "Keyfi anahtar aramalarını destekleyen ve :class:`~collections.abc.Mapping` " "veya :class:`~collections.abc.MutableMapping` :ref:`collections-abstract-" "base-classes` içinde belirtilen yöntemleri uygulayan bir kapsayıcı nesnesi. " -"Örnekler arasında :class:`dict`, :class:`collections.defaultdict`, :class:" -"`collections.OrderedDict` ve :class:`collections.Counter` sayılabilir." +"Örnekler " +"arasında :class:`dict`, :class:`collections.defaultdict`, :class:`collections.OrderedDict` " +"ve :class:`collections.Counter` sayılabilir." #: glossary.rst:783 msgid "meta path finder" @@ -1906,8 +1924,8 @@ msgid "" "See :class:`importlib.abc.MetaPathFinder` for the methods that meta path " "finders implement." msgstr "" -"Meta yol bulucuların uyguladığı yöntemler için :class:`importlib.abc." -"MetaPathFinder` bölümüne bakın." +"Meta yol bulucuların uyguladığı yöntemler " +"için :class:`importlib.abc.MetaPathFinder` bölümüne bakın." #: glossary.rst:791 msgid "metaclass" @@ -1947,8 +1965,8 @@ msgstr "metot" 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`." +"first :term:`argument` (which is usually called ``self``). " +"See :term:`function` and :term:`nested scope`." msgstr "" "Bir sınıf gövdesi içinde tanımlanan bir işlev. Bu sınıfın bir örneğinin " "özniteliği olarak çağrılırsa, yöntem örnek nesnesini ilk :term:`argument` " @@ -1982,8 +2000,8 @@ msgid "" "into Python by the process of :term:`importing`." msgstr "" "Python kodunun kuruluş birimi olarak hizmet eden bir nesne. Modüller, " -"rastgele Python nesneleri içeren bir ad alanına sahiptir. Modüller, :term:" -"`importing` işlemiyle Python'a yüklenir." +"rastgele Python nesneleri içeren bir ad alanına sahiptir. " +"Modüller, :term:`importing` işlemiyle Python'a yüklenir." #: glossary.rst:821 msgid "See also :term:`package`." @@ -2020,11 +2038,11 @@ msgstr "değiştirilebilir" #: glossary.rst:833 msgid "" -"Mutable objects can change their value but keep their :func:`id`. See also :" -"term:`immutable`." +"Mutable objects can change their value but keep their :func:`id`. See " +"also :term:`immutable`." msgstr "" -"Değiştirilebilir (mutable) nesneler değerlerini değiştirebilir ancak :func:" -"`idlerini ` koruyabilirler. Ayrıca bkz. :term:`immutable`." +"Değiştirilebilir (mutable) nesneler değerlerini değiştirebilir " +"ancak :func:`idlerini ` koruyabilirler. Ayrıca bkz. :term:`immutable`." #: glossary.rst:835 msgid "named tuple" @@ -2042,9 +2060,9 @@ msgstr "" #: glossary.rst:841 msgid "" -"Several built-in types are named tuples, including the values returned by :" -"func:`time.localtime` and :func:`os.stat`. Another example is :data:`sys." -"float_info`::" +"Several built-in types are named tuples, including the values returned " +"by :func:`time.localtime` and :func:`os.stat`. Another example " +"is :data:`sys.float_info`::" msgstr "" "Çeşitli yerleşik türler, :func:`time.localtime` ve :func:`os.stat` " "tarafından döndürülen değerler de dahil olmak üzere, tanımlama grupları " @@ -2066,18 +2084,19 @@ msgid "" "Some named tuples are built-in types (such as the above examples). " "Alternatively, a named tuple can be created from a regular class definition " "that inherits from :class:`tuple` and that defines named fields. Such a " -"class can be written by hand, or it can be created by inheriting :class:" -"`typing.NamedTuple`, or with the factory function :func:`collections." -"namedtuple`. The latter techniques also add some extra methods that may not " -"be found in hand-written or built-in named tuples." +"class can be written by hand, or it can be created by " +"inheriting :class:`typing.NamedTuple`, or with the factory " +"function :func:`collections.namedtuple`. The latter techniques also add " +"some extra methods that may not be found in hand-written or built-in named " +"tuples." msgstr "" "Bazı adlandırılmış demetler yerleşik türlerdir (yukarıdaki örnekler gibi). " "Alternatif olarak, :class:`tuple` öğesinden miras alan ve adlandırılmış " "alanları tanımlayan normal bir sınıf tanımından adlandırılmış bir tanımlama " -"grubu oluşturulabilir. Böyle bir sınıf elle yazılabilir veya fabrika işlevi :" -"func:`collections.namedtuple` ile oluşturulabilir. İkinci teknik ayrıca elle " -"yazılmış veya yerleşik adlandırılmış demetlerde bulunmayan bazı ekstra " -"yöntemler ekler." +"grubu oluşturulabilir. Böyle bir sınıf elle yazılabilir veya fabrika " +"işlevi :func:`collections.namedtuple` ile oluşturulabilir. İkinci teknik " +"ayrıca elle yazılmış veya yerleşik adlandırılmış demetlerde bulunmayan bazı " +"ekstra yöntemler ekler." #: glossary.rst:860 msgid "namespace" @@ -2088,22 +2107,23 @@ 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." +"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 "" "Değişkenin saklandığı yer. Ad alanları sözlükler olarak uygulanır. " "Nesnelerde (yöntemlerde) yerel, genel ve yerleşik ad alanlarının yanı sıra " "iç içe ad alanları vardır. Ad alanları, adlandırma çakışmalarını önleyerek " -"modülerliği destekler. Örneğin, :func:`builtins.open <.open>` ve :func:`os." -"open` işlevleri ad alanlarıyla ayırt edilir. Ad alanları, hangi modülün bir " -"işlevi uyguladığını açıkça belirterek okunabilirliğe ve sürdürülebilirliğe " -"de yardımcı olur. Örneğin, :func:`random.seed` veya :func:`itertools.islice` " -"yazmak, bu işlevlerin sırasıyla :mod:`random` ve :mod:`itertools` modülleri " -"tarafından uygulandığını açıkça gösterir." +"modülerliği destekler. Örneğin, :func:`builtins.open <.open>` " +"ve :func:`os.open` işlevleri ad alanlarıyla ayırt edilir. Ad alanları, hangi " +"modülün bir işlevi uyguladığını açıkça belirterek okunabilirliğe ve " +"sürdürülebilirliğe de yardımcı olur. Örneğin, :func:`random.seed` " +"veya :func:`itertools.islice` yazmak, bu işlevlerin sırasıyla :mod:`random` " +"ve :mod:`itertools` modülleri tarafından uygulandığını açıkça gösterir." #: glossary.rst:872 msgid "namespace package" @@ -2155,14 +2175,15 @@ msgstr "yeni stil sınıf" 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:`~object.__getattribute__`, class methods, and static methods." +"versatile features like :attr:`~object.__slots__`, descriptors, " +"properties, :meth:`~object.__getattribute__`, class methods, and static " +"methods." msgstr "" "Artık tüm sınıf nesneleri için kullanılan sınıfların lezzetinin eski adı. " -"Önceki Python sürümlerinde, yalnızca yeni stil sınıfları Python'un :attr:" -"`~object.__slots__`, tanımlayıcılar, özellikler, :meth:`__getattribute__`, " -"sınıf yöntemleri ve statik yöntemler gibi daha yeni, çok yönlü özelliklerini " -"kullanabilirdi." +"Önceki Python sürümlerinde, yalnızca yeni stil sınıfları " +"Python'un :attr:`~object.__slots__`, tanımlayıcılar, " +"özellikler, :meth:`__getattribute__`, sınıf yöntemleri ve statik yöntemler " +"gibi daha yeni, çok yönlü özelliklerini kullanabilirdi." #: glossary.rst:896 msgid "object" @@ -2187,9 +2208,9 @@ msgid "" "subpackages. Technically, a package is a Python module with a ``__path__`` " "attribute." msgstr "" -"Alt modüller veya yinelemeli olarak alt paketler içerebilen bir Python :term:" -"`module`. Teknik olarak bir paket, ``__path__`` özniteliğine sahip bir " -"Python modülüdür." +"Alt modüller veya yinelemeli olarak alt paketler içerebilen bir " +"Python :term:`module`. Teknik olarak bir paket, ``__path__`` özniteliğine " +"sahip bir Python modülüdür." #: glossary.rst:907 msgid "See also :term:`regular package` and :term:`namespace package`." @@ -2205,9 +2226,9 @@ msgid "" "an :term:`argument` (or in some cases, arguments) that the function can " "accept. There are five kinds of parameter:" msgstr "" -"Bir :term:`function` (veya yöntem) tanımında, işlevin kabul edebileceği bir :" -"term:`argument` (veya bazı durumlarda, argümanlar) belirten adlandırılmış " -"bir varlık. Beş çeşit parametre vardır:" +"Bir :term:`function` (veya yöntem) tanımında, işlevin kabul edebileceği " +"bir :term:`argument` (veya bazı durumlarda, argümanlar) belirten " +"adlandırılmış bir varlık. Beş çeşit parametre vardır:" #: glossary.rst:914 msgid "" @@ -2216,9 +2237,10 @@ msgid "" "`. This is the default kind of parameter, for example *foo* and " "*bar* in the following::" msgstr "" -":dfn:`positional-or-keyword`: :term:`pozisyonel ` veya bir :term:" -"`keyword argümanı ` olarak iletilebilen bir argüman belirtir. Bu, " -"varsayılan parametre türüdür, örneğin aşağıdakilerde *foo* ve *bar*::" +":dfn:`positional-or-keyword`: :term:`pozisyonel ` veya " +"bir :term:`keyword argümanı ` olarak iletilebilen bir argüman " +"belirtir. Bu, varsayılan parametre türüdür, örneğin aşağıdakilerde *foo* ve " +"*bar*::" #: glossary.rst:919 msgid "def func(foo, bar=None): ..." @@ -2301,12 +2323,12 @@ msgstr "" 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`." +"the :class:`inspect.Parameter` class, the :ref:`function` section, " +"and :pep:`362`." msgstr "" "Ayrıca bkz. :term:`argüman `, :ref:`argümanlar ve parametreler " -"arasındaki fark `, :class:`inspect.Parameter`, :" -"ref:`function` ve :pep:`362`." +"arasındaki fark `, :class:`inspect.Parameter`, :ref:`function` ve :pep:`362`." #: glossary.rst:961 msgid "path entry" @@ -2317,8 +2339,8 @@ msgid "" "A single location on the :term:`import path` which the :term:`path based " "finder` consults to find modules for importing." msgstr "" -":term:`path based finder` içe aktarma modüllerini bulmak için başvurduğu :" -"term:`import path` üzerindeki tek bir konum." +":term:`path based finder` içe aktarma modüllerini bulmak için " +"başvurduğu :term:`import path` üzerindeki tek bir konum." #: glossary.rst:965 msgid "path entry finder" @@ -2326,9 +2348,9 @@ msgstr "yol girişi bulucu" #: glossary.rst:967 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`." +"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 "" "Bir :term:`finder` :data:`sys.path_hooks` (yani bir :term:`yol giriş " "kancası`) üzerinde bir çağrılabilir tarafından döndürülür ve :term:`path " @@ -2339,8 +2361,8 @@ msgid "" "See :class:`importlib.abc.PathEntryFinder` for the methods that path entry " "finders implement." msgstr "" -"Yol girişi bulucularının uyguladığı yöntemler için :class:`importlib.abc." -"PathEntryFinder` bölümüne bakın." +"Yol girişi bulucularının uyguladığı yöntemler " +"için :class:`importlib.abc.PathEntryFinder` bölümüne bakın." #: glossary.rst:973 msgid "path entry hook" @@ -2375,23 +2397,24 @@ msgstr "yol benzeri nesne" #: glossary.rst:984 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`." +"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 "" "Bir dosya sistemi yolunu temsil eden bir nesne. Yol benzeri bir nesne, bir " -"yolu temsil eden bir :class:`str` veya :class:`bytes` nesnesi veya :class:" -"`os.PathLike` protokolünü uygulayan bir nesnedir. :class:`os.PathLike` " -"protokolünü destekleyen bir nesne, :func:`os.fspath` işlevi çağrılarak bir :" -"class:`str` veya :class:`bytes` dosya sistemi yoluna dönüştürülebilir; :func:" -"`os.fsdecode` ve :func:`os.fsencode`, bunun yerine sırasıyla :class:`str` " -"veya :class:`bytes` sonucunu garanti etmek için kullanılabilir. :pep:`519` " -"tarafından tanıtıldı." +"yolu temsil eden bir :class:`str` veya :class:`bytes` nesnesi " +"veya :class:`os.PathLike` protokolünü uygulayan bir " +"nesnedir. :class:`os.PathLike` protokolünü destekleyen bir " +"nesne, :func:`os.fspath` işlevi çağrılarak bir :class:`str` " +"veya :class:`bytes` dosya sistemi yoluna " +"dönüştürülebilir; :func:`os.fsdecode` ve :func:`os.fsencode`, bunun yerine " +"sırasıyla :class:`str` veya :class:`bytes` sonucunu garanti etmek için " +"kullanılabilir. :pep:`519` tarafından tanıtıldı." #: glossary.rst:992 msgid "PEP" @@ -2577,8 +2600,8 @@ msgstr "" #: glossary.rst:1075 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``::" +"dotted path to the module, including any parent packages, e.g. " +"``email.mime.text``::" msgstr "" "Modüllere atıfta bulunmak için kullanıldığında, *tam nitelenmiş ad*, " "herhangi bir üst paket de dahil olmak üzere, modüle giden tüm noktalı yol " @@ -2618,8 +2641,8 @@ msgstr "sürekli paketleme" #: glossary.rst:1094 msgid "" -"A traditional :term:`package`, such as a directory containing an ``__init__." -"py`` file." +"A traditional :term:`package`, such as a directory containing an " +"``__init__.py`` file." msgstr "" "``__init__.py`` dosyası içeren bir dizin gibi geleneksel bir :term:`package`." @@ -2653,39 +2676,40 @@ msgstr "dizi" #, fuzzy msgid "" "An :term:`iterable` which supports efficient element access using integer " -"indices via the :meth:`~object.__getitem__` special method and defines a :" -"meth:`~object.__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:`~object." -"__getitem__` and :meth:`!__len__`, but is considered a mapping rather than a " -"sequence because the lookups use arbitrary :term:`hashable` keys rather than " -"integers." +"indices via the :meth:`~object.__getitem__` special method and defines " +"a :meth:`~object.__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:`~object.__getitem__` and :meth:`!" +"__len__`, but is considered a mapping rather than a sequence because the " +"lookups use arbitrary :term:`hashable` keys rather than integers." msgstr "" ":meth:`__getitem__` özel yöntemi aracılığıyla tamsayı dizinlerini kullanarak " -"verimli öğe erişimini destekleyen ve dizinin uzunluğunu döndüren bir :meth:" -"`__len__` yöntemini tanımlayan bir :term:`iterable`. Bazı yerleşik dizi " -"türleri şunlardır: :class:`list`, :class:`str`, :class:`tuple` ve :class:" -"`bytes`. :class:`dict` ayrıca :meth:`__getitem__` ve :meth:`__len__` 'i de " -"desteklediğine dikkat edin, ancak aramalar tamsayılar yerine rastgele :term:" -"`immutable` anahtarları kullandığından bir diziden ziyade bir eşleme olarak " -"kabul edilir." +"verimli öğe erişimini destekleyen ve dizinin uzunluğunu döndüren " +"bir :meth:`__len__` yöntemini tanımlayan bir :term:`iterable`. Bazı yerleşik " +"dizi türleri şunlardır: :class:`list`, :class:`str`, :class:`tuple` " +"ve :class:`bytes`. :class:`dict` ayrıca :meth:`__getitem__` " +"ve :meth:`__len__` 'i de desteklediğine dikkat edin, ancak aramalar " +"tamsayılar yerine rastgele :term:`immutable` anahtarları kullandığından bir " +"diziden ziyade bir eşleme olarak kabul edilir." #: glossary.rst:1116 #, fuzzy msgid "" "The :class:`collections.abc.Sequence` abstract base class defines a much " -"richer interface that goes beyond just :meth:`~object.__getitem__` and :meth:" -"`~object.__len__`, adding :meth:`!count`, :meth:`!index`, :meth:`~object." -"__contains__`, and :meth:`~object.__reversed__`. Types that implement this " -"expanded interface can be registered explicitly using :func:`~abc.ABCMeta." -"register`. For more documentation on sequence methods generally, see :ref:" -"`Common Sequence Operations `." -msgstr "" -":class:`collections.abc.Sequence` soyut temel sınıfı;, :meth:`count`, :meth:" -"`index`, :meth:`__contains__`, ve :meth:`__reversed__` ekleyerek sadece :" -"meth:`__getitem__` ve :meth:`__len__` 'in ötesine geçen çok daha zengin bir " -"arayüzü tanımlar. Bu genişletilmiş arabirimi uygulayan türler, :func:`~abc." -"ABCMeta.register` kullanılarak açıkça kaydedilebilir." +"richer interface that goes beyond just :meth:`~object.__getitem__` " +"and :meth:`~object.__len__`, adding :meth:`!count`, :meth:`!" +"index`, :meth:`~object.__contains__`, and :meth:`~object.__reversed__`. " +"Types that implement this expanded interface can be registered explicitly " +"using :func:`~abc.ABCMeta.register`. For more documentation on sequence " +"methods generally, see :ref:`Common Sequence Operations `." +msgstr "" +":class:`collections.abc.Sequence` soyut temel " +"sınıfı;, :meth:`count`, :meth:`index`, :meth:`__contains__`, " +"ve :meth:`__reversed__` ekleyerek sadece :meth:`__getitem__` " +"ve :meth:`__len__` 'in ötesine geçen çok daha zengin bir arayüzü tanımlar. " +"Bu genişletilmiş arabirimi uygulayan türler, :func:`~abc.ABCMeta.register` " +"kullanılarak açıkça kaydedilebilir." #: glossary.rst:1125 msgid "set comprehension" @@ -2695,8 +2719,8 @@ msgstr "anlamak" msgid "" "A compact way to process all or part of the elements in an iterable and " "return a set with the results. ``results = {c for c in 'abracadabra' if c " -"not in 'abc'}`` generates the set of strings ``{'r', 'd'}``. See :ref:" -"`comprehensions`." +"not in 'abc'}`` generates the set of strings ``{'r', 'd'}``. " +"See :ref:`comprehensions`." msgstr "" "Öğelerin tümünü veya bir kısmını yinelenebilir bir şekilde işlemenin ve " "sonuçlarla birlikte bir küme döndürmenin kompakt bir yolu. ``results = {c " @@ -2763,13 +2787,13 @@ msgstr "özel metod" 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`." +"with double underscores. Special methods are documented " +"in :ref:`specialnames`." msgstr "" "Toplama gibi bir tür üzerinde belirli bir işlemi yürütmek için Python " "tarafından örtük olarak çağrılan bir yöntem. Bu tür yöntemlerin çift alt " -"çizgi ile başlayan ve biten adları vardır. Özel yöntemler :ref:" -"`specialnames` içinde belgelenmiştir." +"çizgi ile başlayan ve biten adları vardır. Özel " +"yöntemler :ref:`specialnames` içinde belgelenmiştir." #: glossary.rst:1160 msgid "statement" @@ -2778,12 +2802,12 @@ msgstr "ifade (değer döndürmez)" #: glossary.rst:1162 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`." +"an :term:`expression` or one of several constructs with a keyword, such " +"as :keyword:`if`, :keyword:`while` or :keyword:`for`." msgstr "" -"Bir ifade, bir paketin parçasıdır (kod \"bloğu\"). Bir ifade, bir :term:" -"`expression` veya :keyword:`if`, :keyword:`while` veya :keyword:`for` gibi " -"bir anahtar kelimeye sahip birkaç yapıdan biridir." +"Bir ifade, bir paketin parçasıdır (kod \"bloğu\"). Bir ifade, " +"bir :term:`expression` veya :keyword:`if`, :keyword:`while` " +"veya :keyword:`for` gibi bir anahtar kelimeye sahip birkaç yapıdan biridir." #: glossary.rst:1165 msgid "static type checker" @@ -2792,8 +2816,8 @@ msgstr "" #: glossary.rst:1167 msgid "" "An external tool that reads Python code and analyzes it, looking for issues " -"such as incorrect types. See also :term:`type hints ` and the :" -"mod:`typing` module." +"such as incorrect types. See also :term:`type hints ` and " +"the :mod:`typing` module." msgstr "" #: glossary.rst:1170 @@ -2805,8 +2829,8 @@ msgstr "güçlü referans" msgid "" "In Python's C API, a strong reference is a reference to an object which is " "owned by the code holding the reference. The strong reference is taken by " -"calling :c:func:`Py_INCREF` when the reference is created and released with :" -"c:func:`Py_DECREF` when the reference is deleted." +"calling :c:func:`Py_INCREF` when the reference is created and released " +"with :c:func:`Py_DECREF` when the reference is deleted." msgstr "" "Python'un C API'sinde, güçlü bir referans, oluşturulduğunda nesnenin " "referans sayısını artıran ve silindiğinde nesnenin referans sayısını azaltan " @@ -2866,21 +2890,23 @@ msgstr "yazı dosyası" #: glossary.rst:1198 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. Examples of text files are files opened in " -"text mode (``'r'`` or ``'w'``), :data:`sys.stdin`, :data:`sys.stdout`, and " -"instances of :class:`io.StringIO`." +"text file actually accesses a byte-oriented datastream and handles " +"the :term:`text encoding` automatically. Examples of text files are files " +"opened in text mode (``'r'`` or " +"``'w'``), :data:`sys.stdin`, :data:`sys.stdout`, and instances " +"of :class:`io.StringIO`." msgstr "" "A :term:`file object` :class:`str` nesnelerini okuyabilir ve yazabilir. Çoğu " "zaman, bir metin dosyası aslında bir bayt yönelimli veri akışına erişir ve " "otomatik olarak :term:`text encoding` işler. Metin dosyalarına örnek olarak " -"metin modunda açılan dosyalar (``'r'`` veya ``'w'``), :data:`sys.stdin`, :" -"data:`sys.stdout` ve :class:`io.StringIO` örnekleri verilebilir." +"metin modunda açılan dosyalar (``'r'`` veya " +"``'w'``), :data:`sys.stdin`, :data:`sys.stdout` ve :class:`io.StringIO` " +"örnekleri verilebilir." #: glossary.rst:1205 msgid "" -"See also :term:`binary file` for a file object able to read and write :term:" -"`bytes-like objects `." +"See also :term:`binary file` for a file object able to read and " +"write :term:`bytes-like objects `." msgstr "" "Ayrıca :term:`ikili dosyaları ` okuyabilen ve yazabilen bir " "dosya nesnesi için :term:`bayt benzeri nesnelere ` bakın." @@ -2914,8 +2940,9 @@ msgstr "tip" #, fuzzy 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:`~object." -"__class__` attribute or can be retrieved with ``type(obj)``." +"object has a type. An object's type is accessible as " +"its :attr:`~object.__class__` attribute or can be retrieved with " +"``type(obj)``." msgstr "" "Bir Python nesnesinin türü, onun ne tür bir nesne olduğunu belirler; her " "nesnenin bir türü vardır. Bir nesnenin tipine :attr:`~instance.__class__` " @@ -3001,8 +3028,8 @@ 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." +"``'\\r'``. See :pep:`278` and :pep:`3116`, as well " +"as :func:`bytes.splitlines` for an additional use." msgstr "" "Aşağıdakilerin tümünün bir satırın bitişi olarak kabul edildiği metin " "akışlarını yorumlamanın bir yolu: Unix satır sonu kuralı ``\\n'``, Windows " @@ -3140,8 +3167,8 @@ msgstr "özel metod" #~ "diğerine örtük olarak dönüştürülmesi. Örneğin, ``int(3.15)``, kayan " #~ "noktalı sayıyı ``3`` tamsayısına dönüştürür, ancak ``3+4.5`` 'te her " #~ "argüman farklı türdedir (bir int, bir kayan nokta), ve her ikisi de " -#~ "eklenmeden önce aynı türe dönüştürülmelidir, aksi takdirde bir :exc:" -#~ "`TypeError` yükseltir. Zorlama olmadan, uyumlu türlerin bile tüm " +#~ "eklenmeden önce aynı türe dönüştürülmelidir, aksi takdirde " +#~ "bir :exc:`TypeError` yükseltir. Zorlama olmadan, uyumlu türlerin bile tüm " #~ "argümanlarının programcı tarafından aynı değere normalleştirilmesi " #~ "gerekir, örneğin: ``3+4,5`` yerine ``float(3)+4,5``." diff --git a/howto/annotations.po b/howto/annotations.po index 5565a55fa..3219f3ebc 100644 --- a/howto/annotations.po +++ b/howto/annotations.po @@ -53,8 +53,8 @@ msgstr "" msgid "" "Note that this document is specifically about working with " "``__annotations__``, not uses *for* annotations. If you're looking for " -"information on how to use \"type hints\" in your code, please see the :mod:" -"`typing` module." +"information on how to use \"type hints\" in your code, please see " +"the :mod:`typing` module." msgstr "" #: howto/annotations.rst:33 @@ -63,19 +63,19 @@ msgstr "" #: howto/annotations.rst:35 msgid "" -"Python 3.10 adds a new function to the standard library: :func:`inspect." -"get_annotations`. In Python versions 3.10 and newer, calling this function " -"is the best practice for accessing the annotations dict of any object that " -"supports annotations. This function can also \"un-stringize\" stringized " -"annotations for you." +"Python 3.10 adds a new function to the standard " +"library: :func:`inspect.get_annotations`. In Python versions 3.10 and " +"newer, calling this function is the best practice for accessing the " +"annotations dict of any object that supports annotations. This function can " +"also \"un-stringize\" stringized annotations for you." msgstr "" #: howto/annotations.rst:42 msgid "" "If for some reason :func:`inspect.get_annotations` isn't viable for your use " "case, you may access the ``__annotations__`` data member manually. Best " -"practice for this changed in Python 3.10 as well: as of Python 3.10, ``o." -"__annotations__`` is guaranteed to *always* work on Python functions, " +"practice for this changed in Python 3.10 as well: as of Python 3.10, " +"``o.__annotations__`` is guaranteed to *always* work on Python functions, " "classes, and modules. If you're certain the object you're examining is one " "of these three *specific* objects, you may simply use ``o.__annotations__`` " "to get at the object's annotations dict." @@ -83,11 +83,12 @@ msgstr "" #: howto/annotations.rst:52 msgid "" -"However, other types of callables--for example, callables created by :func:" -"`functools.partial`--may not have an ``__annotations__`` attribute defined. " -"When accessing the ``__annotations__`` of a possibly unknown object, best " -"practice in Python versions 3.10 and newer is to call :func:`getattr` with " -"three arguments, for example ``getattr(o, '__annotations__', None)``." +"However, other types of callables--for example, callables created " +"by :func:`functools.partial`--may not have an ``__annotations__`` attribute " +"defined. When accessing the ``__annotations__`` of a possibly unknown " +"object, best practice in Python versions 3.10 and newer is to " +"call :func:`getattr` with three arguments, for example ``getattr(o, " +"'__annotations__', None)``." msgstr "" #: howto/annotations.rst:60 @@ -171,15 +172,15 @@ msgstr "" #: howto/annotations.rst:118 msgid "" "After running this code, ``ann`` should be either a dictionary or ``None``. " -"You're encouraged to double-check the type of ``ann`` using :func:" -"`isinstance` before further examination." +"You're encouraged to double-check the type of ``ann`` " +"using :func:`isinstance` before further examination." msgstr "" #: howto/annotations.rst:123 msgid "" -"Note that some exotic or malformed type objects may not have a :attr:`~type." -"__dict__` attribute, so for extra safety you may also wish to use :func:" -"`getattr` to access :attr:`!__dict__`." +"Note that some exotic or malformed type objects may not have " +"a :attr:`~type.__dict__` attribute, so for extra safety you may also wish to " +"use :func:`getattr` to access :attr:`!__dict__`." msgstr "" #: howto/annotations.rst:129 @@ -196,10 +197,11 @@ msgstr "" #: howto/annotations.rst:137 msgid "" -"If you're using Python 3.9 or older, or if for some reason you can't use :" -"func:`inspect.get_annotations`, you'll need to duplicate its logic. You're " -"encouraged to examine the implementation of :func:`inspect.get_annotations` " -"in the current Python version and follow a similar approach." +"If you're using Python 3.9 or older, or if for some reason you can't " +"use :func:`inspect.get_annotations`, you'll need to duplicate its logic. " +"You're encouraged to examine the implementation " +"of :func:`inspect.get_annotations` in the current Python version and follow " +"a similar approach." msgstr "" #: howto/annotations.rst:143 @@ -210,29 +212,30 @@ msgstr "" #: howto/annotations.rst:146 msgid "" -"If ``o`` is a module, use ``o.__dict__`` as the ``globals`` when calling :" -"func:`eval`." +"If ``o`` is a module, use ``o.__dict__`` as the ``globals`` when " +"calling :func:`eval`." msgstr "" #: howto/annotations.rst:148 msgid "" "If ``o`` is a class, use ``sys.modules[o.__module__].__dict__`` as the " -"``globals``, and ``dict(vars(o))`` as the ``locals``, when calling :func:" -"`eval`." +"``globals``, and ``dict(vars(o))`` as the ``locals``, when " +"calling :func:`eval`." msgstr "" #: howto/annotations.rst:151 msgid "" -"If ``o`` is a wrapped callable using :func:`functools.update_wrapper`, :func:" -"`functools.wraps`, or :func:`functools.partial`, iteratively unwrap it by " -"accessing either ``o.__wrapped__`` or ``o.func`` as appropriate, until you " -"have found the root unwrapped function." +"If ``o`` is a wrapped callable " +"using :func:`functools.update_wrapper`, :func:`functools.wraps`, " +"or :func:`functools.partial`, iteratively unwrap it by accessing either " +"``o.__wrapped__`` or ``o.func`` as appropriate, until you have found the " +"root unwrapped function." msgstr "" #: howto/annotations.rst:155 msgid "" -"If ``o`` is a callable (but not a class), use :attr:`o.__globals__ ` as the globals when calling :func:`eval`." +"If ``o`` is a callable (but not a class), use :attr:`o.__globals__ " +"` as the globals when calling :func:`eval`." msgstr "" #: howto/annotations.rst:159 @@ -252,8 +255,8 @@ msgstr "" #: howto/annotations.rst:168 msgid "" -"Definitions that aren't needed at runtime, only imported when :const:`typing." -"TYPE_CHECKING` is true." +"Definitions that aren't needed at runtime, only imported " +"when :const:`typing.TYPE_CHECKING` is true." msgstr "" #: howto/annotations.rst:171 diff --git a/howto/argparse-optparse.po b/howto/argparse-optparse.po index 2ec77acc0..6c3736df7 100644 --- a/howto/argparse-optparse.po +++ b/howto/argparse-optparse.po @@ -25,8 +25,8 @@ 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 " -"``nargs=`` specifiers and better usage messages. When most everything in :" -"mod:`optparse` had either been copy-pasted over or monkey-patched, it no " +"``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 "" @@ -66,23 +66,23 @@ msgstr "" #: howto/argparse-optparse.rst:28 msgid "" -"Replace all :meth:`optparse.OptionParser.add_option` calls with :meth:" -"`ArgumentParser.add_argument` calls." +"Replace all :meth:`optparse.OptionParser.add_option` calls " +"with :meth:`ArgumentParser.add_argument` calls." msgstr "" #: howto/argparse-optparse.rst:31 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 the :mod:`argparse` context is called ``args``." +"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 the :mod:`argparse` context is called ``args``." msgstr "" #: howto/argparse-optparse.rst:36 msgid "" -"Replace :meth:`optparse.OptionParser.disable_interspersed_args` by using :" -"meth:`~ArgumentParser.parse_intermixed_args` instead of :meth:" -"`~ArgumentParser.parse_args`." +"Replace :meth:`optparse.OptionParser.disable_interspersed_args` by " +"using :meth:`~ArgumentParser.parse_intermixed_args` instead " +"of :meth:`~ArgumentParser.parse_args`." msgstr "" #: howto/argparse-optparse.rst:40 @@ -99,8 +99,9 @@ msgstr "" #: howto/argparse-optparse.rst:46 msgid "" -"Replace :class:`optparse.Values` with :class:`Namespace` and :exc:`optparse." -"OptionError` and :exc:`optparse.OptionValueError` with :exc:`ArgumentError`." +"Replace :class:`optparse.Values` with :class:`Namespace` " +"and :exc:`optparse.OptionError` and :exc:`optparse.OptionValueError` " +"with :exc:`ArgumentError`." msgstr "" #: howto/argparse-optparse.rst:50 diff --git a/howto/argparse.po b/howto/argparse.po index 0d67b6625..487f6d736 100644 --- a/howto/argparse.po +++ b/howto/argparse.po @@ -37,9 +37,9 @@ msgstr "" #: howto/argparse.rst:16 msgid "" "There are two other modules that fulfill the same task, namely :mod:`getopt` " -"(an equivalent for ``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." +"(an equivalent for ``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 "" #: howto/argparse.rst:24 @@ -295,8 +295,8 @@ msgstr "" #: howto/argparse.rst:198 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::" +"give it as strings, unless we tell it otherwise. So, let's " +"tell :mod:`argparse` to treat that input as an integer::" msgstr "" #: howto/argparse.rst:202 @@ -377,8 +377,8 @@ 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 ``args.verbosity``, is given " -"``None`` as a value, which is the reason it fails the truth test of the :" -"keyword:`if` statement." +"``None`` as a value, which is the reason it fails the truth test of " +"the :keyword:`if` statement." msgstr "" #: howto/argparse.rst:265 @@ -797,8 +797,8 @@ 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)." +"value, and that cannot be compared to an int value (hence " +"the :exc:`TypeError` exception)." msgstr "" #: howto/argparse.rst:585 @@ -941,12 +941,13 @@ msgstr "" #: howto/argparse.rst:701 msgid "" -"So far, we have been working with two methods of an :class:`argparse." -"ArgumentParser` instance. Let's introduce a third one, :meth:" -"`~ArgumentParser.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::" +"So far, we have been working with two methods of " +"an :class:`argparse.ArgumentParser` instance. Let's introduce a third " +"one, :meth:`~ArgumentParser.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 "" #: howto/argparse.rst:709 @@ -1075,9 +1076,9 @@ msgstr "" #: howto/argparse.rst:820 msgid "" -"In order to translate these strings, they must first be extracted into a ``." -"po`` file. For example, using `Babel `__, run this " -"command:" +"In order to translate these strings, they must first be extracted into a " +"``.po`` file. For example, using `Babel `__, run " +"this command:" msgstr "" #: howto/argparse.rst:824 @@ -1112,8 +1113,8 @@ msgstr "" #: howto/argparse.rst:842 msgid "" -"To translate your own strings in the :mod:`argparse` output, use :mod:" -"`gettext`." +"To translate your own strings in the :mod:`argparse` output, " +"use :mod:`gettext`." msgstr "" #: howto/argparse.rst:845 diff --git a/howto/clinic.po b/howto/clinic.po index 0f285c46d..7183ca4a3 100644 --- a/howto/clinic.po +++ b/howto/clinic.po @@ -152,9 +152,9 @@ msgstr "" #~ "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 "" -#~ "Boolean bir değer. Eğer true ise, Argüman Kliniği :c:func:" -#~ "`PyArg_ParseTuple` içine aktarırken değişkenin isminin önüne bir ``&`` " -#~ "ekleyecektir." +#~ "Boolean bir değer. Eğer true ise, Argüman " +#~ "Kliniği :c:func:`PyArg_ParseTuple` içine aktarırken değişkenin isminin " +#~ "önüne bir ``&`` ekleyecektir." #, fuzzy #~ msgid "" @@ -188,13 +188,13 @@ msgstr "" #~ msgid "" #~ "Next, 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 this tutorial, we'll be using :py:meth:" -#~ "`_pickle.Pickler.dump `." +#~ "work with Argument Clinic yet. For this tutorial, we'll be " +#~ "using :py:meth:`_pickle.Pickler.dump `." #~ msgstr "" #~ ":c:func:`PyArg_ParseTuple` veya :c:func:`PyArg_ParseTupleAndKeywords` " #~ "çağıran ve henüz Argüman Kliniği ile çalışmak üzere dönüştürülmemiş bir " -#~ "Python yerleşik bileşeni bulun. Benim örneğim için ``_pickle.Pickler." -#~ "dump()`` kullanıyorum." +#~ "Python yerleşik bileşeni bulun. Benim örneğim için " +#~ "``_pickle.Pickler.dump()`` kullanıyorum." #, fuzzy #~ msgid "" @@ -219,17 +219,18 @@ msgstr "" #~ 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 :c:" -#~ "func:`!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." +#~ "types for the same argument, or if the function uses something " +#~ "besides :c:func:`!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 "" -#~ "Ayrıca, fonksiyonun aynı argüman için farklı türleri desteklediği :c:func:" -#~ "`PyArg_ParseTuple` veya :c:func:`PyArg_ParseTupleAndKeywords` için birden " -#~ "fazla çağrısı varsa veya fonksiyon argümanlarını ayrıştırmak için " -#~ "PyArg_Parse fonksiyonları dışında bir şey kullanıyorsa, muhtemelen " -#~ "Argüman Kliniğine dönüştürmek için uygun değildir. Argüman Kliniği genel " -#~ "fonksiyonları veya çok biçimli parametreleri desteklemez." +#~ "Ayrıca, fonksiyonun aynı argüman için farklı türleri " +#~ "desteklediği :c:func:`PyArg_ParseTuple` " +#~ "veya :c:func:`PyArg_ParseTupleAndKeywords` için birden fazla çağrısı " +#~ "varsa veya fonksiyon argümanlarını ayrıştırmak için PyArg_Parse " +#~ "fonksiyonları dışında bir şey kullanıyorsa, muhtemelen Argüman Kliniğine " +#~ "dönüştürmek için uygun değildir. Argüman Kliniği genel fonksiyonları " +#~ "veya çok biçimli parametreleri desteklemez." #, fuzzy #~ msgid "" @@ -316,12 +317,12 @@ msgstr "" #~ 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." +#~ "Python. Check the name defined in the :c:type:`PyModuleDef` " +#~ "or :c:type:`PyTypeObject` as appropriate." #~ msgstr "" -#~ "Sınıfın ve modülün adı Python tarafından görülenle aynı olmalıdır. :c:" -#~ "type:`PyModuleDef` veya :c:type:`PyTypeObject` içinde tanımlanan ismi " -#~ "kontrol edin." +#~ "Sınıfın ve modülün adı Python tarafından görülenle aynı " +#~ "olmalıdır. :c:type:`PyModuleDef` veya :c:type:`PyTypeObject` içinde " +#~ "tanımlanan ismi kontrol edin." #, fuzzy #~ msgid "" @@ -378,11 +379,11 @@ msgstr "" #, fuzzy #~ msgid "" -#~ "For each parameter, copy the \"format unit\" for that parameter from the :" -#~ "c:func:`PyArg_Parse` format argument and specify *that* as its converter, " -#~ "as a quoted string. The \"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 " +#~ "For each parameter, copy the \"format unit\" for that parameter from " +#~ "the :c:func:`PyArg_Parse` format argument and specify *that* as its " +#~ "converter, as a quoted string. The \"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 "" #~ "Her parametre için, ``PyArg_Parse()`` format argümanından o parametrenin " @@ -438,9 +439,9 @@ msgstr "" #~ "opposed to :c:func:`PyArg_ParseTupleAndKeywords`), then all its arguments " #~ "are positional-only." #~ msgstr "" -#~ "Eğer mevcut C fonksiyonu :c:func:`PyArg_ParseTuple` (:c:func:" -#~ "`PyArg_ParseTupleAndKeywords` yerine) çağrısı yapıyorsa, tüm argümanları " -#~ "sadece konumsaldır." +#~ "Eğer mevcut C fonksiyonu :c:func:`PyArg_ParseTuple` " +#~ "(:c:func:`PyArg_ParseTupleAndKeywords` yerine) çağrısı yapıyorsa, tüm " +#~ "argümanları sadece konumsaldır." #, fuzzy #~ msgid "" @@ -504,9 +505,9 @@ msgstr "" #, fuzzy #~ msgid "" -#~ "For readability, most of the glue code has been generated to a :file:`.c." -#~ "h` file. You'll need to include that in your original :file:`.c` file, " -#~ "typically right after the clinic module block::" +#~ "For readability, most of the glue code has been generated to " +#~ "a :file:`.c.h` file. You'll need to include that in your " +#~ "original :file:`.c` file, typically right after the clinic module block::" #~ msgstr "" #~ "Okunabilirlik için, tutkal kodunun çoğu bir ``.c.h`` dosyasında " #~ "oluşturulmuştur. Bunu orijinal ``.c`` dosyanıza eklemeniz gerekir, tipik " @@ -521,26 +522,27 @@ msgstr "" #~ 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." +#~ "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 "" #~ "İlk olarak, her iki yerin de aynı argüman ayrıştırma işlevini " -#~ "kullandığından emin olun. Mevcut kod :c:func:`PyArg_ParseTuple` veya :c:" -#~ "func:`PyArg_ParseTupleAndKeywords` fonksiyonlarından birini çağırmalıdır; " -#~ "Argüman Kliniği tarafından oluşturulan kodun *tam olarak* aynı fonksiyonu " -#~ "çağırdığından emin olun." +#~ "kullandığından emin olun. Mevcut kod :c:func:`PyArg_ParseTuple` " +#~ "veya :c:func:`PyArg_ParseTupleAndKeywords` fonksiyonlarından birini " +#~ "çağırmalıdır; Argüman Kliniği tarafından oluşturulan kodun *tam olarak* " +#~ "aynı fonksiyonu çağırdığından emin olun." #, fuzzy #~ 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." +#~ "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 "" -#~ "İkinci olarak, :c:func:`PyArg_ParseTuple` veya :c:func:" -#~ "`PyArg_ParseTupleAndKeywords` işlevine aktarılan biçim dizesi, iki nokta " -#~ "üst üste veya noktalı virgülüne kadar mevcut işlevde elle yazılmış olanla " -#~ "*tam olarak* aynı olmalıdır." +#~ "İkinci olarak, :c:func:`PyArg_ParseTuple` " +#~ "veya :c:func:`PyArg_ParseTupleAndKeywords` işlevine aktarılan biçim " +#~ "dizesi, iki nokta üst üste veya noktalı virgülüne kadar mevcut işlevde " +#~ "elle yazılmış olanla *tam olarak* aynı olmalıdır." #, fuzzy #~ msgid "" @@ -700,8 +702,8 @@ msgstr "" #, fuzzy #~ msgid "" -#~ "For example, if we wanted to rename the C function names generated for :" -#~ "py:meth:`pickle.Pickler.dump`, it'd look like this::" +#~ "For example, if we wanted to rename the C function names generated " +#~ "for :py:meth:`pickle.Pickler.dump`, it'd look like this::" #~ msgstr "" #~ "Örneğin, ``pickle.Pickler.dump`` için oluşturulan C fonksiyon adlarını " #~ "yeniden adlandırmak istersek, şöyle görünecektir::" @@ -745,11 +747,11 @@ msgstr "" #, fuzzy #~ 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)." +#~ "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 "" #~ "Argümanlarını :c:func:`PyArg_UnpackTuple` ile ayrıştıran bir fonksiyonu " #~ "dönüştürmek için, her birini bir ``object`` olarak belirterek tüm " @@ -775,44 +777,45 @@ msgstr "" #~ "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." +#~ "to simulate optional arguments back " +#~ "before :c:func:`PyArg_ParseTupleAndKeywords` was created." #~ msgstr "" #~ "Bazı eski fonksiyonların argümanlarını ayrıştırmak için zor bir yaklaşımı " #~ "vardır: konumsal argümanların sayısını sayarlar, ardından kaç tane " -#~ "konumsal argüman olduğuna bağlı olarak birkaç farklı :c:func:" -#~ "`PyArg_ParseTuple` çağrısından birini çağırmak için bir ``switch`` deyimi " -#~ "kullanırlar. (Bu fonksiyonlar sadece anahtar kelime argümanlarını kabul " -#~ "edemez.) Bu yaklaşım :c:func:`PyArg_ParseTupleAndKeywords` oluşturulmadan " -#~ "önce isteğe bağlı argümanları simüle etmek için kullanılıyordu." - -#, fuzzy -#~ 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 :py:func:`range`, which has an " -#~ "optional argument on the *left* side of its required argument! Another " -#~ "example is :py:meth:`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 "" -#~ "Bu yaklaşımı kullanan fonksiyonlar genellikle :c:func:" -#~ "`PyArg_ParseTupleAndKeywords`, isteğe bağlı argümanlar ve varsayılan " -#~ "değerleri kullanacak şekilde dönüştürülebilse de, bu her zaman mümkün " -#~ "değildir. Bu eski fonksiyonlardan bazıları :c:func:" -#~ "`PyArg_ParseTupleAndKeywords` fonksiyonunun doğrudan desteklemediği " -#~ "davranışlara sahiptir. En bariz örnek, gerekli argümanının *sol* " -#~ "tarafında isteğe bağlı bir argümana sahip olan yerleşik ``range()`` " +#~ "konumsal argüman olduğuna bağlı olarak birkaç " +#~ "farklı :c:func:`PyArg_ParseTuple` çağrısından birini çağırmak için bir " +#~ "``switch`` deyimi kullanırlar. (Bu fonksiyonlar sadece anahtar kelime " +#~ "argümanlarını kabul edemez.) Bu " +#~ "yaklaşım :c:func:`PyArg_ParseTupleAndKeywords` oluşturulmadan önce isteğe " +#~ "bağlı argümanları simüle etmek için kullanılıyordu." + +#, fuzzy +#~ 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 :py:func:`range`, which has an optional argument on the *left* " +#~ "side of its required argument! Another example " +#~ "is :py:meth:`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 "" +#~ "Bu yaklaşımı kullanan fonksiyonlar " +#~ "genellikle :c:func:`PyArg_ParseTupleAndKeywords`, isteğe bağlı argümanlar " +#~ "ve varsayılan değerleri kullanacak şekilde dönüştürülebilse de, bu her " +#~ "zaman mümkün değildir. Bu eski fonksiyonlardan " +#~ "bazıları :c:func:`PyArg_ParseTupleAndKeywords` fonksiyonunun doğrudan " +#~ "desteklemediği davranışlara sahiptir. En bariz örnek, gerekli argümanının " +#~ "*sol* tarafında isteğe bağlı bir argümana sahip olan yerleşik ``range()`` " #~ "fonksiyonudur! Diğer bir örnek ise her zaman birlikte belirtilmesi " -#~ "gereken iki argümandan oluşan bir gruba sahip olan ``curses.window." -#~ "addch()`` fonksiyonudur. (Argümanlar ``x`` ve ``y`` olarak adlandırılır; " -#~ "fonksiyonu ``x`` değerini girerek çağırırsanız, ``y`` değerini de " -#~ "girmeniz gerekir ve ``x`` değerini girmezseniz ``y`` değerini de " -#~ "giremezsiniz)" +#~ "gereken iki argümandan oluşan bir gruba sahip olan " +#~ "``curses.window.addch()`` fonksiyonudur. (Argümanlar ``x`` ve ``y`` " +#~ "olarak adlandırılır; fonksiyonu ``x`` değerini girerek çağırırsanız, " +#~ "``y`` değerini de girmeniz gerekir ve ``x`` değerini girmezseniz ``y`` " +#~ "değerini de giremezsiniz)" #~ msgid "" #~ "In any case, the goal of Argument Clinic is to support argument parsing " @@ -853,15 +856,15 @@ msgstr "" #~ 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 :py:meth:`curses." -#~ "window.addch` uses optional groups to make the first two parameters and " -#~ "the last parameter optional::" +#~ "after these parameters. As an example, here's " +#~ "how :py:meth:`curses.window.addch` uses optional groups to make the first " +#~ "two parameters and the last parameter optional::" #~ msgstr "" #~ "İsteğe bağlı bir grup belirtmek için, birlikte gruplamak istediğiniz " #~ "parametrelerden önce tek başına bir satıra ``[`` ve bu parametrelerden " -#~ "sonra tek başına bir satıra ``]`` ekleyin. Örnek olarak, ``curses.window." -#~ "addch`` ilk iki parametreyi ve son parametreyi isteğe bağlı yapmak için " -#~ "isteğe bağlı grupları nasıl kullanır::" +#~ "sonra tek başına bir satıra ``]`` ekleyin. Örnek olarak, " +#~ "``curses.window.addch`` ilk iki parametreyi ve son parametreyi isteğe " +#~ "bağlı yapmak için isteğe bağlı grupları nasıl kullanır::" #~ msgid "Notes:" #~ msgstr "Notlar:" @@ -1065,9 +1068,9 @@ msgstr "" #~ msgstr "``converter``" #~ 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." +#~ "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 "" #~ "Sadece ``object`` dönüştürücü tarafından desteklenir. Bu nesneyi yerel " #~ "bir türe dönüştürmek için kullanılacak :ref:`C \"converter function\" " @@ -1124,12 +1127,13 @@ msgstr "" #, fuzzy #~ msgid "" #~ "Please note, not every possible combination of arguments will work. " -#~ "Usually these arguments are implemented by specific :c:func:" -#~ "`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.)" +#~ "Usually these arguments are implemented by " +#~ "specific :c:func:`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 "" #~ "Lütfen her olası argüman kombinasyonunun çalışmayacağını unutmayın. " #~ "Genellikle bu argümanlar belirli davranışlara sahip belirli " @@ -1437,14 +1441,14 @@ msgstr "" #~ 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)." +#~ "``'*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 "" #~ "``Py_buffer`` dönüştürücüsünü (veya ``'s*'``, ``'w*'``, ``'*y'`` veya " -#~ "``'z*'`` eski dönüştürücülerini) kullanırken, sağlanan tampon üzerinde :c:" -#~ "func:`PyBuffer_Release` çağrısı yapmamanız gerekir. Argument Clinic bunu " -#~ "sizin için yapan kodu üretir (ayrıştırma işlevinde)." +#~ "``'z*'`` eski dönüştürücülerini) kullanırken, sağlanan tampon " +#~ "üzerinde :c:func:`PyBuffer_Release` çağrısı yapmamanız gerekir. Argument " +#~ "Clinic bunu sizin için yapan kodu üretir (ayrıştırma işlevinde)." #, fuzzy #~ msgid "How to use advanced converters" @@ -1505,14 +1509,15 @@ msgstr "" #~ msgstr "" #~ "Argüman Kliniği kullanımıyla ilgili olası bir sorun: ``e`` ile başlayan " #~ "biçim birimleri için bazı olası esneklikleri ortadan kaldırır. Elle bir " -#~ "``PyArg_Parse`` çağrısı yazarken, teorik olarak :c:func:" -#~ "`PyArg_ParseTuple`'a hangi kodlama dizgesini aktaracağınıza çalışma " -#~ "zamanında karar verebilirsiniz. Ancak şimdi bu dizge Argüman Kliniği-" -#~ "önişleme zamanında sabit kodlanmalıdır. Bu sınırlama kasıtlıdır; bu " -#~ "format birimini desteklemeyi çok daha kolay hale getirdi ve gelecekteki " -#~ "optimizasyonlara izin verebilir. Bu kısıtlama mantıksız görünmüyor; " -#~ "CPython'un kendisi, biçim birimleri ``e`` ile başlayan parametreler için " -#~ "her zaman statik sabit kodlu kodlama dizeleri geçirir." +#~ "``PyArg_Parse`` çağrısı yazarken, teorik " +#~ "olarak :c:func:`PyArg_ParseTuple`'a hangi kodlama dizgesini " +#~ "aktaracağınıza çalışma zamanında karar verebilirsiniz. Ancak şimdi bu " +#~ "dizge Argüman Kliniği-önişleme zamanında sabit kodlanmalıdır. Bu " +#~ "sınırlama kasıtlıdır; bu format birimini desteklemeyi çok daha kolay hale " +#~ "getirdi ve gelecekteki optimizasyonlara izin verebilir. Bu kısıtlama " +#~ "mantıksız görünmüyor; CPython'un kendisi, biçim birimleri ``e`` ile " +#~ "başlayan parametreler için her zaman statik sabit kodlu kodlama dizeleri " +#~ "geçirir." #~ msgid "" #~ "Default values for parameters can be any of a number of values. At their " @@ -1699,12 +1704,12 @@ msgstr "" #, fuzzy #~ msgid "" -#~ "By default, the impl function Argument Clinic generates for you returns :" -#~ "c:type:`PyObject * `. But your C function often computes some C " -#~ "type, then converts it into the :c:type:`!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?" +#~ "By default, the impl function Argument Clinic generates for you " +#~ "returns :c:type:`PyObject * `. But your C function often " +#~ "computes some C type, then converts it into the :c:type:`!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 "" #~ "Argüman Kliniği'nin sizin için oluşturduğu impl fonksiyonu varsayılan " #~ "olarak ``PyObject *`` döndürür. Ancak C fonksiyonunuz genellikle bir C " @@ -1847,9 +1852,9 @@ msgstr "" #~ msgstr "Bir fonksiyonu klonlamak için sözdizimi şöyledir::" #~ 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.)" +#~ "(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 "" #~ "(Fonksiyonlar farklı modüllerde veya sınıflarda olabilir. Örnekte " #~ "``module.class`` yazdım, sadece *her iki* fonksiyon için de tam yolu " @@ -1952,8 +1957,9 @@ msgstr "" #, fuzzy #~ 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 :" -#~ "class:`!self_converter` but overwriting the :py:attr:`!type` member::" +#~ "type for ``self``, it's best to create your own converter, " +#~ "subclassing :class:`!self_converter` but overwriting the :py:attr:`!type` " +#~ "member::" #~ msgstr "" #~ "Öte yandan, ``self`` için aynı türü kullanacak çok sayıda işleviniz " #~ "varsa, en iyisi ``self_converter`` alt sınıfını kullanarak, ancak " @@ -1967,9 +1973,9 @@ msgstr "" #~ "Argument Clinic facilitates gaining access to the defining class of a " #~ "method. This is useful for :ref:`heap type ` methods that " #~ "need to fetch module level state. Use :c:func:`PyType_FromModuleAndSpec` " -#~ "to associate a new heap type with a module. You can now use :c:func:" -#~ "`PyType_GetModuleState` on the defining class to fetch the module state, " -#~ "for example from a module method." +#~ "to associate a new heap type with a module. You can now " +#~ "use :c:func:`PyType_GetModuleState` on the defining class to fetch the " +#~ "module state, for example from a module method." #~ msgstr "" #~ "Argüman Kliniği, bir metodun tanımlayıcı sınıfına erişim sağlamayı " #~ "kolaylaştırır. Bu, modül düzeyinde durum getirmesi gereken :ref:`heap " @@ -2016,8 +2022,8 @@ msgstr "" #, fuzzy #~ msgid "" #~ "The ``defining_class`` converter is not compatible with :py:meth:`!" -#~ "__init__` and :py:meth:`!__new__` methods, which cannot use the :c:macro:" -#~ "`METH_METHOD` convention." +#~ "__init__` and :py:meth:`!__new__` methods, which cannot use " +#~ "the :c:macro:`METH_METHOD` convention." #~ msgstr "" #~ "``defining_class`` dönüştürücüsü, ``METH_METHOD`` kuralını kullanamayan " #~ "``__init__`` ve ``__new__`` yöntemleriyle uyumlu değildir." @@ -2025,16 +2031,16 @@ msgstr "" #, fuzzy #~ msgid "" #~ "It is not possible to use ``defining_class`` with slot methods. In order " -#~ "to fetch the module state from such methods, use :c:func:" -#~ "`PyType_GetModuleByDef` to look up the module and then :c:func:" -#~ "`PyModule_GetState` to fetch the module state. Example from the " -#~ "``setattro`` slot method in :source:`Modules/_threadmodule.c`::" +#~ "to fetch the module state from such methods, " +#~ "use :c:func:`PyType_GetModuleByDef` to look up the module and " +#~ "then :c:func:`PyModule_GetState` to fetch the module state. Example from " +#~ "the ``setattro`` slot method in :source:`Modules/_threadmodule.c`::" #~ msgstr "" #~ "Slot metotları ile ``defining_class`` kullanmak mümkün değildir. Bu tür " -#~ "yöntemlerden modül durumunu almak için, modülü aramak için :c:func:" -#~ "`PyType_GetModuleByDef` ve ardından modül durumunu almak için :c:func:" -#~ "`PyModule_GetState` kullanın. ``Modules/_threadmodule.c`` içindeki " -#~ "``setattro`` slot yönteminden örnek::" +#~ "yöntemlerden modül durumunu almak için, modülü aramak " +#~ "için :c:func:`PyType_GetModuleByDef` ve ardından modül durumunu almak " +#~ "için :c:func:`PyModule_GetState` kullanın. ``Modules/_threadmodule.c`` " +#~ "içindeki ``setattro`` slot yönteminden örnek::" #~ msgid "See also :pep:`573`." #~ msgstr "Bkz: :pep:`573`." @@ -2047,14 +2053,15 @@ msgstr "" #~ msgid "" #~ "A converter is a Python class that inherits from :py:class:`CConverter`. " #~ "The main purpose of a custom converter, is for parameters parsed with the " -#~ "``O&`` format unit --- parsing such a parameter means calling a :c:func:" -#~ "`PyArg_ParseTuple` \"converter function\"." +#~ "``O&`` format unit --- parsing such a parameter means calling " +#~ "a :c:func:`PyArg_ParseTuple` \"converter function\"." #~ msgstr "" #~ "Önceki bölümde ima ettiğimiz gibi... kendi dönüştürücülerinizi " #~ "yazabilirsiniz! Bir dönüştürücü basitçe ``CConverter``'dan miras alan bir " #~ "Python sınıfıdır. Özel bir dönüştürücünün ana amacı, ``O&`` biçimini " -#~ "kullanan bir parametreniz varsa, bu parametreyi birim ayrıştırmak, bir :c:" -#~ "func:`PyArg_ParseTuple` \"dönüştürücü işlevi\" çağırmak anlamına gelir." +#~ "kullanan bir parametreniz varsa, bu parametreyi birim ayrıştırmak, " +#~ "bir :c:func:`PyArg_ParseTuple` \"dönüştürücü işlevi\" çağırmak anlamına " +#~ "gelir." #, fuzzy #~ msgid "" @@ -2070,13 +2077,13 @@ msgstr "" #, fuzzy #~ msgid "" -#~ "Instead of subclassing :py:meth:`!CConverter.__init__`, write a :py:meth:" -#~ "`!converter_init` method. :py:meth:`!converter_init` always accepts a " -#~ "*self* parameter. After *self*, all additional parameters **must** be " -#~ "keyword-only. Any arguments passed to the converter in Argument Clinic " -#~ "will be passed along to your :py:meth:`!converter_init` method. See :py:" -#~ "class:`CConverter` for a list of members you may wish to specify in your " -#~ "subclass." +#~ "Instead of subclassing :py:meth:`!CConverter.__init__`, write " +#~ "a :py:meth:`!converter_init` method. :py:meth:`!converter_init` always " +#~ "accepts a *self* parameter. After *self*, all additional parameters " +#~ "**must** be keyword-only. Any arguments passed to the converter in " +#~ "Argument Clinic will be passed along to your :py:meth:`!converter_init` " +#~ "method. See :py:class:`CConverter` for a list of members you may wish to " +#~ "specify in your subclass." #~ msgstr "" #~ "``CConverter.__init__`` alt sınıfını kullanmamalısınız. Bunun yerine, " #~ "bir ``converter_init()`` fonksiyonu yazmalısınız. ``converter_init()`` " @@ -2096,10 +2103,10 @@ msgstr "" #, fuzzy #~ msgid "" #~ "This block adds a converter named ``ssize_t`` to Argument Clinic. " -#~ "Parameters declared as ``ssize_t`` will be declared with type :c:type:" -#~ "`Py_ssize_t`, and will be parsed by the ``'O&'`` format unit, which will " -#~ "call the :c:func:`!ssize_t_converter` converter C function. ``ssize_t`` " -#~ "variables automatically support default values." +#~ "Parameters declared as ``ssize_t`` will be declared with " +#~ "type :c:type:`Py_ssize_t`, and will be parsed by the ``'O&'`` format " +#~ "unit, which will call the :c:func:`!ssize_t_converter` converter C " +#~ "function. ``ssize_t`` variables automatically support default values." #~ msgstr "" #~ "Bu blok Argüman Kliniğine ``ssize_t`` adında bir dönüştürücü ekler. " #~ "``ssize_t`` olarak bildirilen parametreler :c:type:`Py_ssize_t` türünde " @@ -2135,9 +2142,9 @@ msgstr "" #~ msgid "" #~ "Return converters must subclass :py:class:`!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 :" -#~ "source:`Tools/clinic/clinic.py`, specifically the implementation of :py:" -#~ "class:`!CReturnConverter` and all its subclasses." +#~ "used yet. If you wish to write your own return converter, please " +#~ "read :source:`Tools/clinic/clinic.py`, specifically the implementation " +#~ "of :py:class:`!CReturnConverter` and all its subclasses." #~ msgstr "" #~ "Dönüş dönüştürücüleri ``CReturnConverter`` alt sınıfına sahip olmalıdır. " #~ "Henüz yaygın olarak kullanılmadıkları için özel dönüş dönüştürücüleri " @@ -2178,9 +2185,9 @@ msgstr "" #, fuzzy #~ msgid "" -#~ "You can convert :c:member:`~PyTypeObject.tp_new` and :c:member:" -#~ "`~PyTypeObject.tp_init` functions. Just name them ``__new__`` or " -#~ "``__init__`` as appropriate. Notes:" +#~ "You can convert :c:member:`~PyTypeObject.tp_new` " +#~ "and :c:member:`~PyTypeObject.tp_init` functions. Just name them " +#~ "``__new__`` or ``__init__`` as appropriate. Notes:" #~ msgstr "" #~ "``tp_new`` ve ``tp_init`` fonksiyonlarını dönüştürebilirsiniz. Bunları " #~ "uygun şekilde ``__new__`` veya ``__init__`` olarak adlandırmanız " @@ -2339,10 +2346,10 @@ msgstr "" #~ 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 :file:`_pickle.c` would be written to :file:`_pickle." -#~ "clinic.c`.)" +#~ "where ``basename`` and ``extension`` were assigned the output from " +#~ "``os.path.splitext()`` run on the current file. (Example: the ``file`` " +#~ "destination for :file:`_pickle.c` would be written " +#~ "to :file:`_pickle.clinic.c`.)" #~ msgstr "" #~ "Klinik tarafından otomatik olarak oluşturulacak ayrı bir \"klinik " #~ "dosyası\". Dosya için seçilen dosya adı ``{basename}.clinic{extension}`` " @@ -3068,8 +3075,8 @@ msgstr "" #~ "Well, except for one difference: ``inspect.signature()`` run on your " #~ "function should now provide a valid signature!" #~ msgstr "" -#~ "Tek bir fark dışında: fonksiyonunuz üzerinde çalıştırılan ``inspect." -#~ "signature()`` artık geçerli bir imza sağlamalıdır!" +#~ "Tek bir fark dışında: fonksiyonunuz üzerinde çalıştırılan " +#~ "``inspect.signature()`` artık geçerli bir imza sağlamalıdır!" #~ msgid "Advanced Topics" #~ msgstr "İleri Düzey Konular" diff --git a/howto/curses.po b/howto/curses.po index aa7b0178c..8608add1a 100644 --- a/howto/curses.po +++ b/howto/curses.po @@ -172,9 +172,9 @@ 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. ::" +"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 "" #: howto/curses.rst:113 @@ -196,9 +196,9 @@ msgstr "" #: howto/curses.rst:122 msgid "" -"to reverse the curses-friendly terminal settings. Then call the :func:" -"`~curses.endwin` function to restore the terminal to its original operating " -"mode. ::" +"to reverse the curses-friendly terminal settings. Then call " +"the :func:`~curses.endwin` function to restore the terminal to its original " +"operating mode. ::" msgstr "" #: howto/curses.rst:126 @@ -245,11 +245,11 @@ msgid "" "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." +"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 "" #: howto/curses.rst:165 @@ -268,9 +268,9 @@ 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. ::" +"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 "" #: howto/curses.rst:178 @@ -292,17 +292,18 @@ msgstr "" #: howto/curses.rst:190 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)``." +"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 "" #: howto/curses.rst:195 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." +"immediately show up on the display. Instead you must call " +"the :meth:`~curses.window.refresh` method of window objects to update the " +"screen." msgstr "" #: howto/curses.rst:200 @@ -310,8 +311,8 @@ 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 " +"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 "" @@ -406,9 +407,9 @@ msgstr "" #: howto/curses.rst:272 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." +"window object like any other, and methods such " +"as :meth:`~curses.window.addstr` accept multiple argument forms. Usually " +"there are four different forms." msgstr "" #: howto/curses.rst:278 @@ -500,8 +501,8 @@ msgstr "" 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 " +"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 "" @@ -616,10 +617,10 @@ msgstr "" 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." +"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 "" #: howto/curses.rst:389 @@ -643,10 +644,10 @@ msgstr "" #: howto/curses.rst:399 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." +"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 "" #: howto/curses.rst:405 @@ -676,10 +677,10 @@ msgid "" "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." +"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 "" #: howto/curses.rst:427 @@ -688,9 +689,9 @@ msgstr "" #: howto/curses.rst:429 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 :" -"pypi:`Urwid` have more extensive collections of widgets.)" +"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 :pypi:`Urwid` have more extensive collections of widgets.)" msgstr "" #: howto/curses.rst:433 @@ -715,14 +716,15 @@ msgstr "" #: howto/curses.rst:445 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." +"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 "" #: howto/curses.rst:455 @@ -730,9 +732,10 @@ 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::" +"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 "" #: howto/curses.rst:462 @@ -759,11 +762,11 @@ msgstr "" #: howto/curses.rst:478 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. ::" +"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 "" #: howto/curses.rst:484 @@ -777,9 +780,10 @@ msgstr "" #: howto/curses.rst:489 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::" +"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 "" #: howto/curses.rst:495 @@ -825,8 +829,8 @@ 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 :" -"ref:`ACS_\\* ` characters available to you." +"quirks, and provide complete lists of all the functions, attributes, " +"and :ref:`ACS_\\* ` characters available to you." msgstr "" #: howto/curses.rst:531 @@ -835,8 +839,8 @@ msgid "" "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." +"would be welcome; see `the Python Developer's Guide `_ to learn more about submitting patches to Python." msgstr "" #: howto/curses.rst:539 diff --git a/howto/descriptor.po b/howto/descriptor.po index 15f76fd5c..191d71d92 100644 --- a/howto/descriptor.po +++ b/howto/descriptor.po @@ -73,8 +73,9 @@ msgstr "" msgid "" "The last section has pure Python equivalents for built-in descriptors that " "are written in C. Read this if you're curious about how functions turn into " -"bound methods or about the implementation of common tools like :func:" -"`classmethod`, :func:`staticmethod`, :func:`property`, and :term:`__slots__`." +"bound methods or about the implementation of common tools " +"like :func:`classmethod`, :func:`staticmethod`, :func:`property`, " +"and :term:`__slots__`." msgstr "" #: howto/descriptor.rst:36 @@ -364,9 +365,9 @@ msgstr "" #: howto/descriptor.rst:256 msgid "" -"An interactive session shows that the :class:`Person` class has called :meth:" -"`__set_name__` so that the field names would be recorded. Here we call :" -"func:`vars` to look up the descriptor without triggering it:" +"An interactive session shows that the :class:`Person` class has " +"called :meth:`__set_name__` so that the field names would be recorded. Here " +"we call :func:`vars` to look up the descriptor without triggering it:" msgstr "" #: howto/descriptor.rst:260 @@ -409,8 +410,8 @@ msgstr "" #: howto/descriptor.rst:297 msgid "" -"A :term:`descriptor` is what we call any object that defines :meth:" -"`__get__`, :meth:`__set__`, or :meth:`__delete__`." +"A :term:`descriptor` is what we call any object that " +"defines :meth:`__get__`, :meth:`__set__`, or :meth:`__delete__`." msgstr "" #: howto/descriptor.rst:300 @@ -450,9 +451,9 @@ msgstr "" #: howto/descriptor.rst:319 msgid "" "Descriptors are used throughout the language. It is how functions turn into " -"bound methods. Common tools like :func:`classmethod`, :func:" -"`staticmethod`, :func:`property`, and :func:`functools.cached_property` are " -"all implemented as descriptors." +"bound methods. Common tools " +"like :func:`classmethod`, :func:`staticmethod`, :func:`property`, " +"and :func:`functools.cached_property` are all implemented as descriptors." msgstr "" #: howto/descriptor.rst:326 @@ -506,8 +507,8 @@ msgstr "" #: howto/descriptor.rst:363 msgid "" -"Custom validators need to inherit from :class:`Validator` and must supply a :" -"meth:`validate` method to test various restrictions as needed." +"Custom validators need to inherit from :class:`Validator` and must supply " +"a :meth:`validate` method to test various restrictions as needed." msgstr "" #: howto/descriptor.rst:368 @@ -525,9 +526,9 @@ msgstr "" #: howto/descriptor.rst:374 msgid "" -":class:`Number` verifies that a value is either an :class:`int` or :class:" -"`float`. Optionally, it verifies that a value is between a given minimum or " -"maximum." +":class:`Number` verifies that a value is either an :class:`int` " +"or :class:`float`. Optionally, it verifies that a value is between a given " +"minimum or maximum." msgstr "" #: howto/descriptor.rst:378 @@ -678,9 +679,10 @@ msgstr "" #: howto/descriptor.rst:500 msgid "" "In general, a descriptor is an attribute value that has one of the methods " -"in the descriptor protocol. Those methods are :meth:`__get__`, :meth:" -"`__set__`, and :meth:`__delete__`. If any of those methods are defined for " -"an attribute, it is said to be a :term:`descriptor`." +"in the descriptor protocol. Those methods " +"are :meth:`__get__`, :meth:`__set__`, and :meth:`__delete__`. If any of " +"those methods are defined for an attribute, it is said to be " +"a :term:`descriptor`." msgstr "" #: howto/descriptor.rst:505 @@ -698,10 +700,10 @@ msgstr "" #: howto/descriptor.rst:514 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. Descriptors simplify " -"the underlying C code and offer a flexible set of new tools for everyday " -"Python programs." +"mechanism behind properties, methods, static methods, class methods, " +"and :func:`super`. They are used throughout Python itself. Descriptors " +"simplify the underlying C code and offer a flexible set of new tools for " +"everyday Python programs." msgstr "" #: howto/descriptor.rst:522 @@ -746,10 +748,10 @@ msgstr "" #: howto/descriptor.rst:545 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." +"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 "" #: howto/descriptor.rst:552 @@ -758,8 +760,8 @@ msgstr "" #: howto/descriptor.rst:554 msgid "" -"A descriptor can be called directly with ``desc.__get__(obj)`` or ``desc." -"__get__(None, cls)``." +"A descriptor can be called directly with ``desc.__get__(obj)`` or " +"``desc.__get__(None, cls)``." msgstr "" #: howto/descriptor.rst:557 @@ -796,8 +798,8 @@ msgstr "" #: howto/descriptor.rst:577 msgid "" -"If a descriptor is found for ``a.x``, then it is invoked with: ``desc." -"__get__(a, type(a))``." +"If a descriptor is found for ``a.x``, then it is invoked with: " +"``desc.__get__(a, type(a))``." msgstr "" #: howto/descriptor.rst:580 @@ -845,9 +847,9 @@ msgstr "" #: howto/descriptor.rst:723 msgid "" "Instead, it is the dot operator and the :func:`getattr` function that are " -"responsible for invoking :meth:`__getattr__` whenever :meth:" -"`__getattribute__` raises an :exc:`AttributeError`. Their logic is " -"encapsulated in a helper function:" +"responsible for invoking :meth:`__getattr__` " +"whenever :meth:`__getattribute__` raises an :exc:`AttributeError`. Their " +"logic is encapsulated in a helper function:" msgstr "" #: howto/descriptor.rst:728 @@ -868,10 +870,10 @@ msgstr "" #: howto/descriptor.rst:775 msgid "" -"The logic for a dotted lookup such as ``A.x`` is in :meth:`type." -"__getattribute__`. The steps are similar to those for :meth:`object." -"__getattribute__` but the instance dictionary lookup is replaced by a search " -"through the class's :term:`method resolution order`." +"The logic for a dotted lookup such as ``A.x`` is " +"in :meth:`type.__getattribute__`. The steps are similar to those " +"for :meth:`object.__getattribute__` but the instance dictionary lookup is " +"replaced by a search through the class's :term:`method resolution order`." msgstr "" #: howto/descriptor.rst:780 @@ -880,8 +882,8 @@ msgstr "" #: howto/descriptor.rst:782 msgid "" -"The full C implementation can be found in :c:func:`!type_getattro` and :c:" -"func:`!_PyType_Lookup` in :source:`Objects/typeobject.c`." +"The full C implementation can be found in :c:func:`!type_getattro` " +"and :c:func:`!_PyType_Lookup` in :source:`Objects/typeobject.c`." msgstr "" #: howto/descriptor.rst:787 @@ -896,16 +898,16 @@ msgstr "" #: howto/descriptor.rst:792 msgid "" -"A dotted lookup such as ``super(A, obj).m`` searches ``obj.__class__." -"__mro__`` for the base class ``B`` immediately following ``A`` and then " -"returns ``B.__dict__['m'].__get__(obj, A)``. If not a descriptor, ``m`` is " -"returned unchanged." +"A dotted lookup such as ``super(A, obj).m`` searches " +"``obj.__class__.__mro__`` for the base class ``B`` immediately following " +"``A`` and then returns ``B.__dict__['m'].__get__(obj, A)``. If not a " +"descriptor, ``m`` is returned unchanged." msgstr "" #: howto/descriptor.rst:797 msgid "" -"The full C implementation can be found in :c:func:`!super_getattro` in :" -"source:`Objects/typeobject.c`. A pure Python equivalent can be found in " +"The full C implementation can be found in :c:func:`!super_getattro` " +"in :source:`Objects/typeobject.c`. A pure Python equivalent can be found in " "`Guido's Tutorial `_." msgstr "" @@ -930,8 +932,8 @@ msgstr "" #: howto/descriptor.rst:813 msgid "" -"Classes inherit this machinery from :class:`object`, :class:`type`, or :func:" -"`super`." +"Classes inherit this machinery from :class:`object`, :class:`type`, " +"or :func:`super`." msgstr "" #: howto/descriptor.rst:816 @@ -990,8 +992,8 @@ msgstr "" #: howto/descriptor.rst:850 msgid "" "The following code is a simplified skeleton showing how data descriptors " -"could be used to implement an `object relational mapping `_." +"could be used to implement an `object relational mapping `_." msgstr "" #: howto/descriptor.rst:854 @@ -1021,9 +1023,9 @@ msgstr "" #: howto/descriptor.rst:873 msgid "" -"We can use the :class:`Field` class to define `models `_ that describe the schema for each table in a " -"database:" +"We can use the :class:`Field` class to define `models `_ that describe the schema for each " +"table in a database:" msgstr "" #: howto/descriptor.rst:877 @@ -1262,10 +1264,10 @@ msgstr "" #: howto/descriptor.rst:1185 msgid "" -"To support automatic creation of methods, functions include the :meth:" -"`__get__` method for binding methods during attribute access. This means " -"that functions are non-data descriptors that return bound methods during " -"dotted lookup from an instance. Here's how it works:" +"To support automatic creation of methods, functions include " +"the :meth:`__get__` method for binding methods during attribute access. " +"This means that functions are non-data descriptors that return bound methods " +"during dotted lookup from an instance. Here's how it works:" msgstr "" #: howto/descriptor.rst:1190 @@ -1306,8 +1308,9 @@ msgstr "" #: howto/descriptor.rst:1217 msgid "" -"Accessing the function through the class dictionary does not invoke :meth:" -"`__get__`. Instead, it just returns the underlying function object::" +"Accessing the function through the class dictionary does not " +"invoke :meth:`__get__`. Instead, it just returns the underlying function " +"object::" msgstr "" #: howto/descriptor.rst:1220 @@ -1376,8 +1379,8 @@ msgstr "" 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 ``cls." -"f(*args)`` becomes ``f(*args)``." +"transforms an ``obj.f(*args)`` call into ``f(obj, *args)``. Calling " +"``cls.f(*args)`` becomes ``f(*args)``." msgstr "" #: howto/descriptor.rst:1260 @@ -1431,10 +1434,10 @@ msgstr "" #: howto/descriptor.rst:1277 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." +"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 "" #: howto/descriptor.rst:1283 @@ -1479,8 +1482,8 @@ msgstr "" #: howto/descriptor.rst:1312 msgid "" -"Using the non-data descriptor protocol, a pure Python version of :func:" -"`staticmethod` would look like this:" +"Using the non-data descriptor protocol, a pure Python version " +"of :func:`staticmethod` would look like this:" msgstr "" #: howto/descriptor.rst:1315 @@ -1505,9 +1508,9 @@ msgstr "" msgid "" "The :func:`functools.update_wrapper` call adds a ``__wrapped__`` attribute " "that refers to the underlying function. Also it carries forward the " -"attributes necessary to make the wrapper look like the wrapped function: :" -"attr:`~function.__name__`, :attr:`~function.__qualname__`, :attr:`~function." -"__doc__`, and :attr:`~function.__annotations__`." +"attributes necessary to make the wrapper look like the wrapped " +"function: :attr:`~function.__name__`, :attr:`~function.__qualname__`, :attr:`~function.__doc__`, " +"and :attr:`~function.__annotations__`." msgstr "" #: howto/descriptor.rst:1401 @@ -1573,8 +1576,8 @@ msgstr "" #: howto/descriptor.rst:1448 msgid "" -"Using the non-data descriptor protocol, a pure Python version of :func:" -"`classmethod` would look like this:" +"Using the non-data descriptor protocol, a pure Python version " +"of :func:`classmethod` would look like this:" msgstr "" #: howto/descriptor.rst:1451 @@ -1626,9 +1629,9 @@ msgid "" "The :func:`functools.update_wrapper` call in ``ClassMethod`` adds a " "``__wrapped__`` attribute that refers to the underlying function. Also it " "carries forward the attributes necessary to make the wrapper look like the " -"wrapped function: :attr:`~function.__name__`, :attr:`~function." -"__qualname__`, :attr:`~function.__doc__`, and :attr:`~function." -"__annotations__`." +"wrapped " +"function: :attr:`~function.__name__`, :attr:`~function.__qualname__`, :attr:`~function.__doc__`, " +"and :attr:`~function.__annotations__`." msgstr "" #: howto/descriptor.rst:1553 diff --git a/howto/enum.po b/howto/enum.po index f915168b2..11639b14d 100644 --- a/howto/enum.po +++ b/howto/enum.po @@ -139,11 +139,11 @@ msgstr "" msgid "" "Unlike many languages that treat enumerations solely as name/value pairs, " "Python Enums can have behavior added. For example, :class:`datetime.date` " -"has two methods for returning the weekday: :meth:`weekday` and :meth:" -"`isoweekday`. The difference is that one of them counts from 0-6 and the " -"other from 1-7. Rather than keep track of that ourselves we can add a method " -"to the :class:`Weekday` enum to extract the day from the :class:`date` " -"instance and return the matching enum member::" +"has two methods for returning the weekday: :meth:`weekday` " +"and :meth:`isoweekday`. The difference is that one of them counts from 0-6 " +"and the other from 1-7. Rather than keep track of that ourselves we can add " +"a method to the :class:`Weekday` enum to extract the day from " +"the :class:`date` instance and return the matching enum member::" msgstr "" #: howto/enum.rst:84 @@ -262,8 +262,8 @@ msgstr "" #: howto/enum.rst:151 msgid "" ">>> chores_for_ethan = {\n" -"... 'feed the cat': Weekday.MONDAY | Weekday.WEDNESDAY | Weekday." -"FRIDAY,\n" +"... 'feed the cat': Weekday.MONDAY | Weekday.WEDNESDAY | " +"Weekday.FRIDAY,\n" "... 'do the dishes': Weekday.TUESDAY | Weekday.THURSDAY,\n" "... 'answer SO questions': Weekday.SATURDAY,\n" "... }" @@ -310,8 +310,8 @@ msgstr "" #: howto/enum.rst:188 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 " +"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 "" @@ -485,9 +485,9 @@ msgid "" ">>> list(Shape)\n" "[, , ]\n" ">>> list(Weekday)\n" -"[, , , , , , ]" +"[, , , " +", , , " +"]" msgstr "" #: howto/enum.rst:316 @@ -657,9 +657,9 @@ 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.), descriptors (methods are also descriptors), and variable " -"names listed in :attr:`_ignore_`." +"enumeration, with the exception of special methods " +"(:meth:`__str__`, :meth:`__add__`, etc.), descriptors (methods are also " +"descriptors), and variable names listed in :attr:`_ignore_`." msgstr "" #: howto/enum.rst:429 @@ -740,8 +740,8 @@ msgstr "" #: howto/enum.rst:483 msgid "" -"When inheriting from a :class:`~dataclasses.dataclass`, the :meth:`~Enum." -"__repr__` omits the inherited class' name. For example::" +"When inheriting from a :class:`~dataclasses.dataclass`, " +"the :meth:`~Enum.__repr__` omits the inherited class' name. For example::" msgstr "" #: howto/enum.rst:486 @@ -763,8 +763,8 @@ msgstr "" #: howto/enum.rst:500 msgid "" -"Use the :func:`!dataclass` argument ``repr=False`` to use the standard :func:" -"`repr`." +"Use the :func:`!dataclass` argument ``repr=False`` to use the " +"standard :func:`repr`." msgstr "" #: howto/enum.rst:503 @@ -804,9 +804,9 @@ msgstr "" #: howto/enum.rst:527 msgid "" -"It is possible to modify how enum members are pickled/unpickled by defining :" -"meth:`__reduce_ex__` in the enumeration class. The default method is by-" -"value, but enums with complicated values may want to use by-name::" +"It is possible to modify how enum members are pickled/unpickled by " +"defining :meth:`__reduce_ex__` in the enumeration class. The default method " +"is by-value, but enums with complicated values may want to use by-name::" msgstr "" #: howto/enum.rst:531 @@ -899,10 +899,10 @@ msgstr "" #: howto/enum.rst:591 msgid "" -"The new pickle protocol 4 also, in some circumstances, relies on :attr:" -"`~type.__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::" +"The new pickle protocol 4 also, in some circumstances, relies " +"on :attr:`~type.__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 "" #: howto/enum.rst:596 @@ -995,10 +995,10 @@ msgstr "" #: howto/enum.rst:647 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::" +"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 "" #: howto/enum.rst:652 @@ -1076,9 +1076,9 @@ 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, if possible. Like :class:`IntEnum`, :class:" -"`IntFlag` members are also integers and can be used wherever an :class:`int` " -"is used." +"an :class:`IntFlag` member, if possible. " +"Like :class:`IntEnum`, :class:`IntFlag` members are also integers and can be " +"used wherever an :class:`int` is used." msgstr "" #: howto/enum.rst:713 @@ -1143,8 +1143,8 @@ msgstr "" #: howto/enum.rst:761 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`::" +"that if no flags are set (the value is 0), its boolean evaluation " +"is :data:`False`::" msgstr "" #: howto/enum.rst:764 @@ -1199,10 +1199,10 @@ msgstr "" #: howto/enum.rst:797 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 " +"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 "" @@ -1280,10 +1280,10 @@ 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." +"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 "" #: howto/enum.rst:866 @@ -1305,8 +1305,8 @@ msgstr "" #: howto/enum.rst:874 msgid "" "This demonstrates how similar derived enumerations can be defined; for " -"example a :class:`FloatEnum` that mixes in :class:`float` instead of :class:" -"`int`." +"example a :class:`FloatEnum` that mixes in :class:`float` instead " +"of :class:`int`." msgstr "" #: howto/enum.rst:877 @@ -1315,24 +1315,24 @@ msgstr "" #: howto/enum.rst:879 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." +"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 "" #: howto/enum.rst:882 msgid "" -"Mix-in types must be subclassable. For example, :class:`bool` and :class:" -"`range` are not subclassable and will throw an error during Enum creation if " -"used as the mix-in type." +"Mix-in types must be subclassable. For example, :class:`bool` " +"and :class:`range` are not subclassable and will throw an error during Enum " +"creation if used as the mix-in type." msgstr "" #: howto/enum.rst:885 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 type." +"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 type." msgstr "" #: howto/enum.rst:889 @@ -1344,28 +1344,29 @@ msgstr "" #: howto/enum.rst:892 msgid "" -"A ``data type`` is a mixin that defines :meth:`__new__`, or a :class:" -"`~dataclasses.dataclass`" +"A ``data type`` is a mixin that defines :meth:`__new__`, or " +"a :class:`~dataclasses.dataclass`" msgstr "" #: howto/enum.rst:894 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." +"%-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 "" #: howto/enum.rst:897 msgid "" -":ref:`Formatted string literals `, :meth:`str.format`, and :func:" -"`format` will use the enum's :meth:`__str__` method." +":ref:`Formatted string literals `, :meth:`str.format`, " +"and :func:`format` will use the enum's :meth:`__str__` method." msgstr "" #: howto/enum.rst:902 msgid "" "Because :class:`IntEnum`, :class:`IntFlag`, and :class:`StrEnum` are " -"designed to be drop-in replacements for existing constants, their :meth:" -"`__str__` method has been reset to their data types' :meth:`__str__` method." +"designed to be drop-in replacements for existing constants, " +"their :meth:`__str__` method has been reset to their data " +"types' :meth:`__str__` method." msgstr "" #: howto/enum.rst:910 @@ -1375,8 +1376,9 @@ msgstr "" #: howto/enum.rst:912 msgid "" ":meth:`__new__` must be used whenever you want to customize the actual value " -"of the :class:`Enum` member. Any other modifications may go in either :meth:" -"`__new__` or :meth:`__init__`, with :meth:`__init__` being preferred." +"of the :class:`Enum` member. Any other modifications may go in " +"either :meth:`__new__` or :meth:`__init__`, with :meth:`__init__` being " +"preferred." msgstr "" #: howto/enum.rst:916 @@ -1426,8 +1428,8 @@ msgstr "" #: howto/enum.rst:953 msgid "" -":attr:`__members__` is a read-only ordered mapping of ``member_name``:" -"``member`` items. It is only available on the class." +":attr:`__members__` is a read-only ordered mapping of " +"``member_name``:``member`` items. It is only available on the class." msgstr "" #: howto/enum.rst:956 @@ -1458,9 +1460,9 @@ msgstr "" #: howto/enum.rst:969 msgid "" -"``_ignore_`` -- a list of names, either as a :class:`list` or a :class:" -"`str`, that will not be transformed into members, and will be removed from " -"the final class" +"``_ignore_`` -- a list of names, either as a :class:`list` or " +"a :class:`str`, that will not be transformed into members, and will be " +"removed from the final class" msgstr "" #: howto/enum.rst:972 @@ -1471,8 +1473,9 @@ msgstr "" #: howto/enum.rst:974 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" +"``_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 "" #: howto/enum.rst:980 @@ -1573,11 +1576,11 @@ msgstr "" #: howto/enum.rst:1050 msgid "" -"Enum classes 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::" +"Enum classes 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 "" #: howto/enum.rst:1056 @@ -1792,8 +1795,8 @@ msgstr "" #: howto/enum.rst:1178 msgid "" "The default for Flag is ``STRICT``, the default for ``IntFlag`` is " -"``EJECT``, and the default for ``_convert_`` is ``KEEP`` (see ``ssl." -"Options`` for an example of when ``KEEP`` is needed)." +"``EJECT``, and the default for ``_convert_`` is ``KEEP`` (see " +"``ssl.Options`` for an example of when ``KEEP`` is needed)." msgstr "" #: howto/enum.rst:1186 @@ -1802,8 +1805,8 @@ msgstr "" #: howto/enum.rst:1188 msgid "" -"Enums have a custom metaclass that affects many aspects of both derived :" -"class:`Enum` classes and their instances (members)." +"Enums have a custom metaclass that affects many aspects of both " +"derived :class:`Enum` classes and their instances (members)." msgstr "" #: howto/enum.rst:1193 @@ -1812,13 +1815,14 @@ msgstr "" #: howto/enum.rst:1195 msgid "" -"The :class:`EnumType` 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_enum_var in Color``. :class:" -"`EnumType` 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__`)." +"The :class:`EnumType` 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_enum_var in " +"Color``. :class:`EnumType` 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 "" #: howto/enum.rst:1204 @@ -1829,8 +1833,8 @@ msgstr "" msgid "" "Flags have an expanded view of aliasing: to be canonical, the value of a " "flag needs to be a power-of-two value, and not a duplicate name. So, in " -"addition to the :class:`Enum` definition of alias, a flag with no value (a.k." -"a. ``0``) or with more than one power-of-two value (e.g. ``3``) is " +"addition to the :class:`Enum` definition of alias, a flag with no value " +"(a.k.a. ``0``) or with more than one power-of-two value (e.g. ``3``) is " "considered an alias." msgstr "" @@ -1840,10 +1844,10 @@ msgstr "" #: howto/enum.rst:1214 msgid "" -"The most interesting thing about enum members is that they are singletons. :" -"class:`EnumType` creates them all while it is creating the 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 " +"The most interesting thing about enum members is that they are " +"singletons. :class:`EnumType` creates them all while it is creating the 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 "" @@ -1897,10 +1901,11 @@ msgstr "" #: howto/enum.rst:1249 msgid "" -"While :class:`Enum`, :class:`IntEnum`, :class:`StrEnum`, :class:`Flag`, and :" -"class:`IntFlag` 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." +"While :class:`Enum`, :class:`IntEnum`, :class:`StrEnum`, :class:`Flag`, " +"and :class:`IntFlag` 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 "" #: howto/enum.rst:1256 @@ -1978,8 +1983,8 @@ msgstr "" #: howto/enum.rst:1299 msgid "" -"This is also a good example of why you might want to write your own :meth:" -"`__repr__`::" +"This is also a good example of why you might want to write your " +"own :meth:`__repr__`::" msgstr "" #: howto/enum.rst:1302 @@ -2235,11 +2240,11 @@ msgid "" "... Period['day_%d' % i] = i\n" "...\n" ">>> list(Period)[:2]\n" -"[, ]\n" +"[, ]\n" ">>> list(Period)[-2:]\n" -"[, ]" +"[, ]" msgstr "" #: howto/enum.rst:1511 diff --git a/howto/functional.po b/howto/functional.po index 99a128153..c80f6f07d 100644 --- a/howto/functional.po +++ b/howto/functional.po @@ -40,8 +40,8 @@ msgstr "" 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 " +"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 "" @@ -357,9 +357,10 @@ msgid "" "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." +"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 "" #: howto/functional.rst:254 @@ -421,8 +422,9 @@ msgstr "" 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." +"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 "" #: howto/functional.rst:300 @@ -741,9 +743,9 @@ msgstr "" #: howto/functional.rst:537 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::" +"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 "" #: howto/functional.rst:541 @@ -771,8 +773,9 @@ msgstr "" 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``." +"``yield`` expression returns the specified value. If the " +"regular :meth:`~generator.__next__` method is called, the ``yield`` returns " +"``None``." msgstr "" #: howto/functional.rst:559 @@ -823,18 +826,18 @@ msgstr "" 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." +"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 "" #: howto/functional.rst:611 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`." +"suggest using a ``try: ... finally:`` suite instead of " +"catching :exc:`GeneratorExit`." msgstr "" #: howto/functional.rst:614 @@ -1144,10 +1147,11 @@ msgstr "" #: howto/functional.rst:827 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)." +"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 "" #: howto/functional.rst:833 @@ -1267,9 +1271,10 @@ msgstr "" 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*::" +"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 "" #: howto/functional.rst:913 @@ -1314,11 +1319,11 @@ msgstr "" #: howto/functional.rst:938 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. ::" +"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 "" #: howto/functional.rst:944 @@ -1392,8 +1397,8 @@ msgstr "" msgid "" "The :mod:`functools` module 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." +"function. The most useful tool in this module is " +"the :func:`functools.partial` function." msgstr "" #: howto/functional.rst:1002 @@ -1436,14 +1441,14 @@ 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. ::" +"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 "" #: howto/functional.rst:1037 @@ -1488,10 +1493,11 @@ msgstr "" #: howto/functional.rst:1073 msgid "" -"A related function is :func:`itertools.accumulate(iterable, func=operator." -"add) `. It performs the same calculation, but instead " -"of returning only the final result, :func:`~itertools.accumulate` returns an " -"iterator that also yields each partial result::" +"A related function is :func:`itertools.accumulate(iterable, " +"func=operator.add) `. It performs the same " +"calculation, but instead of returning only the final " +"result, :func:`~itertools.accumulate` returns an iterator that also yields " +"each partial result::" msgstr "" #: howto/functional.rst:1078 diff --git a/howto/gdb_helpers.po b/howto/gdb_helpers.po index 1c89be337..ffcc763cb 100644 --- a/howto/gdb_helpers.po +++ b/howto/gdb_helpers.po @@ -54,8 +54,8 @@ msgstr "" #: howto/gdb_helpers.rst:29 msgid "" "This document assumes that you are familiar with the basics of GDB and the " -"CPython C API. It consolidates guidance from the `devguide `_ and the `Python wiki `_ and the `Python wiki `_." msgstr "" @@ -334,8 +334,8 @@ msgstr "" #: howto/gdb_helpers.rst:202 msgid "" -"Again, the implementation details can be revealed with a cast to :c:expr:" -"`PyUnicodeObject *`::" +"Again, the implementation details can be revealed with a cast " +"to :c:expr:`PyUnicodeObject *`::" msgstr "" #: howto/gdb_helpers.rst:205 @@ -461,9 +461,9 @@ msgid "" "9 0 1 0 0 0 3 9 7 6 0 0 0 1 8 0 6 0 0 0 0 2 8 0 0 0 5 0 4 0 6 0 0 2 1 0 0 0 " "0 0 4 5', 'gsd.impossible_hints': 0, 'timer.__absolute_start_time__': , 'gsd.hints': 0, 'timer.active_time': , 'timer.total_time': }], dialog=, saved_game_model=, sudoku_maker=, 'timer.total_time': }], " +"dialog=, saved_game_model=, sudoku_maker=, 'gsd.hints': 0, 'timer.active_time': , 'timer.total_time': }], dialog=, saved_game_model=, sudoku_maker=, 'timer.total_time': }], " +"dialog=, saved_game_model=, sudoku_maker= (), throwflag=0) at Python/ceval." -"c:2665\n" +"test/regrtest.py, line 1548, in (), throwflag=0) at Python/" +"ceval.c:2665\n" "2665 x = call_function(&sp, oparg);\n" "(gdb) py-list\n" "1543 # Run the tests in a context manager that temporary changes the " diff --git a/howto/instrumentation.po b/howto/instrumentation.po index 424cd53dd..9f6bbdadc 100644 --- a/howto/instrumentation.po +++ b/howto/instrumentation.po @@ -392,8 +392,9 @@ msgstr "" #: howto/instrumentation.rst:265 msgid "" -"probe process(\"python\").library(\"libpython3.6dm.so.1.0\")." -"mark(\"function__entry\") {" +"probe " +"process(\"python\").library(\"libpython3.6dm.so.1.0\").mark(\"function__entry\") " +"{" msgstr "" #: howto/instrumentation.rst:269 @@ -514,8 +515,8 @@ msgid "" " lineno = $arg3;\n" " frameptr = $arg4\n" "}\n" -"probe python.function.return = process(\"python\")." -"mark(\"function__return\")\n" +"probe python.function.return = " +"process(\"python\").mark(\"function__return\")\n" "{\n" " filename = user_string($arg1);\n" " funcname = user_string($arg2);\n" diff --git a/howto/ipaddress.po b/howto/ipaddress.po index 20a689d22..5744f2851 100644 --- a/howto/ipaddress.po +++ b/howto/ipaddress.po @@ -129,8 +129,8 @@ msgstr "" #: 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 " +"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 " @@ -212,11 +212,11 @@ msgid "" "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." +"``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 "" #: howto/ipaddress.rst:152 @@ -232,8 +232,8 @@ msgstr "" #: 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." +"Interface) object, so you probably want to get information about " +"it. :mod:`ipaddress` tries to make doing this easy and intuitive." msgstr "" #: howto/ipaddress.rst:163 @@ -433,9 +433,9 @@ msgstr "" #: 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 " +"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 "" diff --git a/howto/isolating-extensions.po b/howto/isolating-extensions.po index dd427504a..0d95ad7d9 100644 --- a/howto/isolating-extensions.po +++ b/howto/isolating-extensions.po @@ -75,8 +75,8 @@ msgstr "" #: howto/isolating-extensions.rst:42 msgid "" -"in parallel, managing \"sub-interpreters\" using :c:func:" -"`Py_NewInterpreter`/:c:func:`Py_EndInterpreter`." +"in parallel, managing \"sub-interpreters\" " +"using :c:func:`Py_NewInterpreter`/:c:func:`Py_EndInterpreter`." msgstr "" #: howto/isolating-extensions.rst:45 @@ -306,8 +306,9 @@ msgstr "" #: howto/isolating-extensions.rst:205 msgid "" "An example of a module with per-module state is currently available as " -"`xxlimited `__; example module initialization shown at the bottom of the file." +"`xxlimited `__; example module initialization shown at the bottom of the " +"file." msgstr "" #: howto/isolating-extensions.rst:211 @@ -434,8 +435,8 @@ msgstr "" #: howto/isolating-extensions.rst:302 msgid "" -"Unlike static types, heap type objects are mutable by default. Use the :c:" -"macro:`Py_TPFLAGS_IMMUTABLETYPE` flag to prevent mutability." +"Unlike static types, heap type objects are mutable by default. Use " +"the :c:macro:`Py_TPFLAGS_IMMUTABLETYPE` flag to prevent mutability." msgstr "" #: howto/isolating-extensions.rst:304 @@ -452,8 +453,8 @@ msgstr "" #: howto/isolating-extensions.rst:312 msgid "" "Heap types can be created by filling a :c:struct:`PyType_Spec` structure, a " -"description or \"blueprint\" of a class, and calling :c:func:" -"`PyType_FromModuleAndSpec` to construct a new class object." +"description or \"blueprint\" of a class, and " +"calling :c:func:`PyType_FromModuleAndSpec` to construct a new class object." msgstr "" #: howto/isolating-extensions.rst:317 @@ -498,8 +499,8 @@ msgstr "" #: howto/isolating-extensions.rst:342 msgid "" -"Please refer to the documentation of :c:macro:`Py_TPFLAGS_HAVE_GC` and :c:" -"member:`~PyTypeObject.tp_traverse` for additional considerations." +"Please refer to the documentation of :c:macro:`Py_TPFLAGS_HAVE_GC` " +"and :c:member:`~PyTypeObject.tp_traverse` for additional considerations." msgstr "" #: howto/isolating-extensions.rst:346 @@ -543,8 +544,8 @@ msgstr "" #: howto/isolating-extensions.rst:370 msgid "" -":py:data:`sys.version_info` (via :c:func:`PySys_GetObject` and :c:func:" -"`PyArg_ParseTuple`)." +":py:data:`sys.version_info` (via :c:func:`PySys_GetObject` " +"and :c:func:`PyArg_ParseTuple`)." msgstr "" #: howto/isolating-extensions.rst:375 @@ -553,10 +554,10 @@ msgstr "" #: howto/isolating-extensions.rst:377 msgid "" -"If your traverse function delegates to the :c:member:`~PyTypeObject." -"tp_traverse` of its base class (or another type), ensure that " -"``Py_TYPE(self)`` is visited only once. Note that only heap type are " -"expected to visit the type in ``tp_traverse``." +"If your traverse function delegates to " +"the :c:member:`~PyTypeObject.tp_traverse` of its base class (or another " +"type), ensure that ``Py_TYPE(self)`` is visited only once. Note that only " +"heap type are expected to visit the type in ``tp_traverse``." msgstr "" #: howto/isolating-extensions.rst:382 @@ -584,8 +585,8 @@ msgstr "" #: howto/isolating-extensions.rst:396 msgid "" -"It is not necessary to handle the type's reference count in :c:member:" -"`~PyTypeObject.tp_new` and :c:member:`~PyTypeObject.tp_clear`." +"It is not necessary to handle the type's reference count " +"in :c:member:`~PyTypeObject.tp_new` and :c:member:`~PyTypeObject.tp_clear`." msgstr "" #: howto/isolating-extensions.rst:401 @@ -637,8 +638,8 @@ msgstr "" #: howto/isolating-extensions.rst:429 msgid "" -"The :c:member:`~PyTypeObject.tp_free` slot of a heap type must be set to :c:" -"func:`PyObject_GC_Del`. This is the default; do not override it." +"The :c:member:`~PyTypeObject.tp_free` slot of a heap type must be set " +"to :c:func:`PyObject_GC_Del`. This is the default; do not override it." msgstr "" #: howto/isolating-extensions.rst:435 @@ -671,8 +672,8 @@ msgstr "" #: howto/isolating-extensions.rst:449 msgid "" -"If the above is not possible (e.g. inside a custom ``tp_alloc``), call :c:" -"func:`PyObject_GC_New` or :c:func:`PyObject_GC_NewVar`::" +"If the above is not possible (e.g. inside a custom ``tp_alloc``), " +"call :c:func:`PyObject_GC_New` or :c:func:`PyObject_GC_NewVar`::" msgstr "" #: howto/isolating-extensions.rst:452 @@ -735,8 +736,8 @@ msgstr "" #: howto/isolating-extensions.rst:490 msgid "" -"The following Python code can illustrate the concept. ``Base." -"get_defining_class`` returns ``Base`` even if ``type(self) == Sub``:" +"The following Python code can illustrate the concept. " +"``Base.get_defining_class`` returns ``Base`` even if ``type(self) == Sub``:" msgstr "" #: howto/isolating-extensions.rst:494 @@ -754,10 +755,10 @@ msgstr "" #: howto/isolating-extensions.rst:506 msgid "" -"For a method to get its \"defining class\", it must use the :ref:" -"`METH_METHOD | METH_FASTCALL | METH_KEYWORDS ` :c:type:`calling convention ` and the " -"corresponding :c:type:`PyCMethod` signature::" +"For a method to get its \"defining class\", it must use " +"the :ref:`METH_METHOD | METH_FASTCALL | METH_KEYWORDS ` :c:type:`calling convention ` and " +"the corresponding :c:type:`PyCMethod` signature::" msgstr "" #: howto/isolating-extensions.rst:511 @@ -817,19 +818,20 @@ msgstr "" #: howto/isolating-extensions.rst:561 msgid "" -"Slot methods—the fast C equivalents for special methods, such as :c:member:" -"`~PyNumberMethods.nb_add` for :py:attr:`~object.__add__` or :c:member:" -"`~PyTypeObject.tp_new` for initialization—have a very simple API that " -"doesn't allow passing in the defining class, unlike with :c:type:" -"`PyCMethod`. The same goes for getters and setters defined with :c:type:" -"`PyGetSetDef`." +"Slot methods—the fast C equivalents for special methods, such " +"as :c:member:`~PyNumberMethods.nb_add` for :py:attr:`~object.__add__` " +"or :c:member:`~PyTypeObject.tp_new` for initialization—have a very simple " +"API that doesn't allow passing in the defining class, unlike " +"with :c:type:`PyCMethod`. The same goes for getters and setters defined " +"with :c:type:`PyGetSetDef`." msgstr "" #: howto/isolating-extensions.rst:568 msgid "" -"To access the module state in these cases, use the :c:func:" -"`PyType_GetModuleByDef` function, and pass in the module definition. Once " -"you have the module, call :c:func:`PyModule_GetState` to get the state::" +"To access the module state in these cases, use " +"the :c:func:`PyType_GetModuleByDef` function, and pass in the module " +"definition. Once you have the module, call :c:func:`PyModule_GetState` to " +"get the state::" msgstr "" #: howto/isolating-extensions.rst:573 @@ -869,11 +871,11 @@ msgstr "" #: howto/isolating-extensions.rst:599 msgid "" -"Usually this is not an issue, because types created with :c:func:" -"`PyType_FromModuleAndSpec`, and their instances, hold a reference to the " -"module. However, you must be careful in reference counting when you " -"reference module state from other places, such as callbacks for external " -"libraries." +"Usually this is not an issue, because types created " +"with :c:func:`PyType_FromModuleAndSpec`, and their instances, hold a " +"reference to the module. However, you must be careful in reference counting " +"when you reference module state from other places, such as callbacks for " +"external libraries." msgstr "" #: howto/isolating-extensions.rst:608 diff --git a/howto/logging-cookbook.po b/howto/logging-cookbook.po index 2cebdd097..72cec1da4 100644 --- a/howto/logging-cookbook.po +++ b/howto/logging-cookbook.po @@ -66,8 +66,8 @@ msgid "" "ch = logging.StreamHandler()\n" "ch.setLevel(logging.ERROR)\n" "# create formatter and add it to the handlers\n" -"formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - " -"%(message)s')\n" +"formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %" +"(message)s')\n" "fh.setFormatter(formatter)\n" "ch.setFormatter(formatter)\n" "# add the handlers to the logger\n" @@ -98,8 +98,8 @@ msgid "" "\n" "class Auxiliary:\n" " def __init__(self):\n" -" self.logger = logging.getLogger('spam_application.auxiliary." -"Auxiliary')\n" +" self.logger = " +"logging.getLogger('spam_application.auxiliary.Auxiliary')\n" " self.logger.info('creating an instance of Auxiliary')\n" "\n" " def do_something(self):\n" @@ -161,8 +161,8 @@ msgid "" " time.sleep(0.5)\n" "\n" "def main():\n" -" logging.basicConfig(level=logging.DEBUG, format='%(relativeCreated)6d " -"%(threadName)s %(message)s')\n" +" logging.basicConfig(level=logging.DEBUG, format='%(relativeCreated)6d %" +"(threadName)s %(message)s')\n" " info = {'stop': False}\n" " thread = threading.Thread(target=worker, args=(info,))\n" " thread.start()\n" @@ -239,8 +239,8 @@ msgid "" "ch = logging.StreamHandler()\n" "ch.setLevel(logging.ERROR)\n" "# create formatter and add it to the handlers\n" -"formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - " -"%(message)s')\n" +"formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %" +"(message)s')\n" "ch.setFormatter(formatter)\n" "fh.setFormatter(formatter)\n" "# add the handlers to logger\n" @@ -293,8 +293,8 @@ msgid "" "\n" "# set up logging to file - see previous section for more details\n" "logging.basicConfig(level=logging.DEBUG,\n" -" format='%(asctime)s %(name)-12s %(levelname)-8s " -"%(message)s',\n" +" format='%(asctime)s %(name)-12s %(levelname)-8s %" +"(message)s',\n" " datefmt='%m-%d %H:%M',\n" " filename='/tmp/myapp.log',\n" " filemode='w')\n" @@ -501,9 +501,9 @@ msgid "" "a function which only returns ``True`` if the level of the passed in record " "is at or below the specified level. Note that in this example I have defined " "the ``filter_maker`` in a test script ``main.py`` that I run from the " -"command line, so its module will be ``__main__`` - hence the ``__main__." -"filter_maker`` in the filter configuration. You will need to change that if " -"you define it in a different module." +"command line, so its module will be ``__main__`` - hence the " +"``__main__.filter_maker`` in the filter configuration. You will need to " +"change that if you define it in a different module." msgstr "" #: howto/logging-cookbook.rst:387 @@ -694,13 +694,13 @@ msgstr "" #: howto/logging-cookbook.rst:555 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)." +"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 "" #: howto/logging-cookbook.rst:563 @@ -720,12 +720,12 @@ msgstr "" #: howto/logging-cookbook.rst:574 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." +"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 "" #: howto/logging-cookbook.rst:582 @@ -773,10 +773,10 @@ msgid "" "Although the earlier discussion wasn't specifically talking about async " "code, but rather about slow logging handlers, it should be noted that when " "logging from async code, network and even file handlers could lead to " -"problems (blocking the event loop) because some logging is done from :mod:" -"`asyncio` internals. It might be best, if any async code is used in an " -"application, to use the above approach for logging, so that any blocking " -"code runs only in the ``QueueListener`` thread." +"problems (blocking the event loop) because some logging is done " +"from :mod:`asyncio` internals. It might be best, if any async code is used " +"in an application, to use the above approach for logging, so that any " +"blocking code runs only in the ``QueueListener`` thread." msgstr "" #: howto/logging-cookbook.rst:619 @@ -798,8 +798,8 @@ msgstr "" #: howto/logging-cookbook.rst:634 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::" +"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 "" #: howto/logging-cookbook.rst:638 @@ -832,8 +832,8 @@ msgstr "" #: howto/logging-cookbook.rst:662 msgid "" -"At the receiving end, you can set up a receiver using the :mod:" -"`socketserver` module. Here is a basic working example::" +"At the receiving end, you can set up a receiver using " +"the :mod:`socketserver` module. Here is a basic working example::" msgstr "" #: howto/logging-cookbook.rst:665 @@ -917,8 +917,8 @@ msgid "" "\n" "def main():\n" " logging.basicConfig(\n" -" format='%(relativeCreated)5d %(name)-15s %(levelname)-8s " -"%(message)s')\n" +" format='%(relativeCreated)5d %(name)-15s %(levelname)-8s %" +"(message)s')\n" " tcpserver = LogRecordSocketReceiver()\n" " print('About to start TCP server...')\n" " tcpserver.serve_until_stopped()\n" @@ -1051,8 +1051,8 @@ msgstr "" #: howto/logging-cookbook.rst:811 msgid "" -"Download `the Gist `__ as a ZIP archive using the :" -"guilabel:`Download ZIP` button." +"Download `the Gist `__ as a ZIP archive using " +"the :guilabel:`Download ZIP` button." msgstr "" #: howto/logging-cookbook.rst:814 @@ -1115,8 +1115,8 @@ msgid "" "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." +"logging an application, it could be hard to manage if the number " +"of :class:`Logger` instances becomes effectively unbounded." msgstr "" #: howto/logging-cookbook.rst:860 @@ -1127,22 +1127,22 @@ msgstr "" 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." +"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 "" #: howto/logging-cookbook.rst:870 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`::" +"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 "" #: howto/logging-cookbook.rst:878 @@ -1176,8 +1176,9 @@ msgid "" "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::" +"string, you just need to subclass :class:`LoggerAdapter` and " +"override :meth:`~LoggerAdapter.process` to do what you need. Here is a " +"simple example::" msgstr "" #: howto/logging-cookbook.rst:903 @@ -1226,23 +1227,23 @@ msgstr "" #: howto/logging-cookbook.rst:933 msgid "" -"You can also add contextual information to log output using a user-defined :" -"class:`Filter`. ``Filter`` instances are allowed to modify the " +"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`." +"can then be output using a suitable format string, or if needed a " +"custom :class:`Formatter`." msgstr "" #: howto/logging-cookbook.rst:938 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::" +"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 "" #: howto/logging-cookbook.rst:947 @@ -1399,8 +1400,8 @@ msgid "" "\n" "# A dummy set of requests which will be used in the simulation - we'll just " "pick\n" -"# from this list randomly. Note that all GET requests are from 192.168.2." -"XXX\n" +"# from this list randomly. Note that all GET requests are from " +"192.168.2.XXX\n" "# addresses, whereas POST requests are from 192.16.3.XXX addresses. Three " "users\n" "# are represented in the sample requests.\n" @@ -1418,8 +1419,8 @@ msgid "" "information\n" "# such as HTTP method, client IP and username\n" "\n" -"formatter = logging.Formatter('%(threadName)-11s %(appName)s %(name)-9s " -"%(user)-6s %(ip)s %(method)-4s %(message)s')\n" +"formatter = logging.Formatter('%(threadName)-11s %(appName)s %(name)-9s %" +"(user)-6s %(ip)s %(method)-4s %(message)s')\n" "\n" "# Create our context variables. These will be filled at the start of " "request\n" @@ -1640,21 +1641,22 @@ msgid "" "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." +"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 "" #: howto/logging-cookbook.rst:1268 msgid "" -"You could also write your own handler which uses the :class:" -"`~multiprocessing.Lock` class from the :mod:`multiprocessing` 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)." +"You could also write your own handler which uses " +"the :class:`~multiprocessing.Lock` class from the :mod:`multiprocessing` " +"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 "" #: howto/logging-cookbook.rst:1278 @@ -1705,8 +1707,8 @@ msgid "" "def listener_configurer():\n" " root = logging.getLogger()\n" " h = logging.handlers.RotatingFileHandler('mptest.log', 'a', 300, 10)\n" -" f = logging.Formatter('%(asctime)s %(processName)-10s %(name)s " -"%(levelname)-8s %(message)s')\n" +" f = logging.Formatter('%(asctime)s %(processName)-10s %(name)s %" +"(levelname)-8s %(message)s')\n" " h.setFormatter(f)\n" " root.addHandler(h)\n" "\n" @@ -1838,8 +1840,8 @@ msgid "" " 'formatters': {\n" " 'detailed': {\n" " 'class': 'logging.Formatter',\n" -" 'format': '%(asctime)s %(name)-15s %(levelname)-8s " -"%(processName)-10s %(message)s'\n" +" 'format': '%(asctime)s %(name)-15s %(levelname)-8s %" +"(processName)-10s %(message)s'\n" " }\n" " },\n" " 'handlers': {\n" @@ -2053,9 +2055,9 @@ msgstr "" 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)." +"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 "" #: howto/logging-cookbook.rst:1612 @@ -2066,9 +2068,9 @@ msgid "" "``'%'``, 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:" +"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 "" #: howto/logging-cookbook.rst:1622 @@ -2118,12 +2120,12 @@ msgid "" "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 be no changing this while preserving backward compatibility, since all " -"logging calls which are out there in existing code will be using %-format " -"strings." +"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 be no changing this while preserving backward compatibility, " +"since all logging calls which are out there in existing code will be using %-" +"format strings." msgstr "" #: howto/logging-cookbook.rst:1667 @@ -2259,10 +2261,10 @@ msgstr "" #: howto/logging-cookbook.rst:1773 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 " +"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 "" @@ -2278,21 +2280,22 @@ 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`)." +"via a :class:`~handlers.SocketHandler`, or in JSON form via " +"an :class:`~handlers.HTTPHandler`)." msgstr "" #: howto/logging-cookbook.rst:1789 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." +"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 "" #: howto/logging-cookbook.rst:1792 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." +"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 "" #: howto/logging-cookbook.rst:1795 @@ -2337,10 +2340,10 @@ msgstr "" 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." +"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 "" #: howto/logging-cookbook.rst:1825 @@ -2460,10 +2463,10 @@ msgstr "" #: howto/logging-cookbook.rst:1914 msgid "" "In a similar way to the above section, we can implement a listener and " -"handler using :pypi:`pynng`, which is a Python binding to `NNG `_, billed as a spiritual successor to ZeroMQ. The following " -"snippets illustrate -- you can test them in an environment which has " -"``pynng`` installed. Just for variety, we present the listener first." +"handler using :pypi:`pynng`, which is a Python binding to `NNG `_, billed as a spiritual successor to ZeroMQ. The " +"following snippets illustrate -- you can test them in an environment which " +"has ``pynng`` installed. Just for variety, we present the listener first." msgstr "" #: howto/logging-cookbook.rst:1924 @@ -2561,8 +2564,8 @@ msgid "" "# Make sure the process ID is in the output\n" "logging.basicConfig(level=logging.DEBUG,\n" " handlers=[logging.StreamHandler(), handler],\n" -" format='%(levelname)-8s %(name)10s %(process)6s " -"%(message)s')\n" +" format='%(levelname)-8s %(name)10s %(process)6s %" +"(message)s')\n" "levels = (logging.DEBUG, logging.INFO, logging.WARNING, logging.ERROR,\n" " logging.CRITICAL)\n" "logger_names = ('myapp', 'myapp.lib1', 'myapp.lib2')\n" @@ -2657,8 +2660,8 @@ msgstr "" 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::" +"stable/topics/logging/#configuring-logging>`_. This dictionary is passed " +"to :func:`~config.dictConfig` to put the configuration into effect::" msgstr "" #: howto/logging-cookbook.rst:2104 @@ -2955,13 +2958,13 @@ msgid "" " 'formatters': {\n" " 'detailed': {\n" " 'class': 'logging.Formatter',\n" -" 'format': '%(asctime)s %(name)-15s %(levelname)-8s " -"%(processName)-10s %(message)s'\n" +" 'format': '%(asctime)s %(name)-15s %(levelname)-8s %" +"(processName)-10s %(message)s'\n" " },\n" " 'simple': {\n" " 'class': 'logging.Formatter',\n" -" 'format': '%(name)-15s %(levelname)-8s %(processName)-10s " -"%(message)s'\n" +" 'format': '%(name)-15s %(levelname)-8s %(processName)-10s %" +"(message)s'\n" " }\n" " },\n" " 'handlers': {\n" @@ -3065,8 +3068,9 @@ msgstr "" #: howto/logging-cookbook.rst:2455 msgid "" -"Attach a :class:`~logging.Formatter` instance to your :class:`~logging." -"handlers.SysLogHandler` instance, with a format string such as::" +"Attach a :class:`~logging.Formatter` instance to " +"your :class:`~logging.handlers.SysLogHandler` instance, with a format string " +"such as::" msgstr "" #: howto/logging-cookbook.rst:2459 @@ -3226,8 +3230,9 @@ msgstr "" #: howto/logging-cookbook.rst:2578 msgid "" -"You can then specify, in a logging configuration passed to :func:" -"`dictConfig`, that a logging handler be created by calling this function::" +"You can then specify, in a logging configuration passed " +"to :func:`dictConfig`, that a logging handler be created by calling this " +"function::" msgstr "" #: howto/logging-cookbook.rst:2581 @@ -3331,11 +3336,11 @@ msgstr "" #: howto/logging-cookbook.rst:2668 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`." +"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 "" #: howto/logging-cookbook.rst:2674 @@ -3401,11 +3406,12 @@ msgid "" "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 be no " -"changing this while preserving backward compatibility, since all logging " -"calls which are out there in existing code will be using %-format strings." +"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 be no changing this while preserving backward compatibility, " +"since all logging calls which are out there in existing code will be using %-" +"format strings." msgstr "" #: howto/logging-cookbook.rst:2723 @@ -3445,8 +3451,8 @@ msgstr "" #: howto/logging-cookbook.rst:2747 msgid "" -"Refer to the reference documentation on :func:`setLogRecordFactory` and :" -"class:`LogRecord` for more information." +"Refer to the reference documentation on :func:`setLogRecordFactory` " +"and :class:`LogRecord` for more information." msgstr "" #: howto/logging-cookbook.rst:2752 @@ -3456,11 +3462,11 @@ msgstr "" #: howto/logging-cookbook.rst:2754 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::" +"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 "" #: howto/logging-cookbook.rst:2779 @@ -3476,8 +3482,8 @@ msgstr "" #: howto/logging-cookbook.rst:2787 msgid "" -"Examples of this approach are given below. Firstly, formatting with :meth:" -"`str.format`::" +"Examples of this approach are given below. Firstly, formatting " +"with :meth:`str.format`::" msgstr "" #: howto/logging-cookbook.rst:2790 @@ -3529,13 +3535,13 @@ msgid "" "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::" +"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 "" #: howto/logging-cookbook.rst:2835 @@ -3702,14 +3708,14 @@ msgid "" "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 " +"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 "" @@ -3801,9 +3807,9 @@ msgid "" "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 (number of records buffered). These default to a :class:`~logging." -"StreamHandler` which writes to ``sys.stderr``, ``logging.ERROR`` and ``100`` " -"respectively." +"the buffer (number of records buffered). These default to " +"a :class:`~logging.StreamHandler` which writes to ``sys.stderr``, " +"``logging.ERROR`` and ``100`` respectively." msgstr "" #: howto/logging-cookbook.rst:3049 @@ -3934,12 +3940,13 @@ msgstr "" #: howto/logging-cookbook.rst:3158 msgid "" "To illustrate how you can send log messages via email, so that a set number " -"of messages are sent per email, you can subclass :class:`~logging.handlers." -"BufferingHandler`. In the following example, which you can adapt to suit " -"your specific needs, a simple test harness is provided which allows you to " -"run the script with command line arguments specifying what you typically " -"need to send things via SMTP. (Run the downloaded script with the ``-h`` " -"argument to see the required and optional arguments.)" +"of messages are sent per email, you can " +"subclass :class:`~logging.handlers.BufferingHandler`. In the following " +"example, which you can adapt to suit your specific needs, a simple test " +"harness is provided which allows you to run the script with command line " +"arguments specifying what you typically need to send things via SMTP. (Run " +"the downloaded script with the ``-h`` argument to see the required and " +"optional arguments.)" msgstr "" #: howto/logging-cookbook.rst:3166 @@ -3962,8 +3969,8 @@ msgid "" " toaddrs = [toaddrs]\n" " self.toaddrs = toaddrs\n" " self.subject = subject\n" -" self.setFormatter(logging.Formatter(\"%(asctime)s %(levelname)-5s " -"%(message)s\"))\n" +" self.setFormatter(logging.Formatter(\"%(asctime)s %(levelname)-5s %" +"(message)s\"))\n" "\n" " def flush(self):\n" " if len(self.buffer) > 0:\n" @@ -4039,10 +4046,10 @@ msgstr "" #: howto/logging-cookbook.rst:3249 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::" +"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 "" #: howto/logging-cookbook.rst:3254 @@ -4272,8 +4279,8 @@ msgid "" "Suppose we have a command-line application whose job is to stop, start or " "restart some services. This could be organised for the purposes of " "illustration as a file ``app.py`` that is the main script for the " -"application, with individual commands implemented in ``start.py``, ``stop." -"py`` and ``restart.py``. Suppose further that we want to control the " +"application, with individual commands implemented in ``start.py``, " +"``stop.py`` and ``restart.py``. Suppose further that we want to control the " "verbosity of the application via a command-line argument, defaulting to " "``logging.INFO``. Here's one way that ``app.py`` could be written::" msgstr "" @@ -4313,8 +4320,8 @@ msgid "" " mod = importlib.import_module(options.command)\n" " cmd = getattr(mod, 'command')\n" " except (ImportError, AttributeError):\n" -" print('Unable to find the code for command \\'%s\\'' % options." -"command)\n" +" print('Unable to find the code for command \\'%s\\'' % " +"options.command)\n" " return 1\n" " # Could get fancy here and load configuration from file or dictionary\n" " logging.basicConfig(level=options.log_level,\n" @@ -4466,8 +4473,8 @@ msgstr "" msgid "" "A question that comes up from time to time is about how to log to a GUI " "application. The `Qt `_ framework is a popular cross-" -"platform UI framework with Python bindings using :pypi:`PySide2` or :pypi:" -"`PyQt5` libraries." +"platform UI framework with Python bindings using :pypi:`PySide2` " +"or :pypi:`PyQt5` libraries." msgstr "" #: howto/logging-cookbook.rst:3581 @@ -4678,8 +4685,8 @@ msgid "" " self.start_thread()\n" " self.work_button.clicked.connect(self.worker.start)\n" " # Once started, the button should be disabled\n" -" self.work_button.clicked.connect(lambda : self.work_button." -"setEnabled(False))\n" +" self.work_button.clicked.connect(lambda : " +"self.work_button.setEnabled(False))\n" "\n" " def start_thread(self):\n" " self.worker = Worker()\n" @@ -4756,8 +4763,9 @@ msgid "" "default to use the older :rfc:`3164`, which hails from 2001. When " "``logging`` was added to Python in 2003, it supported the earlier (and only " "existing) protocol at the time. Since RFC5424 came out, as there has not " -"been widespread deployment of it in syslog servers, the :class:`~logging." -"handlers.SysLogHandler` functionality has not been updated." +"been widespread deployment of it in syslog servers, " +"the :class:`~logging.handlers.SysLogHandler` functionality has not been " +"updated." msgstr "" #: howto/logging-cookbook.rst:3838 @@ -4787,8 +4795,8 @@ msgid "" "\n" " def format(self, record):\n" " version = 1\n" -" asctime = datetime.datetime.fromtimestamp(record.created)." -"isoformat()\n" +" asctime = " +"datetime.datetime.fromtimestamp(record.created).isoformat()\n" " m = self.tz_offset.match(time.strftime('%z'))\n" " has_offset = False\n" " if m and time.timezone:\n" @@ -4919,8 +4927,8 @@ msgstr "" #: howto/logging-cookbook.rst:3967 msgid "" -"You could also use ``LoggerWriter`` to redirect ``sys.stdout`` and ``sys." -"stderr`` by doing something like this:" +"You could also use ``LoggerWriter`` to redirect ``sys.stdout`` and " +"``sys.stderr`` by doing something like this:" msgstr "" #: howto/logging-cookbook.rst:3970 @@ -4934,9 +4942,9 @@ msgstr "" #: howto/logging-cookbook.rst:3977 msgid "" "You should do this *after* configuring logging for your needs. In the above " -"example, the :func:`~logging.basicConfig` call does this (using the ``sys." -"stderr`` value *before* it is overwritten by a ``LoggerWriter`` instance). " -"Then, you'd get this kind of result:" +"example, the :func:`~logging.basicConfig` call does this (using the " +"``sys.stderr`` value *before* it is overwritten by a ``LoggerWriter`` " +"instance). Then, you'd get this kind of result:" msgstr "" #: howto/logging-cookbook.rst:3982 @@ -4950,9 +4958,9 @@ msgstr "" #: howto/logging-cookbook.rst:3990 msgid "" -"Of course, the examples above show output according to the format used by :" -"func:`~logging.basicConfig`, but you can use a different formatter when you " -"configure logging." +"Of course, the examples above show output according to the format used " +"by :func:`~logging.basicConfig`, but you can use a different formatter when " +"you configure logging." msgstr "" #: howto/logging-cookbook.rst:3994 diff --git a/howto/logging.po b/howto/logging.po index b1deac8f3..a976b34fe 100644 --- a/howto/logging.po +++ b/howto/logging.po @@ -56,10 +56,10 @@ msgstr "" #: howto/logging.rst:28 msgid "" "You can access logging functionality by creating a logger via ``logger = " -"getLogger(__name__)``, and then calling the logger's :meth:`~Logger.debug`, :" -"meth:`~Logger.info`, :meth:`~Logger.warning`, :meth:`~Logger.error` and :" -"meth:`~Logger.critical` methods. To determine when to use logging, and to " -"see which logger methods to use when, see the table below. It states, for " +"getLogger(__name__)``, and then calling the " +"logger's :meth:`~Logger.debug`, :meth:`~Logger.info`, :meth:`~Logger.warning`, :meth:`~Logger.error` " +"and :meth:`~Logger.critical` methods. To determine when to use logging, and " +"to see which logger methods to use when, see the table below. It states, for " "each of a set of common tasks, the best tool to use for that task." msgstr "" @@ -124,8 +124,8 @@ msgstr "" #: howto/logging.rst:61 msgid "" -"A logger's :meth:`~Logger.error`, :meth:`~Logger.exception` or :meth:" -"`~Logger.critical` method as appropriate for the specific error and " +"A logger's :meth:`~Logger.error`, :meth:`~Logger.exception` " +"or :meth:`~Logger.critical` method as appropriate for the specific error and " "application domain" msgstr "" @@ -233,8 +233,8 @@ msgstr "" 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!'. The actual output can be formatted quite flexibly if you " +"the level and the description of the event provided in the logging call, " +"i.e. 'Watch out!'. The actual output can be formatted quite flexibly if you " "need that; formatting options will also be explained later." msgstr "" @@ -266,8 +266,8 @@ msgstr "" msgid "" "import logging\n" "logger = logging.getLogger(__name__)\n" -"logging.basicConfig(filename='example.log', encoding='utf-8', level=logging." -"DEBUG)\n" +"logging.basicConfig(filename='example.log', encoding='utf-8', " +"level=logging.DEBUG)\n" "logger.debug('This message should go to the log file')\n" "logger.info('So should this')\n" "logger.warning('And this, too')\n" @@ -358,8 +358,8 @@ msgstr "" #: howto/logging.rst:203 msgid "" -"logging.basicConfig(filename='example.log', filemode='w', level=logging." -"DEBUG)" +"logging.basicConfig(filename='example.log', filemode='w', " +"level=logging.DEBUG)" msgstr "" #: howto/logging.rst:205 @@ -415,8 +415,8 @@ msgstr "" #: howto/logging.rst:238 msgid "" "import logging\n" -"logging.basicConfig(format='%(levelname)s:%(message)s', level=logging." -"DEBUG)\n" +"logging.basicConfig(format='%(levelname)s:%(message)s', " +"level=logging.DEBUG)\n" "logging.debug('This message should appear on the console')\n" "logging.info('So should this')\n" "logging.warning('And this, too')" @@ -470,9 +470,9 @@ msgstr "" #: howto/logging.rst:276 msgid "" -"The default format for date/time display (shown above) is like ISO8601 or :" -"rfc:`3339`. If you need more control over the formatting of the date/time, " -"provide a *datefmt* argument to ``basicConfig``, as in this example::" +"The default format for date/time display (shown above) is like ISO8601 " +"or :rfc:`3339`. If you need more control over the formatting of the date/" +"time, provide a *datefmt* argument to ``basicConfig``, as in this example::" msgstr "" #: howto/logging.rst:280 @@ -493,8 +493,8 @@ msgstr "" #: howto/logging.rst:290 msgid "" -"The format of the *datefmt* argument is the same as supported by :func:`time." -"strftime`." +"The format of the *datefmt* argument is the same as supported " +"by :func:`time.strftime`." msgstr "" #: howto/logging.rst:295 @@ -592,10 +592,11 @@ msgstr "" #: howto/logging.rst:347 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." +"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 "" #: howto/logging.rst:353 @@ -613,12 +614,12 @@ msgstr "" 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." +"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 "" #: howto/logging.rst:368 @@ -706,22 +707,23 @@ msgstr "" #: howto/logging.rst:464 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." +":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 "" #: howto/logging.rst:474 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." +":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 "" #: howto/logging.rst:478 @@ -786,8 +788,8 @@ msgstr "" #: howto/logging.rst:521 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." +"handlers`); the tutorials use mainly :class:`StreamHandler` " +"and :class:`FileHandler` in its examples." msgstr "" #: howto/logging.rst:525 @@ -822,10 +824,10 @@ msgstr "" #: howto/logging.rst:542 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)." +"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 "" #: howto/logging.rst:549 @@ -862,8 +864,8 @@ msgstr "" #: howto/logging.rst:570 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 " +"key>)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`." @@ -917,8 +919,8 @@ msgstr "" #: howto/logging.rst:606 msgid "" -"Creating a dictionary of configuration information and passing it to the :" -"func:`dictConfig` function." +"Creating a dictionary of configuration information and passing it to " +"the :func:`dictConfig` function." msgstr "" #: howto/logging.rst:609 @@ -941,8 +943,8 @@ msgid "" "ch.setLevel(logging.DEBUG)\n" "\n" "# create formatter\n" -"formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - " -"%(message)s')\n" +"formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %" +"(message)s')\n" "\n" "# add formatter to ch\n" "ch.setFormatter(formatter)\n" @@ -1079,11 +1081,11 @@ msgstr "" 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)." +"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 "" #: howto/logging.rst:742 @@ -1148,10 +1150,10 @@ msgstr "" #: howto/logging.rst:788 msgid "" -"The event is output using a 'handler of last resort', stored in :data:" -"`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 " +"The event is output using a 'handler of last resort', stored " +"in :data:`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 " @@ -1208,13 +1210,13 @@ msgstr "" #: howto/logging.rst:832 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::" +"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 "" #: howto/logging.rst:840 @@ -1242,13 +1244,14 @@ msgstr "" #: howto/logging.rst:854 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." +"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 "" #: howto/logging.rst:865 @@ -1309,35 +1312,35 @@ msgstr "" #: howto/logging.rst:896 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." +"class. When a logger decides to actually log an event, " +"a :class:`~logging.LogRecord` instance is created from the logging message." msgstr "" #: howto/logging.rst:900 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)." +"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 "" #: howto/logging.rst:914 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`." +"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 "" #: howto/logging.rst:923 @@ -1381,8 +1384,8 @@ msgstr "" 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`." +"directly. Instead, use :class:`~handlers.RotatingFileHandler` " +"or :class:`~handlers.TimedRotatingFileHandler`." msgstr "" #: howto/logging.rst:953 @@ -1423,8 +1426,8 @@ msgstr "" #: howto/logging.rst:971 msgid "" -":class:`~handlers.NTEventLogHandler` instances send messages to a Windows " -"NT/2000/XP event log." +":class:`~handlers.NTEventLogHandler` instances send messages to a Windows NT/" +"2000/XP event log." msgstr "" #: howto/logging.rst:974 @@ -1480,27 +1483,27 @@ msgstr "" #: howto/logging.rst:1005 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." +"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 "" #: howto/logging.rst:1009 msgid "" -"For formatting multiple messages in a batch, instances of :class:" -"`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." +"For formatting multiple messages in a batch, instances " +"of :class:`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 "" #: howto/logging.rst:1014 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." +"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 "" #: howto/logging.rst:1021 @@ -1526,16 +1529,16 @@ msgstr "" 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." +"method of a :class:`Handler` subclass are passed to " +"its :meth:`~Handler.handleError` method." msgstr "" #: howto/logging.rst:1041 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." +"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 "" #: howto/logging.rst:1047 @@ -1554,12 +1557,12 @@ msgstr "" 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." +"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 "" #: howto/logging.rst:1070 @@ -1571,10 +1574,10 @@ 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::" +"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 "" #: howto/logging.rst:1080 @@ -1624,9 +1627,10 @@ msgstr "" #: howto/logging.rst:1104 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`)." +"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`)." msgstr "" #: howto/logging.rst:1110 diff --git a/howto/mro.po b/howto/mro.po index aa2ba82df..94355c929 100644 --- a/howto/mro.po +++ b/howto/mro.po @@ -445,9 +445,9 @@ msgstr "" #: howto/mro.rst:303 msgid "" -"The only difference with the previous example is the change B(D,E) --> B(E," -"D); however even such a little modification completely changes the ordering " -"of the hierarchy:" +"The only difference with the previous example is the change B(D,E) --> " +"B(E,D); however even such a little modification completely changes the " +"ordering of the hierarchy:" msgstr "" #: howto/mro.rst:307 @@ -564,8 +564,8 @@ msgstr "" #: howto/mro.rst:399 msgid "" "We see that class G inherits from F and E, with F *before* E: therefore we " -"would expect the attribute *G.remember2buy* to be inherited by *F." -"rembermer2buy* and not by *E.remember2buy*: nevertheless Python 2.2 gives" +"would expect the attribute *G.remember2buy* to be inherited by " +"*F.rembermer2buy* and not by *E.remember2buy*: nevertheless Python 2.2 gives" msgstr "" #: howto/mro.rst:407 @@ -893,8 +893,8 @@ msgstr "" #: howto/mro.rst:667 msgid "" -"The paper *A Monotonic Superclass Linearization for Dylan*: https://doi." -"org/10.1145/236337.236343" +"The paper *A Monotonic Superclass Linearization for Dylan*: https://doi.org/" +"10.1145/236337.236343" msgstr "" #: howto/mro.rst:670 diff --git a/howto/perf_profiling.po b/howto/perf_profiling.po index 14fe83bcb..c2d61a2cf 100644 --- a/howto/perf_profiling.po +++ b/howto/perf_profiling.po @@ -238,8 +238,8 @@ msgstr "" msgid "" "``perf`` profiling support can be enabled either from the start using the " "environment variable :envvar:`PYTHONPERFSUPPORT` or the :option:`-X perf <-" -"X>` option, or dynamically using :func:`sys.activate_stack_trampoline` and :" -"func:`sys.deactivate_stack_trampoline`." +"X>` option, or dynamically using :func:`sys.activate_stack_trampoline` " +"and :func:`sys.deactivate_stack_trampoline`." msgstr "" #: howto/perf_profiling.rst:160 diff --git a/howto/pyporting.po b/howto/pyporting.po index 0a2402ea6..0f65d2623 100644 --- a/howto/pyporting.po +++ b/howto/pyporting.po @@ -50,8 +50,8 @@ msgstr "" #: howto/pyporting.rst:21 msgid "" "Since Python 3.11 the original porting guide was discontinued. You can find " -"the old guide in the `archive `_." +"the old guide in the `archive `_." msgstr "" #: howto/pyporting.rst:27 diff --git a/howto/regex.po b/howto/regex.po index 2bcdea3bd..aafd89aff 100644 --- a/howto/regex.po +++ b/howto/regex.po @@ -110,12 +110,12 @@ msgstr "" #: 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." +"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 "" #: howto/regex.rst:76 @@ -150,12 +150,12 @@ msgstr "" #: 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. For example, ``[^5]`` will match any character " -"except ``'5'``. If the caret appears elsewhere in a character class, it " -"does not have special meaning. For example: ``[5^]`` will match either a " -"``'5'`` or a ``'^'``." +"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. For example, ``[^5]`` will match any " +"character except ``'5'``. If the caret appears elsewhere in a character " +"class, it does not have special meaning. For example: ``[5^]`` will match " +"either a ``'5'`` or a ``'^'``." msgstr "" #: howto/regex.rst:103 @@ -180,10 +180,10 @@ 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." +"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 "" #: howto/regex.rst:123 @@ -262,9 +262,9 @@ msgstr "" #: howto/regex.rst:156 msgid "" "The final metacharacter in this section is ``.``. It matches anything " -"except a newline character, and there's an alternate mode (:const:`re." -"DOTALL`) where it will match even a newline. ``.`` is often used where you " -"want to match \"any character\"." +"except a newline character, and there's an alternate mode " +"(:const:`re.DOTALL`) where it will match even a newline. ``.`` is often " +"used where you want to match \"any character\"." msgstr "" #: howto/regex.rst:163 @@ -510,8 +510,8 @@ msgid "" "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." +"simply a C extension module included with Python, just like " +"the :mod:`socket` or :mod:`zlib` modules." msgstr "" #: howto/regex.rst:292 @@ -598,10 +598,10 @@ msgstr "" #: howto/regex.rst:336 msgid "" "In addition, special escape sequences that are valid in regular expressions, " -"but not valid as Python string literals, now result in a :exc:" -"`DeprecationWarning` and will eventually become a :exc:`SyntaxError`, which " -"means the sequences will be invalid if raw string notation or escaping the " -"backslashes isn't used." +"but not valid as Python string literals, now result in " +"a :exc:`DeprecationWarning` and will eventually become a :exc:`SyntaxError`, " +"which means the sequences will be invalid if raw string notation or escaping " +"the backslashes isn't used." msgstr "" #: howto/regex.rst:344 @@ -682,8 +682,8 @@ msgstr "" #: howto/regex.rst:374 msgid "" -"Find all substrings where the RE matches, and returns them as an :term:" -"`iterator`." +"Find all substrings where the RE matches, and returns them as " +"an :term:`iterator`." msgstr "" #: howto/regex.rst:378 @@ -799,11 +799,11 @@ msgstr "" #: howto/regex.rst:438 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:`~re.Pattern.match` method only " -"checks if the RE matches at the start of a string, :meth:`!start` will " +":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:`~re.Pattern.match` method " +"only checks if the RE matches at the start of a string, :meth:`!start` will " "always be zero. However, the :meth:`~re.Pattern.search` method of patterns " "scans through the string, so the match may not start at zero in that " "case. ::" @@ -840,8 +840,8 @@ msgstr "" #: howto/regex.rst:466 msgid "" -"Two pattern methods return all of the matches for a pattern. :meth:`~re." -"Pattern.findall` returns a list of matching strings::" +"Two pattern methods return all of the matches for a " +"pattern. :meth:`~re.Pattern.findall` returns a list of matching strings::" msgstr "" #: howto/regex.rst:469 @@ -856,16 +856,16 @@ msgid "" "The ``r`` prefix, making the literal a raw string literal, is needed in this " "example because escape sequences in a normal \"cooked\" string literal that " "are not recognized by Python, as opposed to regular expressions, now result " -"in a :exc:`DeprecationWarning` and will eventually become a :exc:" -"`SyntaxError`. See :ref:`the-backslash-plague`." +"in a :exc:`DeprecationWarning` and will eventually become " +"a :exc:`SyntaxError`. See :ref:`the-backslash-plague`." msgstr "" #: howto/regex.rst:479 msgid "" ":meth:`~re.Pattern.findall` has to create the entire list before it can be " "returned as the result. The :meth:`~re.Pattern.finditer` method returns a " -"sequence of :ref:`match object ` instances as an :term:" -"`iterator`::" +"sequence of :ref:`match object ` instances as " +"an :term:`iterator`::" msgstr "" #: howto/regex.rst:483 @@ -887,12 +887,12 @@ msgstr "" #: howto/regex.rst:497 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. ::" +"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 "" #: howto/regex.rst:504 @@ -927,12 +927,12 @@ msgstr "" 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." +"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 "" #: howto/regex.rst:534 @@ -1007,13 +1007,13 @@ msgid "" "letters, too. Full Unicode matching also works unless the :const:`ASCII` " "flag is used to disable non-ASCII matches. When the Unicode patterns ``[a-" "z]`` or ``[A-Z]`` are used in combination with the :const:`IGNORECASE` flag, " -"they will match the 52 ASCII letters and 4 additional non-ASCII letters: " -"'İ' (U+0130, Latin capital letter I with dot above), 'ı' (U+0131, Latin " -"small letter dotless i), 'ſ' (U+017F, Latin small letter long s) and " -"'K' (U+212A, Kelvin sign). ``Spam`` will match ``'Spam'``, ``'spam'``, " -"``'spAM'``, or ``'ſpam'`` (the latter is matched only in Unicode mode). This " -"lowercasing doesn't take the current locale into account; it will if you " -"also set the :const:`LOCALE` flag." +"they will match the 52 ASCII letters and 4 additional non-ASCII letters: 'İ' " +"(U+0130, Latin capital letter I with dot above), 'ı' (U+0131, Latin small " +"letter dotless i), 'ſ' (U+017F, Latin small letter long s) and 'K' (U+212A, " +"Kelvin sign). ``Spam`` will match ``'Spam'``, ``'spam'``, ``'spAM'``, or " +"``'ſpam'`` (the latter is matched only in Unicode mode). This lowercasing " +"doesn't take the current locale into account; it will if you also set " +"the :const:`LOCALE` flag." msgstr "" #: howto/regex.rst:581 @@ -1180,9 +1180,9 @@ msgstr "" #: howto/regex.rst:707 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." +"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 "" #: howto/regex.rst:711 @@ -1365,12 +1365,12 @@ msgstr "" 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:`~re.Match.group`, :meth:`~re.Match.start`, :meth:`~re." -"Match.end`, and :meth:`~re.Match.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. ::" +"argument " +"to :meth:`~re.Match.group`, :meth:`~re.Match.start`, :meth:`~re.Match.end`, " +"and :meth:`~re.Match.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 "" #: howto/regex.rst:824 @@ -1566,8 +1566,8 @@ msgstr "" #: howto/regex.rst:946 msgid "" -"Additionally, you can retrieve named groups as a dictionary with :meth:`~re." -"Match.groupdict`::" +"Additionally, you can retrieve named groups as a dictionary " +"with :meth:`~re.Match.groupdict`::" msgstr "" #: howto/regex.rst:949 @@ -1580,8 +1580,8 @@ msgstr "" #: howto/regex.rst:953 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::" +"instead of having to remember numbers. Here's an example RE from " +"the :mod:`imaplib` module::" msgstr "" #: howto/regex.rst:957 @@ -1607,8 +1607,8 @@ msgid "" "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\\b`` can also be written as ``\\b(?" -"P\\w+)\\s+(?P=word)\\b``::" +"words, ``\\b(\\w+)\\s+\\1\\b`` can also be written as ``\\b(?P\\w+)\\s+" +"(?P=word)\\b``::" msgstr "" #: howto/regex.rst:974 @@ -1701,10 +1701,10 @@ 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." +"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 "" #: howto/regex.rst:1030 @@ -2037,13 +2037,13 @@ msgstr "" #: howto/regex.rst:1243 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:`~re.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." +"fixed string, or a single character class, and you're not using " +"any :mod:`re` features such as the :const:`~re.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 "" #: howto/regex.rst:1251 @@ -2055,8 +2055,8 @@ msgid "" "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.)" +"``word`` have a word boundary on either side. This takes the job " +"beyond :meth:`!replace`'s abilities.)" msgstr "" #: howto/regex.rst:1260 @@ -2112,14 +2112,15 @@ msgstr "" #: howto/regex.rst:1292 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." +"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 "" #: howto/regex.rst:1301 diff --git a/howto/sockets.po b/howto/sockets.po index b89f53e44..0bdc03580 100644 --- a/howto/sockets.po +++ b/howto/sockets.po @@ -134,11 +134,11 @@ msgstr "" #: 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." +"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 "" #: howto/sockets.rst:87 diff --git a/howto/sorting.po b/howto/sorting.po index 4080ffda4..82462e043 100644 --- a/howto/sorting.po +++ b/howto/sorting.po @@ -73,9 +73,9 @@ msgid "" "more efficient." msgstr "" "Ayrıca :meth:`list.sort` yöntemini de kullanabilirsiniz. Listeyi yerinde " -"modifiye eder (ve karışıklığı önlemek için ``None`` döndürür). Genellikle :" -"func:`sorted` yönteminden daha az kullanışlıdır - ancak orijinal listeye " -"ihtiyacınız yoksa, biraz daha verimlidir." +"modifiye eder (ve karışıklığı önlemek için ``None`` döndürür). " +"Genellikle :func:`sorted` yönteminden daha az kullanışlıdır - ancak orijinal " +"listeye ihtiyacınız yoksa, biraz daha verimlidir." #: howto/sorting.rst:32 msgid "" @@ -187,8 +187,8 @@ msgstr "" #: howto/sorting.rst:99 msgid "" "Objects with named attributes can be made by a regular class as shown above, " -"or they can be instances of :class:`~dataclasses.dataclass` or a :term:" -"`named tuple`." +"or they can be instances of :class:`~dataclasses.dataclass` or " +"a :term:`named tuple`." msgstr "" #: howto/sorting.rst:104 @@ -201,14 +201,15 @@ msgstr "Operatör Modülü İşlevleri" msgid "" "The :term:`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." +"The :mod:`operator` module " +"has :func:`~operator.itemgetter`, :func:`~operator.attrgetter`, and " +"a :func:`~operator.methodcaller` function." msgstr "" "Yukarıda gösterilen anahtar-fonksiyon kalıpları çok yaygındır. Bu nedenle " "Python, erişim fonksiyonlarını daha kolay ve hızlı hale getirmek için bazı " -"kolaylık fonksiyonları sağlar. :mod:`operator` modülü :func:`~operator." -"itemgetter`, :func:`~operator.attrgetter` ve bir :func:`~operator." -"methodcaller` fonksiyonuna sahiptir." +"kolaylık fonksiyonları sağlar. :mod:`operator` " +"modülü :func:`~operator.itemgetter`, :func:`~operator.attrgetter` ve " +"bir :func:`~operator.methodcaller` fonksiyonuna sahiptir." #: howto/sorting.rst:111 msgid "Using those functions, the above examples become simpler and faster:" @@ -453,13 +454,13 @@ msgstr "" #: howto/sorting.rst:246 msgid "" -"Another name for this idiom is `Schwartzian transform `_\\, after Randal L. Schwartz, who " -"popularized it among Perl programmers." +"Another name for this idiom is `Schwartzian transform `_\\, after Randal L. Schwartz, " +"who popularized it among Perl programmers." msgstr "" "Bu deyimin bir diğer adı da, deyimi Perl programcıları arasında popüler hale " -"getiren Randal L. Schwartz'a atfen `Schwartzian transform `_\\'dur." +"getiren Randal L. Schwartz'a atfen `Schwartzian transform `_\\'dur." #: howto/sorting.rst:250 msgid "" @@ -489,11 +490,11 @@ msgid "" "function such as ``cmp(a, b)`` will return a negative value for less-than, " "zero if the inputs are equal, or a positive value for greater-than." msgstr "" -"Örneğin, bir `balance scale `_ iki örneği karşılaştırarak göreceli " -"bir sıralama verir: daha hafif, eşit veya daha ağır. Benzer şekilde, " -"``cmp(a, b)`` karşılaştırma fonksiyonu; girdiler eşitse sıfır, küçükse " -"negatif, büyükse pozitif bir değer döndürür." +"Örneğin, bir `balance scale `_ iki örneği karşılaştırarak göreceli bir " +"sıralama verir: daha hafif, eşit veya daha ağır. Benzer şekilde, ``cmp(a, " +"b)`` karşılaştırma fonksiyonu; girdiler eşitse sıfır, küçükse negatif, " +"büyükse pozitif bir değer döndürür." #: howto/sorting.rst:265 msgid "" @@ -509,13 +510,13 @@ msgstr "" #: howto/sorting.rst:269 msgid "" -"To accommodate those situations, Python provides :class:`functools." -"cmp_to_key` to wrap the comparison function to make it usable as a key " -"function::" +"To accommodate those situations, Python " +"provides :class:`functools.cmp_to_key` to wrap the comparison function to " +"make it usable as a key function::" msgstr "" "Bu durumlara uyum sağlamak için Python, karşılaştırma fonksiyonunu bir " -"anahtar fonksiyon olarak kullanılabilir hale getirmek için :class:`functools." -"cmp_to_key` aracını sağlar::" +"anahtar fonksiyon olarak kullanılabilir hale getirmek " +"için :class:`functools.cmp_to_key` aracını sağlar::" #: howto/sorting.rst:273 msgid "sorted(words, key=cmp_to_key(strcoll)) # locale-aware sort order" @@ -527,15 +528,16 @@ msgstr "Tuhaflıklar ve Sonlar" #: howto/sorting.rst:278 msgid "" -"For locale aware sorting, use :func:`locale.strxfrm` for a key function or :" -"func:`locale.strcoll` for a comparison function. This is necessary because " -"\"alphabetical\" sort orderings can vary across cultures even if the " +"For locale aware sorting, use :func:`locale.strxfrm` for a key function " +"or :func:`locale.strcoll` for a comparison function. This is necessary " +"because \"alphabetical\" sort orderings can vary across cultures even if the " "underlying alphabet is the same." msgstr "" -"Yerel ayarlara duyarlı sıralama yapmak istiyorsanız, anahtar işlevleri için :" -"func:`locale.strxfrm` ve karşılaştırma işlevleri için :func:`locale.strcoll` " -"kullanabilirsiniz. Bu gereklidir çünkü \"alfabetik\" sıralamalar, temel " -"alfabe aynı olsa bile kültürler arasında farklılık gösterebilir." +"Yerel ayarlara duyarlı sıralama yapmak istiyorsanız, anahtar işlevleri " +"için :func:`locale.strxfrm` ve karşılaştırma işlevleri " +"için :func:`locale.strcoll` kullanabilirsiniz. Bu gereklidir çünkü " +"\"alfabetik\" sıralamalar, temel alfabe aynı olsa bile kültürler arasında " +"farklılık gösterebilir." #: howto/sorting.rst:283 msgid "" @@ -564,8 +566,8 @@ msgstr "" #, fuzzy msgid "" "The sort routines use ``<`` when making comparisons between two objects. So, " -"it is easy to add a standard sort order to a class by defining an :meth:" -"`~object.__lt__` method:" +"it is easy to add a standard sort order to a class by defining " +"an :meth:`~object.__lt__` method:" msgstr "" "Sıralama rutinleri, iki nesne arasında karşılaştırma yaparken ``<`` " "kullanır. Bu nedenle, bir :meth:`__lt__` yöntemi tanımlayarak, bir sınıfa " @@ -580,8 +582,8 @@ msgstr "" #: howto/sorting.rst:307 msgid "" -"However, note that ``<`` can fall back to using :meth:`~object.__gt__` if :" -"meth:`~object.__lt__` is not implemented (see :func:`object.__lt__` for " +"However, note that ``<`` can fall back to using :meth:`~object.__gt__` " +"if :meth:`~object.__lt__` is not implemented (see :func:`object.__lt__` for " "details on the mechanics). To avoid surprises, :pep:`8` recommends that all " "six comparison methods be implemented. The :func:`~functools.total_ordering` " "decorator is provided to make that task easier." diff --git a/howto/unicode.po b/howto/unicode.po index e1e7cd0d0..5b274862e 100644 --- a/howto/unicode.po +++ b/howto/unicode.po @@ -77,10 +77,10 @@ msgstr "" msgid "" "The Unicode standard describes how characters are represented by **code " "points**. A code point value is an integer in the range 0 to 0x10FFFF " -"(about 1.1 million values, the `actual number assigned `_ is less than that). In the standard and in " -"this document, a code point is written using the notation ``U+265E`` to mean " -"the character with value ``0x265e`` (9,822 in decimal)." +"(about 1.1 million values, the `actual number assigned `_ is less than that). In the " +"standard and in this document, a code point is written using the notation " +"``U+265E`` to mean the character with value ``0x265e`` (9,822 in decimal)." msgstr "" #: howto/unicode.rst:50 @@ -280,8 +280,8 @@ msgstr "" #: howto/unicode.rst:173 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." @@ -434,10 +434,10 @@ msgstr "" #: howto/unicode.rst:272 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 " +"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)." @@ -606,9 +606,9 @@ msgid "" "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." +"Values section of the Unicode Character Database documentation `_ for a list of " +"category codes." msgstr "" #: howto/unicode.rst:402 @@ -643,12 +643,12 @@ msgstr "" #: howto/unicode.rst:425 msgid "" -"A second tool is the :mod:`unicodedata` module's :func:`~unicodedata." -"normalize` function that converts strings to one of several normal forms, " -"where letters followed by a combining character are replaced with single " -"characters. :func:`~unicodedata.normalize` can be used to perform string " -"comparisons that won't falsely report inequality if two strings use " -"combining characters differently:" +"A second tool is the :mod:`unicodedata` " +"module's :func:`~unicodedata.normalize` function that converts strings to " +"one of several normal forms, where letters followed by a combining character " +"are replaced with single characters. :func:`~unicodedata.normalize` can be " +"used to perform string comparisons that won't falsely report inequality if " +"two strings use combining characters differently:" msgstr "" #: howto/unicode.rst:434 @@ -768,8 +768,9 @@ msgstr "" #: howto/unicode.rst:520 msgid "" -"`Processing Text Files in Python 3 `_, by Nick Coghlan." +"`Processing Text Files in Python 3 `_, " +"by Nick Coghlan." msgstr "" #: howto/unicode.rst:521 @@ -780,8 +781,8 @@ msgstr "" #: howto/unicode.rst:523 msgid "" -"The :class:`str` type is described in the Python library reference at :ref:" -"`textseq`." +"The :class:`str` type is described in the Python library reference " +"at :ref:`textseq`." msgstr "" #: howto/unicode.rst:526 @@ -852,8 +853,8 @@ msgid "" "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`." +"*encoding* and *errors* parameters which are interpreted just like those " +"in :meth:`str.encode` and :meth:`bytes.decode`." msgstr "" #: howto/unicode.rst:574 @@ -1094,8 +1095,8 @@ msgstr "" #: howto/unicode.rst:737 msgid "" -"One section of `Mastering Python 3 Input/Output `_, a PyCon 2010 talk by David " +"One section of `Mastering Python 3 Input/Output `_, a PyCon 2010 talk by David " "Beazley, discusses text processing and binary data handling." msgstr "" diff --git a/howto/urllib2.po b/howto/urllib2.po index 3dd95b5c0..0cd8a540b 100644 --- a/howto/urllib2.po +++ b/howto/urllib2.po @@ -40,8 +40,8 @@ msgstr "" #: howto/urllib2.rst:18 msgid "" -"`Basic Authentication `_" +"`Basic Authentication `_" msgstr "" #: howto/urllib2.rst:20 @@ -97,8 +97,8 @@ msgstr "" #: howto/urllib2.rst:52 msgid "" "If you wish to retrieve a resource via URL and store it in a temporary " -"location, you can do so via the :func:`shutil.copyfileobj` and :func:" -"`tempfile.NamedTemporaryFile` functions::" +"location, you can do so via the :func:`shutil.copyfileobj` " +"and :func:`tempfile.NamedTemporaryFile` functions::" msgstr "" #: howto/urllib2.rst:56 @@ -298,14 +298,14 @@ msgstr "" #: howto/urllib2.rst:197 msgid "" "*urlopen* raises :exc:`~urllib.error.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)." +"response (though as usual with Python APIs, built-in exceptions such " +"as :exc:`ValueError`, :exc:`TypeError` etc. may also be raised)." msgstr "" #: howto/urllib2.rst:201 msgid "" -":exc:`~urllib.error.HTTPError` is the subclass of :exc:`~urllib.error." -"URLError` raised in the specific case of HTTP URLs." +":exc:`~urllib.error.HTTPError` is the subclass " +"of :exc:`~urllib.error.URLError` raised in the specific case of HTTP URLs." msgstr "" #: howto/urllib2.rst:204 @@ -349,9 +349,9 @@ msgid "" "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:`~urllib.error." -"HTTPError`. Typical errors include '404' (page not found), '403' (request " -"forbidden), and '401' (authentication required)." +"For those it can't handle, urlopen will raise " +"an :exc:`~urllib.error.HTTPError`. Typical errors include '404' (page not " +"found), '403' (request forbidden), and '401' (authentication required)." msgstr "" #: howto/urllib2.rst:235 @@ -474,8 +474,8 @@ msgid "" "...\n" "404\n" "b'\\n\\n\\n\\n\\n\\nPage Not Found\\n\n" " ..." @@ -487,9 +487,9 @@ msgstr "" #: howto/urllib2.rst:341 msgid "" -"So if you want to be prepared for :exc:`~urllib.error.HTTPError` *or* :exc:" -"`~urllib.error.URLError` there are two basic approaches. I prefer the second " -"approach." +"So if you want to be prepared for :exc:`~urllib.error.HTTPError` " +"*or* :exc:`~urllib.error.URLError` there are two basic approaches. I prefer " +"the second approach." msgstr "" #: howto/urllib2.rst:345 @@ -563,8 +563,8 @@ msgstr "" #: howto/urllib2.rst:402 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." +"fetched, particularly the headers sent by the server. It is currently " +"an :class:`http.client.HTTPMessage` instance." msgstr "" #: howto/urllib2.rst:406 @@ -599,8 +599,8 @@ msgstr "" #: howto/urllib2.rst:427 msgid "" -"To create an opener, instantiate an ``OpenerDirector``, and then call ``." -"add_handler(some_handler_instance)`` repeatedly." +"To create an opener, instantiate an ``OpenerDirector``, and then call " +"``.add_handler(some_handler_instance)`` repeatedly." msgstr "" #: howto/urllib2.rst:430 @@ -755,8 +755,8 @@ msgstr "" #: howto/urllib2.rst:540 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 [#]_." +"locations through a proxy. However, this can be enabled by extending " +"urllib.request as shown in the recipe [#]_." msgstr "" #: howto/urllib2.rst:546 @@ -780,9 +780,9 @@ 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 ::" +"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 "" #: howto/urllib2.rst:562 diff --git a/installing/index.po b/installing/index.po index 9df8df848..297b5002e 100644 --- a/installing/index.po +++ b/installing/index.po @@ -435,9 +435,9 @@ msgstr "" #: installing/index.rst:217 msgid "" -"There are also additional resources for `installing pip. `__" +"There are also additional resources for `installing pip. `__" msgstr "" "`pip'i yüklemek `__ için " @@ -473,10 +473,10 @@ msgstr "" #: installing/index.rst:234 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." +"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 "" "`Bilimsel yazılımı `__ yüklemek için " "önceden oluşturulmuş (pre-built) ``wheel`` dosyaları olarak henüz mevcut " @@ -485,8 +485,8 @@ msgstr "" #: installing/index.rst:241 msgid "" -"`Python Packaging User Guide: Binary Extensions `__" +"`Python Packaging User Guide: Binary Extensions `__" msgstr "" -"`Python Paketleme Kullanıcı Kılavuzu: İkili Uzantılar `__" +"`Python Paketleme Kullanıcı Kılavuzu: İkili Uzantılar `__" diff --git a/library/2to3.po b/library/2to3.po index ad70effa5..0a80e565a 100644 --- a/library/2to3.po +++ b/library/2to3.po @@ -107,11 +107,11 @@ msgstr "" #: library/2to3.rst:64 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:" +"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 "" #: library/2to3.rst:69 @@ -168,19 +168,19 @@ 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. Also :option:`!-e` can be used to make :" -"func:`exec` a 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. Also :option:`!-e` " +"can be used to make :func:`exec` a function." msgstr "" #: library/2to3.rst:110 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." +"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 "" #: library/2to3.rst:115 @@ -346,13 +346,14 @@ msgstr "" #: library/2to3.rst:207 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`." +"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 "" #: library/2to3.rst:217 @@ -402,8 +403,8 @@ 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 ::" +"``while 1`` becomes ``while True``. This fixer also tries to make use " +"of :func:`sorted` in appropriate places. For example, this block ::" msgstr "" #: library/2to3.rst:262 @@ -452,16 +453,17 @@ msgstr "" #: library/2to3.rst:299 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`." +"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 "" #: library/2to3.rst:305 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`." +"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 "" #: library/2to3.rst:311 @@ -493,15 +495,15 @@ msgstr "" #: library/2to3.rst:335 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__`." +"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 "" #: library/2to3.rst:341 msgid "" -"Renames definitions of methods called :meth:`__nonzero__` to :meth:`~object." -"__bool__`." +"Renames definitions of methods called :meth:`__nonzero__` " +"to :meth:`~object.__bool__`." msgstr "" #: library/2to3.rst:346 @@ -621,8 +623,9 @@ msgstr "" #: library/2to3.rst:413 msgid "" -"Changes the deprecated :data:`sys.exc_value`, :data:`sys.exc_type`, :data:" -"`sys.exc_traceback` to use :func:`sys.exc_info`." +"Changes the " +"deprecated :data:`sys.exc_value`, :data:`sys.exc_type`, :data:`sys.exc_traceback` " +"to use :func:`sys.exc_info`." msgstr "" #: library/2to3.rst:418 @@ -686,11 +689,11 @@ msgid "" "Python 3.9 switched to a PEG parser (see :pep:`617`) while lib2to3 is using " "a less flexible LL(1) parser. Python 3.10 includes new language syntax that " "is not parsable by lib2to3's LL(1) parser (see :pep:`634`). The ``lib2to3`` " -"module was marked pending for deprecation in Python 3.9 (raising :exc:" -"`PendingDeprecationWarning` on import) and fully deprecated in Python 3.11 " -"(raising :exc:`DeprecationWarning`). It will be removed from the standard " -"library in Python 3.13. Consider third-party alternatives such as `LibCST`_ " -"or `parso`_." +"module was marked pending for deprecation in Python 3.9 " +"(raising :exc:`PendingDeprecationWarning` on import) and fully deprecated in " +"Python 3.11 (raising :exc:`DeprecationWarning`). It will be removed from the " +"standard library in Python 3.13. Consider third-party alternatives such as " +"`LibCST`_ or `parso`_." msgstr "" #: library/2to3.rst:485 diff --git a/library/__future__.po b/library/__future__.po index 424a4b877..6e126e554 100644 --- a/library/__future__.po +++ b/library/__future__.po @@ -26,10 +26,11 @@ msgstr "" #: library/__future__.rst:11 msgid "" -"Imports of the form ``from __future__ import feature`` are called :ref:" -"`future statements `. These are special-cased by the Python compiler " -"to allow the use of new Python features in modules containing the future " -"statement before the release in which the feature becomes standard." +"Imports of the form ``from __future__ import feature`` are " +"called :ref:`future statements `. These are special-cased by the " +"Python compiler to allow the use of new Python features in modules " +"containing the future statement before the release in which the feature " +"becomes standard." msgstr "" #: library/__future__.rst:16 @@ -57,9 +58,9 @@ msgstr "" #: library/__future__.rst:29 msgid "" "To ensure that :ref:`future statements ` run under releases prior to " -"Python 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)." +"Python 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 "" #: library/__future__.rst:34 @@ -271,8 +272,8 @@ msgstr "" 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:`_Feature." -"compiler_flag` attribute on :class:`_Feature` instances." +"dynamically compiled code. This flag is stored in " +"the :attr:`_Feature.compiler_flag` attribute on :class:`_Feature` instances." msgstr "" #: library/__future__.rst:117 diff --git a/library/__main__.po b/library/__main__.po index cb28b7b93..d9cbfb71b 100644 --- a/library/__main__.po +++ b/library/__main__.po @@ -40,8 +40,8 @@ msgstr "" msgid "" "Both of these mechanisms are related to Python modules; how users interact " "with them and how they interact with each other. They are explained in " -"detail below. If you're new to Python modules, see the tutorial section :" -"ref:`tut-modules` for an introduction." +"detail below. If you're new to Python modules, see the tutorial " +"section :ref:`tut-modules` for an introduction." msgstr "" #: library/__main__.rst:25 @@ -120,8 +120,8 @@ msgstr "" #: library/__main__.rst:67 msgid "" -"the Python module or package passed to the Python interpreter with the :" -"option:`-m` argument:" +"the Python module or package passed to the Python interpreter with " +"the :option:`-m` argument:" msgstr "" #: library/__main__.rst:70 @@ -272,9 +272,9 @@ msgstr "" #: library/__main__.rst:175 msgid "" "Since the call to ``main`` is wrapped in :func:`sys.exit`, the expectation " -"is that your function will return some value acceptable as an input to :func:" -"`sys.exit`; typically, an integer or ``None`` (which is implicitly returned " -"if your function does not have a return statement)." +"is that your function will return some value acceptable as an input " +"to :func:`sys.exit`; typically, an integer or ``None`` (which is implicitly " +"returned if your function does not have a return statement)." msgstr "" #: library/__main__.rst:180 @@ -290,8 +290,8 @@ msgid "" "In particular, be careful about returning strings from your ``main`` " "function. :func:`sys.exit` will interpret a string argument as a failure " "message, so your program will have an exit code of ``1``, indicating " -"failure, and the string will be written to :data:`sys.stderr`. The ``echo." -"py`` example from earlier exemplifies using the ``sys.exit(main())`` " +"failure, and the string will be written to :data:`sys.stderr`. The " +"``echo.py`` example from earlier exemplifies using the ``sys.exit(main())`` " "convention." msgstr "" @@ -383,8 +383,8 @@ msgstr "" #: library/__main__.rst:254 msgid "" -"This won't work for ``__main__.py`` files in the root directory of a ``." -"zip`` file though. Hence, for consistency, a minimal ``__main__.py`` " +"This won't work for ``__main__.py`` files in the root directory of a " +"``.zip`` file though. Hence, for consistency, a minimal ``__main__.py`` " "without a ``__name__`` check is preferred." msgstr "" @@ -542,6 +542,6 @@ msgstr "" #: library/__main__.rst:367 msgid "" -"The ``__main__`` scope is used in the implementation of :mod:`pdb` and :mod:" -"`rlcompleter`." +"The ``__main__`` scope is used in the implementation of :mod:`pdb` " +"and :mod:`rlcompleter`." msgstr "" diff --git a/library/_thread.po b/library/_thread.po index e4b2dce69..7075776d1 100644 --- a/library/_thread.po +++ b/library/_thread.po @@ -63,10 +63,11 @@ msgstr "" #: library/_thread.rst:52 msgid "" -"When the function terminates with an unhandled exception, :func:`sys." -"unraisablehook` is called to handle the exception. The *object* attribute of " -"the hook argument is *function*. By default, a stack trace is printed and " -"then the thread exits (but other threads continue to run)." +"When the function terminates with an unhandled " +"exception, :func:`sys.unraisablehook` is called to handle the exception. The " +"*object* attribute of the hook argument is *function*. By default, a stack " +"trace is printed and then the thread exits (but other threads continue to " +"run)." msgstr "" #: library/_thread.rst:57 @@ -100,8 +101,9 @@ msgstr "" #: library/_thread.rst:75 msgid "" -"If the given signal isn't handled by Python (it was set to :const:`signal." -"SIG_DFL` or :const:`signal.SIG_IGN`), this function does nothing." +"If the given signal isn't handled by Python (it was set " +"to :const:`signal.SIG_DFL` or :const:`signal.SIG_IGN`), this function does " +"nothing." msgstr "" #: library/_thread.rst:79 @@ -154,9 +156,9 @@ msgid "" "*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 " +"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 " @@ -234,8 +236,8 @@ msgstr "" #: library/_thread.rst:199 msgid "" -"In addition to these methods, lock objects can also be used via the :keyword:" -"`with` statement, e.g.::" +"In addition to these methods, lock objects can also be used via " +"the :keyword:`with` statement, e.g.::" msgstr "" #: library/_thread.rst:202 @@ -276,8 +278,9 @@ msgstr "" #: library/_thread.rst:225 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." +"survive. On most systems, they are killed without " +"executing :keyword:`try` ... :keyword:`finally` clauses or executing object " +"destructors." msgstr "" #: library/_thread.rst:7 diff --git a/library/abc.po b/library/abc.po index 7ac2299ec..472d2c15c 100644 --- a/library/abc.po +++ b/library/abc.po @@ -28,17 +28,18 @@ msgstr "" 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.)" +"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 "" #: 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, if it is :" -"term:`hashable` or if it is a :term:`mapping`." +"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, if " +"it is :term:`hashable` or if it is a :term:`mapping`." msgstr "" #: library/abc.rst:27 @@ -125,8 +126,8 @@ msgstr "" #: library/abc.rst:88 msgid "" -"To detect calls to :meth:`!register`, you can use the :func:" -"`get_cache_token` function." +"To detect calls to :meth:`!register`, you can use " +"the :func:`get_cache_token` function." msgstr "" #: library/abc.rst:92 @@ -142,8 +143,8 @@ msgid "" "Check whether *subclass* is considered a subclass of this ABC. This means " "that you can customize the behavior of :func:`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:`~type." -"__subclasscheck__` method of the ABC.)" +"subclass of the ABC. (This class method is called from " +"the :meth:`~type.__subclasscheck__` method of the ABC.)" msgstr "" #: library/abc.rst:104 @@ -192,19 +193,20 @@ msgstr "" #: library/abc.rst:143 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." +"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 "" #: library/abc.rst:149 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:" -"`~type.__mro__` list) is considered a ``MyIterable`` too." +"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:`~type.__mro__` list) is considered a ``MyIterable`` " +"too." msgstr "" #: library/abc.rst:154 @@ -373,9 +375,10 @@ msgstr "" #: library/abc.rst:285 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." +"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 "" #: library/abc.rst:290 diff --git a/library/aifc.po b/library/aifc.po index d91e72081..b2220368b 100644 --- a/library/aifc.po +++ b/library/aifc.po @@ -70,9 +70,10 @@ msgid "" "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." +"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 "" #: library/aifc.rst:56 @@ -117,8 +118,8 @@ msgstr "" #: library/aifc.rst:99 msgid "" "Returns a :func:`~collections.namedtuple` ``(nchannels, sampwidth, " -"framerate, nframes, comptype, compname)``, equivalent to output of the :meth:" -"`get\\*` methods." +"framerate, nframes, comptype, compname)``, equivalent to output of " +"the :meth:`get\\*` methods." msgstr "" #: library/aifc.rst:106 diff --git a/library/archiving.po b/library/archiving.po index 36d696862..76e5c40a8 100644 --- a/library/archiving.po +++ b/library/archiving.po @@ -24,6 +24,6 @@ msgstr "" 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." +"format archives. See also :ref:`archiving-operations` provided by " +"the :mod:`shutil` module." msgstr "" diff --git a/library/argparse.po b/library/argparse.po index 970fe6452..44d0d0972 100644 --- a/library/argparse.po +++ b/library/argparse.po @@ -33,16 +33,16 @@ msgstr "" #: 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 `." +"introduction to Python command-line parsing, have a look at " +"the :ref:`argparse tutorial `." msgstr "" #: 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 " +"argparse` will figure out how to parse those out of :data:`sys.argv`. " +"The :mod:`!argparse` module also automatically generates help and usage " "messages. The module will also issue errors when users give the program " "invalid arguments." msgstr "" @@ -92,8 +92,8 @@ msgstr "" #: library/argparse.rst:53 msgid "" -"If you're looking for a guide about how to upgrade :mod:`optparse` code to :" -"mod:`!argparse`, see :ref:`Upgrading Optparse Code `." msgstr "" @@ -357,11 +357,11 @@ msgstr "" 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::" +"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 "" #: library/argparse.rst:237 @@ -408,9 +408,9 @@ msgstr "" #: library/argparse.rst:274 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::" +"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 "" #: library/argparse.rst:279 @@ -581,9 +581,9 @@ msgstr "" #: library/argparse.rst:406 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 " +"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']``." @@ -604,10 +604,10 @@ msgstr "" #: library/argparse.rst:418 msgid "" ":class:`ArgumentParser` changed encoding and errors to read arguments files " -"from default (e.g. :func:`locale.getpreferredencoding(False) ` and ``\"strict\"``) to the :term:`filesystem encoding " -"and error handler`. Arguments file should be encoded in UTF-8 instead of " -"ANSI Codepage on Windows." +"from default (e.g. :func:`locale.getpreferredencoding(False) " +"` and ``\"strict\"``) to the :term:`filesystem " +"encoding and error handler`. Arguments file should be encoded in UTF-8 " +"instead of ANSI Codepage on Windows." msgstr "" #: library/argparse.rst:426 @@ -616,14 +616,15 @@ msgstr "" #: library/argparse.rst:428 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``::" +"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 "" #: library/argparse.rst:437 @@ -643,9 +644,9 @@ msgstr "" #: library/argparse.rst:450 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." +"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 "" #: library/argparse.rst:454 @@ -729,8 +730,8 @@ msgstr "" #: library/argparse.rst:510 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`::" +"This can be achieved by passing ``False`` as the ``add_help=`` argument " +"to :class:`ArgumentParser`::" msgstr "" #: library/argparse.rst:514 @@ -768,9 +769,10 @@ msgstr "" #: library/argparse.rst:539 msgid "" -"Normally, when you pass an invalid argument list to the :meth:" -"`~ArgumentParser.parse_args` method of an :class:`ArgumentParser`, it will " -"print a *message* to :data:`sys.stderr` and exit with a status code of 2." +"Normally, when you pass an invalid argument list to " +"the :meth:`~ArgumentParser.parse_args` method of an :class:`ArgumentParser`, " +"it will print a *message* to :data:`sys.stderr` and exit with a status code " +"of 2." msgstr "" #: library/argparse.rst:543 @@ -856,8 +858,8 @@ msgstr "" #: library/argparse.rst:593 msgid "" -"dest_ - The name of the attribute to be added to the object returned by :" -"meth:`parse_args`." +"dest_ - The name of the attribute to be added to the object returned " +"by :meth:`parse_args`." msgstr "" #: library/argparse.rst:602 @@ -868,9 +870,9 @@ msgstr "" 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." +"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." msgstr "" #: library/argparse.rst:610 @@ -1048,9 +1050,9 @@ msgstr "" #: library/argparse.rst:723 msgid "" -"``'version'`` - This expects a ``version=`` keyword argument in the :meth:" -"`~ArgumentParser.add_argument` call, and prints version information and " -"exits when invoked::" +"``'version'`` - This expects a ``version=`` keyword argument in " +"the :meth:`~ArgumentParser.add_argument` call, and prints version " +"information and exits when invoked::" msgstr "" #: library/argparse.rst:727 @@ -1261,10 +1263,11 @@ msgstr "" 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. If " -"``const`` is not provided to :meth:`~ArgumentParser.add_argument`, it will " -"receive a default value of ``None``." +"the ``const`` value to one of the attributes of the object returned " +"by :meth:`~ArgumentParser.parse_args`. See the action_ description for " +"examples. If ``const`` is not provided " +"to :meth:`~ArgumentParser.add_argument`, it will receive a default value of " +"``None``." msgstr "" #: library/argparse.rst:886 @@ -1290,11 +1293,11 @@ msgstr "" #: library/argparse.rst:902 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::" +"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 "" #: library/argparse.rst:909 @@ -1325,8 +1328,9 @@ msgstr "" 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::" +"conversion argument, if provided, before setting the attribute on " +"the :class:`Namespace` return value. Otherwise, the parser uses the value " +"as is::" msgstr "" #: library/argparse.rst:929 @@ -1399,9 +1403,9 @@ msgstr "" #: library/argparse.rst:974 msgid "" "The argument to ``type`` can be any callable that accepts a single string. " -"If the function raises :exc:`ArgumentTypeError`, :exc:`TypeError`, or :exc:" -"`ValueError`, the exception is caught and a nicely formatted error message " -"is displayed. No other exception types are handled." +"If the function raises :exc:`ArgumentTypeError`, :exc:`TypeError`, " +"or :exc:`ValueError`, the exception is caught and a nicely formatted error " +"message is displayed. No other exception types are handled." msgstr "" #: library/argparse.rst:979 @@ -1456,9 +1460,9 @@ msgstr "" #: library/argparse.rst:1015 msgid "" "For example, JSON or YAML conversions have complex error cases that require " -"better reporting than can be given by the ``type`` keyword. A :exc:`~json." -"JSONDecodeError` would not be well formatted and a :exc:`FileNotFoundError` " -"exception would not be handled at all." +"better reporting than can be given by the ``type`` keyword. " +"A :exc:`~json.JSONDecodeError` would not be well formatted and " +"a :exc:`FileNotFoundError` exception would not be handled at all." msgstr "" #: library/argparse.rst:1020 @@ -1554,9 +1558,9 @@ msgstr "" #: library/argparse.rst:1085 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." +"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 "" #: library/argparse.rst:1091 @@ -1582,8 +1586,8 @@ 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.::" +"arguments to :meth:`~ArgumentParser.add_argument`, e.g. ``%(default)s``, ``%" +"(type)s``, etc.::" msgstr "" #: library/argparse.rst:1110 @@ -1716,10 +1720,10 @@ msgstr "" 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`::" +"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 "" #: library/argparse.rst:1215 @@ -1773,8 +1777,8 @@ msgstr "" msgid "" ":class:`!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:" -"`~ArgumentParser.add_argument`." +"follows this API may be passed as the ``action`` parameter " +"to :meth:`~ArgumentParser.add_argument`." msgstr "" #: library/argparse.rst:1256 @@ -1782,8 +1786,8 @@ msgid "" ":class:`!Action` objects are used by an :class:`ArgumentParser` to represent " "the information needed to parse a single argument from one or more strings " "from the command line. The :class:`!Action` class must accept the two " -"positional arguments plus any keyword arguments passed to :meth:" -"`ArgumentParser.add_argument` except for the ``action`` itself." +"positional arguments plus any keyword arguments passed " +"to :meth:`ArgumentParser.add_argument` except for the ``action`` itself." msgstr "" #: library/argparse.rst:1262 @@ -1808,16 +1812,16 @@ msgstr "" #: library/argparse.rst:1275 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`." +"*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 "" #: library/argparse.rst:1279 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`." +"applied. Type conversions are specified with the type_ keyword argument " +"to :meth:`~ArgumentParser.add_argument`." msgstr "" #: library/argparse.rst:1283 @@ -1861,14 +1865,14 @@ msgstr "" #: library/argparse.rst:1309 msgid "" -"args_ - List of strings to parse. The default is taken from :data:`sys." -"argv`." +"args_ - List of strings to parse. The default is taken " +"from :data:`sys.argv`." msgstr "" #: library/argparse.rst:1312 msgid "" -"namespace_ - An object to take the attributes. The default is a new empty :" -"class:`Namespace` object." +"namespace_ - An object to take the attributes. The default is a new " +"empty :class:`Namespace` object." msgstr "" #: library/argparse.rst:1317 @@ -2155,13 +2159,14 @@ msgid "" "example, the ``svn`` program can invoke subcommands 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 subcommands 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:`~_SubParsersAction.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." +"functions which require different kinds of command-line " +"arguments. :class:`ArgumentParser` supports the creation of such subcommands " +"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:`~_SubParsersAction.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 "" #: library/argparse.rst:1538 @@ -2419,10 +2424,10 @@ msgstr "" #: library/argparse.rst:1726 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)::" +"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 "" #: library/argparse.rst:1732 @@ -2485,12 +2490,12 @@ msgstr "" #: library/argparse.rst:1774 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::" +"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 "" #: library/argparse.rst:1782 @@ -2518,9 +2523,9 @@ msgstr "" msgid "" "The optional, keyword-only parameters argument_default_ and " "conflict_handler_ allow for finer-grained control of the behavior of the " -"argument group. These parameters have the same meaning as in the :class:" -"`ArgumentParser` constructor, but apply specifically to the argument group " -"rather than the entire parser." +"argument group. These parameters have the same meaning as in " +"the :class:`ArgumentParser` constructor, but apply specifically to the " +"argument group rather than the entire parser." msgstr "" #: library/argparse.rst:1805 @@ -2584,9 +2589,10 @@ msgstr "" #: library/argparse.rst:1848 msgid "" "Note that currently mutually exclusive argument groups do not support the " -"*title* and *description* arguments of :meth:`~ArgumentParser." -"add_argument_group`. However, a mutually exclusive group can be added to an " -"argument group that has a title and description. For example::" +"*title* and *description* arguments " +"of :meth:`~ArgumentParser.add_argument_group`. However, a mutually exclusive " +"group can be added to an argument group that has a title and description. " +"For example::" msgstr "" #: library/argparse.rst:1854 @@ -2623,9 +2629,9 @@ msgstr "" #: library/argparse.rst:1883 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 " +"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 "" @@ -2662,8 +2668,9 @@ msgstr "" #: library/argparse.rst:1909 msgid "" -"Get the default value for a namespace attribute, as set by either :meth:" -"`~ArgumentParser.add_argument` or by :meth:`~ArgumentParser.set_defaults`::" +"Get the default value for a namespace attribute, as set by " +"either :meth:`~ArgumentParser.add_argument` or " +"by :meth:`~ArgumentParser.set_defaults`::" msgstr "" #: library/argparse.rst:1913 @@ -2707,8 +2714,8 @@ msgstr "" #: library/argparse.rst:1943 msgid "" -"Return a string containing a brief description of how the :class:" -"`ArgumentParser` should be invoked on the command line." +"Return a string containing a brief description of how " +"the :class:`ArgumentParser` should be invoked on the command line." msgstr "" #: library/argparse.rst:1948 @@ -2743,10 +2750,10 @@ msgstr "" #: library/argparse.rst:1973 msgid "" -":ref:`Prefix matching ` rules apply to :meth:" -"`~ArgumentParser.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." +":ref:`Prefix matching ` rules apply " +"to :meth:`~ArgumentParser.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 "" #: library/argparse.rst:1980 @@ -2803,8 +2810,8 @@ msgstr "" #: library/argparse.rst:2018 msgid "" -"This method prints a usage message, including the *message*, to :data:`sys." -"stderr` and terminates the program with a status code of 2." +"This method prints a usage message, including the *message*, " +"to :data:`sys.stderr` and terminates the program with a status code of 2." msgstr "" #: library/argparse.rst:2023 @@ -2829,10 +2836,11 @@ msgstr "" #: library/argparse.rst:2038 msgid "" -"The following example shows the difference between :meth:`~ArgumentParser." -"parse_known_args` and :meth:`~ArgumentParser.parse_intermixed_args`: the " -"former returns ``['2', '3']`` as unparsed arguments, while the latter " -"collects all the positionals into ``rest``. ::" +"The following example shows the difference " +"between :meth:`~ArgumentParser.parse_known_args` " +"and :meth:`~ArgumentParser.parse_intermixed_args`: the former returns " +"``['2', '3']`` as unparsed arguments, while the latter collects all the " +"positionals into ``rest``. ::" msgstr "" #: library/argparse.rst:2044 diff --git a/library/array.po b/library/array.po index b6a014d68..da49680a9 100644 --- a/library/array.po +++ b/library/array.po @@ -220,9 +220,9 @@ msgstr "" #: library/array.rst:78 msgid "" "A new array whose items are restricted by *typecode*, and initialized from " -"the optional *initializer* value, which must be a :class:`bytes` or :class:" -"`bytearray` object, a Unicode string, or iterable over elements of the " -"appropriate type." +"the optional *initializer* value, which must be a :class:`bytes` " +"or :class:`bytearray` object, a Unicode string, or iterable over elements of " +"the appropriate type." msgstr "" #: library/array.rst:83 @@ -286,9 +286,9 @@ msgstr "" #: 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." +"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 "" #: library/array.rst:143 @@ -298,16 +298,17 @@ msgstr "" #: 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." +"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 "" #: library/array.rst:156 msgid "" "Appends items from the :term:`bytes-like object`, interpreting its content " -"as an array of machine values (as if it had been read from a file using the :" -"meth:`fromfile` method)." +"as an array of machine values (as if it had been read from a file using " +"the :meth:`fromfile` method)." msgstr "" #: library/array.rst:160 @@ -317,31 +318,31 @@ msgstr "" #: library/array.rst:166 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." +"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." msgstr "" #: 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." +"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 "" #: library/array.rst:180 msgid "" "Extends this array with data from the given Unicode string. The array must " -"have type code ``'u'``; otherwise a :exc:`ValueError` is raised. Use ``array." -"frombytes(unicodestring.encode(enc))`` to append Unicode data to an array of " -"some other type." +"have type code ``'u'``; otherwise a :exc:`ValueError` is raised. Use " +"``array.frombytes(unicodestring.encode(enc))`` to append Unicode data to an " +"array of some other type." msgstr "" #: library/array.rst:188 msgid "" "Return the smallest *i* such that *i* is the index of the first occurrence " "of *x* in the array. The optional arguments *start* and *stop* can be " -"specified to search for *x* within a subsection of the array. Raise :exc:" -"`ValueError` if *x* is not found." +"specified to search for *x* within a subsection of the array. " +"Raise :exc:`ValueError` if *x* is not found." msgstr "" #: library/array.rst:193 @@ -401,10 +402,11 @@ msgid "" "initializer)``. The *initializer* is omitted if the array is empty, " "otherwise it is a Unicode string if the *typecode* is ``'u'``, otherwise it " "is a list of numbers. The string representation 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 :class:`~array.array` class has been imported using " -"``from array import array``. Variables ``inf`` and ``nan`` must also be " -"defined if it contains corresponding floating-point values. Examples::" +"be converted back to an array with the same type and value " +"using :func:`eval`, so long as the :class:`~array.array` class has been " +"imported using ``from array import array``. Variables ``inf`` and ``nan`` " +"must also be defined if it contains corresponding floating-point values. " +"Examples::" msgstr "" #: library/array.rst:259 diff --git a/library/ast.po b/library/ast.po index 82a8f5b2b..60b287e54 100644 --- a/library/ast.po +++ b/library/ast.po @@ -34,12 +34,12 @@ msgstr "" #: library/ast.rst:23 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." +"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 "" #: library/ast.rst:33 @@ -231,9 +231,9 @@ msgstr "" #: library/ast.rst:46 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:" -"`above `. They are defined in the :mod:`!_ast` C module " -"and re-exported in :mod:`ast`." +"derived from the :file:`Parser/Python.asdl` file, which is " +"reproduced :ref:`above `. They are defined in the :mod:`!" +"_ast` C module and re-exported in :mod:`ast`." msgstr "" #: library/ast.rst:51 @@ -271,14 +271,14 @@ msgstr "" #: library/ast.rst:82 msgid "" -"Instances of :class:`ast.expr` and :class:`ast.stmt` subclasses have :attr:" -"`lineno`, :attr:`col_offset`, :attr:`end_lineno`, and :attr:`end_col_offset` " -"attributes. The :attr:`lineno` and :attr:`end_lineno` are the first and " -"last line numbers of source text span (1-indexed so the first line is line " -"1) and the :attr:`col_offset` and :attr:`end_col_offset` are the " -"corresponding UTF-8 byte offsets of the first and last tokens that generated " -"the node. The UTF-8 offset is recorded because the parser uses UTF-8 " -"internally." +"Instances of :class:`ast.expr` and :class:`ast.stmt` subclasses " +"have :attr:`lineno`, :attr:`col_offset`, :attr:`end_lineno`, " +"and :attr:`end_col_offset` attributes. The :attr:`lineno` " +"and :attr:`end_lineno` are the first and last line numbers of source text " +"span (1-indexed so the first line is line 1) and the :attr:`col_offset` " +"and :attr:`end_col_offset` are the corresponding UTF-8 byte offsets of the " +"first and last tokens that generated the node. The UTF-8 offset is recorded " +"because the parser uses UTF-8 internally." msgstr "" #: library/ast.rst:91 @@ -346,10 +346,10 @@ msgstr "" #: library/ast.rst:131 msgid "" -"Old classes :class:`!ast.Num`, :class:`!ast.Str`, :class:`!ast.Bytes`, :" -"class:`!ast.NameConstant` and :class:`!ast.Ellipsis` are still available, " -"but they will be removed in future Python releases. In the meantime, " -"instantiating them will return an instance of a different class." +"Old classes :class:`!ast.Num`, :class:`!ast.Str`, :class:`!" +"ast.Bytes`, :class:`!ast.NameConstant` and :class:`!ast.Ellipsis` are still " +"available, but they will be removed in future Python releases. In the " +"meantime, instantiating them will return an instance of a different class." msgstr "" #: library/ast.rst:138 @@ -362,8 +362,9 @@ msgstr "" #: library/ast.rst:144 msgid "" "The descriptions of the specific node classes displayed here were initially " -"adapted from the fantastic `Green Tree Snakes `__ project and all its contributors." +"adapted from the fantastic `Green Tree Snakes `__ project and all its " +"contributors." msgstr "" #: library/ast.rst:153 @@ -538,8 +539,8 @@ msgstr "" #: library/ast.rst:284 msgid "" -"An f-string, comprising a series of :class:`FormattedValue` and :class:" -"`Constant` nodes." +"An f-string, comprising a series of :class:`FormattedValue` " +"and :class:`Constant` nodes." msgstr "" #: library/ast.rst:287 @@ -681,9 +682,9 @@ msgstr "" #: library/ast.rst:421 msgid "" -"A ``*var`` variable reference. ``value`` holds the variable, typically a :" -"class:`Name` node. This type must be used when building a :class:`Call` node " -"with ``*args``." +"A ``*var`` variable reference. ``value`` holds the variable, typically " +"a :class:`Name` node. This type must be used when building a :class:`Call` " +"node with ``*args``." msgstr "" #: library/ast.rst:425 @@ -712,9 +713,9 @@ msgstr "" msgid "" "When an expression, such as a function call, appears as a statement by " "itself with its return value not used or stored, it is wrapped in this " -"container. ``value`` holds one of the other nodes in this section, a :class:" -"`Constant`, a :class:`Name`, a :class:`Lambda`, a :class:`Yield` or :class:" -"`YieldFrom` node." +"container. ``value`` holds one of the other nodes in this section, " +"a :class:`Constant`, a :class:`Name`, a :class:`Lambda`, a :class:`Yield` " +"or :class:`YieldFrom` node." msgstr "" #: library/ast.rst:455 @@ -824,8 +825,8 @@ msgstr "" #: library/ast.rst:584 msgid "" -"A function call. ``func`` is the function, which will often be a :class:" -"`Name` or :class:`Attribute` object. Of the arguments:" +"A function call. ``func`` is the function, which will often be " +"a :class:`Name` or :class:`Attribute` object. Of the arguments:" msgstr "" #: library/ast.rst:587 @@ -888,10 +889,10 @@ msgstr "" #: library/ast.rst:636 msgid "" -"Attribute access, e.g. ``d.keys``. ``value`` is a node, typically a :class:" -"`Name`. ``attr`` is a bare string giving the name of the attribute, and " -"``ctx`` is :class:`Load`, :class:`Store` or :class:`Del` according to how " -"the attribute is acted on." +"Attribute access, e.g. ``d.keys``. ``value`` is a node, typically " +"a :class:`Name`. ``attr`` is a bare string giving the name of the attribute, " +"and ``ctx`` is :class:`Load`, :class:`Store` or :class:`Del` according to " +"how the attribute is acted on." msgstr "" #: library/ast.rst:641 @@ -907,9 +908,9 @@ msgstr "" #: library/ast.rst:653 msgid "" "A named expression. This AST node is produced by the assignment expressions " -"operator (also known as the walrus operator). As opposed to the :class:" -"`Assign` node in which the first argument can be multiple nodes, in this " -"case both ``target`` and ``value`` must be single nodes." +"operator (also known as the walrus operator). As opposed to " +"the :class:`Assign` node in which the first argument can be multiple nodes, " +"in this case both ``target`` and ``value`` must be single nodes." msgstr "" #: library/ast.rst:658 @@ -928,9 +929,10 @@ msgstr "" #: library/ast.rst:673 msgid "" "A subscript, such as ``l[1]``. ``value`` is the subscripted object (usually " -"sequence or mapping). ``slice`` is an index, slice or key. It can be a :" -"class:`Tuple` and contain a :class:`Slice`. ``ctx`` is :class:`Load`, :class:" -"`Store` or :class:`Del` according to the action performed with the subscript." +"sequence or mapping). ``slice`` is an index, slice or key. It can be " +"a :class:`Tuple` and contain a :class:`Slice`. ``ctx`` " +"is :class:`Load`, :class:`Store` or :class:`Del` according to the action " +"performed with the subscript." msgstr "" #: library/ast.rst:679 @@ -1155,17 +1157,17 @@ msgstr "" msgid "" "An assignment with a type annotation. ``target`` is a single node and can be " "a :class:`Name`, an :class:`Attribute` or a :class:`Subscript`. " -"``annotation`` is the annotation, such as a :class:`Constant` or :class:" -"`Name` node. ``value`` is a single optional node." +"``annotation`` is the annotation, such as a :class:`Constant` " +"or :class:`Name` node. ``value`` is a single optional node." msgstr "" #: library/ast.rst:888 msgid "" "``simple`` is always either 0 (indicating a \"complex\" target) or 1 " -"(indicating a \"simple\" target). A \"simple\" target consists solely of a :" -"class:`Name` node that does not appear between parentheses; all other " -"targets are considered complex. Only simple targets appear in the :attr:" -"`~object.__annotations__` dictionary of modules and classes." +"(indicating a \"simple\" target). A \"simple\" target consists solely of " +"a :class:`Name` node that does not appear between parentheses; all other " +"targets are considered complex. Only simple targets appear in " +"the :attr:`~object.__annotations__` dictionary of modules and classes." msgstr "" #: library/ast.rst:894 @@ -1279,8 +1281,8 @@ msgstr "" #: library/ast.rst:997 msgid "" -"Represents a ``del`` statement. ``targets`` is a list of nodes, such as :" -"class:`Name`, :class:`Attribute` or :class:`Subscript` nodes." +"Represents a ``del`` statement. ``targets`` is a list of nodes, such " +"as :class:`Name`, :class:`Attribute` or :class:`Subscript` nodes." msgstr "" #: library/ast.rst:1000 @@ -1312,9 +1314,9 @@ msgstr "" #: library/ast.rst:1028 msgid "" "A :ref:`type alias ` created through the :keyword:`type` " -"statement. ``name`` is the name of the alias, ``type_params`` is a list of :" -"ref:`type parameters `, and ``value`` is the value of the " -"type alias." +"statement. ``name`` is the name of the alias, ``type_params`` is a list " +"of :ref:`type parameters `, and ``value`` is the value of " +"the type alias." msgstr "" #: library/ast.rst:1033 @@ -1411,8 +1413,8 @@ msgstr "" #: library/ast.rst:1118 msgid "" -"An ``if`` statement. ``test`` holds a single node, such as a :class:" -"`Compare` node. ``body`` and ``orelse`` each hold a list of nodes." +"An ``if`` statement. ``test`` holds a single node, such as " +"a :class:`Compare` node. ``body`` and ``orelse`` each hold a list of nodes." msgstr "" #: library/ast.rst:1121 @@ -1454,9 +1456,9 @@ msgstr "" #: library/ast.rst:1156 msgid "" "A ``for`` loop. ``target`` holds the variable(s) the loop assigns to, as a " -"single :class:`Name`, :class:`Tuple`, :class:`List`, :class:`Attribute` or :" -"class:`Subscript` node. ``iter`` holds the item to be looped over, again as " -"a single node. ``body`` and ``orelse`` contain lists of nodes to execute. " +"single :class:`Name`, :class:`Tuple`, :class:`List`, :class:`Attribute` " +"or :class:`Subscript` node. ``iter`` holds the item to be looped over, again " +"as a single node. ``body`` and ``orelse`` contain lists of nodes to execute. " "Those in ``orelse`` are executed if the loop finishes normally, rather than " "via a ``break`` statement." msgstr "" @@ -1669,9 +1671,9 @@ msgstr "" #: library/ast.rst:1375 msgid "" "A single context manager in a ``with`` block. ``context_expr`` is the " -"context manager, often a :class:`Call` node. ``optional_vars`` is a :class:" -"`Name`, :class:`Tuple` or :class:`List` for the ``as foo`` part, or ``None`` " -"if that isn't used." +"context manager, often a :class:`Call` node. ``optional_vars`` is " +"a :class:`Name`, :class:`Tuple` or :class:`List` for the ``as foo`` part, or " +"``None`` if that isn't used." msgstr "" #: library/ast.rst:1380 @@ -1715,8 +1717,8 @@ msgstr "" #: library/ast.rst:1421 msgid "" "A single case pattern in a ``match`` statement. ``pattern`` contains the " -"match pattern that the subject will be matched against. Note that the :class:" -"`AST` nodes produced for patterns differ from those produced for " +"match pattern that the subject will be matched against. Note that " +"the :class:`AST` nodes produced for patterns differ from those produced for " "expressions, even when they share the same syntax." msgstr "" @@ -2121,8 +2123,9 @@ msgstr "" #: library/ast.rst:1804 msgid "" "A :class:`typing.TypeVar`. ``name`` is the name of the type variable. " -"``bound`` is the bound or constraints, if any. If ``bound`` is a :class:" -"`Tuple`, it represents constraints; otherwise it represents the bound." +"``bound`` is the bound or constraints, if any. If ``bound`` is " +"a :class:`Tuple`, it represents constraints; otherwise it represents the " +"bound." msgstr "" #: library/ast.rst:1808 @@ -2424,8 +2427,8 @@ msgstr "" #: library/ast.rst:2062 msgid "" "``keywords`` is a list of :class:`.keyword` nodes, principally for " -"'metaclass'. Other keywords will be passed to the metaclass, as per :pep:" -"`3115`." +"'metaclass'. Other keywords will be passed to the metaclass, as " +"per :pep:`3115`." msgstr "" #: library/ast.rst:2064 @@ -2472,8 +2475,8 @@ msgstr "" #: library/ast.rst:2104 msgid "" -"An ``async def`` function definition. Has the same fields as :class:" -"`FunctionDef`." +"An ``async def`` function definition. Has the same fields " +"as :class:`FunctionDef`." msgstr "" #: library/ast.rst:2113 @@ -2519,11 +2522,11 @@ msgstr "" #: library/ast.rst:2152 msgid "" -"When a string is parsed by :func:`ast.parse`, operator nodes (subclasses of :" -"class:`ast.operator`, :class:`ast.unaryop`, :class:`ast.cmpop`, :class:`ast." -"boolop` and :class:`ast.expr_context`) on the returned tree will be " -"singletons. Changes to one will be reflected in all other occurrences of the " -"same value (e.g. :class:`ast.Add`)." +"When a string is parsed by :func:`ast.parse`, operator nodes (subclasses " +"of :class:`ast.operator`, :class:`ast.unaryop`, :class:`ast.cmpop`, :class:`ast.boolop` " +"and :class:`ast.expr_context`) on the returned tree will be singletons. " +"Changes to one will be reflected in all other occurrences of the same value " +"(e.g. :class:`ast.Add`)." msgstr "" #: library/ast.rst:2160 @@ -2546,8 +2549,8 @@ msgstr "" msgid "" "If ``type_comments=True`` is given, the parser is modified to check and " "return type comments as specified by :pep:`484` and :pep:`526`. This is " -"equivalent to adding :data:`ast.PyCF_TYPE_COMMENTS` to the flags passed to :" -"func:`compile`. This will report syntax errors for misplaced type " +"equivalent to adding :data:`ast.PyCF_TYPE_COMMENTS` to the flags passed " +"to :func:`compile`. This will report syntax errors for misplaced type " "comments. Without this flag, type comments will be ignored, and the " "``type_comment`` field on selected AST nodes will always be ``None``. In " "addition, the locations of ``# type: ignore`` comments will be returned as " @@ -2609,8 +2612,8 @@ msgstr "" #: library/ast.rst:2218 msgid "" "Unparse an :class:`ast.AST` object and generate a string with code that " -"would produce an equivalent :class:`ast.AST` object if parsed back with :" -"func:`ast.parse`." +"would produce an equivalent :class:`ast.AST` object if parsed back " +"with :func:`ast.parse`." msgstr "" #: library/ast.rst:2223 @@ -2622,8 +2625,8 @@ msgstr "" #: library/ast.rst:2228 msgid "" -"Trying to unparse a highly complex expression would result with :exc:" -"`RecursionError`." +"Trying to unparse a highly complex expression would result " +"with :exc:`RecursionError`." msgstr "" #: library/ast.rst:2236 @@ -2661,8 +2664,9 @@ msgstr "" #: library/ast.rst:2259 msgid "" -"It can raise :exc:`ValueError`, :exc:`TypeError`, :exc:`SyntaxError`, :exc:" -"`MemoryError` and :exc:`RecursionError` depending on the malformed input." +"It can " +"raise :exc:`ValueError`, :exc:`TypeError`, :exc:`SyntaxError`, :exc:`MemoryError` " +"and :exc:`RecursionError` depending on the malformed input." msgstr "" #: library/ast.rst:2263 @@ -2679,10 +2683,10 @@ msgstr "" #: library/ast.rst:2275 msgid "" -"Return the docstring of the given *node* (which must be a :class:" -"`FunctionDef`, :class:`AsyncFunctionDef`, :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`." +"Return the docstring of the given *node* (which must be " +"a :class:`FunctionDef`, :class:`AsyncFunctionDef`, :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 "" #: library/ast.rst:2281 @@ -2692,9 +2696,9 @@ msgstr "" #: library/ast.rst:2287 msgid "" "Get source code segment of the *source* that generated *node*. If some " -"location information (:attr:`~ast.AST.lineno`, :attr:`~ast.AST.end_lineno`, :" -"attr:`~ast.AST.col_offset`, or :attr:`~ast.AST.end_col_offset`) is missing, " -"return ``None``." +"location information " +"(:attr:`~ast.AST.lineno`, :attr:`~ast.AST.end_lineno`, :attr:`~ast.AST.col_offset`, " +"or :attr:`~ast.AST.end_col_offset`) is missing, return ``None``." msgstr "" #: library/ast.rst:2291 @@ -2705,12 +2709,12 @@ msgstr "" #: library/ast.rst:2299 msgid "" -"When you compile a node tree with :func:`compile`, the compiler expects :" -"attr:`~ast.AST.lineno` and :attr:`~ast.AST.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*." +"When you compile a node tree with :func:`compile`, the compiler " +"expects :attr:`~ast.AST.lineno` and :attr:`~ast.AST.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 "" #: library/ast.rst:2308 @@ -2722,9 +2726,10 @@ msgstr "" #: library/ast.rst:2315 msgid "" -"Copy source location (:attr:`~ast.AST.lineno`, :attr:`~ast.AST.col_offset`, :" -"attr:`~ast.AST.end_lineno`, and :attr:`~ast.AST.end_col_offset`) from " -"*old_node* to *new_node* if possible, and return *new_node*." +"Copy source location " +"(:attr:`~ast.AST.lineno`, :attr:`~ast.AST.col_offset`, :attr:`~ast.AST.end_lineno`, " +"and :attr:`~ast.AST.end_col_offset`) from *old_node* to *new_node* if " +"possible, and return *new_node*." msgstr "" #: library/ast.rst:2322 @@ -2761,9 +2766,9 @@ msgstr "" #: library/ast.rst:2350 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." +"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 "" #: library/ast.rst:2356 @@ -2783,16 +2788,16 @@ msgstr "" #: library/ast.rst:2366 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." +"during traversal. For this a special visitor exists " +"(:class:`NodeTransformer`) that allows modifications." msgstr "" #: library/ast.rst:2372 msgid "" -"Methods :meth:`!visit_Num`, :meth:`!visit_Str`, :meth:`!visit_Bytes`, :meth:" -"`!visit_NameConstant` and :meth:`!visit_Ellipsis` are deprecated now and " -"will not be called in future Python versions. Add the :meth:" -"`visit_Constant` method to handle all constant nodes." +"Methods :meth:`!visit_Num`, :meth:`!visit_Str`, :meth:`!" +"visit_Bytes`, :meth:`!visit_NameConstant` and :meth:`!visit_Ellipsis` are " +"deprecated now and will not be called in future Python versions. Add " +"the :meth:`visit_Constant` method to handle all constant nodes." msgstr "" #: library/ast.rst:2380 @@ -2831,8 +2836,8 @@ msgstr "" #: library/ast.rst:2401 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:`~ast." -"NodeVisitor.generic_visit` method for the node first." +"either transform the child nodes yourself or call " +"the :meth:`~ast.NodeVisitor.generic_visit` method for the node first." msgstr "" #: library/ast.rst:2405 @@ -2845,9 +2850,9 @@ msgstr "" #: library/ast.rst:2409 msgid "" "If :class:`NodeTransformer` introduces new nodes (that weren't part of " -"original tree) without giving them location information (such as :attr:`~ast." -"AST.lineno`), :func:`fix_missing_locations` should be called with the new " -"sub-tree to recalculate the location information::" +"original tree) without giving them location information (such " +"as :attr:`~ast.AST.lineno`), :func:`fix_missing_locations` should be called " +"with the new sub-tree to recalculate the location information::" msgstr "" #: library/ast.rst:2414 @@ -2941,8 +2946,8 @@ msgstr "" #: library/ast.rst:2496 msgid "" -"Specify what kind of code must be compiled, like the *mode* argument in :" -"func:`parse`." +"Specify what kind of code must be compiled, like the *mode* argument " +"in :func:`parse`." msgstr "" #: library/ast.rst:2501 diff --git a/library/asyncio-dev.po b/library/asyncio-dev.po index 662bc5155..3d372152b 100644 --- a/library/asyncio-dev.po +++ b/library/asyncio-dev.po @@ -67,9 +67,9 @@ msgstr "" #: library/asyncio-dev.rst:36 msgid "" -"setting the log level of the :ref:`asyncio logger ` to :py:" -"const:`logging.DEBUG`, for example the following snippet of code can be run " -"at startup of the application::" +"setting the log level of the :ref:`asyncio logger ` " +"to :py:const:`logging.DEBUG`, for example the following snippet of code can " +"be run at startup of the application::" msgstr "" #: library/asyncio-dev.rst:40 @@ -96,9 +96,9 @@ msgstr "" #: library/asyncio-dev.rst:53 msgid "" -"Many non-threadsafe asyncio APIs (such as :meth:`loop.call_soon` and :meth:" -"`loop.call_at` methods) raise an exception if they are called from a wrong " -"thread." +"Many non-threadsafe asyncio APIs (such as :meth:`loop.call_soon` " +"and :meth:`loop.call_at` methods) raise an exception if they are called from " +"a wrong thread." msgstr "" #: library/asyncio-dev.rst:57 @@ -109,9 +109,9 @@ msgstr "" #: library/asyncio-dev.rst:60 msgid "" -"Callbacks taking longer than 100 milliseconds are logged. The :attr:`loop." -"slow_callback_duration` attribute can be used to set the minimum execution " -"duration in seconds that is considered \"slow\"." +"Callbacks taking longer than 100 milliseconds are logged. " +"The :attr:`loop.slow_callback_duration` attribute can be used to set the " +"minimum execution duration in seconds that is considered \"slow\"." msgstr "" #: library/asyncio-dev.rst:68 @@ -129,8 +129,8 @@ msgstr "" #: library/asyncio-dev.rst:76 msgid "" -"To schedule a :term:`callback` from another OS thread, the :meth:`loop." -"call_soon_threadsafe` method should be used. Example::" +"To schedule a :term:`callback` from another OS thread, " +"the :meth:`loop.call_soon_threadsafe` method should be used. Example::" msgstr "" #: library/asyncio-dev.rst:79 @@ -151,9 +151,9 @@ msgstr "" #: library/asyncio-dev.rst:89 msgid "" -"To schedule a coroutine object from a different OS thread, the :func:" -"`run_coroutine_threadsafe` function should be used. It returns a :class:" -"`concurrent.futures.Future` to access the result::" +"To schedule a coroutine object from a different OS thread, " +"the :func:`run_coroutine_threadsafe` function should be used. It returns " +"a :class:`concurrent.futures.Future` to access the result::" msgstr "" #: library/asyncio-dev.rst:93 @@ -174,22 +174,22 @@ msgstr "" #: library/asyncio-dev.rst:105 msgid "" -"The :meth:`loop.run_in_executor` method can be used with a :class:" -"`concurrent.futures.ThreadPoolExecutor` to execute blocking code in a " -"different OS thread without blocking the OS thread that the event loop runs " -"in." +"The :meth:`loop.run_in_executor` method can be used with " +"a :class:`concurrent.futures.ThreadPoolExecutor` to execute blocking code in " +"a different OS thread without blocking the OS thread that the event loop " +"runs in." msgstr "" #: library/asyncio-dev.rst:110 msgid "" "There is currently no way to schedule coroutines or callbacks directly from " -"a different process (such as one started with :mod:`multiprocessing`). The :" -"ref:`asyncio-event-loop-methods` section lists APIs that can read from pipes " -"and watch file descriptors without blocking the event loop. In addition, " -"asyncio's :ref:`Subprocess ` APIs provide a way to start " -"a process and communicate with it from the event loop. Lastly, the " -"aforementioned :meth:`loop.run_in_executor` method can also be used with a :" -"class:`concurrent.futures.ProcessPoolExecutor` to execute code in a " +"a different process (such as one started with :mod:`multiprocessing`). " +"The :ref:`asyncio-event-loop-methods` section lists APIs that can read from " +"pipes and watch file descriptors without blocking the event loop. In " +"addition, asyncio's :ref:`Subprocess ` APIs provide a " +"way to start a process and communicate with it from the event loop. Lastly, " +"the aforementioned :meth:`loop.run_in_executor` method can also be used with " +"a :class:`concurrent.futures.ProcessPoolExecutor` to execute code in a " "different process." msgstr "" @@ -234,8 +234,8 @@ msgstr "" #: library/asyncio-dev.rst:151 msgid "" "Network logging can block the event loop. It is recommended to use a " -"separate thread for handling logs or use non-blocking IO. For example, see :" -"ref:`blocking-handlers`." +"separate thread for handling logs or use non-blocking IO. For example, " +"see :ref:`blocking-handlers`." msgstr "" #: library/asyncio-dev.rst:159 @@ -245,8 +245,8 @@ msgstr "" #: library/asyncio-dev.rst:161 msgid "" "When a coroutine function is called, but not awaited (e.g. ``coro()`` " -"instead of ``await coro()``) or the coroutine is not scheduled with :meth:" -"`asyncio.create_task`, asyncio will emit a :exc:`RuntimeWarning`::" +"instead of ``await coro()``) or the coroutine is not scheduled " +"with :meth:`asyncio.create_task`, asyncio will emit a :exc:`RuntimeWarning`::" msgstr "" #: library/asyncio-dev.rst:166 @@ -292,8 +292,8 @@ msgstr "" #: library/asyncio-dev.rst:194 msgid "" -"The usual fix is to either await the coroutine or call the :meth:`asyncio." -"create_task` function::" +"The usual fix is to either await the coroutine or call " +"the :meth:`asyncio.create_task` function::" msgstr "" #: library/asyncio-dev.rst:197 diff --git a/library/asyncio-eventloop.po b/library/asyncio-eventloop.po index 6bf4faa75..451d84899 100644 --- a/library/asyncio-eventloop.po +++ b/library/asyncio-eventloop.po @@ -135,9 +135,9 @@ msgstr "" #: library/asyncio-eventloop.rst:86 msgid "" -"The `Callback Handles`_ section documents the :class:`Handle` and :class:" -"`TimerHandle` instances which are returned from scheduling methods such as :" -"meth:`loop.call_soon` and :meth:`loop.call_later`;" +"The `Callback Handles`_ section documents the :class:`Handle` " +"and :class:`TimerHandle` instances which are returned from scheduling " +"methods such as :meth:`loop.call_soon` and :meth:`loop.call_later`;" msgstr "" #: library/asyncio-eventloop.rst:90 @@ -148,8 +148,8 @@ msgstr "" #: library/asyncio-eventloop.rst:93 msgid "" -"The `Event Loop Implementations`_ section documents the :class:" -"`SelectorEventLoop` and :class:`ProactorEventLoop` classes;" +"The `Event Loop Implementations`_ section documents " +"the :class:`SelectorEventLoop` and :class:`ProactorEventLoop` classes;" msgstr "" #: library/asyncio-eventloop.rst:96 @@ -270,8 +270,8 @@ msgstr "" msgid "" "Schedule the closure of the default executor and wait for it to join all of " "the threads in the :class:`~concurrent.futures.ThreadPoolExecutor`. Once " -"this method has been called, using the default executor with :meth:`loop." -"run_in_executor` will raise a :exc:`RuntimeError`." +"this method has been called, using the default executor " +"with :meth:`loop.run_in_executor` will raise a :exc:`RuntimeError`." msgstr "" #: library/asyncio-eventloop.rst:194 @@ -322,9 +322,9 @@ msgstr "" #: library/asyncio-eventloop.rst:227 msgid "" -"The optional keyword-only *context* argument specifies a custom :class:" -"`contextvars.Context` for the *callback* to run in. Callbacks use the " -"current context when no *context* is provided." +"The optional keyword-only *context* argument specifies a " +"custom :class:`contextvars.Context` for the *callback* to run in. Callbacks " +"use the current context when no *context* is provided." msgstr "" #: library/asyncio-eventloop.rst:231 @@ -407,15 +407,15 @@ msgstr "" #: library/asyncio-eventloop.rst:288 msgid "" "The optional positional *args* will be passed to the callback when it is " -"called. If you want the callback to be called with keyword arguments use :" -"func:`functools.partial`." +"called. If you want the callback to be called with keyword arguments " +"use :func:`functools.partial`." msgstr "" #: library/asyncio-eventloop.rst:292 msgid "" -"An optional keyword-only *context* argument allows specifying a custom :" -"class:`contextvars.Context` for the *callback* to run in. The current " -"context is used when no *context* is provided." +"An optional keyword-only *context* argument allows specifying a " +"custom :class:`contextvars.Context` for the *callback* to run in. The " +"current context is used when no *context* is provided." msgstr "" #: library/asyncio-eventloop.rst:300 @@ -474,15 +474,15 @@ msgstr "" #: library/asyncio-eventloop.rst:355 msgid "" -"Schedule the execution of :ref:`coroutine ` *coro*. Return a :" -"class:`Task` object." +"Schedule the execution of :ref:`coroutine ` *coro*. Return " +"a :class:`Task` object." msgstr "" #: library/asyncio-eventloop.rst:358 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`." +"interoperability. In this case, the result type is a subclass " +"of :class:`Task`." msgstr "" #: library/asyncio-eventloop.rst:362 @@ -493,9 +493,9 @@ msgstr "" #: library/asyncio-eventloop.rst:365 msgid "" -"An optional keyword-only *context* argument allows specifying a custom :" -"class:`contextvars.Context` for the *coro* to run in. The current context " -"copy is created when no *context* is provided." +"An optional keyword-only *context* argument allows specifying a " +"custom :class:`contextvars.Context` for the *coro* to run in. The current " +"context copy is created when no *context* is provided." msgstr "" #: library/asyncio-eventloop.rst:369 @@ -515,8 +515,8 @@ msgid "" "If *factory* is ``None`` the default task factory will be set. Otherwise, " "*factory* must be a *callable* with the signature matching ``(loop, coro, " "context=None)``, where *loop* is a reference to the active event loop, and " -"*coro* is a coroutine object. The callable must return a :class:`asyncio." -"Future`-compatible object." +"*coro* is a coroutine object. The callable must return " +"a :class:`asyncio.Future`-compatible object." msgstr "" #: library/asyncio-eventloop.rst:388 @@ -535,9 +535,9 @@ msgstr "" #: library/asyncio-eventloop.rst:406 msgid "" -"The socket family can be either :py:const:`~socket.AF_INET` or :py:const:" -"`~socket.AF_INET6` depending on *host* (or the *family* argument, if " -"provided)." +"The socket family can be either :py:const:`~socket.AF_INET` " +"or :py:const:`~socket.AF_INET6` depending on *host* (or the *family* " +"argument, if provided)." msgstr "" #: library/asyncio-eventloop.rst:410 @@ -569,14 +569,14 @@ msgstr "" #: library/asyncio-eventloop.rst:423 msgid "" -"*protocol_factory* is called without arguments and is expected to return a :" -"ref:`protocol ` instance." +"*protocol_factory* is called without arguments and is expected to return " +"a :ref:`protocol ` instance." msgstr "" #: library/asyncio-eventloop.rst:426 msgid "" -"The protocol instance is coupled with the transport by calling its :meth:" -"`~BaseProtocol.connection_made` method." +"The protocol instance is coupled with the transport by calling " +"its :meth:`~BaseProtocol.connection_made` method." msgstr "" #: library/asyncio-eventloop.rst:429 @@ -596,9 +596,9 @@ msgstr "" 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 default context returned from :func:`ssl.create_default_context` " -"is used." +"object, this context is used to create the transport; if *ssl* " +"is :const:`True`, a default context returned " +"from :func:`ssl.create_default_context` is used." msgstr "" #: library/asyncio-eventloop.rst:442 @@ -647,18 +647,18 @@ msgstr "" #: library/asyncio-eventloop.rst:474 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*, *happy_eyeballs_delay*, " -"*interleave* and *local_addr* should be specified." +"*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*, " +"*happy_eyeballs_delay*, *interleave* and *local_addr* should be specified." msgstr "" #: library/asyncio-eventloop.rst:482 library/asyncio-eventloop.rst:597 #: library/asyncio-eventloop.rst:825 msgid "" "The *sock* argument transfers ownership of the socket to the transport " -"created. To close the socket, call the transport's :meth:`~asyncio." -"BaseTransport.close` method." +"created. To close the socket, call the " +"transport's :meth:`~asyncio.BaseTransport.close` method." msgstr "" #: library/asyncio-eventloop.rst:486 @@ -749,9 +749,10 @@ msgstr "" #: library/asyncio-eventloop.rst:555 msgid "" -"The socket family can be either :py:const:`~socket.AF_INET`, :py:const:" -"`~socket.AF_INET6`, or :py:const:`~socket.AF_UNIX`, depending on *host* (or " -"the *family* argument, if provided)." +"The socket family can be " +"either :py:const:`~socket.AF_INET`, :py:const:`~socket.AF_INET6`, " +"or :py:const:`~socket.AF_UNIX`, depending on *host* (or the *family* " +"argument, if provided)." msgstr "" #: library/asyncio-eventloop.rst:559 @@ -772,8 +773,8 @@ msgstr "" #: library/asyncio-eventloop.rst:568 msgid "" "*local_addr*, if given, is a ``(local_host, local_port)`` tuple used to bind " -"the socket locally. The *local_host* and *local_port* are looked up using :" -"meth:`getaddrinfo`." +"the socket locally. The *local_host* and *local_port* are looked up " +"using :meth:`getaddrinfo`." msgstr "" #: library/asyncio-eventloop.rst:572 @@ -810,14 +811,15 @@ msgstr "" 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`)." +"specified, *local_addr* and *remote_addr* should be omitted (must " +"be :const:`None`)." msgstr "" #: library/asyncio-eventloop.rst:601 msgid "" -"See :ref:`UDP echo client protocol ` and :" -"ref:`UDP echo server protocol ` examples." +"See :ref:`UDP echo client protocol ` " +"and :ref:`UDP echo server protocol ` " +"examples." msgstr "" #: library/asyncio-eventloop.rst:604 @@ -832,9 +834,10 @@ msgstr "" #: library/asyncio-eventloop.rst:611 msgid "" -"The *reuse_address* parameter is no longer supported, as using :ref:`socket." -"SO_REUSEADDR ` poses a significant security concern " -"for UDP. Explicitly passing ``reuse_address=True`` will raise an exception." +"The *reuse_address* parameter is no longer supported, as " +"using :ref:`socket.SO_REUSEADDR ` poses a significant " +"security concern for UDP. Explicitly passing ``reuse_address=True`` will " +"raise an exception." msgstr "" #: library/asyncio-eventloop.rst:617 @@ -864,15 +867,16 @@ msgstr "" #: library/asyncio-eventloop.rst:639 msgid "" -"The socket family will be :py:const:`~socket.AF_UNIX`; socket type will be :" -"py:const:`~socket.SOCK_STREAM`." +"The socket family will be :py:const:`~socket.AF_UNIX`; socket type will " +"be :py:const:`~socket.SOCK_STREAM`." msgstr "" #: library/asyncio-eventloop.rst:644 msgid "" "*path* is the name of a Unix domain socket and is required, unless a *sock* " -"parameter is specified. Abstract Unix sockets, :class:`str`, :class:" -"`bytes`, and :class:`~pathlib.Path` paths are supported." +"parameter is specified. Abstract Unix " +"sockets, :class:`str`, :class:`bytes`, and :class:`~pathlib.Path` paths are " +"supported." msgstr "" #: library/asyncio-eventloop.rst:649 @@ -946,9 +950,10 @@ msgstr "" #: library/asyncio-eventloop.rst:706 msgid "" -"*family* can be set to either :const:`socket.AF_INET` or :const:`~socket." -"AF_INET6` to force the socket to use IPv4 or IPv6. If not set, the *family* " -"will be determined from host name (defaults to :const:`~socket.AF_UNSPEC`)." +"*family* can be set to either :const:`socket.AF_INET` " +"or :const:`~socket.AF_INET6` to force the socket to use IPv4 or IPv6. If not " +"set, the *family* will be determined from host name (defaults " +"to :const:`~socket.AF_UNSPEC`)." msgstr "" #: library/asyncio-eventloop.rst:711 @@ -969,8 +974,8 @@ msgstr "" #: library/asyncio-eventloop.rst:722 msgid "" -"*backlog* is the maximum number of queued connections passed to :meth:" -"`~socket.socket.listen` (defaults to 100)." +"*backlog* is the maximum number of queued connections passed " +"to :meth:`~socket.socket.listen` (defaults to 100)." msgstr "" #: library/asyncio-eventloop.rst:725 @@ -1028,8 +1033,8 @@ msgstr "" #: library/asyncio-eventloop.rst:783 msgid "" -"Similar to :meth:`loop.create_server` but works with the :py:const:`~socket." -"AF_UNIX` socket family." +"Similar to :meth:`loop.create_server` but works with " +"the :py:const:`~socket.AF_UNIX` socket family." msgstr "" #: library/asyncio-eventloop.rst:786 @@ -1158,8 +1163,8 @@ msgstr "" #: library/asyncio-eventloop.rst:907 msgid "" -"*transport* and *protocol* instances that methods like :meth:`~loop." -"create_server` and :meth:`~loop.create_connection` return." +"*transport* and *protocol* instances that methods " +"like :meth:`~loop.create_server` and :meth:`~loop.create_connection` return." msgstr "" #: library/asyncio-eventloop.rst:911 @@ -1224,17 +1229,17 @@ msgstr "" #: library/asyncio-eventloop.rst:970 msgid "" -"In general, protocol implementations that use transport-based APIs such as :" -"meth:`loop.create_connection` and :meth:`loop.create_server` are faster than " -"implementations that work with sockets directly. However, there are some use " -"cases when performance is not critical, and working with :class:`~socket." -"socket` objects directly is more convenient." +"In general, protocol implementations that use transport-based APIs such " +"as :meth:`loop.create_connection` and :meth:`loop.create_server` are faster " +"than implementations that work with sockets directly. However, there are " +"some use cases when performance is not critical, and working " +"with :class:`~socket.socket` objects directly is more convenient." msgstr "" #: library/asyncio-eventloop.rst:979 msgid "" -"Receive up to *nbytes* from *sock*. Asynchronous version of :meth:`socket." -"recv() `." +"Receive up to *nbytes* from *sock*. Asynchronous version " +"of :meth:`socket.recv() `." msgstr "" #: library/asyncio-eventloop.rst:982 @@ -1258,8 +1263,8 @@ msgstr "" #: library/asyncio-eventloop.rst:993 msgid "" -"Receive data from *sock* into the *buf* buffer. Modeled after the blocking :" -"meth:`socket.recv_into() ` method." +"Receive data from *sock* into the *buf* buffer. Modeled after the " +"blocking :meth:`socket.recv_into() ` method." msgstr "" #: library/asyncio-eventloop.rst:996 @@ -1268,8 +1273,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1004 msgid "" -"Receive a datagram of up to *bufsize* from *sock*. Asynchronous version of :" -"meth:`socket.recvfrom() `." +"Receive a datagram of up to *bufsize* from *sock*. Asynchronous version " +"of :meth:`socket.recvfrom() `." msgstr "" #: library/asyncio-eventloop.rst:1007 @@ -1288,8 +1293,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1027 msgid "" -"Send *data* to the *sock* socket. Asynchronous version of :meth:`socket." -"sendall() `." +"Send *data* to the *sock* socket. Asynchronous version " +"of :meth:`socket.sendall() `." msgstr "" #: library/asyncio-eventloop.rst:1030 @@ -1310,8 +1315,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1045 msgid "" -"Send a datagram from *sock* to *address*. Asynchronous version of :meth:" -"`socket.sendto() `." +"Send a datagram from *sock* to *address*. Asynchronous version " +"of :meth:`socket.sendto() `." msgstr "" #: library/asyncio-eventloop.rst:1049 @@ -1330,9 +1335,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1063 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:`loop.getaddrinfo` will be used to resolve the " -"*address*." +"check if the *address* is already resolved by " +"calling :func:`socket.inet_pton`. If not, :meth:`loop.getaddrinfo` will be " +"used to resolve the *address*." msgstr "" #: library/asyncio-eventloop.rst:1072 @@ -1372,8 +1377,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1106 msgid "" -"*sock* must be a non-blocking :const:`socket.SOCK_STREAM` :class:`~socket." -"socket`." +"*sock* must be a non-" +"blocking :const:`socket.SOCK_STREAM` :class:`~socket.socket`." msgstr "" #: library/asyncio-eventloop.rst:1109 @@ -1418,9 +1423,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1150 msgid "" "Both *getaddrinfo* and *getnameinfo* methods were always documented to " -"return a coroutine, but prior to Python 3.7 they were, in fact, returning :" -"class:`asyncio.Future` objects. Starting with Python 3.7 both methods are " -"coroutines." +"return a coroutine, but prior to Python 3.7 they were, in fact, " +"returning :class:`asyncio.Future` objects. Starting with Python 3.7 both " +"methods are coroutines." msgstr "" #: library/asyncio-eventloop.rst:1158 @@ -1437,9 +1442,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1169 msgid "" -"Return pair ``(transport, protocol)``, where *transport* supports the :class:" -"`ReadTransport` interface and *protocol* is an object instantiated by the " -"*protocol_factory*." +"Return pair ``(transport, protocol)``, where *transport* supports " +"the :class:`ReadTransport` interface and *protocol* is an object " +"instantiated by the *protocol_factory*." msgstr "" #: library/asyncio-eventloop.rst:1173 library/asyncio-eventloop.rst:1189 @@ -1458,9 +1463,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1185 msgid "" -"Return pair ``(transport, protocol)``, where *transport* supports :class:" -"`WriteTransport` interface and *protocol* is an object instantiated by the " -"*protocol_factory*." +"Return pair ``(transport, protocol)``, where *transport* " +"supports :class:`WriteTransport` interface and *protocol* is an object " +"instantiated by the *protocol_factory*." msgstr "" #: library/asyncio-eventloop.rst:1194 @@ -1604,14 +1609,14 @@ msgstr "" #: library/asyncio-eventloop.rst:1314 msgid "" "Set *executor* as the default executor used by :meth:`run_in_executor`. " -"*executor* must be an instance of :class:`~concurrent.futures." -"ThreadPoolExecutor`." +"*executor* must be an instance " +"of :class:`~concurrent.futures.ThreadPoolExecutor`." msgstr "" #: library/asyncio-eventloop.rst:1318 msgid "" -"*executor* must be an instance of :class:`~concurrent.futures." -"ThreadPoolExecutor`." +"*executor* must be an instance " +"of :class:`~concurrent.futures.ThreadPoolExecutor`." msgstr "" #: library/asyncio-eventloop.rst:1324 @@ -1637,9 +1642,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1340 msgid "" -"If the handler is called on behalf of a :class:`~asyncio.Task` or :class:" -"`~asyncio.Handle`, it is run in the :class:`contextvars.Context` of that " -"task or callback handle." +"If the handler is called on behalf of a :class:`~asyncio.Task` " +"or :class:`~asyncio.Handle`, it is run in the :class:`contextvars.Context` " +"of that task or callback handle." msgstr "" #: library/asyncio-eventloop.rst:1346 @@ -1667,8 +1672,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1364 msgid "" -"*context* parameter has the same meaning as in :meth:" -"`call_exception_handler`." +"*context* parameter has the same meaning as " +"in :meth:`call_exception_handler`." msgstr "" #: library/asyncio-eventloop.rst:1369 @@ -1737,8 +1742,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1398 msgid "" -"The default value is ``True`` if the environment variable :envvar:" -"`PYTHONASYNCIODEBUG` is set to a non-empty string, ``False`` otherwise." +"The default value is ``True`` if the environment " +"variable :envvar:`PYTHONASYNCIODEBUG` is set to a non-empty string, " +"``False`` otherwise." msgstr "" #: library/asyncio-eventloop.rst:1404 @@ -1780,8 +1786,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1434 msgid "" "On Windows, the default event loop :class:`ProactorEventLoop` supports " -"subprocesses, whereas :class:`SelectorEventLoop` does not. See :ref:" -"`Subprocess Support on Windows ` for details." +"subprocesses, whereas :class:`SelectorEventLoop` does not. " +"See :ref:`Subprocess Support on Windows ` for " +"details." msgstr "" #: library/asyncio-eventloop.rst:1445 @@ -1820,8 +1827,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1464 msgid "" -"The *protocol_factory* must be a callable returning a subclass of the :class:" -"`asyncio.SubprocessProtocol` class." +"The *protocol_factory* must be a callable returning a subclass of " +"the :class:`asyncio.SubprocessProtocol` class." msgstr "" #: library/asyncio-eventloop.rst:1467 @@ -1860,8 +1867,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1477 library/asyncio-eventloop.rst:1487 #: library/asyncio-eventloop.rst:1497 msgid "" -"the :const:`subprocess.DEVNULL` constant which indicates that the special :" -"data:`os.devnull` file will be used" +"the :const:`subprocess.DEVNULL` constant which indicates that the " +"special :data:`os.devnull` file will be used" msgstr "" #: library/asyncio-eventloop.rst:1480 @@ -1895,9 +1902,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1511 msgid "" "If a file-like object passed as *stdin*, *stdout* or *stderr* represents a " -"pipe, then the other side of this pipe should be registered with :meth:" -"`~loop.connect_write_pipe` or :meth:`~loop.connect_read_pipe` for use with " -"the event loop." +"pipe, then the other side of this pipe should be registered " +"with :meth:`~loop.connect_write_pipe` or :meth:`~loop.connect_read_pipe` for " +"use with the event loop." msgstr "" #: library/asyncio-eventloop.rst:1516 @@ -1915,8 +1922,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1527 msgid "" -"Create a subprocess from *cmd*, which can be a :class:`str` or a :class:" -"`bytes` string encoded to the :ref:`filesystem encoding `, using the platform's \"shell\" syntax." msgstr "" @@ -1928,8 +1935,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1535 msgid "" -"The *protocol_factory* must be a callable returning a subclass of the :class:" -"`SubprocessProtocol` class." +"The *protocol_factory* must be a callable returning a subclass of " +"the :class:`SubprocessProtocol` class." msgstr "" #: library/asyncio-eventloop.rst:1538 @@ -1961,8 +1968,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1559 msgid "" -"A callback wrapper object returned by :meth:`loop.call_soon`, :meth:`loop." -"call_soon_threadsafe`." +"A callback wrapper object returned " +"by :meth:`loop.call_soon`, :meth:`loop.call_soon_threadsafe`." msgstr "" #: library/asyncio-eventloop.rst:1564 @@ -1982,8 +1989,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1582 msgid "" -"A callback wrapper object returned by :meth:`loop.call_later`, and :meth:" -"`loop.call_at`." +"A callback wrapper object returned by :meth:`loop.call_later`, " +"and :meth:`loop.call_at`." msgstr "" #: library/asyncio-eventloop.rst:1585 @@ -1996,8 +2003,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1591 msgid "" -"The time is an absolute timestamp, using the same time reference as :meth:" -"`loop.time`." +"The time is an absolute timestamp, using the same time reference " +"as :meth:`loop.time`." msgstr "" #: library/asyncio-eventloop.rst:1598 @@ -2006,9 +2013,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1600 msgid "" -"Server objects are created by :meth:`loop.create_server`, :meth:`loop." -"create_unix_server`, :func:`start_server`, and :func:`start_unix_server` " -"functions." +"Server objects are created " +"by :meth:`loop.create_server`, :meth:`loop.create_unix_server`, :func:`start_server`, " +"and :func:`start_unix_server` functions." msgstr "" #: library/asyncio-eventloop.rst:1604 @@ -2138,8 +2145,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1715 msgid "" -"asyncio ships with two different event loop implementations: :class:" -"`SelectorEventLoop` and :class:`ProactorEventLoop`." +"asyncio ships with two different event loop " +"implementations: :class:`SelectorEventLoop` and :class:`ProactorEventLoop`." msgstr "" #: library/asyncio-eventloop.rst:1718 @@ -2199,9 +2206,10 @@ msgstr "" #: library/asyncio-eventloop.rst:1768 msgid "" "Note that all examples in this section **purposefully** show how to use the " -"low-level event loop APIs, such as :meth:`loop.run_forever` and :meth:`loop." -"call_soon`. Modern asyncio applications rarely need to be written this way; " -"consider using the high-level functions like :func:`asyncio.run`." +"low-level event loop APIs, such as :meth:`loop.run_forever` " +"and :meth:`loop.call_soon`. Modern asyncio applications rarely need to be " +"written this way; consider using the high-level functions " +"like :func:`asyncio.run`." msgstr "" #: library/asyncio-eventloop.rst:1778 @@ -2289,8 +2297,8 @@ msgstr "" #: library/asyncio-eventloop.rst:1850 msgid "" -"Wait until a file descriptor received some data using the :meth:`loop." -"add_reader` method and then close the event loop::" +"Wait until a file descriptor received some data using " +"the :meth:`loop.add_reader` method and then close the event loop::" msgstr "" #: library/asyncio-eventloop.rst:1853 @@ -2351,8 +2359,9 @@ msgstr "" #: library/asyncio-eventloop.rst:1904 msgid "" -"Register handlers for signals :const:`~signal.SIGINT` and :const:`~signal." -"SIGTERM` using the :meth:`loop.add_signal_handler` method::" +"Register handlers for signals :const:`~signal.SIGINT` " +"and :const:`~signal.SIGTERM` using the :meth:`loop.add_signal_handler` " +"method::" msgstr "" #: library/asyncio-eventloop.rst:1907 diff --git a/library/asyncio-extending.po b/library/asyncio-extending.po index 7a1f4cf8e..42890acdb 100644 --- a/library/asyncio-extending.po +++ b/library/asyncio-extending.po @@ -69,8 +69,9 @@ msgstr "" #: library/asyncio-extending.rst:40 msgid "" ":class:`asyncio.Future` and :class:`asyncio.Task` should be never created " -"directly, please use corresponding :meth:`loop.create_future` and :meth:" -"`loop.create_task`, or :func:`asyncio.create_task` factories instead." +"directly, please use corresponding :meth:`loop.create_future` " +"and :meth:`loop.create_task`, or :func:`asyncio.create_task` factories " +"instead." msgstr "" #: library/asyncio-extending.rst:44 @@ -113,8 +114,8 @@ msgstr "" #: library/asyncio-extending.rst:71 msgid "" "A third party task implementation should call the following functions to " -"keep a task visible by :func:`asyncio.all_tasks` and :func:`asyncio." -"current_task`:" +"keep a task visible by :func:`asyncio.all_tasks` " +"and :func:`asyncio.current_task`:" msgstr "" #: library/asyncio-extending.rst:76 @@ -139,8 +140,8 @@ msgstr "" #: library/asyncio-extending.rst:90 msgid "" -"Call the function just before executing a portion of embedded *coroutine* (:" -"meth:`coroutine.send` or :meth:`coroutine.throw`)." +"Call the function just before executing a portion of embedded *coroutine* " +"(:meth:`coroutine.send` or :meth:`coroutine.throw`)." msgstr "" #: library/asyncio-extending.rst:95 @@ -149,6 +150,6 @@ msgstr "" #: library/asyncio-extending.rst:97 msgid "" -"Call the function just after :meth:`coroutine.send` or :meth:`coroutine." -"throw` execution." +"Call the function just after :meth:`coroutine.send` " +"or :meth:`coroutine.throw` execution." msgstr "" diff --git a/library/asyncio-future.po b/library/asyncio-future.po index c3bff5d00..4f7b761f0 100644 --- a/library/asyncio-future.po +++ b/library/asyncio-future.po @@ -64,15 +64,15 @@ msgstr "" #: library/asyncio-future.rst:42 msgid "" -"a :class:`Task` object wrapping *obj*, if *obj* is a coroutine (:func:" -"`iscoroutine` is used for the test); in this case the coroutine will be " -"scheduled by ``ensure_future()``." +"a :class:`Task` object wrapping *obj*, if *obj* is a coroutine " +"(:func:`iscoroutine` is used for the test); in this case the coroutine will " +"be scheduled by ``ensure_future()``." msgstr "" #: library/asyncio-future.rst:47 msgid "" -"a :class:`Task` object that would await on *obj*, if *obj* is an awaitable (:" -"func:`inspect.isawaitable` is used for the test.)" +"a :class:`Task` object that would await on *obj*, if *obj* is an awaitable " +"(:func:`inspect.isawaitable` is used for the test.)" msgstr "" #: library/asyncio-future.rst:50 @@ -103,8 +103,8 @@ msgstr "" #: library/asyncio-future.rst:70 msgid "" -"Wrap a :class:`concurrent.futures.Future` object in a :class:`asyncio." -"Future` object." +"Wrap a :class:`concurrent.futures.Future` object in " +"a :class:`asyncio.Future` object." msgstr "" #: library/asyncio-future.rst:73 @@ -140,9 +140,10 @@ msgstr "" #: library/asyncio-future.rst:96 msgid "" "The rule of thumb is to never expose Future objects in user-facing APIs, and " -"the recommended way to create a Future object is to call :meth:`loop." -"create_future`. This way alternative event loop implementations can inject " -"their own optimized implementations of a Future object." +"the recommended way to create a Future object is to " +"call :meth:`loop.create_future`. This way alternative event loop " +"implementations can inject their own optimized implementations of a Future " +"object." msgstr "" #: library/asyncio-future.rst:102 @@ -167,20 +168,20 @@ msgstr "" #: library/asyncio-future.rst:116 msgid "" -"If the Future is *done* and has an exception set by the :meth:" -"`set_exception` method, this method raises the exception." +"If the Future is *done* and has an exception set by " +"the :meth:`set_exception` method, this method raises the exception." msgstr "" #: library/asyncio-future.rst:207 msgid "" -"If the Future has been *cancelled*, this method raises a :exc:" -"`CancelledError` exception." +"If the Future has been *cancelled*, this method raises " +"a :exc:`CancelledError` exception." msgstr "" #: library/asyncio-future.rst:122 msgid "" -"If the Future's result isn't yet available, this method raises an :exc:" -"`InvalidStateError` exception." +"If the Future's result isn't yet available, this method raises " +"an :exc:`InvalidStateError` exception." msgstr "" #: library/asyncio-future.rst:127 @@ -238,15 +239,15 @@ msgstr "" #: library/asyncio-future.rst:167 msgid "" -"An optional keyword-only *context* argument allows specifying a custom :" -"class:`contextvars.Context` for the *callback* to run in. The current " -"context is used when no *context* is provided." +"An optional keyword-only *context* argument allows specifying a " +"custom :class:`contextvars.Context` for the *callback* to run in. The " +"current context is used when no *context* is provided." msgstr "" #: library/asyncio-future.rst:171 msgid "" -":func:`functools.partial` can be used to pass parameters to the callback, e." -"g.::" +":func:`functools.partial` can be used to pass parameters to the callback, " +"e.g.::" msgstr "" #: library/asyncio-future.rst:174 @@ -299,8 +300,8 @@ msgstr "" #: library/asyncio-future.rst:210 msgid "" -"If the Future isn't *done* yet, this method raises an :exc:" -"`InvalidStateError` exception." +"If the Future isn't *done* yet, this method raises " +"an :exc:`InvalidStateError` exception." msgstr "" #: library/asyncio-future.rst:215 @@ -364,8 +365,8 @@ msgstr "" #: library/asyncio-future.rst:266 msgid "" -":meth:`asyncio.Future.result` and :meth:`asyncio.Future.exception` raise an :" -"exc:`InvalidStateError` exception when the Future is not *done*." +":meth:`asyncio.Future.result` and :meth:`asyncio.Future.exception` raise " +"an :exc:`InvalidStateError` exception when the Future is not *done*." msgstr "" #: library/asyncio-future.rst:270 @@ -382,6 +383,6 @@ msgstr "" #: library/asyncio-future.rst:278 msgid "" -":meth:`asyncio.Future.cancel` accepts an optional ``msg`` argument, but :" -"meth:`concurrent.futures.Future.cancel` does not." +":meth:`asyncio.Future.cancel` accepts an optional ``msg`` argument, " +"but :meth:`concurrent.futures.Future.cancel` does not." msgstr "" diff --git a/library/asyncio-llapi-index.po b/library/asyncio-llapi-index.po index c61892001..b9ea72e06 100644 --- a/library/asyncio-llapi-index.po +++ b/library/asyncio-llapi-index.po @@ -631,8 +631,9 @@ msgstr "" #: library/asyncio-llapi-index.rst:314 msgid "" "Transports that can receive data (TCP and Unix connections, pipes, etc). " -"Returned from methods like :meth:`loop.create_connection`, :meth:`loop." -"create_unix_connection`, :meth:`loop.connect_read_pipe`, etc:" +"Returned from methods " +"like :meth:`loop.create_connection`, :meth:`loop.create_unix_connection`, :meth:`loop.connect_read_pipe`, " +"etc:" msgstr "" #: library/asyncio-llapi-index.rst:319 @@ -666,8 +667,9 @@ msgstr "" #: library/asyncio-llapi-index.rst:334 msgid "" "Transports that can Send data (TCP and Unix connections, pipes, etc). " -"Returned from methods like :meth:`loop.create_connection`, :meth:`loop." -"create_unix_connection`, :meth:`loop.connect_write_pipe`, etc:" +"Returned from methods " +"like :meth:`loop.create_connection`, :meth:`loop.create_unix_connection`, :meth:`loop.connect_write_pipe`, " +"etc:" msgstr "" #: library/asyncio-llapi-index.rst:339 @@ -716,8 +718,8 @@ msgstr "" #: library/asyncio-llapi-index.rst:359 msgid "" -":meth:`transport.get_write_buffer_size() `" +":meth:`transport.get_write_buffer_size() " +"`" msgstr "" #: library/asyncio-llapi-index.rst:361 @@ -726,8 +728,8 @@ msgstr "" #: library/asyncio-llapi-index.rst:363 msgid "" -":meth:`transport.get_write_buffer_limits() `" +":meth:`transport.get_write_buffer_limits() " +"`" msgstr "" #: library/asyncio-llapi-index.rst:365 @@ -736,8 +738,8 @@ msgstr "" #: library/asyncio-llapi-index.rst:367 msgid "" -":meth:`transport.set_write_buffer_limits() `" +":meth:`transport.set_write_buffer_limits() " +"`" msgstr "" #: library/asyncio-llapi-index.rst:369 @@ -766,8 +768,8 @@ msgstr "" #: library/asyncio-llapi-index.rst:386 msgid "" -"Low-level transport abstraction over subprocesses. Returned by :meth:`loop." -"subprocess_exec` and :meth:`loop.subprocess_shell`:" +"Low-level transport abstraction over subprocesses. Returned " +"by :meth:`loop.subprocess_exec` and :meth:`loop.subprocess_shell`:" msgstr "" #: library/asyncio-llapi-index.rst:390 @@ -784,8 +786,8 @@ msgstr "" #: library/asyncio-llapi-index.rst:398 msgid "" -":meth:`transport.get_pipe_transport() `" +":meth:`transport.get_pipe_transport() " +"`" msgstr "" #: library/asyncio-llapi-index.rst:400 @@ -969,9 +971,9 @@ msgstr "" #: library/asyncio-llapi-index.rst:497 msgid "" -"Called when the child process has exited. It can be called before :meth:" -"`~SubprocessProtocol.pipe_data_received` and :meth:`~SubprocessProtocol." -"pipe_connection_lost` methods." +"Called when the child process has exited. It can be called " +"before :meth:`~SubprocessProtocol.pipe_data_received` " +"and :meth:`~SubprocessProtocol.pipe_connection_lost` methods." msgstr "" #: library/asyncio-llapi-index.rst:503 @@ -980,9 +982,9 @@ msgstr "" #: library/asyncio-llapi-index.rst:505 msgid "" -"Policies is a low-level mechanism to alter the behavior of functions like :" -"func:`asyncio.get_event_loop`. See also the main :ref:`policies section " -"` for more details." +"Policies is a low-level mechanism to alter the behavior of functions " +"like :func:`asyncio.get_event_loop`. See also the main :ref:`policies " +"section ` for more details." msgstr "" #: library/asyncio-llapi-index.rst:511 diff --git a/library/asyncio-platforms.po b/library/asyncio-platforms.po index 1491d6401..32033f6d9 100644 --- a/library/asyncio-platforms.po +++ b/library/asyncio-platforms.po @@ -85,15 +85,15 @@ msgstr "" #: library/asyncio-platforms.rst:53 msgid "" -"Pipes are not supported, so the :meth:`loop.connect_read_pipe` and :meth:" -"`loop.connect_write_pipe` methods are not implemented." +"Pipes are not supported, so the :meth:`loop.connect_read_pipe` " +"and :meth:`loop.connect_write_pipe` methods are not implemented." msgstr "" #: library/asyncio-platforms.rst:56 msgid "" -":ref:`Subprocesses ` are not supported, i.e. :meth:`loop." -"subprocess_exec` and :meth:`loop.subprocess_shell` methods are not " -"implemented." +":ref:`Subprocesses ` are not supported, " +"i.e. :meth:`loop.subprocess_exec` and :meth:`loop.subprocess_shell` methods " +"are not implemented." msgstr "" #: library/asyncio-platforms.rst:60 @@ -126,9 +126,10 @@ msgstr "" #: library/asyncio-platforms.rst:80 msgid "" -"The :meth:`policy.set_child_watcher() ` function is also not supported, as :class:" -"`ProactorEventLoop` has a different mechanism to watch child processes." +"The :meth:`policy.set_child_watcher() " +"` function is also not supported, " +"as :class:`ProactorEventLoop` has a different mechanism to watch child " +"processes." msgstr "" #: library/asyncio-platforms.rst:87 @@ -145,11 +146,12 @@ msgstr "" #: library/asyncio-platforms.rst:93 msgid "" -"On macOS 10.6, 10.7 and 10.8, the default event loop uses :class:`selectors." -"KqueueSelector`, which does not support character devices on these " -"versions. The :class:`SelectorEventLoop` can be manually configured to use :" -"class:`~selectors.SelectSelector` or :class:`~selectors.PollSelector` to " -"support character devices on these older versions of macOS. Example::" +"On macOS 10.6, 10.7 and 10.8, the default event loop " +"uses :class:`selectors.KqueueSelector`, which does not support character " +"devices on these versions. The :class:`SelectorEventLoop` can be manually " +"configured to use :class:`~selectors.SelectSelector` " +"or :class:`~selectors.PollSelector` to support character devices on these " +"older versions of macOS. Example::" msgstr "" #: library/asyncio-platforms.rst:100 diff --git a/library/asyncio-policy.po b/library/asyncio-policy.po index 710149670..8d6431858 100644 --- a/library/asyncio-policy.po +++ b/library/asyncio-policy.po @@ -22,12 +22,12 @@ msgstr "" #: library/asyncio-policy.rst:10 msgid "" -"An event loop policy is a global object used to get and set the current :ref:" -"`event loop `, as well as create new event loops. The " -"default policy can be :ref:`replaced ` with :ref:" -"`built-in alternatives ` to use different event loop " -"implementations, or substituted by a :ref:`custom policy ` that can override these behaviors." +"An event loop policy is a global object used to get and set the " +"current :ref:`event loop `, as well as create new event " +"loops. The default policy can be :ref:`replaced ` " +"with :ref:`built-in alternatives ` to use different " +"event loop implementations, or substituted by a :ref:`custom policy ` that can override these behaviors." msgstr "" #: library/asyncio-policy.rst:19 @@ -39,14 +39,15 @@ msgstr "" #: library/asyncio-policy.rst:24 msgid "" -"Custom event loop policies can control the behavior of :func:" -"`get_event_loop`, :func:`set_event_loop`, and :func:`new_event_loop`." +"Custom event loop policies can control the behavior " +"of :func:`get_event_loop`, :func:`set_event_loop`, " +"and :func:`new_event_loop`." msgstr "" #: library/asyncio-policy.rst:27 msgid "" -"Policy objects should implement the APIs defined in the :class:" -"`AbstractEventLoopPolicy` abstract base class." +"Policy objects should implement the APIs defined in " +"the :class:`AbstractEventLoopPolicy` abstract base class." msgstr "" #: library/asyncio-policy.rst:34 @@ -129,8 +130,8 @@ msgstr "" #: library/asyncio-policy.rst:109 msgid "" -"The default asyncio policy. Uses :class:`SelectorEventLoop` on Unix and :" -"class:`ProactorEventLoop` on Windows." +"The default asyncio policy. Uses :class:`SelectorEventLoop` on Unix " +"and :class:`ProactorEventLoop` on Windows." msgstr "" #: library/asyncio-policy.rst:112 @@ -145,8 +146,8 @@ msgstr "" #: library/asyncio-policy.rst:119 msgid "" -"The :meth:`get_event_loop` method of the default asyncio policy now emits a :" -"exc:`DeprecationWarning` if there is no current event loop set and it " +"The :meth:`get_event_loop` method of the default asyncio policy now emits " +"a :exc:`DeprecationWarning` if there is no current event loop set and it " "decides to create one. In some future Python release this will become an " "error." msgstr "" @@ -187,10 +188,10 @@ msgstr "" #: library/asyncio-policy.rst:155 msgid "" "asyncio defines the :class:`AbstractChildWatcher` abstract base class, which " -"child watchers should implement, and has four different implementations: :" -"class:`ThreadedChildWatcher` (configured to be used by default), :class:" -"`MultiLoopChildWatcher`, :class:`SafeChildWatcher`, and :class:" -"`FastChildWatcher`." +"child watchers should implement, and has four different " +"implementations: :class:`ThreadedChildWatcher` (configured to be used by " +"default), :class:`MultiLoopChildWatcher`, :class:`SafeChildWatcher`, " +"and :class:`FastChildWatcher`." msgstr "" #: library/asyncio-policy.rst:161 @@ -212,8 +213,8 @@ msgstr "" #: library/asyncio-policy.rst:175 msgid "" "Set the current child watcher to *watcher* for the current policy. " -"*watcher* must implement methods defined in the :class:" -"`AbstractChildWatcher` base class." +"*watcher* must implement methods defined in " +"the :class:`AbstractChildWatcher` base class." msgstr "" #: library/asyncio-policy.rst:182 @@ -268,8 +269,8 @@ msgstr "" #: library/asyncio-policy.rst:219 msgid "" -"Spawning a subprocess with *inactive* current child watcher raises :exc:" -"`RuntimeError`." +"Spawning a subprocess with *inactive* current child watcher " +"raises :exc:`RuntimeError`." msgstr "" #: library/asyncio-policy.rst:226 @@ -331,9 +332,10 @@ msgstr "" #: library/asyncio-policy.rst:269 msgid "" -"This implementation uses active event loop from the main thread to handle :" -"py:data:`SIGCHLD` signal. If the main thread has no running event loop " -"another thread cannot spawn a subprocess (:exc:`RuntimeError` is raised)." +"This implementation uses active event loop from the main thread to " +"handle :py:data:`SIGCHLD` signal. If the main thread has no running event " +"loop another thread cannot spawn a subprocess (:exc:`RuntimeError` is " +"raised)." msgstr "" #: library/asyncio-policy.rst:276 @@ -345,9 +347,9 @@ msgstr "" #: library/asyncio-policy.rst:283 msgid "" -"This implementation reaps every terminated processes by calling ``os." -"waitpid(-1)`` directly, possibly breaking other code spawning processes and " -"waiting for their termination." +"This implementation reaps every terminated processes by calling " +"``os.waitpid(-1)`` directly, possibly breaking other code spawning processes " +"and waiting for their termination." msgstr "" #: library/asyncio-policy.rst:287 @@ -358,8 +360,8 @@ msgstr "" #: library/asyncio-policy.rst:290 msgid "" -"This solution requires a running event loop in the main thread to work, as :" -"class:`SafeChildWatcher`." +"This solution requires a running event loop in the main thread to work, " +"as :class:`SafeChildWatcher`." msgstr "" #: library/asyncio-policy.rst:297 @@ -379,9 +381,9 @@ msgstr "" #: library/asyncio-policy.rst:313 msgid "" -"To implement a new event loop policy, it is recommended to subclass :class:" -"`DefaultEventLoopPolicy` and override the methods for which custom behavior " -"is wanted, e.g.::" +"To implement a new event loop policy, it is recommended to " +"subclass :class:`DefaultEventLoopPolicy` and override the methods for which " +"custom behavior is wanted, e.g.::" msgstr "" #: library/asyncio-policy.rst:317 diff --git a/library/asyncio-protocol.po b/library/asyncio-protocol.po index 2367a2b61..f3c90dbcf 100644 --- a/library/asyncio-protocol.po +++ b/library/asyncio-protocol.po @@ -75,11 +75,11 @@ msgstr "" #: library/asyncio-protocol.rst:44 msgid "" -"Most of connection oriented event loop methods (such as :meth:`loop." -"create_connection`) usually accept a *protocol_factory* argument used to " -"create a *Protocol* object for an accepted connection, represented by a " -"*Transport* object. Such methods usually return a tuple of ``(transport, " -"protocol)``." +"Most of connection oriented event loop methods (such " +"as :meth:`loop.create_connection`) usually accept a *protocol_factory* " +"argument used to create a *Protocol* object for an accepted connection, " +"represented by a *Transport* object. Such methods usually return a tuple of " +"``(transport, protocol)``." msgstr "" #: library/asyncio-protocol.rst:51 @@ -92,16 +92,16 @@ msgstr "" #: library/asyncio-protocol.rst:54 msgid "" -"The `Transports`_ section documents asyncio :class:`BaseTransport`, :class:" -"`ReadTransport`, :class:`WriteTransport`, :class:`Transport`, :class:" -"`DatagramTransport`, and :class:`SubprocessTransport` classes." +"The `Transports`_ section documents " +"asyncio :class:`BaseTransport`, :class:`ReadTransport`, :class:`WriteTransport`, :class:`Transport`, :class:`DatagramTransport`, " +"and :class:`SubprocessTransport` classes." msgstr "" #: library/asyncio-protocol.rst:59 msgid "" -"The `Protocols`_ section documents asyncio :class:`BaseProtocol`, :class:" -"`Protocol`, :class:`BufferedProtocol`, :class:`DatagramProtocol`, and :class:" -"`SubprocessProtocol` classes." +"The `Protocols`_ section documents " +"asyncio :class:`BaseProtocol`, :class:`Protocol`, :class:`BufferedProtocol`, :class:`DatagramProtocol`, " +"and :class:`SubprocessProtocol` classes." msgstr "" #: library/asyncio-protocol.rst:63 @@ -157,9 +157,9 @@ msgstr "" #: library/asyncio-protocol.rst:100 msgid "" -"Instances of the *WriteTransport* class are returned from the :meth:`loop." -"connect_write_pipe` event loop method and are also used by subprocess-" -"related methods like :meth:`loop.subprocess_exec`." +"Instances of the *WriteTransport* class are returned from " +"the :meth:`loop.connect_write_pipe` event loop method and are also used by " +"subprocess-related methods like :meth:`loop.subprocess_exec`." msgstr "" #: library/asyncio-protocol.rst:107 @@ -168,9 +168,9 @@ msgstr "" #: library/asyncio-protocol.rst:109 msgid "" -"Instances of the *ReadTransport* class are returned from the :meth:`loop." -"connect_read_pipe` event loop method and are also used by subprocess-related " -"methods like :meth:`loop.subprocess_exec`." +"Instances of the *ReadTransport* class are returned from " +"the :meth:`loop.connect_read_pipe` event loop method and are also used by " +"subprocess-related methods like :meth:`loop.subprocess_exec`." msgstr "" #: library/asyncio-protocol.rst:116 @@ -188,8 +188,8 @@ msgstr "" #: library/asyncio-protocol.rst:123 msgid "" "Instances of the *Transport* class are returned from or used by event loop " -"methods like :meth:`loop.create_connection`, :meth:`loop." -"create_unix_connection`, :meth:`loop.create_server`, :meth:`loop.sendfile`, " +"methods " +"like :meth:`loop.create_connection`, :meth:`loop.create_unix_connection`, :meth:`loop.create_server`, :meth:`loop.sendfile`, " "etc." msgstr "" @@ -199,8 +199,8 @@ msgstr "" #: library/asyncio-protocol.rst:133 msgid "" -"Instances of the *DatagramTransport* class are returned from the :meth:`loop." -"create_datagram_endpoint` event loop method." +"Instances of the *DatagramTransport* class are returned from " +"the :meth:`loop.create_datagram_endpoint` event loop method." msgstr "" #: library/asyncio-protocol.rst:139 @@ -286,8 +286,8 @@ msgstr "" #: library/asyncio-protocol.rst:196 msgid "" -"``'sockname'``: the socket's own address, result of :meth:`socket.socket." -"getsockname`" +"``'sockname'``: the socket's own address, result " +"of :meth:`socket.socket.getsockname`" msgstr "" #: library/asyncio-protocol.rst:199 @@ -297,8 +297,8 @@ msgstr "" #: library/asyncio-protocol.rst:201 msgid "" "``'compression'``: the compression algorithm being used as a string, or " -"``None`` if the connection isn't compressed; result of :meth:`ssl.SSLSocket." -"compression`" +"``None`` if the connection isn't compressed; result " +"of :meth:`ssl.SSLSocket.compression`" msgstr "" #: library/asyncio-protocol.rst:205 @@ -400,8 +400,8 @@ msgstr "" #: library/asyncio-protocol.rst:281 msgid "" -"Return :const:`True` if the transport supports :meth:`~WriteTransport." -"write_eof`, :const:`False` if not." +"Return :const:`True` if the transport " +"supports :meth:`~WriteTransport.write_eof`, :const:`False` if not." msgstr "" #: library/asyncio-protocol.rst:286 @@ -424,19 +424,19 @@ msgstr "" #: library/asyncio-protocol.rst:302 msgid "" -"These two values (measured in number of bytes) control when the protocol's :" -"meth:`protocol.pause_writing() ` and :meth:" -"`protocol.resume_writing() ` methods are " -"called. If specified, the low watermark must be less than or equal to the " -"high watermark. Neither *high* nor *low* can be negative." +"These two values (measured in number of bytes) control when the " +"protocol's :meth:`protocol.pause_writing() ` " +"and :meth:`protocol.resume_writing() ` methods " +"are called. If specified, the low watermark must be less than or equal to " +"the high watermark. Neither *high* nor *low* can be negative." msgstr "" #: library/asyncio-protocol.rst:310 msgid "" ":meth:`~BaseProtocol.pause_writing` is called when the buffer size becomes " -"greater than or equal to the *high* value. If writing has been paused, :meth:" -"`~BaseProtocol.resume_writing` is called when the buffer size becomes less " -"than or equal to the *low* value." +"greater than or equal to the *high* value. If writing has been " +"paused, :meth:`~BaseProtocol.resume_writing` is called when the buffer size " +"becomes less than or equal to the *low* value." msgstr "" #: library/asyncio-protocol.rst:315 @@ -445,10 +445,10 @@ msgid "" "given, the low watermark defaults to an implementation-specific value less " "than or equal to the high watermark. Setting *high* to zero forces *low* to " "zero as well, and causes :meth:`~BaseProtocol.pause_writing` to be called " -"whenever the buffer becomes non-empty. Setting *low* to zero causes :meth:" -"`~BaseProtocol.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." +"whenever the buffer becomes non-empty. Setting *low* to zero " +"causes :meth:`~BaseProtocol.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 "" #: library/asyncio-protocol.rst:326 @@ -519,20 +519,20 @@ msgstr "" #: library/asyncio-protocol.rst:388 msgid "" -"``0``: readable streaming transport of the standard input (*stdin*), or :" -"const:`None` if the subprocess was not created with ``stdin=PIPE``" +"``0``: readable streaming transport of the standard input (*stdin*), " +"or :const:`None` if the subprocess was not created with ``stdin=PIPE``" msgstr "" #: library/asyncio-protocol.rst:390 msgid "" -"``1``: writable streaming transport of the standard output (*stdout*), or :" -"const:`None` if the subprocess was not created with ``stdout=PIPE``" +"``1``: writable streaming transport of the standard output (*stdout*), " +"or :const:`None` if the subprocess was not created with ``stdout=PIPE``" msgstr "" #: library/asyncio-protocol.rst:392 msgid "" -"``2``: writable streaming transport of the standard error (*stderr*), or :" -"const:`None` if the subprocess was not created with ``stderr=PIPE``" +"``2``: writable streaming transport of the standard error (*stderr*), " +"or :const:`None` if the subprocess was not created with ``stderr=PIPE``" msgstr "" #: library/asyncio-protocol.rst:394 @@ -562,8 +562,8 @@ msgstr "" #: library/asyncio-protocol.rst:413 msgid "" -"Send the *signal* number to the subprocess, as in :meth:`subprocess.Popen." -"send_signal`." +"Send the *signal* number to the subprocess, as " +"in :meth:`subprocess.Popen.send_signal`." msgstr "" #: library/asyncio-protocol.rst:418 @@ -709,8 +709,9 @@ msgstr "" #: library/asyncio-protocol.rst:524 msgid "" -"If the buffer size equals the high watermark, :meth:`~BaseProtocol." -"pause_writing` is not called: the buffer size must go strictly over." +"If the buffer size equals the high " +"watermark, :meth:`~BaseProtocol.pause_writing` is not called: the buffer " +"size must go strictly over." msgstr "" #: library/asyncio-protocol.rst:528 @@ -726,11 +727,10 @@ msgstr "" #: library/asyncio-protocol.rst:537 msgid "" -"Event methods, such as :meth:`loop.create_server`, :meth:`loop." -"create_unix_server`, :meth:`loop.create_connection`, :meth:`loop." -"create_unix_connection`, :meth:`loop.connect_accepted_socket`, :meth:`loop." -"connect_read_pipe`, and :meth:`loop.connect_write_pipe` accept factories " -"that return streaming protocols." +"Event methods, such " +"as :meth:`loop.create_server`, :meth:`loop.create_unix_server`, :meth:`loop.create_connection`, :meth:`loop.create_unix_connection`, :meth:`loop.connect_accepted_socket`, :meth:`loop.connect_read_pipe`, " +"and :meth:`loop.connect_write_pipe` accept factories that return streaming " +"protocols." msgstr "" #: library/asyncio-protocol.rst:545 @@ -848,17 +848,17 @@ msgstr "" #: library/asyncio-protocol.rst:626 msgid "" -"See the documentation of the :meth:`protocol.eof_received() ` method." +"See the documentation of the :meth:`protocol.eof_received() " +"` method." msgstr "" #: library/asyncio-protocol.rst:630 msgid "" ":meth:`~BufferedProtocol.get_buffer` can be called an arbitrary number of " "times during a connection. However, :meth:`protocol.eof_received() " -"` is called at most once and, if called, :meth:" -"`~BufferedProtocol.get_buffer` and :meth:`~BufferedProtocol.buffer_updated` " -"won't be called after it." +"` is called at most once and, if " +"called, :meth:`~BufferedProtocol.get_buffer` " +"and :meth:`~BufferedProtocol.buffer_updated` won't be called after it." msgstr "" #: library/asyncio-protocol.rst:638 @@ -890,8 +890,8 @@ msgstr "" #: library/asyncio-protocol.rst:662 msgid "" -"Called when a previous send or receive operation raises an :class:" -"`OSError`. *exc* is the :class:`OSError` instance." +"Called when a previous send or receive operation raises " +"an :class:`OSError`. *exc* is the :class:`OSError` instance." msgstr "" #: library/asyncio-protocol.rst:665 @@ -910,10 +910,10 @@ msgstr "" #: library/asyncio-protocol.rst:676 msgid "" -"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." +"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 "" #: library/asyncio-protocol.rst:685 @@ -955,8 +955,8 @@ msgstr "" #: library/asyncio-protocol.rst:711 msgid "" -"It can be called before :meth:`~SubprocessProtocol.pipe_data_received` and :" -"meth:`~SubprocessProtocol.pipe_connection_lost` methods." +"It can be called before :meth:`~SubprocessProtocol.pipe_data_received` " +"and :meth:`~SubprocessProtocol.pipe_connection_lost` methods." msgstr "" #: library/asyncio-protocol.rst:716 @@ -1252,8 +1252,8 @@ msgstr "" #: library/asyncio-protocol.rst:984 msgid "" "The :ref:`watch a file descriptor for read events " -"` example uses the low-level :meth:`loop." -"add_reader` method to register an FD." +"` example uses the low-" +"level :meth:`loop.add_reader` method to register an FD." msgstr "" #: library/asyncio-protocol.rst:988 diff --git a/library/asyncio-queue.po b/library/asyncio-queue.po index ec790f8d4..843e340e6 100644 --- a/library/asyncio-queue.po +++ b/library/asyncio-queue.po @@ -33,8 +33,8 @@ msgstr "" #: library/asyncio-queue.rst:17 msgid "" -"Note that methods of asyncio queues don't have a *timeout* parameter; use :" -"func:`asyncio.wait_for` function to do queue operations with a timeout." +"Note that methods of asyncio queues don't have a *timeout* parameter; " +"use :func:`asyncio.wait_for` function to do queue operations with a timeout." msgstr "" #: library/asyncio-queue.rst:21 @@ -84,8 +84,8 @@ msgstr "" #: library/asyncio-queue.rst:57 msgid "" -"If the queue was initialized with ``maxsize=0`` (the default), then :meth:" -"`full` never returns ``True``." +"If the queue was initialized with ``maxsize=0`` (the default), " +"then :meth:`full` never returns ``True``." msgstr "" #: library/asyncio-queue.rst:62 @@ -106,10 +106,10 @@ msgstr "" #: library/asyncio-queue.rst:74 msgid "" "The count of unfinished tasks goes up whenever an item is added to the " -"queue. The count goes down whenever a consumer coroutine 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." +"queue. The count goes down whenever a consumer coroutine " +"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 "" #: library/asyncio-queue.rst:82 diff --git a/library/asyncio-runner.po b/library/asyncio-runner.po index 7bd8556f5..345a05a7c 100644 --- a/library/asyncio-runner.po +++ b/library/asyncio-runner.po @@ -58,8 +58,8 @@ msgstr "" #: library/asyncio-runner.rst:83 msgid "" "If *debug* is ``True``, the event loop will be run in debug mode. ``False`` " -"disables debug mode explicitly. ``None`` is used to respect the global :ref:" -"`asyncio-debug-mode` settings." +"disables debug mode explicitly. ``None`` is used to respect the " +"global :ref:`asyncio-debug-mode` settings." msgstr "" #: library/asyncio-runner.rst:40 @@ -116,8 +116,8 @@ msgstr "" #: library/asyncio-runner.rst:80 msgid "" -"Sometimes several top-level async functions should be called in the same :" -"ref:`event loop ` and :class:`contextvars.Context`." +"Sometimes several top-level async functions should be called in the " +"same :ref:`event loop ` and :class:`contextvars.Context`." msgstr "" #: library/asyncio-runner.rst:87 @@ -154,9 +154,9 @@ msgstr "" #: library/asyncio-runner.rst:109 msgid "" -"An optional keyword-only *context* argument allows specifying a custom :" -"class:`contextvars.Context` for the *coro* to run in. The runner's default " -"context is used if ``None``." +"An optional keyword-only *context* argument allows specifying a " +"custom :class:`contextvars.Context` for the *coro* to run in. The runner's " +"default context is used if ``None``." msgstr "" #: library/asyncio-runner.rst:118 @@ -191,10 +191,10 @@ msgstr "" #: library/asyncio-runner.rst:141 msgid "" -"When :const:`signal.SIGINT` is raised by :kbd:`Ctrl-C`, :exc:" -"`KeyboardInterrupt` exception is raised in the main thread by default. " -"However this doesn't work with :mod:`asyncio` because it can interrupt " -"asyncio internals and can hang the program from exiting." +"When :const:`signal.SIGINT` is raised by :kbd:`Ctrl-" +"C`, :exc:`KeyboardInterrupt` exception is raised in the main thread by " +"default. However this doesn't work with :mod:`asyncio` because it can " +"interrupt asyncio internals and can hang the program from exiting." msgstr "" #: library/asyncio-runner.rst:146 @@ -222,14 +222,14 @@ msgid "" "handler cancels the main task by calling :meth:`asyncio.Task.cancel` which " "raises :exc:`asyncio.CancelledError` inside the main task. This causes the " "Python stack to unwind, ``try/except`` and ``try/finally`` blocks can be " -"used for resource cleanup. After the main task is cancelled, :meth:`asyncio." -"Runner.run` raises :exc:`KeyboardInterrupt`." +"used for resource cleanup. After the main task is " +"cancelled, :meth:`asyncio.Runner.run` raises :exc:`KeyboardInterrupt`." msgstr "" #: library/asyncio-runner.rst:158 msgid "" -"A user could write a tight loop which cannot be interrupted by :meth:" -"`asyncio.Task.cancel`, in which case the second following :kbd:`Ctrl-C` " -"immediately raises the :exc:`KeyboardInterrupt` without cancelling the main " -"task." +"A user could write a tight loop which cannot be interrupted " +"by :meth:`asyncio.Task.cancel`, in which case the second " +"following :kbd:`Ctrl-C` immediately raises the :exc:`KeyboardInterrupt` " +"without cancelling the main task." msgstr "" diff --git a/library/asyncio-stream.po b/library/asyncio-stream.po index d428e415d..4d9ed1e20 100644 --- a/library/asyncio-stream.po +++ b/library/asyncio-stream.po @@ -79,27 +79,28 @@ msgstr "" #: library/asyncio-stream.rst:61 msgid "" -"The returned *reader* and *writer* objects are instances of :class:" -"`StreamReader` and :class:`StreamWriter` classes." +"The returned *reader* and *writer* objects are instances " +"of :class:`StreamReader` and :class:`StreamWriter` classes." msgstr "" #: library/asyncio-stream.rst:109 msgid "" -"*limit* determines the buffer size limit used by the returned :class:" -"`StreamReader` instance. By default the *limit* is set to 64 KiB." +"*limit* determines the buffer size limit used by the " +"returned :class:`StreamReader` instance. By default the *limit* is set to " +"64 KiB." msgstr "" #: library/asyncio-stream.rst:68 msgid "" -"The rest of the arguments are passed directly to :meth:`loop." -"create_connection`." +"The rest of the arguments are passed directly " +"to :meth:`loop.create_connection`." msgstr "" #: library/asyncio-stream.rst:147 msgid "" -"The *sock* argument transfers ownership of the socket to the :class:" -"`StreamWriter` created. To close the socket, call its :meth:`~asyncio." -"StreamWriter.close` method." +"The *sock* argument transfers ownership of the socket to " +"the :class:`StreamWriter` created. To close the socket, call " +"its :meth:`~asyncio.StreamWriter.close` method." msgstr "" #: library/asyncio-stream.rst:77 @@ -205,14 +206,14 @@ msgstr "" #: library/asyncio-stream.rst:199 msgid "" "Represents a reader object that provides APIs to read data from the IO " -"stream. As an :term:`asynchronous iterable`, the object supports the :" -"keyword:`async for` statement." +"stream. As an :term:`asynchronous iterable`, the object supports " +"the :keyword:`async for` statement." msgstr "" #: library/asyncio-stream.rst:203 msgid "" -"It is not recommended to instantiate *StreamReader* objects directly; use :" -"func:`open_connection` and :func:`start_server` instead." +"It is not recommended to instantiate *StreamReader* objects directly; " +"use :func:`open_connection` and :func:`start_server` instead." msgstr "" #: library/asyncio-stream.rst:209 @@ -281,16 +282,16 @@ msgstr "" #: library/asyncio-stream.rst:254 msgid "" -"If the amount of data read exceeds the configured stream limit, a :exc:" -"`LimitOverrunError` exception is raised, and the data is left in the " +"If the amount of data read exceeds the configured stream limit, " +"a :exc:`LimitOverrunError` exception is raised, and the data is left in the " "internal buffer and can be read again." msgstr "" #: library/asyncio-stream.rst:258 msgid "" -"If EOF is reached before the complete separator is found, an :exc:" -"`IncompleteReadError` exception is raised, and the internal buffer is " -"reset. The :attr:`IncompleteReadError.partial` attribute may contain a " +"If EOF is reached before the complete separator is found, " +"an :exc:`IncompleteReadError` exception is raised, and the internal buffer " +"is reset. The :attr:`IncompleteReadError.partial` attribute may contain a " "portion of the separator." msgstr "" @@ -309,8 +310,8 @@ msgstr "" #: library/asyncio-stream.rst:279 msgid "" -"It is not recommended to instantiate *StreamWriter* objects directly; use :" -"func:`open_connection` and :func:`start_server` instead." +"It is not recommended to instantiate *StreamWriter* objects directly; " +"use :func:`open_connection` and :func:`start_server` instead." msgstr "" #: library/asyncio-stream.rst:285 @@ -376,8 +377,8 @@ msgstr "" #: library/asyncio-stream.rst:332 msgid "" -"Access optional transport information; see :meth:`BaseTransport." -"get_extra_info` for details." +"Access optional transport information; " +"see :meth:`BaseTransport.get_extra_info` for details." msgstr "" #: library/asyncio-stream.rst:337 @@ -395,8 +396,8 @@ msgid "" "This is a flow control method that interacts with the underlying IO write " "buffer. When the size of the buffer reaches the high watermark, *drain()* " "blocks until the size of the buffer is drained down to the low watermark and " -"writing can be resumed. When there is nothing to wait for, the :meth:" -"`drain` returns immediately." +"writing can be resumed. When there is nothing to wait for, " +"the :meth:`drain` returns immediately." msgstr "" #: library/asyncio-stream.rst:353 @@ -462,8 +463,8 @@ msgstr "" #: library/asyncio-stream.rst:426 msgid "" "The :ref:`TCP echo client protocol " -"` example uses the low-level :meth:" -"`loop.create_connection` method." +"` example uses the low-" +"level :meth:`loop.create_connection` method." msgstr "" #: library/asyncio-stream.rst:433 @@ -509,8 +510,8 @@ msgstr "" #: library/asyncio-stream.rst:469 msgid "" "The :ref:`TCP echo server protocol " -"` example uses the :meth:`loop." -"create_server` method." +"` example uses " +"the :meth:`loop.create_server` method." msgstr "" #: library/asyncio-stream.rst:474 @@ -583,8 +584,8 @@ msgstr "" #: library/asyncio-stream.rst:529 msgid "" -"Coroutine waiting until a socket receives data using the :func:" -"`open_connection` function::" +"Coroutine waiting until a socket receives data using " +"the :func:`open_connection` function::" msgstr "" #: library/asyncio-stream.rst:532 @@ -630,6 +631,6 @@ msgstr "" #: library/asyncio-stream.rst:568 msgid "" "The :ref:`watch a file descriptor for read events " -"` example uses the low-level :meth:`loop." -"add_reader` method to watch a file descriptor." +"` example uses the low-" +"level :meth:`loop.add_reader` method to watch a file descriptor." msgstr "" diff --git a/library/asyncio-subprocess.po b/library/asyncio-subprocess.po index 5ff1ef5ab..01b81dfb1 100644 --- a/library/asyncio-subprocess.po +++ b/library/asyncio-subprocess.po @@ -103,8 +103,8 @@ msgstr "" #: library/asyncio-subprocess.rst:69 library/asyncio-subprocess.rst:87 msgid "" "The *limit* argument sets the buffer limit for :class:`StreamReader` " -"wrappers for :attr:`Process.stdout` and :attr:`Process.stderr` (if :const:" -"`subprocess.PIPE` is passed to *stdout* and *stderr* arguments)." +"wrappers for :attr:`Process.stdout` and :attr:`Process.stderr` " +"(if :const:`subprocess.PIPE` is passed to *stdout* and *stderr* arguments)." msgstr "" #: library/asyncio-subprocess.rst:73 library/asyncio-subprocess.rst:91 @@ -148,11 +148,10 @@ msgstr "" #: library/asyncio-subprocess.rst:116 msgid "" -"asyncio also has the following *low-level* APIs to work with subprocesses: :" -"meth:`loop.subprocess_exec`, :meth:`loop.subprocess_shell`, :meth:`loop." -"connect_read_pipe`, :meth:`loop.connect_write_pipe`, as well as the :ref:" -"`Subprocess Transports ` and :ref:`Subprocess " -"Protocols `." +"asyncio also has the following *low-level* APIs to work with " +"subprocesses: :meth:`loop.subprocess_exec`, :meth:`loop.subprocess_shell`, :meth:`loop.connect_read_pipe`, :meth:`loop.connect_write_pipe`, " +"as well as the :ref:`Subprocess Transports ` " +"and :ref:`Subprocess Protocols `." msgstr "" #: library/asyncio-subprocess.rst:124 @@ -165,17 +164,17 @@ msgstr "" #: library/asyncio-subprocess.rst:131 msgid "" -"If *PIPE* is passed to *stdin* argument, the :attr:`Process.stdin ` attribute will point to a :class:`StreamWriter` " -"instance." +"If *PIPE* is passed to *stdin* argument, the :attr:`Process.stdin " +"` attribute will point to " +"a :class:`StreamWriter` instance." msgstr "" #: library/asyncio-subprocess.rst:135 msgid "" -"If *PIPE* is passed to *stdout* or *stderr* arguments, the :attr:`Process." -"stdout ` and :attr:`Process.stderr " -"` attributes will point to :class:" -"`StreamReader` instances." +"If *PIPE* is passed to *stdout* or *stderr* arguments, " +"the :attr:`Process.stdout ` " +"and :attr:`Process.stderr ` attributes " +"will point to :class:`StreamReader` instances." msgstr "" #: library/asyncio-subprocess.rst:143 @@ -187,8 +186,8 @@ msgstr "" #: library/asyncio-subprocess.rst:149 msgid "" "Special value that can be used as the *stdin*, *stdout* or *stderr* argument " -"to process creation functions. It indicates that the special file :data:`os." -"devnull` will be used for the corresponding subprocess stream." +"to process creation functions. It indicates that the special " +"file :data:`os.devnull` will be used for the corresponding subprocess stream." msgstr "" #: library/asyncio-subprocess.rst:155 @@ -205,27 +204,28 @@ msgstr "" #: library/asyncio-subprocess.rst:165 msgid "" -"An object that wraps OS processes created by the :func:" -"`create_subprocess_exec` and :func:`create_subprocess_shell` functions." +"An object that wraps OS processes created by " +"the :func:`create_subprocess_exec` and :func:`create_subprocess_shell` " +"functions." msgstr "" #: library/asyncio-subprocess.rst:169 msgid "" -"This class is designed to have a similar API to the :class:`subprocess." -"Popen` class, but there are some notable differences:" +"This class is designed to have a similar API to " +"the :class:`subprocess.Popen` class, but there are some notable differences:" msgstr "" #: library/asyncio-subprocess.rst:173 msgid "" -"unlike Popen, Process instances do not have an equivalent to the :meth:" -"`~subprocess.Popen.poll` method;" +"unlike Popen, Process instances do not have an equivalent to " +"the :meth:`~subprocess.Popen.poll` method;" msgstr "" #: library/asyncio-subprocess.rst:176 msgid "" -"the :meth:`~asyncio.subprocess.Process.communicate` and :meth:`~asyncio." -"subprocess.Process.wait` methods don't have a *timeout* parameter: use the :" -"func:`~asyncio.wait_for` function;" +"the :meth:`~asyncio.subprocess.Process.communicate` " +"and :meth:`~asyncio.subprocess.Process.wait` methods don't have a *timeout* " +"parameter: use the :func:`~asyncio.wait_for` function;" msgstr "" #: library/asyncio-subprocess.rst:180 @@ -429,8 +429,8 @@ msgstr "" #: library/asyncio-subprocess.rst:319 msgid "" -"On UNIX *child watchers* are used for subprocess finish waiting, see :ref:" -"`asyncio-watchers` for more info." +"On UNIX *child watchers* are used for subprocess finish waiting, " +"see :ref:`asyncio-watchers` for more info." msgstr "" #: library/asyncio-subprocess.rst:325 @@ -441,8 +441,8 @@ msgstr "" #: library/asyncio-subprocess.rst:328 msgid "" -"Spawning a subprocess with *inactive* current child watcher raises :exc:" -"`RuntimeError`." +"Spawning a subprocess with *inactive* current child watcher " +"raises :exc:`RuntimeError`." msgstr "" #: library/asyncio-subprocess.rst:331 diff --git a/library/asyncio-sync.po b/library/asyncio-sync.po index 5a4b50d58..56b4d34cf 100644 --- a/library/asyncio-sync.po +++ b/library/asyncio-sync.po @@ -173,8 +173,8 @@ msgstr "" #: library/asyncio-sync.rst:107 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:`clear` " +"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:`clear` " "method. The :meth:`~Event.wait` method blocks until the flag is set to " "*true*. The flag is set to *false* initially." msgstr "" @@ -231,8 +231,8 @@ msgstr "" #: library/asyncio-sync.rst:158 msgid "" -"Tasks awaiting on :meth:`~Event.wait` will now block until the :meth:`~Event." -"set` method is called again." +"Tasks awaiting on :meth:`~Event.wait` will now block until " +"the :meth:`~Event.set` method is called again." msgstr "" #: library/asyncio-sync.rst:163 @@ -255,11 +255,11 @@ msgstr "" #: library/asyncio-sync.rst:177 msgid "" -"In essence, a Condition object combines the functionality of an :class:" -"`Event` and a :class:`Lock`. It is possible to have multiple Condition " -"objects share one Lock, which allows coordinating exclusive access to a " -"shared resource between different tasks interested in particular states of " -"that shared resource." +"In essence, a Condition object combines the functionality of " +"an :class:`Event` and a :class:`Lock`. It is possible to have multiple " +"Condition objects share one Lock, which allows coordinating exclusive access " +"to a shared resource between different tasks interested in particular states " +"of that shared resource." msgstr "" #: library/asyncio-sync.rst:183 @@ -343,8 +343,8 @@ msgstr "" #: library/asyncio-sync.rst:252 msgid "" -"If the calling task has not acquired the lock when this method is called, a :" -"exc:`RuntimeError` is raised." +"If the calling task has not acquired the lock when this method is called, " +"a :exc:`RuntimeError` is raised." msgstr "" #: library/asyncio-sync.rst:255 @@ -374,17 +374,17 @@ msgstr "" #: library/asyncio-sync.rst:276 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 task calls :meth:`release`." +"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 task calls :meth:`release`." msgstr "" #: library/asyncio-sync.rst:282 msgid "" "The optional *value* argument gives the initial value for the internal " -"counter (``1`` by default). If the given value is less than ``0`` a :exc:" -"`ValueError` is raised." +"counter (``1`` by default). If the given value is less than ``0`` " +"a :exc:`ValueError` is raised." msgstr "" #: library/asyncio-sync.rst:289 @@ -450,9 +450,9 @@ msgstr "" #: library/asyncio-sync.rst:337 msgid "" -"Bounded Semaphore is a version of :class:`Semaphore` that raises a :exc:" -"`ValueError` in :meth:`~Semaphore.release` if it increases the internal " -"counter above the initial *value*." +"Bounded Semaphore is a version of :class:`Semaphore` that raises " +"a :exc:`ValueError` in :meth:`~Semaphore.release` if it increases the " +"internal counter above the initial *value*." msgstr "" #: library/asyncio-sync.rst:346 @@ -466,16 +466,16 @@ msgstr "" #: library/asyncio-sync.rst:352 msgid "" "A barrier is a simple synchronization primitive that allows to block until " -"*parties* number of tasks are waiting on it. Tasks can wait on the :meth:" -"`~Barrier.wait` method and would be blocked until the specified number of " -"tasks end up waiting on :meth:`~Barrier.wait`. At that point all of the " -"waiting tasks would unblock simultaneously." +"*parties* number of tasks are waiting on it. Tasks can wait on " +"the :meth:`~Barrier.wait` method and would be blocked until the specified " +"number of tasks end up waiting on :meth:`~Barrier.wait`. At that point all " +"of the waiting tasks would unblock simultaneously." msgstr "" #: library/asyncio-sync.rst:358 msgid "" -":keyword:`async with` can be used as an alternative to awaiting on :meth:" -"`~Barrier.wait`." +":keyword:`async with` can be used as an alternative to awaiting " +"on :meth:`~Barrier.wait`." msgstr "" #: library/asyncio-sync.rst:361 @@ -550,8 +550,8 @@ msgstr "" #: library/asyncio-sync.rst:417 msgid "" "This method may raise a :class:`BrokenBarrierError` exception if the barrier " -"is broken or reset while a task is waiting. It could raise a :exc:" -"`CancelledError` if a task is cancelled." +"is broken or reset while a task is waiting. It could raise " +"a :exc:`CancelledError` if a task is cancelled." msgstr "" #: library/asyncio-sync.rst:423 @@ -587,13 +587,13 @@ msgstr "" #: library/asyncio-sync.rst:450 msgid "" -"This exception, a subclass of :exc:`RuntimeError`, is raised when the :class:" -"`Barrier` object is reset or broken." +"This exception, a subclass of :exc:`RuntimeError`, is raised when " +"the :class:`Barrier` object is reset or broken." msgstr "" #: library/asyncio-sync.rst:458 msgid "" -"Acquiring a lock using ``await lock`` or ``yield from lock`` and/or :keyword:" -"`with` statement (``with await lock``, ``with (yield from lock)``) was " -"removed. Use ``async with lock`` instead." +"Acquiring a lock using ``await lock`` or ``yield from lock`` and/" +"or :keyword:`with` statement (``with await lock``, ``with (yield from " +"lock)``) was removed. Use ``async with lock`` instead." msgstr "" diff --git a/library/asyncio-task.po b/library/asyncio-task.po index 99a80e741..b4799133d 100644 --- a/library/asyncio-task.po +++ b/library/asyncio-task.po @@ -162,8 +162,8 @@ msgstr "" #: library/asyncio-task.rst:110 msgid "" -"The :class:`asyncio.TaskGroup` class provides a more modern alternative to :" -"func:`create_task`. Using this API, the last example becomes::" +"The :class:`asyncio.TaskGroup` class provides a more modern alternative " +"to :func:`create_task`. Using this API, the last example becomes::" msgstr "" #: library/asyncio-task.rst:114 @@ -197,8 +197,8 @@ msgstr "" #: library/asyncio-task.rst:139 msgid "" -"We say that an object is an **awaitable** object if it can be used in an :" -"keyword:`await` expression. Many asyncio APIs are designed to accept " +"We say that an object is an **awaitable** object if it can be used in " +"an :keyword:`await` expression. Many asyncio APIs are designed to accept " "awaitables." msgstr "" @@ -258,8 +258,9 @@ msgstr "" #: library/asyncio-task.rst:183 msgid "" -"When a coroutine is wrapped into a *Task* with functions like :func:`asyncio." -"create_task` the coroutine is automatically scheduled to run soon::" +"When a coroutine is wrapped into a *Task* with functions " +"like :func:`asyncio.create_task` the coroutine is automatically scheduled to " +"run soon::" msgstr "" #: library/asyncio-task.rst:187 @@ -329,8 +330,8 @@ msgstr "" #: library/asyncio-task.rst:230 msgid "" -"A good example of a low-level function that returns a Future object is :meth:" -"`loop.run_in_executor`." +"A good example of a low-level function that returns a Future object " +"is :meth:`loop.run_in_executor`." msgstr "" #: library/asyncio-task.rst:235 @@ -349,21 +350,22 @@ msgstr "" #: library/asyncio-task.rst:246 msgid "" -"If *name* is not ``None``, it is set as the name of the task using :meth:" -"`Task.set_name`." +"If *name* is not ``None``, it is set as the name of the task " +"using :meth:`Task.set_name`." msgstr "" #: library/asyncio-task.rst:249 msgid "" -"An optional keyword-only *context* argument allows specifying a custom :" -"class:`contextvars.Context` for the *coro* to run in. The current context " -"copy is created when no *context* is provided." +"An optional keyword-only *context* argument allows specifying a " +"custom :class:`contextvars.Context` for the *coro* to run in. The current " +"context copy is created when no *context* is provided." msgstr "" #: library/asyncio-task.rst:253 msgid "" -"The task is executed in the loop returned by :func:`get_running_loop`, :exc:" -"`RuntimeError` is raised if there is no running loop in current thread." +"The task is executed in the loop returned " +"by :func:`get_running_loop`, :exc:`RuntimeError` is raised if there is no " +"running loop in current thread." msgstr "" #: library/asyncio-task.rst:259 @@ -412,28 +414,30 @@ msgstr "" #: library/asyncio-task.rst:297 msgid "" -"Tasks can easily and safely be cancelled. When a task is cancelled, :exc:" -"`asyncio.CancelledError` will be raised in the task at the next opportunity." +"Tasks can easily and safely be cancelled. When a task is " +"cancelled, :exc:`asyncio.CancelledError` will be raised in the task at the " +"next opportunity." msgstr "" #: library/asyncio-task.rst:301 msgid "" "It is recommended that coroutines use ``try/finally`` blocks to robustly " "perform clean-up logic. In case :exc:`asyncio.CancelledError` is explicitly " -"caught, it should generally be propagated when clean-up is complete. :exc:" -"`asyncio.CancelledError` directly subclasses :exc:`BaseException` so most " -"code will not need to be aware of it." +"caught, it should generally be propagated when clean-up is " +"complete. :exc:`asyncio.CancelledError` directly " +"subclasses :exc:`BaseException` so most code will not need to be aware of it." msgstr "" #: library/asyncio-task.rst:307 msgid "" -"The asyncio components that enable structured concurrency, like :class:" -"`asyncio.TaskGroup` and :func:`asyncio.timeout`, are implemented using " -"cancellation internally and might misbehave if a coroutine swallows :exc:" -"`asyncio.CancelledError`. Similarly, user code should not generally call :" -"meth:`uncancel `. However, in cases when suppressing :" -"exc:`asyncio.CancelledError` is truly desired, it is necessary to also call " -"``uncancel()`` to completely remove the cancellation state." +"The asyncio components that enable structured concurrency, " +"like :class:`asyncio.TaskGroup` and :func:`asyncio.timeout`, are implemented " +"using cancellation internally and might misbehave if a coroutine " +"swallows :exc:`asyncio.CancelledError`. Similarly, user code should not " +"generally call :meth:`uncancel `. However, in cases " +"when suppressing :exc:`asyncio.CancelledError` is truly desired, it is " +"necessary to also call ``uncancel()`` to completely remove the cancellation " +"state." msgstr "" #: library/asyncio-task.rst:319 @@ -455,8 +459,8 @@ msgstr "" #: library/asyncio-task.rst:335 msgid "" -"Create a task in this task group. The signature matches that of :func:" -"`asyncio.create_task`." +"Create a task in this task group. The signature matches that " +"of :func:`asyncio.create_task`." msgstr "" #: library/asyncio-task.rst:519 library/asyncio-task.rst:750 @@ -470,8 +474,8 @@ msgid "" " async with asyncio.TaskGroup() as tg:\n" " task1 = tg.create_task(some_coro(...))\n" " task2 = tg.create_task(another_coro(...))\n" -" print(f\"Both tasks have completed now: {task1.result()}, {task2." -"result()}\")" +" print(f\"Both tasks have completed now: {task1.result()}, " +"{task2.result()}\")" msgstr "" #: library/asyncio-task.rst:346 @@ -488,11 +492,11 @@ msgid "" "The first time any of the tasks belonging to the group fails with an " "exception other than :exc:`asyncio.CancelledError`, the remaining tasks in " "the group are cancelled. No further tasks can then be added to the group. At " -"this point, if the body of the ``async with`` statement is still active (i." -"e., :meth:`~object.__aexit__` hasn't been called yet), the task directly " -"containing the ``async with`` statement is also cancelled. The resulting :" -"exc:`asyncio.CancelledError` will interrupt an ``await``, but it will not " -"bubble out of the containing ``async with`` statement." +"this point, if the body of the ``async with`` statement is still active " +"(i.e., :meth:`~object.__aexit__` hasn't been called yet), the task directly " +"containing the ``async with`` statement is also cancelled. The " +"resulting :exc:`asyncio.CancelledError` will interrupt an ``await``, but it " +"will not bubble out of the containing ``async with`` statement." msgstr "" #: library/asyncio-task.rst:363 @@ -505,23 +509,24 @@ msgstr "" #: library/asyncio-task.rst:370 msgid "" -"Two base exceptions are treated specially: If any task fails with :exc:" -"`KeyboardInterrupt` or :exc:`SystemExit`, the task group still cancels the " -"remaining tasks and waits for them, but then the initial :exc:" -"`KeyboardInterrupt` or :exc:`SystemExit` is re-raised instead of :exc:" -"`ExceptionGroup` or :exc:`BaseExceptionGroup`." +"Two base exceptions are treated specially: If any task fails " +"with :exc:`KeyboardInterrupt` or :exc:`SystemExit`, the task group still " +"cancels the remaining tasks and waits for them, but then the " +"initial :exc:`KeyboardInterrupt` or :exc:`SystemExit` is re-raised instead " +"of :exc:`ExceptionGroup` or :exc:`BaseExceptionGroup`." msgstr "" #: library/asyncio-task.rst:376 msgid "" -"If the body of the ``async with`` statement exits with an exception (so :" -"meth:`~object.__aexit__` is called with an exception set), this is treated " -"the same as if one of the tasks failed: the remaining tasks are cancelled " -"and then waited for, and non-cancellation exceptions are grouped into an " -"exception group and raised. The exception passed into :meth:`~object." -"__aexit__`, unless it is :exc:`asyncio.CancelledError`, is also included in " -"the exception group. The same special case is made for :exc:" -"`KeyboardInterrupt` and :exc:`SystemExit` as in the previous paragraph." +"If the body of the ``async with`` statement exits with an exception " +"(so :meth:`~object.__aexit__` is called with an exception set), this is " +"treated the same as if one of the tasks failed: the remaining tasks are " +"cancelled and then waited for, and non-cancellation exceptions are grouped " +"into an exception group and raised. The exception passed " +"into :meth:`~object.__aexit__`, unless it is :exc:`asyncio.CancelledError`, " +"is also included in the exception group. The same special case is made " +"for :exc:`KeyboardInterrupt` and :exc:`SystemExit` as in the previous " +"paragraph." msgstr "" #: library/asyncio-task.rst:390 @@ -764,12 +769,12 @@ msgstr "" #: library/asyncio-task.rst:586 msgid "" -"When using this factory (via :meth:`loop.set_task_factory(asyncio." -"eager_task_factory) `), coroutines begin execution " -"synchronously during :class:`Task` construction. Tasks are only scheduled on " -"the event loop if they block. This can be a performance improvement as the " -"overhead of loop scheduling is avoided for coroutines that complete " -"synchronously." +"When using this factory " +"(via :meth:`loop.set_task_factory(asyncio.eager_task_factory) " +"`), coroutines begin execution synchronously " +"during :class:`Task` construction. Tasks are only scheduled on the event " +"loop if they block. This can be a performance improvement as the overhead of " +"loop scheduling is avoided for coroutines that complete synchronously." msgstr "" #: library/asyncio-task.rst:592 @@ -797,15 +802,15 @@ msgstr "" #: library/asyncio-task.rst:612 msgid "" "*custom_task_constructor* must be a *callable* with the signature matching " -"the signature of :class:`Task.__init__ `. The callable must return a :" -"class:`asyncio.Task`-compatible object." +"the signature of :class:`Task.__init__ `. The callable must return " +"a :class:`asyncio.Task`-compatible object." msgstr "" #: library/asyncio-task.rst:616 msgid "" "This function returns a *callable* intended to be used as a task factory of " -"an event loop via :meth:`loop.set_task_factory(factory) `)." +"an event loop via :meth:`loop.set_task_factory(factory) " +"`)." msgstr "" #: library/asyncio-task.rst:623 @@ -814,8 +819,8 @@ msgstr "" #: library/asyncio-task.rst:627 msgid "" -"Protect an :ref:`awaitable object ` from being :meth:" -"`cancelled `." +"Protect an :ref:`awaitable object ` from " +"being :meth:`cancelled `." msgstr "" #: library/asyncio-task.rst:796 @@ -845,8 +850,8 @@ 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. Although its caller is " -"still cancelled, so the \"await\" expression still raises a :exc:" -"`CancelledError`." +"still cancelled, so the \"await\" expression still raises " +"a :exc:`CancelledError`." msgstr "" #: library/asyncio-task.rst:647 @@ -904,8 +909,8 @@ msgstr "" #: library/asyncio-task.rst:689 msgid "" -"In either case, the context manager can be rescheduled after creation using :" -"meth:`Timeout.reschedule`." +"In either case, the context manager can be rescheduled after creation " +"using :meth:`Timeout.reschedule`." msgstr "" #: library/asyncio-task.rst:694 @@ -918,16 +923,16 @@ msgstr "" #: library/asyncio-task.rst:698 msgid "" "If ``long_running_task`` takes more than 10 seconds to complete, the context " -"manager will cancel the current task and handle the resulting :exc:`asyncio." -"CancelledError` internally, transforming it into a :exc:`TimeoutError` which " -"can be caught and handled." +"manager will cancel the current task and handle the " +"resulting :exc:`asyncio.CancelledError` internally, transforming it into " +"a :exc:`TimeoutError` which can be caught and handled." msgstr "" #: library/asyncio-task.rst:705 msgid "" -"The :func:`asyncio.timeout` context manager is what transforms the :exc:" -"`asyncio.CancelledError` into a :exc:`TimeoutError`, which means the :exc:" -"`TimeoutError` can only be caught *outside* of the context manager." +"The :func:`asyncio.timeout` context manager is what transforms " +"the :exc:`asyncio.CancelledError` into a :exc:`TimeoutError`, which means " +"the :exc:`TimeoutError` can only be caught *outside* of the context manager." msgstr "" #: library/asyncio-task.rst:710 @@ -1048,8 +1053,8 @@ msgstr "" #: library/asyncio-task.rst:805 msgid "" -"To avoid the task :meth:`cancellation `, wrap it in :func:" -"`shield`." +"To avoid the task :meth:`cancellation `, wrap it " +"in :func:`shield`." msgstr "" #: library/asyncio-task.rst:808 @@ -1155,8 +1160,8 @@ msgstr "" #: library/asyncio-task.rst:885 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`." +"If no future raises an exception then it is equivalent " +"to :const:`ALL_COMPLETED`." msgstr "" #: library/asyncio-task.rst:890 @@ -1412,22 +1417,22 @@ msgstr "" #: library/asyncio-task.rst:1098 msgid "" ":meth:`cancelled` can be used to check if the Task was cancelled. The method " -"returns ``True`` if the wrapped coroutine did not suppress the :exc:" -"`CancelledError` exception and was actually cancelled." +"returns ``True`` if the wrapped coroutine did not suppress " +"the :exc:`CancelledError` exception and was actually cancelled." msgstr "" #: library/asyncio-task.rst:1103 msgid "" -":class:`asyncio.Task` inherits from :class:`Future` all of its APIs except :" -"meth:`Future.set_result` and :meth:`Future.set_exception`." +":class:`asyncio.Task` inherits from :class:`Future` all of its APIs " +"except :meth:`Future.set_result` and :meth:`Future.set_exception`." msgstr "" #: library/asyncio-task.rst:1107 msgid "" -"An optional keyword-only *context* argument allows specifying a custom :" -"class:`contextvars.Context` for the *coro* to run in. If no *context* is " -"provided, the Task copies the current context and later runs its coroutine " -"in the copied context." +"An optional keyword-only *context* argument allows specifying a " +"custom :class:`contextvars.Context` for the *coro* to run in. If no " +"*context* is provided, the Task copies the current context and later runs " +"its coroutine in the copied context." msgstr "" #: library/asyncio-task.rst:1112 @@ -1482,8 +1487,8 @@ msgstr "" #: library/asyncio-task.rst:1153 msgid "" -"If the Task's result isn't yet available, this method raises an :exc:" -"`InvalidStateError` exception." +"If the Task's result isn't yet available, this method raises " +"an :exc:`InvalidStateError` exception." msgstr "" #: library/asyncio-task.rst:1158 @@ -1614,8 +1619,8 @@ msgstr "" #: library/asyncio-task.rst:1260 msgid "" -"In the default Task implementation, the name will be visible in the :func:" -"`repr` output of a task object." +"In the default Task implementation, the name will be visible in " +"the :func:`repr` output of a task object." msgstr "" #: library/asyncio-task.rst:1267 @@ -1632,12 +1637,12 @@ msgstr "" msgid "" "The coroutine then has a chance to clean up or even deny the request by " "suppressing the exception with a :keyword:`try` ... ... ``except " -"CancelledError`` ... :keyword:`finally` block. Therefore, unlike :meth:" -"`Future.cancel`, :meth:`Task.cancel` does not guarantee that the Task will " -"be cancelled, although suppressing cancellation completely is not common and " -"is actively discouraged. Should the coroutine nevertheless decide to " -"suppress the cancellation, it needs to call :meth:`Task.uncancel` in " -"addition to catching the exception." +"CancelledError`` ... :keyword:`finally` block. Therefore, " +"unlike :meth:`Future.cancel`, :meth:`Task.cancel` does not guarantee that " +"the Task will be cancelled, although suppressing cancellation completely is " +"not common and is actively discouraged. Should the coroutine nevertheless " +"decide to suppress the cancellation, it needs to call :meth:`Task.uncancel` " +"in addition to catching the exception." msgstr "" #: library/asyncio-task.rst:1282 @@ -1697,9 +1702,9 @@ msgstr "" #: library/asyncio-task.rst:1331 msgid "" -"The Task is *cancelled* when the cancellation was requested with :meth:" -"`cancel` and the wrapped coroutine propagated the :exc:`CancelledError` " -"exception thrown into it." +"The Task is *cancelled* when the cancellation was requested " +"with :meth:`cancel` and the wrapped coroutine propagated " +"the :exc:`CancelledError` exception thrown into it." msgstr "" #: library/asyncio-task.rst:1337 @@ -1712,17 +1717,17 @@ msgstr "" #: library/asyncio-task.rst:1341 msgid "" -"Note that once execution of a cancelled task completed, further calls to :" -"meth:`uncancel` are ineffective." +"Note that once execution of a cancelled task completed, further calls " +"to :meth:`uncancel` are ineffective." msgstr "" #: library/asyncio-task.rst:1346 msgid "" "This method is used by asyncio's internals and isn't expected to be used by " "end-user code. In particular, if a Task gets successfully uncancelled, this " -"allows for elements of structured concurrency like :ref:`taskgroups` and :" -"func:`asyncio.timeout` to continue running, isolating cancellation to the " -"respective structured block. For example::" +"allows for elements of structured concurrency like :ref:`taskgroups` " +"and :func:`asyncio.timeout` to continue running, isolating cancellation to " +"the respective structured block. For example::" msgstr "" #: library/asyncio-task.rst:1353 @@ -1743,15 +1748,15 @@ msgstr "" msgid "" "While the block with ``make_request()`` and ``make_another_request()`` might " "get cancelled due to the timeout, ``unrelated_code()`` should continue " -"running even in case of the timeout. This is implemented with :meth:" -"`uncancel`. :class:`TaskGroup` context managers use :func:`uncancel` in a " -"similar fashion." +"running even in case of the timeout. This is implemented " +"with :meth:`uncancel`. :class:`TaskGroup` context managers " +"use :func:`uncancel` in a similar fashion." msgstr "" #: library/asyncio-task.rst:1370 msgid "" -"If end-user code is, for some reason, suppressing cancellation by catching :" -"exc:`CancelledError`, it needs to call this method to remove the " +"If end-user code is, for some reason, suppressing cancellation by " +"catching :exc:`CancelledError`, it needs to call this method to remove the " "cancellation state." msgstr "" diff --git a/library/asyncio.po b/library/asyncio.po index 005134867..3ec1615bf 100644 --- a/library/asyncio.po +++ b/library/asyncio.po @@ -114,9 +114,9 @@ msgstr "" #: library/asyncio.rst:48 msgid "" "create and manage :ref:`event loops `, which provide " -"asynchronous APIs for :ref:`networking `, running :ref:" -"`subprocesses `, handling :ref:`OS signals " -"`, etc;" +"asynchronous APIs for :ref:`networking `, " +"running :ref:`subprocesses `, handling :ref:`OS " +"signals `, etc;" msgstr "" ":ref:`ağ `, :ref:`alt işlemler ` " "çalıştırmak, :ref:`işletim sistemi sinyallerini ` " diff --git a/library/atexit.po b/library/atexit.po index 2764901c7..e377c4742 100644 --- a/library/atexit.po +++ b/library/atexit.po @@ -52,9 +52,9 @@ msgstr "" #: library/atexit.rst:32 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." +"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 "" #: library/atexit.rst:37 @@ -96,12 +96,13 @@ msgstr "" #: library/atexit.rst:64 msgid "" -"Remove *func* from the list of functions to be run at interpreter shutdown. :" -"func:`unregister` silently does nothing if *func* was not previously " -"registered. If *func* has been registered more than once, every occurrence " -"of that function in the :mod:`atexit` call stack will be removed. Equality " -"comparisons (``==``) are used internally during unregistration, so function " -"references do not need to have matching identities." +"Remove *func* from the list of functions to be run at interpreter " +"shutdown. :func:`unregister` silently does nothing if *func* was not " +"previously registered. If *func* has been registered more than once, every " +"occurrence of that function in the :mod:`atexit` call stack will be " +"removed. Equality comparisons (``==``) are used internally during " +"unregistration, so function references do not need to have matching " +"identities." msgstr "" #: library/atexit.rst:74 diff --git a/library/audioop.po b/library/audioop.po index 79419718a..cd68ad9c8 100644 --- a/library/audioop.po +++ b/library/audioop.po @@ -37,8 +37,9 @@ msgstr "" #: library/audioop.rst:19 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." +"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 "" #: library/audioop.rst:30 diff --git a/library/audit_events.po b/library/audit_events.po index 6efc3cbf0..0f62572e9 100644 --- a/library/audit_events.po +++ b/library/audit_events.po @@ -22,9 +22,9 @@ msgstr "" #: library/audit_events.rst:8 msgid "" -"This table contains all events raised by :func:`sys.audit` or :c:func:" -"`PySys_Audit` calls throughout the CPython runtime and the standard " -"library. These calls were added in 3.8 or later (see :pep:`578`)." +"This table contains all events raised by :func:`sys.audit` " +"or :c:func:`PySys_Audit` calls throughout the CPython runtime and the " +"standard library. These calls were added in 3.8 or later (see :pep:`578`)." msgstr "" #: library/audit_events.rst:12 diff --git a/library/base64.po b/library/base64.po index 8eb17d061..7293c9967 100644 --- a/library/base64.po +++ b/library/base64.po @@ -37,17 +37,18 @@ msgstr "" msgid "" "The :rfc:`4648` encodings are suitable for encoding binary data so that it " "can be 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." +"an HTTP POST request. The encoding algorithm is not the same as " +"the :program:`uuencode` program." msgstr "" #: 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:`4648` (normal, and URL- and filesystem-safe) are supported." +"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:`4648` (normal, and URL- and filesystem-safe) are " +"supported." msgstr "" #: library/base64.rst:33 @@ -56,8 +57,8 @@ msgid "" "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." +"looking for :rfc:`2045` support you probably want to be looking at " +"the :mod:`email` package instead." msgstr "" #: library/base64.rst:41 @@ -127,8 +128,8 @@ msgstr "" #: library/base64.rst:83 msgid "" -"For more information about the strict base64 check, see :func:`binascii." -"a2b_base64`" +"For more information about the strict base64 check, " +"see :func:`binascii.a2b_base64`" msgstr "" #: library/base64.rst:85 @@ -160,8 +161,8 @@ msgstr "" 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`." +"instead of ``/`` in the standard Base64 alphabet, and return the " +"decoded :class:`bytes`." msgstr "" #: library/base64.rst:119 @@ -330,11 +331,12 @@ msgstr "" #: library/base64.rst:267 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)." +"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 "" #: library/base64.rst:277 diff --git a/library/bdb.po b/library/bdb.po index 4aa8bbcd4..ffaadcc95 100644 --- a/library/bdb.po +++ b/library/bdb.po @@ -59,10 +59,10 @@ msgstr "" #: library/bdb.rst:33 msgid "" "When creating a breakpoint, its associated :attr:`file name ` should " -"be in canonical form. If a :attr:`funcname` is defined, a breakpoint :attr:" -"`hit ` will be counted when the first line of that function is " -"executed. A :attr:`conditional ` breakpoint always counts a :attr:" -"`hit `." +"be in canonical form. If a :attr:`funcname` is defined, a " +"breakpoint :attr:`hit ` will be counted when the first line of that " +"function is executed. A :attr:`conditional ` breakpoint always counts " +"a :attr:`hit `." msgstr "" #: library/bdb.rst:39 @@ -156,8 +156,8 @@ msgstr "" #: library/bdb.rst:110 msgid "" -"Dictionary of :class:`Breakpoint` instances indexed by (:attr:`file`, :attr:" -"`line`) tuples." +"Dictionary of :class:`Breakpoint` instances indexed by " +"(:attr:`file`, :attr:`line`) tuples." msgstr "" #: library/bdb.rst:115 @@ -175,8 +175,8 @@ msgstr "" #: library/bdb.rst:125 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." +"should implement user interaction. The standard debugger class " +"(:class:`pdb.Pdb`) is an example." msgstr "" #: library/bdb.rst:129 @@ -203,16 +203,16 @@ msgstr "" #: library/bdb.rst:144 msgid "" -"For real file names, the canonical form is an operating-system-dependent, :" -"func:`case-normalized ` :func:`absolute path `. A *filename* with angle brackets, such as ``\"\"`` " -"generated in interactive mode, is returned unchanged." +"For real file names, the canonical form is an operating-system-" +"dependent, :func:`case-normalized ` :func:`absolute path " +"`. A *filename* with angle brackets, such as " +"``\"\"`` generated in interactive mode, is returned unchanged." msgstr "" #: library/bdb.rst:151 msgid "" -"Set the :attr:`!botframe`, :attr:`!stopframe`, :attr:`!returnframe` and :" -"attr:`quitting ` attributes with values ready to start " +"Set the :attr:`!botframe`, :attr:`!stopframe`, :attr:`!returnframe` " +"and :attr:`quitting ` attributes with values ready to start " "debugging." msgstr "" @@ -272,44 +272,45 @@ msgstr "" #: library/bdb.rst:177 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`." +"trace function. For more information on code and frame objects, refer " +"to :ref:`types`." msgstr "" #: library/bdb.rst:183 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:`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." +"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:`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 "" #: library/bdb.rst:191 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:`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." +"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:`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 "" #: library/bdb.rst:199 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:`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." +"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:`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 "" #: library/bdb.rst:207 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:`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." +"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:`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 "" #: library/bdb.rst:213 @@ -360,8 +361,8 @@ msgstr "" #: library/bdb.rst:248 msgid "" -"Called from :meth:`dispatch_line` when either :meth:`stop_here` or :meth:" -"`break_here` returns ``True``." +"Called from :meth:`dispatch_line` when either :meth:`stop_here` " +"or :meth:`break_here` returns ``True``." msgstr "" #: library/bdb.rst:253 @@ -447,9 +448,9 @@ msgstr "" #: library/bdb.rst:322 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." +"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 "" #: library/bdb.rst:328 @@ -563,17 +564,17 @@ msgstr "" #: library/bdb.rst:411 msgid "" -"Return ``True`` if we should break here, depending on the way the :class:" -"`Breakpoint` *b* was set." +"Return ``True`` if we should break here, depending on the way " +"the :class:`Breakpoint` *b* was set." msgstr "" #: library/bdb.rst:414 msgid "" -"If it was set via line number, it checks if :attr:`b.line ` is the same as the one in *frame*. If the breakpoint was set via :" -"attr:`function name `, we have to check we are in " -"the right *frame* (the right function) and if we are on its first executable " -"line." +"If it was set via line number, it checks if :attr:`b.line " +"` is the same as the one in *frame*. If the breakpoint " +"was set via :attr:`function name `, we have to " +"check we are in the right *frame* (the right function) and if we are on its " +"first executable line." msgstr "" #: library/bdb.rst:423 @@ -584,15 +585,16 @@ msgstr "" #: library/bdb.rst:426 msgid "" -"The *active breakpoint* is the first entry in :attr:`bplist ` for the (:attr:`file `, :attr:`line `) (which must exist) that is :attr:`enabled `, for which :func:`checkfuncname` is true, and that has neither a " +"The *active breakpoint* is the first entry in :attr:`bplist " +"` for the (:attr:`file " +"`, :attr:`line `) (which must " +"exist) that is :attr:`enabled `, for " +"which :func:`checkfuncname` is true, and that has neither a " "false :attr:`condition ` nor positive :attr:`ignore " "` count. The *flag*, meaning that a temporary " -"breakpoint should be deleted, is ``False`` only when the :attr:`cond ` cannot be evaluated (in which case, :attr:`ignore ` count is ignored)." +"breakpoint should be deleted, is ``False`` only when the :attr:`cond " +"` cannot be evaluated (in which case, :attr:`ignore " +"` count is ignored)." msgstr "" #: library/bdb.rst:437 diff --git a/library/binascii.po b/library/binascii.po index e4bd5fac6..b50b71615 100644 --- a/library/binascii.po +++ b/library/binascii.po @@ -24,8 +24,8 @@ msgstr "" 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` or :" -"mod:`base64` instead. The :mod:`binascii` module contains low-level " +"not use these functions directly but use wrapper modules like :mod:`uu` " +"or :mod:`base64` instead. The :mod:`binascii` module contains low-level " "functions written in C for greater speed that are used by the higher-level " "modules." msgstr "" @@ -200,8 +200,8 @@ msgstr "" #: library/binascii.rst:162 msgid "" "Similar functionality (accepting only text string arguments, but more " -"liberal towards whitespace) is also accessible using the :meth:`bytes." -"fromhex` class method." +"liberal towards whitespace) is also accessible using " +"the :meth:`bytes.fromhex` class method." msgstr "" #: library/binascii.rst:168 diff --git a/library/bisect.po b/library/bisect.po index c2ffb5465..f2cbb8c90 100644 --- a/library/bisect.po +++ b/library/bisect.po @@ -37,10 +37,10 @@ msgid "" "The module is called :mod:`bisect` because it uses a basic bisection " "algorithm to do its work. Unlike other bisection tools that search for a " "specific value, the functions in this module are designed to locate an " -"insertion point. Accordingly, the functions never call an :meth:`~object." -"__eq__` method to determine whether a value has been found. Instead, the " -"functions only call the :meth:`~object.__lt__` method and will return an " -"insertion point between values in an array." +"insertion point. Accordingly, the functions never call " +"an :meth:`~object.__eq__` method to determine whether a value has been " +"found. Instead, the functions only call the :meth:`~object.__lt__` method " +"and will return an insertion point between values in an array." msgstr "" #: library/bisect.rst:29 @@ -159,10 +159,10 @@ msgid "" "The search functions are stateless and discard key function results after " "they are used. Consequently, if the search functions are used in a loop, " "the key function may be called again and again on the same array elements. " -"If the key function isn't fast, consider wrapping it with :py:func:" -"`functools.cache` to avoid duplicate computations. Alternatively, consider " -"searching an array of precomputed keys to locate the insertion point (as " -"shown in the examples section below)." +"If the key function isn't fast, consider wrapping it " +"with :py:func:`functools.cache` to avoid duplicate computations. " +"Alternatively, consider searching an array of precomputed keys to locate the " +"insertion point (as shown in the examples section below)." msgstr "" #: library/bisect.rst:131 diff --git a/library/builtins.po b/library/builtins.po index bc41c18d1..b97f2934b 100644 --- a/library/builtins.po +++ b/library/builtins.po @@ -23,8 +23,8 @@ msgstr "" #: 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`." +"for example, ``builtins.open`` is the full name for the built-in " +"function :func:`open`." msgstr "" #: library/builtins.rst:12 @@ -60,9 +60,9 @@ msgstr "" 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." +"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 "" #: library/builtins.rst:43 diff --git a/library/bz2.po b/library/bz2.po index 913f28335..860f591a5 100644 --- a/library/bz2.po +++ b/library/bz2.po @@ -78,8 +78,8 @@ msgstr "" #: library/bz2.rst:45 msgid "" -"The *compresslevel* argument is an integer from 1 to 9, as for the :class:" -"`BZ2File` constructor." +"The *compresslevel* argument is an integer from 1 to 9, as for " +"the :class:`BZ2File` constructor." msgstr "" #: library/bz2.rst:48 @@ -92,8 +92,8 @@ msgstr "" #: library/bz2.rst:53 msgid "" -"For text mode, a :class:`BZ2File` object is created, and wrapped in an :" -"class:`io.TextIOWrapper` instance with the specified encoding, error " +"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 "" @@ -145,9 +145,10 @@ msgstr "" #: library/bz2.rst:89 msgid "" -":class:`BZ2File` provides all of the members specified by the :class:`io." -"BufferedIOBase`, except for :meth:`~io.BufferedIOBase.detach` and :meth:`~io." -"IOBase.truncate`. Iteration and the :keyword:`with` statement are supported." +":class:`BZ2File` provides all of the members specified by " +"the :class:`io.BufferedIOBase`, except for :meth:`~io.BufferedIOBase.detach` " +"and :meth:`~io.IOBase.truncate`. Iteration and the :keyword:`with` statement " +"are supported." msgstr "" #: library/bz2.rst:94 @@ -163,10 +164,10 @@ msgstr "" #: library/bz2.rst:102 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*)." +"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 "" #: library/bz2.rst:111 @@ -268,8 +269,8 @@ msgstr "" #: library/bz2.rst:202 msgid "" -"When you have finished providing data to the compressor, call the :meth:" -"`flush` method to finish the compression process." +"When you have finished providing data to the compressor, call " +"the :meth:`flush` method to finish the compression process." msgstr "" #: library/bz2.rst:208 @@ -324,9 +325,9 @@ msgstr "" #: library/bz2.rst:246 msgid "" -"Attempting to decompress data after the end of stream is reached raises an :" -"exc:`EOFError`. Any data found after the end of the stream is ignored and " -"saved in the :attr:`~.unused_data` attribute." +"Attempting to decompress data after the end of stream is reached raises " +"an :exc:`EOFError`. Any data found after the end of the stream is ignored " +"and saved in the :attr:`~.unused_data` attribute." msgstr "" #: library/bz2.rst:250 diff --git a/library/calendar.po b/library/calendar.po index 54a138c31..02d33d548 100644 --- a/library/calendar.po +++ b/library/calendar.po @@ -49,8 +49,8 @@ msgstr "" #: library/calendar.rst:33 msgid "" "Creates a :class:`Calendar` object. *firstweekday* is an integer specifying " -"the first day of the week. :const:`MONDAY` is ``0`` (the default), :const:" -"`SUNDAY` is ``6``." +"the first day of the week. :const:`MONDAY` is ``0`` (the " +"default), :const:`SUNDAY` is ``6``." msgstr "" #: library/calendar.rst:36 @@ -67,8 +67,8 @@ msgstr "" #: library/calendar.rst:45 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." +"The first value from the iterator will be the same as the value of " +"the :attr:`firstweekday` property." msgstr "" #: library/calendar.rst:52 @@ -81,34 +81,34 @@ msgstr "" #: library/calendar.rst:60 msgid "" -"Return an iterator for the month *month* in the year *year* similar to :meth:" -"`itermonthdates`, but not restricted by the :class:`datetime.date` range. " -"Days returned will simply be day of the month numbers. For the days outside " -"of the specified month, the day number is ``0``." +"Return an iterator for the month *month* in the year *year* similar " +"to :meth:`itermonthdates`, but not restricted by the :class:`datetime.date` " +"range. Days returned will simply be day of the month numbers. For the days " +"outside of the specified month, the day number is ``0``." msgstr "" #: library/calendar.rst:68 msgid "" -"Return an iterator for the month *month* in the year *year* similar to :meth:" -"`itermonthdates`, but not restricted by the :class:`datetime.date` range. " -"Days returned will be tuples consisting of a day of the month number and a " -"week day number." +"Return an iterator for the month *month* in the year *year* similar " +"to :meth:`itermonthdates`, but not restricted by the :class:`datetime.date` " +"range. Days returned will be tuples consisting of a day of the month number " +"and a week day number." msgstr "" #: library/calendar.rst:76 msgid "" -"Return an iterator for the month *month* in the year *year* similar to :meth:" -"`itermonthdates`, but not restricted by the :class:`datetime.date` range. " -"Days returned will be tuples consisting of a year, a month and a day of the " -"month numbers." +"Return an iterator for the month *month* in the year *year* similar " +"to :meth:`itermonthdates`, but not restricted by the :class:`datetime.date` " +"range. Days returned will be tuples consisting of a year, a month and a day " +"of the month numbers." msgstr "" #: library/calendar.rst:86 msgid "" -"Return an iterator for the month *month* in the year *year* similar to :meth:" -"`itermonthdates`, but not restricted by the :class:`datetime.date` range. " -"Days returned will be tuples consisting of a year, a month, a day of the " -"month, and a day of the week numbers." +"Return an iterator for the month *month* in the year *year* similar " +"to :meth:`itermonthdates`, but not restricted by the :class:`datetime.date` " +"range. Days returned will be tuples consisting of a year, a month, a day of " +"the month, and a day of the week numbers." msgstr "" #: library/calendar.rst:96 @@ -139,16 +139,16 @@ msgstr "" #: library/calendar.rst:123 msgid "" -"Return the data for the specified year ready for formatting (similar to :" -"meth:`yeardatescalendar`). Entries in the week lists are tuples of day " +"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 "" #: library/calendar.rst:130 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." +"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 "" #: library/calendar.rst:137 @@ -164,8 +164,8 @@ 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." +"the first weekday as specified in the constructor or set by " +"the :meth:`setfirstweekday` method." msgstr "" #: library/calendar.rst:152 @@ -177,9 +177,9 @@ 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." +"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 "" #: library/calendar.rst:167 @@ -276,14 +276,14 @@ msgstr "" #: library/calendar.rst:255 msgid "" -"The CSS class for the whole year's table of tables (used by :meth:" -"`formatyear`). The default value is ``\"year\"``." +"The CSS class for the whole year's table of tables (used " +"by :meth:`formatyear`). The default value is ``\"year\"``." msgstr "" #: library/calendar.rst:263 msgid "" -"The CSS class for the table head for the whole year (used by :meth:" -"`formatyear`). The default value is ``\"year\"``." +"The CSS class for the table head for the whole year (used " +"by :meth:`formatyear`). The default value is ``\"year\"``." msgstr "" #: library/calendar.rst:269 @@ -338,9 +338,9 @@ msgstr "" #: library/calendar.rst:309 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::" +"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 "" #: library/calendar.rst:314 @@ -399,8 +399,8 @@ msgstr "" #: library/calendar.rst:368 msgid "" -"Returns a month's calendar in a multi-line string using the :meth:" -"`~TextCalendar.formatmonth` of the :class:`TextCalendar` class." +"Returns a month's calendar in a multi-line string using " +"the :meth:`~TextCalendar.formatmonth` of the :class:`TextCalendar` class." msgstr "" #: library/calendar.rst:374 @@ -448,8 +448,8 @@ msgstr "" #: library/calendar.rst:429 msgid "" "Enumeration defining days of the week as integer constants. The members of " -"this enumeration are exported to the module scope as :data:`MONDAY` through :" -"data:`SUNDAY`." +"this enumeration are exported to the module scope as :data:`MONDAY` " +"through :data:`SUNDAY`." msgstr "" #: library/calendar.rst:438 @@ -597,8 +597,8 @@ msgstr "" #: library/calendar.rst:595 msgid "" -"The encoding to use for output. :option:`--encoding` is required if :option:" -"`--locale` is set." +"The encoding to use for output. :option:`--encoding` is required " +"if :option:`--locale` is set." msgstr "" #: library/calendar.rst:601 diff --git a/library/cgi.po b/library/cgi.po index 58f3eb7d9..05fcbaf16 100644 --- a/library/cgi.po +++ b/library/cgi.po @@ -32,10 +32,11 @@ msgstr "" #: library/cgi.rst:22 msgid "" -"The :class:`FieldStorage` class can typically be replaced with :func:`urllib." -"parse.parse_qsl` for ``GET`` and ``HEAD`` requests, and the :mod:`email." -"message` module or :pypi:`multipart` for ``POST`` and ``PUT``. Most :ref:" -"`utility functions ` have replacements." +"The :class:`FieldStorage` class can typically be replaced " +"with :func:`urllib.parse.parse_qsl` for ``GET`` and ``HEAD`` requests, and " +"the :mod:`email.message` module or :pypi:`multipart` for ``POST`` and " +"``PUT``. Most :ref:`utility functions ` have " +"replacements." msgstr "" #: library/cgi.rst:30 @@ -184,15 +185,16 @@ msgid "" "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." +"for the optional *keep_blank_values* keyword parameter when creating " +"the :class:`FieldStorage` instance." msgstr "" #: library/cgi.rst:122 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::" +"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 "" #: library/cgi.rst:127 @@ -220,14 +222,14 @@ msgstr "" #: library/cgi.rst:143 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::" +"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 "" #: library/cgi.rst:153 @@ -238,15 +240,16 @@ msgstr "" #: library/cgi.rst:156 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)::" +"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 "" #: library/cgi.rst:167 @@ -279,11 +282,12 @@ msgstr "" 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." +"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 "" #: library/cgi.rst:192 @@ -297,8 +301,8 @@ msgstr "" #: library/cgi.rst:197 msgid "" -"A form submitted via POST that also has a query string will contain both :" -"class:`FieldStorage` and :class:`MiniFieldStorage` items." +"A form submitted via POST that also has a query string will contain " +"both :class:`FieldStorage` and :class:`MiniFieldStorage` items." msgstr "" #: library/cgi.rst:200 @@ -309,8 +313,8 @@ msgstr "" #: library/cgi.rst:204 msgid "" -"Added support for the context management protocol to the :class:" -"`FieldStorage` class." +"Added support for the context management protocol to " +"the :class:`FieldStorage` class." msgstr "" #: library/cgi.rst:210 @@ -319,12 +323,12 @@ msgstr "" #: library/cgi.rst:212 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." +"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 "" #: library/cgi.rst:221 @@ -392,9 +396,9 @@ msgstr "" #: library/cgi.rst:258 msgid "" -"A more convenient approach is to use the methods :meth:`~FieldStorage." -"getfirst` and :meth:`~FieldStorage.getlist` provided by this higher level " -"interface." +"A more convenient approach is to use the " +"methods :meth:`~FieldStorage.getfirst` and :meth:`~FieldStorage.getlist` " +"provided by this higher level interface." msgstr "" #: library/cgi.rst:264 @@ -441,8 +445,8 @@ msgstr "" #: library/cgi.rst:299 msgid "" -"Parse a query in the environment or from a file (the file defaults to ``sys." -"stdin``). The *keep_blank_values*, *strict_parsing* and *separator* " +"Parse a query in the environment or from a file (the file defaults to " +"``sys.stdin``). The *keep_blank_values*, *strict_parsing* and *separator* " "parameters are passed to :func:`urllib.parse.parse_qs` unchanged." msgstr "" @@ -489,9 +493,10 @@ msgstr "" #: library/cgi.rst:332 msgid "" "This function, like the rest of the :mod:`cgi` module, is deprecated. It can " -"be replaced with the functionality in the :mod:`email` package (e.g. :class:" -"`email.message.EmailMessage`/:class:`email.message.Message`) which " -"implements the same MIME RFCs, or with the :pypi:`multipart` PyPI project." +"be replaced with the functionality in the :mod:`email` package " +"(e.g. :class:`email.message.EmailMessage`/:class:`email.message.Message`) " +"which implements the same MIME RFCs, or with the :pypi:`multipart` PyPI " +"project." msgstr "" #: library/cgi.rst:342 @@ -547,13 +552,13 @@ msgstr "" #: library/cgi.rst:391 msgid "" -"There's one important rule: if you invoke an external program (via :func:`os." -"system`, :func:`os.popen` or other functions 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!" +"There's one important rule: if you invoke an external program " +"(via :func:`os.system`, :func:`os.popen` or other functions 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 "" #: library/cgi.rst:399 @@ -601,9 +606,9 @@ msgid "" "(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." +"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 "" #: library/cgi.rst:431 @@ -695,8 +700,8 @@ msgstr "" #: library/cgi.rst:491 msgid "" -"This should produce the same results as those gotten from installing the :" -"file:`cgi.py` file itself." +"This should produce the same results as those gotten from installing " +"the :file:`cgi.py` file itself." msgstr "" #: library/cgi.rst:494 @@ -712,8 +717,8 @@ msgstr "" #: library/cgi.rst:501 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::" +"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 "" #: library/cgi.rst:508 diff --git a/library/cgitb.po b/library/cgitb.po index e90d61979..be4cb7943 100644 --- a/library/cgitb.po +++ b/library/cgitb.po @@ -64,8 +64,8 @@ msgstr "" #: library/cgitb.rst:49 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`." +"default handling for exceptions by setting the value " +"of :attr:`sys.excepthook`." msgstr "" #: library/cgitb.rst:52 @@ -105,9 +105,9 @@ msgid "" "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`." +"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 "" #: library/cgitb.rst:13 diff --git a/library/chunk.po b/library/chunk.po index 30d861b5d..d65692497 100644 --- a/library/chunk.po +++ b/library/chunk.po @@ -117,17 +117,17 @@ msgstr "" 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." +"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 "" #: library/chunk.rst:78 @@ -151,9 +151,9 @@ msgstr "" #: library/chunk.rst:97 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`." +"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 "" #: library/chunk.rst:104 diff --git a/library/cmath.po b/library/cmath.po index 4f1d65ca8..1a2373d5a 100644 --- a/library/cmath.po +++ b/library/cmath.po @@ -75,8 +75,8 @@ msgstr "" #: library/cmath.rst:44 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``." +"*Cartesian* coordinates. It is completely determined by its *real part* " +"``z.real`` and its *imaginary part* ``z.imag``." msgstr "" #: library/cmath.rst:48 @@ -151,8 +151,8 @@ msgstr "" #: library/cmath.rst:111 msgid "" -"Return the base-10 logarithm of *x*. This has the same branch cut as :func:" -"`log`." +"Return the base-10 logarithm of *x*. This has the same branch cut " +"as :func:`log`." msgstr "" #: library/cmath.rst:117 @@ -342,10 +342,10 @@ msgid "" "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)." +"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 "" #: library/cmath.rst:311 diff --git a/library/cmd.po b/library/cmd.po index 6a3a70c22..7de4bdc2d 100644 --- a/library/cmd.po +++ b/library/cmd.po @@ -44,24 +44,24 @@ msgstr "" #: 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." +"completion key; it defaults to :kbd:`Tab`. If *completekey* is " +"not :const:`None` and :mod:`readline` is available, command completion is " +"done automatically." msgstr "" #: 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`." +"and output. If not specified, they will default to :data:`sys.stdin` " +"and :data:`sys.stdout`." msgstr "" #: 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." +"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 "" #: library/cmd.rst:42 @@ -87,11 +87,12 @@ msgstr "" #: 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.)." +"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 "" #: library/cmd.rst:62 @@ -129,10 +130,10 @@ msgstr "" #: library/cmd.rst:89 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:`!" +"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 "" @@ -140,10 +141,10 @@ msgstr "" #: library/cmd.rst:100 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 " +"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 "" @@ -176,9 +177,9 @@ msgstr "" #: library/cmd.rst:136 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; " +"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 "" @@ -225,15 +226,15 @@ msgstr "" #: library/cmd.rst:186 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." +"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 "" #: library/cmd.rst:193 msgid "" -"A string to issue as an intro or banner. May be overridden by giving the :" -"meth:`cmdloop` method an argument." +"A string to issue as an intro or banner. May be overridden by giving " +"the :meth:`cmdloop` method an argument." msgstr "" #: library/cmd.rst:199 @@ -244,15 +245,15 @@ msgstr "" #: library/cmd.rst:204 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)." +"topics (that is, there are :meth:`!help_\\*` methods without " +"corresponding :meth:`!do_\\*` methods)." msgstr "" #: library/cmd.rst:211 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)." +"commands (that is, there are :meth:`!do_\\*` methods without " +"corresponding :meth:`!help_\\*` methods)." msgstr "" #: library/cmd.rst:218 @@ -264,11 +265,12 @@ msgstr "" #: library/cmd.rst:224 msgid "" "A flag, defaulting to true. If true, :meth:`cmdloop` uses :func:`input` to " -"display a prompt and read the next command; if false, :data:`sys.stdout." -"write() ` and :data:`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.)" +"display a prompt and read the next command; if " +"false, :data:`sys.stdout.write() ` " +"and :data:`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 "" #: library/cmd.rst:234 @@ -289,10 +291,10 @@ msgstr "" #: library/cmd.rst:244 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." +"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 "" #: library/cmd.rst:249 @@ -300,8 +302,8 @@ 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:`~Cmd.cmdqueue` for immediate playback::" +"do_playback` method reads the file and adds the recorded commands to " +"the :attr:`~Cmd.cmdqueue` for immediate playback::" msgstr "" #: library/cmd.rst:255 diff --git a/library/code.po b/library/code.po index c1ac7d8a1..3870bfe00 100644 --- a/library/code.po +++ b/library/code.po @@ -54,9 +54,9 @@ msgid "" "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:" -"`~InteractiveConsole.interact` method of the instance is then run with " -"*banner* and *exitmsg* passed as the banner and exit message to use, if " +"use as the default namespace for the interpreter loop. " +"The :meth:`~InteractiveConsole.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 "" @@ -104,10 +104,10 @@ msgstr "" #: 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``." +"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 "" #: library/code.rst:86 @@ -126,15 +126,15 @@ msgstr "" #: 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." +"The return value can be used to decide whether to use ``sys.ps1`` or " +"``sys.ps2`` to prompt the next line." msgstr "" #: 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." +"called to display a traceback. All exceptions are caught " +"except :exc:`SystemExit`, which is allowed to propagate." msgstr "" #: library/code.rst:103 @@ -179,9 +179,9 @@ msgstr "" #: 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." +"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 "" #: library/code.rst:145 @@ -229,7 +229,7 @@ msgstr "" #: 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." +"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 "" diff --git a/library/codecs.po b/library/codecs.po index 66d2f8519..3d332573d 100644 --- a/library/codecs.po +++ b/library/codecs.po @@ -50,9 +50,9 @@ msgstr "" #: 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 " +"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 "" @@ -63,9 +63,9 @@ msgstr "" #: 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 " +"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 "" @@ -75,16 +75,17 @@ msgstr "" #: library/codecs.rst:60 msgid "" -"Looks up the codec info in the Python codec registry and returns a :class:" -"`CodecInfo` object as defined below." +"Looks up the codec info in the Python codec registry and returns " +"a :class:`CodecInfo` object as defined below." msgstr "" #: 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." +"object is found, a :exc:`LookupError` is raised. Otherwise, " +"the :class:`CodecInfo` object is stored in the cache and returned to the " +"caller." msgstr "" #: library/codecs.rst:70 @@ -100,25 +101,25 @@ msgstr "" #: 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." +"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 "" #: 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." +"provide the interface defined by the base " +"classes :class:`IncrementalEncoder` and :class:`IncrementalDecoder`, " +"respectively. Incremental codecs can maintain state." msgstr "" #: 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." +"the interface defined by the base classes :class:`StreamWriter` " +"and :class:`StreamReader`, respectively. Stream codecs can maintain state." msgstr "" #: library/codecs.rst:106 @@ -167,14 +168,14 @@ msgstr "" #: library/codecs.rst:143 msgid "" -"Look up the codec for the given encoding and return its :class:" -"`StreamReader` class or factory function." +"Look up the codec for the given encoding and return " +"its :class:`StreamReader` class or factory function." msgstr "" #: library/codecs.rst:151 msgid "" -"Look up the codec for the given encoding and return its :class:" -"`StreamWriter` class or factory function." +"Look up the codec for the given encoding and return " +"its :class:`StreamWriter` class or factory function." msgstr "" #: library/codecs.rst:156 @@ -212,9 +213,9 @@ msgstr "" #: library/codecs.rst:186 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." +"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 "" #: library/codecs.rst:192 @@ -302,8 +303,8 @@ msgstr "" 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`." +"``rot_13``, although ``rot_13`` may be used equivalently " +"with :func:`iterencode`." msgstr "" #: library/codecs.rst:256 @@ -317,11 +318,11 @@ 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." +"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 "" #: library/codecs.rst:285 @@ -406,9 +407,10 @@ msgstr "" #: library/codecs.rst:346 msgid "" "Replace with backslashed escape sequences. On encoding, use hexadecimal form " -"of Unicode code point with formats :samp:`\\\\x{hh}` :samp:`\\\\u{xxxx}` :" -"samp:`\\\\U{xxxxxxxx}`. On decoding, use hexadecimal form of byte value with " -"format :samp:`\\\\x{hh}`. Implemented in :func:`backslashreplace_errors`." +"of Unicode code point with formats :samp:`\\\\x{hh}` :samp:`\\\\u{xxxx}" +"` :samp:`\\\\U{xxxxxxxx}`. On decoding, use hexadecimal form of byte value " +"with format :samp:`\\\\x{hh}`. Implemented " +"in :func:`backslashreplace_errors`." msgstr "" #: library/codecs.rst:355 @@ -425,8 +427,8 @@ msgstr "" #: library/codecs.rst:369 msgid "" -"The following error handlers are only applicable to encoding (within :term:" -"`text encodings `):" +"The following error handlers are only applicable to encoding " +"(within :term:`text encodings `):" msgstr "" #: library/codecs.rst:375 @@ -436,8 +438,8 @@ msgstr "" #: library/codecs.rst:375 msgid "" "Replace with XML/HTML numeric character reference, which is a decimal form " -"of Unicode code point with format :samp:`&#{num};`. Implemented in :func:" -"`xmlcharrefreplace_errors`." +"of Unicode code point with format :samp:`&#{num};`. Implemented " +"in :func:`xmlcharrefreplace_errors`." msgstr "" #: library/codecs.rst:381 @@ -447,8 +449,8 @@ msgstr "" #: library/codecs.rst:381 msgid "" "Replace with ``\\N{...}`` escape sequences, what appears in the braces is " -"the Name property from Unicode Character Database. Implemented in :func:" -"`namereplace_errors`." +"the Name property from Unicode Character Database. Implemented " +"in :func:`namereplace_errors`." msgstr "" #: library/codecs.rst:390 @@ -510,17 +512,18 @@ msgstr "" #: library/codecs.rst:425 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." +"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 "" #: library/codecs.rst:437 @@ -596,8 +599,8 @@ msgstr "" #: library/codecs.rst:493 msgid "" -"Implements the ``'xmlcharrefreplace'`` error handling (for encoding within :" -"term:`text encoding` only)." +"Implements the ``'xmlcharrefreplace'`` error handling (for encoding " +"within :term:`text encoding` only)." msgstr "" #: library/codecs.rst:496 @@ -609,8 +612,8 @@ msgstr "" #: library/codecs.rst:503 msgid "" -"Implements the ``'namereplace'`` error handling (for encoding within :term:" -"`text encoding` only)." +"Implements the ``'namereplace'`` error handling (for encoding " +"within :term:`text encoding` only)." msgstr "" #: library/codecs.rst:506 @@ -647,9 +650,9 @@ msgstr "" #: library/codecs.rst:535 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." +"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 "" #: library/codecs.rst:539 @@ -675,9 +678,9 @@ msgstr "" #: library/codecs.rst:557 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." +"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 "" #: library/codecs.rst:561 @@ -695,18 +698,18 @@ 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." +"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 "" #: library/codecs.rst:576 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." +"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 "" #: library/codecs.rst:585 @@ -742,21 +745,21 @@ msgstr "" 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." +"error handling strategies during the lifetime of " +"the :class:`IncrementalEncoder` object." msgstr "" #: library/codecs.rst:612 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)." +"returns the resulting encoded object. If this is the last call " +"to :meth:`encode` *final* must be true (the default is false)." msgstr "" #: library/codecs.rst:619 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 " +"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 "" @@ -808,19 +811,19 @@ msgstr "" 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." +"error handling strategies during the lifetime of " +"the :class:`IncrementalDecoder` object." msgstr "" #: library/codecs.rst:669 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)." +"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 "" #: library/codecs.rst:680 @@ -975,8 +978,8 @@ msgstr "" #: library/codecs.rst:797 msgid "" -"The set of allowed values for the *errors* argument can be extended with :" -"func:`register_error`." +"The set of allowed values for the *errors* argument can be extended " +"with :func:`register_error`." msgstr "" #: library/codecs.rst:803 @@ -1042,8 +1045,8 @@ msgstr "" #: library/codecs.rst:846 msgid "" -"*sizehint*, if given, is passed as the *size* argument to the stream's :meth:" -"`read` method." +"*sizehint*, if given, is passed as the *size* argument to the " +"stream's :meth:`read` method." msgstr "" #: library/codecs.rst:854 @@ -1070,8 +1073,8 @@ msgstr "" #: library/codecs.rst:893 msgid "" -"The design is such that one can use the factory functions returned by the :" -"func:`lookup` function to construct the instance." +"The design is such that one can use the factory functions returned by " +"the :func:`lookup` function to construct the instance." msgstr "" #: library/codecs.rst:875 @@ -1085,8 +1088,8 @@ msgstr "" #: library/codecs.rst:880 msgid "" -":class:`StreamReaderWriter` instances define the combined interfaces of :" -"class:`StreamReader` and :class:`StreamWriter` classes. They inherit all " +":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 "" @@ -1134,9 +1137,9 @@ msgstr "" #: library/codecs.rst:919 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." +":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 "" #: library/codecs.rst:927 @@ -2279,9 +2282,9 @@ msgstr "" #: library/codecs.rst:1323 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." +"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 "" #: library/codecs.rst:1332 @@ -2509,9 +2512,9 @@ msgstr "" #: library/codecs.rst:1448 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)." +"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 "" #: library/codecs.rst:1457 @@ -2556,15 +2559,15 @@ msgstr "" #: library/codecs.rst:1484 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." +"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 "" #: library/codecs.rst:1495 @@ -2578,8 +2581,8 @@ msgid "" "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 " +"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 "" diff --git a/library/codeop.po b/library/codeop.po index 4560d7593..613141cc2 100644 --- a/library/codeop.po +++ b/library/codeop.po @@ -70,17 +70,17 @@ msgstr "" #: 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." +"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 "" #: library/codeop.rst:45 msgid "" "The *symbol* argument determines whether *source* is compiled as a statement " "(``'single'``, the default), as a sequence of :term:`statement` (``'exec'``) " -"or as an :term:`expression` (``'eval'``). Any other value will cause :exc:" -"`ValueError` to be raised." +"or as an :term:`expression` (``'eval'``). Any other value will " +"cause :exc:`ValueError` to be raised." msgstr "" #: library/codeop.rst:52 diff --git a/library/collections.abc.po b/library/collections.abc.po index 4e68c3896..439ce2db2 100644 --- a/library/collections.abc.po +++ b/library/collections.abc.po @@ -32,8 +32,8 @@ msgstr "" 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 :term:`hashable` or whether it is a :term:" -"`mapping`." +"for example, whether it is :term:`hashable` or whether it is " +"a :term:`mapping`." msgstr "" #: library/collections.abc.rst:27 @@ -103,9 +103,9 @@ msgstr "" msgid "" "In this example, class :class:`!D` does not need to define ``__contains__``, " "``__iter__``, and ``__reversed__`` because the :ref:`in-operator " -"`, the :term:`iteration ` logic, and the :func:" -"`reversed` function automatically fall back to using ``__getitem__`` and " -"``__len__``." +"`, the :term:`iteration ` logic, and " +"the :func:`reversed` function automatically fall back to using " +"``__getitem__`` and ``__len__``." msgstr "" #: library/collections.abc.rst:82 @@ -471,8 +471,8 @@ msgid "" "Checking ``isinstance(obj, Iterable)`` detects classes that are registered " "as :class:`Iterable` or that have an :meth:`~container.__iter__` method, but " "it does not detect classes that iterate with the :meth:`~object.__getitem__` " -"method. The only reliable way to determine whether an object is :term:" -"`iterable` is to call ``iter(obj)``." +"method. The only reliable way to determine whether an object " +"is :term:`iterable` is to call ``iter(obj)``." msgstr "" #: library/collections.abc.rst:200 @@ -510,8 +510,8 @@ msgid "" "Checking ``isinstance(obj, Iterable)`` detects classes that are registered " "as :class:`Iterable` or that have an :meth:`~container.__iter__` method, but " "it does not detect classes that iterate with the :meth:`~object.__getitem__` " -"method. The only reliable way to determine whether an object is :term:" -"`iterable` is to call ``iter(obj)``." +"method. The only reliable way to determine whether an object " +"is :term:`iterable` is to call ``iter(obj)``." msgstr "" #: library/collections.abc.rst:235 @@ -520,8 +520,9 @@ msgstr "" #: library/collections.abc.rst:241 msgid "" -"ABC for classes that provide the :meth:`~iterator.__iter__` and :meth:" -"`~iterator.__next__` methods. See also the definition of :term:`iterator`." +"ABC for classes that provide the :meth:`~iterator.__iter__` " +"and :meth:`~iterator.__next__` methods. See also the definition " +"of :term:`iterator`." msgstr "" #: library/collections.abc.rst:247 @@ -532,16 +533,16 @@ msgstr "" #: library/collections.abc.rst:254 msgid "" -"ABC for :term:`generator` classes that implement the protocol defined in :" -"pep:`342` that extends :term:`iterators ` with the :meth:" -"`~generator.send`, :meth:`~generator.throw` and :meth:`~generator.close` " -"methods." +"ABC for :term:`generator` classes that implement the protocol defined " +"in :pep:`342` that extends :term:`iterators ` with " +"the :meth:`~generator.send`, :meth:`~generator.throw` " +"and :meth:`~generator.close` methods." msgstr "" #: library/collections.abc.rst:259 msgid "" -"See :ref:`annotating-generators-and-coroutines` for details on using :class:" -"`!Generator` in type annotations." +"See :ref:`annotating-generators-and-coroutines` for details on " +"using :class:`!Generator` in type annotations." msgstr "" #: library/collections.abc.rst:268 @@ -550,9 +551,10 @@ msgstr "" #: library/collections.abc.rst:270 msgid "" -"Implementation note: Some of the mixin methods, such as :meth:`~container." -"__iter__`, :meth:`~object.__reversed__` and :meth:`index`, make repeated " -"calls to the underlying :meth:`~object.__getitem__` method. Consequently, " +"Implementation note: Some of the mixin methods, such " +"as :meth:`~container.__iter__`, :meth:`~object.__reversed__` " +"and :meth:`index`, make repeated calls to the " +"underlying :meth:`~object.__getitem__` method. Consequently, " "if :meth:`~object.__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 " @@ -586,14 +588,14 @@ msgstr "" #: library/collections.abc.rst:308 msgid "" "ABC for :term:`awaitable` objects, which can be used in :keyword:`await` " -"expressions. Custom implementations must provide the :meth:`~object." -"__await__` method." +"expressions. Custom implementations must provide " +"the :meth:`~object.__await__` method." msgstr "" #: library/collections.abc.rst:312 msgid "" -":term:`Coroutine ` objects and instances of the :class:" -"`~collections.abc.Coroutine` ABC are all instances of this ABC." +":term:`Coroutine ` objects and instances of " +"the :class:`~collections.abc.Coroutine` ABC are all instances of this ABC." msgstr "" #: library/collections.abc.rst:316 @@ -601,17 +603,18 @@ msgid "" "In CPython, generator-based coroutines (:term:`generators ` " "decorated with :func:`@types.coroutine `) are *awaitables*, " "even though they do not have an :meth:`~object.__await__` method. Using " -"``isinstance(gencoro, Awaitable)`` for them will return ``False``. Use :func:" -"`inspect.isawaitable` to detect them." +"``isinstance(gencoro, Awaitable)`` for them will return ``False``. " +"Use :func:`inspect.isawaitable` to detect them." msgstr "" #: library/collections.abc.rst:326 msgid "" "ABC for :term:`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:`~object.__await__`. All :class:`Coroutine` " -"instances are also instances of :class:`Awaitable`." +"methods, defined in :ref:`coroutine-" +"objects`: :meth:`~coroutine.send`, :meth:`~coroutine.throw`, " +"and :meth:`~coroutine.close`. Custom implementations must also " +"implement :meth:`~object.__await__`. All :class:`Coroutine` instances are " +"also instances of :class:`Awaitable`." msgstr "" #: library/collections.abc.rst:334 @@ -619,15 +622,15 @@ msgid "" "In CPython, generator-based coroutines (:term:`generators ` " "decorated with :func:`@types.coroutine `) are *awaitables*, " "even though they do not have an :meth:`~object.__await__` method. Using " -"``isinstance(gencoro, Coroutine)`` for them will return ``False``. Use :func:" -"`inspect.isawaitable` to detect them." +"``isinstance(gencoro, Coroutine)`` for them will return ``False``. " +"Use :func:`inspect.isawaitable` to detect them." msgstr "" #: library/collections.abc.rst:340 msgid "" -"See :ref:`annotating-generators-and-coroutines` for details on using :class:" -"`!Coroutine` in type annotations. The variance and order of type parameters " -"correspond to those of :class:`Generator`." +"See :ref:`annotating-generators-and-coroutines` for details on " +"using :class:`!Coroutine` in type annotations. The variance and order of " +"type parameters correspond to those of :class:`Generator`." msgstr "" #: library/collections.abc.rst:349 @@ -650,8 +653,8 @@ msgstr "" #: library/collections.abc.rst:366 msgid "" -"See :ref:`annotating-generators-and-coroutines` for details on using :class:" -"`!AsyncGenerator` in type annotations." +"See :ref:`annotating-generators-and-coroutines` for details on " +"using :class:`!AsyncGenerator` in type annotations." msgstr "" #: library/collections.abc.rst:373 @@ -682,9 +685,10 @@ 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:`~object.__contains__`, :meth:`~container." -"__iter__`, and :meth:`~object.__len__`. The ABC supplies the remaining " -"methods such as :meth:`!__and__` and :meth:`~frozenset.isdisjoint`::" +"underlying abstract " +"methods: :meth:`~object.__contains__`, :meth:`~container.__iter__`, " +"and :meth:`~object.__len__`. The ABC supplies the remaining methods such " +"as :meth:`!__and__` and :meth:`~frozenset.isdisjoint`::" msgstr "" #: library/collections.abc.rst:395 @@ -722,12 +726,12 @@ msgid "" "Since some set operations create new sets, the default mixin methods need a " "way to create new instances from an :term:`iterable`. The class constructor " "is assumed to have a signature in the form ``ClassName(iterable)``. That " -"assumption is factored-out to an internal :class:`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 or regular method that can construct new instances from an " -"iterable argument." +"assumption is factored-out to an internal :class:`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 or regular method that can construct new instances from " +"an iterable argument." msgstr "" #: library/collections.abc.rst:431 diff --git a/library/collections.po b/library/collections.po index aa133e630..93e120519 100644 --- a/library/collections.po +++ b/library/collections.po @@ -27,8 +27,8 @@ msgstr "" #: 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`." +"alternatives to Python's general purpose built-in " +"containers, :class:`dict`, :class:`list`, :class:`set`, and :class:`tuple`." msgstr "" #: library/collections.rst:25 @@ -186,10 +186,11 @@ msgstr "" 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:])``." +"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 "" #: library/collections.rst:102 @@ -236,9 +237,9 @@ msgstr "" 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 :attr:`~collections." -"ChainMap.parents` property." +"also features pushing and popping of contexts similar to " +"the :meth:`~collections.ChainMap.new_child` method and " +"the :attr:`~collections.ChainMap.parents` property." msgstr "" #: library/collections.rst:136 @@ -251,8 +252,8 @@ msgstr "" #: library/collections.rst:141 msgid "" -"A `greatly simplified read-only version of Chainmap `_." +"A `greatly simplified read-only version of Chainmap `_." msgstr "" #: library/collections.rst:146 @@ -575,9 +576,9 @@ msgstr "" 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:" -"`~Counter.update` and :meth:`~Counter.subtract` which allow negative and " -"zero values for both inputs and outputs." +"work and negative values are supported. The same is also true " +"for :meth:`~Counter.update` and :meth:`~Counter.subtract` which allow " +"negative and zero values for both inputs and outputs." msgstr "" #: library/collections.rst:422 @@ -596,8 +597,8 @@ msgstr "" #: library/collections.rst:432 msgid "" -"`Bag class `_ in Smalltalk." +"`Bag class `_ in Smalltalk." msgstr "" #: library/collections.rst:435 @@ -717,8 +718,8 @@ msgstr "" #: library/collections.rst:535 msgid "" -"If the insertion would cause a bounded deque to grow beyond *maxlen*, an :" -"exc:`IndexError` is raised." +"If the insertion would cause a bounded deque to grow beyond *maxlen*, " +"an :exc:`IndexError` is raised." msgstr "" #: library/collections.rst:543 @@ -735,8 +736,8 @@ msgstr "" #: library/collections.rst:555 msgid "" -"Remove the first occurrence of *value*. If not found, raises a :exc:" -"`ValueError`." +"Remove the first occurrence of *value*. If not found, raises " +"a :exc:`ValueError`." msgstr "" #: library/collections.rst:561 @@ -886,11 +887,11 @@ msgstr "" #: library/collections.rst:678 msgid "" "A `round-robin scheduler `_ can be implemented with input iterators stored in a :" -"class:`deque`. Values are yielded from the active iterator in position " -"zero. If that iterator is exhausted, it can be removed with :meth:`~deque." -"popleft`; otherwise, it can be cycled back to the end with the :meth:`~deque." -"rotate` method::" +"robin_scheduling>`_ can be implemented with input iterators stored in " +"a :class:`deque`. Values are yielded from the active iterator in position " +"zero. If that iterator is exhausted, it can be removed " +"with :meth:`~deque.popleft`; otherwise, it can be cycled back to the end " +"with the :meth:`~deque.rotate` method::" msgstr "" #: library/collections.rst:685 @@ -925,12 +926,13 @@ msgstr "" #: library/collections.rst:706 msgid "" -"To implement :class:`deque` slicing, use a similar approach applying :meth:" -"`~deque.rotate` to bring a target element to the left side of the deque. " -"Remove old entries with :meth:`~deque.popleft`, add new entries with :meth:" -"`~deque.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``." +"To implement :class:`deque` slicing, use a similar approach " +"applying :meth:`~deque.rotate` to bring a target element to the left side of " +"the deque. Remove old entries with :meth:`~deque.popleft`, add new entries " +"with :meth:`~deque.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 "" #: library/collections.rst:716 @@ -947,10 +949,10 @@ msgstr "" #: library/collections.rst:725 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." +"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 "" #: library/collections.rst:731 @@ -961,8 +963,8 @@ msgstr "" #: library/collections.rst:736 msgid "" -"If the :attr:`default_factory` attribute is ``None``, this raises a :exc:" -"`KeyError` exception with the *key* as argument." +"If the :attr:`default_factory` attribute is ``None``, this raises " +"a :exc:`KeyError` exception with the *key* as argument." msgstr "" #: library/collections.rst:739 @@ -980,17 +982,17 @@ msgstr "" #: library/collections.rst:746 msgid "" -"This method is called by the :meth:`~object.__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:`~object.__getitem__`." +"This method is called by the :meth:`~object.__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:`~object.__getitem__`." msgstr "" #: library/collections.rst:750 msgid "" -"Note that :meth:`__missing__` is *not* called for any operations besides :" -"meth:`~object.__getitem__`. This means that :meth:`get` will, like normal " -"dictionaries, return ``None`` as a default rather than using :attr:" -"`default_factory`." +"Note that :meth:`__missing__` is *not* called for any operations " +"besides :meth:`~object.__getitem__`. This means that :meth:`get` will, like " +"normal dictionaries, return ``None`` as a default rather than " +"using :attr:`default_factory`." msgstr "" #: library/collections.rst:756 @@ -1022,28 +1024,29 @@ msgstr "" #: library/collections.rst:784 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:`~defaultdict." -"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 " +"mapping; so an entry is automatically created using " +"the :attr:`~defaultdict.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 "" #: library/collections.rst:799 msgid "" -"Setting the :attr:`~defaultdict.default_factory` to :class:`int` makes the :" -"class:`defaultdict` useful for counting (like a bag or multiset in other " -"languages):" +"Setting the :attr:`~defaultdict.default_factory` to :class:`int` makes " +"the :class:`defaultdict` useful for counting (like a bag or multiset in " +"other languages):" msgstr "" #: library/collections.rst:811 msgid "" -"When a letter is first encountered, it is missing from the mapping, so the :" -"attr:`~defaultdict.default_factory` function calls :func:`int` to supply a " -"default count of zero. The increment operation then builds up the count for " -"each letter." +"When a letter is first encountered, it is missing from the mapping, so " +"the :attr:`~defaultdict.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 "" #: library/collections.rst:815 @@ -1056,8 +1059,8 @@ msgstr "" #: library/collections.rst:828 msgid "" -"Setting the :attr:`~defaultdict.default_factory` to :class:`set` makes the :" -"class:`defaultdict` useful for building a dictionary of sets:" +"Setting the :attr:`~defaultdict.default_factory` to :class:`set` makes " +"the :class:`defaultdict` useful for building a dictionary of sets:" msgstr "" #: library/collections.rst:841 @@ -1077,8 +1080,9 @@ 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." +"helpful docstring (with typename and field_names) and a " +"helpful :meth:`__repr__` method which lists the tuple contents in a " +"``name=value`` format." msgstr "" #: library/collections.rst:855 @@ -1092,8 +1096,9 @@ msgstr "" 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*." +"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 "" #: library/collections.rst:865 @@ -1290,8 +1295,8 @@ msgstr "" #: library/collections.rst:1009 msgid "" -"To retrieve a field whose name is stored in a string, use the :func:" -"`getattr` function:" +"To retrieve a field whose name is stored in a string, use " +"the :func:`getattr` function:" msgstr "" #: library/collections.rst:1015 @@ -1511,16 +1516,16 @@ msgstr "" #: library/collections.rst:1171 msgid "" -"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." +"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 "" #: library/collections.rst:1176 msgid "" -"The items, keys, and values :term:`views ` of :class:" -"`OrderedDict` now support reverse iteration using :func:`reversed`." +"The items, keys, and values :term:`views ` " +"of :class:`OrderedDict` now support reverse iteration using :func:`reversed`." msgstr "" #: library/collections.rst:1180 @@ -1553,8 +1558,8 @@ msgstr "" #: library/collections.rst:1204 msgid "" -"An :class:`OrderedDict` would also be useful for implementing variants of :" -"func:`functools.lru_cache`:" +"An :class:`OrderedDict` would also be useful for implementing variants " +"of :func:`functools.lru_cache`:" msgstr "" #: library/collections.rst:1207 @@ -1637,16 +1642,16 @@ msgstr "" #: library/collections.rst:1313 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 to be used for other purposes." +"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 to be used for other purposes." msgstr "" #: library/collections.rst:1319 msgid "" -"In addition to supporting the methods and operations of mappings, :class:" -"`UserDict` instances provide the following attribute:" +"In addition to supporting the methods and operations of " +"mappings, :class:`UserDict` instances provide the following attribute:" msgstr "" #: library/collections.rst:1324 @@ -1676,22 +1681,22 @@ msgstr "" #: library/collections.rst:1343 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." +"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 "" #: library/collections.rst:1349 msgid "" -"In addition to supporting the methods and operations of mutable sequences, :" -"class:`UserList` instances provide the following attribute:" +"In addition to supporting the methods and operations of mutable " +"sequences, :class:`UserList` instances provide the following attribute:" msgstr "" #: library/collections.rst:1354 msgid "" -"A real :class:`list` object used to store the contents of the :class:" -"`UserList` class." +"A real :class:`list` object used to store the contents of " +"the :class:`UserList` class." msgstr "" #: library/collections.rst:1357 @@ -1735,14 +1740,14 @@ msgstr "" #: library/collections.rst:1387 msgid "" -"In addition to supporting the methods and operations of strings, :class:" -"`UserString` instances provide the following attribute:" +"In addition to supporting the methods and operations of " +"strings, :class:`UserString` instances provide the following attribute:" msgstr "" #: library/collections.rst:1392 msgid "" -"A real :class:`str` object used to store the contents of the :class:" -"`UserString` class." +"A real :class:`str` object used to store the contents of " +"the :class:`UserString` class." msgstr "" #: library/collections.rst:1395 diff --git a/library/colorsys.po b/library/colorsys.po index fbeeede8f..b93743614 100644 --- a/library/colorsys.po +++ b/library/colorsys.po @@ -38,8 +38,8 @@ msgstr "" #: library/colorsys.rst:23 msgid "" "More information about color spaces can be found at https://poynton.ca/" -"ColorFAQ.html and https://www.cambridgeincolour.com/tutorials/color-spaces." -"htm." +"ColorFAQ.html and https://www.cambridgeincolour.com/tutorials/color-" +"spaces.htm." msgstr "" #: library/colorsys.rst:27 diff --git a/library/compileall.po b/library/compileall.po index c6c32d583..5f191a795 100644 --- a/library/compileall.po +++ b/library/compileall.po @@ -135,9 +135,9 @@ msgid "" "values cause hash-based pycs to be generated. Hash-based pycs embed a hash " "of the source file contents rather than a timestamp. See :ref:`pyc-" "invalidation` for more information on how Python validates bytecode cache " -"files at runtime. The default is ``timestamp`` if the :envvar:" -"`SOURCE_DATE_EPOCH` environment variable is not set, and ``checked-hash`` if " -"the ``SOURCE_DATE_EPOCH`` environment variable is set." +"files at runtime. The default is ``timestamp`` if " +"the :envvar:`SOURCE_DATE_EPOCH` environment variable is not set, and " +"``checked-hash`` if the ``SOURCE_DATE_EPOCH`` environment variable is set." msgstr "" #: library/compileall.rst:111 @@ -188,10 +188,10 @@ msgstr "" #: library/compileall.rst:146 msgid "" -"Similarly, the :func:`compile` function respects the :data:`sys." -"pycache_prefix` setting. The generated bytecode cache will only be useful " -"if :func:`compile` is run with the same :data:`sys.pycache_prefix` (if any) " -"that will be used at runtime." +"Similarly, the :func:`compile` function respects " +"the :data:`sys.pycache_prefix` setting. The generated bytecode cache will " +"only be useful if :func:`compile` is run with the " +"same :data:`sys.pycache_prefix` (if any) that will be used at runtime." msgstr "" #: library/compileall.rst:152 @@ -200,9 +200,9 @@ msgstr "" #: library/compileall.rst:156 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." +"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 "" #: library/compileall.rst:160 @@ -264,15 +264,15 @@ msgid "" "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 0, the number of " -"cores in the system is used. If *workers* is lower than ``0``, a :exc:" -"`ValueError` will be raised." +"cores in the system is used. If *workers* is lower than ``0``, " +"a :exc:`ValueError` will be raised." msgstr "" #: library/compileall.rst:268 msgid "" -"*invalidation_mode* should be a member of the :class:`py_compile." -"PycInvalidationMode` enum and controls how the generated pycs are " -"invalidated at runtime." +"*invalidation_mode* should be a member of " +"the :class:`py_compile.PycInvalidationMode` enum and controls how the " +"generated pycs are invalidated at runtime." msgstr "" #: library/compileall.rst:272 @@ -327,8 +327,8 @@ msgstr "" #: library/compileall.rst:234 msgid "" "Added *stripdir*, *prependdir*, *limit_sl_dest* and *hardlink_dupes* " -"arguments. Default value of *maxlevels* was changed from ``10`` to ``sys." -"getrecursionlimit()``" +"arguments. Default value of *maxlevels* was changed from ``10`` to " +"``sys.getrecursionlimit()``" msgstr "" #: library/compileall.rst:240 @@ -371,9 +371,9 @@ msgstr "" #: library/compileall.rst:302 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``." +"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 "" #: library/compileall.rst:323 diff --git a/library/concurrent.futures.po b/library/concurrent.futures.po index ec2f9e06f..f86ab4cb3 100644 --- a/library/concurrent.futures.po +++ b/library/concurrent.futures.po @@ -34,10 +34,10 @@ msgstr "" #: 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." +"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 "" #: includes/wasm-notavail.rst:3 @@ -91,11 +91,11 @@ msgstr "" #: library/concurrent.futures.rst:51 msgid "" -"The returned iterator raises a :exc:`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." +"The returned iterator raises a :exc:`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." msgstr "" #: library/concurrent.futures.rst:57 @@ -121,9 +121,9 @@ msgstr "" #: library/concurrent.futures.rst:73 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`." +"the currently pending futures are done executing. Calls " +"to :meth:`Executor.submit` and :meth:`Executor.map` made after shutdown will " +"raise :exc:`RuntimeError`." msgstr "" #: library/concurrent.futures.rst:78 @@ -153,9 +153,10 @@ msgstr "" #: library/concurrent.futures.rst:95 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``)::" +"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 "" #: library/concurrent.futures.rst:100 @@ -251,17 +252,17 @@ msgstr "" #: library/concurrent.futures.rst:166 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`." +"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 "" #: library/concurrent.futures.rst:174 msgid "" -"Added the *thread_name_prefix* parameter to allow users to control the :" -"class:`threading.Thread` names for worker threads created by the pool for " -"easier debugging." +"Added the *thread_name_prefix* parameter to allow users to control " +"the :class:`threading.Thread` names for worker threads created by the pool " +"for easier debugging." msgstr "" #: library/concurrent.futures.rst:179 library/concurrent.futures.rst:283 @@ -324,11 +325,11 @@ msgstr "" #: library/concurrent.futures.rst:229 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." +"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 "" #: library/concurrent.futures.rst:236 @@ -381,10 +382,10 @@ msgstr "" #: library/concurrent.futures.rst:272 msgid "" -"When one of the worker processes terminates abruptly, a :exc:`~concurrent." -"futures.process.BrokenProcessPool` error is now raised. Previously, " -"behaviour was undefined but operations on the executor or its futures would " -"often freeze or deadlock." +"When one of the worker processes terminates abruptly, " +"a :exc:`~concurrent.futures.process.BrokenProcessPool` error is now raised. " +"Previously, behaviour was undefined but operations on the executor or its " +"futures would often freeze or deadlock." msgstr "" #: library/concurrent.futures.rst:279 @@ -398,8 +399,8 @@ msgid "" "The default :mod:`multiprocessing` start method (see :ref:`multiprocessing-" "start-methods`) will change away from *fork* in Python 3.14. Code that " "requires *fork* be used for their :class:`ProcessPoolExecutor` should " -"explicitly specify that by passing a ``mp_context=multiprocessing." -"get_context(\"fork\")`` parameter." +"explicitly specify that by passing a " +"``mp_context=multiprocessing.get_context(\"fork\")`` parameter." msgstr "" #: library/concurrent.futures.rst:293 @@ -410,11 +411,12 @@ msgstr "" #: library/concurrent.futures.rst:297 msgid "" -"On POSIX systems, if your application has multiple threads and the :mod:" -"`multiprocessing` context uses the ``\"fork\"`` start method: The :func:`os." -"fork` function called internally to spawn workers may raise a :exc:" -"`DeprecationWarning`. Pass a *mp_context* configured to use a different " -"start method. See the :func:`os.fork` documentation for further explanation." +"On POSIX systems, if your application has multiple threads and " +"the :mod:`multiprocessing` context uses the ``\"fork\"`` start method: " +"The :func:`os.fork` function called internally to spawn workers may raise " +"a :exc:`DeprecationWarning`. Pass a *mp_context* configured to use a " +"different start method. See the :func:`os.fork` documentation for further " +"explanation." msgstr "" #: library/concurrent.futures.rst:308 @@ -554,8 +556,8 @@ msgstr "" #: library/concurrent.futures.rst:421 msgid "" -"The following :class:`Future` methods are meant for use in unit tests and :" -"class:`Executor` implementations." +"The following :class:`Future` methods are meant for use in unit tests " +"and :class:`Executor` implementations." msgstr "" #: library/concurrent.futures.rst:426 @@ -567,8 +569,8 @@ msgstr "" #: library/concurrent.futures.rst:430 msgid "" -"If the method returns ``False`` then the :class:`Future` was cancelled, i." -"e. :meth:`Future.cancel` was called and returned ``True``. Any threads " +"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 "" @@ -582,8 +584,9 @@ msgstr "" #: library/concurrent.futures.rst:439 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." +"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 "" #: library/concurrent.futures.rst:445 @@ -599,14 +602,14 @@ msgstr "" #: library/concurrent.futures.rst:451 library/concurrent.futures.rst:464 msgid "" -"This method raises :exc:`concurrent.futures.InvalidStateError` if the :class:" -"`Future` is already done." +"This method raises :exc:`concurrent.futures.InvalidStateError` if " +"the :class:`Future` is already done." msgstr "" #: library/concurrent.futures.rst:458 msgid "" -"Sets the result of the work associated with the :class:`Future` to the :" -"class:`Exception` *exception*." +"Sets the result of the work associated with the :class:`Future` to " +"the :class:`Exception` *exception*." msgstr "" #: library/concurrent.futures.rst:470 @@ -615,13 +618,13 @@ msgstr "" #: library/concurrent.futures.rst:474 msgid "" -"Wait for the :class:`Future` instances (possibly created by different :class:" -"`Executor` instances) given by *fs* to complete. Duplicate futures given to " -"*fs* are removed and will be returned only once. Returns a named 2-tuple of " -"sets. The first set, named ``done``, contains the futures that completed " -"(finished or cancelled futures) before the wait completed. The second set, " -"named ``not_done``, contains the futures that did not complete (pending or " -"running futures)." +"Wait for the :class:`Future` instances (possibly created by " +"different :class:`Executor` instances) given by *fs* to complete. Duplicate " +"futures given to *fs* are removed and will be returned only once. Returns a " +"named 2-tuple of sets. The first set, named ``done``, contains the futures " +"that completed (finished or cancelled futures) before the wait completed. " +"The second set, named ``not_done``, contains the futures that did not " +"complete (pending or running futures)." msgstr "" #: library/concurrent.futures.rst:482 @@ -652,8 +655,8 @@ msgstr "" #: library/concurrent.futures.rst:499 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`." +"If no future raises an exception then it is equivalent " +"to :const:`ALL_COMPLETED`." msgstr "" #: library/concurrent.futures.rst:504 @@ -717,14 +720,15 @@ msgstr "" #: library/concurrent.futures.rst:564 msgid "" "Derived from :exc:`~concurrent.futures.BrokenExecutor`, this exception class " -"is raised when one of the workers of a :class:`~concurrent.futures." -"ThreadPoolExecutor` has failed initializing." +"is raised when one of the workers of " +"a :class:`~concurrent.futures.ThreadPoolExecutor` has failed initializing." msgstr "" #: library/concurrent.futures.rst:575 msgid "" -"Derived from :exc:`~concurrent.futures.BrokenExecutor` (formerly :exc:" -"`RuntimeError`), this exception class is raised when one of the workers of " -"a :class:`~concurrent.futures.ProcessPoolExecutor` has terminated in a non-" -"clean fashion (for example, if it was killed from the outside)." +"Derived from :exc:`~concurrent.futures.BrokenExecutor` " +"(formerly :exc:`RuntimeError`), this exception class is raised when one of " +"the workers of a :class:`~concurrent.futures.ProcessPoolExecutor` has " +"terminated in a non-clean fashion (for example, if it was killed from the " +"outside)." msgstr "" diff --git a/library/configparser.po b/library/configparser.po index 4bd3927b4..0ea7cd971 100644 --- a/library/configparser.po +++ b/library/configparser.po @@ -176,12 +176,12 @@ msgstr "" #: library/configparser.rst:967 msgid "" -"It is possible to read several configurations into a single :class:" -"`ConfigParser`, where the most recently added configuration has the highest " -"priority. Any conflicting keys are taken from the more recent configuration " -"while the previously existing keys are retained. The example below reads in " -"an ``override.ini`` file, which will override any conflicting keys from the " -"``example.ini`` file." +"It is possible to read several configurations into a " +"single :class:`ConfigParser`, where the most recently added configuration " +"has the highest priority. Any conflicting keys are taken from the more " +"recent configuration while the previously existing keys are retained. The " +"example below reads in an ``override.ini`` file, which will override any " +"conflicting keys from the ``example.ini`` file." msgstr "" #: library/configparser.rst:974 @@ -296,10 +296,10 @@ msgstr "" #: library/configparser.rst:241 msgid "" -"One more thing to be aware of is that the parser-level :meth:`~ConfigParser." -"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:" +"One more thing to be aware of is that the parser-" +"level :meth:`~ConfigParser.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 "" #: library/configparser.rst:246 @@ -311,9 +311,9 @@ msgstr "" #: library/configparser.rst:252 msgid "" -"The same ``fallback`` argument can be used with the :meth:`~ConfigParser." -"getint`, :meth:`~ConfigParser.getfloat` and :meth:`~ConfigParser.getboolean` " -"methods, for example:" +"The same ``fallback`` argument can be used with " +"the :meth:`~ConfigParser.getint`, :meth:`~ConfigParser.getfloat` " +"and :meth:`~ConfigParser.getboolean` methods, for example:" msgstr "" #: library/configparser.rst:256 @@ -450,8 +450,8 @@ msgstr "" #: library/configparser.rst:370 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/" +"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 "" @@ -460,9 +460,9 @@ 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)." +"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 "" #: library/configparser.rst:385 @@ -515,8 +515,8 @@ msgstr "" #: library/configparser.rst:425 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 " +"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 "" @@ -532,9 +532,9 @@ msgstr "" #: library/configparser.rst:436 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:" +"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 "" #: library/configparser.rst:441 @@ -554,8 +554,8 @@ msgstr "" #: library/configparser.rst:449 msgid "" -"All sections include ``DEFAULTSECT`` values as well which means that ``." -"clear()`` on a section may not leave the section visibly empty. This is " +"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 " @@ -589,10 +589,10 @@ msgstr "" 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)." +"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 "" #: library/configparser.rst:475 @@ -635,8 +635,8 @@ msgstr "" #: library/configparser.rst:499 msgid "" -"Hint: if you want to specify default values for a specific section, use :" -"meth:`~ConfigParser.read_dict` before you read the actual file." +"Hint: if you want to specify default values for a specific section, " +"use :meth:`~ConfigParser.read_dict` before you read the actual file." msgstr "" #: library/configparser.rst:502 @@ -739,8 +739,8 @@ msgstr "" #: library/configparser.rst:577 msgid "" -"See also the *space_around_delimiters* argument to :meth:`ConfigParser." -"write`." +"See also the *space_around_delimiters* argument " +"to :meth:`ConfigParser.write`." msgstr "" #: library/configparser.rst:580 @@ -826,9 +826,10 @@ msgstr "" #: library/configparser.rst:643 msgid "" "When set to ``True``, the parser will not allow for any section or option " -"duplicates while reading from a single source (using :meth:`~ConfigParser." -"read_file`, :meth:`~ConfigParser.read_string` or :meth:`~ConfigParser." -"read_dict`). It is recommended to use strict parsers in new applications." +"duplicates while reading from a single source " +"(using :meth:`~ConfigParser.read_file`, :meth:`~ConfigParser.read_string` " +"or :meth:`~ConfigParser.read_dict`). It is recommended to use strict " +"parsers in new applications." msgstr "" #: library/configparser.rst:648 @@ -884,9 +885,9 @@ msgid "" "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)." +"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 "" #: library/configparser.rst:689 @@ -899,8 +900,8 @@ msgid "" "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``." +"`dedicated documentation section <#interpolation-of-" +"values>`_. :class:`RawConfigParser` has a default value of ``None``." msgstr "" #: library/configparser.rst:698 @@ -914,9 +915,9 @@ msgid "" "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 " +"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 "" @@ -1188,13 +1189,13 @@ msgstr "" 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." +"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 "" #: library/configparser.rst:942 @@ -1218,11 +1219,11 @@ msgstr "" #: library/configparser.rst:955 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." +"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 "" #: library/configparser.rst:961 @@ -1295,9 +1296,9 @@ msgstr "" #: library/configparser.rst:1047 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." +"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 "" #: library/configparser.rst:1054 @@ -1321,8 +1322,8 @@ msgstr "" msgid "" "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::" +"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 "" #: library/configparser.rst:1072 @@ -1440,9 +1441,9 @@ msgid "" "``'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*." +"insensitive manner. Any other value will cause it to " +"raise :exc:`ValueError`. See :meth:`get` for explanation of *raw*, *vars* " +"and *fallback*." msgstr "" #: library/configparser.rst:1176 @@ -1454,8 +1455,8 @@ msgstr "" #: library/configparser.rst:1179 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." +"given *section*. Optional arguments have the same meaning as for " +"the :meth:`get` method." msgstr "" #: library/configparser.rst:1183 @@ -1532,9 +1533,9 @@ msgstr "" #: library/configparser.rst:1248 msgid "" -"The maximum depth for recursive interpolation for :meth:`~configparser." -"ConfigParser.get` when the *raw* parameter is false. This is relevant only " -"when the default *interpolation* is used." +"The maximum depth for recursive interpolation " +"for :meth:`~configparser.ConfigParser.get` when the *raw* parameter is " +"false. This is relevant only when the default *interpolation* is used." msgstr "" #: library/configparser.rst:1256 @@ -1572,9 +1573,9 @@ msgstr "" #: library/configparser.rst:1293 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 " +"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 "" @@ -1608,8 +1609,8 @@ msgstr "" #: library/configparser.rst:1325 msgid "" -"Added the optional *source* and *lineno* attributes and parameters to :meth:" -"`!__init__`." +"Added the optional *source* and *lineno* attributes and parameters " +"to :meth:`!__init__`." msgstr "" #: library/configparser.rst:1332 @@ -1635,8 +1636,8 @@ msgstr "" #: library/configparser.rst:1352 msgid "" "Exception raised when string interpolation cannot be completed because the " -"number of iterations exceeds :const:`MAX_INTERPOLATION_DEPTH`. Subclass of :" -"exc:`InterpolationError`." +"number of iterations exceeds :const:`MAX_INTERPOLATION_DEPTH`. Subclass " +"of :exc:`InterpolationError`." msgstr "" #: library/configparser.rst:1359 diff --git a/library/constants.po b/library/constants.po index 22f3607c2..b4606340e 100644 --- a/library/constants.po +++ b/library/constants.po @@ -46,14 +46,14 @@ msgstr "" #: library/constants.rst:30 msgid "" -"A special value which should be returned by the binary special methods (e." -"g. :meth:`~object.__eq__`, :meth:`~object.__lt__`, :meth:`~object.__add__`, :" -"meth:`~object.__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:`~object.__imul__`, :meth:`~object." -"__iand__`, etc.) for the same purpose. It should not be evaluated in a " -"boolean context. :data:`!NotImplemented` is the sole instance of the :data:" -"`types.NotImplementedType` type." +"A special value which should be returned by the binary special methods " +"(e.g. :meth:`~object.__eq__`, :meth:`~object.__lt__`, :meth:`~object.__add__`, :meth:`~object.__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:`~object.__imul__`, :meth:`~object.__iand__`, etc.) for the same " +"purpose. It should not be evaluated in a boolean context. :data:`!" +"NotImplemented` is the sole instance of the :data:`types.NotImplementedType` " +"type." msgstr "" #: library/constants.rst:40 @@ -74,8 +74,8 @@ msgstr "" #: library/constants.rst:51 msgid "" "``NotImplementedError`` and :data:`!NotImplemented` are not interchangeable, " -"even though they have similar names and purposes. See :exc:" -"`NotImplementedError` for details on when to use it." +"even though they have similar names and purposes. " +"See :exc:`NotImplementedError` for details on when to use it." msgstr "" #: library/constants.rst:55 @@ -102,8 +102,8 @@ msgstr "" #: library/constants.rst:77 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." +"cannot be reassigned (assignments to them, even as an attribute name, " +"raise :exc:`SyntaxError`), so they can be considered \"true\" constants." msgstr "" #: library/constants.rst:85 diff --git a/library/contextlib.po b/library/contextlib.po index f65e99d39..3b5575444 100644 --- a/library/contextlib.po +++ b/library/contextlib.po @@ -27,9 +27,9 @@ msgstr "" #: 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`." +"This module provides utilities for common tasks involving " +"the :keyword:`with` statement. For more information see " +"also :ref:`typecontextmanager` and :ref:`context-managers`." msgstr "" #: library/contextlib.rst:17 @@ -42,36 +42,38 @@ msgstr "" #: 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`." +"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 "" #: library/contextlib.rst:34 msgid "" -"An :term:`abstract base class` for classes that implement :meth:`object." -"__aenter__` and :meth:`object.__aexit__`. A default implementation for :meth:" -"`object.__aenter__` is provided which returns ``self`` while :meth:`object." -"__aexit__` is an abstract method which by default returns ``None``. See also " -"the definition of :ref:`async-context-managers`." +"An :term:`abstract base class` for classes that " +"implement :meth:`object.__aenter__` and :meth:`object.__aexit__`. A default " +"implementation for :meth:`object.__aenter__` is provided which returns " +"``self`` while :meth:`object.__aexit__` is an abstract method which by " +"default returns ``None``. See also the definition of :ref:`async-context-" +"managers`." msgstr "" #: library/contextlib.rst:46 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:`~object.__enter__` and :meth:`~object." -"__exit__` methods." +"create a class or separate :meth:`~object.__enter__` " +"and :meth:`~object.__exit__` methods." msgstr "" #: library/contextlib.rst:50 msgid "" "While many objects natively support use in with statements, sometimes a " "resource needs to be managed that isn't a context manager in its own right, " -"and doesn't implement a ``close()`` method for use with ``contextlib." -"closing``" +"and doesn't implement a ``close()`` method for use with " +"``contextlib.closing``" msgstr "" #: library/contextlib.rst:54 @@ -115,18 +117,18 @@ msgstr "" #: library/contextlib.rst:79 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." +"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 "" #: library/contextlib.rst:91 @@ -146,8 +148,8 @@ msgstr "" #: library/contextlib.rst:104 msgid "" -"Similar to :func:`~contextlib.contextmanager`, but creates an :ref:" -"`asynchronous context manager `." +"Similar to :func:`~contextlib.contextmanager`, but creates " +"an :ref:`asynchronous context manager `." msgstr "" #: library/contextlib.rst:107 @@ -155,8 +157,8 @@ msgid "" "This function is a :term:`decorator` that can be used to define a factory " "function for :keyword:`async with` statement asynchronous context managers, " "without needing to create a class or separate :meth:`~object.__aenter__` " -"and :meth:`~object.__aexit__` methods. It must be applied to an :term:" -"`asynchronous generator` function." +"and :meth:`~object.__aexit__` methods. It must be applied to " +"an :term:`asynchronous generator` function." msgstr "" #: library/contextlib.rst:113 @@ -259,10 +261,11 @@ msgstr "" #: library/contextlib.rst:187 msgid "" "Most types managing resources support the :term:`context manager` protocol, " -"which closes *thing* on leaving the :keyword:`with` statement. As such, :" -"func:`!closing` is most useful for third party types that don't support " -"context managers. This example is purely for illustration purposes, as :func:" -"`~urllib.request.urlopen` would normally be used in a context manager." +"which closes *thing* on leaving the :keyword:`with` statement. As " +"such, :func:`!closing` is most useful for third party types that don't " +"support context managers. This example is purely for illustration purposes, " +"as :func:`~urllib.request.urlopen` would normally be used in a context " +"manager." msgstr "" #: library/contextlib.rst:196 @@ -424,17 +427,17 @@ msgstr "" #: library/contextlib.rst:315 msgid "" -"If the code within the :keyword:`!with` block raises a :exc:" -"`BaseExceptionGroup`, suppressed exceptions are removed from the group. Any " -"exceptions of the group which are not suppressed are re-raised in a new " -"group which is created using the original group's :meth:`~BaseExceptionGroup." -"derive` method." +"If the code within the :keyword:`!with` block raises " +"a :exc:`BaseExceptionGroup`, suppressed exceptions are removed from the " +"group. Any exceptions of the group which are not suppressed are re-raised " +"in a new group which is created using the original " +"group's :meth:`~BaseExceptionGroup.derive` method." msgstr "" #: library/contextlib.rst:323 msgid "" -"``suppress`` now supports suppressing exceptions raised as part of a :exc:" -"`BaseExceptionGroup`." +"``suppress`` now supports suppressing exceptions raised as part of " +"a :exc:`BaseExceptionGroup`." msgstr "" #: library/contextlib.rst:329 @@ -452,10 +455,10 @@ msgstr "" #: library/contextlib.rst:335 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. The replacement stream is returned from the " -"``__enter__`` method and so is available as the target of the :keyword:" -"`with` statement::" +"You can capture that output in a string by redirecting the output to " +"an :class:`io.StringIO` object. The replacement stream is returned from the " +"``__enter__`` method and so is available as the target of " +"the :keyword:`with` statement::" msgstr "" #: library/contextlib.rst:341 @@ -498,8 +501,8 @@ msgstr "" #: library/contextlib.rst:369 msgid "" -"Similar to :func:`~contextlib.redirect_stdout` but redirecting :data:`sys." -"stderr` to another file or file-like object." +"Similar to :func:`~contextlib.redirect_stdout` but " +"redirecting :data:`sys.stderr` to another file or file-like object." msgstr "" #: library/contextlib.rst:379 @@ -766,15 +769,16 @@ msgstr "" #: library/contextlib.rst:571 msgid "" "As ``__enter__`` is *not* invoked, this method can be used to cover part of " -"an :meth:`~object.__enter__` implementation with a context manager's own :" -"meth:`~object.__exit__` method." +"an :meth:`~object.__enter__` implementation with a context manager's " +"own :meth:`~object.__exit__` method." msgstr "" #: library/contextlib.rst:575 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:`~object." -"__exit__` method and adds it directly to the callback stack." +"a callback with the same signature as a context " +"manager's :meth:`~object.__exit__` method and adds it directly to the " +"callback stack." msgstr "" #: library/contextlib.rst:579 @@ -842,9 +846,10 @@ msgstr "" #: library/contextlib.rst:624 msgid "" -"An :ref:`asynchronous context manager `, similar to :" -"class:`ExitStack`, that supports combining both synchronous and asynchronous " -"context managers, as well as having coroutines for cleanup logic." +"An :ref:`asynchronous context manager `, similar " +"to :class:`ExitStack`, that supports combining both synchronous and " +"asynchronous context managers, as well as having coroutines for cleanup " +"logic." msgstr "" #: library/contextlib.rst:629 @@ -942,10 +947,10 @@ msgstr "" #: library/contextlib.rst:698 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::" +"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 "" #: library/contextlib.rst:704 @@ -963,12 +968,12 @@ msgstr "" #: library/contextlib.rst:713 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." +"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 "" #: library/contextlib.rst:723 @@ -978,8 +983,8 @@ msgstr "" #: library/contextlib.rst:725 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:`~object.__enter__` implementation fail." +"useful in cleaning up an already allocated resource if later steps in " +"the :meth:`~object.__enter__` implementation fail." msgstr "" #: library/contextlib.rst:729 @@ -1109,8 +1114,8 @@ msgstr "" #: library/contextlib.rst:822 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::" +"function, then it is still possible to use the decorator form " +"of :meth:`ExitStack.callback` to declare the resource cleanup in advance::" msgstr "" #: library/contextlib.rst:827 @@ -1196,9 +1201,9 @@ msgstr "" #: library/contextlib.rst:882 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:" -"`~object.__enter__`. If that value is needed, then it is still necessary to " -"use an explicit ``with`` statement." +"function decorators: there's no way to access the return value " +"of :meth:`~object.__enter__`. If that value is needed, then it is still " +"necessary to use an explicit ``with`` statement." msgstr "" #: library/contextlib.rst:889 @@ -1315,8 +1320,8 @@ msgstr "" 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." +"as it makes a global modification to the system state by " +"binding :data:`sys.stdout` to a different stream." msgstr "" #: library/contextlib.rst:979 @@ -1336,15 +1341,16 @@ msgstr "" #: library/contextlib.rst:988 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)." +"context manager (for a reentrant lock, it is necessary to " +"use :class:`threading.RLock` instead)." msgstr "" #: library/contextlib.rst:992 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::" +"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 "" #: library/contextlib.rst:997 diff --git a/library/contextvars.po b/library/contextvars.po index 38d42bfdc..d6176fa01 100644 --- a/library/contextvars.po +++ b/library/contextvars.po @@ -31,9 +31,9 @@ msgstr "" #: library/contextvars.rst:17 msgid "" -"Context managers that have state should use Context Variables instead of :" -"func:`threading.local` to prevent their state from bleeding to other code " -"unexpectedly, when used in concurrent code." +"Context managers that have state should use Context Variables instead " +"of :func:`threading.local` to prevent their state from bleeding to other " +"code unexpectedly, when used in concurrent code." msgstr "" #: library/contextvars.rst:21 @@ -59,9 +59,9 @@ msgstr "" #: library/contextvars.rst:38 msgid "" -"The optional keyword-only *default* parameter is returned by :meth:" -"`ContextVar.get` when no value for the variable is found in the current " -"context." +"The optional keyword-only *default* parameter is returned " +"by :meth:`ContextVar.get` when no value for the variable is found in the " +"current context." msgstr "" #: library/contextvars.rst:42 @@ -119,8 +119,8 @@ msgstr "" #: library/contextvars.rst:82 msgid "" -"Reset the context variable to the value it had before the :meth:`ContextVar." -"set` that created the *token* was used." +"Reset the context variable to the value it had before " +"the :meth:`ContextVar.set` that created the *token* was used." msgstr "" #: library/contextvars.rst:85 @@ -154,9 +154,9 @@ msgstr "" #: library/contextvars.rst:111 msgid "" -"A read-only property. Set to the value the variable had before the :meth:" -"`ContextVar.set` method call that created the token. It points to :attr:" -"`Token.MISSING` if the variable was not set before the call." +"A read-only property. Set to the value the variable had before " +"the :meth:`ContextVar.set` method call that created the token. It points " +"to :attr:`Token.MISSING` if the variable was not set before the call." msgstr "" #: library/contextvars.rst:118 diff --git a/library/copy.po b/library/copy.po index 5a4203d2f..4f8cb42a7 100644 --- a/library/copy.po +++ b/library/copy.po @@ -107,8 +107,8 @@ msgid "" "This module does not copy types like module, method, stack trace, stack " "frame, file, socket, window, 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." +"unchanged; this is compatible with the way these are treated by " +"the :mod:`pickle` module." msgstr "" #: library/copy.rst:67 @@ -133,10 +133,10 @@ msgid "" "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. The memo dictionary should be treated as an " -"opaque object." +"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. The memo dictionary should be treated as " +"an opaque object." msgstr "" #: library/copy.rst:94 diff --git a/library/copyreg.po b/library/copyreg.po index 42607ffbe..11a01a3f8 100644 --- a/library/copyreg.po +++ b/library/copyreg.po @@ -43,8 +43,9 @@ msgstr "" msgid "" "Declares that *function* should be used as a \"reduction\" function for " "objects of type *type*. *function* must return either a string or a tuple " -"containing between two and six elements. See the :attr:`~pickle.Pickler." -"dispatch_table` for more details on the interface of *function*." +"containing between two and six elements. See " +"the :attr:`~pickle.Pickler.dispatch_table` for more details on the interface " +"of *function*." msgstr "" #: library/copyreg.rst:35 diff --git a/library/crypt.po b/library/crypt.po index f3c55a8c2..51c8f19ff 100644 --- a/library/crypt.po +++ b/library/crypt.po @@ -169,8 +169,8 @@ msgstr "" #: library/crypt.rst:135 msgid "" -"The return value is a string suitable for passing as the *salt* argument to :" -"func:`crypt`." +"The return value is a string suitable for passing as the *salt* argument " +"to :func:`crypt`." msgstr "" #: library/crypt.rst:138 @@ -179,8 +179,8 @@ msgid "" "``METHOD_SHA512`` and ``METHOD_BLOWFISH``. For ``METHOD_SHA256`` and " "``METHOD_SHA512`` it must be an integer between ``1000`` and " "``999_999_999``, the default is ``5000``. For ``METHOD_BLOWFISH`` it must " -"be a power of two between ``16`` (2\\ :sup:`4`) and ``2_147_483_648`` (2\\ :" -"sup:`31`), the default is ``4096`` (2\\ :sup:`12`)." +"be a power of two between ``16`` (2\\ :sup:`4`) and ``2_147_483_648`` " +"(2\\ :sup:`31`), the default is ``4096`` (2\\ :sup:`12`)." msgstr "" #: library/crypt.rst:148 @@ -194,8 +194,8 @@ msgstr "" #: library/crypt.rst:155 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)::" +"operation is needed to limit exposure to timing " +"attacks. :func:`hmac.compare_digest` is suitable for this purpose)::" msgstr "" #: library/crypt.rst:159 diff --git a/library/csv.po b/library/csv.po index 7cbcc1188..eeae096f3 100644 --- a/library/csv.po +++ b/library/csv.po @@ -116,12 +116,12 @@ msgid "" "object with a :meth:`~io.TextIOBase.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 dialects and formatting parameters, see " -"the :ref:`csv-fmt-params` section. To make it as easy as possible to " +"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 dialects and formatting parameters, " +"see the :ref:`csv-fmt-params` section. 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 " @@ -150,8 +150,8 @@ msgstr "" #: library/csv.rst:127 msgid "" -"Delete the dialect associated with *name* from the dialect registry. An :" -"exc:`Error` is raised if *name* is not a registered dialect name." +"Delete the dialect associated with *name* from the dialect registry. " +"An :exc:`Error` is raised if *name* is not a registered dialect name." msgstr "" #: library/csv.rst:133 @@ -203,8 +203,8 @@ msgstr "" #: library/csv.rst:170 msgid "" -"All other optional or keyword arguments are passed to the underlying :class:" -"`reader` instance." +"All other optional or keyword arguments are passed to the " +"underlying :class:`reader` instance." msgstr "" #: library/csv.rst:217 @@ -246,10 +246,10 @@ msgid "" "written if the dictionary is missing a key in *fieldnames*. If the " "dictionary passed to the :meth:`~csvwriter.writerow` method contains a key " "not found in *fieldnames*, the optional *extrasaction* parameter indicates " -"what action to take. If it is set to ``'raise'``, the default value, 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." +"what action to take. If it is set to ``'raise'``, the default value, " +"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 "" #: library/csv.rst:214 @@ -277,8 +277,8 @@ msgid "" "The :class:`Dialect` class is a container class whose attributes contain " "information for how to handle doublequotes, whitespace, delimiters, etc. Due " "to the lack of a strict CSV specification, different applications produce " -"subtly different CSV data. :class:`Dialect` instances define how :class:" -"`reader` and :class:`writer` instances behave." +"subtly different CSV data. :class:`Dialect` instances define " +"how :class:`reader` and :class:`writer` instances behave." msgstr "" #: library/csv.rst:241 @@ -333,10 +333,10 @@ msgstr "" #: library/csv.rst:288 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. Inspecting " -"each column, one of two key criteria will be considered to estimate if the " -"sample contains a header:" +"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. Inspecting each column, one of two key criteria will be considered " +"to estimate if the sample contains a header:" msgstr "" #: library/csv.rst:293 @@ -463,12 +463,12 @@ 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 containing various " -"attributes describing the format of the CSV file. 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." +"attributes describing the format of the CSV file. 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 "" #: library/csv.rst:396 @@ -483,15 +483,15 @@ msgstr "" #: library/csv.rst:406 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`." +"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 "" #: library/csv.rst:411 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." +"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 "" #: library/csv.rst:417 @@ -556,8 +556,8 @@ msgstr "" #: library/csv.rst:469 msgid "" -"Reader objects (:class:`DictReader` instances and objects returned by the :" -"func:`reader` function) have the following public methods:" +"Reader objects (:class:`DictReader` instances and objects returned by " +"the :func:`reader` function) have the following public methods:" msgstr "" #: library/csv.rst:474 @@ -647,8 +647,8 @@ msgstr "" #: library/csv.rst:548 msgid "" -":meth:`writeheader` now also returns the value returned by the :meth:" -"`csvwriter.writerow` method it uses internally." +":meth:`writeheader` now also returns the value returned by " +"the :meth:`csvwriter.writerow` method it uses internally." msgstr "" #: library/csv.rst:556 @@ -696,9 +696,9 @@ msgstr "" #: library/csv.rst:581 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.getencoding`). To decode a file using a different encoding, use the " -"``encoding`` argument of open::" +"default be decoded into unicode using the system default encoding " +"(see :func:`locale.getencoding`). To decode a file using a different " +"encoding, use the ``encoding`` argument of open::" msgstr "" #: library/csv.rst:586 @@ -769,8 +769,8 @@ 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." +"safe to specify ``newline=''``, since the csv module does its own " +"(:term:`universal `) newline handling." msgstr "" #: library/csv.rst:11 diff --git a/library/ctypes.po b/library/ctypes.po index 8a16f99e3..687f4325b 100644 --- a/library/ctypes.po +++ b/library/ctypes.po @@ -45,9 +45,10 @@ msgstr "" #: library/ctypes.rst:27 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." +"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 "" #: library/ctypes.rst:35 @@ -73,8 +74,8 @@ msgstr "" #: library/ctypes.rst:48 msgid "" -"Windows errors used to raise :exc:`WindowsError`, which is now an alias of :" -"exc:`OSError`." +"Windows errors used to raise :exc:`WindowsError`, which is now an alias " +"of :exc:`OSError`." msgstr "" #: library/ctypes.rst:53 @@ -178,8 +179,8 @@ msgstr "" #: library/ctypes.rst:125 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::" +"identifiers, like ``\"??2@YAPAXI@Z\"``. In this case you have to " +"use :func:`getattr` to retrieve the function::" msgstr "" #: library/ctypes.rst:129 @@ -298,10 +299,10 @@ 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:expr:" -"`char *` or :c:expr:`wchar_t *`). Python integers are passed as the " -"platforms default C :c:expr:`int` type, their value is masked to fit into " -"the C type." +"are passed as pointer to the memory block that contains their data " +"(:c:expr:`char *` or :c:expr:`wchar_t *`). Python integers are passed as " +"the platforms default C :c:expr:`int` type, their value is masked to fit " +"into the C type." msgstr "" #: library/ctypes.rst:205 @@ -577,10 +578,10 @@ msgstr "" #: library/ctypes.rst:292 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)::" +"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 "" #: library/ctypes.rst:297 @@ -604,11 +605,11 @@ msgstr "" #: library/ctypes.rst:312 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::" +"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 "" #: library/ctypes.rst:319 @@ -647,9 +648,9 @@ msgstr "" #: library/ctypes.rst:347 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*::" +"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 "" #: library/ctypes.rst:351 @@ -799,13 +800,13 @@ msgstr "" msgid "" "If you have defined your own classes which you pass to function calls, you " "have to implement a :meth:`~_CData.from_param` class method for them to be " -"able to use them in the :attr:`~_CFuncPtr.argtypes` sequence. The :meth:" -"`~_CData.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:`!" +"able to use them in the :attr:`~_CFuncPtr.argtypes` sequence. " +"The :meth:`~_CData.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 "" @@ -822,9 +823,10 @@ msgstr "" #: library/ctypes.rst:482 msgid "" -"The C prototype of :c:func:`time` is ``time_t time(time_t *)``. Because :c:" -"type:`time_t` might be of a different type than the default return type :c:" -"expr:`int`, you should specify the :attr:`!restype` attribute::" +"The C prototype of :c:func:`time` is ``time_t time(time_t *)``. " +"Because :c:type:`time_t` might be of a different type than the default " +"return type :c:expr:`int`, you should specify the :attr:`!restype` " +"attribute::" msgstr "" #: library/ctypes.rst:486 @@ -954,10 +956,10 @@ msgstr "" #: library/ctypes.rst:571 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::" +"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 "" #: library/ctypes.rst:577 @@ -981,11 +983,11 @@ msgstr "" #: library/ctypes.rst:595 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:`~Structure._fields_` attribute. :attr:`!" -"_fields_` must be a list of *2-tuples*, containing a *field name* and a " -"*field type*." +"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:`~Structure._fields_` " +"attribute. :attr:`!_fields_` must be a list of *2-tuples*, containing a " +"*field name* and a *field type*." msgstr "" #: library/ctypes.rst:600 @@ -1089,8 +1091,8 @@ msgstr "" #: library/ctypes.rst:667 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 by specifying a :" -"attr:`~Structure._pack_` class attribute in the subclass definition. This " +"compiler does it. It is possible to override this behavior by specifying " +"a :attr:`~Structure._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 "" @@ -1098,10 +1100,10 @@ msgstr "" #: library/ctypes.rst:673 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." +"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 "" #: library/ctypes.rst:683 @@ -1210,8 +1212,8 @@ msgstr "" #: library/ctypes.rst:755 msgid "" -"Pointer instances are created by calling the :func:`pointer` function on a :" -"mod:`ctypes` type::" +"Pointer instances are created by calling the :func:`pointer` function on " +"a :mod:`ctypes` type::" msgstr "" #: library/ctypes.rst:758 @@ -1506,8 +1508,8 @@ msgstr "" #: library/ctypes.rst:954 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:" -"`~Structure._fields_` attribute later, after the class statement::" +"itself. In :mod:`ctypes`, we can define the ``cell`` class and set " +"the :attr:`~Structure._fields_` attribute later, after the class statement::" msgstr "" #: library/ctypes.rst:958 @@ -2107,13 +2109,14 @@ msgstr "" #: library/ctypes.rst:1371 msgid "" "On Windows creating a :class:`CDLL` instance may fail even if the DLL name " -"exists. When a dependent DLL of the loaded DLL is not found, a :exc:" -"`OSError` error is raised with the message *\"[WinError 126] The specified " -"module could not be found\".* This error message does not contain the name " -"of the missing DLL because the Windows API does not return this information " -"making this error hard to diagnose. To resolve this error and determine " -"which DLL is not found, you need to find the list of dependent DLLs and " -"determine which one is not found using Windows debugging and tracing tools." +"exists. When a dependent DLL of the loaded DLL is not found, " +"a :exc:`OSError` error is raised with the message *\"[WinError 126] The " +"specified module could not be found\".* This error message does not contain " +"the name of the missing DLL because the Windows API does not return this " +"information making this error hard to diagnose. To resolve this error and " +"determine which DLL is not found, you need to find the list of dependent " +"DLLs and determine which one is not found using Windows debugging and " +"tracing tools." msgstr "" #: library/ctypes.rst:1406 library/ctypes.rst:1434 @@ -2130,16 +2133,17 @@ msgstr "" 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." +"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 "" #: library/ctypes.rst:1400 msgid "" -":exc:`WindowsError` used to be raised, which is now an alias of :exc:" -"`OSError`." +":exc:`WindowsError` used to be raised, which is now an alias " +"of :exc:`OSError`." msgstr "" #: library/ctypes.rst:1411 @@ -2188,11 +2192,12 @@ msgstr "" #: library/ctypes.rst:1448 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." +"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 "" #: library/ctypes.rst:1455 @@ -2205,10 +2210,11 @@ msgstr "" #: library/ctypes.rst:1459 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." +"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 "" #: library/ctypes.rst:1465 @@ -2286,8 +2292,8 @@ msgstr "" #: library/ctypes.rst:1530 msgid "" -"Class which loads shared libraries. *dlltype* should be one of the :class:" -"`CDLL`, :class:`PyDLL`, :class:`WinDLL`, or :class:`OleDLL` types." +"Class which loads shared libraries. *dlltype* should be one of " +"the :class:`CDLL`, :class:`PyDLL`, :class:`WinDLL`, or :class:`OleDLL` types." msgstr "" #: library/ctypes.rst:1533 @@ -2333,9 +2339,9 @@ msgstr "" #: library/ctypes.rst:1575 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:expr:" -"`int`, which is of course not always the truth, so you have to assign the " -"correct :attr:`!restype` attribute to use these functions." +"attributes. Note that all these functions are assumed to return " +"C :c:expr:`int`, which is of course not always the truth, so you have to " +"assign the correct :attr:`!restype` attribute to use these functions." msgstr "" #: library/ctypes.rst:1582 @@ -2347,9 +2353,9 @@ msgstr "" #: library/ctypes.rst:1588 msgid "" -"Accessing a function on a loaded library raises an auditing event ``ctypes." -"dlsym`` with arguments ``library`` (the library object) and ``name`` (the " -"symbol's name as a string or integer)." +"Accessing a function on a loaded library raises an auditing event " +"``ctypes.dlsym`` with arguments ``library`` (the library object) and " +"``name`` (the symbol's name as a string or integer)." msgstr "" #: library/ctypes.rst:1594 @@ -2431,12 +2437,12 @@ msgstr "" #: library/ctypes.rst:1650 msgid "" -"When a foreign function is called, each actual argument is passed to the :" -"meth:`~_CData.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." +"When a foreign function is called, each actual argument is passed to " +"the :meth:`~_CData.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 "" #: library/ctypes.rst:1657 @@ -2488,9 +2494,9 @@ msgstr "" msgid "" "On Windows, when a foreign function call raises a system exception (for " "example, due to an access violation), it will be captured and replaced with " -"a suitable Python exception. Further, an auditing event ``ctypes." -"set_exception`` with argument ``code`` will be raised, allowing an audit " -"hook to replace the exception with its own." +"a suitable Python exception. Further, an auditing event " +"``ctypes.set_exception`` with argument ``code`` will be raised, allowing an " +"audit hook to replace the exception with its own." msgstr "" #: library/ctypes.rst:1703 @@ -2519,9 +2525,10 @@ msgstr "" 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." +"*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 "" #: library/ctypes.rst:1732 @@ -2585,8 +2592,8 @@ msgstr "" #: library/ctypes.rst:1786 msgid "" -"*paramflags* must be a tuple of the same length as :attr:`~_CFuncPtr." -"argtypes`." +"*paramflags* must be a tuple of the same length " +"as :attr:`~_CFuncPtr.argtypes`." msgstr "" #: library/ctypes.rst:1788 @@ -2910,8 +2917,8 @@ msgstr "" #: library/ctypes.rst:2012 msgid "" -"Returns the current value of the ctypes-private copy of the system :data:" -"`errno` variable in the calling thread." +"Returns the current value of the ctypes-private copy of the " +"system :data:`errno` variable in the calling thread." msgstr "" #: library/ctypes.rst:2015 @@ -3052,9 +3059,9 @@ msgstr "" 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 " +"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 "" @@ -3069,8 +3076,8 @@ 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." +"in bytes; the default is zero. If the source buffer is not large enough " +"a :exc:`ValueError` is raised." msgstr "" #: library/ctypes.rst:2153 @@ -3095,8 +3102,9 @@ msgstr "" #: library/ctypes.rst:2162 msgid "" -"This method, and others that indirectly call this method, raises an :ref:" -"`auditing event ` ``ctypes.cdata`` with argument ``address``." +"This method, and others that indirectly call this method, raises " +"an :ref:`auditing event ` ``ctypes.cdata`` with argument " +"``address``." msgstr "" #: library/ctypes.rst:2168 @@ -3128,9 +3136,9 @@ msgstr "" #: library/ctypes.rst:2187 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." +"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 "" #: library/ctypes.rst:2194 @@ -3151,8 +3159,8 @@ msgstr "" 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 " +"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 "" @@ -3248,8 +3256,8 @@ msgstr "" #: library/ctypes.rst:2297 msgid "" -"Represents the C 8-bit :c:expr:`signed int` datatype. Usually an alias for :" -"class:`c_byte`." +"Represents the C 8-bit :c:expr:`signed int` datatype. Usually an alias " +"for :class:`c_byte`." msgstr "" #: library/ctypes.rst:2303 @@ -3398,9 +3406,9 @@ msgstr "" #: library/ctypes.rst:2450 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." +"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 "" #: library/ctypes.rst:2458 @@ -3440,9 +3448,9 @@ msgstr "" #: library/ctypes.rst:2495 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" +"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 "" #: library/ctypes.rst:2503 @@ -3499,23 +3507,23 @@ msgstr "" #: library/ctypes.rst:2536 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. Setting this " -"attribute to 0 is the same as not setting it at all." +"fields in the instance. :attr:`_pack_` must already be defined " +"when :attr:`_fields_` is assigned, otherwise it will have no effect. Setting " +"this attribute to 0 is the same as not setting it at all." msgstr "" #: library/ctypes.rst:2544 msgid "" -"An optional sequence that lists the names of unnamed (anonymous) fields. :" -"attr:`_anonymous_` must be already defined when :attr:`_fields_` is " +"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 "" #: library/ctypes.rst:2548 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 " +"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 "" @@ -3557,9 +3565,9 @@ msgstr "" #: library/ctypes.rst:2578 msgid "" "It is possible to define 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." +"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 "" #: library/ctypes.rst:2583 @@ -3582,9 +3590,9 @@ msgstr "" #: library/ctypes.rst:2600 msgid "" -"The recommended way to create concrete array types is by multiplying any :" -"mod:`ctypes` data type with a non-negative integer. Alternatively, you can " -"subclass this type and define :attr:`_length_` and :attr:`_type_` class " +"The recommended way to create concrete array types is by multiplying " +"any :mod:`ctypes` data type with a non-negative 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`." @@ -3593,8 +3601,8 @@ msgstr "" #: library/ctypes.rst:2610 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`." +"range subscripts result in an :exc:`IndexError`. Will be returned " +"by :func:`len`." msgstr "" #: library/ctypes.rst:2617 @@ -3620,10 +3628,10 @@ msgstr "" #: library/ctypes.rst:2632 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)." +"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 "" #: library/ctypes.rst:2642 diff --git a/library/curses.ascii.po b/library/curses.ascii.po index 35704ec9b..a882a7679 100644 --- a/library/curses.ascii.po +++ b/library/curses.ascii.po @@ -253,8 +253,8 @@ msgstr "" #: library/curses.ascii.rst:168 msgid "" -"Checks for an ASCII hexadecimal digit. This is equivalent to ``c in string." -"hexdigits``." +"Checks for an ASCII hexadecimal digit. This is equivalent to ``c in " +"string.hexdigits``." msgstr "" #: library/curses.ascii.rst:174 @@ -268,8 +268,8 @@ msgstr "" #: library/curses.ascii.rst:181 msgid "" "These functions accept either integers or single-character strings; when the " -"argument is a string, it is first converted using the built-in function :" -"func:`ord`." +"argument is a string, it is first converted using the built-in " +"function :func:`ord`." msgstr "" #: library/curses.ascii.rst:184 diff --git a/library/curses.po b/library/curses.po index 0608b8a60..f967afd7a 100644 --- a/library/curses.po +++ b/library/curses.po @@ -152,9 +152,9 @@ msgstr "" msgid "" "Return the attribute value for displaying text in the specified color pair. " "Only the first 256 color pairs are supported. 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." +"combined with :const:`A_STANDOUT`, :const:`A_REVERSE`, and the " +"other :const:`!A_\\*` attributes. :func:`pair_number` is the counterpart to " +"this function." msgstr "" #: library/curses.rst:116 @@ -170,16 +170,16 @@ msgstr "" 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." +"for when the program is not in curses.) Subsequent calls " +"to :func:`reset_prog_mode` will restore this mode." msgstr "" #: library/curses.rst:133 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." +"mode, when the program is using curses capabilities.) Subsequent calls " +"to :func:`reset_shell_mode` will restore this mode." msgstr "" #: library/curses.rst:141 @@ -201,8 +201,8 @@ msgid "" "a window. The normal :meth:`~window.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`." +"issuing :meth:`!noutrefresh` calls on all windows, followed by a " +"single :func:`!doupdate`." msgstr "" #: library/curses.rst:161 @@ -255,10 +255,8 @@ msgid "" "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 5: :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`." +"from 1 to " +"5: :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 "" #: library/curses.rst:1774 @@ -276,9 +274,9 @@ msgstr "" #: library/curses.rst:226 msgid "" -"Read window related data stored in the file by an earlier :func:`window." -"putwin` call. The routine then creates and initializes a new window using " -"that data, returning the new window object." +"Read window related data stored in the file by an " +"earlier :func:`window.putwin` call. The routine then creates and initializes " +"a new window using that data, returning the new window object." msgstr "" #: library/curses.rst:233 @@ -441,14 +439,14 @@ msgid "" "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:`~window." -"refresh` and :meth:`~window.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." +"as from scrolling or echoing of input) do not occur. " +"The :meth:`~window.refresh` and :meth:`~window.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 "" #: library/curses.rst:394 @@ -511,15 +509,15 @@ msgstr "" #: library/curses.rst:449 msgid "" -"Return the number of the color-pair set by the attribute value *attr*. :func:" -"`color_pair` is the counterpart to this function." +"Return the number of the color-pair set by the attribute value " +"*attr*. :func:`color_pair` is the counterpart to this function." msgstr "" #: library/curses.rst:455 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." +"terminfo capability for the current terminal. Note that the output " +"of :func:`putp` always goes to standard output." msgstr "" #: library/curses.rst:462 @@ -538,20 +536,20 @@ msgstr "" #: library/curses.rst:476 msgid "" -"Restore the terminal to \"program\" mode, as previously saved by :func:" -"`def_prog_mode`." +"Restore the terminal to \"program\" mode, as previously saved " +"by :func:`def_prog_mode`." msgstr "" #: library/curses.rst:482 msgid "" -"Restore the terminal to \"shell\" mode, as previously saved by :func:" -"`def_shell_mode`." +"Restore the terminal to \"shell\" mode, as previously saved " +"by :func:`def_shell_mode`." msgstr "" #: library/curses.rst:488 msgid "" -"Restore the state of the terminal modes to what it was at the last call to :" -"func:`savetty`." +"Restore the state of the terminal modes to what it was at the last call " +"to :func:`savetty`." msgstr "" #: library/curses.rst:494 @@ -573,8 +571,8 @@ msgstr "" #: library/curses.rst:511 msgid "" -"Save the current state of the terminal modes in a buffer, usable by :func:" -"`resetty`." +"Save the current state of the terminal modes in a buffer, usable " +"by :func:`resetty`." msgstr "" #: library/curses.rst:516 @@ -623,11 +621,11 @@ msgstr "" #: library/curses.rst:562 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." +"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 "" #: library/curses.rst:571 @@ -1040,8 +1038,8 @@ msgstr "" #: library/curses.rst:893 msgid "" -"Add character *ch* with attribute *attr*, and immediately call :meth:" -"`refresh` on the window." +"Add character *ch* with attribute *attr*, and immediately " +"call :meth:`refresh` on the window." msgstr "" #: library/curses.rst:899 @@ -1205,15 +1203,15 @@ msgstr "" #: library/curses.rst:1071 msgid "" -"Return ``True`` if the specified line was modified since the last call to :" -"meth:`refresh`; otherwise return ``False``. Raise a :exc:`curses.error` " +"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 "" #: library/curses.rst:1078 msgid "" -"Return ``True`` if the specified window was modified since the last call to :" -"meth:`refresh`; otherwise return ``False``." +"Return ``True`` if the specified window was modified since the last call " +"to :meth:`refresh`; otherwise return ``False``." msgstr "" #: library/curses.rst:1084 @@ -1282,8 +1280,8 @@ msgstr "" #: library/curses.rst:1142 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 " +"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 "" @@ -1298,8 +1296,8 @@ msgstr "" #: library/curses.rst:1155 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 " +"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 "" @@ -1318,8 +1316,8 @@ msgstr "" #: library/curses.rst:1175 msgid "" -"Touch the entire window, causing it to be completely redrawn on the next :" -"meth:`refresh` call." +"Touch the entire window, causing it to be completely redrawn on the " +"next :meth:`refresh` call." msgstr "" #: library/curses.rst:1181 @@ -1417,9 +1415,9 @@ 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 :meth:`getch` will " -"return ``-1`` 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." +"return ``-1`` 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 "" #: library/curses.rst:1284 @@ -1438,8 +1436,8 @@ msgstr "" #: library/curses.rst:1297 msgid "" -"Mark all lines in the window as unchanged since the last call to :meth:" -"`refresh`." +"Mark all lines in the window as unchanged since the last call " +"to :meth:`refresh`." msgstr "" #: library/curses.rst:1304 @@ -1458,8 +1456,8 @@ msgstr "" #: library/curses.rst:1316 msgid "" -"Some curses routines that return an integer, such as :meth:`~window." -"getch`, return :const:`ERR` upon failure." +"Some curses routines that return an integer, such " +"as :meth:`~window.getch`, return :const:`ERR` upon failure." msgstr "" #: library/curses.rst:1322 @@ -1499,15 +1497,15 @@ msgstr "" #: library/curses.rst:1355 msgid "" "The width of the screen, i.e., the number of columns. It is defined only " -"after the call to :func:`initscr`. Updated by :func:`update_lines_cols`, :" -"func:`resizeterm` and :func:`resize_term`." +"after the call to :func:`initscr`. Updated " +"by :func:`update_lines_cols`, :func:`resizeterm` and :func:`resize_term`." msgstr "" #: library/curses.rst:1362 msgid "" "The height of the screen, i.e., the number of lines. It is defined only " -"after the call to :func:`initscr`. Updated by :func:`update_lines_cols`, :" -"func:`resizeterm` and :func:`resize_term`." +"after the call to :func:`initscr`. Updated " +"by :func:`update_lines_cols`, :func:`resizeterm` and :func:`resize_term`." msgstr "" #: library/curses.rst:1368 @@ -2011,13 +2009,14 @@ msgstr "" #: library/curses.rst:1627 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:" +"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 "" #: library/curses.rst:1636 @@ -2381,11 +2380,11 @@ msgstr "" #: library/curses.rst:1841 msgid "" -"Return a textbox widget object. The *win* argument should be a curses :ref:" -"`window ` object 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." +"Return a textbox widget object. The *win* argument should be a " +"curses :ref:`window ` object 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 "" #: library/curses.rst:1847 @@ -2399,8 +2398,8 @@ msgid "" "*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." +"whether blanks in the window are included is affected by " +"the :attr:`stripspaces` attribute." msgstr "" #: library/curses.rst:1863 diff --git a/library/dataclasses.po b/library/dataclasses.po index 7c67102b0..275768bb3 100644 --- a/library/dataclasses.po +++ b/library/dataclasses.po @@ -27,15 +27,15 @@ msgstr "" #: library/dataclasses.rst:14 msgid "" "This module provides a decorator and functions for automatically adding " -"generated :term:`special methods ` such as :meth:`~object." -"__init__` and :meth:`~object.__repr__` to user-defined classes. It was " -"originally described in :pep:`557`." +"generated :term:`special methods ` such " +"as :meth:`~object.__init__` and :meth:`~object.__repr__` to user-defined " +"classes. It was originally described in :pep:`557`." msgstr "" #: library/dataclasses.rst:19 msgid "" -"The member variables to use in these generated methods are defined using :" -"pep:`526` type annotations. For example, this code::" +"The member variables to use in these generated methods are defined " +"using :pep:`526` type annotations. For example, this code::" msgstr "" #: library/dataclasses.rst:22 @@ -78,8 +78,9 @@ msgstr "" #: library/dataclasses.rst:51 msgid "" -"This function is a :term:`decorator` that is used to add generated :term:" -"`special methods ` to classes, as described below." +"This function is a :term:`decorator` that is used to add " +"generated :term:`special methods ` to classes, as described " +"below." msgstr "" #: library/dataclasses.rst:54 @@ -174,17 +175,19 @@ msgstr "" #: library/dataclasses.rst:113 msgid "" -"*order*: If true (the default is ``False``), :meth:`~object.__lt__`, :meth:" -"`~object.__le__`, :meth:`~object.__gt__`, and :meth:`~object.__ge__` methods " -"will be generated. These compare the class as if it were a tuple of its " -"fields, in order. Both instances in the comparison must be of the identical " -"type. If *order* is true and *eq* is false, a :exc:`ValueError` is raised." +"*order*: If true (the default is " +"``False``), :meth:`~object.__lt__`, :meth:`~object.__le__`, :meth:`~object.__gt__`, " +"and :meth:`~object.__ge__` methods will be generated. These compare the " +"class as if it were a tuple of its fields, in order. Both instances in the " +"comparison must be of the identical type. If *order* is true and *eq* is " +"false, a :exc:`ValueError` is raised." msgstr "" #: library/dataclasses.rst:120 msgid "" -"If the class already defines any of :meth:`!__lt__`, :meth:`!__le__`, :meth:" -"`!__gt__`, or :meth:`!__ge__`, then :exc:`TypeError` is raised." +"If the class already defines any of :meth:`!__lt__`, :meth:`!" +"__le__`, :meth:`!__gt__`, or :meth:`!__ge__`, then :exc:`TypeError` is " +"raised." msgstr "" #: library/dataclasses.rst:124 @@ -205,11 +208,11 @@ msgstr "" #: library/dataclasses.rst:134 msgid "" -"By default, ``@dataclass`` will not implicitly add a :meth:`~object." -"__hash__` method unless it is safe to do so. Neither will it add or change " -"an existing explicitly defined :meth:`!__hash__` method. Setting the class " -"attribute ``__hash__ = None`` has a specific meaning to Python, as described " -"in the :meth:`!__hash__` documentation." +"By default, ``@dataclass`` will not implicitly add " +"a :meth:`~object.__hash__` method unless it is safe to do so. Neither will " +"it add or change an existing explicitly defined :meth:`!__hash__` method. " +"Setting the class attribute ``__hash__ = None`` has a specific meaning to " +"Python, as described in the :meth:`!__hash__` documentation." msgstr "" #: library/dataclasses.rst:140 @@ -226,36 +229,37 @@ msgstr "" msgid "" "Here are the rules governing implicit creation of a :meth:`!__hash__` " "method. Note that you cannot both have an explicit :meth:`!__hash__` method " -"in your dataclass and set ``unsafe_hash=True``; this will result in a :exc:" -"`TypeError`." +"in your dataclass and set ``unsafe_hash=True``; this will result in " +"a :exc:`TypeError`." msgstr "" #: library/dataclasses.rst:152 msgid "" "If *eq* and *frozen* are both true, by default ``@dataclass`` will generate " -"a :meth:`!__hash__` method for you. If *eq* is true and *frozen* is false, :" -"meth:`!__hash__` will be set to ``None``, marking it unhashable (which it " -"is, since it is mutable). If *eq* is false, :meth:`!__hash__` will be left " -"untouched meaning the :meth:`!__hash__` method of the superclass will be " -"used (if the superclass is :class:`object`, this means it will fall back to " -"id-based hashing)." +"a :meth:`!__hash__` method for you. If *eq* is true and *frozen* is " +"false, :meth:`!__hash__` will be set to ``None``, marking it unhashable " +"(which it is, since it is mutable). If *eq* is false, :meth:`!__hash__` " +"will be left untouched meaning the :meth:`!__hash__` method of the " +"superclass will be used (if the superclass is :class:`object`, this means it " +"will fall back to id-based hashing)." msgstr "" #: library/dataclasses.rst:160 msgid "" "*frozen*: If true (the default is ``False``), assigning to fields will " -"generate an exception. This emulates read-only frozen instances. If :meth:" -"`~object.__setattr__` or :meth:`~object.__delattr__` is defined in the " -"class, then :exc:`TypeError` is raised. See the discussion below." +"generate an exception. This emulates read-only frozen instances. " +"If :meth:`~object.__setattr__` or :meth:`~object.__delattr__` is defined in " +"the class, then :exc:`TypeError` is raised. See the discussion below." msgstr "" #: library/dataclasses.rst:165 msgid "" -"*match_args*: If true (the default is ``True``), the :attr:`~object." -"__match_args__` tuple will be created from the list of parameters to the " -"generated :meth:`~object.__init__` method (even if :meth:`!__init__` is not " -"generated, see above). If false, or if :attr:`!__match_args__` is already " -"defined in the class, then :attr:`!__match_args__` will not be generated." +"*match_args*: If true (the default is ``True``), " +"the :attr:`~object.__match_args__` tuple will be created from the list of " +"parameters to the generated :meth:`~object.__init__` method (even if :meth:`!" +"__init__` is not generated, see above). If false, or if :attr:`!" +"__match_args__` is already defined in the class, then :attr:`!" +"__match_args__` will not be generated." msgstr "" #: library/dataclasses.rst:174 @@ -264,17 +268,17 @@ msgid "" "marked as keyword-only. If a field is marked as keyword-only, then the only " "effect is that the :meth:`~object.__init__` parameter generated from a " "keyword-only field must be specified with a keyword when :meth:`!__init__` " -"is called. There is no effect on any other aspect of dataclasses. See the :" -"term:`parameter` glossary entry for details. Also see the :const:`KW_ONLY` " -"section." +"is called. There is no effect on any other aspect of dataclasses. See " +"the :term:`parameter` glossary entry for details. Also see " +"the :const:`KW_ONLY` section." msgstr "" #: library/dataclasses.rst:185 msgid "" "*slots*: If true (the default is ``False``), :attr:`~object.__slots__` " "attribute will be generated and new class will be returned instead of the " -"original one. If :attr:`!__slots__` is already defined in the class, then :" -"exc:`TypeError` is raised." +"original one. If :attr:`!__slots__` is already defined in the class, " +"then :exc:`TypeError` is raised." msgstr "" #: library/dataclasses.rst:191 @@ -298,9 +302,9 @@ msgid "" "If a field name is already included in the :attr:`!__slots__` of a base " "class, it will not be included in the generated :attr:`!__slots__` to " "prevent :ref:`overriding them `. Therefore, do not " -"use :attr:`!__slots__` to retrieve the field names of a dataclass. Use :func:" -"`fields` instead. To be able to determine inherited slots, base class :attr:" -"`!__slots__` may be any iterable, but *not* an iterator." +"use :attr:`!__slots__` to retrieve the field names of a dataclass. " +"Use :func:`fields` instead. To be able to determine inherited slots, base " +"class :attr:`!__slots__` may be any iterable, but *not* an iterator." msgstr "" #: library/dataclasses.rst:216 @@ -422,8 +426,8 @@ msgstr "" #: library/dataclasses.rst:292 msgid "" "*compare*: If true (the default), this field is included in the generated " -"equality and comparison methods (:meth:`~object.__eq__`, :meth:`~object." -"__gt__`, et al.)." +"equality and comparison methods " +"(:meth:`~object.__eq__`, :meth:`~object.__gt__`, et al.)." msgstr "" #: library/dataclasses.rst:296 @@ -488,9 +492,10 @@ msgstr "" #: library/dataclasses.rst:339 msgid "" -":attr:`!default`, :attr:`!default_factory`, :attr:`!init`, :attr:`!repr`, :" -"attr:`!hash`, :attr:`!compare`, :attr:`!metadata`, and :attr:`!kw_only` have " -"the identical meaning and values as they do in the :func:`field` function." +":attr:`!default`, :attr:`!default_factory`, :attr:`!init`, :attr:`!" +"repr`, :attr:`!hash`, :attr:`!compare`, :attr:`!metadata`, and :attr:`!" +"kw_only` have the identical meaning and values as they do in " +"the :func:`field` function." msgstr "" #: library/dataclasses.rst:343 @@ -586,8 +591,8 @@ msgid "" "``name``, ``(name, type)``, or ``(name, type, Field)``. If just ``name`` is " "supplied, :data:`typing.Any` is used for ``type``. The values of *init*, " "*repr*, *eq*, *order*, *unsafe_hash*, *frozen*, *match_args*, *kw_only*, " -"*slots*, and *weakref_slot* have the same meaning as they do in :func:" -"`@dataclass `." +"*slots*, and *weakref_slot* have the same meaning as they do " +"in :func:`@dataclass `." msgstr "" #: library/dataclasses.rst:417 @@ -599,9 +604,9 @@ msgstr "" #: library/dataclasses.rst:421 msgid "" "This function is not strictly required, because any Python mechanism for " -"creating a new class with :attr:`!__annotations__` can then apply the :func:" -"`@dataclass ` function to convert that class to a dataclass. " -"This function is provided as a convenience. For example::" +"creating a new class with :attr:`!__annotations__` can then apply " +"the :func:`@dataclass ` function to convert that class to a " +"dataclass. This function is provided as a convenience. For example::" msgstr "" #: library/dataclasses.rst:427 @@ -633,8 +638,8 @@ msgstr "" msgid "" "Creates a new object of the same type as *obj*, replacing fields with values " "from *changes*. If *obj* is not a Data Class, raises :exc:`TypeError`. If " -"keys in *changes* are not field names of the given dataclass, raises :exc:" -"`TypeError`." +"keys in *changes* are not field names of the given dataclass, " +"raises :exc:`TypeError`." msgstr "" #: library/dataclasses.rst:451 @@ -697,9 +702,9 @@ msgid "" "with the type of :const:`!KW_ONLY` are marked as keyword-only fields. Note " "that a pseudo-field of type :const:`!KW_ONLY` is otherwise completely " "ignored. This includes the name of such a field. By convention, a name of " -"``_`` is used for a :const:`!KW_ONLY` field. Keyword-only fields signify :" -"meth:`~object.__init__` parameters that must be specified as keywords when " -"the class is instantiated." +"``_`` is used for a :const:`!KW_ONLY` field. Keyword-only fields " +"signify :meth:`~object.__init__` parameters that must be specified as " +"keywords when the class is instantiated." msgstr "" #: library/dataclasses.rst:499 @@ -728,9 +733,9 @@ msgstr "" #: library/dataclasses.rst:517 msgid "" -"Raised when an implicitly defined :meth:`~object.__setattr__` or :meth:" -"`~object.__delattr__` is called on a dataclass which was defined with " -"``frozen=True``. It is a subclass of :exc:`AttributeError`." +"Raised when an implicitly defined :meth:`~object.__setattr__` " +"or :meth:`~object.__delattr__` is called on a dataclass which was defined " +"with ``frozen=True``. It is a subclass of :exc:`AttributeError`." msgstr "" #: library/dataclasses.rst:524 @@ -739,12 +744,12 @@ msgstr "" #: library/dataclasses.rst:528 msgid "" -"When defined on the class, it will be called by the generated :meth:`~object." -"__init__`, normally as :meth:`!self.__post_init__`. However, if any " -"``InitVar`` fields are defined, they will also be passed to :meth:`!" -"__post_init__` in the order they were defined in the class. If no :meth:`!" -"__init__` method is generated, then :meth:`!__post_init__` will not " -"automatically be called." +"When defined on the class, it will be called by the " +"generated :meth:`~object.__init__`, normally as :meth:`!self.__post_init__`. " +"However, if any ``InitVar`` fields are defined, they will also be passed " +"to :meth:`!__post_init__` in the order they were defined in the class. If " +"no :meth:`!__init__` method is generated, then :meth:`!__post_init__` will " +"not automatically be called." msgstr "" #: library/dataclasses.rst:535 @@ -797,8 +802,8 @@ msgstr "" #: library/dataclasses.rst:568 msgid "" -"See the section below on init-only variables for ways to pass parameters to :" -"meth:`!__post_init__`. Also see the warning about how :func:`replace` " +"See the section below on init-only variables for ways to pass parameters " +"to :meth:`!__post_init__`. Also see the warning about how :func:`replace` " "handles ``init=False`` fields." msgstr "" @@ -813,8 +818,8 @@ msgid "" "defined in :pep:`526`. It does this by checking if the type of the field " "is :data:`typing.ClassVar`. If a field is a ``ClassVar``, it is excluded " "from consideration as a field and is ignored by the dataclass mechanisms. " -"Such ``ClassVar`` pseudo-fields are not returned by the module-level :func:" -"`fields` function." +"Such ``ClassVar`` pseudo-fields are not returned by the module-" +"level :func:`fields` function." msgstr "" #: library/dataclasses.rst:588 @@ -869,16 +874,17 @@ msgstr "" msgid "" "It is not possible to create truly immutable Python objects. However, by " "passing ``frozen=True`` to the :func:`@dataclass ` decorator you " -"can emulate immutability. In that case, dataclasses will add :meth:`~object." -"__setattr__` and :meth:`~object.__delattr__` methods to the class. These " -"methods will raise a :exc:`FrozenInstanceError` when invoked." +"can emulate immutability. In that case, dataclasses will " +"add :meth:`~object.__setattr__` and :meth:`~object.__delattr__` methods to " +"the class. These methods will raise a :exc:`FrozenInstanceError` when " +"invoked." msgstr "" #: library/dataclasses.rst:629 msgid "" -"There is a tiny performance penalty when using ``frozen=True``: :meth:" -"`~object.__init__` cannot use simple assignment to initialize fields, and " -"must use :meth:`!object.__setattr__`." +"There is a tiny performance penalty when using " +"``frozen=True``: :meth:`~object.__init__` cannot use simple assignment to " +"initialize fields, and must use :meth:`!object.__setattr__`." msgstr "" #: library/dataclasses.rst:638 @@ -1071,14 +1077,14 @@ msgstr "" #: library/dataclasses.rst:758 msgid "" "This has the same issue as the original example using class :class:`!C`. " -"That is, two instances of class :class:`!D` that do not specify a value for :" -"attr:`!x` when creating a class instance will share the same copy of :attr:`!" -"x`. Because dataclasses just use normal Python class creation they also " -"share this behavior. There is no general way for Data Classes to detect " -"this condition. Instead, the :func:`@dataclass ` decorator will " -"raise a :exc:`ValueError` if it detects an unhashable default parameter. " -"The assumption is that if a value is unhashable, it is mutable. This is a " -"partial solution, but it does protect against many common errors." +"That is, two instances of class :class:`!D` that do not specify a value " +"for :attr:`!x` when creating a class instance will share the same copy " +"of :attr:`!x`. Because dataclasses just use normal Python class creation " +"they also share this behavior. There is no general way for Data Classes to " +"detect this condition. Instead, the :func:`@dataclass ` " +"decorator will raise a :exc:`ValueError` if it detects an unhashable default " +"parameter. The assumption is that if a value is unhashable, it is mutable. " +"This is a partial solution, but it does protect against many common errors." msgstr "" #: library/dataclasses.rst:769 @@ -1098,9 +1104,10 @@ msgstr "" #: library/dataclasses.rst:778 msgid "" -"Instead of looking for and disallowing objects of type :class:`list`, :class:" -"`dict`, or :class:`set`, unhashable objects are now not allowed as default " -"values. Unhashability is used to approximate mutability." +"Instead of looking for and disallowing objects of " +"type :class:`list`, :class:`dict`, or :class:`set`, unhashable objects are " +"now not allowed as default values. Unhashability is used to approximate " +"mutability." msgstr "" #: library/dataclasses.rst:785 @@ -1122,9 +1129,9 @@ msgstr "" #: library/dataclasses.rst:794 msgid "" -"Similarly, when getting or setting the field, the descriptor's :meth:" -"`~object.__get__` or :meth:`!__set__` method is called rather than returning " -"or overwriting the descriptor object." +"Similarly, when getting or setting the field, the " +"descriptor's :meth:`~object.__get__` or :meth:`!__set__` method is called " +"rather than returning or overwriting the descriptor object." msgstr "" #: library/dataclasses.rst:798 diff --git a/library/datatypes.po b/library/datatypes.po index 16dcc3a1c..2cdf09806 100644 --- a/library/datatypes.po +++ b/library/datatypes.po @@ -29,10 +29,11 @@ msgstr "" #: 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` and :class:`bytearray` classes are used to hold binary data." +"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` and :class:`bytearray` " +"classes are used to hold binary data." msgstr "" #: library/datatypes.rst:17 diff --git a/library/datetime.po b/library/datetime.po index 2eb7a17cb..2aeae85c2 100644 --- a/library/datetime.po +++ b/library/datetime.po @@ -85,9 +85,9 @@ msgstr "" #: library/datetime.rst:41 #, fuzzy msgid "" -"Third-party library that introduces distinct static types to e.g. allow :" -"term:`static type checkers ` to differentiate between " -"naive and aware datetimes." +"Third-party library that introduces distinct static types to e.g. " +"allow :term:`static type checkers ` to differentiate " +"between naive and aware datetimes." msgstr "" "Statik tür denetleyicilerinin bilinçli ve bilinçsiz tarih zamanları arasında " "ayrım yapmasına izin vermek için farklı statik türler sunan üçüncü taraf bir " @@ -140,19 +140,19 @@ msgstr "" #: library/datetime.rst:66 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." +"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." msgstr "" -"Bilinçli nesneler gerektiren uygulamalar için, :class:`.datetime` ve :class:" -"`.time` nesneleri, soyut :class:`tzinfo` sınıfının bir alt sınıfının " -"örneğine ayarlanabilen isteğe bağlı bir saat dilimi bilgisi özniteliğine, :" -"attr:`!tzinfo` sahiptir. :class:`tzinfo` nesneleri UTC zamanından sapma, " -"saat dilimi adı ve yaz saati uygulamasının geçerli olup olmadığına ilişkin " -"bilgileri yakalar." +"Bilinçli nesneler gerektiren uygulamalar için, :class:`.datetime` " +"ve :class:`.time` nesneleri, soyut :class:`tzinfo` sınıfının bir alt " +"sınıfının örneğine ayarlanabilen isteğe bağlı bir saat dilimi bilgisi " +"özniteliğine, :attr:`!tzinfo` sahiptir. :class:`tzinfo` nesneleri UTC " +"zamanından sapma, saat dilimi adı ve yaz saati uygulamasının geçerli olup " +"olmadığına ilişkin bilgileri yakalar." #: library/datetime.rst:72 #, fuzzy @@ -165,13 +165,13 @@ msgid "" "across the world are more political than rational, change frequently, and " "there is no standard suitable for every application aside from UTC." msgstr "" -"Sadece bir somut :class:`tzinfo` sınıfı, :class:`timezone` sınıfı, :mod:" -"`datetime` modülü tarafından sağlanır. :class:`timezone` sınıfı, UTC'nin " -"kendisi veya Kuzey Amerika EST ve EDT zaman dilimleri gibi UTC'den sabit " -"uzaklıklara sahip basit zaman dilimlerini temsil edebilir. Daha derin " -"ayrıntı seviyelerinde zaman dilimlerini desteklemek uygulamaya bağlıdır. " -"Dünya genelinde zaman ayarlaması için kurallar rasyonel olmaktan çok " -"politiktir, sık sık değişir ve UTC dışında her uygulama için uygun bir " +"Sadece bir somut :class:`tzinfo` sınıfı, :class:`timezone` " +"sınıfı, :mod:`datetime` modülü tarafından sağlanır. :class:`timezone` " +"sınıfı, UTC'nin kendisi veya Kuzey Amerika EST ve EDT zaman dilimleri gibi " +"UTC'den sabit uzaklıklara sahip basit zaman dilimlerini temsil edebilir. " +"Daha derin ayrıntı seviyelerinde zaman dilimlerini desteklemek uygulamaya " +"bağlıdır. Dünya genelinde zaman ayarlaması için kurallar rasyonel olmaktan " +"çok politiktir, sık sık değişir ve UTC dışında her uygulama için uygun bir " "standart yoktur." #: library/datetime.rst:81 @@ -214,40 +214,42 @@ msgstr "Mevcut Türler" #: library/datetime.rst:108 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`." +"and always will be, in effect. Attributes: :attr:`year`, :attr:`month`, " +"and :attr:`day`." msgstr "" "Geçerli Miladi takvimin her zaman yürürlükte olduğu ve her zaman yürürlükte " -"olacağı varsayılarak idealleştirilmiş bilinçsiz bir tarih. Öznitelikler: :" -"attr:`year`, :attr:`month`, ve :attr:`day`." +"olacağı varsayılarak idealleştirilmiş bilinçsiz bir tarih. " +"Öznitelikler: :attr:`year`, :attr:`month`, ve :attr:`day`." #: library/datetime.rst:116 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`." +"seconds\" here.) " +"Attributes: :attr:`hour`, :attr:`minute`, :attr:`second`, :attr:`microsecond`, " +"and :attr:`.tzinfo`." msgstr "" "Her günün tam olarak 24\\*60\\*60 saniye olduğu varsayılarak, belirli bir " "günden bağımsız idealleştirilmiş bir zaman. (Burada \"artık saniye\" " -"kavramı yoktur.) Öznitelikler: :attr:`hour`, :attr:`minute`, :attr:" -"`second`, :attr:`microsecond`, ve :attr:`.tzinfo`." +"kavramı yoktur.) " +"Öznitelikler: :attr:`hour`, :attr:`minute`, :attr:`second`, :attr:`microsecond`, " +"ve :attr:`.tzinfo`." #: library/datetime.rst:125 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`." +"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 "" -"Tarih ve saatin bir kombinasyonu. Öznitelikler: :attr:`year`, :attr:" -"`month`, :attr:`day`, :attr:`hour`, :attr:`minute`, :attr:`second`, :attr:" -"`microsecond` ve :attr:`.tzinfo`." +"Tarih ve saatin bir kombinasyonu. " +"Öznitelikler: :attr:`year`, :attr:`month`, :attr:`day`, :attr:`hour`, :attr:`minute`, :attr:`second`, :attr:`microsecond` " +"ve :attr:`.tzinfo`." #: library/datetime.rst:133 #, fuzzy msgid "" -"A duration expressing the difference between two :class:`.datetime` or :" -"class:`date` instances to microsecond resolution." +"A duration expressing the difference between two :class:`.datetime` " +"or :class:`date` instances to microsecond resolution." msgstr "" "İki :class:`date`, :class:`.time` veya :class:`.datetime` örneği arasındaki " "farkı mikrosaniye çözünürlüğünde ifade eden bir süre." @@ -259,10 +261,10 @@ msgid "" "notion of time adjustment (for example, to account for time zone and/or " "daylight saving time)." msgstr "" -"Zaman dilimi bilgi nesneleri için soyut bir temel sınıf. Bunlar :class:`." -"datetime` ve :class:`.time` sınıfları tarafından özelleştirilebilir bir " -"zaman ayarlaması sağlamak için kullanılır (örneğin, saat dilimini ve/veya " -"yaz saati uygulamasını hesaba katmak için)." +"Zaman dilimi bilgi nesneleri için soyut bir temel sınıf. " +"Bunlar :class:`.datetime` ve :class:`.time` sınıfları tarafından " +"özelleştirilebilir bir zaman ayarlaması sağlamak için kullanılır (örneğin, " +"saat dilimini ve/veya yaz saati uygulamasını hesaba katmak için)." #: library/datetime.rst:148 msgid "" @@ -493,11 +495,11 @@ msgstr "" #: library/datetime.rst:253 msgid "" -"If the normalized value of days lies outside the indicated range, :exc:" -"`OverflowError` is raised." +"If the normalized value of days lies outside the indicated " +"range, :exc:`OverflowError` is raised." msgstr "" -"Günlerin normalleştirilmiş değeri belirtilen aralığın dışında kalıyorsa, :" -"exc:`OverflowError` ortaya çıkar." +"Günlerin normalleştirilmiş değeri belirtilen aralığın dışında " +"kalıyorsa, :exc:`OverflowError` ortaya çıkar." #: library/datetime.rst:256 msgid "" @@ -543,8 +545,8 @@ msgstr "" #, fuzzy msgid "" "Note that, because of normalization, ``timedelta.max`` is greater than ``-" -"timedelta.min``. ``-timedelta.max`` is not representable as a :class:" -"`timedelta` object." +"timedelta.min``. ``-timedelta.max`` is not representable as " +"a :class:`timedelta` object." msgstr "" "Normalleştirme nedeniyle ``timedelta.max`` > ``-timedelta.min`` olduğuna " "dikkat edin. ``-timedelta.max`` bir :class:`timedelta` nesnesi olarak temsil " @@ -654,8 +656,8 @@ msgstr "" #: library/datetime.rst:344 msgid "" -"Division (3) of overall duration ``t2`` by interval unit ``t3``. Returns a :" -"class:`float` object." +"Division (3) of overall duration ``t2`` by interval unit ``t3``. Returns " +"a :class:`float` object." msgstr "" #: library/datetime.rst:348 @@ -793,16 +795,16 @@ msgstr "" #: library/datetime.rst:413 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)." +"support certain additions and subtractions with :class:`date` " +"and :class:`.datetime` objects (see below)." msgstr "" #: library/datetime.rst:417 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." +"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 "" #: library/datetime.rst:423 @@ -935,19 +937,19 @@ msgstr "" #: library/datetime.rst:509 msgid "" "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`." +"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 "" #: library/datetime.rst:516 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." +"function. Raise :exc:`OSError` instead of :exc:`ValueError` " +"on :c:func:`localtime` failure." msgstr "" #: library/datetime.rst:525 @@ -1005,8 +1007,8 @@ msgstr "" #: library/datetime.rst:560 msgid "" "Return a :class:`date` corresponding to the ISO calendar date specified by " -"year, week and day. This is the inverse of the function :meth:`date." -"isocalendar`." +"year, week and day. This is the inverse of the " +"function :meth:`date.isocalendar`." msgstr "" #: library/datetime.rst:570 @@ -1095,9 +1097,9 @@ msgstr "" 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`." +"``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 "" #: library/datetime.rst:633 @@ -1106,8 +1108,8 @@ msgstr "" #: library/datetime.rst:636 msgid "" -"This is exact, and cannot overflow. ``timedelta.seconds`` and ``timedelta." -"microseconds`` are 0, and ``date2 + timedelta == date1`` after." +"This is exact, and cannot overflow. ``timedelta.seconds`` and " +"``timedelta.microseconds`` are 0, and ``date2 + timedelta == date1`` after." msgstr "" #: library/datetime.rst:640 @@ -1146,8 +1148,8 @@ msgstr "" #: library/datetime.rst:1361 msgid "" -"Return a :class:`time.struct_time` such as returned by :func:`time." -"localtime`." +"Return a :class:`time.struct_time` such as returned " +"by :func:`time.localtime`." msgstr "" #: library/datetime.rst:668 @@ -1172,22 +1174,22 @@ msgstr "" #: library/datetime.rst:680 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``." +"1 has ordinal 1. For any :class:`date` object ``d``, " +"``date.fromordinal(d.toordinal()) == d``." msgstr "" #: library/datetime.rst:687 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`." +"For example, ``date(2002, 12, 4).weekday() == 2``, a Wednesday. See " +"also :meth:`isoweekday`." msgstr "" #: library/datetime.rst:694 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`." +"For example, ``date(2002, 12, 4).isoweekday() == 3``, a Wednesday. See " +"also :meth:`weekday`, :meth:`isocalendar`." msgstr "" #: library/datetime.rst:701 @@ -1266,17 +1268,17 @@ msgstr "" #: library/datetime.rst:748 msgid "" -"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." +"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 "" #: library/datetime.rst:755 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. See also :ref:`strftime-strptime-behavior` and :meth:`date." -"isoformat`." +"values. See also :ref:`strftime-strptime-behavior` " +"and :meth:`date.isoformat`." msgstr "" #: library/datetime.rst:762 @@ -1456,10 +1458,11 @@ msgstr "" #: library/datetime.rst:888 msgid "" -"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)." +"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 "" #: library/datetime.rst:894 @@ -1519,21 +1522,21 @@ msgstr "" 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. This method is " -"preferred over :meth:`utcfromtimestamp`." +"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. This " +"method is preferred over :meth:`utcfromtimestamp`." msgstr "" #: library/datetime.rst:945 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." +"or :c:func:`gmtime` functions. Raise :exc:`OSError` instead " +"of :exc:`ValueError` on :c:func:`localtime` or :c:func:`gmtime` failure." msgstr "" #: library/datetime.rst:952 @@ -1549,9 +1552,9 @@ msgstr "" #: library/datetime.rst:960 msgid "" "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." +"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 "" #: library/datetime.rst:965 @@ -1575,8 +1578,8 @@ msgstr "" #: library/datetime.rst:974 msgid "" -"except the latter formula always supports the full years range: between :" -"const:`MINYEAR` and :const:`MAXYEAR` inclusive." +"except the latter formula always supports the full years range: " +"between :const:`MINYEAR` and :const:`MAXYEAR` inclusive." msgstr "" #: library/datetime.rst:979 @@ -1592,8 +1595,8 @@ msgstr "" 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." +"function. Raise :exc:`OSError` instead of :exc:`ValueError` " +"on :c:func:`gmtime` failure." msgstr "" #: library/datetime.rst:993 @@ -1616,14 +1619,14 @@ msgid "" "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. If the " -"*date* argument is a :class:`.datetime` object, its time components and :" -"attr:`.tzinfo` attributes are ignored." +"*date* argument is a :class:`.datetime` object, its time components " +"and :attr:`.tzinfo` attributes are ignored." msgstr "" #: library/datetime.rst:1014 msgid "" -"For any :class:`.datetime` object ``d``, ``d == datetime.combine(d.date(), d." -"time(), d.tzinfo)``." +"For any :class:`.datetime` object ``d``, ``d == datetime.combine(d.date(), " +"d.time(), d.tzinfo)``." msgstr "" #: library/datetime.rst:1017 @@ -1666,8 +1669,8 @@ msgid "" ">>> datetime.fromisoformat('2011-11-04 00:05:23.283')\n" "datetime.datetime(2011, 11, 4, 0, 5, 23, 283000)\n" ">>> datetime.fromisoformat('2011-11-04 00:05:23.283+00:00')\n" -"datetime.datetime(2011, 11, 4, 0, 5, 23, 283000, tzinfo=datetime.timezone." -"utc)\n" +"datetime.datetime(2011, 11, 4, 0, 5, 23, 283000, " +"tzinfo=datetime.timezone.utc)\n" ">>> datetime.fromisoformat('2011-11-04T00:05:23+04:00') \n" "datetime.datetime(2011, 11, 4, 0, 5, 23,\n" " tzinfo=datetime.timezone(datetime.timedelta(seconds=14400)))" @@ -1675,16 +1678,16 @@ msgstr "" #: library/datetime.rst:1059 msgid "" -"Previously, this method only supported formats that could be emitted by :" -"meth:`date.isoformat` or :meth:`datetime.isoformat`." +"Previously, this method only supported formats that could be emitted " +"by :meth:`date.isoformat` or :meth:`datetime.isoformat`." msgstr "" #: library/datetime.rst:1066 msgid "" "Return a :class:`.datetime` corresponding to the ISO calendar date specified " "by year, week and day. The non-date components of the datetime are populated " -"with their normal default values. This is the inverse of the function :meth:" -"`datetime.isocalendar`." +"with their normal default values. This is the inverse of the " +"function :meth:`datetime.isocalendar`." msgstr "" #: library/datetime.rst:1075 @@ -1707,8 +1710,8 @@ msgstr "" msgid "" ":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. " -"See also :ref:`strftime-strptime-behavior` and :meth:`datetime." -"fromisoformat`." +"See also :ref:`strftime-strptime-behavior` " +"and :meth:`datetime.fromisoformat`." msgstr "" #: library/datetime.rst:1093 @@ -1805,12 +1808,12 @@ msgstr "" #: library/datetime.rst:1183 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." +"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 "" #: library/datetime.rst:1192 @@ -1830,19 +1833,20 @@ msgstr "" #: library/datetime.rst:1201 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." +"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 "" #: library/datetime.rst:1206 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. The result is ``(a.replace(tzinfo=None) - a.utcoffset()) - (b." -"replace(tzinfo=None) - b.utcoffset())`` except that the implementation never " -"overflows." +"datetimes. The result is ``(a.replace(tzinfo=None) - a.utcoffset()) - " +"(b.replace(tzinfo=None) - b.utcoffset())`` except that the implementation " +"never overflows." msgstr "" #: library/datetime.rst:1212 @@ -1960,17 +1964,17 @@ msgstr "" #: library/datetime.rst:1307 msgid "" "If you merely want to attach a :class:`timezone` 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 :class:`!timezone` " -"object from an aware datetime *dt* without conversion of date and time data, " -"use ``dt.replace(tzinfo=None)``." +"*dt* without adjustment of date and time data, use " +"``dt.replace(tzinfo=tz)``. If you merely want to remove the :class:`!" +"timezone` object from an aware datetime *dt* without conversion of date and " +"time data, use ``dt.replace(tzinfo=None)``." msgstr "" #: library/datetime.rst:1312 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::" +"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 "" #: library/datetime.rst:1316 @@ -1996,9 +2000,10 @@ msgstr "" #: library/datetime.rst:1334 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 with magnitude less than one day." +"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 with magnitude less " +"than one day." msgstr "" #: library/datetime.rst:1930 library/datetime.rst:2282 @@ -2008,9 +2013,10 @@ msgstr "" #: library/datetime.rst:1344 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 with magnitude less than one day." +"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 with magnitude less than one " +"day." msgstr "" #: library/datetime.rst:1940 library/datetime.rst:2091 @@ -2019,9 +2025,9 @@ msgstr "" #: library/datetime.rst:1354 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," +"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 "" #: library/datetime.rst:1365 @@ -2034,29 +2040,29 @@ msgstr "" #: library/datetime.rst:1369 msgid "" "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:`~time.struct_time.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." +"day number within the current year starting with 1 for January 1st. " +"The :attr:`~time.struct_time.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 "" #: library/datetime.rst:1380 msgid "" -"If :class:`.datetime` instance ``d`` is naive, this is the same as ``d." -"timetuple()`` except that :attr:`~.time.struct_time.tm_isdst` is forced to 0 " -"regardless of what ``d.dst()`` returns. DST is never in effect for a UTC " -"time." +"If :class:`.datetime` instance ``d`` is naive, this is the same as " +"``d.timetuple()`` except that :attr:`~.time.struct_time.tm_isdst` is forced " +"to 0 regardless of what ``d.dst()`` returns. DST is never in effect for a " +"UTC time." msgstr "" #: library/datetime.rst:1384 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." +"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 "" #: library/datetime.rst:1393 @@ -2064,22 +2070,22 @@ msgid "" "Because naive ``datetime`` objects are treated by many ``datetime`` methods " "as local times, it is preferred to use aware datetimes to represent times in " "UTC; as a result, using :meth:`datetime.utctimetuple` may give misleading " -"results. If you have a naive ``datetime`` representing UTC, use ``datetime." -"replace(tzinfo=timezone.utc)`` to make it aware, at which point you can use :" -"meth:`.datetime.timetuple`." +"results. If you have a naive ``datetime`` representing UTC, use " +"``datetime.replace(tzinfo=timezone.utc)`` to make it aware, at which point " +"you can use :meth:`.datetime.timetuple`." msgstr "" #: library/datetime.rst:1402 msgid "" -"Return the proleptic Gregorian ordinal of the date. The same as ``self." -"date().toordinal()``." +"Return the proleptic Gregorian ordinal of the date. The same as " +"``self.date().toordinal()``." msgstr "" #: library/datetime.rst:1407 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`." +"return value is a :class:`float` similar to that returned " +"by :func:`time.time`." msgstr "" #: library/datetime.rst:1411 @@ -2087,9 +2093,9 @@ 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` or :exc:`OSError` for times far in the past or far in the " -"future." +"than :c:func:`mktime` on many platforms, this method may " +"raise :exc:`OverflowError` or :exc:`OSError` for times far in the past or " +"far in the future." msgstr "" #: library/datetime.rst:1418 @@ -2109,10 +2115,10 @@ msgstr "" #: library/datetime.rst:1431 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 time zone is not set to UTC, you can obtain " -"the POSIX timestamp by supplying ``tzinfo=timezone.utc``::" +"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 time zone is not set to UTC, you can " +"obtain the POSIX timestamp by supplying ``tzinfo=timezone.utc``::" msgstr "" #: library/datetime.rst:1437 @@ -2136,8 +2142,8 @@ msgstr "" #: library/datetime.rst:1451 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`." +"The same as ``self.date().isoweekday()``. See " +"also :meth:`weekday`, :meth:`isocalendar`." msgstr "" #: library/datetime.rst:1458 @@ -2266,8 +2272,8 @@ msgstr "" #: library/datetime.rst:1532 msgid "" -"For a :class:`.datetime` instance ``d``, ``str(d)`` is equivalent to ``d." -"isoformat(' ')``." +"For a :class:`.datetime` instance ``d``, ``str(d)`` is equivalent to " +"``d.isoformat(' ')``." msgstr "" #: library/datetime.rst:1538 @@ -2289,24 +2295,24 @@ msgstr "" #: library/datetime.rst:1551 msgid "" -"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." +"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 "" #: library/datetime.rst:1558 msgid "" "Return a string representing the date and time, controlled by an explicit " -"format string. See also :ref:`strftime-strptime-behavior` and :meth:" -"`datetime.isoformat`." +"format string. See also :ref:`strftime-strptime-behavior` " +"and :meth:`datetime.isoformat`." msgstr "" #: library/datetime.rst:1565 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`. See also :ref:" -"`strftime-strptime-behavior` and :meth:`datetime.isoformat`." +"literals ` and when using :meth:`str.format`. See " +"also :ref:`strftime-strptime-behavior` and :meth:`datetime.isoformat`." msgstr "" #: library/datetime.rst:1572 @@ -2331,8 +2337,8 @@ msgid "" ">>> datetime.now() \n" "datetime.datetime(2007, 12, 6, 16, 29, 43, 79043) # GMT +1\n" ">>> datetime.now(timezone.utc) \n" -"datetime.datetime(2007, 12, 6, 15, 29, 43, 79060, tzinfo=datetime.timezone." -"utc)\n" +"datetime.datetime(2007, 12, 6, 15, 29, 43, 79060, " +"tzinfo=datetime.timezone.utc)\n" "\n" ">>> # Using datetime.strptime()\n" ">>> dt = datetime.strptime(\"21/11/06 16:30\", \"%d/%m/%y %H:%M\")\n" @@ -2366,8 +2372,8 @@ msgid "" ">>> # Formatting a datetime\n" ">>> dt.strftime(\"%A, %d. %B %Y %I:%M%p\")\n" "'Tuesday, 21. November 2006 04:30PM'\n" -">>> 'The {1} is {0:%d}, the {2} is {0:%B}, the {3} is {0:%I:%M%p}.'." -"format(dt, \"day\", \"month\", \"time\")\n" +">>> 'The {1} is {0:%d}, the {2} is {0:%B}, the {3} is {0:%I:" +"%M%p}.'.format(dt, \"day\", \"month\", \"time\")\n" "'The day is 21, the month is November, the time is 04:30PM.'" msgstr "" @@ -2465,8 +2471,8 @@ msgstr "" #: library/datetime.rst:1707 msgid "" -"All arguments are optional. *tzinfo* may be ``None``, or an instance of a :" -"class:`tzinfo` subclass. The remaining arguments must be integers in the " +"All arguments are optional. *tzinfo* may be ``None``, or an instance of " +"a :class:`tzinfo` subclass. The remaining arguments must be integers in the " "following ranges:" msgstr "" @@ -2487,8 +2493,8 @@ msgstr "" #: library/datetime.rst:1735 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." +"``timedelta(microseconds=1)``, although note that arithmetic " +"on :class:`.time` objects is not supported." msgstr "" #: library/datetime.rst:1764 @@ -2577,8 +2583,8 @@ msgid "" ">>> time.fromisoformat('04:23:01,000384')\n" "datetime.time(4, 23, 1, 384)\n" ">>> time.fromisoformat('04:23:01+04:00')\n" -"datetime.time(4, 23, 1, tzinfo=datetime.timezone(datetime." -"timedelta(seconds=14400)))\n" +"datetime.time(4, 23, 1, " +"tzinfo=datetime.timezone(datetime.timedelta(seconds=14400)))\n" ">>> time.fromisoformat('04:23:01Z')\n" "datetime.time(4, 23, 1, tzinfo=datetime.timezone.utc)\n" ">>> time.fromisoformat('04:23:01+00:00')\n" @@ -2587,8 +2593,8 @@ msgstr "" #: library/datetime.rst:1842 msgid "" -"Previously, this method only supported formats that could be emitted by :" -"meth:`time.isoformat`." +"Previously, this method only supported formats that could be emitted " +"by :meth:`time.isoformat`." msgstr "" #: library/datetime.rst:1852 @@ -2619,8 +2625,8 @@ msgstr "" #: library/datetime.rst:1868 msgid "" -"``HH:MM:SS+HH:MM[:SS[.ffffff]]``, if :attr:`microsecond` is 0 and :meth:" -"`utcoffset` does not return ``None``" +"``HH:MM:SS+HH:MM[:SS[.ffffff]]``, if :attr:`microsecond` is 0 " +"and :meth:`utcoffset` does not return ``None``" msgstr "" #: library/datetime.rst:1888 @@ -2630,8 +2636,8 @@ msgstr "" #: library/datetime.rst:1892 msgid "" ">>> from datetime import time\n" -">>> time(hour=12, minute=34, second=56, microsecond=123456)." -"isoformat(timespec='minutes')\n" +">>> time(hour=12, minute=34, second=56, " +"microsecond=123456).isoformat(timespec='minutes')\n" "'12:34'\n" ">>> dt = time(hour=12, minute=34, second=56, microsecond=0)\n" ">>> dt.isoformat(timespec='microseconds')\n" @@ -2647,8 +2653,8 @@ msgstr "" #: library/datetime.rst:1912 msgid "" "Return a string representing the time, controlled by an explicit format " -"string. See also :ref:`strftime-strptime-behavior` and :meth:`time." -"isoformat`." +"string. See also :ref:`strftime-strptime-behavior` " +"and :meth:`time.isoformat`." msgstr "" #: library/datetime.rst:1918 @@ -2661,23 +2667,25 @@ msgstr "" #: library/datetime.rst:1926 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 with magnitude less than one day." +"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 with magnitude less " +"than one day." msgstr "" #: library/datetime.rst:1936 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 with magnitude less than one day." +"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 with magnitude less than one " +"day." msgstr "" #: library/datetime.rst:1945 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." +"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 "" #: library/datetime.rst:1950 @@ -2731,26 +2739,26 @@ msgstr "" 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." +"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 "" #: library/datetime.rst:1997 msgid "" "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 provides :class:" -"`timezone`, a simple concrete subclass of :class:`tzinfo` which can " -"represent time zones with fixed offset from UTC such as UTC itself or North " -"American EST and EDT." +"implementations of the standard :class:`tzinfo` methods needed by " +"the :class:`.datetime` methods you use. The :mod:`!datetime` module " +"provides :class:`timezone`, a simple concrete subclass of :class:`tzinfo` " +"which can represent time zones with fixed offset from UTC such as UTC itself " +"or North American EST and EDT." msgstr "" #: library/datetime.rst:2004 msgid "" -"Special requirement for pickling: A :class:`tzinfo` subclass must have an :" -"meth:`~object.__init__` method that can be called with no arguments, " +"Special requirement for pickling: A :class:`tzinfo` subclass must have " +"an :meth:`~object.__init__` method that can be called with no arguments, " "otherwise it can be pickled but possibly not unpickled again. This is a " "technical requirement that may be relaxed in the future." msgstr "" @@ -2758,8 +2766,8 @@ msgstr "" #: library/datetime.rst:2010 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." +"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 "" #: library/datetime.rst:2017 @@ -2770,13 +2778,14 @@ msgstr "" #: library/datetime.rst:2020 msgid "" -"This represents 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 " -"strictly between ``-timedelta(hours=24)`` and ``timedelta(hours=24)`` (the " -"magnitude of the offset must be less than one day). Most implementations of :" -"meth:`utcoffset` will probably look like one of these two::" +"This represents 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 strictly between ``-timedelta(hours=24)`` and " +"``timedelta(hours=24)`` (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 "" #: library/datetime.rst:2028 @@ -2793,8 +2802,8 @@ msgstr "" #: library/datetime.rst:2034 msgid "" -"The default implementation of :meth:`utcoffset` raises :exc:" -"`NotImplementedError`." +"The default implementation of :meth:`utcoffset` " +"raises :exc:`NotImplementedError`." msgstr "" #: library/datetime.rst:2043 @@ -2808,12 +2817,13 @@ msgid "" "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:`~time.struct_time." -"tm_isdst` flag should be set, and :meth:`tzinfo.fromutc` calls :meth:`dst` " -"to account for DST changes when crossing time zones." +"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:`~time.struct_time.tm_isdst` flag should be set, " +"and :meth:`tzinfo.fromutc` calls :meth:`dst` to account for DST changes when " +"crossing time zones." msgstr "" #: library/datetime.rst:2057 @@ -2828,15 +2838,15 @@ msgstr "" #: library/datetime.rst:2062 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:`~.datetime." -"astimezone` regardless." +"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:`~.datetime.astimezone` regardless." msgstr "" #: library/datetime.rst:2071 @@ -2882,16 +2892,16 @@ msgid "" "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." +"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 "" #: library/datetime.rst:2107 msgid "" -"The default implementation of :meth:`tzname` raises :exc:" -"`NotImplementedError`." +"The default implementation of :meth:`tzname` " +"raises :exc:`NotImplementedError`." msgstr "" #: library/datetime.rst:2110 @@ -2900,8 +2910,8 @@ msgid "" "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`." +"prepared to accept a *dt* argument of ``None``, or of " +"class :class:`.datetime`." msgstr "" #: library/datetime.rst:2116 @@ -2915,12 +2925,12 @@ msgstr "" #: library/datetime.rst:2122 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 time " -"zones." +"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 time zones." msgstr "" #: library/datetime.rst:2128 @@ -2933,24 +2943,24 @@ msgstr "" msgid "" "This is called from the default :meth:`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." +"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 "" #: library/datetime.rst:2139 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:" -"`~.datetime.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." +"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:`~.datetime.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 "" #: library/datetime.rst:2150 @@ -2979,8 +2989,8 @@ msgstr "" #: library/datetime.rst:2168 msgid "" -"In the following :download:`tzinfo_examples.py <../includes/tzinfo_examples." -"py>` file there are some examples of :class:`tzinfo` classes:" +"In the following :download:`tzinfo_examples.py <../includes/" +"tzinfo_examples.py>` file there are some examples of :class:`tzinfo` classes:" msgstr "" #: library/datetime.rst:2172 @@ -3165,11 +3175,11 @@ msgstr "" #: library/datetime.rst:2174 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::" +"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 "" #: library/datetime.rst:2180 @@ -3246,11 +3256,11 @@ msgstr "" #: library/datetime.rst:2232 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))." +"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 "" #: library/datetime.rst:2240 @@ -3347,8 +3357,8 @@ msgstr "" #: library/datetime.rst:2319 msgid "" -"Return ``dt + offset``. The *dt* argument must be an aware :class:`." -"datetime` instance, with ``tzinfo`` set to ``self``." +"Return ``dt + offset``. The *dt* argument must be an " +"aware :class:`.datetime` instance, with ``tzinfo`` set to ``self``." msgstr "" #: library/datetime.rst:2326 @@ -3368,15 +3378,15 @@ msgstr "" #: library/datetime.rst:2341 msgid "" -"Conversely, the :meth:`datetime.strptime` class method creates a :class:`." -"datetime` object from a string representing a date and time and a " +"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." msgstr "" #: library/datetime.rst:2345 msgid "" -"The table below provides a high-level comparison of :meth:`~.datetime." -"strftime` versus :meth:`~.datetime.strptime`:" +"The table below provides a high-level comparison " +"of :meth:`~.datetime.strftime` versus :meth:`~.datetime.strptime`:" msgstr "" #: library/datetime.rst:2349 @@ -3889,11 +3899,11 @@ msgstr "" #: library/datetime.rst:2503 msgid "" -"These may not be available on all platforms when used with the :meth:`~." -"datetime.strftime` method. The ISO 8601 year and ISO 8601 week directives " -"are not interchangeable with the year and week number directives above. " -"Calling :meth:`~.datetime.strptime` with incomplete or ambiguous ISO 8601 " -"directives will raise a :exc:`ValueError`." +"These may not be available on all platforms when used with " +"the :meth:`~.datetime.strftime` method. The ISO 8601 year and ISO 8601 week " +"directives are not interchangeable with the year and week number directives " +"above. Calling :meth:`~.datetime.strptime` with incomplete or ambiguous ISO " +"8601 directives will raise a :exc:`ValueError`." msgstr "" #: library/datetime.rst:2508 @@ -3921,8 +3931,8 @@ msgstr "" #: library/datetime.rst:2523 msgid "" "Broadly speaking, ``d.strftime(fmt)`` acts like the :mod:`time` module's " -"``time.strftime(fmt, d.timetuple())`` although not all objects support a :" -"meth:`~date.timetuple` method." +"``time.strftime(fmt, d.timetuple())`` although not all objects support " +"a :meth:`~date.timetuple` method." msgstr "" #: library/datetime.rst:2527 @@ -3962,8 +3972,8 @@ msgid "" "For the same reason, handling of format strings containing Unicode code " "points that can't be represented in the charset of the current locale is " "also platform-dependent. On some platforms such code points are preserved " -"intact in the output, while on others ``strftime`` may raise :exc:" -"`UnicodeError` or return an empty string instead." +"intact in the output, while on others ``strftime`` may " +"raise :exc:`UnicodeError` or return an empty string instead." msgstr "" #: library/datetime.rst:2556 @@ -4032,9 +4042,9 @@ msgid "" "seconds and ``ffffff`` is a 6-digit string giving the number of UTC offset " "microseconds. The ``ffffff`` part is omitted when the offset is a whole " "number of seconds and both the ``ffffff`` and the ``SS`` part is omitted " -"when the offset is a whole number of minutes. For example, if :meth:`~." -"datetime.utcoffset` returns ``timedelta(hours=-3, minutes=-30)``, ``%z`` is " -"replaced with the string ``'-0330'``." +"when the offset is a whole number of minutes. For example, " +"if :meth:`~.datetime.utcoffset` returns ``timedelta(hours=-3, " +"minutes=-30)``, ``%z`` is replaced with the string ``'-0330'``." msgstr "" #: library/datetime.rst:2609 @@ -4054,9 +4064,9 @@ msgstr "" #: library/datetime.rst:2621 msgid "" -"In :meth:`~.datetime.strftime`, ``%Z`` is replaced by an empty string if :" -"meth:`~.datetime.tzname` returns ``None``; otherwise ``%Z`` is replaced by " -"the returned value, which must be a string." +"In :meth:`~.datetime.strftime`, ``%Z`` is replaced by an empty string " +"if :meth:`~.datetime.tzname` returns ``None``; otherwise ``%Z`` is replaced " +"by the returned value, which must be a string." msgstr "" #: library/datetime.rst:2625 @@ -4095,9 +4105,9 @@ msgstr "" #: library/datetime.rst:2645 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:`~." -"datetime.strptime` format string. Also note that ``%G`` and ``%Y`` are not " -"interchangeable." +"day of the week and the ISO year (``%G``) are specified in " +"a :meth:`~.datetime.strptime` format string. Also note that ``%G`` and " +"``%Y`` are not interchangeable." msgstr "" #: library/datetime.rst:2651 diff --git a/library/dbm.po b/library/dbm.po index 1785fecc4..e5e21aa74 100644 --- a/library/dbm.po +++ b/library/dbm.po @@ -26,11 +26,11 @@ msgstr "" #: 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." +":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 "" #: library/dbm.rst:20 @@ -80,10 +80,10 @@ msgstr "" #: library/dbm.rst:63 msgid "" -"The database file to open. 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 submodule listed above that can be " -"imported is used." +"The database file to open. 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 submodule listed " +"above that can be imported is used." msgstr "" #: library/dbm.rst:174 @@ -131,8 +131,8 @@ msgstr "" msgid "" "The object returned by :func:`~dbm.open` supports the same basic " "functionality as a :class:`dict`; 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:`!" +"stored, retrieved, and deleted, and the :keyword:`in` operator and " +"the :meth:`!keys` method are available, as well as :meth:`!get` and :meth:`!" "setdefault` methods." msgstr "" @@ -151,8 +151,8 @@ msgstr "" #: library/dbm.rst:95 msgid "" -":meth:`!get` and :meth:`!setdefault` methods are now available for all :mod:" -"`dbm` backends." +":meth:`!get` and :meth:`!setdefault` methods are now available for " +"all :mod:`dbm` backends." msgstr "" #: library/dbm.rst:99 @@ -235,9 +235,9 @@ msgstr "" #: library/dbm.rst:166 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." +"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 "" #: library/dbm.rst:172 @@ -300,9 +300,9 @@ msgstr "" #: library/dbm.rst:209 msgid "" -":class:`!gdbm` objects behave similar to :term:`mappings `, but :" -"meth:`!items` and :meth:`!values` methods are not supported. The following " -"methods are also provided:" +":class:`!gdbm` objects behave similar to :term:`mappings `, " +"but :meth:`!items` and :meth:`!values` methods are not supported. The " +"following methods are also provided:" msgstr "" #: library/dbm.rst:215 @@ -331,10 +331,10 @@ msgstr "" #: library/dbm.rst:233 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. :" -"class:`!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." +"space used by the GDBM file, this routine will reorganize the " +"database. :class:`!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 "" #: library/dbm.rst:241 @@ -372,9 +372,9 @@ msgstr "" #: library/dbm.rst:279 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." +"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 "" #: library/dbm.rst:285 @@ -393,9 +393,9 @@ msgstr "" #: library/dbm.rst:306 msgid "" -":class:`!ndbm` objects behave similar to :term:`mappings `, but :" -"meth:`!items` and :meth:`!values` methods are not supported. The following " -"methods are also provided:" +":class:`!ndbm` objects behave similar to :term:`mappings `, " +"but :meth:`!items` and :meth:`!values` methods are not supported. The " +"following methods are also provided:" msgstr "" #: library/dbm.rst:310 @@ -416,10 +416,10 @@ msgstr "" #: library/dbm.rst:330 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." +"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 "" #: library/dbm.rst:337 @@ -435,9 +435,9 @@ msgstr "" #: library/dbm.rst:346 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." +"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 "" #: library/dbm.rst:352 @@ -450,8 +450,8 @@ msgstr "" #: library/dbm.rst:357 msgid "" "The basename of the database file (without extensions). A new database " -"creates the following files: - :file:`{filename}.dat` - :file:`{filename}." -"dir`" +"creates the following files: - :file:`{filename}.dat` " +"- :file:`{filename}.dir`" msgstr "" #: library/dbm.rst:358 @@ -502,8 +502,9 @@ msgstr "" #: library/dbm.rst:389 msgid "" -"In addition to the methods provided by the :class:`collections.abc." -"MutableMapping` class, the following methods are provided:" +"In addition to the methods provided by " +"the :class:`collections.abc.MutableMapping` class, the following methods are " +"provided:" msgstr "" #: library/dbm.rst:395 diff --git a/library/decimal.po b/library/decimal.po index 104197fe8..90b1779df 100644 --- a/library/decimal.po +++ b/library/decimal.po @@ -27,8 +27,8 @@ msgstr "" #: library/decimal.rst:33 msgid "" "The :mod:`decimal` module provides support for fast correctly rounded " -"decimal floating-point arithmetic. It offers several advantages over the :" -"class:`float` datatype:" +"decimal floating-point arithmetic. It offers several advantages over " +"the :class:`float` datatype:" msgstr "" #: library/decimal.rst:37 @@ -113,9 +113,9 @@ 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`." +"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 "" #: library/decimal.rst:101 @@ -123,10 +123,9 @@ 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`." +"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 "" #: library/decimal.rst:108 @@ -309,16 +308,16 @@ msgstr "" #: library/decimal.rst:266 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." +"the Context() constructor. To make an alternate active, use " +"the :func:`setcontext` function." msgstr "" #: library/decimal.rst:270 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:" +"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 "" #: library/decimal.rst:275 @@ -409,11 +408,11 @@ msgstr "" #: library/decimal.rst:350 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::" +"*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 "" #: library/decimal.rst:355 @@ -500,8 +499,8 @@ msgid "" "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`)." +"compared, sorted, and coerced to another type (such as :class:`float` " +"or :class:`int`)." msgstr "" #: library/decimal.rst:413 @@ -543,13 +542,13 @@ msgstr "" #: library/decimal.rst:436 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." +"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 "" #: library/decimal.rst:444 @@ -574,9 +573,9 @@ msgstr "" #: library/decimal.rst:461 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::" +"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 "" #: library/decimal.rst:465 @@ -655,8 +654,8 @@ msgstr "" 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())``." +"``x.compare_total_mag(y)`` is equivalent to " +"``x.copy_abs().compare_total(y.copy_abs())``." msgstr "" #: library/decimal.rst:537 @@ -692,8 +691,8 @@ msgstr "" #: library/decimal.rst:576 msgid "" -"Alternative constructor that only accepts instances of :class:`float` or :" -"class:`int`." +"Alternative constructor that only accepts instances of :class:`float` " +"or :class:`int`." msgstr "" #: library/decimal.rst:579 @@ -750,14 +749,14 @@ msgstr "" #: library/decimal.rst:627 msgid "" -"Return :const:`True` if the argument is a (quiet or signaling) NaN and :" -"const:`False` otherwise." +"Return :const:`True` if the argument is a (quiet or signaling) NaN " +"and :const:`False` otherwise." msgstr "" #: library/decimal.rst:632 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." +"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 "" #: library/decimal.rst:637 @@ -786,8 +785,8 @@ msgstr "" #: library/decimal.rst:657 msgid "" -"Return :const:`True` if the argument is a (positive or negative) zero and :" -"const:`False` otherwise." +"Return :const:`True` if the argument is a (positive or negative) zero " +"and :const:`False` otherwise." msgstr "" #: library/decimal.rst:662 @@ -804,8 +803,8 @@ msgstr "" #: library/decimal.rst:672 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('-" +"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 "" @@ -998,8 +997,8 @@ msgstr "" #: library/decimal.rst:803 msgid "" -"An error is returned whenever the resulting exponent is greater than :attr:" -"`~Context.Emax` or less than :meth:`~Context.Etiny`." +"An error is returned whenever the resulting exponent is greater " +"than :attr:`~Context.Emax` or less than :meth:`~Context.Etiny`." msgstr "" #: library/decimal.rst:808 @@ -1094,9 +1093,9 @@ msgstr "" #: library/decimal.rst:896 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." +"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 "" #: library/decimal.rst:900 @@ -1106,8 +1105,8 @@ msgstr "" #: library/decimal.rst:905 msgid "" "If *ndigits* is not given or ``None``, returns the nearest :class:`int` to " -"*number*, rounding ties to even, and ignoring the rounding mode of the :" -"class:`Decimal` context. Raises :exc:`OverflowError` if *number* is an " +"*number*, rounding ties to even, and ignoring the rounding mode of " +"the :class:`Decimal` context. Raises :exc:`OverflowError` if *number* is an " "infinity or :exc:`ValueError` if it is a (quiet or signaling) NaN." msgstr "" @@ -1117,10 +1116,11 @@ msgid "" "and a :class:`Decimal` representing *number* rounded to the nearest multiple " "of ``Decimal('1E-ndigits')`` is returned; in this case, ``round(number, " "ndigits)`` is equivalent to ``self.quantize(Decimal('1E-ndigits'))``. " -"Returns ``Decimal('NaN')`` if *number* is a quiet NaN. Raises :class:" -"`InvalidOperation` if *number* is an infinity, a signaling NaN, or if the " -"length of the coefficient after the quantize operation would be greater than " -"the current context's precision. In other words, for the non-corner cases:" +"Returns ``Decimal('NaN')`` if *number* is a quiet NaN. " +"Raises :class:`InvalidOperation` if *number* is an infinity, a signaling " +"NaN, or if the length of the coefficient after the quantize operation would " +"be greater than the current context's precision. In other words, for the " +"non-corner cases:" msgstr "" #: library/decimal.rst:921 @@ -1165,11 +1165,11 @@ msgstr "" #: library/decimal.rst:948 msgid "" -"The :meth:`~Decimal.logical_and`, :meth:`~Decimal.logical_invert`, :meth:" -"`~Decimal.logical_or`, and :meth:`~Decimal.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 ``0`` or ``1``." +"The :meth:`~Decimal.logical_and`, :meth:`~Decimal.logical_invert`, :meth:`~Decimal.logical_or`, " +"and :meth:`~Decimal.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 ``0`` " +"or ``1``." msgstr "" #: library/decimal.rst:960 @@ -1244,9 +1244,9 @@ msgstr "" #: library/decimal.rst:1008 msgid "" -"Raises :exc:`TypeError` if *kwargs* supplies an attribute that :class:" -"`Context` doesn't support. Raises either :exc:`TypeError` or :exc:" -"`ValueError` if *kwargs* supplies an invalid value for an attribute." +"Raises :exc:`TypeError` if *kwargs* supplies an attribute " +"that :class:`Context` doesn't support. Raises either :exc:`TypeError` " +"or :exc:`ValueError` if *kwargs* supplies an invalid value for an attribute." msgstr "" #: library/decimal.rst:1012 @@ -1264,10 +1264,10 @@ msgstr "" #: library/decimal.rst:1021 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`." +"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 "" #: library/decimal.rst:1027 @@ -1278,9 +1278,9 @@ msgstr "" #: library/decimal.rst:1032 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)." +"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 "" #: library/decimal.rst:1037 @@ -1315,9 +1315,10 @@ msgstr "" #: library/decimal.rst:1057 msgid "" -"The default values are :attr:`Context.prec`\\ =\\ ``28``, :attr:`Context." -"rounding`\\ =\\ :const:`ROUND_HALF_EVEN`, and enabled traps for :class:" -"`Overflow`, :class:`InvalidOperation`, and :class:`DivisionByZero`." +"The default values are :attr:`Context.prec`\\ =\\ " +"``28``, :attr:`Context.rounding`\\ =\\ :const:`ROUND_HALF_EVEN`, and enabled " +"traps for :class:`Overflow`, :class:`InvalidOperation`, " +"and :class:`DivisionByZero`." msgstr "" #: library/decimal.rst:1062 @@ -1396,12 +1397,13 @@ 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:`~Decimal.adjusted` and :meth:" -"`~Decimal.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." +"above (with the exception of the :meth:`~Decimal.adjusted` " +"and :meth:`~Decimal.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 "" #: library/decimal.rst:1120 @@ -1475,8 +1477,8 @@ msgstr "" #: library/decimal.rst:1182 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`." +"value for subnormal results. When underflow occurs, the exponent is set " +"to :const:`Etiny`." msgstr "" #: library/decimal.rst:1188 @@ -1692,9 +1694,9 @@ msgstr "" #: library/decimal.rst:1433 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\"." +"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 "" #: library/decimal.rst:1438 @@ -1899,9 +1901,9 @@ msgstr "" #: library/decimal.rst:1615 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." +"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 "" #: library/decimal.rst:1623 @@ -1910,9 +1912,9 @@ msgstr "" #: library/decimal.rst:1625 msgid "" -"Typically, clamping occurs when an exponent falls outside the context's :" -"attr:`~Context.Emin` and :attr:`~Context.Emax` limits. If possible, the " -"exponent is reduced to fit by adding zeros to the coefficient." +"Typically, clamping occurs when an exponent falls outside the " +"context's :attr:`~Context.Emin` and :attr:`~Context.Emax` limits. If " +"possible, the exponent is reduced to fit by adding zeros to the coefficient." msgstr "" #: library/decimal.rst:1632 @@ -1973,8 +1975,8 @@ msgid "" "Indicates the exponent is larger than :attr:`Context.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 ``Infinity``. In either case, :class:`Inexact` and :class:" -"`Rounded` are also signaled." +"outward to ``Infinity``. In either case, :class:`Inexact` " +"and :class:`Rounded` are also signaled." msgstr "" #: library/decimal.rst:1684 @@ -2004,8 +2006,8 @@ msgstr "" #: library/decimal.rst:1704 msgid "" -"Occurs when a subnormal result is pushed to zero by rounding. :class:" -"`Inexact` and :class:`Subnormal` are also signaled." +"Occurs when a subnormal result is pushed to zero by " +"rounding. :class:`Inexact` and :class:`Subnormal` are also signaled." msgstr "" #: library/decimal.rst:1710 @@ -2015,19 +2017,19 @@ msgstr "" #: library/decimal.rst:1712 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." +"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 "" #: library/decimal.rst:1720 msgid "" "Otherwise (the signal is trapped), only equality comparisons and explicit " -"conversions are silent. All other mixed operations raise :exc:" -"`FloatOperation`." +"conversions are silent. All other mixed operations " +"raise :exc:`FloatOperation`." msgstr "" #: library/decimal.rst:1724 @@ -2144,10 +2146,10 @@ msgstr "" #: library/decimal.rst:1814 msgid "" -"Some operations are indeterminate and return ``NaN``, or if the :exc:" -"`InvalidOperation` signal is trapped, raise an exception. For example, " -"``0/0`` returns ``NaN`` which means \"not a number\". This variety of " -"``NaN`` is quiet and, once created, will flow through other computations " +"Some operations are indeterminate and return ``NaN``, or if " +"the :exc:`InvalidOperation` signal is trapped, raise an exception. For " +"example, ``0/0`` returns ``NaN`` which means \"not a number\". This variety " +"of ``NaN`` is quiet and, once created, will flow through other computations " "always resulting in another ``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." @@ -2167,14 +2169,14 @@ msgid "" "is a quiet or signaling ``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 ``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 " +"of the ``<``, ``<=``, ``>`` or ``>=`` operators will raise " +"the :exc:`InvalidOperation` signal if either operand is a ``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 ``NaN`` were taken from " "the IEEE 854 standard (see Table 3 in section 5.7). To ensure strict " -"standards-compliance, use the :meth:`~Decimal.compare` and :meth:`~Decimal." -"compare_signal` methods instead." +"standards-compliance, use the :meth:`~Decimal.compare` " +"and :meth:`~Decimal.compare_signal` methods instead." msgstr "" #: library/decimal.rst:1839 @@ -2214,9 +2216,9 @@ msgstr "" #: library/decimal.rst:1868 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." +"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 "" #: library/decimal.rst:1872 @@ -2585,8 +2587,8 @@ msgstr "" #: library/decimal.rst:2217 msgid "" -"Alternatively, inputs can be rounded upon creation using the :meth:`Context." -"create_decimal` method:" +"Alternatively, inputs can be rounded upon creation using " +"the :meth:`Context.create_decimal` method:" msgstr "" #: library/decimal.rst:2223 @@ -2596,10 +2598,10 @@ msgstr "" #: library/decimal.rst:2225 msgid "" "A. Yes. In the CPython and PyPy3 implementations, the C/CFFI versions of " -"the decimal module integrate the high speed `libmpdec `_ library for arbitrary precision " -"correctly rounded decimal floating-point arithmetic [#]_. ``libmpdec`` uses " -"`Karatsuba multiplication `_ library for arbitrary " +"precision correctly rounded decimal floating-point arithmetic [#]_. " +"``libmpdec`` uses `Karatsuba multiplication `_ for medium-sized numbers and the `Number Theoretic " "Transform `_ for very " @@ -2608,10 +2610,10 @@ msgstr "" #: library/decimal.rst:2235 msgid "" -"The context must be adapted for exact arbitrary precision arithmetic. :attr:" -"`~Context.Emin` and :attr:`~Context.Emax` should always be set to the " -"maximum values, :attr:`~Context.clamp` should always be 0 (the default). " -"Setting :attr:`~Context.prec` requires some care." +"The context must be adapted for exact arbitrary precision " +"arithmetic. :attr:`~Context.Emin` and :attr:`~Context.Emax` should always be " +"set to the maximum values, :attr:`~Context.clamp` should always be 0 (the " +"default). Setting :attr:`~Context.prec` requires some care." msgstr "" #: library/decimal.rst:2239 diff --git a/library/devmode.po b/library/devmode.po index a73084a38..af82dbe9a 100644 --- a/library/devmode.po +++ b/library/devmode.po @@ -92,9 +92,9 @@ msgstr "" #: library/devmode.rst:41 msgid "" -"Use the :option:`-W error <-W>` command line option or set the :envvar:" -"`PYTHONWARNINGS` environment variable to ``error`` to treat warnings as " -"errors." +"Use the :option:`-W error <-W>` command line option or set " +"the :envvar:`PYTHONWARNINGS` environment variable to ``error`` to treat " +"warnings as errors." msgstr "" #: library/devmode.rst:45 @@ -137,9 +137,8 @@ msgstr "" #: library/devmode.rst:61 msgid "" "Call :func:`faulthandler.enable` at Python startup to install handlers for " -"the :const:`~signal.SIGSEGV`, :const:`~signal.SIGFPE`, :const:`~signal." -"SIGABRT`, :const:`~signal.SIGBUS` and :const:`~signal.SIGILL` signals to " -"dump the Python traceback on a crash." +"the :const:`~signal.SIGSEGV`, :const:`~signal.SIGFPE`, :const:`~signal.SIGABRT`, :const:`~signal.SIGBUS` " +"and :const:`~signal.SIGILL` signals to dump the Python traceback on a crash." msgstr "" #: library/devmode.rst:66 @@ -151,8 +150,9 @@ msgstr "" #: library/devmode.rst:70 msgid "" -"Enable :ref:`asyncio debug mode `. For example, :mod:" -"`asyncio` checks for coroutines that were not awaited and logs them." +"Enable :ref:`asyncio debug mode `. For " +"example, :mod:`asyncio` checks for coroutines that were not awaited and logs " +"them." msgstr "" #: library/devmode.rst:73 @@ -164,8 +164,8 @@ msgstr "" #: library/devmode.rst:76 msgid "" "Check the *encoding* and *errors* arguments for string encoding and decoding " -"operations. Examples: :func:`open`, :meth:`str.encode` and :meth:`bytes." -"decode`." +"operations. Examples: :func:`open`, :meth:`str.encode` " +"and :meth:`bytes.decode`." msgstr "" #: library/devmode.rst:80 @@ -190,17 +190,17 @@ msgid "" "The Python Development Mode does not enable the :mod:`tracemalloc` module by " "default, because the overhead cost (to performance and memory) would be too " "large. Enabling the :mod:`tracemalloc` module provides additional " -"information on the origin of some errors. For example, :exc:" -"`ResourceWarning` logs the traceback where the resource was allocated, and a " -"buffer overflow error logs the traceback where the memory block was " -"allocated." +"information on the origin of some errors. For " +"example, :exc:`ResourceWarning` logs the traceback where the resource was " +"allocated, and a buffer overflow error logs the traceback where the memory " +"block was allocated." msgstr "" #: library/devmode.rst:95 msgid "" "The Python Development Mode does not prevent the :option:`-O` command line " -"option from removing :keyword:`assert` statements nor from setting :const:" -"`__debug__` to ``False``." +"option from removing :keyword:`assert` statements nor from " +"setting :const:`__debug__` to ``False``." msgstr "" #: library/devmode.rst:99 @@ -265,8 +265,8 @@ msgstr "" msgid "" "$ python -X dev script.py README.txt\n" "269\n" -"script.py:10: ResourceWarning: unclosed file <_io.TextIOWrapper name='README." -"rst' mode='r' encoding='UTF-8'>\n" +"script.py:10: ResourceWarning: unclosed file <_io.TextIOWrapper " +"name='README.rst' mode='r' encoding='UTF-8'>\n" " main()\n" "ResourceWarning: Enable tracemalloc to get the object allocation traceback" msgstr "" @@ -281,8 +281,8 @@ msgstr "" msgid "" "$ python -X dev -X tracemalloc=5 script.py README.rst\n" "269\n" -"script.py:10: ResourceWarning: unclosed file <_io.TextIOWrapper name='README." -"rst' mode='r' encoding='UTF-8'>\n" +"script.py:10: ResourceWarning: unclosed file <_io.TextIOWrapper " +"name='README.rst' mode='r' encoding='UTF-8'>\n" " main()\n" "Object allocated at (most recent call last):\n" " File \"script.py\", lineno 10\n" @@ -355,8 +355,8 @@ msgstr "" msgid "" "$ python -X dev script.py\n" "import os\n" -"script.py:10: ResourceWarning: unclosed file <_io.TextIOWrapper name='script." -"py' mode='r' encoding='UTF-8'>\n" +"script.py:10: ResourceWarning: unclosed file <_io.TextIOWrapper " +"name='script.py' mode='r' encoding='UTF-8'>\n" " main()\n" "ResourceWarning: Enable tracemalloc to get the object allocation traceback\n" "Exception ignored in: <_io.TextIOWrapper name='script.py' mode='r' " @@ -372,8 +372,8 @@ msgid "" "``os.close(fp.fileno())`` closes the file descriptor. When the file object " "finalizer tries to close the file descriptor again, it fails with the ``Bad " "file descriptor`` error. A file descriptor must be closed only once. In the " -"worst case scenario, closing it twice can lead to a crash (see :issue:" -"`18748` for an example)." +"worst case scenario, closing it twice can lead to a crash " +"(see :issue:`18748` for an example)." msgstr "" #: library/devmode.rst:219 diff --git a/library/difflib.po b/library/difflib.po index 86da66d4b..0d56c51b1 100644 --- a/library/difflib.po +++ b/library/difflib.po @@ -164,10 +164,10 @@ msgstr "" #: library/difflib.rst:105 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." +"*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 "" #: library/difflib.rst:109 @@ -221,8 +221,8 @@ msgstr "" #: library/difflib.rst:145 msgid "" -"The arguments for this method are the same as those for the :meth:" -"`make_file` method." +"The arguments for this method are the same as those for " +"the :meth:`make_file` method." msgstr "" #: library/difflib.rst:152 @@ -444,8 +444,8 @@ msgstr "" #: library/difflib.rst:380 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`." +"default to empty strings. The elements of both sequences must " +"be :term:`hashable`." msgstr "" #: library/difflib.rst:383 @@ -460,8 +460,8 @@ msgid "" "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`." +"where they occur. All three are reset whenever *b* is reset " +"with :meth:`set_seqs` or :meth:`set_seq2`." msgstr "" #: library/difflib.rst:396 @@ -544,8 +544,8 @@ msgstr "" #: library/difflib.rst:466 msgid "" "Return list of triples describing non-overlapping 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*." +"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 "" #: library/difflib.rst:471 @@ -662,9 +662,10 @@ msgstr "" #: library/difflib.rst:547 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." +"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 "" #: library/difflib.rst:554 @@ -692,10 +693,10 @@ msgstr "" #: library/difflib.rst:573 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:`~SequenceMatcher.quick_ratio` and :meth:`~SequenceMatcher." -"real_quick_ratio` are always at least as large as :meth:`~SequenceMatcher." -"ratio`:" +"give different results due to differing levels of approximation, " +"although :meth:`~SequenceMatcher.quick_ratio` " +"and :meth:`~SequenceMatcher.real_quick_ratio` are always at least as large " +"as :meth:`~SequenceMatcher.ratio`:" msgstr "" #: library/difflib.rst:590 @@ -709,28 +710,29 @@ msgstr "" #: library/difflib.rst:598 msgid "" ":meth:`~SequenceMatcher.ratio` returns a float in [0, 1], measuring the " -"similarity of the sequences. As a rule of thumb, a :meth:`~SequenceMatcher." -"ratio` value over 0.6 means the sequences are close matches:" +"similarity of the sequences. As a rule of thumb, " +"a :meth:`~SequenceMatcher.ratio` value over 0.6 means the sequences are " +"close matches:" msgstr "" #: library/difflib.rst:605 msgid "" -"If you're only interested in where the sequences match, :meth:" -"`~SequenceMatcher.get_matching_blocks` is handy:" +"If you're only interested in where the sequences " +"match, :meth:`~SequenceMatcher.get_matching_blocks` is handy:" msgstr "" #: library/difflib.rst:614 msgid "" -"Note that the last tuple returned by :meth:`~SequenceMatcher." -"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``." +"Note that the last tuple returned " +"by :meth:`~SequenceMatcher.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 "" #: library/difflib.rst:618 msgid "" -"If you want to know how to change the first sequence into the second, use :" -"meth:`~SequenceMatcher.get_opcodes`:" +"If you want to know how to change the first sequence into the second, " +"use :meth:`~SequenceMatcher.get_opcodes`:" msgstr "" #: library/difflib.rst:629 @@ -742,8 +744,8 @@ msgstr "" #: library/difflib.rst:633 msgid "" "`Simple version control recipe `_ for a small application built with :class:" -"`SequenceMatcher`." +"simple-version-control/>`_ for a small application built " +"with :class:`SequenceMatcher`." msgstr "" #: library/difflib.rst:641 @@ -805,10 +807,10 @@ msgstr "" #: library/difflib.rst:679 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." +"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 "" #: library/difflib.rst:690 @@ -910,8 +912,8 @@ msgid "" " elif options.n:\n" " diff = difflib.ndiff(fromlines, tolines)\n" " elif options.m:\n" -" diff = difflib.HtmlDiff().make_file(fromlines,tolines,fromfile," -"tofile,context=options.c,numlines=n)\n" +" diff = " +"difflib.HtmlDiff().make_file(fromlines,tolines,fromfile,tofile,context=options.c,numlines=n)\n" " else:\n" " diff = difflib.context_diff(fromlines, tolines, fromfile, tofile, " "fromdate, todate, n=n)\n" @@ -958,8 +960,8 @@ msgid "" "confusing if the source files contain tab characters.\n" "\n" "The first file can be recovered by retaining only lines that begin with\n" -"\" \" or \"- \", and deleting those 2-character prefixes; use ndiff with -" -"r1.\n" +"\" \" or \"- \", and deleting those 2-character prefixes; use ndiff with " +"-r1.\n" "\n" "The second file can be recovered similarly, but by retaining only \" \" " "and\n" diff --git a/library/dis.po b/library/dis.po index df5e91b79..d03d505f0 100644 --- a/library/dis.po +++ b/library/dis.po @@ -56,17 +56,17 @@ msgstr "" msgid "" "Some instructions are accompanied by one or more inline cache entries, which " "take the form of :opcode:`CACHE` instructions. These instructions are hidden " -"by default, but can be shown by passing ``show_caches=True`` to any :mod:" -"`dis` utility. Furthermore, the interpreter now adapts the bytecode to " -"specialize it for different runtime conditions. The adaptive bytecode can be " -"shown by passing ``adaptive=True``." +"by default, but can be shown by passing ``show_caches=True`` to " +"any :mod:`dis` utility. Furthermore, the interpreter now adapts the bytecode " +"to specialize it for different runtime conditions. The adaptive bytecode can " +"be shown by passing ``adaptive=True``." msgstr "" #: library/dis.rst:45 msgid "" "The argument of a jump is the offset of the target instruction relative to " -"the instruction that appears immediately after the jump instruction's :" -"opcode:`CACHE` entries." +"the instruction that appears immediately after the jump " +"instruction's :opcode:`CACHE` entries." msgstr "" #: library/dis.rst:50 @@ -140,9 +140,9 @@ msgstr "" #: library/dis.rst:101 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." +"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 "" #: library/dis.rst:108 @@ -202,8 +202,8 @@ msgstr "" #: library/dis.rst:146 msgid "" -"Return a formatted view of the bytecode operations (the same as printed by :" -"func:`dis.dis`, but returned as a multi-line string)." +"Return a formatted view of the bytecode operations (the same as printed " +"by :func:`dis.dis`, but returned as a multi-line string)." msgstr "" #: library/dis.rst:151 @@ -390,10 +390,10 @@ msgstr "" #: library/dis.rst:319 msgid "" -"This generator function uses the :meth:`~codeobject.co_lines` method of the :" -"ref:`code object ` *code* to find the offsets which are starts " -"of lines in the source code. They are generated as ``(offset, lineno)`` " -"pairs." +"This generator function uses the :meth:`~codeobject.co_lines` method of " +"the :ref:`code object ` *code* to find the offsets which are " +"starts of lines in the source code. They are generated as ``(offset, " +"lineno)`` pairs." msgstr "" #: library/dis.rst:324 @@ -402,8 +402,8 @@ msgstr "" #: library/dis.rst:327 msgid "" -"The :pep:`626` :meth:`~codeobject.co_lines` method is used instead of the :" -"attr:`~codeobject.co_firstlineno` and :attr:`~codeobject.co_lnotab` " +"The :pep:`626` :meth:`~codeobject.co_lines` method is used instead of " +"the :attr:`~codeobject.co_firstlineno` and :attr:`~codeobject.co_lnotab` " "attributes of the :ref:`code object `." msgstr "" @@ -743,10 +743,10 @@ msgstr "" #: library/dis.rst:671 msgid "" -"Handles an exception raised during a :meth:`~generator.throw` or :meth:" -"`~generator.close` call through the current frame. If ``STACK[-1]`` is an " -"instance of :exc:`StopIteration`, pop three values from the stack and push " -"its ``value`` member. Otherwise, re-raise ``STACK[-1]``." +"Handles an exception raised during a :meth:`~generator.throw` " +"or :meth:`~generator.close` call through the current frame. If " +"``STACK[-1]`` is an instance of :exc:`StopIteration`, pop three values from " +"the stack and push its ``value`` member. Otherwise, re-raise ``STACK[-1]``." msgstr "" #: library/dis.rst:681 @@ -802,10 +802,10 @@ msgstr "" #: library/dis.rst:727 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." +"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 "" #: library/dis.rst:735 @@ -846,8 +846,8 @@ msgstr "" #: library/dis.rst:775 msgid "" "Re-raises the exception currently on top of the stack. If oparg is non-zero, " -"pops an additional value from the stack which is used to set :attr:`~frame." -"f_lasti` of the current frame." +"pops an additional value from the stack which is used to " +"set :attr:`~frame.f_lasti` of the current frame." msgstr "" #: library/dis.rst:786 @@ -908,9 +908,9 @@ msgstr "" 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_EXCEPT_START`. Then, :meth:" -"`~object.__enter__` is called. Finally, the result of calling the " -"``__enter__()`` method is pushed onto the stack." +"onto the stack for later use by :opcode:`WITH_EXCEPT_START`. " +"Then, :meth:`~object.__enter__` is called. Finally, the result of calling " +"the ``__enter__()`` method is pushed onto the stack." msgstr "" #: library/dis.rst:853 @@ -939,8 +939,9 @@ msgstr "" #: library/dis.rst:881 msgid "" "``STACK[-1]`` is a tuple of mapping keys, and ``STACK[-2]`` is the match " -"subject. If ``STACK[-2]`` contains all of the keys in ``STACK[-1]``, push a :" -"class:`tuple` containing the corresponding values. Otherwise, push ``None``." +"subject. If ``STACK[-2]`` contains all of the keys in ``STACK[-1]``, push " +"a :class:`tuple` containing the corresponding values. Otherwise, push " +"``None``." msgstr "" #: library/dis.rst:1521 @@ -953,14 +954,15 @@ msgstr "" msgid "" "Implements ``name = STACK.pop()``. *namei* is the index of *name* in the " "attribute :attr:`~codeobject.co_names` of the :ref:`code object `. The compiler tries to use :opcode:`STORE_FAST` or :opcode:" -"`STORE_GLOBAL` if possible." +"objects>`. The compiler tries to use :opcode:`STORE_FAST` " +"or :opcode:`STORE_GLOBAL` if possible." msgstr "" #: library/dis.rst:901 msgid "" -"Implements ``del name``, where *namei* is the index into :attr:`~codeobject." -"co_names` attribute of the :ref:`code object `." +"Implements ``del name``, where *namei* is the index " +"into :attr:`~codeobject.co_names` attribute of the :ref:`code object `." msgstr "" #: library/dis.rst:907 @@ -1011,8 +1013,8 @@ msgstr "" #: library/dis.rst:941 msgid "" -"where *namei* is the index of name in :attr:`~codeobject.co_names` of the :" -"ref:`code object `." +"where *namei* is the index of name in :attr:`~codeobject.co_names` of " +"the :ref:`code object `." msgstr "" #: library/dis.rst:948 @@ -1023,8 +1025,8 @@ msgstr "" #: library/dis.rst:951 msgid "" -"where *namei* is the index of name into :attr:`~codeobject.co_names` of the :" -"ref:`code object `." +"where *namei* is the index of name into :attr:`~codeobject.co_names` of " +"the :ref:`code object `." msgstr "" #: library/dis.rst:957 @@ -1048,8 +1050,8 @@ msgstr "" #: library/dis.rst:978 msgid "" "Pushes a reference to the locals dictionary onto the stack. This is used to " -"prepare namespace dictionaries for :opcode:`LOAD_FROM_DICT_OR_DEREF` and :" -"opcode:`LOAD_FROM_DICT_OR_GLOBALS`." +"prepare namespace dictionaries for :opcode:`LOAD_FROM_DICT_OR_DEREF` " +"and :opcode:`LOAD_FROM_DICT_OR_GLOBALS`." msgstr "" #: library/dis.rst:987 @@ -1191,9 +1193,9 @@ msgstr "" #: library/dis.rst:1123 msgid "" -"The low bit of ``namei`` signals to attempt a method load, as with :opcode:" -"`LOAD_ATTR`, which results in pushing ``NULL`` and the loaded method. When " -"it is unset a single value is pushed to the stack." +"The low bit of ``namei`` signals to attempt a method load, as " +"with :opcode:`LOAD_ATTR`, which results in pushing ``NULL`` and the loaded " +"method. When it is unset a single value is pushed to the stack." msgstr "" #: library/dis.rst:1127 @@ -1225,10 +1227,10 @@ msgstr "" #: library/dis.rst:1158 msgid "" "Imports the module ``co_names[namei]``. ``STACK[-1]`` and ``STACK[-2]`` 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." +"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 "" #: library/dis.rst:1166 @@ -1383,10 +1385,10 @@ msgstr "" msgid "" "Pops a mapping off the stack and looks up the name associated with slot " "``i`` of the \"fast locals\" storage in this mapping. If the name is not " -"found there, loads it from the cell contained in slot ``i``, similar to :" -"opcode:`LOAD_DEREF`. This is used for loading free variables in class bodies " -"(which previously used :opcode:`!LOAD_CLASSDEREF`) and in :ref:`annotation " -"scopes ` within class bodies." +"found there, loads it from the cell contained in slot ``i``, similar " +"to :opcode:`LOAD_DEREF`. This is used for loading free variables in class " +"bodies (which previously used :opcode:`!LOAD_CLASSDEREF`) and " +"in :ref:`annotation scopes ` within class bodies." msgstr "" #: library/dis.rst:1339 @@ -1906,8 +1908,9 @@ msgstr "" #: library/dis.rst:1693 msgid "" "This variant is used in :keyword:`with` and :keyword:`async with` " -"constructs, which push the return value of the context manager's :meth:" -"`~object.__enter__` or :meth:`~object.__aenter__` to the stack." +"constructs, which push the return value of the context " +"manager's :meth:`~object.__enter__` or :meth:`~object.__aenter__` to the " +"stack." msgstr "" #: library/dis.rst:1700 diff --git a/library/doctest.po b/library/doctest.po index 64510cdc9..ca41ab8dd 100644 --- a/library/doctest.po +++ b/library/doctest.po @@ -171,11 +171,11 @@ msgstr "" #: library/doctest.rst:133 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/test_doctest.py`." +"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/test_doctest.py`." msgstr "" #: library/doctest.rst:143 @@ -252,9 +252,9 @@ msgstr "" #: library/doctest.rst:182 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." +"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 "" #: library/doctest.rst:186 @@ -327,8 +327,8 @@ msgstr "" 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`." +"cause(s) of the failure(s) are printed to stdout, using the same format " +"as :func:`testmod`." msgstr "" #: library/doctest.rst:239 @@ -399,10 +399,10 @@ msgid "" "the docstring. Doctest looks for a module-level variable called ``__test__`` " "and uses it to locate other tests. If ``M.__test__`` exists, 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 ``M." -"__test__.K``." +"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 " +"``M.__test__.K``." msgstr "" #: library/doctest.rst:289 @@ -426,8 +426,8 @@ msgstr "" msgid "" "The value of ``example.__test__[\"numbers\"]`` will be treated as a " "docstring and all the tests inside it will be run. It is important to note " -"that the value can be mapped to a function, class object, or module; if so, :" -"mod:`!doctest` searches them recursively for docstrings, which are then " +"that the value can be mapped to a function, class object, or module; if " +"so, :mod:`!doctest` searches them recursively for docstrings, which are then " "scanned for tests." msgstr "" @@ -491,14 +491,14 @@ 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." +"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 "" #: library/doctest.rst:366 @@ -606,8 +606,8 @@ msgstr "" #: library/doctest.rst:435 msgid "" -"That doctest succeeds if :exc:`ValueError` is raised, with the ``list." -"remove(x): x not in list`` detail as shown." +"That doctest succeeds if :exc:`ValueError` is raised, with the " +"``list.remove(x): x not in list`` detail as shown." msgstr "" #: library/doctest.rst:438 @@ -674,10 +674,10 @@ msgstr "" #: library/doctest.rst:474 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." +"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 "" #: library/doctest.rst:480 @@ -712,8 +712,8 @@ msgstr "" #: library/doctest.rst:499 msgid "" -"The interactive shell omits the traceback header line for some :exc:" -"`SyntaxError`\\ s. But doctest uses the traceback header line to " +"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." @@ -758,11 +758,11 @@ msgstr "" #: library/doctest.rst:533 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 :" -"ref:`bitwise ORed ` 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." +"Symbolic names for the flags are supplied as module constants, which can " +"be :ref:`bitwise ORed ` 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 "" #: library/doctest.rst:539 @@ -779,12 +779,12 @@ msgstr "" 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." +"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 "" #: library/doctest.rst:560 @@ -792,8 +792,9 @@ 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." +"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 "" #: library/doctest.rst:569 @@ -825,11 +826,11 @@ msgstr "" #: library/doctest.rst:593 msgid "" "For example, an example expecting ``ValueError: 42`` will pass if the actual " -"exception raised is ``ValueError: 3*14``, but will fail if, say, a :exc:" -"`TypeError` is raised instead. It will also ignore any fully qualified name " -"included before the exception class, which can vary between implementations " -"and versions of Python and the code/libraries in use. Hence, all three of " -"these variations will work with the flag specified:" +"exception raised is ``ValueError: 3*14``, but will fail if, say, " +"a :exc:`TypeError` is raised instead. It will also ignore any fully " +"qualified name included before the exception class, which can vary between " +"implementations and versions of Python and the code/libraries in use. Hence, " +"all three of these variations will work with the flag specified:" msgstr "" #: library/doctest.rst:601 @@ -942,10 +943,10 @@ msgstr "" #: library/doctest.rst:698 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::" +"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 "" #: library/doctest.rst:704 @@ -1293,10 +1294,10 @@ msgstr "" #: library/doctest.rst:947 msgid "" -"Also test examples reachable from dict ``m.__test__``, if it exists. ``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." +"Also test examples reachable from dict ``m.__test__``, if it exists. " +"``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 "" #: library/doctest.rst:952 @@ -1318,11 +1319,11 @@ msgstr "" 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." +"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 "" #: library/doctest.rst:967 @@ -1403,16 +1404,16 @@ msgstr "" #: library/doctest.rst:1017 msgid "" -"Convert doctest tests from one or more text files to a :class:`unittest." -"TestSuite`." +"Convert doctest tests from one or more text files to " +"a :class:`unittest.TestSuite`." msgstr "" #: library/doctest.rst:1020 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 " +"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 "" @@ -1484,9 +1485,10 @@ msgstr "" #: library/doctest.rst:1066 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." +"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 "" #: library/doctest.rst:1078 @@ -1545,9 +1547,9 @@ msgstr "" #: library/doctest.rst:1117 msgid "" -"When doctests which have been converted to unit tests by :func:" -"`DocFileSuite` or :func:`DocTestSuite` fail, this exception is raised " -"showing the name of the file containing the test and a (sometimes " +"When doctests which have been converted to unit tests " +"by :func:`DocFileSuite` or :func:`DocTestSuite` fail, this exception is " +"raised showing the name of the file containing the test and a (sometimes " "approximate) line number." msgstr "" @@ -1569,15 +1571,15 @@ msgstr "" #: library/doctest.rst:1131 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." +"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 "" #: library/doctest.rst:1141 @@ -1600,14 +1602,14 @@ msgstr "" 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 :ref:`bitwise ORed ` 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." +"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 :ref:`bitwise ORed ` " +"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 "" #: library/doctest.rst:1163 @@ -1654,9 +1656,9 @@ msgstr "" #: library/doctest.rst:1189 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." +":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 "" #: library/doctest.rst:1193 @@ -1722,8 +1724,8 @@ msgstr "" 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." +"the examples (such as binding new variables) will be reflected " +"in :attr:`globs` after the test is run." msgstr "" #: library/doctest.rst:1247 @@ -1788,9 +1790,9 @@ msgstr "" 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." +"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 "" #: library/doctest.rst:1314 @@ -1847,8 +1849,9 @@ msgstr "" #: library/doctest.rst:1356 msgid "" -"If the optional argument *exclude_empty* is false, then :meth:`DocTestFinder." -"find` will include tests for objects with empty docstrings." +"If the optional argument *exclude_empty* is false, " +"then :meth:`DocTestFinder.find` will include tests for objects with empty " +"docstrings." msgstr "" #: library/doctest.rst:1360 @@ -1930,15 +1933,15 @@ msgstr "" #: library/doctest.rst:1417 msgid "" -"Extract all doctest examples from the given string, and collect them into a :" -"class:`DocTest` object." +"Extract all doctest examples from the given string, and collect them into " +"a :class:`DocTest` object." msgstr "" #: library/doctest.rst:1420 msgid "" -"*globs*, *name*, *filename*, and *lineno* are attributes for the new :class:" -"`DocTest` object. See the documentation for :class:`DocTest` for more " -"information." +"*globs*, *name*, *filename*, and *lineno* are attributes for the " +"new :class:`DocTest` object. See the documentation for :class:`DocTest` for " +"more information." msgstr "" #: library/doctest.rst:1427 @@ -1963,16 +1966,16 @@ msgstr "" #: library/doctest.rst:1448 msgid "" -"A processing class used to execute and verify the interactive examples in a :" -"class:`DocTest`." +"A processing class used to execute and verify the interactive examples in " +"a :class:`DocTest`." msgstr "" #: library/doctest.rst:1451 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 " +"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 "" @@ -1981,11 +1984,12 @@ msgstr "" msgid "" "The test runner's display output can be controlled in two ways. First, an " "output function can be passed to :meth:`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`." +"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 "" #: library/doctest.rst:1465 @@ -1997,11 +2001,12 @@ msgstr "" #: library/doctest.rst:1469 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." +"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 "" #: library/doctest.rst:1475 @@ -2025,8 +2030,8 @@ msgstr "" #: library/doctest.rst:1489 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`." +"*containing example*. *out* is the output function that was passed " +"to :meth:`DocTestRunner.run`." msgstr "" #: library/doctest.rst:1496 @@ -2060,9 +2065,9 @@ msgstr "" #: library/doctest.rst:1522 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`." +"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 "" #: library/doctest.rst:1530 @@ -2089,8 +2094,8 @@ msgstr "" #: library/doctest.rst:1542 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." +"output checker, and the results are formatted by the :meth:`!" +"DocTestRunner.report_\\*` methods." msgstr "" #: library/doctest.rst:1549 @@ -2114,10 +2119,10 @@ msgstr "" #: library/doctest.rst:1564 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." +"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 "" #: library/doctest.rst:1571 @@ -2129,8 +2134,8 @@ 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." +"using, several non-exact match types are also possible. See " +"section :ref:`doctest-options` for more information about option flags." msgstr "" #: library/doctest.rst:1584 @@ -2164,16 +2169,16 @@ msgstr "" #: library/doctest.rst:1604 msgid "" -"The :mod:`unittest` cases generated by :func:`DocTestSuite` support the :" -"meth:`debug` method defined by :class:`unittest.TestCase`." +"The :mod:`unittest` cases generated by :func:`DocTestSuite` support " +"the :meth:`debug` method defined by :class:`unittest.TestCase`." msgstr "" #: library/doctest.rst:1607 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::" +"inspect current values of variables, and so on. For example, " +"suppose :file:`a.py` contains just this module docstring::" msgstr "" #: library/doctest.rst:1612 @@ -2311,10 +2316,10 @@ msgstr "" #: library/doctest.rst:1715 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`." +"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 "" #: library/doctest.rst:1720 @@ -2328,8 +2333,8 @@ 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 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`." @@ -2369,11 +2374,11 @@ msgstr "" #: library/doctest.rst:1754 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." +"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 "" #: library/doctest.rst:1761 diff --git a/library/email.charset.po b/library/email.charset.po index 2db3b373e..1ad962a47 100644 --- a/library/email.charset.po +++ b/library/email.charset.po @@ -41,8 +41,8 @@ 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." +"Instances of :class:`Charset` are used in several other modules within " +"the :mod:`email` package." msgstr "" #: library/email.charset.rst:22 @@ -104,8 +104,8 @@ msgstr "" #: 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*." +"body, which indeed may be different than the header encoding. " +"``charset.SHORTEST`` is not allowed for *body_encoding*." msgstr "" #: library/email.charset.rst:76 @@ -288,6 +288,6 @@ msgstr "" #: library/email.charset.rst:211 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." +"of a Python codec, as appropriate for the second argument to " +"the :class:`str`'s :meth:`~str.encode` method." msgstr "" diff --git a/library/email.compat32-message.po b/library/email.compat32-message.po index 918070742..9de6b7ec3 100644 --- a/library/email.compat32-message.po +++ b/library/email.compat32-message.po @@ -18,18 +18,18 @@ msgstr "" #: library/email.compat32-message.rst:4 msgid "" -":mod:`email.message.Message`: Representing an email message using the :data:" -"`~email.policy.compat32` API" +":mod:`email.message.Message`: Representing an email message using " +"the :data:`~email.policy.compat32` API" msgstr "" #: library/email.compat32-message.rst:13 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." +"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 "" #: library/email.compat32-message.rst:20 @@ -38,22 +38,22 @@ msgstr "" #: library/email.compat32-message.rst:22 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." +"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 "" #: library/email.compat32-message.rst:26 msgid "" -"An email message consists of *headers* and a *payload*. Headers must be :" -"rfc:`5322` style names and values, where the field name and value are " +"An email message consists of *headers* and a *payload*. Headers must " +"be :rfc:`5322` 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`." +"message having a MIME type such as :mimetype:`multipart/\\*` " +"or :mimetype:`message/rfc822`." msgstr "" #: library/email.compat32-message.rst:35 @@ -76,8 +76,8 @@ msgid "" "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`)." +"list of :class:`Message` objects, for MIME container documents " +"(e.g. :mimetype:`multipart/\\*` and :mimetype:`message/rfc822`)." msgstr "" #: library/email.compat32-message.rst:53 @@ -88,10 +88,10 @@ msgstr "" 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." +"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 "" #: library/email.compat32-message.rst:65 @@ -123,9 +123,10 @@ 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::" +"format. For more flexibility, instantiate " +"a :class:`~email.generator.Generator` instance and use " +"its :meth:`~email.generator.Generator.flatten` method directly. For " +"example::" msgstr "" #: library/email.compat32-message.rst:91 @@ -142,8 +143,8 @@ msgstr "" 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`.)" +"character\" code points. (See also :meth:`.as_bytes` " +"and :class:`~email.generator.BytesGenerator`.)" msgstr "" #: library/email.compat32-message.rst:103 @@ -171,9 +172,10 @@ 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::" +"format. For more flexibility, instantiate " +"a :class:`~email.generator.BytesGenerator` instance and use " +"its :meth:`~email.generator.BytesGenerator.flatten` method directly. For " +"example::" msgstr "" #: library/email.compat32-message.rst:134 @@ -194,13 +196,14 @@ msgstr "" #: library/email.compat32-message.rst:154 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``.)" +"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 "" #: library/email.compat32-message.rst:166 @@ -226,8 +229,9 @@ msgstr "" #: library/email.compat32-message.rst:183 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 related ``make`` and ``add`` methods." +"class its functionality is replaced " +"by :meth:`~email.message.EmailMessage.set_content` and the related ``make`` " +"and ``add`` methods." msgstr "" #: library/email.compat32-message.rst:191 @@ -244,8 +248,8 @@ msgid "" "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." +"is a string (i.e. :meth:`is_multipart` is ``False``) and *i* is given, " +"a :exc:`TypeError` is raised." msgstr "" #: library/email.compat32-message.rst:203 @@ -269,17 +273,19 @@ 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." +"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 "" #: library/email.compat32-message.rst:226 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`." +"class its functionality is replaced " +"by :meth:`~email.message.EmailMessage.get_content` " +"and :meth:`~email.message.EmailMessage.iter_parts`." msgstr "" #: library/email.compat32-message.rst:234 @@ -292,43 +298,43 @@ msgstr "" #: library/email.compat32-message.rst:238 msgid "" "This is a legacy method. On the :class:`~email.emailmessage.EmailMessage` " -"class its functionality is replaced by :meth:`~email.message.EmailMessage." -"set_content`." +"class its functionality is replaced " +"by :meth:`~email.message.EmailMessage.set_content`." msgstr "" #: library/email.compat32-message.rst:245 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 " +"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`." +"``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 "" #: library/email.compat32-message.rst:253 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." +"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 "" #: library/email.compat32-message.rst:267 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." +"class its functionality is replaced by the *charset* parameter of " +"the :meth:`email.emailmessage.EmailMessage.set_content` method." msgstr "" #: library/email.compat32-message.rst:275 @@ -350,10 +356,11 @@ msgid "" "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." +"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 "" #: library/email.compat32-message.rst:293 @@ -396,8 +403,8 @@ msgstr "" #: library/email.compat32-message.rst:322 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." +"colon field separator. If the header is missing, ``None`` is returned; " +"a :exc:`KeyError` is never raised." msgstr "" #: library/email.compat32-message.rst:326 @@ -450,9 +457,9 @@ msgstr "" #: library/email.compat32-message.rst:370 msgid "" -"Return the value of the named header field. This is identical to :meth:" -"`~object.__getitem__` except that optional *failobj* is returned if the " -"named header is missing (defaults to ``None``)." +"Return the value of the named header field. This is identical " +"to :meth:`~object.__getitem__` except that optional *failobj* is returned if " +"the named header is missing (defaults to ``None``)." msgstr "" #: library/email.compat32-message.rst:374 @@ -483,11 +490,11 @@ msgid "" "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 " +"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 " +"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 "" @@ -536,11 +543,11 @@ msgstr "" #: library/email.compat32-message.rst:432 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." +"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 "" #: library/email.compat32-message.rst:439 @@ -567,8 +574,8 @@ msgstr "" #: library/email.compat32-message.rst:460 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 " +"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 "" @@ -585,15 +592,16 @@ msgid "" "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)." +"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 "" #: library/email.compat32-message.rst:484 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`." +"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 "" #: library/email.compat32-message.rst:488 @@ -614,8 +622,8 @@ msgstr "" #: library/email.compat32-message.rst:501 msgid "" -"Optional *header* if given, specifies the message header to use instead of :" -"mailheader:`Content-Type`." +"Optional *header* if given, specifies the message header to use instead " +"of :mailheader:`Content-Type`." msgstr "" #: library/email.compat32-message.rst:504 @@ -630,11 +638,12 @@ msgstr "" #: library/email.compat32-message.rst:512 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::" +"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 "" #: library/email.compat32-message.rst:519 @@ -690,8 +699,8 @@ 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`." +"(the default is ``True``). Optional *header* specifies an alternative " +"to :mailheader:`Content-Type`." msgstr "" #: library/email.compat32-message.rst:568 @@ -711,9 +720,9 @@ msgstr "" #: library/email.compat32-message.rst:577 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." +"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 "" #: library/email.compat32-message.rst:581 @@ -750,12 +759,12 @@ msgstr "" #: library/email.compat32-message.rst:612 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." +"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 "" #: library/email.compat32-message.rst:622 @@ -767,8 +776,8 @@ msgstr "" #: library/email.compat32-message.rst:626 msgid "" -"Note that this method differs from :meth:`get_charset` which returns the :" -"class:`~email.charset.Charset` instance for the default encoding of the " +"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 "" @@ -790,10 +799,10 @@ msgstr "" #: library/email.compat32-message.rst:646 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`." +"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 "" #: library/email.compat32-message.rst:655 @@ -882,11 +891,12 @@ 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." +"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 "" #: library/email.compat32-message.rst:741 @@ -904,8 +914,9 @@ msgstr "" #: library/email.compat32-message.rst:751 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." +"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 "" #: library/email.compat32-message.rst:758 diff --git a/library/email.contentmanager.po b/library/email.contentmanager.po index 79f1403dc..3d42f1a29 100644 --- a/library/email.contentmanager.po +++ b/library/email.contentmanager.po @@ -91,8 +91,8 @@ msgstr "" #: library/email.contentmanager.rst:59 msgid "" -"the type's fully qualified name (``typ.__module__ + '.' + typ." -"__qualname__``)." +"the type's fully qualified name (``typ.__module__ + '.' + " +"typ.__qualname__``)." msgstr "" #: library/email.contentmanager.rst:61 @@ -137,10 +137,11 @@ msgstr "" #: library/email.contentmanager.rst:91 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." +"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 "" #: library/email.contentmanager.rst:100 @@ -158,12 +159,12 @@ msgstr "" #: library/email.contentmanager.rst:112 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``." +"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 "" #: library/email.contentmanager.rst:131 @@ -183,8 +184,8 @@ msgstr "" #: library/email.contentmanager.rst:138 msgid "" -"For ``bytes``, use the specified *maintype* and *subtype*, or raise a :exc:" -"`TypeError` if they are not specified." +"For ``bytes``, use the specified *maintype* and *subtype*, or raise " +"a :exc:`TypeError` if they are not specified." msgstr "" #: library/email.contentmanager.rst:140 @@ -231,8 +232,8 @@ msgstr "" #: library/email.contentmanager.rst:168 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." +"``EmailMessage`` object as modified by ``set_content`` is correct, " +"but :class:`~email.generator.BytesGenerator` does not serialize it correctly." msgstr "" #: library/email.contentmanager.rst:173 @@ -259,8 +260,8 @@ msgstr "" #: library/email.contentmanager.rst:186 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." +"``(key, value)`` pairs to set additional parameters on " +"the :mailheader:`Content-Type` header." msgstr "" #: library/email.contentmanager.rst:190 diff --git a/library/email.encoders.po b/library/email.encoders.po index 01008c2df..061b62e1f 100644 --- a/library/email.encoders.po +++ b/library/email.encoders.po @@ -27,8 +27,8 @@ msgstr "" #: 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." +"the functionality is provided by the *cte* parameter of " +"the :meth:`~email.message.EmailMessage.set_content` method." msgstr "" #: library/email.encoders.rst:15 @@ -49,27 +49,27 @@ msgstr "" 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." +"servers. This is especially true for :mimetype:`image/\\*` " +"and :mimetype:`text/\\*` type messages containing binary data." msgstr "" #: library/email.encoders.rst:27 msgid "" -"The :mod:`email` package provides some convenient encoders in its :mod:" -"`~email.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." +"The :mod:`email` package provides some convenient encoders in " +"its :mod:`~email.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 "" #: library/email.encoders.rst:35 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." +"must be applied to individual subparts instead, and will raise " +"a :exc:`TypeError` if passed a message whose type is multipart." msgstr "" #: library/email.encoders.rst:39 @@ -78,10 +78,10 @@ msgstr "" #: library/email.encoders.rst:44 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." +"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 "" #: library/email.encoders.rst:52 @@ -95,9 +95,9 @@ msgstr "" #: library/email.encoders.rst:61 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." +"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 "" #: library/email.encoders.rst:68 diff --git a/library/email.errors.po b/library/email.errors.po index b7d88e421..d52169b5c 100644 --- a/library/email.errors.po +++ b/library/email.errors.po @@ -39,21 +39,23 @@ msgstr "" #: 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`." +"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 "" #: 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)." +"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 "" #: library/email.errors.rst:43 @@ -64,18 +66,18 @@ msgstr "" 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`." +"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 "" #: 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`)." +"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 "" #: library/email.errors.rst:64 @@ -118,8 +120,8 @@ msgstr "" #: library/email.errors.rst:89 msgid "" -":class:`StartBoundaryNotFoundDefect` -- The start boundary claimed in the :" -"mailheader:`Content-Type` header was never found." +":class:`StartBoundaryNotFoundDefect` -- The start boundary claimed in " +"the :mailheader:`Content-Type` header was never found." msgstr "" #: library/email.errors.rst:92 @@ -159,11 +161,11 @@ msgstr "" #: library/email.errors.rst:115 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`." +":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 "" #: library/email.errors.rst:120 diff --git a/library/email.examples.po b/library/email.examples.po index dfdbe9301..d9738804d 100644 --- a/library/email.examples.po +++ b/library/email.examples.po @@ -424,8 +424,8 @@ msgid "" " elif richest['content-type'].subtype == 'html':\n" " body = richest\n" " else:\n" -" print(\"Don't know how to display {}\".format(richest." -"get_content_type()))\n" +" print(\"Don't know how to display {}" +"\".format(richest.get_content_type()))\n" " sys.exit()\n" "elif richest['content-type'].content_type == 'multipart/related':\n" " body = richest.get_body(preferencelist=('html'))\n" @@ -441,8 +441,8 @@ msgid "" " # again strip the <> to go from email form of cid to html form.\n" " partfiles[part['content-id'][1:-1]] = f.name\n" "else:\n" -" print(\"Don't know how to display {}\".format(richest." -"get_content_type()))\n" +" print(\"Don't know how to display {}" +"\".format(richest.get_content_type()))\n" " sys.exit()\n" "with tempfile.NamedTemporaryFile(mode='w', delete=False) as f:\n" " f.write(magic_html_parser(body.get_content(), partfiles))\n" diff --git a/library/email.generator.po b/library/email.generator.po index 200597367..b01a0ab7a 100644 --- a/library/email.generator.po +++ b/library/email.generator.po @@ -28,10 +28,10 @@ msgstr "" 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." +"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 "" #: library/email.generator.rst:18 @@ -41,14 +41,14 @@ msgid "" "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.)" +"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 "" #: library/email.generator.rst:32 @@ -63,9 +63,9 @@ msgstr "" #: library/email.generator.rst:39 msgid "" -"To accommodate reproducible processing of SMIME-signed messages :class:" -"`Generator` disables header folding for message parts of type ``multipart/" -"signed`` and all subparts." +"To accommodate reproducible processing of SMIME-signed " +"messages :class:`Generator` disables header folding for message parts of " +"type ``multipart/signed`` and all subparts." msgstr "" #: library/email.generator.rst:47 @@ -82,11 +82,11 @@ msgid "" "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 `_)." +"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 "" #: library/email.generator.rst:163 @@ -100,10 +100,10 @@ msgstr "" #: library/email.generator.rst:168 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." +"*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 "" #: library/email.generator.rst:174 @@ -128,15 +128,15 @@ 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:`Content-Transfer-Encoding` (:" -"mailheader:`Content-Transfer-Encoding: 8bit`) to an ASCII compatible :" -"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." +"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:`Content-Transfer-" +"Encoding` (:mailheader:`Content-Transfer-Encoding: 8bit`) to an ASCII " +"compatible :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 "" #: library/email.generator.rst:104 library/email.generator.rst:197 @@ -164,28 +164,29 @@ msgstr "" #: library/email.generator.rst:125 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." +"handler, and pass it to the *write* method of the *outfp* passed to " +"the :class:`BytesGenerator`'s constructor." msgstr "" #: library/email.generator.rst:130 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`." +"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 "" #: library/email.generator.rst:137 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`." +"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 "" #: library/email.generator.rst:148 @@ -208,12 +209,13 @@ 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:`Content-Transfer-Encoding` (:mailheader:`Content-Transfer-" -"Encoding: 8bit`) to an ASCII compatible :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." +"bytes with the high bit set as needed using an ASCII-" +"compatible :mailheader:`Content-Transfer-Encoding`. That is, transform " +"parts with non-ASCII :mailheader:`Content-Transfer-Encoding` " +"(:mailheader:`Content-Transfer-Encoding: 8bit`) to an ASCII " +"compatible :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 "" #: library/email.generator.rst:209 @@ -230,35 +232,36 @@ msgstr "" #: library/email.generator.rst:222 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." +"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 "" #: library/email.generator.rst:228 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`." +"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 "" #: library/email.generator.rst:235 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." +"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 "" #: library/email.generator.rst:244 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 " +"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 "" @@ -307,8 +310,8 @@ msgstr "" #: library/email.generator.rst:270 msgid "" -"Optional *_mangle_from_* and *maxheaderlen* are as with the :class:" -"`Generator` base class." +"Optional *_mangle_from_* and *maxheaderlen* are as with " +"the :class:`Generator` base class." msgstr "" #: library/email.generator.rst:275 @@ -319,10 +322,10 @@ msgstr "" msgid "" "This statement assumes that you use the appropriate setting for " "``unixfrom``, and that there are no :mod:`email.policy` settings calling for " -"automatic adjustments (for example, :attr:`~email.policy.EmailPolicy." -"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." +"automatic adjustments (for " +"example, :attr:`~email.policy.EmailPolicy.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 "" diff --git a/library/email.header.po b/library/email.header.po index 21dc41801..a484333f7 100644 --- a/library/email.header.po +++ b/library/email.header.po @@ -56,19 +56,20 @@ msgid "" "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." +"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 "" #: 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::" +"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 "" #: library/email.header.rst:40 @@ -87,9 +88,10 @@ 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." +"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 "" #: library/email.header.rst:57 @@ -105,9 +107,9 @@ msgstr "" #: 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." +"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 "" #: library/email.header.rst:70 @@ -172,9 +174,9 @@ msgstr "" #: 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 " +"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 "" @@ -285,8 +287,8 @@ msgstr "" #: library/email.header.rst:195 msgid "" -"Create a :class:`Header` instance from a sequence of pairs as returned by :" -"func:`decode_header`." +"Create a :class:`Header` instance from a sequence of pairs as returned " +"by :func:`decode_header`." msgstr "" #: library/email.header.rst:198 @@ -298,7 +300,7 @@ msgstr "" #: 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 " +"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 "" diff --git a/library/email.headerregistry.po b/library/email.headerregistry.po index fde8fe325..298c2ad55 100644 --- a/library/email.headerregistry.po +++ b/library/email.headerregistry.po @@ -31,42 +31,44 @@ msgstr "" #: 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." +"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 "" #: 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." +"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 "" #: 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." +"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 "" #: 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." +"*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 "" #: library/email.headerregistry.rst:48 @@ -76,8 +78,9 @@ msgstr "" #: 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." +"exactly the value passed in " +"the :attr:`~email.policy.EmailPolicy.header_factory` call for *name*; that " +"is, case is preserved." msgstr "" #: library/email.headerregistry.rst:61 @@ -106,11 +109,11 @@ msgstr "" #: 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." +"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 "" #: library/email.headerregistry.rst:88 @@ -204,10 +207,11 @@ msgid "" "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." +"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 "" #: library/email.headerregistry.rst:160 @@ -235,8 +239,8 @@ msgstr "" 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::" +"more useful is to use the :func:`~email.utils.localtime` function from " +"the :mod:`~email.utils` module::" msgstr "" #: library/email.headerregistry.rst:176 @@ -346,8 +350,8 @@ msgstr "" #: library/email.headerregistry.rst:275 msgid "" -"A :class:`ParameterizedMIMEHeader` class that handles the :mailheader:" -"`Content-Type` header." +"A :class:`ParameterizedMIMEHeader` class that handles " +"the :mailheader:`Content-Type` header." msgstr "" #: library/email.headerregistry.rst:280 @@ -356,8 +360,8 @@ msgstr "" #: library/email.headerregistry.rst:289 msgid "" -"A :class:`ParameterizedMIMEHeader` class that handles the :mailheader:" -"`Content-Disposition` header." +"A :class:`ParameterizedMIMEHeader` class that handles " +"the :mailheader:`Content-Disposition` header." msgstr "" #: library/email.headerregistry.rst:294 @@ -574,8 +578,8 @@ msgstr "" #: library/email.headerregistry.rst:386 msgid "" -"where each part must conform to specific syntax rules spelled out in :rfc:" -"`5322`." +"where each part must conform to specific syntax rules spelled out " +"in :rfc:`5322`." msgstr "" #: library/email.headerregistry.rst:389 @@ -611,8 +615,8 @@ msgstr "" #: library/email.headerregistry.rst:418 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 " +"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 "" diff --git a/library/email.iterators.po b/library/email.iterators.po index c2cd0493d..9c6367179 100644 --- a/library/email.iterators.po +++ b/library/email.iterators.po @@ -26,10 +26,10 @@ msgstr "" #: 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." +"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 "" #: library/email.iterators.rst:19 @@ -44,8 +44,8 @@ msgstr "" #: library/email.iterators.rst:26 msgid "" -"Optional *decode* is passed through to :meth:`Message.get_payload `." +"Optional *decode* is passed through to :meth:`Message.get_payload " +"`." msgstr "" #: library/email.iterators.rst:32 diff --git a/library/email.message.po b/library/email.message.po index b1e0fc122..685cfd6d9 100644 --- a/library/email.message.po +++ b/library/email.message.po @@ -83,25 +83,25 @@ msgstr "" #: library/email.message.rst:55 msgid "" "If *policy* is specified use the rules it specifies to update 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." +"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 "" #: 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 compatibility 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.Policy.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`." +"defaults to ``False``. For backward compatibility 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.Policy.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 "" #: library/email.message.rst:114 @@ -117,8 +117,9 @@ msgid "" "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." +"restricted to producing messages serialized as \"7 bit clean\" " +"when :attr:`~email.policy.EmailPolicy.utf8` is ``False``, which is the " +"default." msgstr "" #: library/email.message.rst:88 @@ -138,8 +139,8 @@ msgstr "" #: 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`." +"like message representation, instead of being a direct alias " +"for :meth:`as_string`." msgstr "" #: library/email.message.rst:106 @@ -149,8 +150,8 @@ msgid "" "*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`." +"specified *policy* will be passed to " +"the :class:`~email.generator.BytesGenerator`." msgstr "" #: library/email.message.rst:118 @@ -169,14 +170,14 @@ msgstr "" #: 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``." +"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 "" #: library/email.message.rst:145 @@ -237,8 +238,8 @@ msgstr "" #: 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." +"colon field separator. If the header is missing, ``None`` is returned; " +"a :exc:`KeyError` is never raised." msgstr "" #: library/email.message.rst:195 @@ -307,9 +308,9 @@ msgstr "" #: library/email.message.rst:249 msgid "" -"Return the value of the named header field. This is identical to :meth:" -"`~object.__getitem__` except that optional *failobj* is returned if the " -"named header is missing (*failobj* defaults to ``None``)." +"Return the value of the named header field. This is identical " +"to :meth:`~object.__getitem__` except that optional *failobj* is returned if " +"the named header is missing (*failobj* defaults to ``None``)." msgstr "" #: library/email.message.rst:254 @@ -388,22 +389,22 @@ msgstr "" #: 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``." +"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 "" #: 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`.)" +"(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 "" #: library/email.message.rst:328 @@ -421,8 +422,8 @@ msgstr "" #: 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 " +"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 "" @@ -441,8 +442,8 @@ msgid "" "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`." +"parameter value. Optional *header* specifies an alternative header " +"to :mailheader:`Content-Type`." msgstr "" #: library/email.message.rst:366 @@ -470,9 +471,9 @@ msgstr "" #: library/email.message.rst:380 msgid "" -"Note that existing parameter values of headers may be accessed through the :" -"attr:`~email.headerregistry.ParameterizedMIMEHeader.params` attribute of the " -"header value (for example, ``msg['Content-Type'].params['charset']``)." +"Note that existing parameter values of headers may be accessed through " +"the :attr:`~email.headerregistry.ParameterizedMIMEHeader.params` attribute " +"of the header value (for example, ``msg['Content-Type'].params['charset']``)." msgstr "" #: library/email.message.rst:384 @@ -515,10 +516,10 @@ msgstr "" #: 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." +"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 "" #: library/email.message.rst:433 @@ -552,16 +553,16 @@ msgstr "" #: 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`." +"is_attachment is now a method instead of a property, for consistency " +"with :meth:`~email.message.Message.is_multipart`." msgstr "" #: 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`." +"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 "" #: library/email.message.rst:471 @@ -699,8 +700,8 @@ 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 " +"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`` " @@ -712,8 +713,8 @@ msgstr "" #: 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`.)" +"will be empty for a non-``multipart``. (See " +"also :meth:`~email.message.EmailMessage.walk`.)" msgstr "" #: library/email.message.rst:600 @@ -757,50 +758,52 @@ msgstr "" #: 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)." +"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 "" #: 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``." +"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 "" #: 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`." +"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 "" #: 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``." +"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 "" #: library/email.message.rst:689 @@ -832,11 +835,12 @@ 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." +"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 "" #: library/email.message.rst:720 @@ -862,10 +866,10 @@ msgstr "" #: 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." +"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 "" #: library/email.message.rst:748 diff --git a/library/email.mime.po b/library/email.mime.po index 5cd9047d6..72c9a3bef 100644 --- a/library/email.mime.po +++ b/library/email.mime.po @@ -38,17 +38,18 @@ msgid "" "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." +"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 "" #: 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." +"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 "" #: library/email.mime.rst:29 @@ -61,8 +62,8 @@ msgstr "" #: 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 " +"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." @@ -70,17 +71,19 @@ msgstr "" #: 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 `." +"*_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 "" #: 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`." +"If *policy* is specified, (defaults to the :class:`compat32 " +"` policy) it will be passed " +"to :class:`~email.message.Message`." msgstr "" #: library/email.mime.rst:53 @@ -103,9 +106,10 @@ msgstr "" 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, " +"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 "" @@ -118,9 +122,9 @@ 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." +"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 "" #: library/email.mime.rst:89 @@ -134,15 +138,15 @@ msgstr "" 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." +"subparts to the message by using the :meth:`Message.attach " +"` method." msgstr "" #: library/email.mime.rst:131 library/email.mime.rst:200 #: library/email.mime.rst:254 msgid "" -"Optional *policy* argument defaults to :class:`compat32 `." +"Optional *policy* argument defaults to :class:`compat32 " +"`." msgstr "" #: library/email.mime.rst:100 @@ -158,10 +162,10 @@ msgstr "" #: 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* contains the bytes for the raw " -"application data. Optional *_subtype* specifies the MIME subtype and " +"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* contains the bytes for the " +"raw application data. Optional *_subtype* specifies the MIME subtype and " "defaults to :mimetype:`octet-stream`." msgstr "" @@ -169,12 +173,13 @@ msgstr "" 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." +"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 "" #: library/email.mime.rst:167 @@ -187,26 +192,27 @@ msgstr "" #: 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* contains the bytes for the raw audio data. " -"If this data can be decoded as au, wav, aiff, or aifc, 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." +"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* contains the bytes for the raw audio " +"data. If this data can be decoded as au, wav, aiff, or aifc, 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 "" #: 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." +"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 "" #: library/email.mime.rst:178 @@ -215,33 +221,34 @@ msgstr "" #: 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* contains the bytes for the raw image data. " -"If this data type can be detected (jpeg, png, gif, tiff, rgb, pbm, pgm, ppm, " -"rast, xbm, bmp, webp, and exr attempted), then the subtype will be " +"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* contains the bytes for the raw image " +"data. If this data type can be detected (jpeg, png, gif, tiff, rgb, pbm, " +"pgm, ppm, rast, xbm, bmp, webp, and exr attempted), 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." +"the minor type could not be guessed and *_subtype* was not given, " +"then :exc:`TypeError` is raised." msgstr "" #: library/email.mime.rst:190 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." +"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 "" #: library/email.mime.rst:202 msgid "" -"*_params* are passed straight through to the :class:`~email.mime.base." -"MIMEBase` constructor." +"*_params* are passed straight through to " +"the :class:`~email.mime.base.MIMEBase` constructor." msgstr "" #: library/email.mime.rst:212 @@ -250,17 +257,17 @@ msgstr "" #: library/email.mime.rst:214 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." +"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 "" #: library/email.mime.rst:220 msgid "" -"Optional *_subtype* sets the subtype of the message; it defaults to :" -"mimetype:`rfc822`." +"Optional *_subtype* sets the subtype of the message; it defaults " +"to :mimetype:`rfc822`." msgstr "" #: library/email.mime.rst:232 @@ -269,15 +276,15 @@ msgstr "" #: library/email.mime.rst:234 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." +"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 "" #: library/email.mime.rst:244 diff --git a/library/email.parser.po b/library/email.parser.po index 213fc5565..6056db9c8 100644 --- a/library/email.parser.po +++ b/library/email.parser.po @@ -42,35 +42,35 @@ msgid "" "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`." +"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 "" #: 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." +"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 "" #: 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 :class:`~email.policy.Policy` " -"class, so a custom parser can create message object trees any way it finds " -"necessary by implementing custom versions of the appropriate :class:`!" -"Policy` methods." +"connects the :mod:`email` package's bundled parser and " +"the :class:`~email.message.EmailMessage` class is embodied in " +"the :class:`~email.policy.Policy` class, so a custom parser can create " +"message object trees any way it finds necessary by implementing custom " +"versions of the appropriate :class:`!Policy` methods." msgstr "" #: library/email.parser.rst:49 @@ -82,11 +82,11 @@ 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." +"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 "" #: library/email.parser.rst:60 @@ -96,10 +96,10 @@ msgid "" "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." +"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 "" #: library/email.parser.rst:70 @@ -109,21 +109,21 @@ msgstr "" #: 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." +"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 "" #: 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." +"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 "" #: library/email.parser.rst:145 @@ -158,10 +158,10 @@ msgstr "" #: 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 " +"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 "" @@ -174,13 +174,13 @@ 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." +"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 "" #: library/email.parser.rst:141 @@ -203,8 +203,8 @@ msgstr "" #: 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." +"bytes, and return the message object. *fp* must support both " +"the :meth:`~io.IOBase.readline` and the :meth:`~io.IOBase.read` methods." msgstr "" #: library/email.parser.rst:161 @@ -214,8 +214,8 @@ msgid "" "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``)." +"contain MIME-encoded subparts, including subparts with " +"a :mailheader:`Content-Transfer-Encoding` of ``8bit``)." msgstr "" #: library/email.parser.rst:169 @@ -228,9 +228,9 @@ msgstr "" #: 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`." +"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 "" #: library/email.parser.rst:221 @@ -263,16 +263,16 @@ msgstr "" #: library/email.parser.rst:210 msgid "" -"Other than the text mode requirement, this method operates like :meth:" -"`BytesParser.parse`." +"Other than the text mode requirement, this method operates " +"like :meth:`BytesParser.parse`." msgstr "" #: 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`." +"wrapping *text* in a :class:`~io.StringIO` instance first and " +"calling :meth:`parse`." msgstr "" #: library/email.parser.rst:226 @@ -341,37 +341,39 @@ msgstr "" 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." +"for :meth:`~email.message.EmailMessage.is_multipart`, " +"and :meth:`~email.message.EmailMessage.iter_parts` will yield an empty list." msgstr "" #: 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." +"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 "" #: 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." +"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 "" #: 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." +"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 "" diff --git a/library/email.po b/library/email.po index fa620b9ee..15b04f2a8 100644 --- a/library/email.po +++ b/library/email.po @@ -27,12 +27,12 @@ msgstr "" #: 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:`5322` and :rfc:`6532`, as " -"well as such MIME-related RFCs as :rfc:`2045`, :rfc:`2046`, :rfc:`2047`, :" -"rfc:`2183`, and :rfc:`2231`." +"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:`5322` and :rfc:`6532`, as " +"well as such MIME-related RFCs " +"as :rfc:`2045`, :rfc:`2046`, :rfc:`2047`, :rfc:`2183`, and :rfc:`2231`." msgstr "" #: library/email.rst:23 @@ -51,35 +51,35 @@ msgid "" "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." +"model is a tree structure of objects that all provide " +"the :class:`~email.message.EmailMessage` API." msgstr "" #: 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.)" +"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 "" #: 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." +"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 "" #: library/email.rst:58 @@ -103,22 +103,22 @@ msgstr "" 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." +"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 "" #: 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." +"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 "" #: library/email.rst:87 @@ -130,20 +130,22 @@ msgstr "" #: library/email.rst:90 msgid "" "The foregoing 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." +"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 "" #: library/email.rst:100 msgid "" -"Docs reorganized and rewritten to promote the new :class:`~email.message." -"EmailMessage`/:class:`~email.policy.EmailPolicy` API." +"Docs reorganized and rewritten to promote the " +"new :class:`~email.message.EmailMessage`/:class:`~email.policy.EmailPolicy` " +"API." msgstr "" #: library/email.rst:105 diff --git a/library/email.policy.po b/library/email.policy.po index fef8afc59..263bc7943 100644 --- a/library/email.policy.po +++ b/library/email.policy.po @@ -48,40 +48,41 @@ msgstr "" #: 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." +"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 "" #: 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." +"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 "" #: 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`." +"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 "" #: 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." +"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 "" #: library/email.policy.rst:57 @@ -108,8 +109,8 @@ msgstr "" #: 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 " +"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 "" @@ -269,9 +270,9 @@ msgstr "" #: library/email.policy.rst:209 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." +"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 "" #: library/email.policy.rst:216 @@ -284,24 +285,24 @@ msgstr "" #: 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." +"parser when building messages. Defaults to ``None``, in which " +"case :class:`~email.message.Message` is used." msgstr "" #: library/email.policy.rst:235 msgid "" -"If ``True`` (the default), the generator will raise :exc:`~email.errors." -"HeaderWriteError` instead of writing a header that is improperly folded or " -"delimited, such that it would be parsed as multiple headers or joined with " -"adjacent data. Such headers can be generated by custom header classes or " -"bugs in the ``email`` module." +"If ``True`` (the default), the generator will " +"raise :exc:`~email.errors.HeaderWriteError` instead of writing a header that " +"is improperly folded or delimited, such that it would be parsed as multiple " +"headers or joined with adjacent data. Such headers can be generated by " +"custom header classes or bugs in the ``email`` module." msgstr "" #: library/email.policy.rst:242 msgid "" -"As it's a security feature, this defaults to ``True`` even in the :class:" -"`~email.policy.Compat32` policy. For backwards compatible, but unsafe, " -"behavior, it must be set to ``False`` explicitly." +"As it's a security feature, this defaults to ``True`` even in " +"the :class:`~email.policy.Compat32` policy. For backwards compatible, but " +"unsafe, behavior, it must be set to ``False`` explicitly." msgstr "" #: library/email.policy.rst:250 @@ -359,10 +360,11 @@ msgstr "" #: library/email.policy.rst:294 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* " -"greater than or equal to the value returned, a :exc:`ValueError` is raised." +"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* greater than or equal to the value returned, a :exc:`ValueError` is " +"raised." msgstr "" #: library/email.policy.rst:300 @@ -444,9 +446,9 @@ 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." +"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 "" #: library/email.policy.rst:372 @@ -508,9 +510,9 @@ msgstr "" #: library/email.policy.rst:417 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 " +"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 "" @@ -557,13 +559,14 @@ msgstr "" #: library/email.policy.rst:448 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`." +"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 "" #: library/email.policy.rst:618 @@ -667,8 +670,8 @@ 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 transmission if the " -"sender or recipient addresses have non-ASCII characters (the :meth:`smtplib." -"SMTP.send_message` method handles this automatically)." +"sender or recipient addresses have non-ASCII characters " +"(the :meth:`smtplib.SMTP.send_message` method handles this automatically)." msgstr "" #: library/email.policy.rst:561 @@ -716,8 +719,8 @@ msgstr "" #: library/email.policy.rst:589 msgid "" -"From the application view, this means that any header obtained through the :" -"class:`~email.message.EmailMessage` is a header object with extra " +"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 " @@ -726,23 +729,24 @@ msgstr "" #: library/email.policy.rst:596 msgid "" -"The header objects and their attributes are described in :mod:`~email." -"headerregistry`." +"The header objects and their attributes are described " +"in :mod:`~email.headerregistry`." msgstr "" #: library/email.policy.rst:603 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." +"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 "" #: library/email.policy.rst:609 msgid "" -"The following attributes have values that are different from the :class:" -"`Policy` default:" +"The following attributes have values that are different from " +"the :class:`Policy` default:" msgstr "" #: library/email.policy.rst:615 @@ -755,9 +759,9 @@ msgstr "" #: library/email.policy.rst:637 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." +"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 "" #: library/email.policy.rst:644 diff --git a/library/email.utils.po b/library/email.utils.po index e61f659d7..2474c95a1 100644 --- a/library/email.utils.po +++ b/library/email.utils.po @@ -33,11 +33,11 @@ msgstr "" #: library/email.utils.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. The *isdst* parameter is " -"ignored." +"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. " +"The *isdst* parameter is ignored." msgstr "" #: library/email.utils.rst:25 @@ -46,13 +46,13 @@ msgstr "" #: library/email.utils.rst:30 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." +"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 "" #: library/email.utils.rst:38 @@ -100,17 +100,17 @@ msgstr "" #: library/email.utils.rst:76 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." +"``(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 "" #: library/email.utils.rst:81 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``." +"characters. Can be an instance of :class:`str` or " +"a :class:`~email.charset.Charset`. Defaults to ``utf-8``." msgstr "" #: library/email.utils.rst:86 @@ -143,10 +143,10 @@ msgstr "" 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 " +"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 "" @@ -163,15 +163,15 @@ msgstr "" #: library/email.utils.rst:135 msgid "" -"The inverse of :func:`format_datetime`. Performs the same function as :func:" -"`parsedate`, but on success returns a :mod:`~datetime.datetime`; otherwise " -"``ValueError`` is raised if *date* contains an invalid value such as an hour " -"greater than 23 or a timezone offset not between -24 and 24 hours. 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 " +"The inverse of :func:`format_datetime`. Performs the same function " +"as :func:`parsedate`, but on success returns a :mod:`~datetime.datetime`; " +"otherwise ``ValueError`` is raised if *date* contains an invalid value such " +"as an hour greater than 23 or a timezone offset not between -24 and 24 " +"hours. 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 "" @@ -192,9 +192,9 @@ msgstr "" #: library/email.utils.rst:162 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." +"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 "" #: library/email.utils.rst:166 @@ -240,14 +240,14 @@ msgstr "" #: library/email.utils.rst:206 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'``." +"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 "" #: library/email.utils.rst:215 diff --git a/library/ensurepip.po b/library/ensurepip.po index 489dee190..b56bca543 100644 --- a/library/ensurepip.po +++ b/library/ensurepip.po @@ -222,8 +222,8 @@ msgstr "" #: library/ensurepip.rst:129 msgid "" -"The bootstrapping process has side effects on both ``sys.path`` and ``os." -"environ``. Invoking the command line interface in a subprocess instead " +"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 "" diff --git a/library/enum.po b/library/enum.po index be20d405a..e1264cefe 100644 --- a/library/enum.po +++ b/library/enum.po @@ -137,8 +137,8 @@ msgstr "" #: library/enum.rst:77 msgid "" -"Base class for creating enumerated constants that are also subclasses of :" -"class:`int`. (`Notes`_)" +"Base class for creating enumerated constants that are also subclasses " +"of :class:`int`. (`Notes`_)" msgstr "" #: library/enum.rst:80 @@ -147,8 +147,8 @@ msgstr "" #: library/enum.rst:82 msgid "" -"Base class for creating enumerated constants that are also subclasses of :" -"class:`str`. (`Notes`_)" +"Base class for creating enumerated constants that are also subclasses " +"of :class:`str`. (`Notes`_)" msgstr "" #: library/enum.rst:85 @@ -168,8 +168,9 @@ msgstr "" #: library/enum.rst:92 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`. (`Notes`_)" +"bitwise operators without losing their :class:`IntFlag` " +"membership. :class:`IntFlag` members are also subclasses of :class:`int`. " +"(`Notes`_)" msgstr "" #: library/enum.rst:96 @@ -210,9 +211,9 @@ msgstr "" #: library/enum.rst:115 msgid "" -"Instances are replaced with an appropriate value for Enum members. :class:" -"`StrEnum` defaults to the lower-cased version of the member name, while " -"other Enums default to 1 and increase from there." +"Instances are replaced with an appropriate value for Enum " +"members. :class:`StrEnum` defaults to the lower-cased version of the member " +"name, while other Enums default to 1 and increase from there." msgstr "" #: library/enum.rst:119 @@ -427,8 +428,8 @@ msgstr "" #: library/enum.rst:219 msgid "" -"Returns the Enum member in *cls* matching *name*, or raises a :exc:" -"`KeyError`::" +"Returns the Enum member in *cls* matching *name*, or raises " +"a :exc:`KeyError`::" msgstr "" #: library/enum.rst:221 @@ -541,8 +542,8 @@ msgstr "" #: library/enum.rst:304 msgid "" "``_ignore_`` is a list of names that will not become members, and whose " -"names will also be removed from the completed enumeration. See :ref:" -"`TimePeriod ` for an example." +"names will also be removed from the completed enumeration. " +"See :ref:`TimePeriod ` for an example." msgstr "" #: library/enum.rst:310 @@ -601,8 +602,8 @@ msgstr "" #: library/enum.rst:336 msgid "" -"A *staticmethod* that is used to determine the next value returned by :class:" -"`auto`::" +"A *staticmethod* that is used to determine the next value returned " +"by :class:`auto`::" msgstr "" #: library/enum.rst:339 @@ -697,8 +698,8 @@ msgid "" "... cls_name = self.__class__.__name__\n" "... return f'{cls_name}.{self.name}'\n" "...\n" -">>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), f\"{OtherStyle." -"ALTERNATE}\"\n" +">>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), " +"f\"{OtherStyle.ALTERNATE}\"\n" "(OtherStyle.ALTERNATE, 'OtherStyle.ALTERNATE', 'OtherStyle.ALTERNATE')" msgstr "" @@ -717,8 +718,8 @@ msgid "" "... def __str__(self):\n" "... return f'{self.name}'\n" "...\n" -">>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), f\"{OtherStyle." -"ALTERNATE}\"\n" +">>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), " +"f\"{OtherStyle.ALTERNATE}\"\n" "(, 'ALTERNATE', 'ALTERNATE')" msgstr "" @@ -737,8 +738,8 @@ msgid "" "... def __format__(self, spec):\n" "... return f'{self.name}'\n" "...\n" -">>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), f\"{OtherStyle." -"ALTERNATE}\"\n" +">>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), " +"f\"{OtherStyle.ALTERNATE}\"\n" "(, 'OtherStyle.ALTERNATE', 'ALTERNATE')" msgstr "" @@ -1008,9 +1009,9 @@ msgstr "" #: library/enum.rst:684 msgid "" -"Inherit from :class:`!ReprEnum` to keep the :class:`str() ` / :func:" -"`format` of the mixed-in data type instead of using the :class:`Enum`-" -"default :meth:`str() `." +"Inherit from :class:`!ReprEnum` to keep the :class:`str() " +"` / :func:`format` of the mixed-in data type instead of using " +"the :class:`Enum`-default :meth:`str() `." msgstr "" #: library/enum.rst:693 @@ -1189,9 +1190,9 @@ msgstr "" #: library/enum.rst:836 msgid "" -":attr:`~Enum._ignore_` -- a list of names, either as a :class:`list` or a :" -"class:`str`, that will not be transformed into members, and will be removed " -"from the final class" +":attr:`~Enum._ignore_` -- a list of names, either as a :class:`list` or " +"a :class:`str`, that will not be transformed into members, and will be " +"removed from the final class" msgstr "" #: library/enum.rst:839 @@ -1320,9 +1321,9 @@ msgstr "" #: library/enum.rst:923 msgid "" -"A :keyword:`class` decorator specifically for enumerations. Members from :" -"class:`EnumCheck` are used to specify which constraints should be checked on " -"the decorated enumeration." +"A :keyword:`class` decorator specifically for enumerations. Members " +"from :class:`EnumCheck` are used to specify which constraints should be " +"checked on the decorated enumeration." msgstr "" #: library/enum.rst:931 diff --git a/library/errno.po b/library/errno.po index 9d157e2cb..aa08f940c 100644 --- a/library/errno.po +++ b/library/errno.po @@ -37,8 +37,8 @@ msgstr "" #: library/errno.rst:21 msgid "" -"To translate a numeric error code to an error message, use :func:`os." -"strerror`." +"To translate a numeric error code to an error message, " +"use :func:`os.strerror`." msgstr "" #: library/errno.rst:23 @@ -50,26 +50,26 @@ msgstr "" #: library/errno.rst:30 msgid "" -"Operation not permitted. This error is mapped to the exception :exc:" -"`PermissionError`." +"Operation not permitted. This error is mapped to the " +"exception :exc:`PermissionError`." msgstr "" #: library/errno.rst:36 msgid "" -"No such file or directory. This error is mapped to the exception :exc:" -"`FileNotFoundError`." +"No such file or directory. This error is mapped to the " +"exception :exc:`FileNotFoundError`." msgstr "" #: library/errno.rst:42 msgid "" -"No such process. This error is mapped to the exception :exc:" -"`ProcessLookupError`." +"No such process. This error is mapped to the " +"exception :exc:`ProcessLookupError`." msgstr "" #: library/errno.rst:48 msgid "" -"Interrupted system call. This error is mapped to the exception :exc:" -"`InterruptedError`." +"Interrupted system call. This error is mapped to the " +"exception :exc:`InterruptedError`." msgstr "" #: library/errno.rst:54 @@ -94,8 +94,8 @@ msgstr "" #: library/errno.rst:79 msgid "" -"No child processes. This error is mapped to the exception :exc:" -"`ChildProcessError`." +"No child processes. This error is mapped to the " +"exception :exc:`ChildProcessError`." msgstr "" #: library/errno.rst:85 @@ -109,8 +109,8 @@ msgstr "" #: library/errno.rst:95 msgid "" -"Permission denied. This error is mapped to the exception :exc:" -"`PermissionError`." +"Permission denied. This error is mapped to the " +"exception :exc:`PermissionError`." msgstr "" #: library/errno.rst:101 @@ -140,14 +140,14 @@ msgstr "" #: library/errno.rst:132 msgid "" -"Not a directory. This error is mapped to the exception :exc:" -"`NotADirectoryError`." +"Not a directory. This error is mapped to the " +"exception :exc:`NotADirectoryError`." msgstr "" #: library/errno.rst:138 msgid "" -"Is a directory. This error is mapped to the exception :exc:" -"`IsADirectoryError`." +"Is a directory. This error is mapped to the " +"exception :exc:`IsADirectoryError`." msgstr "" #: library/errno.rst:144 @@ -229,8 +229,8 @@ msgstr "" #: library/errno.rst:240 msgid "" -"Operation would block. This error is mapped to the exception :exc:" -"`BlockingIOError`." +"Operation would block. This error is mapped to the " +"exception :exc:`BlockingIOError`." msgstr "" #: library/errno.rst:246 @@ -483,14 +483,14 @@ msgstr "" #: library/errno.rst:558 msgid "" -"Software caused connection abort. This error is mapped to the exception :exc:" -"`ConnectionAbortedError`." +"Software caused connection abort. This error is mapped to the " +"exception :exc:`ConnectionAbortedError`." msgstr "" #: library/errno.rst:564 msgid "" -"Connection reset by peer. This error is mapped to the exception :exc:" -"`ConnectionResetError`." +"Connection reset by peer. This error is mapped to the " +"exception :exc:`ConnectionResetError`." msgstr "" #: library/errno.rst:570 @@ -517,14 +517,14 @@ msgstr "" #: library/errno.rst:596 msgid "" -"Connection timed out. This error is mapped to the exception :exc:" -"`TimeoutError`." +"Connection timed out. This error is mapped to the " +"exception :exc:`TimeoutError`." msgstr "" #: library/errno.rst:602 msgid "" -"Connection refused. This error is mapped to the exception :exc:" -"`ConnectionRefusedError`." +"Connection refused. This error is mapped to the " +"exception :exc:`ConnectionRefusedError`." msgstr "" #: library/errno.rst:608 @@ -537,14 +537,14 @@ msgstr "" #: library/errno.rst:618 msgid "" -"Operation already in progress. This error is mapped to the exception :exc:" -"`BlockingIOError`." +"Operation already in progress. This error is mapped to the " +"exception :exc:`BlockingIOError`." msgstr "" #: library/errno.rst:624 msgid "" -"Operation now in progress. This error is mapped to the exception :exc:" -"`BlockingIOError`." +"Operation now in progress. This error is mapped to the " +"exception :exc:`BlockingIOError`." msgstr "" #: library/errno.rst:630 @@ -581,8 +581,8 @@ msgstr "" #: library/errno.rst:670 msgid "" -"Capabilities insufficient. This error is mapped to the exception :exc:" -"`PermissionError`." +"Capabilities insufficient. This error is mapped to the " +"exception :exc:`PermissionError`." msgstr "" #: library/errno.rst:673 diff --git a/library/exceptions.po b/library/exceptions.po index d7f038ad3..a9bdcc6ed 100644 --- a/library/exceptions.po +++ b/library/exceptions.po @@ -23,20 +23,21 @@ msgstr "Gömülü İstisnalar" #: 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." +"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 "" "Python'da tüm istisnalar(exceptions) :class:`BaseException` sınıfından " -"türeyen bir sınıfın örnekleri olmalıdır. Belirli bir sınıftan bahseden :" -"keyword:`except` cümlesine sahip bir :keyword:`try` deyiminde, bu cümle aynı " -"zamanda o sınıftan türetilen istisna sınıflarını da ele alır (ancak *onun* " -"türetildiği istisna sınıflarını değil). Alt sınıflandırma yoluyla ilişkili " -"olmayan iki istisna sınıfı, aynı ada sahip olsalar bile asla eşdeğer " -"değildir." +"türeyen bir sınıfın örnekleri olmalıdır. Belirli bir sınıftan " +"bahseden :keyword:`except` cümlesine sahip bir :keyword:`try` deyiminde, bu " +"cümle aynı zamanda o sınıftan türetilen istisna sınıflarını da ele alır " +"(ancak *onun* türetildiği istisna sınıflarını değil). Alt sınıflandırma " +"yoluyla ilişkili olmayan iki istisna sınıfı, aynı ada sahip olsalar bile " +"asla eşdeğer değildir." #: library/exceptions.rst:19 #, fuzzy @@ -72,10 +73,10 @@ msgstr "" #: 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`." +"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 "" "Gömülü istisna sınıfları yeni istisnalar tanımlamak için alt sınıflara " "ayrılabilir; programcıların yeni istisnaları :exc:`BaseException` sınıfından " @@ -99,22 +100,22 @@ msgstr "" msgid "" "When raising a new exception while another exception is already being " "handled, the new exception's :attr:`!__context__` attribute is automatically " -"set to the handled exception. An exception may be handled when an :keyword:" -"`except` or :keyword:`finally` clause, or a :keyword:`with` statement, is " -"used." +"set to the handled exception. An exception may be handled when " +"an :keyword:`except` or :keyword:`finally` clause, or a :keyword:`with` " +"statement, is used." msgstr "" "Başka bir istisna zaten işlenirken yeni bir istisna yükseltirken, yeni " "istisnanın :attr:`!__context__` niteliği otomatik olarak işlenen istisnaya " -"ayarlanır. Bir :keyword:`except` veya :keyword:`finally` cümlesi veya bir :" -"keyword:`with` deyimi kullanıldığında bir istisna ele alınabilir." +"ayarlanır. Bir :keyword:`except` veya :keyword:`finally` cümlesi veya " +"bir :keyword:`with` deyimi kullanıldığında bir istisna ele alınabilir." #: library/exceptions.rst:59 msgid "" "This implicit exception context can be supplemented with an explicit cause " "by using :keyword:`!from` with :keyword:`raise`::" msgstr "" -"Bu örtük istisna bağlamı(implicit exception context), :keyword:`!from` ile :" -"keyword:`raise`: kullanılarak açık bir neden ile desteklenebilir:" +"Bu örtük istisna bağlamı(implicit exception context), :keyword:`!from` " +"ile :keyword:`raise`: kullanılarak açık bir neden ile desteklenebilir:" #: library/exceptions.rst:63 msgid "raise new_exc from original_exc" @@ -136,10 +137,10 @@ msgstr "" "ayarlanacaktır. :attr:`!__cause__` ayarı aynı zamanda :attr:`!" "__suppress_context__` niteliğini de örtük(implicit) olarak ``True`` olarak " "ayarlar, böylece ``raise new_exc from None`` kullanımı görüntüleme amacıyla " -"eski istisnayı yenisiyle değiştirirken (örneğin :exc:`KeyError` ifadesini :" -"exc:`AttributeError` ifadesine dönüştürmek), hata ayıklama sırasında iç " -"gözlem için eski istisnayı :attr:`!__context__` içinde kullanılabilir " -"bırakır." +"eski istisnayı yenisiyle değiştirirken (örneğin :exc:`KeyError` " +"ifadesini :exc:`AttributeError` ifadesine dönüştürmek), hata ayıklama " +"sırasında iç gözlem için eski istisnayı :attr:`!__context__` içinde " +"kullanılabilir bırakır." #: library/exceptions.rst:74 msgid "" @@ -150,10 +151,10 @@ msgid "" "__cause__` is :const:`None` and :attr:`!__suppress_context__` is false." msgstr "" "Varsayılan geri izleme görüntüleme kodu(default traceback display code), " -"istisnanın geri izlemesine ek olarak bu zincirleme istisnaları da gösterir. :" -"attr:`!__cause__` içinde açıkça zincirlenmiş bir istisna mevcut olduğunda " -"her zaman gösterilir. :attr:`!__context__` içindeki dolaylı zincirleme " -"istisna yalnızca :attr:`!__cause__` :const:`None` ve :attr:`!" +"istisnanın geri izlemesine ek olarak bu zincirleme istisnaları da " +"gösterir. :attr:`!__cause__` içinde açıkça zincirlenmiş bir istisna mevcut " +"olduğunda her zaman gösterilir. :attr:`!__context__` içindeki dolaylı " +"zincirleme istisna yalnızca :attr:`!__cause__` :const:`None` ve :attr:`!" "__suppress_context__` false ise gösterilir." #: library/exceptions.rst:80 @@ -185,20 +186,21 @@ msgstr "" #: library/exceptions.rst:95 msgid "" -"Most built-in exceptions are implemented in C for efficiency, see: :source:" -"`Objects/exceptions.c`. Some have custom memory layouts which makes it " -"impossible to create a subclass that inherits from multiple exception types. " -"The memory layout of a type is an implementation detail and might change " -"between Python versions, leading to new conflicts in the future. Therefore, " -"it's recommended to avoid subclassing multiple exception types altogether." -msgstr "" -"Çoğu gömülü istisna, verimlilik için C dilinde uygulanmıştır, bkz: :source:" -"`Objects/exceptions.c`. Bazılarının özel bellek düzenleri vardır, bu da " -"birden fazla istisna türünden miras alan bir alt sınıf oluşturmayı imkansız " -"kılar. Bir türün bellek düzeni bir uygulama detayıdır ve Python sürümleri " -"arasında değişebilir, bu da gelecekte yeni çakışmalara yol açabilir. Bu " -"nedenle, birden fazla istisna türünün alt sınıfını oluşturmaktan tamamen " -"kaçınmanız önerilir." +"Most built-in exceptions are implemented in C for efficiency, " +"see: :source:`Objects/exceptions.c`. Some have custom memory layouts which " +"makes it impossible to create a subclass that inherits from multiple " +"exception types. The memory layout of a type is an implementation detail and " +"might change between Python versions, leading to new conflicts in the " +"future. Therefore, it's recommended to avoid subclassing multiple exception " +"types altogether." +msgstr "" +"Çoğu gömülü istisna, verimlilik için C dilinde uygulanmıştır, " +"bkz: :source:`Objects/exceptions.c`. Bazılarının özel bellek düzenleri " +"vardır, bu da birden fazla istisna türünden miras alan bir alt sınıf " +"oluşturmayı imkansız kılar. Bir türün bellek düzeni bir uygulama detayıdır " +"ve Python sürümleri arasında değişebilir, bu da gelecekte yeni çakışmalara " +"yol açabilir. Bu nedenle, birden fazla istisna türünün alt sınıfını " +"oluşturmaktan tamamen kaçınmanız önerilir." #: library/exceptions.rst:105 msgid "Base classes" @@ -215,14 +217,14 @@ msgstr "" #: library/exceptions.rst:111 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 " +"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 "" "Tüm gömülü istisnalar için temel sınıf. Kullanıcı tanımlı sınıflar " -"tarafından doğrudan miras alınması amaçlanmamıştır (bunun için :exc:" -"`Exception` kullanın). Bu sınıfın bir örneği üzerinde :func:`str` " +"tarafından doğrudan miras alınması amaçlanmamıştır (bunun " +"için :exc:`Exception` kullanın). Bu sınıfın bir örneği üzerinde :func:`str` " "çağrılırsa, örneğin argüman(lar)ının gösterimi veya argüman yoksa boş dize " "döndürülür." @@ -233,10 +235,10 @@ msgid "" "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 "" -"İstisna kurucusuna verilen argümanlar demeti. Bazı gömülü istisnalar (:exc:" -"`OSError` gibi) belirli sayıda argüman bekler ve bu ikilinin elemanlarına " -"özel bir anlam atarken, diğerleri genellikle yalnızca bir hata mesajı veren " -"tek bir dizeyle çağrılır." +"İstisna kurucusuna verilen argümanlar demeti. Bazı gömülü istisnalar " +"(:exc:`OSError` gibi) belirli sayıda argüman bekler ve bu ikilinin " +"elemanlarına özel bir anlam atarken, diğerleri genellikle yalnızca bir hata " +"mesajı veren tek bir dizeyle çağrılır." #: library/exceptions.rst:126 msgid "" @@ -282,13 +284,14 @@ msgid "" "if ``note`` is not a string." msgstr "" "İstisna dizesinden sonra standart geri dönüşte görünen istisna notlarına " -"``note`` dizesini ekleyin. Eğer ``note`` bir string değilse bir :exc:" -"`TypeError` oluşur." +"``note`` dizesini ekleyin. Eğer ``note`` bir string değilse " +"bir :exc:`TypeError` oluşur." #: library/exceptions.rst:157 msgid "" -"A list of the notes of this exception, which were added with :meth:" -"`add_note`. This attribute is created when :meth:`add_note` is called." +"A list of the notes of this exception, which were added " +"with :meth:`add_note`. This attribute is created when :meth:`add_note` is " +"called." msgstr "" "Bu istisnanın :meth:`add_note` ile eklenen notlarının bir listesi. Bu " "nitelik :meth:`add_note` çağrıldığında oluşturulur." @@ -305,12 +308,11 @@ msgstr "" #: library/exceptions.rst:171 msgid "" "The base class for those built-in exceptions that are raised for various " -"arithmetic errors: :exc:`OverflowError`, :exc:`ZeroDivisionError`, :exc:" -"`FloatingPointError`." +"arithmetic " +"errors: :exc:`OverflowError`, :exc:`ZeroDivisionError`, :exc:`FloatingPointError`." msgstr "" "Çeşitli aritmetik hatalar için oluşturulan gömülü istisnalar için temel " -"sınıf: :exc:`OverflowError`, :exc:`ZeroDivisionError`, :exc:" -"`FloatingPointError`." +"sınıf: :exc:`OverflowError`, :exc:`ZeroDivisionError`, :exc:`FloatingPointError`." #: library/exceptions.rst:178 msgid "" @@ -327,8 +329,9 @@ msgid "" "This can be raised directly by :func:`codecs.lookup`." msgstr "" "Bir eşleme veya dizide kullanılan bir anahtar veya dizin geçersiz olduğunda " -"ortaya çıkan istisnalar için temel sınıf: :exc:`IndexError`, :exc:" -"`KeyError`. Bu doğrudan :func:`codecs.lookup` tarafından oluşturulabilir." +"ortaya çıkan istisnalar için temel " +"sınıf: :exc:`IndexError`, :exc:`KeyError`. Bu " +"doğrudan :func:`codecs.lookup` tarafından oluşturulabilir." #: library/exceptions.rst:190 msgid "Concrete exceptions" @@ -371,12 +374,13 @@ msgstr ":attr:`name` ve :attr:`obj` nitelikleri eklendi." #: library/exceptions.rst:217 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.)" +"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 "" ":func:`input` fonksiyonu herhangi bir veri okumadan dosya sonu koşuluna (end-" -"of-file EOF) ulaştığında ortaya çıkar. (Not: :meth:`io.IOBase.read` ve :meth:" -"`io.IOBase.readline` yöntemleri EOF'ye ulaştıklarında boş bir dize " +"of-file EOF) ulaştığında ortaya çıkar. (Not: :meth:`io.IOBase.read` " +"ve :meth:`io.IOBase.readline` yöntemleri EOF'ye ulaştıklarında boş bir dize " "döndürürler)" #: library/exceptions.rst:224 @@ -385,10 +389,10 @@ msgstr "Şu anda kullanılmıyor." #: library/exceptions.rst:229 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." +"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 "" "Bir :term:`generator` veya :term:`coroutine` kapatıldığında ortaya çıkar; " "bkz :meth:`generator.close` ve :meth:`coroutine.close`. Teknik olarak bir " @@ -428,12 +432,12 @@ msgstr ":attr:`name` ve :attr:`path` nitelikleri eklendi." #: library/exceptions.rst:257 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`." +"module could not be located. It is also raised when ``None`` is found " +"in :data:`sys.modules`." msgstr "" -"Bir modül bulunamadığında :keyword:`import` tarafından ortaya çıkarılan :exc:" -"`ImportError` alt sınıfı. Ayrıca :data:`sys.modules` içinde ``None`` " -"bulunduğunda da ortaya çıkar." +"Bir modül bulunamadığında :keyword:`import` tarafından ortaya " +"çıkarılan :exc:`ImportError` alt sınıfı. Ayrıca :data:`sys.modules` içinde " +"``None`` bulunduğunda da ortaya çıkar." #: library/exceptions.rst:266 msgid "" @@ -455,17 +459,17 @@ msgstr "" #: library/exceptions.rst:282 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 " +"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 "" "Kullanıcı kesme(interrupt) tuşuna bastığında oluşur (normalde :kbd:`Control-" "C` veya :kbd:`Delete`). Yürütme sırasında düzenli olarak kesme kontrolü " "yapılır. İstisna, :exc:`Exception` kodunu yakalayan kod tarafından " -"yanlışlıkla yakalanmamak ve böylece yorumlayıcının çıkmasını önlemek için :" -"exc:`BaseException` kodundan miras alır." +"yanlışlıkla yakalanmamak ve böylece yorumlayıcının çıkmasını önlemek " +"için :exc:`BaseException` kodundan miras alır." #: library/exceptions.rst:290 msgid "" @@ -477,20 +481,21 @@ msgid "" msgstr "" "Bir :exc:`KeyboardInterrupt` yakalamak özel dikkat gerektirir. Tahmin " "edilemeyen noktalarda yükseltilebildiğinden, bazı durumlarda çalışan " -"programı tutarsız bir durumda bırakabilir. Genellikle en iyisi :exc:" -"`KeyboardInterrupt` ın programı mümkün olduğunca çabuk sonlandırmasına izin " -"vermek veya tamamen yükseltilmesinden kaçınmaktır. (Bkz. :ref:`handlers-and-" -"exceptions`.)" +"programı tutarsız bir durumda bırakabilir. Genellikle en " +"iyisi :exc:`KeyboardInterrupt` ın programı mümkün olduğunca çabuk " +"sonlandırmasına izin vermek veya tamamen yükseltilmesinden kaçınmaktır. " +"(Bkz. :ref:`handlers-and-exceptions`.)" #: library/exceptions.rst:300 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." +"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 "" "Bir işlemin belleği tükendiğinde ancak durum hala kurtarılabildiğinde (bazı " "nesneleri silerek) yükseltilir. İlişkili değer, ne tür bir (dahili) işlemin " @@ -560,8 +565,8 @@ msgstr "" #: library/exceptions.rst:347 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)." +"error, including I/O failures such as \"file not found\" or \"disk full\" " +"(not for illegal argument types or other incidental errors)." msgstr "" "Bu istisna, bir sistem işlevi \"dosya bulunamadı\" veya \"disk dolu\" gibi G/" "Ç hataları da dahil olmak üzere sistemle ilgili bir hata döndürdüğünde " @@ -572,29 +577,29 @@ msgstr "" 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." +"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 "" "Kurucunun(constructor) ikinci formu, aşağıda açıklanan ilgili nitelikleri " "ayarlar. Öznitelikler belirtilmezse varsayılan olarak :const:`None` olur. " -"Geriye dönük uyumluluk için, üç argüman geçilirse, :attr:`~BaseException." -"args` niteliği yalnızca ilk iki kurucu argümanının 2'li bir çiftini(tuple) " -"içerir." +"Geriye dönük uyumluluk için, üç argüman " +"geçilirse, :attr:`~BaseException.args` niteliği yalnızca ilk iki kurucu " +"argümanının 2'li bir çiftini(tuple) içerir." #: library/exceptions.rst:357 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." +"final :attr:`.errno` value. This behaviour only occurs when " +"constructing :exc:`OSError` directly or via an alias, and is not inherited " +"when subclassing." msgstr "" -"Kurucu genellikle aşağıda `OS istisnaları`_ bölümünde açıklandığı gibi :exc:" -"`OSError` alt sınıfını döndürür. Belirli alt sınıf son :attr:`.errno` " -"değerine bağlıdır. Bu davranış yalnızca :exc:`OSError` doğrudan veya bir " -"takma ad aracılığıyla oluşturulurken ortaya çıkar ve alt sınıf " -"oluşturulurken miras alınmaz." +"Kurucu genellikle aşağıda `OS istisnaları`_ bölümünde açıklandığı " +"gibi :exc:`OSError` alt sınıfını döndürür. Belirli alt sınıf " +"son :attr:`.errno` değerine bağlıdır. Bu davranış yalnızca :exc:`OSError` " +"doğrudan veya bir takma ad aracılığıyla oluşturulurken ortaya çıkar ve alt " +"sınıf oluşturulurken miras alınmaz." #: library/exceptions.rst:365 msgid "A numeric error code from the C variable :c:data:`errno`." @@ -602,65 +607,66 @@ msgstr "C değişkeni :c:data:`errno` dan alınan sayısal bir hata kodu." #: library/exceptions.rst:369 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." +"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 "" -"Windows altında, bu size yerel Windows hata kodunu verir. O halde :attr:`." -"errno` niteliği bu yerel hata kodunun POSIX terimleriyle yaklaşık bir " -"çevirisidir." +"Windows altında, bu size yerel Windows hata kodunu verir. O " +"halde :attr:`.errno` niteliği bu yerel hata kodunun POSIX terimleriyle " +"yaklaşık bir çevirisidir." #: library/exceptions.rst:373 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." +"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 "" -"Windows altında, *winerror* kurucu bağımsız değişkeni bir tamsayı ise, :attr:" -"`.errno` özniteliği Windows hata kodundan belirlenir ve *errno* bağımsız " -"değişkeni yok sayılır. Diğer platformlarda, *winerror* argümanı yok sayılır " -"ve :attr:`winerror` niteliği mevcut değildir." +"Windows altında, *winerror* kurucu bağımsız değişkeni bir tamsayı " +"ise, :attr:`.errno` özniteliği Windows hata kodundan belirlenir ve *errno* " +"bağımsız değişkeni yok sayılır. Diğer platformlarda, *winerror* argümanı yok " +"sayılır ve :attr:`winerror` niteliği mevcut değildir." #: library/exceptions.rst:381 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." +"formatted by the C functions :c:func:`perror` under POSIX, " +"and :c:func:`FormatMessage` under Windows." msgstr "" -"İşletim sistemi tarafından sağlanan ilgili hata mesajı. POSIX altında :c:" -"func:`perror` ve Windows altında :c:func:`FormatMessage` C işlevleri " -"tarafından biçimlendirilir." +"İşletim sistemi tarafından sağlanan ilgili hata mesajı. POSIX " +"altında :c:func:`perror` ve Windows altında :c:func:`FormatMessage` C " +"işlevleri tarafından biçimlendirilir." #: library/exceptions.rst:389 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." +"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 "" -"Bir dosya sistemi yolu içeren istisnalar için (örneğin :func:`open` veya :" -"func:`os.unlink`), :attr:`filename` fonksiyona aktarılan dosya adıdır. İki " -"dosya sistemi yolu içeren fonksiyonlar için (:func:`os.rename` gibi), :attr:" -"`filename2` fonksiyona aktarılan ikinci dosya adına karşılık gelir." +"Bir dosya sistemi yolu içeren istisnalar için (örneğin :func:`open` " +"veya :func:`os.unlink`), :attr:`filename` fonksiyona aktarılan dosya adıdır. " +"İki dosya sistemi yolu içeren fonksiyonlar için (:func:`os.rename` " +"gibi), :attr:`filename2` fonksiyona aktarılan ikinci dosya adına karşılık " +"gelir." #: library/exceptions.rst:396 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." +":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 "" -":exc:`EnvironmentError`, :exc:`IOError`, :exc:`WindowsError`, :exc:`socket." -"error`, :exc:`select.error` ve :exc:`mmap.error`, :exc:`OSError` ile " -"birleştirilmiştir ve kurucu bir alt sınıf döndürebilir." +":exc:`EnvironmentError`, :exc:`IOError`, :exc:`WindowsError`, :exc:`socket.error`, :exc:`select.error` " +"ve :exc:`mmap.error`, :exc:`OSError` ile birleştirilmiştir ve kurucu bir alt " +"sınıf döndürebilir." #: library/exceptions.rst:402 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 :term:" -"`filesystem encoding and error handler`. Also, the *filename2* constructor " -"argument and attribute was added." +"function, instead of the name encoded to or decoded from " +"the :term:`filesystem encoding and error handler`. Also, the *filename2* " +"constructor argument and attribute was added." msgstr "" ":attr:`filename` özniteliği artık :term:`filesystem encoding and error " "handler` ile kodlanan veya kodu çözülen ad yerine işleve aktarılan orijinal " @@ -670,29 +676,30 @@ msgstr "" #, fuzzy 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." +"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 "" "Bir aritmetik işlemin sonucu gösterilemeyecek kadar büyük olduğunda ortaya " -"çıkar. Bu durum tamsayılar için oluşmaz (tamsayılar vazgeçmektense :exc:" -"`MemoryError` yükseltmeyi tercih ederler). Bununla birlikte, tarihsel " -"nedenlerden dolayı, OverflowError bazen gerekli bir aralığın dışında kalan " -"tamsayılar için yükseltilir. C'de kayan nokta istisna işlemlerinin(floating " -"point exception handling) standartlaştırılmaması nedeniyle, çoğu kayan nokta " -"işlemi kontrol edilmez." +"çıkar. Bu durum tamsayılar için oluşmaz (tamsayılar " +"vazgeçmektense :exc:`MemoryError` yükseltmeyi tercih ederler). Bununla " +"birlikte, tarihsel nedenlerden dolayı, OverflowError bazen gerekli bir " +"aralığın dışında kalan tamsayılar için yükseltilir. C'de kayan nokta istisna " +"işlemlerinin(floating point exception handling) standartlaştırılmaması " +"nedeniyle, çoğu kayan nokta işlemi kontrol edilmez." #: library/exceptions.rst:421 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." +"interpreter detects that the maximum recursion depth " +"(see :func:`sys.getrecursionlimit`) is exceeded." msgstr "" "Bu istisna :exc:`RuntimeError` öğesinden türetilmiştir. Yorumlayıcı maksimum " -"özyineleme derinliğinin(recursion depth) (bkz. :func:`sys." -"getrecursionlimit`) aşıldığını tespit ettiğinde ortaya çıkar." +"özyineleme derinliğinin(recursion depth) " +"(bkz. :func:`sys.getrecursionlimit`) aşıldığını tespit ettiğinde ortaya " +"çıkar." #: library/exceptions.rst:425 msgid "Previously, a plain :exc:`RuntimeError` was raised." @@ -700,9 +707,9 @@ msgstr "Önceden, düz bir :exc:`RuntimeError` oluşturulurdu." #: library/exceptions.rst:431 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 " +"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 "" "Bu istisna, :func:`weakref.proxy` fonksiyonu tarafından oluşturulan bir " @@ -723,29 +730,30 @@ msgstr "" #: library/exceptions.rst:446 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." +"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 "" -"Yerleşik işlev :func:`next` ve bir :term:`iterator` ün :meth:`~iterator." -"__next__` yöntemi tarafından yineleyici tarafından üretilen başka öğe " -"olmadığını bildirmek için yükseltilir." +"Yerleşik işlev :func:`next` ve bir :term:`iterator` " +"ün :meth:`~iterator.__next__` yöntemi tarafından yineleyici tarafından " +"üretilen başka öğe olmadığını bildirmek için yükseltilir." #: library/exceptions.rst:452 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`." +"as an argument when constructing the exception, and defaults " +"to :const:`None`." msgstr "" "İstisna nesnesinin tek bir :attr:`!value` özelliği vardır; bu özellik " -"istisna oluşturulurken argüman olarak verilir ve varsayılan olarak :const:" -"`None` değerini alır." +"istisna oluşturulurken argüman olarak verilir ve varsayılan " +"olarak :const:`None` değerini alır." #: library/exceptions.rst:456 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." +"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 "" "Bir :term:`generator` veya :term:`coroutine` fonksiyonu döndüğünde, yeni " "bir :exc:`StopIteration` örneği oluşturulur ve fonksiyon tarafından " @@ -758,10 +766,10 @@ msgid "" "is converted into a :exc:`RuntimeError` (retaining the :exc:`StopIteration` " "as the new exception's cause)." msgstr "" -"Bir generator(işleyici) kodu doğrudan veya dolaylı olarak :exc:" -"`StopIteration` değerini oluşturunca, :exc:`RuntimeError` değerine " -"dönüştürülür (yeni istisnanın nedeni olarak :exc:`StopIteration` değeri " -"korunur)." +"Bir generator(işleyici) kodu doğrudan veya dolaylı " +"olarak :exc:`StopIteration` değerini oluşturunca, :exc:`RuntimeError` " +"değerine dönüştürülür (yeni istisnanın nedeni olarak :exc:`StopIteration` " +"değeri korunur)." #: library/exceptions.rst:465 msgid "" @@ -785,28 +793,28 @@ msgid "" "raised in a generator is transformed into a :exc:`RuntimeError`." msgstr "" "Varsayılan olarak tüm kodlar için :pep:`479` özelliğini etkinleştirin: bir " -"generator'da ortaya çıkan :exc:`StopIteration` hatası bir :exc:" -"`RuntimeError` hatasına dönüştürülür." +"generator'da ortaya çıkan :exc:`StopIteration` hatası " +"bir :exc:`RuntimeError` hatasına dönüştürülür." #: library/exceptions.rst:479 msgid "" "Must be raised by :meth:`~object.__anext__` method of an :term:`asynchronous " "iterator` object to stop the iteration." msgstr "" -"Yinelemeyi durdurmak için bir :term:`asynchronous iterator` nesnesinin :meth:" -"`~object.__anext__` yöntemi tarafından oluşturulmalıdır." +"Yinelemeyi durdurmak için bir :term:`asynchronous iterator` " +"nesnesinin :meth:`~object.__anext__` yöntemi tarafından oluşturulmalıdır." #: library/exceptions.rst:486 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:" -"`compile`, :func:`exec`, or :func:`eval`, or when reading the initial script " -"or standard input (also interactively)." +"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:`compile`, :func:`exec`, or :func:`eval`, or when reading " +"the initial script or standard input (also interactively)." msgstr "" -"Ayrıştırıcı bir sözdizimi hatasıyla karşılaştığında ortaya çıkar. Bu, bir :" -"keyword:`import` deyiminde, yerleşik :func:`compile`, :func:`exec` veya :" -"func:`eval` işlevlerine yapılan bir çağrıda veya ilk kod veya standart girdi " -"okunurken (etkileşimli olarak da) meydana gelebilir." +"Ayrıştırıcı bir sözdizimi hatasıyla karşılaştığında ortaya çıkar. Bu, " +"bir :keyword:`import` deyiminde, yerleşik :func:`compile`, :func:`exec` " +"veya :func:`eval` işlevlerine yapılan bir çağrıda veya ilk kod veya standart " +"girdi okunurken (etkileşimli olarak da) meydana gelebilir." #: library/exceptions.rst:492 msgid "" @@ -877,8 +885,8 @@ msgid "" "Base class for syntax errors related to incorrect indentation. This is a " "subclass of :exc:`SyntaxError`." msgstr "" -"Yanlış girintileme ile ilgili sözdizimi hataları için temel sınıf. Bu, :exc:" -"`SyntaxError` alt sınıfıdır." +"Yanlış girintileme ile ilgili sözdizimi hataları için temel sınıf. " +"Bu, :exc:`SyntaxError` alt sınıfıdır." #: library/exceptions.rst:539 msgid "" @@ -901,8 +909,8 @@ msgstr "" #: library/exceptions.rst:549 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 " +"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 "" @@ -919,11 +927,11 @@ msgid "" "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." +"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 "" "Bu istisna :func:`sys.exit` işlevi tarafından ortaya çıkartılır. " "Yanlışlıkla :exc:`Exception` kodunu yakalayan kod tarafından yakalanmaması " @@ -946,11 +954,11 @@ msgid "" "child process after a call to :func:`os.fork`)." msgstr "" "Bir :func:`sys.exit` çağrısı bir istisnaya çevrilir, böylece temizleme " -"işleyicileri(clean-up handlers) (:keyword:`try` deyimlerinin :keyword:" -"`finally` cümleleri) çalıştırılabilir ve böylece bir hata ayıklayıcı " -"kontrolü kaybetme riski olmadan bir betiği çalıştırabilir. Hemen çıkmak " -"kesinlikle gerekliyse :func:`os._exit` fonksiyonu kullanılabilir (örneğin, :" -"func:`os.fork` çağrısından sonra alt süreçte)." +"işleyicileri(clean-up handlers) (:keyword:`try` " +"deyimlerinin :keyword:`finally` cümleleri) çalıştırılabilir ve böylece bir " +"hata ayıklayıcı kontrolü kaybetme riski olmadan bir betiği çalıştırabilir. " +"Hemen çıkmak kesinlikle gerekliyse :func:`os._exit` fonksiyonu " +"kullanılabilir (örneğin, :func:`os.fork` çağrısından sonra alt süreçte)." #: library/exceptions.rst:578 msgid "" @@ -985,25 +993,25 @@ msgstr "" #: library/exceptions.rst:592 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`." +"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 "" -"Yanlış türde argümanlar geçirmek (örneğin bir :class:`int` beklenirken bir :" -"class:`list` geçirmek) bir :exc:`TypeError` ile sonuçlanmalıdır, ancak " +"Yanlış türde argümanlar geçirmek (örneğin bir :class:`int` beklenirken " +"bir :class:`list` geçirmek) bir :exc:`TypeError` ile sonuçlanmalıdır, ancak " "yanlış değere sahip argümanlar geçirmek (örneğin beklenen sınırların dışında " "bir sayı) bir :exc:`ValueError` ile sonuçlanmalıdır." #: library/exceptions.rst:599 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`." +"but no value has been bound to that variable. This is a subclass " +"of :exc:`NameError`." msgstr "" "Bir işlev veya yöntemde yerel(local) bir değişkene referans yapıldığında, " -"ancak bu değişkene herhangi bir değer bağlanmadığında ortaya çıkar. Bu, :exc:" -"`NameError` alt sınıfıdır." +"ancak bu değişkene herhangi bir değer bağlanmadığında ortaya çıkar. " +"Bu, :exc:`NameError` alt sınıfıdır." #: library/exceptions.rst:606 msgid "" @@ -1020,8 +1028,9 @@ msgid "" "invalid input that the codec failed on." msgstr "" ":exc:`UnicodeError` kodlama(encoding) veya kod çözme(decoding) hatasını " -"tanımlayan özniteliklere sahiptir. Örneğin, ``err.object[err.start:err." -"end]`` codec'in başarısız olduğu belirli geçersiz girdiyi verir." +"tanımlayan özniteliklere sahiptir. Örneğin, " +"``err.object[err.start:err.end]`` codec'in başarısız olduğu belirli geçersiz " +"girdiyi verir." #: library/exceptions.rst:615 msgid "The name of the encoding that raised the error." @@ -1048,8 +1057,8 @@ msgid "" "Raised when a Unicode-related error occurs during encoding. It is a " "subclass of :exc:`UnicodeError`." msgstr "" -"Kodlama sırasında Unicode ile ilgili bir hata oluştuğunda ortaya çıkar. Bu :" -"exc:`UnicodeError` alt sınıfıdır." +"Kodlama sırasında Unicode ile ilgili bir hata oluştuğunda ortaya çıkar. " +"Bu :exc:`UnicodeError` alt sınıfıdır." #: library/exceptions.rst:642 msgid "" @@ -1064,8 +1073,8 @@ msgid "" "Raised when a Unicode-related error occurs during translating. It is a " "subclass of :exc:`UnicodeError`." msgstr "" -"Çeviri sırasında Unicode ile ilgili bir hata oluştuğunda ortaya çıkar. Bu :" -"exc:`UnicodeError` alt sınıfıdır." +"Çeviri sırasında Unicode ile ilgili bir hata oluştuğunda ortaya çıkar. " +"Bu :exc:`UnicodeError` alt sınıfıdır." #: library/exceptions.rst:654 msgid "" @@ -1114,14 +1123,14 @@ msgstr "" #: library/exceptions.rst:686 msgid "" "Raised when an operation would block on an object (e.g. socket) set for non-" -"blocking operation. Corresponds to :c:data:`errno` :py:const:`~errno." -"EAGAIN`, :py:const:`~errno.EALREADY`, :py:const:`~errno.EWOULDBLOCK` and :py:" -"const:`~errno.EINPROGRESS`." +"blocking operation. Corresponds " +"to :c:data:`errno` :py:const:`~errno.EAGAIN`, :py:const:`~errno.EALREADY`, :py:const:`~errno.EWOULDBLOCK` " +"and :py:const:`~errno.EINPROGRESS`." msgstr "" "Bir işlem, bloklanmayan işlem(non-blocking operation) için ayarlanmış bir " -"nesne (örn. soket) üzerinde bloklandığında ortaya çıkar. :c:data:`errno` :py:" -"const:`~errno.EAGAIN`, :py:const:`~errno.EALREADY`, :py:const:`~errno." -"EWOULDBLOCK` ve :py:const:`~errno.EINPROGRESS` değerlerine karşılık gelir." +"nesne (örn. soket) üzerinde bloklandığında ortaya " +"çıkar. :c:data:`errno` :py:const:`~errno.EAGAIN`, :py:const:`~errno.EALREADY`, :py:const:`~errno.EWOULDBLOCK` " +"ve :py:const:`~errno.EINPROGRESS` değerlerine karşılık gelir." #: library/exceptions.rst:691 msgid "" @@ -1143,8 +1152,8 @@ msgstr "" #: library/exceptions.rst:702 msgid "" -"Raised when an operation on a child process failed. Corresponds to :c:data:" -"`errno` :py:const:`~errno.ECHILD`." +"Raised when an operation on a child process failed. Corresponds " +"to :c:data:`errno` :py:const:`~errno.ECHILD`." msgstr "" "Bir alt süreç(child process) üzerindeki bir işlem başarısız olduğunda " "yükseltilir. Karşılığı :c:data:`errno` :py:const:`~errno.ECHILD`." @@ -1155,52 +1164,54 @@ msgstr "Bağlantı ile ilgili konular için bir temel sınıf." #: library/exceptions.rst:709 msgid "" -"Subclasses are :exc:`BrokenPipeError`, :exc:`ConnectionAbortedError`, :exc:" -"`ConnectionRefusedError` and :exc:`ConnectionResetError`." +"Subclasses " +"are :exc:`BrokenPipeError`, :exc:`ConnectionAbortedError`, :exc:`ConnectionRefusedError` " +"and :exc:`ConnectionResetError`." msgstr "" -"Alt sınıflar :exc:`BrokenPipeError`, :exc:`ConnectionAbortedError`, :exc:" -"`ConnectionRefusedError` ve :exc:`ConnectionResetError`." +"Alt " +"sınıflar :exc:`BrokenPipeError`, :exc:`ConnectionAbortedError`, :exc:`ConnectionRefusedError` " +"ve :exc:`ConnectionResetError`." #: library/exceptions.rst:714 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` :py:const:" -"`~errno.EPIPE` and :py:const:`~errno.ESHUTDOWN`." +"has been shutdown for writing. Corresponds " +"to :c:data:`errno` :py:const:`~errno.EPIPE` and :py:const:`~errno.ESHUTDOWN`." msgstr "" ":exc:`ConnectionError` alt sınıfı, diğer ucu kapatılmış bir pipe'ın üzerine " "yazmaya çalışıldığında veya yazmaya kapatılmış bir soket üzerine yazmaya " -"çalışıldığında ortaya çıkar. :c:data:`errno` :py:const:`~errno.EPIPE` ve :py:" -"const:`~errno.ESHUTDOWN` değerlerine karşılık gelir." +"çalışıldığında ortaya çıkar. :c:data:`errno` :py:const:`~errno.EPIPE` " +"ve :py:const:`~errno.ESHUTDOWN` değerlerine karşılık gelir." #: library/exceptions.rst:721 msgid "" "A subclass of :exc:`ConnectionError`, raised when a connection attempt is " -"aborted by the peer. Corresponds to :c:data:`errno` :py:const:`~errno." -"ECONNABORTED`." +"aborted by the peer. Corresponds " +"to :c:data:`errno` :py:const:`~errno.ECONNABORTED`." msgstr "" -"Bir bağlantı girişimi eş(peer) tarafından iptal edildiğinde ortaya çıkan :" -"exc:`ConnectionError` alt sınıfı. Karşılığı :c:data:`errno` :py:const:" -"`~errno.ECONNABORTED`." +"Bir bağlantı girişimi eş(peer) tarafından iptal edildiğinde ortaya " +"çıkan :exc:`ConnectionError` alt sınıfı. " +"Karşılığı :c:data:`errno` :py:const:`~errno.ECONNABORTED`." #: library/exceptions.rst:727 msgid "" "A subclass of :exc:`ConnectionError`, raised when a connection attempt is " -"refused by the peer. Corresponds to :c:data:`errno` :py:const:`~errno." -"ECONNREFUSED`." +"refused by the peer. Corresponds " +"to :c:data:`errno` :py:const:`~errno.ECONNREFUSED`." msgstr "" -"Bir bağlantı girişimi eş(peer) tarafından reddedildiğinde ortaya çıkan :exc:" -"`ConnectionError` alt sınıfı. Karşılığı :c:data:`errno` :py:const:`~errno." -"ECONNREFUSED`." +"Bir bağlantı girişimi eş(peer) tarafından reddedildiğinde ortaya " +"çıkan :exc:`ConnectionError` alt sınıfı. " +"Karşılığı :c:data:`errno` :py:const:`~errno.ECONNREFUSED`." #: library/exceptions.rst:733 msgid "" "A subclass of :exc:`ConnectionError`, raised when a connection is reset by " "the peer. Corresponds to :c:data:`errno` :py:const:`~errno.ECONNRESET`." msgstr "" -"Bir bağlantı eş(peer) tarafından sıfırlandığında ortaya çıkan :exc:" -"`ConnectionError` alt sınıfı. Karşılığı :c:data:`errno` :py:const:`~errno." -"ECONNRESET`." +"Bir bağlantı eş(peer) tarafından sıfırlandığında ortaya " +"çıkan :exc:`ConnectionError` alt sınıfı. " +"Karşılığı :c:data:`errno` :py:const:`~errno.ECONNRESET`." #: library/exceptions.rst:739 msgid "" @@ -1250,8 +1261,8 @@ msgid "" "Raised when a directory operation (such as :func:`os.listdir`) is requested " "on something which is not a directory. On most POSIX platforms, it may also " "be raised if an operation attempts to open or traverse a non-directory file " -"as if it were a directory. Corresponds to :c:data:`errno` :py:const:`~errno." -"ENOTDIR`." +"as if it were a directory. Corresponds " +"to :c:data:`errno` :py:const:`~errno.ENOTDIR`." msgstr "" "Dizin olmayan bir şey üzerinde bir dizin işlemi (örneğin :func:`os.listdir`) " "istendiğinde ortaya çıakr. Çoğu POSIX platformunda, bir işlem dizin olmayan " @@ -1261,35 +1272,35 @@ msgstr "" #: library/exceptions.rst:773 msgid "" "Raised when trying to run an operation without the adequate access rights - " -"for example filesystem permissions. Corresponds to :c:data:`errno` :py:const:" -"`~errno.EACCES`, :py:const:`~errno.EPERM`, and :py:const:`~errno." -"ENOTCAPABLE`." +"for example filesystem permissions. Corresponds " +"to :c:data:`errno` :py:const:`~errno.EACCES`, :py:const:`~errno.EPERM`, " +"and :py:const:`~errno.ENOTCAPABLE`." msgstr "" "Yeterli erişim hakları (örneğin dosya sistemi izinleri) olmadan bir işlem " -"çalıştırılmaya çalışıldığında ortaya çıkar. :c:data:`errno` :py:const:" -"`~errno.EACCES`, :py:const:`~errno.EPERM` ve :py:const:`~errno.ENOTCAPABLE` " -"değerlerine karşılık gelir." +"çalıştırılmaya çalışıldığında ortaya " +"çıkar. :c:data:`errno` :py:const:`~errno.EACCES`, :py:const:`~errno.EPERM` " +"ve :py:const:`~errno.ENOTCAPABLE` değerlerine karşılık gelir." #: library/exceptions.rst:778 msgid "" -"WASI's :py:const:`~errno.ENOTCAPABLE` is now mapped to :exc:" -"`PermissionError`." +"WASI's :py:const:`~errno.ENOTCAPABLE` is now mapped " +"to :exc:`PermissionError`." msgstr "" "WASI'nin :py:const:`~errno.ENOTCAPABLE` ifadesi artık :exc:`PermissionError` " "ile eşleştirilmiştir." #: library/exceptions.rst:784 msgid "" -"Raised when a given process doesn't exist. Corresponds to :c:data:`errno` :" -"py:const:`~errno.ESRCH`." +"Raised when a given process doesn't exist. Corresponds " +"to :c:data:`errno` :py:const:`~errno.ESRCH`." msgstr "" -"Belirli bir süreç mevcut olmadığında ortaya çıkar. Karşılığı :c:data:" -"`errno` :py:const:`~errno.ESRCH`." +"Belirli bir süreç mevcut olmadığında ortaya çıkar. " +"Karşılığı :c:data:`errno` :py:const:`~errno.ESRCH`." #: library/exceptions.rst:789 msgid "" -"Raised when a system function timed out at the system level. Corresponds to :" -"c:data:`errno` :py:const:`~errno.ETIMEDOUT`." +"Raised when a system function timed out at the system level. Corresponds " +"to :c:data:`errno` :py:const:`~errno.ETIMEDOUT`." msgstr "" "Bir sistem işlevi sistem düzeyinde zaman aşımına uğradığında ortaya çıkar. " "Karşılığı :c:data:`errno` :py:const:`~errno.ETIMEDOUT`." @@ -1310,8 +1321,8 @@ msgstr "Uyarılar" #: library/exceptions.rst:806 msgid "" -"The following exceptions are used as warning categories; see the :ref:" -"`warning-categories` documentation for more details." +"The following exceptions are used as warning categories; see " +"the :ref:`warning-categories` documentation for more details." msgstr "" "Aşağıdaki istisnalar uyarı kategorileri olarak kullanılır; daha fazla " "ayrıntı için :ref:`warning-categories` belgesine bakın." @@ -1334,9 +1345,9 @@ msgstr "" #: library/exceptions.rst:824 msgid "" -"Ignored by the default warning filters, except in the ``__main__`` module (:" -"pep:`565`). Enabling the :ref:`Python Development Mode ` shows this " -"warning." +"Ignored by the default warning filters, except in the ``__main__`` module " +"(:pep:`565`). Enabling the :ref:`Python Development Mode ` shows " +"this warning." msgstr "" "``__main__`` modülü (:pep:`565`) dışında varsayılan uyarı filtreleri " "tarafından yok sayılır. :ref:`Python Geliştirme Modu ` " @@ -1361,9 +1372,9 @@ msgid "" "already active deprecations." msgstr "" "Bu sınıf nadiren kullanılır çünkü yaklaşan olası bir kullanımdan kaldırma " -"hakkında bir uyarı yayınlamak alışılmadık bir durumdur ve :exc:" -"`DeprecationWarning` zaten aktif olan kullanımdan kaldırmalar için tercih " -"edilir." +"hakkında bir uyarı yayınlamak alışılmadık bir durumdur " +"ve :exc:`DeprecationWarning` zaten aktif olan kullanımdan kaldırmalar için " +"tercih edilir." #: library/exceptions.rst:867 library/exceptions.rst:894 msgid "" @@ -1433,41 +1444,43 @@ msgstr "" "Aşağıdakiler, birden fazla ilgisiz istisnayı yükseltmek gerektiğinde " "kullanılır. Bunlar istisna hiyerarşisinin bir parçasıdır, bu nedenle diğer " "tüm istisnalar gibi :keyword:`except` ile ele alınabilirler. Ayrıca, " -"içerdikleri istisnaların türlerine göre alt gruplarını eşleştiren :keyword:" -"`except*` tarafından tanınırlar." +"içerdikleri istisnaların türlerine göre alt gruplarını " +"eşleştiren :keyword:`except*` tarafından tanınırlar." #: library/exceptions.rst:914 msgid "" "Both of these exception types wrap the exceptions in the sequence ``excs``. " "The ``msg`` parameter must be a string. The difference between the two " "classes is that :exc:`BaseExceptionGroup` extends :exc:`BaseException` and " -"it can wrap any exception, while :exc:`ExceptionGroup` extends :exc:" -"`Exception` and it can only wrap subclasses of :exc:`Exception`. This design " -"is so that ``except Exception`` catches an :exc:`ExceptionGroup` but not :" -"exc:`BaseExceptionGroup`." +"it can wrap any exception, while :exc:`ExceptionGroup` " +"extends :exc:`Exception` and it can only wrap subclasses " +"of :exc:`Exception`. This design is so that ``except Exception`` catches " +"an :exc:`ExceptionGroup` but not :exc:`BaseExceptionGroup`." msgstr "" "Bu istisna türlerinin her ikisi de istisnaları ``excs`` dizisine sarar. " -"``msg`` parametresi bir string olmalıdır. İki sınıf arasındaki fark, :exc:" -"`BaseExceptionGroup`, :exc:`BaseException`'ı genişletir ve herhangi bir " -"istisnayı sarabilirken, :exc:`ExceptionGroup`, :exc:`Exception`'ı genişletir " -"ve yalnızca :exc:`Exception`'ın alt sınıflarını sarabilir. Bu tasarım " -"sayesinde ``except Exception`` bir :exc:`ExceptionGroup` u yakalar ancak :" -"exc:`BaseExceptionGroup` u yakalayamaz." +"``msg`` parametresi bir string olmalıdır. İki sınıf arasındaki " +"fark, :exc:`BaseExceptionGroup`, :exc:`BaseException`'ı genişletir ve " +"herhangi bir istisnayı " +"sarabilirken, :exc:`ExceptionGroup`, :exc:`Exception`'ı genişletir ve " +"yalnızca :exc:`Exception`'ın alt sınıflarını sarabilir. Bu tasarım sayesinde " +"``except Exception`` bir :exc:`ExceptionGroup` u yakalar " +"ancak :exc:`BaseExceptionGroup` u yakalayamaz." #: library/exceptions.rst:922 msgid "" "The :exc:`BaseExceptionGroup` constructor returns an :exc:`ExceptionGroup` " -"rather than a :exc:`BaseExceptionGroup` if all contained exceptions are :exc:" -"`Exception` instances, so it can be used to make the selection automatic. " -"The :exc:`ExceptionGroup` constructor, on the other hand, raises a :exc:" -"`TypeError` if any contained exception is not an :exc:`Exception` subclass." -msgstr "" -"İçerdiği tüm istisnalar :exc:`Exception` örneğiyse, :exc:" -"`BaseExceptionGroup` yapıcısı bir :exc:`BaseExceptionGroup` yerine bir :exc:" -"`ExceptionGroup` döndürür, böylece seçimi otomatik hale getirmek için " -"kullanılabilir. Öte yandan, :exc:`ExceptionGroup` kurucusu, içerdiği " -"herhangi bir istisna bir :exc:`Exception` alt sınıfı değilse bir :exc:" -"`TypeError` yükseltir." +"rather than a :exc:`BaseExceptionGroup` if all contained exceptions " +"are :exc:`Exception` instances, so it can be used to make the selection " +"automatic. The :exc:`ExceptionGroup` constructor, on the other hand, raises " +"a :exc:`TypeError` if any contained exception is not an :exc:`Exception` " +"subclass." +msgstr "" +"İçerdiği tüm istisnalar :exc:`Exception` " +"örneğiyse, :exc:`BaseExceptionGroup` yapıcısı bir :exc:`BaseExceptionGroup` " +"yerine bir :exc:`ExceptionGroup` döndürür, böylece seçimi otomatik hale " +"getirmek için kullanılabilir. Öte yandan, :exc:`ExceptionGroup` kurucusu, " +"içerdiği herhangi bir istisna bir :exc:`Exception` alt sınıfı değilse " +"bir :exc:`TypeError` yükseltir." #: library/exceptions.rst:931 msgid "The ``msg`` argument to the constructor. This is a read-only attribute." @@ -1505,16 +1518,15 @@ msgstr "" #: library/exceptions.rst:948 msgid "" "The nesting structure of the current exception is preserved in the result, " -"as are the values of its :attr:`message`, :attr:`~BaseException." -"__traceback__`, :attr:`~BaseException.__cause__`, :attr:`~BaseException." -"__context__` and :attr:`~BaseException.__notes__` fields. Empty nested " -"groups are omitted from the result." +"as are the values of " +"its :attr:`message`, :attr:`~BaseException.__traceback__`, :attr:`~BaseException.__cause__`, :attr:`~BaseException.__context__` " +"and :attr:`~BaseException.__notes__` fields. Empty nested groups are omitted " +"from the result." msgstr "" -"Mevcut istisna içindeki iç içe geçme yapısı sonuçta korunur, ayrıca :attr:" -"`message`, :attr:`~BaseException.__traceback__`, :attr:`~BaseException." -"__cause__`, :attr:`~BaseException.__context__` ve :attr:`~BaseException." -"__notes__` alanlarının değerleri de korunur. Boş iç içe gruplar sonuçtan " -"çıkarılır." +"Mevcut istisna içindeki iç içe geçme yapısı sonuçta korunur, " +"ayrıca :attr:`message`, :attr:`~BaseException.__traceback__`, :attr:`~BaseException.__cause__`, :attr:`~BaseException.__context__` " +"ve :attr:`~BaseException.__notes__` alanlarının değerleri de korunur. Boş iç " +"içe gruplar sonuçtan çıkarılır." #: library/exceptions.rst:955 msgid "" @@ -1558,17 +1570,17 @@ msgstr "" #: library/exceptions.rst:976 msgid "" -":meth:`subgroup` and :meth:`split` copy the :attr:`~BaseException." -"__traceback__`, :attr:`~BaseException.__cause__`, :attr:`~BaseException." -"__context__` and :attr:`~BaseException.__notes__` fields from the original " -"exception group to the one returned by :meth:`derive`, so these fields do " -"not need to be updated by :meth:`derive`." +":meth:`subgroup` and :meth:`split` copy " +"the :attr:`~BaseException.__traceback__`, :attr:`~BaseException.__cause__`, :attr:`~BaseException.__context__` " +"and :attr:`~BaseException.__notes__` fields from the original exception " +"group to the one returned by :meth:`derive`, so these fields do not need to " +"be updated by :meth:`derive`." msgstr "" -":meth:`subgroup` ve :meth:`split`, :attr:`~BaseException.__traceback__`, :" -"attr:`~BaseException.__cause__`, :attr:`~BaseException.__context__` ve :attr:" -"`~BaseException.__notes__` alanlarını orijinal istisna grubundan :meth:" -"`derive` tarafından döndürülene kopyalar, böylece bu alanların :meth:" -"`derive` tarafından güncellenmesi gerekmez." +":meth:`subgroup` " +"ve :meth:`split`, :attr:`~BaseException.__traceback__`, :attr:`~BaseException.__cause__`, :attr:`~BaseException.__context__` " +"ve :attr:`~BaseException.__notes__` alanlarını orijinal istisna " +"grubundan :meth:`derive` tarafından döndürülene kopyalar, böylece bu " +"alanların :meth:`derive` tarafından güncellenmesi gerekmez." #: library/exceptions.rst:983 msgid "" @@ -1628,11 +1640,11 @@ msgstr "" #: library/exceptions.rst:1024 msgid "" "Like :exc:`ExceptionGroup`, any subclass of :exc:`BaseExceptionGroup` which " -"is also a subclass of :exc:`Exception` can only wrap instances of :exc:" -"`Exception`." +"is also a subclass of :exc:`Exception` can only wrap instances " +"of :exc:`Exception`." msgstr "" -"Tıpkı :exc:`ExceptionGroup` gibi, :exc:`BaseExceptionGroup` alt sınıfı olan :" -"exc:`Exception` alt sınıfı da yalnızca :exc:`Exception` örneklerini " +"Tıpkı :exc:`ExceptionGroup` gibi, :exc:`BaseExceptionGroup` alt sınıfı " +"olan :exc:`Exception` alt sınıfı da yalnızca :exc:`Exception` örneklerini " "sarabilir." #: library/exceptions.rst:1032 diff --git a/library/faulthandler.po b/library/faulthandler.po index 19402fc2b..057968361 100644 --- a/library/faulthandler.po +++ b/library/faulthandler.po @@ -23,10 +23,10 @@ msgstr "" #: 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:`~signal.SIGSEGV`, :const:" -"`~signal.SIGFPE`, :const:`~signal.SIGABRT`, :const:`~signal.SIGBUS`, and :" -"const:`~signal.SIGILL` signals. You can also enable them at startup by " +"fault, after a timeout, or on a user signal. " +"Call :func:`faulthandler.enable` to install fault handlers for " +"the :const:`~signal.SIGSEGV`, :const:`~signal.SIGFPE`, :const:`~signal.SIGABRT`, :const:`~signal.SIGBUS`, " +"and :const:`~signal.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 "" @@ -86,8 +86,8 @@ msgstr "" #: library/faulthandler.rst:44 msgid "" -"The :ref:`Python Development Mode ` calls :func:`faulthandler." -"enable` at Python startup." +"The :ref:`Python Development Mode ` " +"calls :func:`faulthandler.enable` at Python startup." msgstr "" #: library/faulthandler.rst:49 @@ -133,17 +133,17 @@ msgstr "" #: library/faulthandler.rst:74 msgid "" -"Enable the fault handler: install handlers for the :const:`~signal." -"SIGSEGV`, :const:`~signal.SIGFPE`, :const:`~signal.SIGABRT`, :const:`~signal." -"SIGBUS` and :const:`~signal.SIGILL` signals to dump the Python traceback. If " +"Enable the fault handler: install handlers for " +"the :const:`~signal.SIGSEGV`, :const:`~signal.SIGFPE`, :const:`~signal.SIGABRT`, :const:`~signal.SIGBUS` " +"and :const:`~signal.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 "" #: library/faulthandler.rst:81 msgid "" -"The *file* must be kept open until the fault handler is disabled: see :ref:" -"`issue with file descriptors `." +"The *file* must be kept open until the fault handler is disabled: " +"see :ref:`issue with file descriptors `." msgstr "" #: library/faulthandler.rst:87 @@ -158,8 +158,8 @@ msgstr "" #: library/faulthandler.rst:96 msgid "" -"Disable the fault handler: uninstall the signal handlers installed by :func:" -"`enable`." +"Disable the fault handler: uninstall the signal handlers installed " +"by :func:`enable`." msgstr "" #: library/faulthandler.rst:101 @@ -174,17 +174,17 @@ msgstr "" 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." +"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 "" #: library/faulthandler.rst:117 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 " +"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 "" @@ -213,8 +213,9 @@ msgstr "" #: library/faulthandler.rst:143 msgid "" -"The *file* must be kept open until the signal is unregistered by :func:" -"`unregister`: see :ref:`issue with file descriptors `." +"The *file* must be kept open until the signal is unregistered " +"by :func:`unregister`: see :ref:`issue with file descriptors `." msgstr "" #: library/faulthandler.rst:157 diff --git a/library/fcntl.po b/library/fcntl.po index b18aa2b32..c4b5fec29 100644 --- a/library/fcntl.po +++ b/library/fcntl.po @@ -23,8 +23,8 @@ msgstr "" #: library/fcntl.rst:16 msgid "" "This module performs file and I/O control on file descriptors. It is an " -"interface to the :c:func:`fcntl` and :c:func:`ioctl` Unix routines. See the :" -"manpage:`fcntl(2)` and :manpage:`ioctl(2)` Unix manual pages for full " +"interface to the :c:func:`fcntl` and :c:func:`ioctl` Unix routines. See " +"the :manpage:`fcntl(2)` and :manpage:`ioctl(2)` Unix manual pages for full " "details." msgstr "" @@ -35,10 +35,10 @@ msgstr "" #: library/fcntl.rst:23 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." +"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 "" #: library/fcntl.rst:29 @@ -94,17 +94,18 @@ msgid "" "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." +"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 "" #: library/fcntl.rst:83 @@ -220,9 +221,9 @@ msgstr "" #: library/fcntl.rst:153 msgid "" "This is essentially a wrapper around the :func:`~fcntl.fcntl` locking calls. " -"*fd* is the file descriptor (file objects providing a :meth:`~io.IOBase." -"fileno` method are accepted as well) of the file to lock or unlock, and " -"*cmd* is one of the following values:" +"*fd* is the file descriptor (file objects providing " +"a :meth:`~io.IOBase.fileno` method are accepted as well) of the file to lock " +"or unlock, and *cmd* is one of the following values:" msgstr "" #: library/fcntl.rst:160 @@ -245,19 +246,19 @@ msgstr "" #: library/fcntl.rst:175 msgid "" -"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:`~errno.EACCES` or :const:`~errno.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." +"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:`~errno.EACCES` or :const:`~errno.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 "" #: library/fcntl.rst:182 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:" +"the lock starts, relative to *whence*, and *whence* is as " +"with :func:`io.IOBase.seek`, specifically:" msgstr "" #: library/fcntl.rst:186 diff --git a/library/filecmp.po b/library/filecmp.po index 0154f2b14..c8661e2bb 100644 --- a/library/filecmp.po +++ b/library/filecmp.po @@ -85,8 +85,8 @@ msgstr "" #: library/filecmp.rst:51 msgid "" -"The *shallow* parameter has the same meaning and default value as for :func:" -"`filecmp.cmp`." +"The *shallow* parameter has the same meaning and default value as " +"for :func:`filecmp.cmp`." msgstr "" #: library/filecmp.rst:54 @@ -110,9 +110,9 @@ msgstr "" #: library/filecmp.rst:75 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 :const:" -"`filecmp.DEFAULT_IGNORES`. *hide* is a list of names to hide, and defaults " -"to ``[os.curdir, os.pardir]``." +"and *b*. *ignore* is a list of names to ignore, and defaults " +"to :const:`filecmp.DEFAULT_IGNORES`. *hide* is a list of names to hide, and " +"defaults to ``[os.curdir, os.pardir]``." msgstr "" #: library/filecmp.rst:80 diff --git a/library/fileinput.po b/library/fileinput.po index f24cb502f..73df1a19c 100644 --- a/library/fileinput.po +++ b/library/fileinput.po @@ -55,9 +55,9 @@ msgstr "" #: library/fileinput.rst:30 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." +"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 "" #: library/fileinput.rst:35 @@ -109,9 +109,9 @@ msgstr "" #: library/fileinput.rst:66 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::" +"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 "" #: library/fileinput.rst:70 @@ -136,8 +136,9 @@ msgstr "" #: library/fileinput.rst:84 msgid "" -"The following functions use the global state created by :func:`fileinput." -"input`; if there is no active state, :exc:`RuntimeError` is raised." +"The following functions use the global state created " +"by :func:`fileinput.input`; if there is no active state, :exc:`RuntimeError` " +"is raised." msgstr "" #: library/fileinput.rst:90 @@ -201,14 +202,13 @@ msgstr "" #: library/fileinput.rst:146 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 " -"is :term:`iterable` and has a :meth:`~io.TextIOBase.readline` method which " -"returns the next input line. The sequence must be accessed in strictly " -"sequential order; random access and :meth:`~io.TextIOBase.readline` cannot " -"be mixed." +"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 is :term:`iterable` and has " +"a :meth:`~io.TextIOBase.readline` method which returns the next input line. " +"The sequence must be accessed in strictly sequential order; random access " +"and :meth:`~io.TextIOBase.readline` cannot be mixed." msgstr "" #: library/fileinput.rst:154 @@ -232,9 +232,9 @@ msgstr "" #: library/fileinput.rst:163 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::" +"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 "" #: library/fileinput.rst:167 @@ -287,8 +287,8 @@ msgstr "" #: library/fileinput.rst:208 msgid "" -"Usage example: ``fi = fileinput.FileInput(openhook=fileinput." -"hook_compressed, encoding=\"utf-8\")``" +"Usage example: ``fi = " +"fileinput.FileInput(openhook=fileinput.hook_compressed, encoding=\"utf-8\")``" msgstr "" #: library/fileinput.rst:216 @@ -299,8 +299,9 @@ msgstr "" #: library/fileinput.rst:219 msgid "" -"Usage example: ``fi = fileinput.FileInput(openhook=fileinput." -"hook_encoded(\"utf-8\", \"surrogateescape\"))``" +"Usage example: ``fi = " +"fileinput.FileInput(openhook=fileinput.hook_encoded(\"utf-8\", " +"\"surrogateescape\"))``" msgstr "" #: library/fileinput.rst:223 @@ -309,6 +310,6 @@ msgstr "" #: library/fileinput.rst:226 msgid "" -"This function is deprecated since :func:`fileinput.input` and :class:" -"`FileInput` now have *encoding* and *errors* parameters." +"This function is deprecated since :func:`fileinput.input` " +"and :class:`FileInput` now have *encoding* and *errors* parameters." msgstr "" diff --git a/library/fnmatch.po b/library/fnmatch.po index a638d06db..abc8adacd 100644 --- a/library/fnmatch.po +++ b/library/fnmatch.po @@ -80,25 +80,25 @@ msgstr "" #: library/fnmatch.rst:43 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:`.filter` to match pathname segments). Similarly, filenames starting " -"with a period are not special for this module, and are matched by the ``*`` " -"and ``?`` patterns." +"module. See module :mod:`glob` for pathname expansion (:mod:`glob` " +"uses :func:`.filter` to match pathname segments). Similarly, filenames " +"starting with a period are not special for this module, and are matched by " +"the ``*`` and ``?`` patterns." msgstr "" #: library/fnmatch.rst:49 msgid "" "Also note that :func:`functools.lru_cache` with the *maxsize* of 32768 is " -"used to cache the compiled regex patterns in the following functions: :func:" -"`fnmatch`, :func:`fnmatchcase`, :func:`.filter`." +"used to cache the compiled regex patterns in the following " +"functions: :func:`fnmatch`, :func:`fnmatchcase`, :func:`.filter`." msgstr "" #: library/fnmatch.rst:55 msgid "" "Test whether the filename string *name* matches the pattern string *pat*, " -"returning ``True`` or ``False``. Both parameters are case-normalized using :" -"func:`os.path.normcase`. :func:`fnmatchcase` can be used to perform a case-" -"sensitive comparison, regardless of whether that's standard for the " +"returning ``True`` or ``False``. Both parameters are case-normalized " +"using :func:`os.path.normcase`. :func:`fnmatchcase` can be used to perform a " +"case-sensitive comparison, regardless of whether that's standard for the " "operating system." msgstr "" diff --git a/library/fractions.po b/library/fractions.po index 5789a26c8..d267800e3 100644 --- a/library/fractions.po +++ b/library/fractions.po @@ -41,13 +41,13 @@ msgid "" "of :class:`numbers.Rational` and returns a new :class:`Fraction` instance " "with value ``numerator/denominator``. If *denominator* is ``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 " +"*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::" @@ -62,10 +62,10 @@ msgid "" "where the optional ``sign`` may be either '+' or '-' and ``numerator`` and " "``denominator`` (if present) are strings of decimal digits (underscores may " "be used to delimit digits as with integral literals in code). 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::" +"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 "" #: library/fractions.rst:52 @@ -98,17 +98,17 @@ msgstr "" #: library/fractions.rst:78 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 :term:`hashable`, and should be " -"treated as immutable. In addition, :class:`Fraction` has the following " -"properties and methods:" +"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 :term:`hashable`, and should be treated as immutable. In " +"addition, :class:`Fraction` has the following properties and methods:" msgstr "" #: library/fractions.rst:84 msgid "" -"The :class:`Fraction` constructor now accepts :class:`float` and :class:" -"`decimal.Decimal` instances." +"The :class:`Fraction` constructor now accepts :class:`float` " +"and :class:`decimal.Decimal` instances." msgstr "" #: library/fractions.rst:88 @@ -126,8 +126,8 @@ msgstr "" #: library/fractions.rst:97 msgid "" -":class:`Fraction` implements ``__int__`` now to satisfy ``typing." -"SupportsInt`` instance checks." +":class:`Fraction` implements ``__int__`` now to satisfy " +"``typing.SupportsInt`` instance checks." msgstr "" #: library/fractions.rst:101 @@ -162,9 +162,9 @@ msgstr "" #: library/fractions.rst:134 msgid "" -"Alternative constructor which only accepts instances of :class:`float` or :" -"class:`numbers.Integral`. Beware that ``Fraction.from_float(0.3)`` is not " -"the same value as ``Fraction(3, 10)``." +"Alternative constructor which only accepts instances of :class:`float` " +"or :class:`numbers.Integral`. Beware that ``Fraction.from_float(0.3)`` is " +"not the same value as ``Fraction(3, 10)``." msgstr "" #: library/fractions.rst:140 @@ -175,8 +175,8 @@ msgstr "" #: library/fractions.rst:146 msgid "" -"Alternative constructor which only accepts instances of :class:`decimal." -"Decimal` or :class:`numbers.Integral`." +"Alternative constructor which only accepts instances " +"of :class:`decimal.Decimal` or :class:`numbers.Integral`." msgstr "" #: library/fractions.rst:151 @@ -213,19 +213,19 @@ 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." +"rounding half toward even. This method can also be accessed through " +"the :func:`round` function." msgstr "" #: library/fractions.rst:204 msgid "" "Provides support for float-style formatting of :class:`Fraction` instances " -"via the :meth:`str.format` method, the :func:`format` built-in function, or :" -"ref:`Formatted string literals `. The presentation types " +"via the :meth:`str.format` method, the :func:`format` built-in function, " +"or :ref:`Formatted string literals `. The presentation types " "``\"e\"``, ``\"E\"``, ``\"f\"``, ``\"F\"``, ``\"g\"``, ``\"G\"`` and ``\"%" -"\"`` are supported. For these presentation types, formatting for a :class:" -"`Fraction` object ``x`` follows the rules outlined for the :class:`float` " -"type in the :ref:`formatspec` section." +"\"`` are supported. For these presentation types, formatting for " +"a :class:`Fraction` object ``x`` follows the rules outlined for " +"the :class:`float` type in the :ref:`formatspec` section." msgstr "" #: library/fractions.rst:212 diff --git a/library/ftplib.po b/library/ftplib.po index 5ce318550..c786a96cd 100644 --- a/library/ftplib.po +++ b/library/ftplib.po @@ -26,12 +26,12 @@ msgstr "" #: 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`." +"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 "" #: library/ftplib.rst:22 @@ -139,8 +139,8 @@ msgstr "" #: library/ftplib.rst:505 msgid "" -"If the *timeout* parameter is set to be zero, it will raise a :class:" -"`ValueError` to prevent the creation of a non-blocking socket. The " +"If the *timeout* parameter is set to be zero, it will raise " +"a :class:`ValueError` to prevent the creation of a non-blocking socket. The " "*encoding* parameter was added, and the default was changed from Latin-1 to " "UTF-8 to follow :rfc:`2640`." msgstr "" @@ -309,9 +309,9 @@ msgstr "" #: library/ftplib.rst:292 msgid "" -"A file object (opened in binary mode) which is read until EOF, using its :" -"meth:`~io.RawIOBase.read` method in blocks of size *blocksize* to provide " -"the data to be stored." +"A file object (opened in binary mode) which is read until EOF, using " +"its :meth:`~io.RawIOBase.read` method in blocks of size *blocksize* to " +"provide the data to be stored." msgstr "" #: library/ftplib.rst:298 @@ -369,14 +369,14 @@ msgstr "" #: library/ftplib.rst:354 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." +"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 "" #: library/ftplib.rst:368 @@ -460,15 +460,15 @@ msgstr "" #: library/ftplib.rst:452 msgid "" -"An :class:`FTP` subclass which adds TLS support to FTP as described in :rfc:" -"`4217`. Connect to port 21 implicitly securing the FTP control connection " -"before authenticating." +"An :class:`FTP` subclass which adds TLS support to FTP as described " +"in :rfc:`4217`. Connect to port 21 implicitly securing the FTP control " +"connection before authenticating." msgstr "" #: library/ftplib.rst:458 msgid "" -"The user must explicitly secure the data connection by calling the :meth:" -"`prot_p` method." +"The user must explicitly secure the data connection by calling " +"the :meth:`prot_p` method." msgstr "" #: library/ftplib.rst:476 @@ -490,8 +490,9 @@ msgstr "" #: library/ftplib.rst:500 msgid "" -"The class now supports hostname check with :attr:`ssl.SSLContext." -"check_hostname` and *Server Name Indication* (see :const:`ssl.HAS_SNI`)." +"The class now supports hostname check " +"with :attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* " +"(see :const:`ssl.HAS_SNI`)." msgstr "" #: library/ftplib.rst:511 @@ -537,8 +538,9 @@ msgstr "" #: library/ftplib.rst:536 msgid "" -"The method now supports hostname check with :attr:`ssl.SSLContext." -"check_hostname` and *Server Name Indication* (see :const:`ssl.HAS_SNI`)." +"The method now supports hostname check " +"with :attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* " +"(see :const:`ssl.HAS_SNI`)." msgstr "" #: library/ftplib.rst:543 diff --git a/library/functions.po b/library/functions.po index 74464a713..69e574e81 100644 --- a/library/functions.po +++ b/library/functions.po @@ -458,10 +458,10 @@ msgid "" "iterator. If *default* is given, it is returned if the iterator is " "exhausted, otherwise :exc:`StopAsyncIteration` is raised." msgstr "" -"Bu *async_iterator* 'ın :meth:`~object.__anext__` metodunu çağırır. Bir :" -"term:`awaitable` döndürür. Bunu beklemek yineleyicinin bir sonraki değerini " -"döndürür. Eğer *default* değer verildiyse, yineleyici tükendiğinde o " -"döndürülür. Aksi takdirde :exc:`StopAsyncIteration` hatası ortaya çıkar." +"Bu *async_iterator* 'ın :meth:`~object.__anext__` metodunu çağırır. " +"Bir :term:`awaitable` döndürür. Bunu beklemek yineleyicinin bir sonraki " +"değerini döndürür. Eğer *default* değer verildiyse, yineleyici tükendiğinde " +"o döndürülür. Aksi takdirde :exc:`StopAsyncIteration` hatası ortaya çıkar." #: library/functions.rst:104 msgid "" @@ -483,9 +483,9 @@ msgstr "" #: library/functions.rst:116 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." +"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 "" ":func:`repr` 'in bir nesnenin yazdırılabilir temsilini içeren bir dize " "döndürdüğü, ancak :func:`repr` tarafından döndürülen dizedeki ASCII olmayan " @@ -524,9 +524,9 @@ msgid "" "Return a Boolean value, i.e. one of ``True`` or ``False``. The argument is " "converted using the standard :ref:`truth testing procedure `. If the " "argument 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:`typebool`)." +"``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:`typebool`)." msgstr "" "``True`` ya da ``False`` değeri döndürür. *x*, standart :ref:`truth testing " "procedure ` kullanılarak boolean veri tipine dönüştürülür. *x* " @@ -559,16 +559,16 @@ msgstr "" "beklemeden :func:`pdb.set_trace()` fonksiyonunu çağırır. Bu durumda, bu " "tamamen size kolaylık sağlamak içindir, bu nedenle hata ayıklayıcıya girmek " "için :mod:`pdb` 'yi içe aktarmanız veya fazla kod yazmanız gerekmez. Buna " -"rağmen, :func:`sys.breakpointhook` başka bir fonksiyona ayarlanabilir ve :" -"func:`breakpoint` otomatik olarak bunu çağırır ve tercih ettiğiniz hata " +"rağmen, :func:`sys.breakpointhook` başka bir fonksiyona ayarlanabilir " +"ve :func:`breakpoint` otomatik olarak bunu çağırır ve tercih ettiğiniz hata " "ayıklayıcıya girmenize izin verir. Eğer :func:`sys.breakpointhook` " "ulaşılabilir değilse, bu fonksiyon :exc:`RuntimeError` hatasını verecektir." #: library/functions.rst:173 msgid "" -"By default, the behavior of :func:`breakpoint` can be changed with the :" -"envvar:`PYTHONBREAKPOINT` environment variable. See :func:`sys." -"breakpointhook` for usage details." +"By default, the behavior of :func:`breakpoint` can be changed with " +"the :envvar:`PYTHONBREAKPOINT` environment variable. " +"See :func:`sys.breakpointhook` for usage details." msgstr "" #: library/functions.rst:177 @@ -594,10 +594,10 @@ msgid "" "as most methods that the :class:`bytes` type has, see :ref:`bytes-methods`." msgstr "" "Baytlardan oluşan yeni bir dizi döndürür. :class:`bytearray` sınıfı 0 <= x < " -"256 aralığındaki tam sayılardan oluşan değişebilir bir dizedir. :ref:" -"`typesseq-mutable` 'da tarif edildiği gibi değişebilir dizeler klasik " -"metotlarının çoğuna sahiptir. :class:`bytes` tipinin sahip olduğu metotlar " -"için, :ref:`bytes-methods` 'a bakınız." +"256 aralığındaki tam sayılardan oluşan değişebilir bir " +"dizedir. :ref:`typesseq-mutable` 'da tarif edildiği gibi değişebilir dizeler " +"klasik metotlarının çoğuna sahiptir. :class:`bytes` tipinin sahip olduğu " +"metotlar için, :ref:`bytes-methods` 'a bakınız." #: library/functions.rst:195 msgid "" @@ -652,8 +652,8 @@ msgstr ":ref:`binaryseq` ve :ref:`typebytearray` 'a bakınız." #: library/functions.rst:222 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 " +"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 "" "``0 <= x < 256`` aralığındaki tam sayılardan oluşan değiştirilemez bir " @@ -681,18 +681,19 @@ msgstr "" #: library/functions.rst:236 #, fuzzy 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:`~object.__call__` method." +"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:`~object.__call__` method." msgstr "" -"Eğer *object* argümanı çağrılabilir ise, :const:`True` , değilse :const:" -"`False` döndürür. Eğer ``True`` döndürür ise, bir çağrının başarısız olması " -"hala mümkündür, ``False`` döndürdüğü takdirde, *object* çağrısı hiçbir zaman " -"başarılı olamaz. Sınıfların ve örneklerin (Sınıflarında :meth:`__call__` " -"metodu varsa) çağrılabilir olduğunu not edin. Bir sınıfı çağırmak sınıftan " -"türeyen yeni bir örnek döndürür." +"Eğer *object* argümanı çağrılabilir ise, :const:`True` , " +"değilse :const:`False` döndürür. Eğer ``True`` döndürür ise, bir çağrının " +"başarısız olması hala mümkündür, ``False`` döndürdüğü takdirde, *object* " +"çağrısı hiçbir zaman başarılı olamaz. Sınıfların ve örneklerin " +"(Sınıflarında :meth:`__call__` metodu varsa) çağrılabilir olduğunu not " +"edin. Bir sınıfı çağırmak sınıftan türeyen yeni bir örnek döndürür." #: library/functions.rst:242 msgid "" @@ -745,8 +746,8 @@ msgstr "" #: library/functions.rst:269 msgid "" -"The ``@classmethod`` form is a function :term:`decorator` -- see :ref:" -"`function` for details." +"The ``@classmethod`` form is a function :term:`decorator` -- " +"see :ref:`function` for details." msgstr "" "``@classmethod`` formu, bir :term:`decorator` fonksiyonudur. -- detaylar " "için :ref:`function` 'a bakınız." @@ -775,8 +776,8 @@ msgstr "" #: library/functions.rst:281 msgid "" -"Class methods can now wrap other :term:`descriptors ` such as :" -"func:`property`." +"Class methods can now wrap other :term:`descriptors ` such " +"as :func:`property`." msgstr "" "Sınıf metotları artık :func:`property` gibi diğer :term:`descriptors " "` 'ları sarmalayabilir." @@ -784,10 +785,10 @@ msgstr "" #: library/functions.rst:285 #, fuzzy msgid "" -"Class methods now inherit the method attributes (:attr:`~function." -"__module__`, :attr:`~function.__name__`, :attr:`~function.__qualname__`, :" -"attr:`~function.__doc__` and :attr:`~function.__annotations__`) and have a " -"new ``__wrapped__`` attribute." +"Class methods now inherit the method attributes " +"(:attr:`~function.__module__`, :attr:`~function.__name__`, :attr:`~function.__qualname__`, :attr:`~function.__doc__` " +"and :attr:`~function.__annotations__`) and have a new ``__wrapped__`` " +"attribute." msgstr "" "Sınıf metotları artık (``__module__``, ``__name__``, ``__qualname__``, " "``__doc__`` and ``__annotations__``) metot özelliklerini miras alır ve yeni " @@ -839,22 +840,22 @@ msgstr "" #: library/functions.rst:314 msgid "" -"The optional arguments *flags* and *dont_inherit* control which :ref:" -"`compiler options ` should be activated and which :ref:" -"`future features ` should be allowed. If neither is present (or both " -"are zero) the code is compiled with the same flags that affect the code that " -"is calling :func:`compile`. If the *flags* argument is given and " -"*dont_inherit* is not (or is zero) then the compiler options and 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 flags (future features and compiler options) " -"in the surrounding code are ignored." +"The optional arguments *flags* and *dont_inherit* control " +"which :ref:`compiler options ` should be activated and " +"which :ref:`future features ` should be allowed. If neither is " +"present (or both are zero) the code is compiled with the same flags that " +"affect the code that is calling :func:`compile`. If the *flags* argument is " +"given and *dont_inherit* is not (or is zero) then the compiler options and " +"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 flags (future features and compiler " +"options) in the surrounding code are ignored." msgstr "" "*flags* ve *dont_inherit* opsiyonel argümanları hangi :ref:`derleyici " -"seçenekleri ` 'ın aktive edilmesi gerektiğini ve hangi :" -"ref:`gelecekteki özellikler ` 'e izin verileceğini kontrol eder. " -"İkisi de verilmediyse (veya ikisi de sıfır ise) kod, :func:`compile` 'ı " -"çağıran kodu etkileyen aynı bayraklarla derlenir. Eğer *flags* argümanı " +"seçenekleri ` 'ın aktive edilmesi gerektiğini ve " +"hangi :ref:`gelecekteki özellikler ` 'e izin verileceğini kontrol " +"eder. İkisi de verilmediyse (veya ikisi de sıfır ise) kod, :func:`compile` " +"'ı çağıran kodu etkileyen aynı bayraklarla derlenir. Eğer *flags* argümanı " "verilip *dont_inherit* verilmediyse (veya sıfırsa), derleyici seçenekleri ve " "gelecek ifadeleri *flags* argümanı tarafından belirtilirler, her " "türlükullanılacak olanlara ek olarak kullanılır. Eğer *dont_inherit* " @@ -866,18 +867,19 @@ msgstr "" msgid "" "Compiler options and future statements are specified by bits which can be " "bitwise ORed together to specify multiple options. The bitfield required to " -"specify a given future feature can be found as the :attr:`~__future__." -"_Feature.compiler_flag` attribute on the :class:`~__future__._Feature` " -"instance in the :mod:`__future__` module. :ref:`Compiler flags ` can be found in :mod:`ast` module, with ``PyCF_`` prefix." +"specify a given future feature can be found as " +"the :attr:`~__future__._Feature.compiler_flag` attribute on " +"the :class:`~__future__._Feature` instance in the :mod:`__future__` " +"module. :ref:`Compiler flags ` can be found " +"in :mod:`ast` module, with ``PyCF_`` prefix." msgstr "" "Derleyici seçenekleri ve gelecek ifadeleri, birden fazla seçeneği belirlemek " "için bit düzeyinde VEYA'lanabilen bitler tarafından belirlenirler. " -"Gelecekteki belirli bir özelliği belirtmek için gereken bit alanı, :mod:" -"`__future__` modülündeki :class:`~__future__._Feature` örneğinde :attr:" -"`~__future__._Feature.compiler_flag` niteliği olarak bulunabilir. :ref:" -"`Derleyici bayrakları ` , :mod:`ast` modülünde ``PyCF_`` " -"öneki ile bulunabilir." +"Gelecekteki belirli bir özelliği belirtmek için gereken bit " +"alanı, :mod:`__future__` modülündeki :class:`~__future__._Feature` " +"örneğinde :attr:`~__future__._Feature.compiler_flag` niteliği olarak " +"bulunabilir. :ref:`Derleyici bayrakları ` , :mod:`ast` " +"modülünde ``PyCF_`` öneki ile bulunabilir." #: library/functions.rst:333 msgid "" @@ -903,8 +905,8 @@ msgstr "" #: library/functions.rst:342 msgid "" -"If you want to parse Python code into its AST representation, see :func:`ast." -"parse`." +"If you want to parse Python code into its AST representation, " +"see :func:`ast.parse`." msgstr "" "Python kodunu onun AST temsiline ayrıştırmak isterseniz, :func:`ast.parse` " "'a bakınız." @@ -923,12 +925,12 @@ msgstr "" 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." +"to facilitate detection of incomplete and complete statements in " +"the :mod:`code` module." msgstr "" "``'single'`` veya ``'eval'`` modunda çok satırlı bir dize derleneceğinde, " -"giren veri en az bir yeni satır karakteri ile sonlandırılmalıdır. Bu :mod:" -"`code` modülündeki tamamlanmış ve tamamlanmamış ifadelerin tespitini " +"giren veri en az bir yeni satır karakteri ile sonlandırılmalıdır. " +"Bu :mod:`code` modülündeki tamamlanmış ve tamamlanmamış ifadelerin tespitini " "kolaylaştırmak içindir." #: library/functions.rst:360 @@ -1007,9 +1009,9 @@ msgid "" "and ``')'``, which are ignored. The string must not contain whitespace " "between ``'+'``, ``'-'``, the ``'j'`` or ``'J'`` suffix, and the decimal " "number. For example, ``complex('1+2j')`` is fine, but ``complex('1 + 2j')`` " -"raises :exc:`ValueError`. More precisely, the input must conform to the :" -"token:`~float:complexvalue` production rule in the following grammar, after " -"parentheses and leading and trailing whitespace characters are removed:" +"raises :exc:`ValueError`. More precisely, the input must conform to " +"the :token:`~float:complexvalue` production rule in the following grammar, " +"after parentheses and leading and trailing whitespace characters are removed:" msgstr "" #: library/functions.rst:424 @@ -1017,10 +1019,10 @@ msgstr "" msgid "" "If the argument is a number, the constructor serves as a numeric conversion " "like :class:`int` and :class:`float`. For a general Python object ``x``, " -"``complex(x)`` delegates to ``x.__complex__()``. If :meth:`~object." -"__complex__` is not defined then it falls back to :meth:`~object.__float__`. " -"If :meth:`!__float__` is not defined then it falls back to :meth:`~object." -"__index__`." +"``complex(x)`` delegates to ``x.__complex__()``. " +"If :meth:`~object.__complex__` is not defined then it falls back " +"to :meth:`~object.__float__`. If :meth:`!__float__` is not defined then it " +"falls back to :meth:`~object.__index__`." msgstr "" "Genel bir python nesnesi ``x`` için, ``complex(x)`` , ``x.__complex__()`` 'i " "temsil eder. Eğer ``__complex__()`` tanımlanmadıysa, :meth:`__float__` 'a " @@ -1054,11 +1056,11 @@ msgstr "" #: library/functions.rst:450 #, fuzzy msgid "" -"Falls back to :meth:`~object.__index__` if :meth:`~object.__complex__` and :" -"meth:`~object.__float__` are not defined." +"Falls back to :meth:`~object.__index__` if :meth:`~object.__complex__` " +"and :meth:`~object.__float__` are not defined." msgstr "" -"Eğer :meth:`__complex__` ve :meth:`__float__` tanımlanmadıysa, :meth:" -"`__index__` 'e geri döner." +"Eğer :meth:`__complex__` ve :meth:`__float__` " +"tanımlanmadıysa, :meth:`__index__` 'e geri döner." #: library/functions.rst:457 msgid "" @@ -1072,8 +1074,8 @@ msgstr "" "dizedir. Dize nesnenin özelliklerinden birinin adı olmak zorundadır. " "Fonksiyon nesnenin izin vermesi koşuluyla, dizede belirtilen bu özelliği " "siler. Örnek olarak, ``delattr(x, 'foobar')`` , ``del x.foobar`` 'a eş " -"değerdir. *name* bir Python tanımlayıcısı olmak zorunda değildir (:func:" -"`setattr` bkz.)." +"değerdir. *name* bir Python tanımlayıcısı olmak zorunda değildir " +"(:func:`setattr` bkz.)." #: library/functions.rst:470 msgid "" @@ -1086,8 +1088,8 @@ msgstr "" #: library/functions.rst:473 msgid "" -"For other containers see the built-in :class:`list`, :class:`set`, and :" -"class:`tuple` classes, as well as the :mod:`collections` module." +"For other containers see the built-in :class:`list`, :class:`set`, " +"and :class:`tuple` classes, as well as the :mod:`collections` module." msgstr "" "Diğer konteynerler için dahili :class:`list` , :class:`set` , :class:`tuple` " "sınıfları ve :mod:`collections` modülüne bakınız." @@ -1107,13 +1109,13 @@ msgstr "" msgid "" "If the object has a method named :meth:`~object.__dir__`, this method will " "be called and must return the list of attributes. This allows objects that " -"implement a custom :func:`~object.__getattr__` or :func:`~object." -"__getattribute__` function to customize the way :func:`dir` reports their " -"attributes." +"implement a custom :func:`~object.__getattr__` " +"or :func:`~object.__getattribute__` function to customize the " +"way :func:`dir` reports their attributes." msgstr "" "Eğer nesne :meth:`__dir__` adında bir metoda sahipse, bu metot çağrılır ve " -"nesnenin özelliklerinin listesini döndürmelidir. Bu, özel bir :func:" -"`__getattr__` veya :func:`__getattribute__` fonksiyonunu uygulayan " +"nesnenin özelliklerinin listesini döndürmelidir. Bu, özel " +"bir :func:`__getattr__` veya :func:`__getattribute__` fonksiyonunu uygulayan " "nesnelerin, :func:`dir` 'in özellikleri bildirme şeklini özelleştirmesine " "izin verir." @@ -1123,13 +1125,13 @@ msgid "" "If the object does not provide :meth:`~object.__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:`~object.__getattr__`." +"necessarily complete and may be inaccurate when the object has a " +"custom :func:`~object.__getattr__`." msgstr "" -"Eğer nesne :meth:`__dir__` metodu sağlamıyorsa, fonksiyon nesnenin :attr:" -"`~object.__dict__` özelliğinden veri toplamak için elinen gelenin en iyisini " -"dener. Sonuç listesinin tamamlanmış olmasına gerek yoktur ve nesnenin özel " -"bir :func:`__getattr__` fonksiyonu varsa kusurlu olabilir." +"Eğer nesne :meth:`__dir__` metodu sağlamıyorsa, fonksiyon " +"nesnenin :attr:`~object.__dict__` özelliğinden veri toplamak için elinen " +"gelenin en iyisini dener. Sonuç listesinin tamamlanmış olmasına gerek yoktur " +"ve nesnenin özel bir :func:`__getattr__` fonksiyonu varsa kusurlu olabilir." #: library/functions.rst:496 msgid "" @@ -1190,10 +1192,10 @@ msgid "" "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)``." +"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 "" "Argüman olarak iki (karmaşık olmayan) sayı alır ve bölme işlemi yapılırken " "bu argümanların bölümleri ve kalanlarından oluşan bir sayı çifti döndürür. " @@ -1206,16 +1208,16 @@ msgstr "" #: library/functions.rst:552 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*." +"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 "" "Bir numaralandırma nesnesi döndürür. *iterable* bir dize, :term:`iterator` " -"veya tekrarlamayı destekleyen başka bir nesne olmalıdır. Yineleyicinin by :" -"func:`enumerate` tarafından döndürülen :meth:`~iterator.__next__` metodu bir " -"sayıyı (varsayılan olarak 0 olan *start* 'dan) ve *iterable* üzerinde " +"veya tekrarlamayı destekleyen başka bir nesne olmalıdır. Yineleyicinin " +"by :func:`enumerate` tarafından döndürülen :meth:`~iterator.__next__` metodu " +"bir sayıyı (varsayılan olarak 0 olan *start* 'dan) ve *iterable* üzerinde " "yinelemeden elde edilen değerleri içeren bir demet döndürür." #: library/functions.rst:564 @@ -1278,12 +1280,13 @@ msgid "" "reference to the dictionary of the built-in module :mod:`builtins` is " "inserted under that key before *expression* is parsed. 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:" -"`eval`. If the *locals* dictionary is omitted it defaults to the *globals* " -"dictionary. If both dictionaries are omitted, the expression is executed " -"with the *globals* and *locals* in the environment where :func:`eval` is " -"called. Note, *eval()* does not have access to the :term:`nested scopes " -"` (non-locals) in the enclosing environment." +"own ``__builtins__`` dictionary into *globals* before passing it " +"to :func:`eval`. If the *locals* dictionary is omitted it defaults to the " +"*globals* dictionary. If both dictionaries are omitted, the expression is " +"executed with the *globals* and *locals* in the environment " +"where :func:`eval` is called. Note, *eval()* does not have access to " +"the :term:`nested scopes ` (non-locals) in the enclosing " +"environment." msgstr "" "*expression* bağımsız değişkeni, genel ve yerel ad alanı olarak *globals* ve " "*locals* sözlükleri kullanılarak Python ifadesi (teknik olarak bir koşul " @@ -1362,20 +1365,21 @@ msgid "" "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 :ref:`file-input` in the Reference Manual). Be aware that the :" -"keyword:`nonlocal`, :keyword:`yield`, and :keyword:`return` 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``." +"the section :ref:`file-input` in the Reference Manual). Be aware that " +"the :keyword:`nonlocal`, :keyword:`yield`, and :keyword:`return` 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 "" "Bu fonksiyon Python kodunun dinamik çalıştırılmasını destekler. *object* bir " "kod objesi veya dize olmalıdır. Dize ise, dize daha sonra yürütülen bir " "Python ifadeleri paketi olarak ayrıştırılır (bir sözdizimi hatası " "olmadıkça). [#]_ eğer bir kod objesiyse, sadece çalıştırılır. Her durumda, " "çalıştırılacak kodun dosya girişi olarak geçerli olması beklenir (Referans " -"Kılavuzundaki :ref:`file-input` kısmına bakınız). :keyword:`nonlocal`, :" -"keyword:`yield`, ve :keyword:`return` ifadelerinin :func:`exec` fonksiyonuna " -"geçirilen kod kaynağında bile fonksiyonlar dışında kullanılamayacağını " -"unutmayınız. Döndürülen değer ``None`` 'dır." +"Kılavuzundaki :ref:`file-input` kısmına " +"bakınız). :keyword:`nonlocal`, :keyword:`yield`, ve :keyword:`return` " +"ifadelerinin :func:`exec` fonksiyonuna geçirilen kod kaynağında bile " +"fonksiyonlar dışında kullanılamayacağını unutmayınız. Döndürülen değer " +"``None`` 'dır." #: library/functions.rst:658 #, fuzzy @@ -1407,16 +1411,16 @@ msgstr "" #: library/functions.rst:672 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__``, 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 "" "Eğer *globals* sözlüğü ``__builtins__`` anahtarı için bir değer içermiyorsa, " "bu anahtarın altına bir referans yerleşik modül :mod:`builtins` 'in " -"sözlüğüne eklenir. Bu şekilde, kendi ``__builtins__`` sözlüğünüzü :func:" -"`exec` 'e geçirmeden önce *globals* içine ekleyerek yürütülen kod için hangi " -"yerleşiklerin mevcut olduğunu kontrol edebilirsiniz." +"sözlüğüne eklenir. Bu şekilde, kendi ``__builtins__`` " +"sözlüğünüzü :func:`exec` 'e geçirmeden önce *globals* içine ekleyerek " +"yürütülen kod için hangi yerleşiklerin mevcut olduğunu kontrol edebilirsiniz." #: library/functions.rst:678 msgid "" @@ -1547,19 +1551,19 @@ msgid "" "float, an :exc:`OverflowError` will be raised." msgstr "" "Aksi takdirde, argüman bir tam sayı veya reel sayıysa, aynı değerde reel " -"sayı döndürülür. Eğer argüman Python reel sayı aralığının dışındaysa, :exc:" -"`OverflowError` hatası ortaya çıkar." +"sayı döndürülür. Eğer argüman Python reel sayı aralığının " +"dışındaysa, :exc:`OverflowError` hatası ortaya çıkar." #: library/functions.rst:775 #, fuzzy msgid "" -"For a general Python object ``x``, ``float(x)`` delegates to ``x." -"__float__()``. If :meth:`~object.__float__` is not defined then it falls " -"back to :meth:`~object.__index__`." +"For a general Python object ``x``, ``float(x)`` delegates to " +"``x.__float__()``. If :meth:`~object.__float__` is not defined then it " +"falls back to :meth:`~object.__index__`." msgstr "" "Genel bir Python nesnesi ``x`` için, ``float(x)``, ``x.__float__()`` " -"fonksiyonuna delege eder. Eğer ``__float__()`` tanımlanmamışsa, :meth:" -"`__index__` 'e geri döner." +"fonksiyonuna delege eder. Eğer ``__float__()`` " +"tanımlanmamışsa, :meth:`__index__` 'e geri döner." #: library/functions.rst:779 msgid "If no argument is given, ``0.0`` is returned." @@ -1601,12 +1605,12 @@ msgstr "" #: library/functions.rst:807 #, fuzzy 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:`~object.__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." +"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:`~object.__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 "" "``format(value, format_spec)`` çağrısı, değerin :meth:`__format__` metodunu " "ararken örnek sözlüğü atlayan ``type(value).__format__(value, format_spec)`` " @@ -1619,28 +1623,30 @@ msgid "" "``object().__format__(format_spec)`` raises :exc:`TypeError` if " "*format_spec* is not an empty string." msgstr "" -"*format_spec* boş bir dize değilse, ``object().__format__(format_spec)``, :" -"exc:`TypeError` hatasını ortaya çıkartır." +"*format_spec* boş bir dize değilse, " +"``object().__format__(format_spec)``, :exc:`TypeError` hatasını ortaya " +"çıkartır." #: library/functions.rst:823 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." +"*iterable*. ``frozenset`` is a built-in class. See :class:`frozenset` " +"and :ref:`types-set` for documentation about this class." msgstr "" -"Opsiyonel olarak *iterable* öğesinden alınan öğelerle yeni bir :class:" -"`frozenset` nesnesi döndürür. ``frozenset`` yerleşik bir sınıftır. Bu sınıf " -"hakkında dokümantasyona ulaşmak için :class:`frozenset` ve :ref:`types-set` " -"'e bakınız." +"Opsiyonel olarak *iterable* öğesinden alınan öğelerle yeni " +"bir :class:`frozenset` nesnesi döndürür. ``frozenset`` yerleşik bir " +"sınıftır. Bu sınıf hakkında dokümantasyona ulaşmak için :class:`frozenset` " +"ve :ref:`types-set` 'e bakınız." #: library/functions.rst:827 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." +"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 "" -"Diğer konteynerler için, yerleşik :class:`set`, :class:`list`, :class:" -"`tuple`, ve :class:`dict` sınıflarına, ayrıca :mod:`collections` modülüne " -"bakabilirsiniz." +"Diğer konteynerler için, " +"yerleşik :class:`set`, :class:`list`, :class:`tuple`, ve :class:`dict` " +"sınıflarına, ayrıca :mod:`collections` modülüne bakabilirsiniz." #: library/functions.rst:835 msgid "" @@ -1656,15 +1662,15 @@ msgstr "" "ise, sonuç bu özelliğin değeri olur. Örnek olarak, ``getattr(x, 'foobar')``, " "``x.foobar`` 'a eşittir. Eğer isimlendirilmiş özellik objede bulunmuyorsa, " "*default* sağlanmışsa döndürülür, aksi takdirde :exc:`AttributeError` hatası " -"ortaya çıkar. *name* bir Python tanımlayıcısı olmak zorunda değildir (:func:" -"`setattr` bkz)." +"ortaya çıkar. *name* bir Python tanımlayıcısı olmak zorunda değildir " +"(:func:`setattr` bkz)." #: library/functions.rst:844 msgid "" "Since :ref:`private name mangling ` happens at " "compilation time, one must manually mangle a private attribute's (attributes " -"with two leading underscores) name in order to retrieve it with :func:" -"`getattr`." +"with two leading underscores) name in order to retrieve it " +"with :func:`getattr`." msgstr "" ":ref:`özel isim yönetimi ` derleme zamanında " "gerçekleştiğinden dolayı, :func:`getattr` ile almak için özel bir niteliğin " @@ -1708,8 +1714,9 @@ msgstr "" #: library/functions.rst:874 #, fuzzy msgid "" -"For objects with custom :meth:`~object.__hash__` methods, note that :func:" -"`hash` truncates the return value based on the bit width of the host machine." +"For objects with custom :meth:`~object.__hash__` methods, note " +"that :func:`hash` truncates the return value based on the bit width of the " +"host machine." msgstr "" ":meth:`__hash__` metodu olan nesneler için, :func:`hash` öğesinin ana " "makinenin bit genişliğine göre döndürdüğü değeri kestiğini unutmayın. " @@ -1763,8 +1770,8 @@ msgstr "" #, fuzzy msgid "" "Convert an integer number to a lowercase hexadecimal string prefixed with " -"\"0x\". If *x* is not a Python :class:`int` object, it has to define an :" -"meth:`~object.__index__` method that returns an integer. Some examples:" +"\"0x\". If *x* is not a Python :class:`int` object, it has to define " +"an :meth:`~object.__index__` method that returns an integer. Some examples:" msgstr "" "Bir tam sayıyı küçük harflerden oluşan ve \"0x\" ile başlayan onaltılık bir " "dizeye dönüştürür. Eğer *x* Python :class:`int` nesnesi değilse, tam sayı " @@ -1789,11 +1796,11 @@ msgstr "" #: library/functions.rst:928 msgid "" -"To obtain a hexadecimal string representation for a float, use the :meth:" -"`float.hex` method." +"To obtain a hexadecimal string representation for a float, use " +"the :meth:`float.hex` method." msgstr "" -"Bir gerçel sayıdan onaltılık bir dize gösterimi elde etmek için :meth:`float." -"hex` metodunu kullanın." +"Bir gerçel sayıdan onaltılık bir dize gösterimi elde etmek " +"için :meth:`float.hex` metodunu kullanın." #: library/functions.rst:934 msgid "" @@ -1889,17 +1896,17 @@ msgstr "" #: library/functions.rst:994 #, fuzzy msgid "" -"If the argument defines :meth:`~object.__int__`, ``int(x)`` returns ``x." -"__int__()``. If the argument defines :meth:`~object.__index__`, it returns " -"``x.__index__()``. If the argument defines :meth:`~object.__trunc__`, it " -"returns ``x.__trunc__()``. For floating-point numbers, this truncates " -"towards zero." +"If the argument defines :meth:`~object.__int__`, ``int(x)`` returns " +"``x.__int__()``. If the argument defines :meth:`~object.__index__`, it " +"returns ``x.__index__()``. If the argument " +"defines :meth:`~object.__trunc__`, it returns ``x.__trunc__()``. For " +"floating-point numbers, this truncates towards zero." msgstr "" "Bir numara veya *x* dizesinden bir tam sayı oluşturur. Eğer argüman " -"verilmediyse 0 döndürür. *x* :meth:`__int__` 'i içeriyorsa, ``int(x)`` ``x." -"__int__()`` 'i döndürür. *x* :meth:`__index__` 'i içeriyorsa, ``x." -"__index__()`` 'i döndürür. *x* :meth:`__trunc__` 'ı içeriyorsa, ``x." -"__trunc__()`` 'ı döndürür. Gerçel sayılar için, sayı tam sayıya çevrilir." +"verilmediyse 0 döndürür. *x* :meth:`__int__` 'i içeriyorsa, ``int(x)`` " +"``x.__int__()`` 'i döndürür. *x* :meth:`__index__` 'i içeriyorsa, " +"``x.__index__()`` 'i döndürür. *x* :meth:`__trunc__` 'ı içeriyorsa, " +"``x.__trunc__()`` 'ı döndürür. Gerçel sayılar için, sayı tam sayıya çevrilir." #: library/functions.rst:1000 #, fuzzy @@ -1936,11 +1943,11 @@ msgstr "" "``Z``) ile temsil edilebilir. Varsayılan *taban* 10'dur. İzin verilen " "tabanlar 0 ve 2--36'dır. Taban-2, -8 ve -16 dizelerinin önüne isteğe bağlı " "olarak ``0b``/``0B``, ``0o``/``0O`` veya ``0x``/``0X`` eklenebilir, tıpkı " -"koddaki tamsayı değişmezlerinde olduğu gibi. Taban 0 için, dize :ref:" -"`koddaki tamsayı değişmezi ` 'ne benzer bir şekilde yorumlanır, " -"gerçek taban önek tarafından belirlenen 2, 8, 10 veya 16'dır. Taban 0 ayrıca " -"baştaki sıfırlara da izin vermez: ``int('010', 0)`` yasal değilken, " -"``int('010')`` ve ``int('010', 8)`` yasaldır." +"koddaki tamsayı değişmezlerinde olduğu gibi. Taban 0 için, " +"dize :ref:`koddaki tamsayı değişmezi ` 'ne benzer bir şekilde " +"yorumlanır, gerçek taban önek tarafından belirlenen 2, 8, 10 veya 16'dır. " +"Taban 0 ayrıca baştaki sıfırlara da izin vermez: ``int('010', 0)`` yasal " +"değilken, ``int('010')`` ve ``int('010', 8)`` yasaldır." #: library/functions.rst:1017 msgid "The integer type is described in :ref:`typesnumeric`." @@ -1948,15 +1955,16 @@ msgstr "Tam sayı tipi :ref:`typesnumeric` kısmında açıklandı." #: library/functions.rst:1019 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 " +"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 "" -"Eğer *base* bir :class:`int` örneği değilse ve *base* objesi :meth:`base." -"__index__ ` metoduna sahipse, bu metot, taban için bir " -"tamsayı elde etmek için çağrılır. Önceki sürümler :meth:`base.__index__ " -"` yerine :meth:`base.__int__ ` 'i kullandı." +"Eğer *base* bir :class:`int` örneği değilse ve *base* " +"objesi :meth:`base.__index__ ` metoduna sahipse, bu metot, " +"taban için bir tamsayı elde etmek için çağrılır. Önceki " +"sürümler :meth:`base.__index__ ` " +"yerine :meth:`base.__int__ ` 'i kullandı." #: library/functions.rst:1029 msgid "The first parameter is now positional-only." @@ -1980,16 +1988,16 @@ msgid "" ":class:`int` string inputs and string representations can be limited to help " "avoid denial of service attacks. A :exc:`ValueError` is raised when the " "limit is exceeded while converting a string to an :class:`int` or when " -"converting an :class:`int` into a string would exceed the limit. See the :" -"ref:`integer string conversion length limitation ` " +"converting an :class:`int` into a string would exceed the limit. See " +"the :ref:`integer string conversion length limitation ` " "documentation." msgstr "" ":class:`int` dizi girişleri ve dizi gösterimleri, hizmet reddi " -"saldırılarından (DOS) kaçınmaya yardımcı olmak için sınırlandırılabilir. :" -"exc:`ValueError`, bir *x* dizgesini :class:`int` 'e dönüştürürken sınır " -"aşıldığında veya :class:`int` 'i bir dizgeye dönüştürürken sınırı aştığında " -"ortaya çıkar. :ref:`tam sayı dönüştürme uzunluk sınırlaması " -"` dokümanına bakın." +"saldırılarından (DOS) kaçınmaya yardımcı olmak için " +"sınırlandırılabilir. :exc:`ValueError`, bir *x* dizgesini :class:`int` 'e " +"dönüştürürken sınır aşıldığında veya :class:`int` 'i bir dizgeye " +"dönüştürürken sınırı aştığında ortaya çıkar. :ref:`tam sayı dönüştürme " +"uzunluk sınırlaması ` dokümanına bakın." #: library/functions.rst:1048 msgid "" @@ -1999,9 +2007,9 @@ msgid "" "the function always returns ``False``. If *classinfo* is a tuple of type " "objects (or recursively, other such tuples) or a :ref:`types-union` of " "multiple types, 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. :exc:`TypeError` may not be raised for " -"an invalid type if an earlier check succeeds." +"types. If *classinfo* is not a type or tuple of types and such tuples, " +"a :exc:`TypeError` exception is raised. :exc:`TypeError` may not be raised " +"for an invalid type if an earlier check succeeds." msgstr "" "*object* argümanı, *classinfo* argümanının bir örneğiyse veya (doğrudan, " "dolaylı veya :term:`sanal `) alt sınıfının bir " @@ -2020,30 +2028,30 @@ msgstr "*classinfo* bir :ref:`types-union` olabilir." #: library/functions.rst:1065 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 (or " -"recursively, other such tuples) or a :ref:`types-union`, in which case " +"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 " +"(or recursively, other such tuples) or a :ref:`types-union`, in which case " "return ``True`` if *class* is a subclass of any entry in *classinfo*. In " "any other case, a :exc:`TypeError` exception is raised." msgstr "" -"Eğer *class*, *classinfo* 'nun bir alt sınıfıysa (doğrudan, dolaylı, veya :" -"term:`sanal `), ``True`` döndürür. Bir sınıf kendisinin " -"alt sınıfı olarak dikkate alınır. *classinfo* sınıf nesnelerinden oluşan bir " -"demet (veya tekrarlı diğer benzer demetler) veya :ref:`types-union` " -"olabilir, bu durumda eğer *class*, *classinfo* 'daki elemanlardan herhangi " -"birinin alt sınıfıysa ``True`` döndürülür. Diğer her durumda, :exc:" -"`TypeError` hatası ortaya çıkar." +"Eğer *class*, *classinfo* 'nun bir alt sınıfıysa (doğrudan, dolaylı, " +"veya :term:`sanal `), ``True`` döndürür. Bir sınıf " +"kendisinin alt sınıfı olarak dikkate alınır. *classinfo* sınıf nesnelerinden " +"oluşan bir demet (veya tekrarlı diğer benzer demetler) veya :ref:`types-" +"union` olabilir, bu durumda eğer *class*, *classinfo* 'daki elemanlardan " +"herhangi birinin alt sınıfıysa ``True`` döndürülür. Diğer her " +"durumda, :exc:`TypeError` hatası ortaya çıkar." #: library/functions.rst:1080 #, fuzzy 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 :" -"term:`iterable` protocol (the :meth:`~object.__iter__` method), or it must " -"support the sequence protocol (the :meth:`~object.__getitem__` method with " -"integer arguments starting at ``0``). If it does not support either of " +"second argument, *object* must be a collection object which supports " +"the :term:`iterable` protocol (the :meth:`~object.__iter__` method), or it " +"must support the sequence protocol (the :meth:`~object.__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 " @@ -2097,8 +2105,8 @@ msgstr "" #: library/functions.rst:1114 msgid "" -"``len`` raises :exc:`OverflowError` on lengths larger than :data:`sys." -"maxsize`, such as :class:`range(2 ** 100) `." +"``len`` raises :exc:`OverflowError` on lengths larger " +"than :data:`sys.maxsize`, such as :class:`range(2 ** 100) `." msgstr "" "``len``, :class:`range(2 ** 100) ` gibi :data:`sys.maxsize` 'dan daha " "geniş uzunluklar için :exc:`OverflowError` hatası ortaya çıkartır." @@ -2115,8 +2123,8 @@ msgstr "" 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. Note that at the module level, :func:" -"`locals` and :func:`globals` are the same dictionary." +"blocks, but not in class blocks. Note that at the module " +"level, :func:`locals` and :func:`globals` are the same dictionary." msgstr "" "Anlık yerel sembol tablosunu temsil eden bir sözlüğü günceller ve döndürür. " "Serbest değişkenler :func:`locals` fonksiyon bloklarında çağırıldığında onun " @@ -2147,8 +2155,8 @@ msgstr "" "o sayıda parametre almalı ve paralel bir şekilde tüm yinelenebilir " "nesnelerden tüm elementleri uygulamalıdır. Birden fazla yinelenebilir nesne " "ile, yineleyici en kısa yinelenebilir nesne tükendiğinde durur. Fonksiyon " -"girdilerinin zaten demetler halinde verildiği durumlar için, :func:" -"`itertools.starmap`\\ 'a bakın." +"girdilerinin zaten demetler halinde verildiği durumlar " +"için, :func:`itertools.starmap`\\ 'a bakın." #: library/functions.rst:1152 msgid "" @@ -2174,21 +2182,21 @@ 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." +"empty. If the iterable is empty and *default* is not provided, " +"a :exc:`ValueError` is raised." msgstr "" -"İki tane opsiyonel anahtar kelime parametresi vardır. *key* parametresi, :" -"meth:`list.sort` için kullanıldığı gibi bir parametre talep etme " -"fonksiyonunu belirtir. *varsayılan* parametre, sağlanan yineleyici boş ise " -"döndürülecek nesneyi belirtir. Eğer yineleyici boş ve *varsayılan* " +"İki tane opsiyonel anahtar kelime parametresi vardır. *key* " +"parametresi, :meth:`list.sort` için kullanıldığı gibi bir parametre talep " +"etme fonksiyonunu belirtir. *varsayılan* parametre, sağlanan yineleyici boş " +"ise döndürülecek nesneyi belirtir. Eğer yineleyici boş ve *varsayılan* " "verilmemiş ise, :exc:`ValueError` hatası ortaya çıkar." #: library/functions.rst:1166 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)``." +"such as ``sorted(iterable, key=keyfunc, reverse=True)[0]`` and " +"``heapq.nlargest(1, iterable, key=keyfunc)``." msgstr "" "Eğer birden fazla element en büyük ise, fonksiyon ilk rastlananı döndürür. " "bu ``sorted(iterable, key=keyfunc, reverse=True)[0]`` ve ``heapq.nlargest(1, " @@ -2206,8 +2214,8 @@ msgstr "*key* ``None`` olabilir." #: library/functions.rst:1182 msgid "" -"Return a \"memory view\" object created from the given argument. See :ref:" -"`typememoryview` for more information." +"Return a \"memory view\" object created from the given argument. " +"See :ref:`typememoryview` for more information." msgstr "" "Verilen argümandan oluşturulan bir \"memory view\" objesi döndürür. Daha " "fazla bilgi için :ref:`typememoryview` bkz." @@ -2244,9 +2252,10 @@ msgstr "" #: library/functions.rst:1219 msgid "" -"Retrieve the next item from the :term:`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." +"Retrieve the next item from the :term:`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 "" ":term:`iterator` 'ın :meth:`~iterator.__next__` metodunu çağırarak sıradaki " "elementi getirir. Eğer *default* verildiyse ve yineleyici tükenmiş ise " @@ -2326,10 +2335,10 @@ msgid "" "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: :func:" -"`locale.getencoding` 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:" +"*encoding* is not specified the encoding used is platform-" +"dependent: :func:`locale.getencoding` 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 "" "*mode* dosyanın açılacağı modu belirten opsiyonel bir dizedir. Varsayılan " "olarak metin modunda okuma anlamına gelen ``'r'`` değerini alır. Diğer " @@ -2337,10 +2346,10 @@ msgstr "" "ayrıcalıklı oluşturma için ``'x'`` ve dosyaya ekleme yapmak için (*bazı* " "Unix sistemlerinde, *hepsi* o anki imleç pozisyonundan bağımsız dosyanın " "sonuna ekleme anlamına gelir). Metin modunda, *encoding* belirtilmemiş ise " -"kullanılan kodlayıcı platforma bağlıdır: :func:`locale." -"getpreferredencoding(False)` geçerli kodlayıcıyı getirmek için çağırılır. " -"(İşlenmemiş baytlar okumak veya yazmak için ikili modu kullanın ve " -"*encoding* 'i boş bırakın. Geçerli modlar:" +"kullanılan kodlayıcı platforma " +"bağlıdır: :func:`locale.getpreferredencoding(False)` geçerli kodlayıcıyı " +"getirmek için çağırılır. (İşlenmemiş baytlar okumak veya yazmak için ikili " +"modu kullanın ve *encoding* 'i boş bırakın. Geçerli modlar:" #: library/functions.rst:1294 msgid "Character" @@ -2512,14 +2521,15 @@ 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:" +"though any error handling name that has been registered " +"with :func:`codecs.register_error` is also valid. The standard names " +"include:" msgstr "" "*errors* şifreleme ve deşifreleme hatalarının nasıl işleneceğini belirten " "opsiyonel bir dizedir—bu ikili modda kullanılamaz. Bazı standart hata " -"işleyecileri mevcuttur (:ref:`error-handlers` 'da listelendi), ayrıca :func:" -"`codecs.register_error` ile kaydedilen herhangi bir hata işleyici ismi de " -"geçerlidir. Standart isimler bunları içerir:" +"işleyecileri mevcuttur (:ref:`error-handlers` 'da listelendi), " +"ayrıca :func:`codecs.register_error` ile kaydedilen herhangi bir hata " +"işleyici ismi de geçerlidir. Standart isimler bunları içerir:" #: library/functions.rst:1356 msgid "" @@ -2619,10 +2629,10 @@ msgstr "" #: library/functions.rst:1400 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." +"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 "" "Çıktıyı akışa yazarkeni eğer *newline* ``None`` ise, tüm ``'\\n'`` " "karakterleri sistemin varsayılan satır ayırıcısına, :data:`os.linesep` 'e " @@ -2662,11 +2672,12 @@ msgstr "Yeni oluşturulan dosya :ref:`non-inheritable ` 'dir." #: library/functions.rst:1419 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::" +"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 "" -"Aşağıdaki örnek verilen bir dizine ait bir dosyayı açmak için :func:`os." -"open` fonksiyonunun :ref:`dir_fd ` parametresini kullanır:" +"Aşağıdaki örnek verilen bir dizine ait bir dosyayı açmak " +"için :func:`os.open` fonksiyonunun :ref:`dir_fd ` parametresini " +"kullanır:" #: library/functions.rst:1422 msgid "" @@ -2685,15 +2696,15 @@ msgstr "" 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 " +"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." +"disabled, the raw stream, a subclass " +"of :class:`io.RawIOBase`, :class:`io.FileIO`, is returned." msgstr "" ":func:`open` metodu tarafından döndürülen :term:`file object` 'in tipi moda " "bağlıdır. :func:`open` bir dosyayı metin modunda (``'w'``, ``'r'``, " @@ -2704,18 +2715,18 @@ msgstr "" "ikili okuma modunda, bir :class:`io.BufferedReader` döndürür; ikili yazma ve " "ikili ekleme modunda, :class:`io.BufferedWriter` döndürür, ve okuma/yazma " "modunda :class:`io.BufferedRandom` döndürür. Arabelleğe alma devre dışı " -"olduğunda, ham akış, :class:`io.RawIOBase` 'in alt sınıfı, :class:`io." -"FileIO` döndürülür." +"olduğunda, ham akış, :class:`io.RawIOBase` 'in alt " +"sınıfı, :class:`io.FileIO` döndürülür." #: library/functions.rst:1453 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`." +"(where :func:`open` is " +"declared), :mod:`os`, :mod:`os.path`, :mod:`tempfile`, and :mod:`shutil`." msgstr "" -"Ayrıca :mod:`fileinput`, :mod:`io` (:func:`open` 'ın tanımlandığı yer), :mod:" -"`os`, :mod:`os.path`, :mod:`tempfile`, ve :mod:`shutil` gibi dosya işleme " -"modüllerine de bkz." +"Ayrıca :mod:`fileinput`, :mod:`io` (:func:`open` 'ın tanımlandığı " +"yer), :mod:`os`, :mod:`os.path`, :mod:`tempfile`, ve :mod:`shutil` gibi " +"dosya işleme modüllerine de bkz." #: library/functions.rst:1457 #, fuzzy @@ -2763,8 +2774,8 @@ msgstr "Dosya artık miras alınamaz." #: library/functions.rst:1476 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)." +"exception, the function now retries the system call instead of raising " +"an :exc:`InterruptedError` exception (see :pep:`475` for the rationale)." msgstr "" "Eğer sistem çağrısı bölündüyse ve sinyal işleyicisi bir hata ortaya " "çıkartmazsa, artık fonksiyon :exc:`InterruptedError` hatası ortaya çıkartmak " @@ -2780,8 +2791,8 @@ msgstr ":class:`os.PathLike` uygulayan nesneleri kabul etme desteği eklendi." #: library/functions.rst:1484 msgid "" -"On Windows, opening a console buffer may return a subclass of :class:`io." -"RawIOBase` other than :class:`io.FileIO`." +"On Windows, opening a console buffer may return a subclass " +"of :class:`io.RawIOBase` other than :class:`io.FileIO`." msgstr "" "Windows'da, bir konsol arabelleğinin açılması :class:`io.FileIO` dışında " "bir :class:`io.RawIOBase` alt sınıfını döndürebilir." @@ -2825,9 +2836,9 @@ msgid "" "2)`` returns ``100``, but ``pow(10, -2)`` returns ``0.01``. For a negative " "base of type :class:`int` or :class:`float` and a non-integral exponent, a " "complex result is delivered. For example, ``pow(-9, 0.5)`` returns a value " -"close to ``3j``. Whereas, for a negative base of type :class:`int` or :class:" -"`float` with an integral exponent, a float result is delivered. For example, " -"``pow(-9, 2.0)`` returns ``81.0``." +"close to ``3j``. Whereas, for a negative base of type :class:`int` " +"or :class:`float` with an integral exponent, a float result is delivered. " +"For example, ``pow(-9, 2.0)`` returns ``81.0``." msgstr "" "Parametreler nümerik olmak zorundadır. Karışık işlenen türleriyle, ikili " "aritmetik operatörler için baskı kuralları geçerlidir. :class:`int` " @@ -2835,9 +2846,9 @@ msgstr "" "aynı türe sahip olmalıdır (baskıdan sonra); bu durumda, tüm parametreler " "gerçel sayıya çevrilir ve bir gerçel sayı sonucu teslim edilir. Örneğin " "``pow(10, 2)``, ``100`` değerini döndürür, ama ``pow(10, -2)``, ``0.01`` " -"değerini döndürür. integral olmayan bir üs ile :class:`int` veya :class:" -"`float` tipinin negatif tabanı için, karmaşık bir sayı çıktı verilir. " -"Örneğin, ``pow(-9, 0.5)``, ``3j`` 'ye yakın bir değer döndürür." +"değerini döndürür. integral olmayan bir üs ile :class:`int` " +"veya :class:`float` tipinin negatif tabanı için, karmaşık bir sayı çıktı " +"verilir. Örneğin, ``pow(-9, 0.5)``, ``3j`` 'ye yakın bir değer döndürür." #: library/functions.rst:1517 msgid "" @@ -2978,8 +2989,8 @@ msgstr "" 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`::" +"possible to create read-only properties easily using :func:`property` as " +"a :term:`decorator`::" msgstr "" "Eğer verildiyse, *doc* property özelliğinin doküman dizisi olacaktır. Aksi " "takdirde, property *fget* 'in (bulunuyorsa) doküman dizisini " @@ -3019,9 +3030,9 @@ msgid "" msgstr "" "Bir property nesnesi, dekore edilmiş metoda ayarlanan ilgili erişimci " "metoduyla özelliğin bir kopyasını oluşturmak için dekoratör olarak " -"kullanılabilen :attr:`~property.getter`, :attr:`~property.setter`, ve :attr:" -"`~property.deleter` metotlarını içerir. Bu en iyi şekilde bir örnekle " -"açıklanabilir::" +"kullanılabilen :attr:`~property.getter`, :attr:`~property.setter`, " +"ve :attr:`~property.deleter` metotlarını içerir. Bu en iyi şekilde bir " +"örnekle açıklanabilir::" #: library/functions.rst:1619 msgid "" @@ -3113,10 +3124,10 @@ msgstr "" #: library/functions.rst:1684 #, fuzzy msgid "" -"Return a reverse :term:`iterator`. *seq* must be an object which has a :" -"meth:`~object.__reversed__` method or supports the sequence protocol (the :" -"meth:`~object.__len__` method and the :meth:`~object.__getitem__` method " -"with integer arguments starting at ``0``)." +"Return a reverse :term:`iterator`. *seq* must be an object which has " +"a :meth:`~object.__reversed__` method or supports the sequence protocol " +"(the :meth:`~object.__len__` method and the :meth:`~object.__getitem__` " +"method with integer arguments starting at ``0``)." msgstr "" "Ters bir :term:`iterator` döndürür. *seq* :meth:`__reversed__` metodunu " "içeren veya dizi protokolünü (:meth:`__len__` metodu ve ``0`` ile başlayıp " @@ -3153,8 +3164,8 @@ msgstr "" #: library/functions.rst:1705 msgid "" -"For a general Python object ``number``, ``round`` delegates to ``number." -"__round__``." +"For a general Python object ``number``, ``round`` delegates to " +"``number.__round__``." msgstr "" "Genel bir Python nesnesi için ``number``, ``round`` ``number.__round__`` 'u " "temsil eder." @@ -3185,13 +3196,13 @@ msgstr "" #: library/functions.rst:1726 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." +"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 "" -"Diğer konteynerler için, yerleşik :class:`frozenset`, :class:`list`, :class:" -"`tuple` ve :class:`dict` sınıflarını; aynı zamanda :mod:`collections` " -"modülüne bakınız." +"Diğer konteynerler için, " +"yerleşik :class:`frozenset`, :class:`list`, :class:`tuple` ve :class:`dict` " +"sınıflarını; aynı zamanda :mod:`collections` modülüne bakınız." #: library/functions.rst:1733 msgid "" @@ -3209,16 +3220,17 @@ msgstr "" #: library/functions.rst:1739 msgid "" "*name* need not be a Python identifier as defined in :ref:`identifiers` " -"unless the object chooses to enforce that, for example in a custom :meth:" -"`~object.__getattribute__` or via :attr:`~object.__slots__`. An attribute " -"whose name is not an identifier will not be accessible using the dot " -"notation, but is accessible through :func:`getattr` etc.." -msgstr "" -"*name*, nesne bunu zorunlu kılmayı seçmedikçe, örneğin özel bir :meth:" -"`~object.__getattribute__` veya :attr:`~object.__slots__` aracılığıyla, :ref:" -"`identifiers` içinde tanımlandığı gibi bir Python tanımlayıcısı olmak " -"zorunda değildir. Adı tanımlayıcı olmayan bir özelliğe nokta kullanılarak " -"erişilemez, ancak :func:`getattr` vb. aracılığıyla erişilebilir." +"unless the object chooses to enforce that, for example in a " +"custom :meth:`~object.__getattribute__` or via :attr:`~object.__slots__`. An " +"attribute whose name is not an identifier will not be accessible using the " +"dot notation, but is accessible through :func:`getattr` etc.." +msgstr "" +"*name*, nesne bunu zorunlu kılmayı seçmedikçe, örneğin özel " +"bir :meth:`~object.__getattribute__` veya :attr:`~object.__slots__` " +"aracılığıyla, :ref:`identifiers` içinde tanımlandığı gibi bir Python " +"tanımlayıcısı olmak zorunda değildir. Adı tanımlayıcı olmayan bir özelliğe " +"nokta kullanılarak erişilemez, ancak :func:`getattr` vb. aracılığıyla " +"erişilebilir." #: library/functions.rst:1747 msgid "" @@ -3248,14 +3260,16 @@ msgstr "" #: library/functions.rst:1769 msgid "" "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 :term:`iterator`." +"example: ``a[start:stop:step]`` or ``a[start:stop, i]``. " +"See :func:`itertools.islice` for an alternate version that returns " +"an :term:`iterator`." msgstr "" #: library/functions.rst:1774 msgid "" -"Slice objects are now :term:`hashable` (provided :attr:`~slice.start`, :attr:" -"`~slice.stop`, and :attr:`~slice.step` are hashable)." +"Slice objects are now :term:`hashable` " +"(provided :attr:`~slice.start`, :attr:`~slice.stop`, and :attr:`~slice.step` " +"are hashable)." msgstr "" #: library/functions.rst:1780 @@ -3271,12 +3285,14 @@ msgstr "İsimle belirtilmesi gereken 2 opsiyonel parametresi vardır." #: library/functions.rst:1784 msgid "" "*key* specifies a function of one argument that is used to extract a " -"comparison key from each element in *iterable* (for example, ``key=str." -"lower``). The default value is ``None`` (compare the elements directly)." +"comparison key from each element in *iterable* (for example, " +"``key=str.lower``). The default value is ``None`` (compare the elements " +"directly)." msgstr "" "*key*, *iterable* 'ın her elementinden bir karşılaştırma anahtarı ayıklamak " -"için kullanılan bir argümanın fonksiyonunu belirtir (örneğin, ``key=str." -"lower``). Varsayılan değer ``None`` 'dır (elementleri direkt karşılaştırır)." +"için kullanılan bir argümanın fonksiyonunu belirtir (örneğin, " +"``key=str.lower``). Varsayılan değer ``None`` 'dır (elementleri direkt " +"karşılaştırır)." #: library/functions.rst:1788 msgid "" @@ -3291,8 +3307,8 @@ msgid "" "Use :func:`functools.cmp_to_key` to convert an old-style *cmp* function to a " "*key* function." msgstr "" -"Eski stil *cmp* fonksiyonunu bir *key* fonksiyonuna dönüştürmek için :func:" -"`functools.cmp_to_key` 'yi kullanın." +"Eski stil *cmp* fonksiyonunu bir *key* fonksiyonuna dönüştürmek " +"için :func:`functools.cmp_to_key` 'yi kullanın." #: library/functions.rst:1794 msgid "" @@ -3354,8 +3370,8 @@ msgstr "" #: library/functions.rst:1821 msgid "" -"The ``@staticmethod`` form is a function :term:`decorator` -- see :ref:" -"`function` for details." +"The ``@staticmethod`` form is a function :term:`decorator` -- " +"see :ref:`function` for details." msgstr "" "``@staticmethod`` ifadesi bir :term:`decorator` fonksiyonudur. -- detaylar " "için :ref:`function` bkz." @@ -3364,9 +3380,9 @@ msgstr "" #, fuzzy msgid "" "A static method can be called either on the class (such as ``C.f()``) or on " -"an instance (such as ``C().f()``). Moreover, the static method :term:" -"`descriptor` is also callable, so it can be used in the class definition " -"(such as ``f()``)." +"an instance (such as ``C().f()``). Moreover, the static " +"method :term:`descriptor` is also callable, so it can be used in the class " +"definition (such as ``f()``)." msgstr "" "Bir statik metot sınıf üzerinden (``C.f()`` gibi) veya bir örnek üzerinden " "(``C().f()`` gibi) çağırılabilir. Hatta normal fonksiyonlar gibi (``f()``) " @@ -3412,10 +3428,10 @@ msgstr "Statik metotlar hakkında daha fazla bilgi için, :ref:`types` bkz." #: library/functions.rst:1847 #, fuzzy msgid "" -"Static methods now inherit the method attributes (:attr:`~function." -"__module__`, :attr:`~function.__name__`, :attr:`~function.__qualname__`, :" -"attr:`~function.__doc__` and :attr:`~function.__annotations__`), have a new " -"``__wrapped__`` attribute, and are now callable as regular functions." +"Static methods now inherit the method attributes " +"(:attr:`~function.__module__`, :attr:`~function.__name__`, :attr:`~function.__qualname__`, :attr:`~function.__doc__` " +"and :attr:`~function.__annotations__`), have a new ``__wrapped__`` " +"attribute, and are now callable as regular functions." msgstr "" "Statik metotlar artık metot özelliklerini (``__module__``, ``__name__``, " "``__qualname__``, ``__doc__`` and ``__annotations__``) miras alır, yeni bir " @@ -3451,17 +3467,18 @@ msgstr "" #, fuzzy 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`." +"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 "" "Bazı kullanım durumları için, :func:`sum` fonksiyonuna iyi alternatifler " "var. Dizelerden oluşan bir diziyi birleştirmek için tercih edilen hızlı " "yöntem ``''.join(sequence)`` fonksiyonudur. Gerçel değerleri hassas bir " "şekilde eklemek istiyorsanız, :func:`math.fsum`\\ bkz. Yinelenebilir " -"nesnelerden oluşan bir diziyi birleştirmek istiyorsanız, :func:`itertools." -"chain` fonksiyonunu kullanmayı göz önünde bulundurun." +"nesnelerden oluşan bir diziyi birleştirmek " +"istiyorsanız, :func:`itertools.chain` fonksiyonunu kullanmayı göz önünde " +"bulundurun." #: library/functions.rst:1881 msgid "The *start* parameter can be specified as a keyword argument." @@ -3494,21 +3511,21 @@ msgstr "" #: library/functions.rst:1899 #, fuzzy msgid "" -"For example, if :attr:`~type.__mro__` of *object_or_type* is ``D -> B -> C -" -"> A -> object`` and the value of *type* is ``B``, then :func:`super` " +"For example, if :attr:`~type.__mro__` of *object_or_type* is ``D -> B -> C " +"-> A -> object`` and the value of *type* is ``B``, then :func:`super` " "searches ``C -> A -> object``." msgstr "" -"Örnek olarak, eğer *object_or_type* 'ın :attr:`~class.__mro__` özelliği ``D -" -"> B -> C -> A -> object`` ise ve *type* değeri ``B`` ise, :func:`super` ``C -" -"> A -> object`` 'i arar." +"Örnek olarak, eğer *object_or_type* 'ın :attr:`~class.__mro__` özelliği ``D " +"-> B -> C -> A -> object`` ise ve *type* değeri ``B`` ise, :func:`super` ``C " +"-> A -> object`` 'i arar." #: library/functions.rst:1903 #, fuzzy msgid "" "The :attr:`~type.__mro__` attribute of the class corresponding to " -"*object_or_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." +"*object_or_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 "" "*object_or_type* 'ın :attr:`~class.__mro__` özelliği, hem :func:`getattr` " "hem de :func:`super` tarafından kullanılan yöntem çözümleme arama sırasını " @@ -3579,8 +3596,8 @@ msgid "" "` in a parent or sibling class." msgstr "" "Metot aramalarına ek olarak, :func:`super` özellik aramaları için de " -"çalışır. Bunun kullanım şekli ebeveyn veya kardeş bir sınıfta :term:" -"`tanımlayıcılar ` 'i çağırmaktır." +"çalışır. Bunun kullanım şekli ebeveyn veya kardeş bir " +"sınıfta :term:`tanımlayıcılar ` 'i çağırmaktır." #: library/functions.rst:1939 #, fuzzy @@ -3595,9 +3612,9 @@ msgstr "" ":func:`super` 'ın, ``super().__getitem__(name)`` gibi açık noktalı öznitelik " "aramaları için bağlayan işlemin bir parçası olarak uygulanır. Sınıfları " "işbirlikli çoklu kalıtımı destekleyen tahmin edilebilir bir sırada aramak " -"için kendi :meth:`__getattribute__` metodunu sağlar. Bu nedenle :func:" -"`super`, ifadeler veya ``super()[name]`` gibi operatörler kullanarak kesin " -"aramalar için tanımsızdır." +"için kendi :meth:`__getattribute__` metodunu sağlar. Bu " +"nedenle :func:`super`, ifadeler veya ``super()[name]`` gibi operatörler " +"kullanarak kesin aramalar için tanımsızdır." #: library/functions.rst:1947 msgid "" @@ -3616,28 +3633,28 @@ msgstr "" #: library/functions.rst:1954 msgid "" -"For practical suggestions on how to design cooperative classes using :func:" -"`super`, see `guide to using super() `_." +"For practical suggestions on how to design cooperative classes " +"using :func:`super`, see `guide to using super() `_." msgstr "" ":func:`super` 'ı kullanarak kooperatif sınıflar tasarlamaya yönelik pratik " -"öneriler için, `guide to using super() `_ bkz." +"öneriler için, `guide to using super() `_ bkz." #: library/functions.rst:1964 msgid "" "Rather than being a function, :class:`tuple` is actually an immutable " "sequence type, as documented in :ref:`typesseq-tuple` and :ref:`typesseq`." msgstr "" -"Bir fonksiyon olmaktansa, :class:`tuple` :ref:`typesseq-tuple` ve :ref:" -"`typesseq` 'de gösterildiği gibi düzenlenemez bir dizi türüdür." +"Bir fonksiyon olmaktansa, :class:`tuple` :ref:`typesseq-tuple` " +"ve :ref:`typesseq` 'de gösterildiği gibi düzenlenemez bir dizi türüdür." #: library/functions.rst:1973 #, fuzzy 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__`." +"type object and generally the same object as returned " +"by :attr:`object.__class__`." msgstr "" "Bir parametre ile, *object* 'in türünü döndürür. Döndürülen değer bir obje " "türüdür ve genellikle :attr:`object.__class__ ` " @@ -3660,18 +3677,19 @@ msgid "" "tuple contains the base classes and becomes the :attr:`~type.__bases__` " "attribute; if empty, :class:`object`, the ultimate base of all classes, is " "added. The *dict* dictionary contains attribute and method definitions for " -"the class body; it may be copied or wrapped before becoming the :attr:`~type." -"__dict__` attribute. The following two statements create identical :class:`!" -"type` objects:" +"the class body; it may be copied or wrapped before becoming " +"the :attr:`~type.__dict__` attribute. The following two statements create " +"identical :class:`!type` objects:" msgstr "" "Üç parametre ile, yeni nesne türü döndürür. Bu esasen :keyword:`class` " -"ifadesinin dinamik biçimidir. *name* dizesi sınıfın ismidir ve :attr:" -"`~definition.__name__` özelliği yerine gelir. *bases* demeti temel sınıfları " -"içerir ve :attr:`~class.__bases__` özelliği yerine gelir; eğer boş ise, :" -"class:`object`, tüm sınıfların nihai temeli eklenir. *dict* sözlüğü sınıf " -"gövdesi için özellik ve metot tanımlamaları içerir; :attr:`~object.__dict__` " -"özelliği yerine geçmeden önce kopyalanabilir veya sarılabilir. Aşağıdaki iki " -"ifade birebir aynı :class:`type` nesneleri oluşturur:" +"ifadesinin dinamik biçimidir. *name* dizesi sınıfın ismidir " +"ve :attr:`~definition.__name__` özelliği yerine gelir. *bases* demeti temel " +"sınıfları içerir ve :attr:`~class.__bases__` özelliği yerine gelir; eğer boş " +"ise, :class:`object`, tüm sınıfların nihai temeli eklenir. *dict* sözlüğü " +"sınıf gövdesi için özellik ve metot tanımlamaları " +"içerir; :attr:`~object.__dict__` özelliği yerine geçmeden önce " +"kopyalanabilir veya sarılabilir. Aşağıdaki iki ifade birebir " +"aynı :class:`type` nesneleri oluşturur:" #: library/functions.rst:1995 msgid "See also:" @@ -3725,16 +3743,17 @@ msgstr "" #: library/functions.rst:2017 #, fuzzy msgid "" -"Objects such as modules and instances have an updateable :attr:`~object." -"__dict__` attribute; however, other objects may have write restrictions on " -"their :attr:`!__dict__` attributes (for example, classes use a :class:`types." -"MappingProxyType` to prevent direct dictionary updates)." +"Objects such as modules and instances have an " +"updateable :attr:`~object.__dict__` attribute; however, other objects may " +"have write restrictions on their :attr:`!__dict__` attributes (for example, " +"classes use a :class:`types.MappingProxyType` to prevent direct dictionary " +"updates)." msgstr "" -"Modüller ve örnekler gibi nesneler güncellenebilir bir :attr:`~object." -"__dict__` özelliğine sahiptir; ama diğer nesnelerin kendilerinin :attr:" -"`~object.__dict__` özelliklerine yazma kısıtlaması olabilir (örnek olarak, " -"sınıflar doğrudan sözlük güncellemelerini önlemek için :class:`types." -"MappingProxyType` sınıfını kullanırlar)." +"Modüller ve örnekler gibi nesneler güncellenebilir " +"bir :attr:`~object.__dict__` özelliğine sahiptir; ama diğer nesnelerin " +"kendilerinin :attr:`~object.__dict__` özelliklerine yazma kısıtlaması " +"olabilir (örnek olarak, sınıflar doğrudan sözlük güncellemelerini önlemek " +"için :class:`types.MappingProxyType` sınıfını kullanırlar)." #: library/functions.rst:2022 msgid "" @@ -3753,8 +3772,8 @@ msgid "" "defines the :attr:`~object.__slots__` attribute)." msgstr "" "Eğer bir obje belirtildiyse ama :attr:`~object.__dict__` özelliği yoksa " -"(örneğin, :attr:`~object.__slots__` özelliğini tanımlayan bir sınıf ise), :" -"exc:`TypeError` hatası ortaya çıkar." +"(örneğin, :attr:`~object.__slots__` özelliğini tanımlayan bir sınıf " +"ise), :exc:`TypeError` hatası ortaya çıkar." #: library/functions.rst:2032 msgid "" @@ -3790,8 +3809,8 @@ msgstr "" #: library/functions.rst:2047 msgid "" "Another way to think of :func:`zip` is that it turns rows into columns, and " -"columns into rows. This is similar to `transposing a matrix `_." +"columns into rows. This is similar to `transposing a matrix `_." msgstr "" ":func:`zip` 'i anlamanın başka bir yolu da, sütunları satırlara ve satırları " "sütunlara çevirmesidir. Bu `transposing a matrix ` parameter for further details." +#~ "has any effect, and is considered deprecated. It previously " +#~ "enabled :term:`universal newlines` in text mode, which became the default " +#~ "behavior in Python 3.0. Refer to the documentation of the :ref:`newline " +#~ "` parameter for further details." #~ msgstr "" #~ "İzin verilen ek bir mod karakteri vardır, ``'U'``, artık bir etkisi " #~ "yoktur ve \"kullanımdan kaldırıldı\" olarak değerlendirilir. Önceden " diff --git a/library/functools.po b/library/functools.po index 5e3c4c623..3ab36ba09 100644 --- a/library/functools.po +++ b/library/functools.po @@ -111,9 +111,9 @@ msgstr "" #: library/functools.rst:81 msgid "" -"The mechanics of :func:`cached_property` are somewhat different from :func:" -"`property`. A regular property blocks attribute writes unless a setter is " -"defined. In contrast, a *cached_property* allows writes." +"The mechanics of :func:`cached_property` are somewhat different " +"from :func:`property`. A regular property blocks attribute writes unless a " +"setter is defined. In contrast, a *cached_property* allows writes." msgstr "" #: library/functools.rst:85 @@ -164,8 +164,8 @@ msgid "" "If a mutable mapping is not available or if space-efficient key sharing is " "desired, an effect similar to :func:`cached_property` can also be achieved " "by stacking :func:`property` on top of :func:`lru_cache`. See :ref:`faq-" -"cache-method-calls` for more details on how this differs from :func:" -"`cached_property`." +"cache-method-calls` for more details on how this differs " +"from :func:`cached_property`." msgstr "" #: library/functools.rst:120 @@ -180,11 +180,10 @@ msgstr "" #: library/functools.rst:130 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." +"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 "" #: library/functools.rst:137 @@ -287,9 +286,9 @@ msgstr "" #: library/functools.rst:210 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." +"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 "" #: library/functools.rst:214 @@ -349,9 +348,10 @@ msgstr "" #: library/functools.rst:252 msgid "" -"Example of efficiently computing `Fibonacci numbers `_ using a cache to implement a `dynamic " -"programming `_ technique::" +"Example of efficiently computing `Fibonacci numbers `_ using a cache to implement a " +"`dynamic programming `_ " +"technique::" msgstr "" #: library/functools.rst:258 @@ -469,9 +469,9 @@ msgstr "" #: library/functools.rst:364 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." +"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 "" #: library/functools.rst:368 @@ -482,11 +482,11 @@ msgstr "" #: library/functools.rst:371 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 :ref:`partial object` returned as the result." +"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 :ref:`partial " +"object` returned as the result." msgstr "" #: library/functools.rst:377 @@ -494,8 +494,8 @@ 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." +"argument, even before the *args* and *keywords* supplied to " +"the :class:`partialmethod` constructor." msgstr "" #: library/functools.rst:385 @@ -557,8 +557,8 @@ msgstr "" #: library/functools.rst:434 msgid "" -"Transform a function into a :term:`single-dispatch ` :term:" -"`generic function`." +"Transform a function into a :term:`single-dispatch ` :term:`generic function`." msgstr "" #: library/functools.rst:437 @@ -730,9 +730,9 @@ msgstr "" 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 :" -"class:`object` type, which means it is used if no better implementation is " -"found." +"function decorated with ``@singledispatch`` is registered for the " +"base :class:`object` type, which means it is used if no better " +"implementation is found." msgstr "" #: library/functools.rst:561 @@ -794,14 +794,14 @@ msgstr "" #: library/functools.rst:601 msgid "" -"The :func:`register` attribute now supports :data:`types.UnionType` and :" -"data:`typing.Union` as type annotations." +"The :func:`register` attribute now supports :data:`types.UnionType` " +"and :data:`typing.Union` as type annotations." msgstr "" #: library/functools.rst:608 msgid "" -"Transform a method into a :term:`single-dispatch ` :term:" -"`generic function`." +"Transform a method into a :term:`single-dispatch ` :term:`generic function`." msgstr "" #: library/functools.rst:611 @@ -830,11 +830,11 @@ msgstr "" #: library/functools.rst:629 msgid "" -"``@singledispatchmethod`` supports nesting with other decorators such as :" -"func:`@classmethod`. Note that to allow for ``dispatcher." -"register``, ``singledispatchmethod`` must be the *outer most* decorator. " -"Here is the ``Negator`` class with the ``neg`` methods bound to the class, " -"rather than an instance of the class::" +"``@singledispatchmethod`` supports nesting with other decorators such " +"as :func:`@classmethod`. Note that to allow for " +"``dispatcher.register``, ``singledispatchmethod`` must be the *outer most* " +"decorator. Here is the ``Negator`` class with the ``neg`` methods bound to " +"the class, rather than an instance of the class::" msgstr "" #: library/functools.rst:635 @@ -858,8 +858,8 @@ msgstr "" #: library/functools.rst:651 msgid "" -"The same pattern can be used for other similar decorators: :func:" -"`@staticmethod`, :func:`@abstractmethod`, " +"The same pattern can be used for other similar " +"decorators: :func:`@staticmethod`, :func:`@abstractmethod`, " "and others." msgstr "" @@ -871,12 +871,11 @@ msgid "" "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 :attr:`~function.__module__`, :attr:" -"`~function.__name__`, :attr:`~function.__qualname__`, :attr:`~function." -"__annotations__`, :attr:`~function.__type_params__`, and :attr:`~function." -"__doc__`, the documentation string) and ``WRAPPER_UPDATES`` (which updates " -"the wrapper function's :attr:`~function.__dict__`, i.e. the instance " -"dictionary)." +"(which assigns to the wrapper " +"function's :attr:`~function.__module__`, :attr:`~function.__name__`, :attr:`~function.__qualname__`, :attr:`~function.__annotations__`, :attr:`~function.__type_params__`, " +"and :attr:`~function.__doc__`, the documentation string) and " +"``WRAPPER_UPDATES`` (which updates the wrapper " +"function's :attr:`~function.__dict__`, i.e. the instance dictionary)." msgstr "" #: library/functools.rst:672 @@ -907,16 +906,16 @@ msgstr "" #: library/functools.rst:689 msgid "" -"The ``__wrapped__`` attribute is now automatically added. The :attr:" -"`~function.__annotations__` attribute is now copied by default. Missing " -"attributes no longer trigger an :exc:`AttributeError`." +"The ``__wrapped__`` attribute is now automatically added. " +"The :attr:`~function.__annotations__` attribute is now copied by default. " +"Missing attributes no longer trigger an :exc:`AttributeError`." msgstr "" #: library/functools.rst:694 msgid "" "The ``__wrapped__`` attribute now always refers to the wrapped function, " -"even if that function defined a ``__wrapped__`` attribute. (see :issue:" -"`17482`)" +"even if that function defined a ``__wrapped__`` attribute. " +"(see :issue:`17482`)" msgstr "" #: library/functools.rst:699 @@ -959,8 +958,8 @@ msgstr "" #: library/functools.rst:731 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." +"would have been ``'wrapper'``, and the docstring of the " +"original :func:`example` would have been lost." msgstr "" #: library/functools.rst:739 @@ -995,9 +994,9 @@ msgstr "" msgid "" ":class:`partial` objects are like :ref:`function objects ` in that they are callable, weak referenceable, and can have " -"attributes. There are some important differences. For instance, the :attr:" -"`~function.__name__` and :attr:`function.__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." +"attributes. There are some important differences. For instance, " +"the :attr:`~function.__name__` and :attr:`function.__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 "" diff --git a/library/gc.po b/library/gc.po index b73e3d359..4ad6b45a9 100644 --- a/library/gc.po +++ b/library/gc.po @@ -144,9 +144,9 @@ msgid "" "examined. If generation ``0`` has been examined more than *threshold1* " "times since generation ``1`` has been examined, then generation ``1`` is " "examined as well. With the third generation, things are a bit more " -"complicated, see `Collecting the oldest generation `_ for more " -"information." +"complicated, see `Collecting the oldest generation `_ " +"for more information." msgstr "" #: library/gc.rst:121 @@ -194,13 +194,14 @@ msgstr "" #: library/gc.rst:154 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." +"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 "" #: library/gc.rst:162 @@ -307,10 +308,10 @@ msgstr "" #: library/gc.rst:255 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." +"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 "" #: library/gc.rst:261 diff --git a/library/getopt.po b/library/getopt.po index a32ea796a..b46bc0207 100644 --- a/library/getopt.po +++ b/library/getopt.po @@ -35,8 +35,8 @@ msgstr "" #: 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` " +"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." @@ -52,8 +52,8 @@ msgid "" "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)." +"argument followed by a colon (``':'``; i.e., the same format that " +"Unix :c:func:`getopt` uses)." msgstr "" #: library/getopt.rst:40 @@ -83,9 +83,9 @@ msgid "" "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 " +"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 "" @@ -167,8 +167,8 @@ msgstr "" #: 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::" +"code and more informative help and error messages by using " +"the :mod:`argparse` module::" msgstr "" #: library/getopt.rst:150 diff --git a/library/getpass.po b/library/getpass.po index d0a08bfa5..f15876dfd 100644 --- a/library/getpass.po +++ b/library/getpass.po @@ -52,8 +52,8 @@ msgstr "" #: library/getpass.rst:28 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`." +"message to *stream* and reading from ``sys.stdin`` and issuing " +"a :exc:`GetPassWarning`." msgstr "" #: library/getpass.rst:33 @@ -72,11 +72,12 @@ msgstr "" #: library/getpass.rst:45 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." +"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 "" #: library/getpass.rst:52 diff --git a/library/gettext.po b/library/gettext.po index 8634770ef..87664b97b 100644 --- a/library/gettext.po +++ b/library/gettext.po @@ -57,12 +57,13 @@ msgstr "" #: 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 *language* is searched for in the environment variables :envvar:" -"`LANGUAGE`, :envvar:`LC_ALL`, :envvar:`LC_MESSAGES`, and :envvar:`LANG` " -"respectively." +"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 *language* is searched for in the " +"environment " +"variables :envvar:`LANGUAGE`, :envvar:`LC_ALL`, :envvar:`LC_MESSAGES`, " +"and :envvar:`LANG` respectively." msgstr "" #: library/gettext.rst:45 @@ -167,11 +168,12 @@ msgstr "" 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." +"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 "" #: library/gettext.rst:140 @@ -213,8 +215,8 @@ msgstr "" #: library/gettext.rst:165 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." +"*fallback* is false (which is the default), and returns " +"a :class:`NullTranslations` instance if *fallback* is true." msgstr "" #: library/gettext.rst:169 @@ -228,8 +230,8 @@ msgstr "" #: library/gettext.rst:177 msgid "" "This installs the function :func:`!_` in Python's builtins namespace, based " -"on *domain* and *localedir* which are passed to the function :func:" -"`translation`." +"on *domain* and *localedir* which are passed to the " +"function :func:`translation`." msgstr "" #: library/gettext.rst:180 @@ -348,9 +350,9 @@ msgstr "" #: library/gettext.rst:279 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, " +"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 "" @@ -378,18 +380,18 @@ msgstr "" #: library/gettext.rst:299 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." +"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 "" #: library/gettext.rst:304 msgid "" ":class:`GNUTranslations` parses optional metadata out of the translation " "catalog. It is convention with GNU :program:`gettext` to include metadata as " -"the translation for the empty string. This metadata is in :rfc:`822`\\ -" -"style ``key: value`` pairs, and should contain the ``Project-Id-Version`` " +"the translation for the empty string. This metadata 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, " @@ -440,9 +442,9 @@ msgstr "" #: library/gettext.rst:343 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:`~NullTranslations." -"ngettext` method. Otherwise, when *n* is 1 *singular* is returned, and " -"*plural* is returned in all other cases." +"the request is forwarded to the " +"fallback's :meth:`~NullTranslations.ngettext` method. Otherwise, when *n* " +"is 1 *singular* is returned, and *plural* is returned in all other cases." msgstr "" #: library/gettext.rst:348 @@ -595,34 +597,35 @@ msgstr "" #: library/gettext.rst:452 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.)" +"(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 "" #: library/gettext.rst:464 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." +":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 "" #: library/gettext.rst:470 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." +"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 "" #: library/gettext.rst:479 @@ -639,8 +642,8 @@ msgstr "" #: library/gettext.rst:487 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 :program:" -"`gettext` API but instead the class-based API." +"changes, e.g. to the built-in namespace. You should not use the " +"GNU :program:`gettext` API but instead the class-based API." msgstr "" #: library/gettext.rst:491 @@ -684,8 +687,8 @@ msgstr "" #: library/gettext.rst:515 msgid "" -"If you need to set the locale directory, you can pass it into the :func:" -"`install` function::" +"If you need to set the locale directory, you can pass it into " +"the :func:`install` function::" msgstr "" #: library/gettext.rst:518 diff --git a/library/glob.po b/library/glob.po index 364427f3d..4ee791e6d 100644 --- a/library/glob.po +++ b/library/glob.po @@ -37,21 +37,21 @@ msgstr "" ":mod:`glob` modülü Unix kabuğu tarafından kullanılan kurallarına uyarak " "spesifik desenlerle eşleşen tüm yol adlarını bulur ve sonucu gelişigüzel bir " "sırada ile döndürür. Tilde açılımı yapılmaz fakat ``[]`` içinde ifade edilen " -"karakter aralığı ve ``*``, ``?`` karakterleri eşleştirilir. Bu işlem :func:" -"`os.scandir` ve :func:`fnmatch.fnmatch` fonksiyonlarının birlikte çalışması " -"ile olur ve bir altkabuk çağırılmaz." +"karakter aralığı ve ``*``, ``?`` karakterleri eşleştirilir. Bu " +"işlem :func:`os.scandir` ve :func:`fnmatch.fnmatch` fonksiyonlarının " +"birlikte çalışması ile olur ve bir altkabuk çağırılmaz." #: library/glob.rst:28 msgid "" "Note that files beginning with a dot (``.``) can only be matched by patterns " -"that also start with a dot, unlike :func:`fnmatch.fnmatch` or :func:`pathlib." -"Path.glob`. (For tilde and shell variable expansion, use :func:`os.path." -"expanduser` and :func:`os.path.expandvars`.)" +"that also start with a dot, unlike :func:`fnmatch.fnmatch` " +"or :func:`pathlib.Path.glob`. (For tilde and shell variable expansion, " +"use :func:`os.path.expanduser` and :func:`os.path.expandvars`.)" msgstr "" "Dikkat edilmeli ki :func:`fnmatch.fnmatch` veya :func:`pathlib.Path.glob` " "aksine, nokta (``.``) ile başlayan dosyalar sadece nokta ile başlayan " -"desenler ile eşleştirilebilir. (Tilde ve kabuk değişken açılımları için :" -"func:`os.path.expanduser` ve :func:`os.path.expandvars` kullanın.)" +"desenler ile eşleştirilebilir. (Tilde ve kabuk değişken açılımları " +"için :func:`os.path.expanduser` ve :func:`os.path.expandvars` kullanın.)" #: library/glob.rst:34 msgid "" @@ -69,12 +69,12 @@ msgstr ":mod:`pathlib` modülü yüksek-seviye dizin yolu nesneleri döndürür. 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). Whether or not the " -"results are sorted depends on the file system. If a file that satisfies " -"conditions is removed or added during the call of this function, whether a " -"path name for that file will be included is unspecified." +"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). " +"Whether or not the results are sorted depends on the file system. If a file " +"that satisfies conditions is removed or added during the call of this " +"function, whether a path name for that file will be included is unspecified." msgstr "" "*pathname* ile eşleşen bir liste döndürür ve bu boş liste de olabilir. " "*pathname*, dizin yolu belirtimi içeren bir string olmalıdır. *pathname* hem " @@ -89,12 +89,12 @@ msgstr "" #: library/glob.rst:54 msgid "" "If *root_dir* is not ``None``, it should be a :term:`path-like object` " -"specifying the root directory for searching. It has the same effect on :" -"func:`glob` as changing the current directory before calling it. If " +"specifying the root directory for searching. It has the same effect " +"on :func:`glob` as changing the current directory before calling it. If " "*pathname* is relative, the result will contain paths relative to *root_dir*." msgstr "" -"Eğer *root_dir* ``None`` değilse, arama için kök dizini belirten bir :term:" -"`yol benzeri nesne ` olmalıdır. Bu, :func:`glob` " +"Eğer *root_dir* ``None`` değilse, arama için kök dizini belirten " +"bir :term:`yol benzeri nesne ` olmalıdır. Bu, :func:`glob` " "fonksiyonu üzerinde, fonksiyonu çağırmadan önce geçerli dizini değiştirmekle " "aynı etkiyi yaratır. Eğer *pathname* göreceli bir yol ise, sonuç " "*root_dir*'den itibaren oluşturulmuş göreceli yolları içerir." @@ -189,16 +189,16 @@ msgstr "" "Tüm özel karakterlerden (``'?'``, ``'*'`` and ``'['``) kaçar. Eğer özel " "karakterler içerme ihtimali olan belirsiz bir dizini harfi harfine " "eşleştirmek istiyorsanız faydalıdır. Sürücü/UNC paylaşım noktalarındaki özel " -"karakterler kaçırılamaz; örneğin Windows'ta ``escape('//?/c:/Quo vadis?." -"txt')`` ``'//?/c:/Quo vadis[?].txt'`` döndürür." +"karakterler kaçırılamaz; örneğin Windows'ta ``escape('//?/c:/Quo " +"vadis?.txt')`` ``'//?/c:/Quo vadis[?].txt'`` döndürür." #: library/glob.rst:128 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. ::" +"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 "" "Örneğin, :file:`1.gif`, :file:`2.txt`, :file:`card.gif` dosyalarını içeren " "bir dizin ve :file:`sub` adında sadece :file:`3.txt` dosyasını içeren bir " @@ -234,8 +234,8 @@ msgstr "" #: library/glob.rst:146 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`::" +"default. For example, consider a directory containing :file:`card.gif` " +"and :file:`.card.gif`::" msgstr "" "Eğer dizin ``.`` ile başlayan dosyalar içeriyorsa varsayılan olarak " "eşleştirilmezler. Örneğin, :file:`card.gif` and :file:`.card.gif`:: " diff --git a/library/graphlib.po b/library/graphlib.po index fb858c40a..7b8239b69 100644 --- a/library/graphlib.po +++ b/library/graphlib.po @@ -82,8 +82,8 @@ msgstr "" #: library/graphlib.rst:49 msgid "" "In case just an immediate sorting of the nodes in the graph is required and " -"no parallelism is involved, the convenience method :meth:`TopologicalSorter." -"static_order` can be used directly:" +"no parallelism is involved, the convenience " +"method :meth:`TopologicalSorter.static_order` can be used directly:" msgstr "" #: library/graphlib.rst:53 @@ -153,21 +153,21 @@ msgstr "" #: library/graphlib.rst:102 msgid "" "Mark the graph as finished and check for cycles in the graph. If any cycle " -"is detected, :exc:`CycleError` will be raised, but :meth:`~TopologicalSorter." -"get_ready` can still be used to obtain as many nodes as possible until " -"cycles block more progress. After a call to this function, the graph cannot " -"be modified, and therefore no more nodes can be added using :meth:" -"`~TopologicalSorter.add`." +"is detected, :exc:`CycleError` will be raised, " +"but :meth:`~TopologicalSorter.get_ready` can still be used to obtain as many " +"nodes as possible until cycles block more progress. After a call to this " +"function, the graph cannot be modified, and therefore no more nodes can be " +"added using :meth:`~TopologicalSorter.add`." msgstr "" #: library/graphlib.rst:111 msgid "" "Returns ``True`` if more progress can be made and ``False`` otherwise. " "Progress can be made if cycles do not block the resolution and either there " -"are still nodes ready that haven't yet been returned by :meth:" -"`TopologicalSorter.get_ready` or the number of nodes marked :meth:" -"`TopologicalSorter.done` is less than the number that have been returned by :" -"meth:`TopologicalSorter.get_ready`." +"are still nodes ready that haven't yet been returned " +"by :meth:`TopologicalSorter.get_ready` or the number of nodes " +"marked :meth:`TopologicalSorter.done` is less than the number that have been " +"returned by :meth:`TopologicalSorter.get_ready`." msgstr "" #: library/graphlib.rst:118 @@ -194,8 +194,8 @@ msgstr "" #: library/graphlib.rst:152 msgid "" -"Raises :exc:`ValueError` if called without calling :meth:`~TopologicalSorter." -"prepare` previously." +"Raises :exc:`ValueError` if called without " +"calling :meth:`~TopologicalSorter.prepare` previously." msgstr "" #: library/graphlib.rst:134 @@ -209,9 +209,9 @@ msgstr "" msgid "" "Raises :exc:`ValueError` if any node in *nodes* has already been marked as " "processed by a previous call to this method or if a node was not added to " -"the graph by using :meth:`TopologicalSorter.add`, if called without calling :" -"meth:`~TopologicalSorter.prepare` or if node has not yet been returned by :" -"meth:`~TopologicalSorter.get_ready`." +"the graph by using :meth:`TopologicalSorter.add`, if called without " +"calling :meth:`~TopologicalSorter.prepare` or if node has not yet been " +"returned by :meth:`~TopologicalSorter.get_ready`." msgstr "" #: library/graphlib.rst:146 @@ -226,9 +226,9 @@ msgstr "" #: library/graphlib.rst:157 msgid "" "Returns an iterator object which will iterate over nodes in a topological " -"order. When using this method, :meth:`~TopologicalSorter.prepare` and :meth:" -"`~TopologicalSorter.done` should not be called. This method is equivalent " -"to::" +"order. When using this method, :meth:`~TopologicalSorter.prepare` " +"and :meth:`~TopologicalSorter.done` should not be called. This method is " +"equivalent to::" msgstr "" #: library/graphlib.rst:162 @@ -265,9 +265,9 @@ msgstr "" #: library/graphlib.rst:186 msgid "" "This is due to the fact that \"0\" and \"2\" are in the same level in the " -"graph (they would have been returned in the same call to :meth:" -"`~TopologicalSorter.get_ready`) and the order between them is determined by " -"the order of insertion." +"graph (they would have been returned in the same call " +"to :meth:`~TopologicalSorter.get_ready`) and the order between them is " +"determined by the order of insertion." msgstr "" #: library/graphlib.rst:192 @@ -291,9 +291,10 @@ msgstr "" #: library/graphlib.rst:207 msgid "" -"The detected cycle can be accessed via the second element in the :attr:" -"`~BaseException.args` attribute of the exception instance and consists in a " -"list of nodes, such that each node is, in the graph, an immediate " -"predecessor of the next node in the list. In the reported list, the first " -"and the last node will be the same, to make it clear that it is cyclic." +"The detected cycle can be accessed via the second element in " +"the :attr:`~BaseException.args` attribute of the exception instance and " +"consists in a list of nodes, such that each node is, in the graph, an " +"immediate predecessor of the next node in the list. In the reported list, " +"the first and the last node will be the same, to make it clear that it is " +"cyclic." msgstr "" diff --git a/library/grp.po b/library/grp.po index 1cd949631..21c8278e4 100644 --- a/library/grp.po +++ b/library/grp.po @@ -104,8 +104,8 @@ msgid "" "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`.)" +"reference and may not be accessible via :func:`getgrnam` " +"or :func:`getgrgid`.)" msgstr "" #: library/grp.rst:40 @@ -114,8 +114,8 @@ msgstr "" #: library/grp.rst:45 msgid "" -"Return the group database entry for the given numeric group ID. :exc:" -"`KeyError` is raised if the entry asked for cannot be found." +"Return the group database entry for the given numeric group " +"ID. :exc:`KeyError` is raised if the entry asked for cannot be found." msgstr "" #: library/grp.rst:48 diff --git a/library/gzip.po b/library/gzip.po index eeb0d4481..4cf52dd09 100644 --- a/library/gzip.po +++ b/library/gzip.po @@ -36,18 +36,18 @@ msgstr "" #: 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`." +"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 "" #: 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." +"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 "" #: library/gzip.rst:26 @@ -62,8 +62,9 @@ msgstr "" #: 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." +"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 "" #: library/gzip.rst:37 @@ -75,8 +76,8 @@ msgstr "" #: library/gzip.rst:41 msgid "" -"The *compresslevel* argument is an integer from 0 to 9, as for the :class:" -"`GzipFile` constructor." +"The *compresslevel* argument is an integer from 0 to 9, as for " +"the :class:`GzipFile` constructor." msgstr "" #: library/gzip.rst:44 @@ -88,8 +89,8 @@ msgstr "" #: 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 " +"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 "" @@ -109,17 +110,17 @@ msgstr "" #: library/gzip.rst:64 msgid "" -"An exception raised for invalid gzip files. It inherits from :exc:" -"`OSError`. :exc:`EOFError` and :exc:`zlib.error` can also be raised for " -"invalid gzip files." +"An exception raised for invalid gzip files. It inherits " +"from :exc:`OSError`. :exc:`EOFError` and :exc:`zlib.error` can also be " +"raised for invalid gzip files." msgstr "" #: library/gzip.rst:72 msgid "" "Constructor for the :class:`GzipFile` class, which simulates most of the " -"methods of a :term:`file object`, with the exception of the :meth:`~io." -"IOBase.truncate` method. At least one of *fileobj* and *filename* must be " -"given a non-trivial value." +"methods of a :term:`file object`, with the exception of " +"the :meth:`~io.IOBase.truncate` method. At least one of *fileobj* and " +"*filename* must be given a non-trivial value." msgstr "" #: library/gzip.rst:77 @@ -177,15 +178,15 @@ 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." +"writing as *fileobj*, and retrieve the resulting memory buffer using " +"the :class:`io.BytesIO` object's :meth:`~io.BytesIO.getvalue` method." msgstr "" #: library/gzip.rst:114 msgid "" ":class:`GzipFile` supports the :class:`io.BufferedIOBase` interface, " -"including iteration and the :keyword:`with` statement. Only the :meth:`~io." -"IOBase.truncate` method isn't implemented." +"including iteration and the :keyword:`with` statement. Only " +"the :meth:`~io.IOBase.truncate` method isn't implemented." msgstr "" #: library/gzip.rst:118 @@ -201,9 +202,10 @@ msgstr "" #: library/gzip.rst:127 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)." +"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 "" #: library/gzip.rst:136 @@ -217,9 +219,9 @@ msgstr "" 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`." +"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 "" #: library/gzip.rst:148 @@ -282,10 +284,10 @@ msgstr "" #: library/gzip.rst:194 msgid "" "Speed is improved by compressing all data at once instead of in a streamed " -"fashion. Calls with *mtime* set to ``0`` are delegated to :func:`zlib." -"compress` for better speed. In this situation the output may contain a gzip " -"header \"OS\" byte value other than 255 \"unknown\" as supplied by the " -"underlying zlib implementation." +"fashion. Calls with *mtime* set to ``0`` are delegated " +"to :func:`zlib.compress` for better speed. In this situation the output may " +"contain a gzip header \"OS\" byte value other than 255 \"unknown\" as " +"supplied by the underlying zlib implementation." msgstr "" #: library/gzip.rst:203 diff --git a/library/hashlib.po b/library/hashlib.po index 6affae605..ca610e8ae 100644 --- a/library/hashlib.po +++ b/library/hashlib.po @@ -37,8 +37,8 @@ msgstr "" #: library/hashlib.rst:33 msgid "" -"If you want the adler32 or crc32 hash functions, they are available in the :" -"mod:`zlib` module." +"If you want the adler32 or crc32 hash functions, they are available in " +"the :mod:`zlib` module." msgstr "" #: library/hashlib.rst:40 @@ -48,39 +48,38 @@ msgstr "" #: library/hashlib.rst:42 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." +"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 "" #: library/hashlib.rst:50 msgid "" "To allow multithreading, the Python :term:`GIL` is released while computing " -"a hash supplied more than 2047 bytes of data at once in its constructor or :" -"meth:`.update` method." +"a hash supplied more than 2047 bytes of data at once in its constructor " +"or :meth:`.update` method." msgstr "" #: library/hashlib.rst:57 msgid "" -"Constructors for hash algorithms that are always present in this module are :" -"func:`sha1`, :func:`sha224`, :func:`sha256`, :func:`sha384`, :func:" -"`sha512`, :func:`sha3_224`, :func:`sha3_256`, :func:`sha3_384`, :func:" -"`sha3_512`, :func:`shake_128`, :func:`shake_256`, :func:`blake2b`, and :func:" -"`blake2s`. :func:`md5` is normally available as well, though it may be " -"missing or blocked if you are using a rare \"FIPS compliant\" build of " -"Python. These correspond to :data:`algorithms_guaranteed`." +"Constructors for hash algorithms that are always present in this module " +"are :func:`sha1`, :func:`sha224`, :func:`sha256`, :func:`sha384`, :func:`sha512`, :func:`sha3_224`, :func:`sha3_256`, :func:`sha3_384`, :func:`sha3_512`, :func:`shake_128`, :func:`shake_256`, :func:`blake2b`, " +"and :func:`blake2s`. :func:`md5` is normally available as well, though it " +"may be missing or blocked if you are using a rare \"FIPS compliant\" build " +"of Python. These correspond to :data:`algorithms_guaranteed`." msgstr "" #: library/hashlib.rst:65 msgid "" -"Additional algorithms may also be available if your Python distribution's :" -"mod:`hashlib` was linked against a build of OpenSSL that provides others. " -"Others *are not guaranteed available* on all installations and will only be " -"accessible by name via :func:`new`. See :data:`algorithms_available`." +"Additional algorithms may also be available if your Python " +"distribution's :mod:`hashlib` was linked against a build of OpenSSL that " +"provides others. Others *are not guaranteed available* on all installations " +"and will only be accessible by name via :func:`new`. " +"See :data:`algorithms_available`." msgstr "" #: library/hashlib.rst:72 @@ -92,9 +91,9 @@ msgstr "" #: 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` were " -"added. :func:`blake2b` and :func:`blake2s` were added." +"SHA3 (Keccak) and SHAKE " +"constructors :func:`sha3_224`, :func:`sha3_256`, :func:`sha3_384`, :func:`sha3_512`, :func:`shake_128`, :func:`shake_256` " +"were added. :func:`blake2b` and :func:`blake2s` were added." msgstr "" #: library/hashlib.rst:84 @@ -135,8 +134,7 @@ msgid "" ">>> m.update(b\" the spammish repetition\")\n" ">>> m.digest()\n" "b'\\x03\\x1e\\xdd}Ae\\x15\\x93\\xc5\\xfe\\\\" -"\\x00o\\xa5u+7\\xfd\\xdf\\xf7\\xbcN\\x84:" -"\\xa6\\xaf\\x0c\\x95\\x0fK\\x94\\x06'\n" +"\\x00o\\xa5u+7\\xfd\\xdf\\xf7\\xbcN\\x84:\\xa6\\xaf\\x0c\\x95\\x0fK\\x94\\x06'\n" ">>> m.hexdigest()\n" "'031edd7d41651593c5fe5c006fa5752b37fddff7bc4e843aa6af0c950f4b9406'" msgstr "" @@ -186,8 +184,8 @@ msgstr "" #: library/hashlib.rst:167 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 " +"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 "" @@ -429,8 +427,8 @@ msgstr "" #: library/hashlib.rst:385 msgid "" -"Hash objects from this module follow the API of standard library's :mod:" -"`hashlib` objects." +"Hash objects from this module follow the API of standard " +"library's :mod:`hashlib` objects." msgstr "" #: library/hashlib.rst:390 @@ -623,10 +621,11 @@ msgstr "" #: library/hashlib.rst:506 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:`~hash.update` on " -"the object, and, finally, get the digest out of the object by calling :meth:" -"`~hash.digest` (or :meth:`~hash.hexdigest` for hex-encoded string)." +"calling the appropriate constructor function (:func:`blake2b` " +"or :func:`blake2s`), then update it with the data by " +"calling :meth:`~hash.update` on the object, and, finally, get the digest out " +"of the object by calling :meth:`~hash.digest` (or :meth:`~hash.hexdigest` " +"for hex-encoded string)." msgstr "" #: library/hashlib.rst:519 @@ -666,9 +665,9 @@ msgstr "" #: library/hashlib.rst:574 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." +"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 "" #: library/hashlib.rst:580 diff --git a/library/heapq.po b/library/heapq.po index 2c9a53daa..fcbdf0826 100644 --- a/library/heapq.po +++ b/library/heapq.po @@ -99,8 +99,8 @@ msgstr "" #: library/heapq.rst:71 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." +"*item*. The heap size doesn't change. If the heap is " +"empty, :exc:`IndexError` is raised." msgstr "" #: library/heapq.rst:74 @@ -175,17 +175,17 @@ 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 *iterable* (for " -"example, ``key=str.lower``). Equivalent to: ``sorted(iterable, key=key)[:" -"n]``." +"example, ``key=str.lower``). Equivalent to: ``sorted(iterable, key=key)" +"[:n]``." msgstr "" #: library/heapq.rst:130 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." +"``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 "" #: library/heapq.rst:138 diff --git a/library/hmac.po b/library/hmac.po index 253d4ddc3..ce00097b9 100644 --- a/library/hmac.po +++ b/library/hmac.po @@ -55,8 +55,8 @@ msgid "" "Return digest of *msg* for given secret *key* and *digest*. The function is " "equivalent to ``HMAC(key, msg, digest).digest()``, but uses an optimized C " "or inline implementation, which is faster for messages that fit into memory. " -"The parameters *key*, *msg*, and *digest* have the same meaning as in :func:" -"`~hmac.new`." +"The parameters *key*, *msg*, and *digest* have the same meaning as " +"in :func:`~hmac.new`." msgstr "" #: library/hmac.rst:43 @@ -73,8 +73,8 @@ msgstr "" #: library/hmac.rst:54 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)``." +"single call with the concatenation of all the arguments: ``m.update(a); " +"m.update(b)`` is equivalent to ``m.update(a + b)``." msgstr "" #: library/hmac.rst:58 @@ -92,9 +92,9 @@ msgstr "" #: library/hmac.rst:71 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." +"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 "" #: library/hmac.rst:79 @@ -107,9 +107,9 @@ msgstr "" #: library/hmac.rst:85 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." +"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 "" #: library/hmac.rst:93 @@ -150,8 +150,8 @@ 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`." +"either :class:`str` (ASCII only, as e.g. returned " +"by :meth:`HMAC.hexdigest`), or a :term:`bytes-like object`." msgstr "" #: library/hmac.rst:132 diff --git a/library/html.entities.po b/library/html.entities.po index 72c969c0f..1995dee2a 100644 --- a/library/html.entities.po +++ b/library/html.entities.po @@ -26,8 +26,9 @@ msgstr "" #: library/html.entities.rst:13 msgid "" -"This module defines four dictionaries, :data:`html5`, :data:" -"`name2codepoint`, :data:`codepoint2name`, and :data:`entitydefs`." +"This module defines four " +"dictionaries, :data:`html5`, :data:`name2codepoint`, :data:`codepoint2name`, " +"and :data:`entitydefs`." msgstr "" #: library/html.entities.rst:19 @@ -36,8 +37,8 @@ msgid "" "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`." +"case the name is present with and without the ``';'``. See " +"also :func:`html.unescape`." msgstr "" #: library/html.entities.rst:31 diff --git a/library/html.parser.po b/library/html.parser.po index dd75102f1..ace6cc54c 100644 --- a/library/html.parser.po +++ b/library/html.parser.po @@ -71,9 +71,9 @@ msgstr "" #: 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::" +"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 "" #: library/html.parser.rst:48 @@ -126,8 +126,8 @@ msgstr "" #: 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`." +"complete elements; incomplete data is buffered until more data is fed " +"or :meth:`close` is called. *data* must be :class:`str`." msgstr "" #: library/html.parser.rst:97 @@ -160,8 +160,8 @@ msgstr "" 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`):" +"class implementations do nothing (except " +"for :meth:`~HTMLParser.handle_startendtag`):" msgstr "" #: library/html.parser.rst:129 @@ -182,8 +182,8 @@ msgstr "" #: library/html.parser.rst:137 msgid "" "For instance, for the tag ````, this method " -"would be called as ``handle_starttag('a', [('href', 'https://www.cwi." -"nl/')])``." +"would be called as ``handle_starttag('a', [('href', 'https://" +"www.cwi.nl/')])``." msgstr "" #: library/html.parser.rst:140 @@ -206,8 +206,8 @@ 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`." +"implementation simply calls :meth:`handle_starttag` " +"and :meth:`handle_endtag`." msgstr "" #: library/html.parser.rst:161 @@ -347,8 +347,8 @@ msgstr "" msgid "" ">>> parser.feed('')\n" -"Decl : DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01//EN\" \"http://www.w3." -"org/TR/html4/strict.dtd\"" +"Decl : DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01//EN\" \"http://" +"www.w3.org/TR/html4/strict.dtd\"" msgstr "" #: library/html.parser.rst:275 @@ -419,8 +419,8 @@ msgstr "" #: 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 " +"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 "" diff --git a/library/html.po b/library/html.po index bbe2f7590..9c68eca4b 100644 --- a/library/html.po +++ b/library/html.po @@ -39,11 +39,11 @@ msgstr "" #: library/html.rst:26 msgid "" -"Convert all named and numeric character references (e.g. ``>``, ``>" -"``, ``>``) 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 `." +"Convert all named and numeric character references (e.g. ``>``, " +"``>``, ``>``) 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 "" #: library/html.rst:36 diff --git a/library/http.client.po b/library/http.client.po index 2869c5afd..636d17e67 100644 --- a/library/http.client.po +++ b/library/http.client.po @@ -27,8 +27,8 @@ msgstr "" #: library/http.client.rst:17 msgid "" "This module defines classes that 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." +"HTTPS protocols. It is normally not used directly --- the " +"module :mod:`urllib.request` uses it to handle URLs that use HTTP and HTTPS." msgstr "" #: library/http.client.rst:23 @@ -118,8 +118,8 @@ msgstr "" #: library/http.client.rst:84 msgid "" -"This class now supports HTTPS virtual hosts if possible (that is, if :const:" -"`ssl.HAS_SNI` is true)." +"This class now supports HTTPS virtual hosts if possible (that is, " +"if :const:`ssl.HAS_SNI` is true)." msgstr "" #: library/http.client.rst:88 @@ -131,8 +131,8 @@ msgstr "" #: library/http.client.rst:92 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." +"default. To revert to the previous, unverified, behavior :func:`!" +"ssl._create_unverified_context` can be passed to the *context* parameter." msgstr "" #: library/http.client.rst:98 @@ -145,8 +145,8 @@ msgstr "" #: library/http.client.rst:103 msgid "" "This class now sends an ALPN extension with protocol indicator ``http/1.1`` " -"when no *context* is given. Custom *context* should set ALPN protocols with :" -"meth:`~ssl.SSLContext.set_alpn_protocols`." +"when no *context* is given. Custom *context* should set ALPN protocols " +"with :meth:`~ssl.SSLContext.set_alpn_protocols`." msgstr "" #: library/http.client.rst:108 @@ -181,9 +181,10 @@ msgstr "" #: library/http.client.rst:130 msgid "" "This function returns an instance of :class:`http.client.HTTPMessage` that " -"holds the header fields, but no payload (the same as :attr:`HTTPResponse." -"msg` and :attr:`http.server.BaseHTTPRequestHandler.headers`). After " -"returning, the file pointer *fp* is ready to read the HTTP body." +"holds the header fields, but no payload (the same " +"as :attr:`HTTPResponse.msg` " +"and :attr:`http.server.BaseHTTPRequestHandler.headers`). After returning, " +"the file pointer *fp* is ready to read the HTTP body." msgstr "" #: library/http.client.rst:137 @@ -200,8 +201,8 @@ msgstr "" #: library/http.client.rst:147 msgid "" -"The base class of the other exceptions in this module. It is a subclass of :" -"exc:`Exception`." +"The base class of the other exceptions in this module. It is a subclass " +"of :exc:`Exception`." msgstr "" #: library/http.client.rst:164 library/http.client.rst:174 @@ -290,16 +291,16 @@ msgstr "" #: library/http.client.rst:262 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 " +"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." +"``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 "" #: library/http.client.rst:274 @@ -382,9 +383,9 @@ msgstr "" #: library/http.client.rst:334 msgid "" -"If a :exc:`ConnectionError` or subclass is raised, the :class:" -"`HTTPConnection` object will be ready to reconnect when a new request is " -"sent." +"If a :exc:`ConnectionError` or subclass is raised, " +"the :class:`HTTPConnection` object will be ready to reconnect when a new " +"request is sent." msgstr "" #: library/http.client.rst:342 @@ -517,11 +518,11 @@ msgid "" "*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.abc.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*." +"encoding will result in a single chunk. If *message_body* is " +"a :class:`collections.abc.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 "" #: library/http.client.rst:459 @@ -538,8 +539,9 @@ msgstr "" #: library/http.client.rst:470 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." +"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 "" #: library/http.client.rst:474 @@ -594,8 +596,8 @@ msgstr "" #: library/http.client.rst:520 msgid "" "A :class:`http.client.HTTPMessage` instance containing the response " -"headers. :class:`http.client.HTTPMessage` is a subclass of :class:`email." -"message.Message`." +"headers. :class:`http.client.HTTPMessage` is a subclass " +"of :class:`email.message.Message`." msgstr "" #: library/http.client.rst:526 @@ -611,8 +613,8 @@ msgstr "" #: library/http.client.rst:534 msgid "" -"Headers of the response in the form of an :class:`email.message." -"EmailMessage` instance." +"Headers of the response in the form of " +"an :class:`email.message.EmailMessage` instance." msgstr "" #: library/http.client.rst:538 @@ -718,8 +720,8 @@ msgid "" "302 Found\n" ">>> data = response.read()\n" ">>> data\n" -"b'Redirecting to https://bugs." -"python.org/issue12524'\n" +"b'Redirecting to https://" +"bugs.python.org/issue12524'\n" ">>> conn.close()" msgstr "" diff --git a/library/http.cookiejar.po b/library/http.cookiejar.po index 3b4297a28..17fccff3d 100644 --- a/library/http.cookiejar.po +++ b/library/http.cookiejar.po @@ -35,11 +35,11 @@ msgstr "" #: 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 " +"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`` " @@ -48,11 +48,11 @@ msgstr "" #: 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 " +"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." +"Python attributes, the documentation for this module uses the " +"term :dfn:`cookie-attribute` instead." msgstr "" #: library/http.cookiejar.rst:38 @@ -125,8 +125,8 @@ msgid "" "a sequence of the only domains for which we accept and return cookies. " "*secure_protocols* is a sequence of protocols for which secure cookies can " "be added to. By default *https* and *wss* (secure websocket) are considered " -"secure protocols. For all other arguments, see the documentation for :class:" -"`CookiePolicy` and :class:`DefaultCookiePolicy` objects." +"secure protocols. For all other arguments, see the documentation " +"for :class:`CookiePolicy` and :class:`DefaultCookiePolicy` objects." msgstr "" #: library/http.cookiejar.rst:98 @@ -137,17 +137,17 @@ msgid "" "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." +"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 "" #: library/http.cookiejar.rst:111 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." +"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 "" #: library/http.cookiejar.rst:119 @@ -164,8 +164,9 @@ msgstr "" #: library/http.cookiejar.rst:123 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." +"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 "" #: library/http.cookiejar.rst:127 @@ -239,10 +240,10 @@ msgstr "" #: library/http.cookiejar.rst:164 msgid "" "The *request* object (usually a :class:`urllib.request.Request` instance) " -"must support the methods :meth:`get_full_url`, :meth:`has_header`, :meth:" -"`get_header`, :meth:`header_items`, :meth:`add_unredirected_header` and the " -"attributes :attr:`host`, :attr:`!type`, :attr:`unverifiable` and :attr:" -"`origin_req_host` as documented by :mod:`urllib.request`." +"must support the " +"methods :meth:`get_full_url`, :meth:`has_header`, :meth:`get_header`, :meth:`header_items`, :meth:`add_unredirected_header` " +"and the attributes :attr:`host`, :attr:`!type`, :attr:`unverifiable` " +"and :attr:`origin_req_host` as documented by :mod:`urllib.request`." msgstr "" #: library/http.cookiejar.rst:198 @@ -253,32 +254,34 @@ msgstr "" #: library/http.cookiejar.rst:178 msgid "" -"Extract cookies from HTTP *response* and store them in the :class:" -"`CookieJar`, where allowed by policy." +"Extract cookies from HTTP *response* and store them in " +"the :class:`CookieJar`, where allowed by policy." msgstr "" #: library/http.cookiejar.rst:181 msgid "" -"The :class:`CookieJar` will look for allowable :mailheader:`Set-Cookie` and :" -"mailheader:`Set-Cookie2` headers in the *response* argument, and store " +"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 "" #: library/http.cookiejar.rst:185 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." +"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 "" #: library/http.cookiejar.rst:189 msgid "" "The *request* object (usually a :class:`urllib.request.Request` instance) " -"must support the method :meth:`get_full_url` and the attributes :attr:" -"`host`, :attr:`unverifiable` and :attr:`origin_req_host`, 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." +"must support the method :meth:`get_full_url` and the " +"attributes :attr:`host`, :attr:`unverifiable` and :attr:`origin_req_host`, " +"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 "" #: library/http.cookiejar.rst:203 @@ -360,8 +363,8 @@ msgstr "" 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." +"passed to the constructor, if any); if :attr:`self.filename` " +"is :const:`None`, :exc:`ValueError` is raised." msgstr "" #: library/http.cookiejar.rst:265 @@ -373,8 +376,8 @@ msgstr "" #: library/http.cookiejar.rst:268 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." +"contains. Saved cookies can be restored later using the :meth:`load` " +"or :meth:`revert` methods." msgstr "" #: library/http.cookiejar.rst:275 @@ -391,9 +394,9 @@ msgstr "" #: library/http.cookiejar.rst:281 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." +"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 "" #: library/http.cookiejar.rst:285 @@ -492,8 +495,8 @@ msgstr "" #: library/http.cookiejar.rst:366 msgid "" "*cookie* is a :class:`Cookie` instance. *request* is an object implementing " -"the interface defined by the documentation for :meth:`CookieJar." -"extract_cookies`." +"the interface defined by the documentation " +"for :meth:`CookieJar.extract_cookies`." msgstr "" #: library/http.cookiejar.rst:373 @@ -504,8 +507,8 @@ msgstr "" #: library/http.cookiejar.rst:375 msgid "" "*cookie* is a :class:`Cookie` instance. *request* is an object implementing " -"the interface defined by the documentation for :meth:`CookieJar." -"add_cookie_header`." +"the interface defined by the documentation " +"for :meth:`CookieJar.add_cookie_header`." msgstr "" #: library/http.cookiejar.rst:382 @@ -523,12 +526,13 @@ msgstr "" #: library/http.cookiejar.rst:389 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." +"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 "" #: library/http.cookiejar.rst:396 @@ -553,10 +557,10 @@ msgstr "" #: library/http.cookiejar.rst:410 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." +"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 "" #: library/http.cookiejar.rst:418 @@ -630,8 +634,8 @@ msgid "" "A domain blocklist and allowlist is provided (both off by default). Only " "domains not in the blocklist and present in the allowlist (if the allowlist " "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 " +"*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 an allowlist, you can turn it " "off again by setting it to :const:`None`." msgstr "" @@ -642,11 +646,12 @@ msgid "" "cookie domain to be matched. For example, ``\"example.com\"`` matches a " "blocklist 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." +"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 "" #: library/http.cookiejar.rst:483 @@ -694,10 +699,10 @@ 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." +"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 "" #: library/http.cookiejar.rst:532 @@ -757,8 +762,8 @@ msgstr "" #: library/http.cookiejar.rst:580 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`` " +"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 "" @@ -814,10 +819,10 @@ msgstr "" #: library/http.cookiejar.rst:630 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." +"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 "" #: library/http.cookiejar.rst:638 @@ -830,8 +835,8 @@ msgstr "" #: library/http.cookiejar.rst:648 msgid "" -"String representing a port or a set of ports (eg. '80', or '80,8080'), or :" -"const:`None`." +"String representing a port or a set of ports (eg. '80', or '80,8080'), " +"or :const:`None`." msgstr "" #: library/http.cookiejar.rst:654 @@ -848,8 +853,8 @@ msgstr "" #: library/http.cookiejar.rst:669 msgid "" -"Integer expiry date in seconds since epoch, or :const:`None`. See also the :" -"meth:`is_expired` method." +"Integer expiry date in seconds since epoch, or :const:`None`. See also " +"the :meth:`is_expired` method." msgstr "" #: library/http.cookiejar.rst:675 @@ -858,8 +863,8 @@ msgstr "" #: library/http.cookiejar.rst:680 msgid "" -"String comment from the server explaining the function of this cookie, or :" -"const:`None`." +"String comment from the server explaining the function of this cookie, " +"or :const:`None`." msgstr "" #: library/http.cookiejar.rst:686 @@ -937,8 +942,8 @@ msgstr "" msgid "" "import http.cookiejar, urllib.request\n" "cj = http.cookiejar.CookieJar()\n" -"opener = urllib.request.build_opener(urllib.request." -"HTTPCookieProcessor(cj))\n" +"opener = " +"urllib.request.build_opener(urllib.request.HTTPCookieProcessor(cj))\n" "r = opener.open(\"http://example.com/\")" msgstr "" @@ -953,10 +958,10 @@ msgstr "" msgid "" "import os, http.cookiejar, urllib.request\n" "cj = http.cookiejar.MozillaCookieJar()\n" -"cj.load(os.path.join(os.path.expanduser(\"~\"), \".netscape\", \"cookies." -"txt\"))\n" -"opener = urllib.request.build_opener(urllib.request." -"HTTPCookieProcessor(cj))\n" +"cj.load(os.path.join(os.path.expanduser(\"~\"), \".netscape\", " +"\"cookies.txt\"))\n" +"opener = " +"urllib.request.build_opener(urllib.request.HTTPCookieProcessor(cj))\n" "r = opener.open(\"http://example.com/\")" msgstr "" @@ -976,7 +981,7 @@ msgid "" " rfc2965=True, strict_ns_domain=Policy.DomainStrict,\n" " blocked_domains=[\"ads.net\", \".ads.net\"])\n" "cj = CookieJar(policy)\n" -"opener = urllib.request.build_opener(urllib.request." -"HTTPCookieProcessor(cj))\n" +"opener = " +"urllib.request.build_opener(urllib.request.HTTPCookieProcessor(cj))\n" "r = opener.open(\"http://example.com/\")" msgstr "" diff --git a/library/http.cookies.po b/library/http.cookies.po index e7fdce535..1a09c5479 100644 --- a/library/http.cookies.po +++ b/library/http.cookies.po @@ -34,12 +34,12 @@ msgstr "" #: 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 didn't follow the character rules outlined in those specs; many " -"current-day browsers and servers have also relaxed parsing rules when it " -"comes to cookie handling. As a result, this module now uses parsing rules " -"that are a bit less strict than they once were." +"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 didn't follow the character rules outlined in " +"those specs; many current-day browsers and servers have also relaxed parsing " +"rules when it comes to cookie handling. As a result, this module now uses " +"parsing rules that are a bit less strict than they once were." msgstr "" #: library/http.cookies.rst:26 @@ -80,11 +80,12 @@ msgstr "" #: library/http.cookies.rst:58 msgid "" -"This class derives from :class:`BaseCookie` and overrides :meth:`~BaseCookie." -"value_decode` and :meth:`~BaseCookie.value_encode`. :class:`!SimpleCookie` " -"supports strings as cookie values. When setting the value, :class:`!" -"SimpleCookie` calls the builtin :func:`str` to convert the value to a " -"string. Values received from HTTP are kept as strings." +"This class derives from :class:`BaseCookie` and " +"overrides :meth:`~BaseCookie.value_decode` " +"and :meth:`~BaseCookie.value_encode`. :class:`!SimpleCookie` supports " +"strings as cookie values. When setting the value, :class:`!SimpleCookie` " +"calls the builtin :func:`str` to convert the value to a string. Values " +"received from HTTP are kept as strings." msgstr "" #: library/http.cookies.rst:66 @@ -93,8 +94,8 @@ msgstr "" #: library/http.cookies.rst:67 msgid "" -"HTTP cookie handling for web *clients*. The :mod:`http.cookiejar` and :mod:" -"`http.cookies` modules do not depend on each other." +"HTTP cookie handling for web *clients*. The :mod:`http.cookiejar` " +"and :mod:`http.cookies` modules do not depend on each other." msgstr "" #: library/http.cookies.rst:70 @@ -112,8 +113,8 @@ msgstr "" #: library/http.cookies.rst:82 msgid "" "Return a tuple ``(real_value, coded_value)`` from a string representation. " -"``real_value`` can be any type. This method does no decoding in :class:" -"`BaseCookie` --- it exists so it can be overridden." +"``real_value`` can be any type. This method does no decoding " +"in :class:`BaseCookie` --- it exists so it can be overridden." msgstr "" #: library/http.cookies.rst:89 @@ -125,8 +126,8 @@ msgstr "" #: library/http.cookies.rst:94 msgid "" -"In general, it should be the case that :meth:`value_encode` and :meth:" -"`value_decode` are inverses on the range of *value_decode*." +"In general, it should be the case that :meth:`value_encode` " +"and :meth:`value_decode` are inverses on the range of *value_decode*." msgstr "" #: library/http.cookies.rst:100 @@ -200,8 +201,9 @@ msgstr "" #: library/http.cookies.rst:160 msgid "" -"Attributes :attr:`~Morsel.key`, :attr:`~Morsel.value` and :attr:`~Morsel." -"coded_value` are read-only. Use :meth:`~Morsel.set` for setting them." +"Attributes :attr:`~Morsel.key`, :attr:`~Morsel.value` " +"and :attr:`~Morsel.coded_value` are read-only. Use :meth:`~Morsel.set` for " +"setting them." msgstr "" #: library/http.cookies.rst:165 diff --git a/library/http.po b/library/http.po index d355d1a56..9918cd517 100644 --- a/library/http.po +++ b/library/http.po @@ -38,8 +38,8 @@ msgstr "" #: library/http.rst:20 msgid "" -":mod:`http.server` contains basic HTTP server classes based on :mod:" -"`socketserver`" +":mod:`http.server` contains basic HTTP server classes based " +"on :mod:`socketserver`" msgstr "" #: library/http.rst:21 @@ -92,8 +92,8 @@ msgstr "" #: library/http.rst:55 msgid "" "Supported, `IANA-registered status codes `_ available in :class:`http." -"HTTPStatus` are:" +"http-status-codes/http-status-codes.xhtml>`_ available " +"in :class:`http.HTTPStatus` are:" msgstr "" #: library/http.rst:60 diff --git a/library/http.server.po b/library/http.server.po index 5331d8808..3d607f842 100644 --- a/library/http.server.po +++ b/library/http.server.po @@ -30,8 +30,8 @@ msgstr "" #: library/http.server.rst:22 msgid "" -":mod:`http.server` is not recommended for production. It only implements :" -"ref:`basic security checks `." +":mod:`http.server` is not recommended for production. It only " +"implements :ref:`basic security checks `." msgstr "" #: includes/wasm-notavail.rst:3 @@ -63,9 +63,9 @@ msgstr "" #: library/http.server.rst:39 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." +"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 "" #: library/http.server.rst:46 @@ -87,9 +87,9 @@ msgstr "" 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." +"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 "" #: library/http.server.rst:66 @@ -126,9 +126,9 @@ msgstr "" #: library/http.server.rst:92 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." +"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 "" #: library/http.server.rst:99 @@ -186,9 +186,9 @@ msgstr "" #: library/http.server.rst:144 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'``." +"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 "" #: library/http.server.rst:150 @@ -219,8 +219,8 @@ msgstr "" #: library/http.server.rst:172 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`." +"headers. Typically, this is not overridden, and it defaults " +"to :class:`http.client.HTTPMessage`." msgstr "" #: library/http.server.rst:178 @@ -301,8 +301,8 @@ 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." +"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 "" #: library/http.server.rst:250 @@ -351,15 +351,15 @@ msgstr "" 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." +"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 "" #: library/http.server.rst:301 msgid "" -"Returns the server software's version string. This is a combination of the :" -"attr:`server_version` and :attr:`sys_version` attributes." +"Returns the server software's version string. This is a combination of " +"the :attr:`server_version` and :attr:`sys_version` attributes." msgstr "" #: library/http.server.rst:306 @@ -404,15 +404,15 @@ msgstr "" #: library/http.server.rst:337 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." +"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 "" #: library/http.server.rst:341 msgid "" -"The following are defined as class-level attributes of :class:" -"`SimpleHTTPRequestHandler`:" +"The following are defined as class-level attributes " +"of :class:`SimpleHTTPRequestHandler`:" msgstr "" #: library/http.server.rst:346 @@ -457,9 +457,9 @@ 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." +"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 "" #: library/http.server.rst:379 @@ -489,8 +489,8 @@ msgstr "" #: library/http.server.rst:395 msgid "" -"For example usage, see the implementation of the ``test`` function in :" -"source:`Lib/http/server.py`." +"For example usage, see the implementation of the ``test`` function " +"in :source:`Lib/http/server.py`." msgstr "" #: library/http.server.rst:398 @@ -683,10 +683,10 @@ msgstr "" #: library/http.server.rst:527 msgid "" "Earlier versions of Python did not scrub control characters from the log " -"messages emitted to stderr from ``python -m http.server`` or the default :" -"class:`BaseHTTPRequestHandler` ``.log_message`` implementation. This could " -"allow remote clients connecting to your server to send nefarious control " -"codes to your terminal." +"messages emitted to stderr from ``python -m http.server`` or the " +"default :class:`BaseHTTPRequestHandler` ``.log_message`` implementation. " +"This could allow remote clients connecting to your server to send nefarious " +"control codes to your terminal." msgstr "" #: library/http.server.rst:533 diff --git a/library/idle.po b/library/idle.po index fbb500c1a..fefdfd118 100644 --- a/library/idle.po +++ b/library/idle.po @@ -324,8 +324,9 @@ msgstr "" #: library/idle.rst:153 msgid "" -"Open a scrollable list allowing selection of existing names. See :ref:" -"`Completions ` in the Editing and navigation section below." +"Open a scrollable list allowing selection of existing names. " +"See :ref:`Completions ` in the Editing and navigation section " +"below." msgstr "" #: library/idle.rst:156 @@ -907,11 +908,11 @@ msgid "" "attributes of classes or functions, or filenames. Each request method " "displays a completion box with existing names. (See tab completions below " "for an exception.) For any box, change the name being completed and the item " -"highlighted in the box by typing and deleting characters; by hitting :kbd:" -"`Up`, :kbd:`Down`, :kbd:`PageUp`, :kbd:`PageDown`, :kbd:`Home`, and :kbd:" -"`End` keys; and by a single click within the box. Close the box with :kbd:" -"`Escape`, :kbd:`Enter`, and double :kbd:`Tab` keys or clicks outside the " -"box. A double click within the box selects and closes." +"highlighted in the box by typing and deleting characters; by " +"hitting :kbd:`Up`, :kbd:`Down`, :kbd:`PageUp`, :kbd:`PageDown`, :kbd:`Home`, " +"and :kbd:`End` keys; and by a single click within the box. Close the box " +"with :kbd:`Escape`, :kbd:`Enter`, and double :kbd:`Tab` keys or clicks " +"outside the box. A double click within the box selects and closes." msgstr "" #: library/idle.rst:492 @@ -920,21 +921,21 @@ msgid "" "interval. This defaults to 2 seconds; customize it in the settings dialog. " "(To prevent auto popups, set the delay to a large number of milliseconds, " "such as 100000000.) For imported module names or class or function " -"attributes, type '.'. For filenames in the root directory, type :data:`os." -"sep` or :data:`os.altsep` immediately after an opening quote. (On Windows, " -"one can specify a drive first.) Move into subdirectories by typing a " -"directory name and a separator." +"attributes, type '.'. For filenames in the root directory, " +"type :data:`os.sep` or :data:`os.altsep` immediately after an opening " +"quote. (On Windows, one can specify a drive first.) Move into " +"subdirectories by typing a directory name and a separator." msgstr "" #: library/idle.rst:502 msgid "" "Instead of waiting, or after a box is closed, open a completion box " -"immediately with Show Completions on the Edit menu. The default hot key is :" -"kbd:`C-space`. If one types a prefix for the desired name before opening " -"the box, the first match or near miss is made visible. The result is the " -"same as if one enters a prefix after the box is displayed. Show Completions " -"after a quote completes filenames in the current directory instead of a root " -"directory." +"immediately with Show Completions on the Edit menu. The default hot key " +"is :kbd:`C-space`. If one types a prefix for the desired name before " +"opening the box, the first match or near miss is made visible. The result is " +"the same as if one enters a prefix after the box is displayed. Show " +"Completions after a quote completes filenames in the current directory " +"instead of a root directory." msgstr "" #: library/idle.rst:510 @@ -1051,9 +1052,9 @@ msgstr "" #: library/idle.rst:587 msgid "" "Submit a single-line statement for execution by hitting :kbd:`Return` with " -"the cursor anywhere on the line. If a line is extended with Backslash (:kbd:" -"`\\\\`), the cursor must be on the last physical line. Submit a multi-line " -"compound statement by entering a blank line after the statement." +"the cursor anywhere on the line. If a line is extended with Backslash " +"(:kbd:`\\\\`), the cursor must be on the last physical line. Submit a multi-" +"line compound statement by entering a blank line after the statement." msgstr "" #: library/idle.rst:593 @@ -1116,11 +1117,11 @@ msgstr "" #: library/idle.rst:628 msgid "" -"IDLE also highlights the :ref:`soft keywords ` :keyword:" -"`match`, :keyword:`case `, and :keyword:`_ ` in " -"pattern-matching statements. However, this highlighting is not perfect and " -"will be incorrect in some rare cases, including some ``_``-s in ``case`` " -"patterns." +"IDLE also highlights the :ref:`soft keywords ` :keyword:`match`, :keyword:`case `, and :keyword:`_ " +"` in pattern-matching statements. However, this " +"highlighting is not perfect and will be incorrect in some rare cases, " +"including some ``_``-s in ``case`` patterns." msgstr "" #: library/idle.rst:634 @@ -1138,13 +1139,13 @@ msgstr "" #: library/idle.rst:643 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." +"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 "" #: library/idle.rst:651 @@ -1182,10 +1183,10 @@ msgstr "" #: library/idle.rst:676 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." +"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 "" #: library/idle.rst:681 @@ -1256,8 +1257,8 @@ msgstr "" #: library/idle.rst:726 msgid "" -"When IDLE first starts, it attempts to read user configuration files in ``~/." -"idlerc/`` (~ is one's home directory). If there is a problem, an error " +"When IDLE first starts, it attempts to read user configuration files in " +"``~/.idlerc/`` (~ is one's home directory). If there is a problem, an error " "message should be displayed. Leaving aside random disk glitches, this can " "be prevented by never editing the files by hand. Instead, use the " "configuration dialog, under Options. Once there is an error in a user " @@ -1301,8 +1302,8 @@ msgid "" "user interface process that runs the shell and editor. In the execution " "process, it replaces ``sys.stdin``, ``sys.stdout``, and ``sys.stderr`` with " "objects that get input from and send output to the Shell window. The " -"original values stored in ``sys.__stdin__``, ``sys.__stdout__``, and ``sys." -"__stderr__`` are not touched, but may be ``None``." +"original values stored in ``sys.__stdin__``, ``sys.__stdout__``, and " +"``sys.__stderr__`` are not touched, but may be ``None``." msgstr "" #: library/idle.rst:762 @@ -1321,9 +1322,9 @@ msgstr "" msgid "" "IDLE's standard stream replacements are not inherited by subprocesses " "created in the execution process, whether directly by user code or by " -"modules such as multiprocessing. If such subprocess use ``input`` from sys." -"stdin or ``print`` or ``write`` to sys.stdout or sys.stderr, IDLE should be " -"started in a command line window. (On Windows, use ``python`` or ``py`` " +"modules such as multiprocessing. If such subprocess use ``input`` from " +"sys.stdin or ``print`` or ``write`` to sys.stdout or sys.stderr, IDLE should " +"be started in a command line window. (On Windows, use ``python`` or ``py`` " "rather than ``pythonw`` or ``pyw``.) The secondary subprocess will then be " "attached to that window for input and output." msgstr "" @@ -1364,9 +1365,9 @@ msgstr "" #: library/idle.rst:800 msgid "" "When a program outputs text, the result is determined by the corresponding " -"output device. When IDLE executes user code, ``sys.stdout`` and ``sys." -"stderr`` are connected to the display area of IDLE's Shell. Some of its " -"features are inherited from the underlying Tk Text widget. Others are " +"output device. When IDLE executes user code, ``sys.stdout`` and " +"``sys.stderr`` are connected to the display area of IDLE's Shell. Some of " +"its features are inherited from the underlying Tk Text widget. Others are " "programmed additions. Where it matters, Shell is designed for development " "rather than production runs." msgstr "" @@ -1452,13 +1453,13 @@ msgstr "" #: library/idle.rst:861 msgid "" "IDLE is intentionally different from standard Python in order to facilitate " -"development of tkinter programs. Enter ``import tkinter as tk; root = tk." -"Tk()`` in standard Python and nothing appears. Enter the same in IDLE and a " -"tk window appears. In standard Python, one must also enter ``root." -"update()`` to see the window. IDLE does the equivalent in the background, " -"about 20 times a second, which is about every 50 milliseconds. Next enter " -"``b = tk.Button(root, text='button'); b.pack()``. Again, nothing visibly " -"changes in standard Python until one enters ``root.update()``." +"development of tkinter programs. Enter ``import tkinter as tk; root = " +"tk.Tk()`` in standard Python and nothing appears. Enter the same in IDLE " +"and a tk window appears. In standard Python, one must also enter " +"``root.update()`` to see the window. IDLE does the equivalent in the " +"background, about 20 times a second, which is about every 50 milliseconds. " +"Next enter ``b = tk.Button(root, text='button'); b.pack()``. Again, nothing " +"visibly changes in standard Python until one enters ``root.update()``." msgstr "" #: library/idle.rst:870 diff --git a/library/imaplib.po b/library/imaplib.po index 41ede2786..712955fb9 100644 --- a/library/imaplib.po +++ b/library/imaplib.po @@ -26,11 +26,11 @@ msgstr "" #: 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." +"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 "" #: includes/wasm-notavail.rst:3 @@ -64,8 +64,8 @@ msgstr "" #: library/imaplib.rst:44 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.::" +"like this, the IMAP4 ``LOGOUT`` command is issued automatically when " +"the :keyword:`!with` statement exits. E.g.::" msgstr "" #: library/imaplib.rst:48 @@ -139,8 +139,9 @@ msgstr "" #: library/imaplib.rst:106 msgid "" -"The class now supports hostname check with :attr:`ssl.SSLContext." -"check_hostname` and *Server Name Indication* (see :const:`ssl.HAS_SNI`)." +"The class now supports hostname check " +"with :attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* " +"(see :const:`ssl.HAS_SNI`)." msgstr "" #: library/imaplib.rst:114 @@ -154,8 +155,8 @@ msgstr "" #: library/imaplib.rst:122 msgid "" "This is a subclass derived from :class:`IMAP4` that connects to the ``stdin/" -"stdout`` file descriptors created by passing *command* to ``subprocess." -"Popen()``." +"stdout`` file descriptors created by passing *command* to " +"``subprocess.Popen()``." msgstr "" #: library/imaplib.rst:127 @@ -186,9 +187,9 @@ msgid "" "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." +"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 "" #: library/imaplib.rst:159 @@ -322,8 +323,8 @@ msgstr "" #: library/imaplib.rst:264 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`)." +"enabled. Currently only the ``UTF8=ACCEPT`` capability is supported " +"(see :RFC:`6855`)." msgstr "" #: library/imaplib.rst:268 @@ -420,12 +421,12 @@ msgid "" "Opens socket to *port* at *host*. The optional *timeout* parameter specifies " "a timeout in seconds for the connection attempt. If timeout is not given or " "is ``None``, the global default socket timeout is used. Also note that if " -"the *timeout* parameter is set to be zero, it will raise a :class:" -"`ValueError` to reject creating a non-blocking socket. 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." +"the *timeout* parameter is set to be zero, it will raise " +"a :class:`ValueError` to reject creating a non-blocking socket. 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 "" #: library/imaplib.rst:371 @@ -481,8 +482,8 @@ msgid "" "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." +"be ``None`` if the ``UTF8=ACCEPT`` capability was enabled using " +"the :meth:`enable` command." msgstr "" #: library/imaplib.rst:424 @@ -575,8 +576,9 @@ msgstr "" #: library/imaplib.rst:503 msgid "" -"The method now supports hostname check with :attr:`ssl.SSLContext." -"check_hostname` and *Server Name Indication* (see :const:`ssl.HAS_SNI`)." +"The method now supports hostname check " +"with :attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* " +"(see :const:`ssl.HAS_SNI`)." msgstr "" #: library/imaplib.rst:511 @@ -689,8 +691,9 @@ msgstr "" #: library/imaplib.rst:608 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." +"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 "" #: library/imaplib.rst:618 diff --git a/library/imghdr.po b/library/imghdr.po index ac1975679..d9ced914c 100644 --- a/library/imghdr.po +++ b/library/imghdr.po @@ -182,8 +182,9 @@ msgstr "" #: library/imghdr.rst:74 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``." +"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 "" #: library/imghdr.rst:78 diff --git a/library/importlib.metadata.po b/library/importlib.metadata.po index b4badfd25..6ed1884e2 100644 --- a/library/importlib.metadata.po +++ b/library/importlib.metadata.po @@ -45,9 +45,9 @@ msgstr "" #: library/importlib.metadata.rst:27 msgid "" "``importlib.metadata`` operates on third-party *distribution packages* " -"installed into Python's ``site-packages`` directory via tools such as :pypi:" -"`pip`. Specifically, it works with distributions with discoverable ``dist-" -"info`` or ``egg-info`` directories, and metadata defined by the `Core " +"installed into Python's ``site-packages`` directory via tools such " +"as :pypi:`pip`. Specifically, it works with distributions with discoverable " +"``dist-info`` or ``egg-info`` directories, and metadata defined by the `Core " "metadata specifications `_." msgstr "" @@ -58,9 +58,9 @@ msgid "" "level *import package* names that can be imported inside Python code. One " "*distribution package* can contain multiple *import packages* (and single " "modules), and one top-level *import package* may map to multiple " -"*distribution packages* if it is a namespace package. You can use :ref:" -"`package_distributions() ` to get a mapping between " -"them." +"*distribution packages* if it is a namespace package. You can " +"use :ref:`package_distributions() ` to get a mapping " +"between them." msgstr "" #: library/importlib.metadata.rst:47 @@ -79,8 +79,8 @@ msgid "" "The documentation for ``importlib_metadata``, which supplies a backport of " "``importlib.metadata``. This includes an `API reference `__ for this module's classes and " -"functions, as well as a `migration guide `__ for existing users of " +"functions, as well as a `migration guide `__ for existing users of " "``pkg_resources``." msgstr "" @@ -119,8 +119,8 @@ msgstr "" msgid "" "You can also get a collection of entry points selectable by properties of " "the EntryPoint (typically 'group' or 'name'), such as ``console_scripts``, " -"``distutils.commands`` and others. Each group contains a collection of :ref:" -"`EntryPoint ` objects." +"``distutils.commands`` and others. Each group contains a collection " +"of :ref:`EntryPoint ` objects." msgstr "" #: library/importlib.metadata.rst:93 @@ -141,9 +141,9 @@ msgstr "" #: library/importlib.metadata.rst:98 msgid "" -"You can also get a :ref:`distribution's version number `, list its :" -"ref:`constituent files `, and get a list of the distribution's :ref:" -"`requirements`." +"You can also get a :ref:`distribution's version number `, list " +"its :ref:`constituent files `, and get a list of the " +"distribution's :ref:`requirements`." msgstr "" #: library/importlib.metadata.rst:105 @@ -175,10 +175,10 @@ msgstr "" #: library/importlib.metadata.rst:128 msgid "" -"Note: it is not currently possible to query for entry points based on their :" -"attr:`!EntryPoint.dist` attribute (as different :class:`!Distribution` " -"instances do not currently compare equal, even if they have the same " -"attributes)" +"Note: it is not currently possible to query for entry points based on " +"their :attr:`!EntryPoint.dist` attribute (as different :class:`!" +"Distribution` instances do not currently compare equal, even if they have " +"the same attributes)" msgstr "" #: library/importlib.metadata.rst:134 @@ -199,10 +199,10 @@ msgstr "" #: library/importlib.metadata.rst:144 msgid "" "Each :class:`!EntryPoint` instance has ``.name``, ``.group``, and ``.value`` " -"attributes and a ``.load()`` method to resolve the value. There are also ``." -"module``, ``.attr``, and ``.extras`` attributes for getting the components " -"of the ``.value`` attribute, and ``.dist`` for obtaining information " -"regarding the distribution package that provides the entry point." +"attributes and a ``.load()`` method to resolve the value. There are also " +"``.module``, ``.attr``, and ``.extras`` attributes for getting the " +"components of the ``.value`` attribute, and ``.dist`` for obtaining " +"information regarding the distribution package that provides the entry point." msgstr "" #: library/importlib.metadata.rst:150 @@ -308,8 +308,8 @@ msgid "" "3.6 and Python 3.10. Prior to those changes, ``entry_points`` accepted no " "parameters and always returned a dictionary of entry points, keyed by group. " "With ``importlib_metadata`` 5.0 and Python 3.12, ``entry_points`` always " -"returns an ``EntryPoints`` object. See :pypi:`backports." -"entry_points_selectable` for compatibility options." +"returns an ``EntryPoints`` object. " +"See :pypi:`backports.entry_points_selectable` for compatibility options." msgstr "" #: library/importlib.metadata.rst:217 @@ -333,8 +333,8 @@ msgstr "" #: library/importlib.metadata.rst:229 msgid "" "A concrete implementation of the `PackageMetadata protocol `_." +"importlib-metadata.readthedocs.io/en/latest/" +"api.html#importlib_metadata.PackageMetadata>`_." msgstr "" #: library/importlib.metadata.rst:232 @@ -443,10 +443,10 @@ msgstr "" #: library/importlib.metadata.rst:306 msgid "" -"The :func:`!files` function takes a `Distribution Package `_ name and returns " -"all of the files installed by this distribution. Each file is reported as a :" -"class:`PackagePath` instance. For example::" +"The :func:`!files` function takes a `Distribution Package `_ name " +"and returns all of the files installed by this distribution. Each file is " +"reported as a :class:`PackagePath` instance. For example::" msgstr "" #: library/importlib.metadata.rst:311 @@ -492,12 +492,13 @@ msgstr "" #: library/importlib.metadata.rst:338 msgid "" -"In the case where the metadata file listing files (``RECORD`` or ``SOURCES." -"txt``) is missing, :func:`!files` will return :const:`None`. The caller may " -"wish to wrap calls to :func:`!files` in `always_iterable `_ or otherwise guard against this condition if the target " -"distribution is not known to have the metadata present." +"In the case where the metadata file listing files (``RECORD`` or " +"``SOURCES.txt``) is missing, :func:`!files` will return :const:`None`. The " +"caller may wish to wrap calls to :func:`!files` in `always_iterable `_ or otherwise guard against this " +"condition if the target distribution is not known to have the metadata " +"present." msgstr "" #: library/importlib.metadata.rst:349 @@ -542,11 +543,11 @@ msgstr "" #: library/importlib.metadata.rst:383 msgid "" -"A convenience method to resolve the `Distribution Package `_ name (or names, " -"in the case of a namespace package) that provide each importable top-level " -"Python module or `Import Package `_::" +"A convenience method to resolve the `Distribution Package `_ name " +"(or names, in the case of a namespace package) that provide each importable " +"top-level Python module or `Import Package `_::" msgstr "" #: library/importlib.metadata.rst:388 @@ -590,9 +591,9 @@ msgid "" "usage, you can get all of that information from the :class:`!Distribution` " "class. :class:`!Distribution` is an abstract object that represents the " "metadata for a Python `Distribution Package `_. You can get the concreate :" -"class:`!Distribution` subclass instance for an installed distribution " -"package by calling the :func:`distribution` function::" +"latest/glossary/#term-Distribution-Package>`_. You can get the " +"concreate :class:`!Distribution` subclass instance for an installed " +"distribution package by calling the :func:`distribution` function::" msgstr "" #: library/importlib.metadata.rst:425 @@ -636,10 +637,11 @@ msgstr "" #: library/importlib.metadata.rst:451 msgid "" "By default, this package provides built-in support for discovery of metadata " -"for file system and zip file `Distribution Package `_\\s. This metadata " -"finder search defaults to ``sys.path``, but varies slightly in how it " -"interprets those values from how other import machinery does. In particular:" +"for file system and zip file `Distribution Package `_\\s. " +"This metadata finder search defaults to ``sys.path``, but varies slightly in " +"how it interprets those values from how other import machinery does. In " +"particular:" msgstr "" #: library/importlib.metadata.rst:455 @@ -660,12 +662,12 @@ msgstr "" #: library/importlib.metadata.rst:462 msgid "" "Because `Distribution Package `_ metadata is not available through :" -"data:`sys.path` searches, or package loaders directly, the metadata for a " -"distribution is found through import system :ref:`finders `. To find a distribution package's metadata, ``importlib." -"metadata`` queries the list of :term:`meta path finders ` " -"on :data:`sys.meta_path`." +"glossary/#term-Distribution-Package>`_ metadata is not available " +"through :data:`sys.path` searches, or package loaders directly, the metadata " +"for a distribution is found through import system :ref:`finders `. To find a distribution package's metadata, " +"``importlib.metadata`` queries the list of :term:`meta path finders ` on :data:`sys.meta_path`." msgstr "" #: library/importlib.metadata.rst:470 @@ -678,8 +680,8 @@ msgstr "" #: library/importlib.metadata.rst:475 msgid "" "The abstract class :py:class:`importlib.abc.MetaPathFinder` defines the " -"interface expected of finders by Python's import system. ``importlib." -"metadata`` extends this protocol by looking for an optional " +"interface expected of finders by Python's import system. " +"``importlib.metadata`` extends this protocol by looking for an optional " "``find_distributions`` callable on the finders from :data:`sys.meta_path` " "and presents this extended interface as the ``DistributionFinder`` abstract " "base class, which defines this abstract method::" diff --git a/library/importlib.po b/library/importlib.po index 1d1442f70..c22446c0e 100644 --- a/library/importlib.po +++ b/library/importlib.po @@ -84,8 +84,8 @@ msgstr "" #: library/importlib.rst:47 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`)." +"writing of this document (e.g. redirecting based on ``None`` " +"in :data:`sys.modules`)." msgstr "" #: library/importlib.rst:51 @@ -226,11 +226,11 @@ msgstr "" #: library/importlib.rst:115 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__` " +"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 "" @@ -338,11 +338,11 @@ msgstr "" #: library/importlib.rst:193 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." +"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 "" #: library/importlib.rst:199 @@ -355,8 +355,8 @@ msgstr "" #: library/importlib.rst:205 msgid "" -":exc:`ModuleNotFoundError` is raised when the module being reloaded lacks a :" -"class:`~importlib.machinery.ModuleSpec`." +":exc:`ModuleNotFoundError` is raised when the module being reloaded lacks " +"a :class:`~importlib.machinery.ModuleSpec`." msgstr "" #: library/importlib.rst:211 @@ -426,26 +426,27 @@ msgstr "" 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:" -"`importlib.machinery.PathFinder`." +"meant for use only within the path-based import subsystem provided " +"by :class:`importlib.machinery.PathFinder`." msgstr "" #: library/importlib.rst:285 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, " +"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. :" -"func:`importlib.util.spec_from_loader` may be useful for implementing " -"concrete ``PathEntryFinders``." +"the finder may use to make a more educated guess about what spec to " +"return. :func:`importlib.util.spec_from_loader` may be useful for " +"implementing concrete ``PathEntryFinders``." msgstr "" #: library/importlib.rst:297 msgid "" "An optional method which, when called, should invalidate any internal cache " -"used by the finder. Used by :meth:`importlib.machinery.PathFinder." -"invalidate_caches` when invalidating the caches of all cached finders." +"used by the finder. Used " +"by :meth:`importlib.machinery.PathFinder.invalidate_caches` when " +"invalidating the caches of all cached finders." msgstr "" #: library/importlib.rst:305 @@ -456,9 +457,9 @@ msgstr "" #: library/importlib.rst:308 msgid "" -"Loaders that wish to support resource reading should implement a :meth:" -"`get_resource_reader` method as specified by :class:`importlib.resources.abc." -"ResourceReader`." +"Loaders that wish to support resource reading should implement " +"a :meth:`get_resource_reader` method as specified " +"by :class:`importlib.resources.abc.ResourceReader`." msgstr "" #: library/importlib.rst:312 @@ -480,8 +481,8 @@ msgstr "" 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 :meth:`exec_module` is called. When this method exists, :meth:" -"`create_module` must be defined." +"when :meth:`exec_module` is called. When this method " +"exists, :meth:`create_module` must be defined." msgstr "" #: library/importlib.rst:336 @@ -490,8 +491,9 @@ msgstr "" #: library/importlib.rst:341 msgid "" -"A legacy method for loading a module. If the module cannot be loaded, :exc:" -"`ImportError` is raised, otherwise the loaded module is returned." +"A legacy method for loading a module. If the module cannot be " +"loaded, :exc:`ImportError` is raised, otherwise the loaded module is " +"returned." msgstr "" #: library/importlib.rst:345 @@ -549,23 +551,24 @@ msgstr "" #: library/importlib.rst:373 msgid "" -"The recommended API for loading a module is :meth:`exec_module` (and :meth:" -"`create_module`). Loaders should implement it instead of :meth:" -"`load_module`. The import machinery takes care of all the other " +"The recommended API for loading a module is :meth:`exec_module` " +"(and :meth:`create_module`). Loaders should implement it instead " +"of :meth:`load_module`. The import machinery takes care of all the other " "responsibilities of :meth:`load_module` when :meth:`exec_module` is " "implemented." msgstr "" #: library/importlib.rst:383 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." +"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 "" #: library/importlib.rst:387 msgid "" -"This ABC is deprecated in favour of supporting resource loading through :" -"class:`importlib.resources.abc.ResourceReader`." +"This ABC is deprecated in favour of supporting resource loading " +"through :class:`importlib.resources.abc.ResourceReader`." msgstr "" #: library/importlib.rst:393 @@ -574,8 +577,9 @@ msgid "" "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:`~module." -"__file__` attribute or an item from a package's :attr:`~module.__path__`." +"*path* is expected to be constructed using a " +"module's :attr:`~module.__file__` attribute or an item from a " +"package's :attr:`~module.__path__`." msgstr "" #: library/importlib.rst:402 @@ -584,8 +588,8 @@ msgstr "" #: library/importlib.rst:408 msgid "" -"An abstract base class for a :term:`loader` which implements the optional :" -"pep:`302` protocol for loaders that inspect modules." +"An abstract base class for a :term:`loader` which implements the " +"optional :pep:`302` protocol for loaders that inspect modules." msgstr "" #: library/importlib.rst:413 @@ -631,10 +635,10 @@ msgstr "" #: library/importlib.rst:452 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)." +"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 "" #: library/importlib.rst:457 @@ -681,9 +685,9 @@ msgstr "" #: library/importlib.rst:501 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`." +"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 "" #: library/importlib.rst:505 @@ -719,8 +723,8 @@ msgstr "" #: library/importlib.rst:536 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:" +"file loading. The class inherits from both :class:`ResourceLoader` " +"and :class:`ExecutionLoader`, requiring the implementation of:" msgstr "" #: library/importlib.rst:540 @@ -740,9 +744,9 @@ msgstr "" #: library/importlib.rst:545 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* " +"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 " @@ -797,8 +801,9 @@ msgstr "" #: library/importlib.rst:590 msgid "" -"When writing to the path fails because the path is read-only (:const:`errno." -"EACCES`/:exc:`PermissionError`), do not propagate the exception." +"When writing to the path fails because the path is read-only " +"(:const:`errno.EACCES`/:exc:`PermissionError`), do not propagate the " +"exception." msgstr "" #: library/importlib.rst:594 @@ -828,9 +833,9 @@ msgstr "" #: library/importlib.rst:620 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 " +"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 "" @@ -855,9 +860,9 @@ msgstr "" #: library/importlib.rst:642 msgid "" -"For any of methods of this class, a *resource* argument is expected to be a :" -"term:`path-like object` which represents conceptually just a file name. This " -"means that no subdirectory paths should be included in the *resource* " +"For any of methods of this class, a *resource* argument is expected to be " +"a :term:`path-like object` which represents conceptually just a file name. " +"This means that no subdirectory paths should be included in the *resource* " "argument. This is because the location of the package the reader is for, " "acts as the \"directory\". Hence the metaphor for directories and file names " "is packages and resources, respectively. This is also why instances of this " @@ -894,22 +899,22 @@ msgstr "" #: library/importlib.rst:677 msgid "" -"If the resource does not concretely exist on the file system, raise :exc:" -"`FileNotFoundError`." +"If the resource does not concretely exist on the file system, " +"raise :exc:`FileNotFoundError`." msgstr "" #: library/importlib.rst:682 msgid "" -"Returns ``True`` if the named *name* is considered a resource. :exc:" -"`FileNotFoundError` is raised if *name* does not exist." +"Returns ``True`` if the named *name* is considered a " +"resource. :exc:`FileNotFoundError` is raised if *name* does not exist." msgstr "" #: library/importlib.rst:687 msgid "" "Returns an :term:`iterable` of strings over the contents of the package. Do " "note that it is not required that all names returned by the iterator be " -"actual resources, e.g. it is acceptable to return names for which :meth:" -"`is_resource` would be false." +"actual resources, e.g. it is acceptable to return names for " +"which :meth:`is_resource` would be false." msgstr "" #: library/importlib.rst:693 @@ -933,8 +938,8 @@ msgstr "" #: library/importlib.rst:709 msgid "" -"For a representation of the object on the file-system, use :meth:`importlib." -"resources.as_file`." +"For a representation of the object on the file-system, " +"use :meth:`importlib.resources.as_file`." msgstr "" #: library/importlib.rst:714 @@ -973,8 +978,8 @@ msgstr "" #: library/importlib.rst:746 msgid "" -"When opening as text, accepts encoding parameters such as those accepted by :" -"attr:`io.TextIOWrapper`." +"When opening as text, accepts encoding parameters such as those accepted " +"by :attr:`io.TextIOWrapper`." msgstr "" #: library/importlib.rst:751 @@ -987,10 +992,11 @@ msgstr "" #: library/importlib.rst:760 msgid "" -"An abstract base class for resource readers capable of serving the :meth:" -"`importlib.resources.files` interface. Subclasses :class:`importlib." -"resources.abc.ResourceReader` and provides concrete implementations of the :" -"class:`importlib.resources.abc.ResourceReader`'s abstract methods. " +"An abstract base class for resource readers capable of serving " +"the :meth:`importlib.resources.files` interface. " +"Subclasses :class:`importlib.resources.abc.ResourceReader` and provides " +"concrete implementations of " +"the :class:`importlib.resources.abc.ResourceReader`'s abstract methods. " "Therefore, any loader supplying :class:`importlib.abc.TraversableResources` " "also supplies ResourceReader." msgstr "" @@ -1064,15 +1070,16 @@ 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`)." +"module without needing any details on the kind of module (for " +"example, :func:`inspect.getmodulename`)." msgstr "" #: library/importlib.rst:852 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." +"listed in :data:`sys.builtin_module_names`. This class implements " +"the :class:`importlib.abc.MetaPathFinder` " +"and :class:`importlib.abc.InspectLoader` ABCs." msgstr "" #: library/importlib.rst:871 library/importlib.rst:899 @@ -1083,14 +1090,15 @@ msgstr "" #: library/importlib.rst:860 msgid "" -"As part of :pep:`489`, the builtin importer now implements :meth:`Loader." -"create_module` and :meth:`Loader.exec_module`" +"As part of :pep:`489`, the builtin importer now " +"implements :meth:`Loader.create_module` and :meth:`Loader.exec_module`" msgstr "" #: library/importlib.rst:867 msgid "" -"An :term:`importer` for frozen modules. This class implements the :class:" -"`importlib.abc.MetaPathFinder` and :class:`importlib.abc.InspectLoader` ABCs." +"An :term:`importer` for frozen modules. This class implements " +"the :class:`importlib.abc.MetaPathFinder` " +"and :class:`importlib.abc.InspectLoader` ABCs." msgstr "" #: library/importlib.rst:874 @@ -1121,21 +1129,22 @@ msgstr "" 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." +"*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 "" #: library/importlib.rst:918 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`." +"longer valid then ``None`` is returned but no value is cached " +"in :data:`sys.path_importer_cache`." msgstr "" #: library/importlib.rst:925 @@ -1209,8 +1218,8 @@ msgstr "" #: library/importlib.rst:984 msgid "" -"If the argument to the closure is not an existing directory, :exc:" -"`ImportError` is raised." +"If the argument to the closure is not an existing " +"directory, :exc:`ImportError` is raised." msgstr "" #: library/importlib.rst:990 @@ -1318,8 +1327,8 @@ msgstr "" #: library/importlib.rst:1096 msgid "" -"Creates the module object from the given specification in accordance with :" -"pep:`489`." +"Creates the module object from the given specification in accordance " +"with :pep:`489`." msgstr "" #: library/importlib.rst:1103 @@ -1367,14 +1376,14 @@ msgid "" "the *values* are usually equivalent, they can differ since there is no " "synchronization between the two objects. For example, it is possible to " "update the module's :attr:`~module.__file__` at runtime and this will not be " -"automatically reflected in the module's :attr:`__spec__.origin `, and vice versa." +"automatically reflected in the module's :attr:`__spec__.origin " +"`, and vice versa." msgstr "" #: library/importlib.rst:1161 msgid "" -"The module's fully qualified name (see :attr:`module.__name__`). The :term:" -"`finder` should always set this attribute to a non-empty string." +"The module's fully qualified name (see :attr:`module.__name__`). " +"The :term:`finder` should always set this attribute to a non-empty string." msgstr "" #: library/importlib.rst:1166 @@ -1385,11 +1394,12 @@ msgstr "" #: library/importlib.rst:1171 msgid "" -"The location the :term:`loader` should use to load the module (see :attr:" -"`module.__file__`). For example, for modules loaded from a ``.py`` file this " -"is the filename. The :term:`finder` should always set this attribute to a " -"meaningful value for the :term:`loader` to use. In the uncommon case that " -"there is not one (like for namespace packages), it should be set to ``None``." +"The location the :term:`loader` should use to load the module " +"(see :attr:`module.__file__`). For example, for modules loaded from a " +"``.py`` file this is the filename. The :term:`finder` should always set this " +"attribute to a meaningful value for the :term:`loader` to use. In the " +"uncommon case that there is not one (like for namespace packages), it should " +"be set to ``None``." msgstr "" #: library/importlib.rst:1180 @@ -1416,9 +1426,10 @@ msgstr "" #: library/importlib.rst:1199 msgid "" -"The filename of a compiled version of the module's code (see :attr:`module." -"__cached__`). The :term:`finder` should always set this attribute but it may " -"be ``None`` for modules that do not need compiled code stored." +"The filename of a compiled version of the module's code " +"(see :attr:`module.__cached__`). The :term:`finder` should always set this " +"attribute but it may be ``None`` for modules that do not need compiled code " +"stored." msgstr "" #: library/importlib.rst:1206 @@ -1460,9 +1471,9 @@ 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)." +"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 "" #: library/importlib.rst:1248 @@ -1473,9 +1484,9 @@ msgid "" "``/foo/bar/__pycache__/baz.cpython-32.pyc``. ``None`` causes the " "interpreter's optimization level to be used. Any other value's string " "representation is 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." +"``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 "" #: library/importlib.rst:1258 @@ -1500,18 +1511,19 @@ msgstr "" #: library/importlib.rst:1276 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* " +"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 :exc:`ValueError` is raised. If :attr:`sys.implementation." -"cache_tag` is not defined, :exc:`NotImplementedError` is raised." +"format, a :exc:`ValueError` is raised. " +"If :attr:`sys.implementation.cache_tag` is not " +"defined, :exc:`NotImplementedError` is raised." msgstr "" #: library/importlib.rst:1291 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`)." +"with universal newlines (as required " +"by :meth:`importlib.abc.InspectLoader.get_source`)." msgstr "" #: library/importlib.rst:1299 @@ -1521,16 +1533,18 @@ msgstr "" #: library/importlib.rst:1301 msgid "" "If **name** has no leading dots, then **name** is simply returned. This " -"allows for usage such as ``importlib.util.resolve_name('sys', __spec__." -"parent)`` without doing a check to see if the **package** argument is needed." +"allows for usage such as ``importlib.util.resolve_name('sys', " +"__spec__.parent)`` without doing a check to see if the **package** argument " +"is needed." msgstr "" #: library/importlib.rst:1306 msgid "" ":exc:`ImportError` is raised if **name** is a relative module name but " -"**package** is a false value (e.g. ``None`` or the empty string). :exc:" -"`ImportError` is also raised if a relative name would escape its containing " -"package (e.g. requesting ``..bacon`` from within the ``spam`` package)." +"**package** is a false value (e.g. ``None`` or the empty " +"string). :exc:`ImportError` is also raised if a relative name would escape " +"its containing package (e.g. requesting ``..bacon`` from within the ``spam`` " +"package)." msgstr "" #: library/importlib.rst:1314 @@ -1591,9 +1605,9 @@ msgstr "" msgid "" "A factory function for creating a :class:`~importlib.machinery.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." +"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 "" #: library/importlib.rst:1368 @@ -1648,15 +1662,16 @@ msgstr "" #: library/importlib.rst:1415 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 :data:" -"`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." +"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 :data:`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 "" #: library/importlib.rst:1426 @@ -1671,8 +1686,8 @@ msgstr "" #: library/importlib.rst:1434 msgid "" "Began calling :meth:`~importlib.abc.Loader.create_module`, removing the " -"compatibility warning for :class:`importlib.machinery.BuiltinImporter` and :" -"class:`importlib.machinery.ExtensionFileLoader`." +"compatibility warning for :class:`importlib.machinery.BuiltinImporter` " +"and :class:`importlib.machinery.ExtensionFileLoader`." msgstr "" #: library/importlib.rst:1441 @@ -1722,8 +1737,8 @@ msgstr "" #: library/importlib.rst:1473 msgid "" -"Note that if ``name`` is a submodule (contains a dot), :func:`importlib.util." -"find_spec` will import the parent module. ::" +"Note that if ``name`` is a submodule (contains a " +"dot), :func:`importlib.util.find_spec` will import the parent module. ::" msgstr "" #: library/importlib.rst:1477 @@ -1753,11 +1768,11 @@ msgstr "" #: library/importlib.rst:1498 msgid "" "This recipe should be used with caution: it is an approximation of an import " -"statement where the file path is specified directly, rather than :data:`sys." -"path` being searched. Alternatives should first be considered first, such as " -"modifying :data:`sys.path` when a proper module is required, or using :func:" -"`runpy.run_path` when the global namespace resulting from running a Python " -"file is appropriate." +"statement where the file path is specified directly, rather " +"than :data:`sys.path` being searched. Alternatives should first be " +"considered first, such as modifying :data:`sys.path` when a proper module is " +"required, or using :func:`runpy.run_path` when the global namespace " +"resulting from running a Python file is appropriate." msgstr "" #: library/importlib.rst:1505 @@ -1823,16 +1838,17 @@ msgstr "" #: library/importlib.rst:1554 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 :data:`sys.meta_path` while the latter " -"is what you create using a :term:`path entry hook` on :data:`sys.path_hooks` " -"which works with :data:`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)::" +"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 :data:`sys.meta_path` while the latter is what you create using " +"a :term:`path entry hook` on :data:`sys.path_hooks` which works " +"with :data:`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 "" #: library/importlib.rst:1565 diff --git a/library/importlib.resources.abc.po b/library/importlib.resources.abc.po index 350e94841..4c2f69af1 100644 --- a/library/importlib.resources.abc.po +++ b/library/importlib.resources.abc.po @@ -45,9 +45,9 @@ msgstr "" #: library/importlib.resources.abc.rst:28 msgid "" -"For any of methods of this class, a *resource* argument is expected to be a :" -"term:`path-like object` which represents conceptually just a file name. This " -"means that no subdirectory paths should be included in the *resource* " +"For any of methods of this class, a *resource* argument is expected to be " +"a :term:`path-like object` which represents conceptually just a file name. " +"This means that no subdirectory paths should be included in the *resource* " "argument. This is because the location of the package the reader is for, " "acts as the \"directory\". Hence the metaphor for directories and file names " "is packages and resources, respectively. This is also why instances of this " @@ -84,22 +84,22 @@ msgstr "" #: library/importlib.resources.abc.rst:61 msgid "" -"If the resource does not concretely exist on the file system, raise :exc:" -"`FileNotFoundError`." +"If the resource does not concretely exist on the file system, " +"raise :exc:`FileNotFoundError`." msgstr "" #: library/importlib.resources.abc.rst:66 msgid "" -"Returns ``True`` if the named *name* is considered a resource. :exc:" -"`FileNotFoundError` is raised if *name* does not exist." +"Returns ``True`` if the named *name* is considered a " +"resource. :exc:`FileNotFoundError` is raised if *name* does not exist." msgstr "" #: library/importlib.resources.abc.rst:71 msgid "" "Returns an :term:`iterable` of strings over the contents of the package. Do " "note that it is not required that all names returned by the iterator be " -"actual resources, e.g. it is acceptable to return names for which :meth:" -"`is_resource` would be false." +"actual resources, e.g. it is acceptable to return names for " +"which :meth:`is_resource` would be false." msgstr "" #: library/importlib.resources.abc.rst:77 @@ -123,8 +123,8 @@ msgstr "" #: library/importlib.resources.abc.rst:93 msgid "" -"For a representation of the object on the file-system, use :meth:`importlib." -"resources.as_file`." +"For a representation of the object on the file-system, " +"use :meth:`importlib.resources.as_file`." msgstr "" #: library/importlib.resources.abc.rst:98 @@ -145,8 +145,8 @@ msgstr "" #: library/importlib.resources.abc.rst:114 msgid "" -"Traverse directories according to *pathsegments* and return the result as :" -"class:`!Traversable`." +"Traverse directories according to *pathsegments* and return the result " +"as :class:`!Traversable`." msgstr "" #: library/importlib.resources.abc.rst:117 @@ -193,8 +193,8 @@ msgstr "" #: library/importlib.resources.abc.rst:147 msgid "" -"When opening as text, accepts encoding parameters such as those accepted by :" -"class:`io.TextIOWrapper`." +"When opening as text, accepts encoding parameters such as those accepted " +"by :class:`io.TextIOWrapper`." msgstr "" #: library/importlib.resources.abc.rst:152 @@ -207,11 +207,12 @@ msgstr "" #: library/importlib.resources.abc.rst:161 msgid "" -"An abstract base class for resource readers capable of serving the :meth:" -"`importlib.resources.files` interface. Subclasses :class:`ResourceReader` " -"and provides concrete implementations of the :class:`!ResourceReader`'s " -"abstract methods. Therefore, any loader supplying :class:`!" -"TraversableResources` also supplies :class:`!ResourceReader`." +"An abstract base class for resource readers capable of serving " +"the :meth:`importlib.resources.files` interface. " +"Subclasses :class:`ResourceReader` and provides concrete implementations of " +"the :class:`!ResourceReader`'s abstract methods. Therefore, any loader " +"supplying :class:`!TraversableResources` also supplies :class:`!" +"ResourceReader`." msgstr "" #: library/importlib.resources.abc.rst:168 diff --git a/library/importlib.resources.po b/library/importlib.resources.po index c5776acb6..2367f3925 100644 --- a/library/importlib.resources.po +++ b/library/importlib.resources.po @@ -83,8 +83,8 @@ msgstr "" #: library/importlib.resources.rst:55 msgid "" -"Represents an anchor for resources, either a :class:`module object ` or a module name as a string. Defined as ``Union[str, " +"Represents an anchor for resources, either a :class:`module object " +"` or a module name as a string. Defined as ``Union[str, " "ModuleType]``." msgstr "" @@ -107,9 +107,10 @@ msgstr "" msgid "" "*package* parameter was renamed to *anchor*. *anchor* can now be a non-" "package module and if omitted will default to the caller's module. *package* " -"is still accepted for compatibility but will raise a :exc:" -"`DeprecationWarning`. Consider passing the anchor positionally or using " -"``importlib_resources >= 5.10`` for a compatible interface on older Pythons." +"is still accepted for compatibility but will raise " +"a :exc:`DeprecationWarning`. Consider passing the anchor positionally or " +"using ``importlib_resources >= 5.10`` for a compatible interface on older " +"Pythons." msgstr "" #: library/importlib.resources.rst:84 @@ -152,8 +153,8 @@ msgstr "" msgid "" "Whenever a function accepts a ``Package`` argument, you can pass in either " "a :class:`module object ` or a module name as a string. " -"You can only pass module objects whose ``__spec__." -"submodule_search_locations`` is not ``None``." +"You can only pass module objects whose " +"``__spec__.submodule_search_locations`` is not ``None``." msgstr "" #: library/importlib.resources.rst:117 @@ -179,8 +180,8 @@ msgid "" "*package* is either a name or a module object which conforms to the " "``Package`` requirements. *resource* is the name of the resource to open " "within *package*; it may not contain path separators and it may not have sub-" -"resources (i.e. it cannot be a directory). This function returns a ``typing." -"BinaryIO`` instance, a binary I/O stream open for reading." +"resources (i.e. it cannot be a directory). This function returns a " +"``typing.BinaryIO`` instance, a binary I/O stream open for reading." msgstr "" #: library/importlib.resources.rst:143 library/importlib.resources.rst:164 @@ -312,6 +313,6 @@ msgstr "" #: library/importlib.resources.rst:255 msgid "" -"(resource.name for resource in files(package).iterdir() if resource." -"is_file())" +"(resource.name for resource in files(package).iterdir() if " +"resource.is_file())" msgstr "" diff --git a/library/inspect.po b/library/inspect.po index f395bd432..2deed05f1 100644 --- a/library/inspect.po +++ b/library/inspect.po @@ -49,10 +49,10 @@ msgstr "" 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 (see :ref:`import-mod-attrs` for module " -"attributes):" +"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 (see :ref:`import-mod-attrs` for " +"module attributes):" msgstr "" #: library/inspect.rst:46 @@ -659,8 +659,8 @@ msgstr "" msgid "" "Return ``True`` if the object is a :term:`coroutine function` (a function " "defined with an :keyword:`async def` syntax), a :func:`functools.partial` " -"wrapping a :term:`coroutine function`, or a sync function marked with :func:" -"`markcoroutinefunction`." +"wrapping a :term:`coroutine function`, or a sync function marked " +"with :func:`markcoroutinefunction`." msgstr "" #: library/inspect.rst:381 @@ -689,14 +689,14 @@ msgstr "" #: library/inspect.rst:398 msgid "" "When possible, using an :keyword:`async def` function is preferred. Also " -"acceptable is calling the function and testing the return with :func:" -"`iscoroutine`." +"acceptable is calling the function and testing the return " +"with :func:`iscoroutine`." msgstr "" #: library/inspect.rst:407 msgid "" -"Return ``True`` if the object is a :term:`coroutine` created by an :keyword:" -"`async def` function." +"Return ``True`` if the object is a :term:`coroutine` created by " +"an :keyword:`async def` function." msgstr "" #: library/inspect.rst:415 @@ -776,8 +776,9 @@ msgstr "" #: library/inspect.rst:487 msgid "" -"These are instances of :class:`~types.MethodWrapperType`, such as :meth:" -"`~object.__str__`, :meth:`~object.__eq__` and :meth:`~object.__repr__`." +"These are instances of :class:`~types.MethodWrapperType`, such " +"as :meth:`~object.__str__`, :meth:`~object.__eq__` " +"and :meth:`~object.__repr__`." msgstr "" #: library/inspect.rst:495 @@ -792,26 +793,27 @@ msgstr "" #: library/inspect.rst:505 msgid "" -"Return ``True`` if the object is a method descriptor, but not if :func:" -"`ismethod`, :func:`isclass`, :func:`isfunction` or :func:`isbuiltin` are " -"true." +"Return ``True`` if the object is a method descriptor, but not " +"if :func:`ismethod`, :func:`isclass`, :func:`isfunction` " +"or :func:`isbuiltin` are true." msgstr "" #: library/inspect.rst:509 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:`~definition.__doc__` " -"often is." +"method, but beyond that the set of attributes varies. " +"A :attr:`~definition.__name__` attribute is usually sensible, " +"and :attr:`~definition.__doc__` often is." msgstr "" #: library/inspect.rst:515 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:" -"`~method.__func__` attribute (etc) when an object passes :func:`ismethod`." +"the other tests promise more -- you can, e.g., count on having " +"the :attr:`~method.__func__` attribute (etc) when an object " +"passes :func:`ismethod`." msgstr "" #: library/inspect.rst:524 @@ -820,13 +822,14 @@ msgstr "" #: library/inspect.rst:526 msgid "" -"Data descriptors have a :attr:`~object.__set__` or a :attr:`~object." -"__delete__` 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." +"Data descriptors have a :attr:`~object.__set__` or " +"a :attr:`~object.__delete__` 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 "" #: library/inspect.rst:537 @@ -835,9 +838,9 @@ msgstr "" #: library/inspect.rst:541 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``." +"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 "" #: library/inspect.rst:548 @@ -846,9 +849,9 @@ msgstr "" #: library/inspect.rst:552 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``." +"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 "" #: library/inspect.rst:560 @@ -857,11 +860,11 @@ msgstr "" #: library/inspect.rst:564 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. Return ``None`` if the " -"documentation string is invalid or missing." +"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. Return " +"``None`` if the documentation string is invalid or missing." msgstr "" #: library/inspect.rst:570 @@ -981,15 +984,16 @@ msgid "" "For objects defined in modules using stringized annotations (``from " "__future__ import annotations``), :func:`signature` will attempt to " "automatically un-stringize the annotations using :func:`get_annotations`. " -"The *globals*, *locals*, and *eval_str* parameters are passed into :func:" -"`get_annotations` when resolving the annotations; see the documentation for :" -"func:`get_annotations` for instructions on how to use these parameters." +"The *globals*, *locals*, and *eval_str* parameters are passed " +"into :func:`get_annotations` when resolving the annotations; see the " +"documentation for :func:`get_annotations` for instructions on how to use " +"these parameters." msgstr "" #: library/inspect.rst:690 msgid "" -"Raises :exc:`ValueError` if no signature can be provided, and :exc:" -"`TypeError` if that type of object is not supported. Also, if the " +"Raises :exc:`ValueError` if no signature can be provided, " +"and :exc:`TypeError` if that type of object is not supported. Also, if the " "annotations are stringized, and *eval_str* is not false, the ``eval()`` " "call(s) to un-stringize the annotations in :func:`get_annotations` could " "potentially raise any kind of exception." @@ -1066,9 +1070,9 @@ msgstr "" #: library/inspect.rst:751 msgid "" -"An ordered mapping of parameters' names to the corresponding :class:" -"`Parameter` objects. Parameters appear in strict definition order, " -"including keyword-only parameters." +"An ordered mapping of parameters' names to the " +"corresponding :class:`Parameter` objects. Parameters appear in strict " +"definition order, including keyword-only parameters." msgstr "" #: library/inspect.rst:1093 @@ -1101,11 +1105,11 @@ msgstr "" #: library/inspect.rst:780 msgid "" -"Create a new :class:`Signature` instance based on the instance :meth:" -"`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 :class:`!" -"Signature`, pass in :attr:`Signature.empty`." +"Create a new :class:`Signature` instance based on the " +"instance :meth:`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 :class:`!Signature`, pass in :attr:`Signature.empty`." msgstr "" #: library/inspect.rst:788 @@ -1191,8 +1195,9 @@ msgstr "" #: library/inspect.rst:861 msgid "" "Describes how argument values are bound to the parameter. The possible " -"values are accessible via :class:`Parameter` (like ``Parameter." -"KEYWORD_ONLY``), and support comparison and ordering, in the following order:" +"values are accessible via :class:`Parameter` (like " +"``Parameter.KEYWORD_ONLY``), and support comparison and ordering, in the " +"following order:" msgstr "" #: library/inspect.rst:868 @@ -1332,8 +1337,8 @@ msgstr "" #: library/inspect.rst:963 msgid "" "A mutable mapping of parameters' names to arguments' values. Contains only " -"explicitly bound arguments. Changes in :attr:`arguments` will reflect in :" -"attr:`args` and :attr:`kwargs`." +"explicitly bound arguments. Changes in :attr:`arguments` will reflect " +"in :attr:`args` and :attr:`kwargs`." msgstr "" #: library/inspect.rst:967 @@ -1345,27 +1350,27 @@ msgstr "" #: library/inspect.rst:972 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." +"relied on a default value are skipped. However, if needed, " +"use :meth:`BoundArguments.apply_defaults` to add them." msgstr "" #: library/inspect.rst:977 msgid "" -":attr:`arguments` is now of type :class:`dict`. Formerly, it was of type :" -"class:`collections.OrderedDict`." +":attr:`arguments` is now of type :class:`dict`. Formerly, it was of " +"type :class:`collections.OrderedDict`." msgstr "" #: library/inspect.rst:983 msgid "" -"A tuple of positional arguments values. Dynamically computed from the :attr:" -"`arguments` attribute." +"A tuple of positional arguments values. Dynamically computed from " +"the :attr:`arguments` attribute." msgstr "" #: library/inspect.rst:988 msgid "" -"A dict of keyword arguments values. Dynamically computed from the :attr:" -"`arguments` attribute. Arguments that can be passed positionally are " -"included in :attr:`args` instead." +"A dict of keyword arguments values. Dynamically computed from " +"the :attr:`arguments` attribute. Arguments that can be passed positionally " +"are included in :attr:`args` instead." msgstr "" #: library/inspect.rst:994 @@ -1436,8 +1441,8 @@ msgstr "" #: library/inspect.rst:1053 msgid "" -"Get the names and default values of a Python function's parameters. A :term:" -"`named tuple` is returned:" +"Get the names and default values of a Python function's parameters. " +"A :term:`named tuple` is returned:" msgstr "" #: library/inspect.rst:1056 @@ -1480,19 +1485,19 @@ msgstr "" #: library/inspect.rst:1086 msgid "" -"This method was previously documented as deprecated in favour of :func:" -"`signature` in Python 3.5, but that decision has been reversed in order to " -"restore a clearly supported standard interface for single-source Python 2/3 " -"code migrating away from the legacy :func:`getargspec` API." +"This method was previously documented as deprecated in favour " +"of :func:`signature` in Python 3.5, but that decision has been reversed in " +"order to restore a clearly supported standard interface for single-source " +"Python 2/3 code migrating away from the legacy :func:`getargspec` API." msgstr "" #: library/inspect.rst:1101 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." +"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 "" #: library/inspect.rst:1118 @@ -1501,9 +1506,10 @@ msgstr "" #: library/inspect.rst:1113 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." +"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 "" #: library/inspect.rst:1123 @@ -1567,8 +1573,8 @@ msgstr "" #: library/inspect.rst:1179 msgid "" -"Get the object wrapped by *func*. It follows the chain of :attr:" -"`__wrapped__` attributes returning the last object in the chain." +"Get the object wrapped by *func*. It follows the chain " +"of :attr:`__wrapped__` attributes returning the last object in the chain." msgstr "" #: library/inspect.rst:1182 @@ -1576,9 +1582,9 @@ 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." +"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 "" #: library/inspect.rst:1189 @@ -1608,9 +1614,9 @@ msgstr "" #: library/inspect.rst:1207 msgid "" -"If ``eval_str`` is true, values of type ``str`` will be un-stringized using :" -"func:`eval`. This is intended for use with stringized annotations (``from " -"__future__ import annotations``)." +"If ``eval_str`` is true, values of type ``str`` will be un-stringized " +"using :func:`eval`. This is intended for use with stringized annotations " +"(``from __future__ import annotations``)." msgstr "" #: library/inspect.rst:1211 @@ -1668,15 +1674,16 @@ msgstr "" #: library/inspect.rst:1236 msgid "" -"If ``obj`` is a class, ``globals`` defaults to ``sys.modules[obj.__module__]." -"__dict__`` and ``locals`` defaults to the ``obj`` class namespace." +"If ``obj`` is a class, ``globals`` defaults to " +"``sys.modules[obj.__module__].__dict__`` and ``locals`` defaults to the " +"``obj`` class namespace." msgstr "" #: library/inspect.rst:1239 msgid "" "If ``obj`` is a callable, ``globals`` defaults to :attr:`obj.__globals__ " -"`, although if ``obj`` is a wrapped function (using :" -"func:`functools.update_wrapper`) it is first unwrapped." +"`, although if ``obj`` is a wrapped function " +"(using :func:`functools.update_wrapper`) it is first unwrapped." msgstr "" #: library/inspect.rst:1244 @@ -1801,9 +1808,10 @@ msgstr "" #: library/inspect.rst:1351 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::" +"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 "" #: library/inspect.rst:1356 @@ -1901,15 +1909,15 @@ msgstr "" 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:`~object.__getattr__` and :meth:" -"`~object.__getattribute__` may be called." +"properties, will be invoked and :meth:`~object.__getattr__` " +"and :meth:`~object.__getattribute__` may be called." msgstr "" #: library/inspect.rst:1460 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." +"this can be inconvenient. :func:`getattr_static` has the same signature " +"as :func:`getattr` but avoids executing code when it fetches attributes." msgstr "" #: library/inspect.rst:1466 @@ -2033,10 +2041,10 @@ msgstr "" #: library/inspect.rst:1551 msgid "" "Get current state of an asynchronous generator object. The function is " -"intended to be used with asynchronous iterator objects created by :keyword:" -"`async def` functions which use the :keyword:`yield` statement, but will " -"accept any asynchronous generator-like object that has ``ag_running`` and " -"``ag_frame`` attributes." +"intended to be used with asynchronous iterator objects created " +"by :keyword:`async def` functions which use the :keyword:`yield` statement, " +"but will accept any asynchronous generator-like object that has " +"``ag_running`` and ``ag_frame`` attributes." msgstr "" #: library/inspect.rst:1559 @@ -2172,8 +2180,8 @@ msgstr "" #: library/inspect.rst:1678 msgid "" "This is an :class:`enum.IntFlag` that represents the flags that can be " -"passed to the :meth:`~object.__buffer__` method of objects implementing the :" -"ref:`buffer protocol `." +"passed to the :meth:`~object.__buffer__` method of objects implementing " +"the :ref:`buffer protocol `." msgstr "" #: library/inspect.rst:1682 diff --git a/library/internet.po b/library/internet.po index 8f5cb088f..351d6784f 100644 --- a/library/internet.po +++ b/library/internet.po @@ -24,9 +24,9 @@ msgstr "" 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:" +"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 "" #: library/internet.rst:7 diff --git a/library/intro.po b/library/intro.po index d83715e8f..8a9a363a0 100644 --- a/library/intro.po +++ b/library/intro.po @@ -47,11 +47,11 @@ msgid "" "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 "" -"Kütüphane ayrıca yerleşik fonksiyonlar ve istisnalar da içerir --- bir :" -"keyword:`import` deyimine ihtiyaç duymadan tüm Python kodları tarafından " -"kullanılabilen nesneler. Bunlardan bazıları çekirdek dil tarafından " -"tanımlanmıştır, ancak çoğu çekirdek semantiği için gerekli değildir ve " -"burada sadece açıklanmıştır." +"Kütüphane ayrıca yerleşik fonksiyonlar ve istisnalar da içerir --- " +"bir :keyword:`import` deyimine ihtiyaç duymadan tüm Python kodları " +"tarafından kullanılabilen nesneler. Bunlardan bazıları çekirdek dil " +"tarafından tanımlanmıştır, ancak çoğu çekirdek semantiği için gerekli " +"değildir ve burada sadece açıklanmıştır." #: library/intro.rst:20 msgid "" @@ -114,8 +114,8 @@ msgstr "" "olarak, rastgele konular hakkında bilgi edinmekten hoşlanıyorsanız, rastgele " "bir sayfa numarası seçip (bkz. modül :mod:`random`) bir ya da iki bölüm " "okuyabilirsiniz. Bu kılavuzun bölümlerini okuma sıranız ne olursa olsun, " -"kılavuzun geri kalanı bu materyale aşina olduğunuzu varsaydığından, bölüm :" -"ref:`built-in-funcs` ile başlamanıza yardımcı olur." +"kılavuzun geri kalanı bu materyale aşina olduğunuzu varsaydığından, " +"bölüm :ref:`built-in-funcs` ile başlamanıza yardımcı olur." #: library/intro.rst:48 msgid "Let the show begin!" @@ -216,16 +216,17 @@ msgstr "" #: library/intro.rst:95 msgid "" "Process-related APIs are not available or always fail with an error. That " -"includes APIs that spawn new processes (:func:`~os.fork`, :func:`~os." -"execve`), wait for processes (:func:`~os.waitpid`), send signals (:func:`~os." -"kill`), or otherwise interact with processes. The :mod:`subprocess` is " -"importable but does not work." +"includes APIs that spawn new processes " +"(:func:`~os.fork`, :func:`~os.execve`), wait for processes " +"(:func:`~os.waitpid`), send signals (:func:`~os.kill`), or otherwise " +"interact with processes. The :mod:`subprocess` is importable but does not " +"work." msgstr "" "Süreçle ilgili API'ler kullanılamaz veya her zaman bir hata ile başarısız " "olur. Bu, yeni süreçler oluşturan (:func:`~os.fork`, :func:`~os.execve`), " "süreçleri bekleyen (:func:`~os.waitpid`), sinyal gönderen (:func:`~os.kill`) " -"veya süreçlerle başka şekilde etkileşime giren API'leri içerir. :mod:" -"`subprocess` içe aktarılabilir ancak çalışmaz." +"veya süreçlerle başka şekilde etkileşime giren API'leri " +"içerir. :mod:`subprocess` içe aktarılabilir ancak çalışmaz." #: library/intro.rst:101 msgid "" diff --git a/library/io.po b/library/io.po index 982cf63bc..77c50e014 100644 --- a/library/io.po +++ b/library/io.po @@ -51,8 +51,8 @@ msgstr "" msgid "" "All streams are careful about the type of data you give to them. For " "example giving a :class:`str` object to the :meth:`!write` method of a " -"binary stream will raise a :exc:`TypeError`. So will giving a :class:" -"`bytes` object to the :meth:`!write` method of a text stream." +"binary stream will raise a :exc:`TypeError`. So will giving " +"a :class:`bytes` object to the :meth:`!write` method of a text stream." msgstr "" #: library/io.rst:45 @@ -94,8 +94,8 @@ msgstr "" #: library/io.rst:67 msgid "" -"The text stream API is described in detail in the documentation of :class:" -"`TextIOBase`." +"The text stream API is described in detail in the documentation " +"of :class:`TextIOBase`." msgstr "" #: library/io.rst:1137 @@ -132,8 +132,8 @@ msgstr "" #: library/io.rst:89 msgid "" -"The binary stream API is described in detail in the docs of :class:" -"`BufferedIOBase`." +"The binary stream API is described in detail in the docs " +"of :class:`BufferedIOBase`." msgstr "" #: library/io.rst:92 @@ -224,19 +224,20 @@ msgstr "" #: library/io.rst:148 msgid "" -"To find where the default locale encoding is used, you can enable the :" -"option:`-X warn_default_encoding <-X>` command line option or set the :" -"envvar:`PYTHONWARNDEFAULTENCODING` environment variable, which will emit an :" -"exc:`EncodingWarning` when the default encoding is used." +"To find where the default locale encoding is used, you can enable " +"the :option:`-X warn_default_encoding <-X>` command line option or set " +"the :envvar:`PYTHONWARNDEFAULTENCODING` environment variable, which will " +"emit an :exc:`EncodingWarning` when the default encoding is used." msgstr "" #: library/io.rst:153 msgid "" "If you are providing an API that uses :func:`open` or :class:`TextIOWrapper` " -"and passes ``encoding=None`` as a parameter, you can use :func:" -"`text_encoding` so that callers of the API will emit an :exc:" -"`EncodingWarning` if they don't pass an ``encoding``. However, please " -"consider using UTF-8 by default (i.e. ``encoding=\"utf-8\"``) for new APIs." +"and passes ``encoding=None`` as a parameter, you can " +"use :func:`text_encoding` so that callers of the API will emit " +"an :exc:`EncodingWarning` if they don't pass an ``encoding``. However, " +"please consider using UTF-8 by default (i.e. ``encoding=\"utf-8\"``) for new " +"APIs." msgstr "" #: library/io.rst:162 @@ -246,8 +247,8 @@ msgstr "" #: library/io.rst:166 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." +"classes. :func:`open` uses the file's blksize (as obtained " +"by :func:`os.stat`) if possible." msgstr "" #: library/io.rst:173 @@ -273,17 +274,17 @@ msgstr "" #: library/io.rst:189 msgid "" -"The behavior of this function may be overridden by an earlier call to the :c:" -"func:`PyFile_SetOpenCodeHook`. However, assuming that *path* is a :class:" -"`str` and an absolute path, ``open_code(path)`` should always behave the " -"same as ``open(path, 'rb')``. Overriding the behavior is intended for " -"additional validation or preprocessing of the file." +"The behavior of this function may be overridden by an earlier call to " +"the :c:func:`PyFile_SetOpenCodeHook`. However, assuming that *path* is " +"a :class:`str` and an absolute path, ``open_code(path)`` should always " +"behave the same as ``open(path, 'rb')``. Overriding the behavior is intended " +"for additional validation or preprocessing of the file." msgstr "" #: library/io.rst:200 msgid "" -"This is a helper function for callables that use :func:`open` or :class:" -"`TextIOWrapper` and have an ``encoding=None`` parameter." +"This is a helper function for callables that use :func:`open` " +"or :class:`TextIOWrapper` and have an ``encoding=None`` parameter." msgstr "" #: library/io.rst:203 @@ -295,9 +296,10 @@ msgstr "" #: library/io.rst:207 msgid "" -"This function emits an :class:`EncodingWarning` if :data:`sys.flags." -"warn_default_encoding ` is true and *encoding* is ``None``. " -"*stacklevel* specifies where the warning is emitted. For example::" +"This function emits an :class:`EncodingWarning` " +"if :data:`sys.flags.warn_default_encoding ` is true and " +"*encoding* is ``None``. *stacklevel* specifies where the warning is emitted. " +"For example::" msgstr "" #: library/io.rst:212 @@ -362,8 +364,8 @@ msgstr "" 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:`!readinto` and :meth:`!readline`." +"example, :class:`BufferedIOBase` provides unoptimized implementations " +"of :meth:`!readinto` and :meth:`!readline`." msgstr "" #: library/io.rst:263 @@ -378,19 +380,21 @@ msgstr "" #: library/io.rst:268 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." +"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 "" #: library/io.rst:272 msgid "" "The :class:`BufferedIOBase` ABC extends :class:`IOBase`. It deals with " -"buffering on a raw binary stream (:class:`RawIOBase`). Its subclasses, :" -"class:`BufferedWriter`, :class:`BufferedReader`, and :class:`BufferedRWPair` " -"buffer raw binary streams that are writable, readable, and both readable and " -"writable, respectively. :class:`BufferedRandom` provides a buffered " -"interface to seekable streams. Another :class:`BufferedIOBase` subclass, :" -"class:`BytesIO`, is a stream of in-memory bytes." +"buffering on a raw binary stream (:class:`RawIOBase`). Its " +"subclasses, :class:`BufferedWriter`, :class:`BufferedReader`, " +"and :class:`BufferedRWPair` buffer raw binary streams that are writable, " +"readable, and both readable and writable, " +"respectively. :class:`BufferedRandom` provides a buffered interface to " +"seekable streams. Another :class:`BufferedIOBase` " +"subclass, :class:`BytesIO`, is a stream of in-memory bytes." msgstr "" #: library/io.rst:280 @@ -404,8 +408,8 @@ msgstr "" #: library/io.rst:286 msgid "" -"Argument names are not part of the specification, and only the arguments of :" -"func:`open` are intended to be used as keyword arguments." +"Argument names are not part of the specification, and only the arguments " +"of :func:`open` are intended to be used as keyword arguments." msgstr "" #: library/io.rst:289 @@ -507,9 +511,10 @@ msgstr "" #: library/io.rst:329 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. Text I/O classes work with :class:`str` data." +"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. Text I/O classes work with :class:`str` " +"data." msgstr "" #: library/io.rst:333 @@ -529,9 +534,10 @@ msgstr "" #: library/io.rst:342 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::" +":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 "" #: library/io.rst:346 @@ -648,15 +654,16 @@ msgstr "" #: library/io.rst:423 msgid "" -"Some operating systems could support additional values, like :const:`os." -"SEEK_HOLE` or :const:`os.SEEK_DATA`. The valid values for a file could " -"depend on it being open in text or binary mode." +"Some operating systems could support additional values, " +"like :const:`os.SEEK_HOLE` or :const:`os.SEEK_DATA`. The valid values for a " +"file could depend on it being open in text or binary mode." msgstr "" #: library/io.rst:430 msgid "" -"Return ``True`` if the stream supports random access. If ``False``, :meth:" -"`seek`, :meth:`tell` and :meth:`truncate` will raise :exc:`OSError`." +"Return ``True`` if the stream supports random access. If " +"``False``, :meth:`seek`, :meth:`tell` and :meth:`truncate` will " +"raise :exc:`OSError`." msgstr "" #: library/io.rst:435 @@ -691,8 +698,8 @@ msgstr "" #: library/io.rst:462 msgid "" "Prepare for object destruction. :class:`IOBase` provides a default " -"implementation of this method that calls the instance's :meth:`~IOBase." -"close` method." +"implementation of this method that calls the " +"instance's :meth:`~IOBase.close` method." msgstr "" #: library/io.rst:469 @@ -709,8 +716,8 @@ msgstr "" #: library/io.rst:476 msgid "" -":class:`RawIOBase` provides these methods in addition to those from :class:" -"`IOBase`:" +":class:`RawIOBase` provides these methods in addition to those " +"from :class:`IOBase`:" msgstr "" #: library/io.rst:481 @@ -742,8 +749,8 @@ msgstr "" #: library/io.rst:500 msgid "" "Read bytes into a pre-allocated, writable :term:`bytes-like object` *b*, and " -"return the number of bytes read. For example, *b* might be a :class:" -"`bytearray`. If the object is in non-blocking mode and no bytes are " +"return the number of bytes read. For example, *b* might be " +"a :class:`bytearray`. If the object is in non-blocking mode and no bytes are " "available, ``None`` is returned." msgstr "" @@ -766,10 +773,10 @@ msgstr "" #: library/io.rst:524 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." +"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 "" #: library/io.rst:529 @@ -788,9 +795,9 @@ msgstr "" #: library/io.rst:537 msgid "" -"A typical :class:`BufferedIOBase` implementation should not inherit from a :" -"class:`RawIOBase` implementation, but wrap one, like :class:`BufferedWriter` " -"and :class:`BufferedReader` do." +"A typical :class:`BufferedIOBase` implementation should not inherit from " +"a :class:`RawIOBase` implementation, but wrap one, " +"like :class:`BufferedWriter` and :class:`BufferedReader` do." msgstr "" #: library/io.rst:541 @@ -801,9 +808,9 @@ msgstr "" #: library/io.rst:546 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." +"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 "" #: library/io.rst:552 @@ -824,8 +831,8 @@ msgstr "" #: library/io.rst:565 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." +"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 "" #: library/io.rst:569 @@ -860,8 +867,8 @@ msgstr "" #: library/io.rst:591 msgid "" "Read bytes into a pre-allocated, writable :term:`bytes-like object` *b* and " -"return the number of bytes read. For example, *b* might be a :class:" -"`bytearray`." +"return the number of bytes read. For example, *b* might be " +"a :class:`bytearray`." msgstr "" #: library/io.rst:595 @@ -873,9 +880,9 @@ msgstr "" #: library/io.rst:603 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." +"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 "" #: library/io.rst:615 @@ -942,9 +949,9 @@ msgstr "" #: library/io.rst:656 msgid "" -"The :meth:`~RawIOBase.read` (when called with a positive argument), :meth:" -"`~RawIOBase.readinto` and :meth:`~RawIOBase.write` methods on this class " -"will only make one system call." +"The :meth:`~RawIOBase.read` (when called with a positive " +"argument), :meth:`~RawIOBase.readinto` and :meth:`~RawIOBase.write` methods " +"on this class will only make one system call." msgstr "" #: library/io.rst:660 @@ -976,8 +983,8 @@ msgstr "" #: library/io.rst:678 msgid "" -":class:`FileIO` provides these data attributes in addition to those from :" -"class:`RawIOBase` and :class:`IOBase`:" +":class:`FileIO` provides these data attributes in addition to those " +"from :class:`RawIOBase` and :class:`IOBase`:" msgstr "" #: library/io.rst:683 @@ -1002,9 +1009,9 @@ msgstr "" #: library/io.rst:699 msgid "" -"A binary stream using an in-memory bytes buffer. It inherits from :class:" -"`BufferedIOBase`. The buffer is discarded when the :meth:`~IOBase.close` " -"method is called." +"A binary stream using an in-memory bytes buffer. It inherits " +"from :class:`BufferedIOBase`. The buffer is discarded when " +"the :meth:`~IOBase.close` method is called." msgstr "" #: library/io.rst:703 @@ -1061,8 +1068,8 @@ msgstr "" #: library/io.rst:747 msgid "" "A buffered binary stream providing higher-level access to a readable, non " -"seekable :class:`RawIOBase` raw binary stream. It inherits from :class:" -"`BufferedIOBase`." +"seekable :class:`RawIOBase` raw binary stream. It inherits " +"from :class:`BufferedIOBase`." msgstr "" #: library/io.rst:751 @@ -1075,8 +1082,8 @@ msgstr "" #: library/io.rst:755 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." +"*raw* stream and *buffer_size*. If *buffer_size* is " +"omitted, :data:`DEFAULT_BUFFER_SIZE` is used." msgstr "" #: library/io.rst:759 @@ -1108,8 +1115,8 @@ msgstr "" #: library/io.rst:785 msgid "" "A buffered binary stream providing higher-level access to a writeable, non " -"seekable :class:`RawIOBase` raw binary stream. It inherits from :class:" -"`BufferedIOBase`." +"seekable :class:`RawIOBase` raw binary stream. It inherits " +"from :class:`BufferedIOBase`." msgstr "" #: library/io.rst:789 @@ -1140,8 +1147,8 @@ msgstr "" #: library/io.rst:798 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`." +"*raw* stream. If the *buffer_size* is not given, it defaults " +"to :data:`DEFAULT_BUFFER_SIZE`." msgstr "" #: library/io.rst:802 @@ -1152,8 +1159,8 @@ msgstr "" #: library/io.rst:807 msgid "" -"Force bytes held in the buffer into the raw stream. A :exc:" -"`BlockingIOError` should be raised if the raw stream blocks." +"Force bytes held in the buffer into the raw stream. " +"A :exc:`BlockingIOError` should be raised if the raw stream blocks." msgstr "" #: library/io.rst:812 @@ -1165,44 +1172,44 @@ msgstr "" #: library/io.rst:820 msgid "" -"A buffered binary stream providing higher-level access to a seekable :class:" -"`RawIOBase` raw binary stream. It inherits from :class:`BufferedReader` " -"and :class:`BufferedWriter`." +"A buffered binary stream providing higher-level access to a " +"seekable :class:`RawIOBase` raw binary stream. It inherits " +"from :class:`BufferedReader` and :class:`BufferedWriter`." msgstr "" #: library/io.rst:824 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`." +"in the first argument. If the *buffer_size* is omitted it defaults " +"to :data:`DEFAULT_BUFFER_SIZE`." msgstr "" #: library/io.rst:828 msgid "" -":class:`BufferedRandom` is capable of anything :class:`BufferedReader` or :" -"class:`BufferedWriter` can do. In addition, :meth:`~IOBase.seek` and :meth:" -"`~IOBase.tell` are guaranteed to be implemented." +":class:`BufferedRandom` is capable of anything :class:`BufferedReader` " +"or :class:`BufferedWriter` can do. In addition, :meth:`~IOBase.seek` " +"and :meth:`~IOBase.tell` are guaranteed to be implemented." msgstr "" #: library/io.rst:835 msgid "" -"A buffered binary stream providing higher-level access to two non seekable :" -"class:`RawIOBase` raw binary streams---one readable, the other writeable. It " -"inherits from :class:`BufferedIOBase`." +"A buffered binary stream providing higher-level access to two non " +"seekable :class:`RawIOBase` raw binary streams---one readable, the other " +"writeable. It inherits from :class:`BufferedIOBase`." msgstr "" #: library/io.rst:839 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`." +"writeable respectively. If the *buffer_size* is omitted it defaults " +"to :data:`DEFAULT_BUFFER_SIZE`." msgstr "" #: library/io.rst:843 msgid "" ":class:`BufferedRWPair` implements all of :class:`BufferedIOBase`\\'s " -"methods except for :meth:`~BufferedIOBase.detach`, which raises :exc:" -"`UnsupportedOperation`." +"methods except for :meth:`~BufferedIOBase.detach`, which " +"raises :exc:`UnsupportedOperation`." msgstr "" #: library/io.rst:849 @@ -1243,9 +1250,9 @@ msgstr "" #: library/io.rst:882 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." +"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 "" #: library/io.rst:888 @@ -1263,14 +1270,14 @@ msgstr "" #: library/io.rst:894 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`." +"have the concept of an underlying buffer and calling this method will " +"raise :exc:`UnsupportedOperation`." msgstr "" #: library/io.rst:902 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." +"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 "" #: library/io.rst:907 @@ -1326,9 +1333,9 @@ msgstr "" #: library/io.rst:948 msgid "" -"A buffered text stream providing higher-level access to a :class:" -"`BufferedIOBase` buffered binary stream. It inherits from :class:" -"`TextIOBase`." +"A buffered text stream providing higher-level access to " +"a :class:`BufferedIOBase` buffered binary stream. It inherits " +"from :class:`TextIOBase`." msgstr "" #: library/io.rst:952 @@ -1362,10 +1369,10 @@ msgstr "" #: library/io.rst:976 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 *newline* is ``''``, " +"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 *newline* is ``''``, " "universal newlines mode is enabled, but line endings are returned to the " "caller untranslated. If *newline* has any of the other legal values, input " "lines are only terminated by the given string, and the line ending is " @@ -1375,10 +1382,10 @@ msgstr "" #: library/io.rst:985 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." +"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 "" #: library/io.rst:991 @@ -1390,9 +1397,9 @@ msgstr "" #: library/io.rst:994 msgid "" "If *write_through* is ``True``, calls to :meth:`~BufferedIOBase.write` are " -"guaranteed not to be buffered: any data written on the :class:" -"`TextIOWrapper` object is immediately handled to its underlying binary " -"*buffer*." +"guaranteed not to be buffered: any data written on " +"the :class:`TextIOWrapper` object is immediately handled to its underlying " +"binary *buffer*." msgstr "" #: library/io.rst:998 @@ -1499,8 +1506,8 @@ msgstr "" #: library/io.rst:1076 msgid "" -"A text stream using an in-memory text buffer. It inherits from :class:" -"`TextIOBase`." +"A text stream using an in-memory text buffer. It inherits " +"from :class:`TextIOBase`." msgstr "" #: library/io.rst:1079 @@ -1511,10 +1518,10 @@ msgstr "" #: library/io.rst:1082 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 " -"which emulates opening an existing file in a ``w+`` mode, making it ready " -"for an immediate write from the beginning or for a write that would " +"newline translation is enabled, newlines will be encoded as if " +"by :meth:`~TextIOBase.write`. The stream is positioned at the start of the " +"buffer which emulates opening an existing file in a ``w+`` mode, making it " +"ready for an immediate write from the beginning or for a write that would " "overwrite the initial value. To emulate opening a file in an ``a+`` mode " "ready for appending, use ``f.seek(0, io.SEEK_END)`` to reposition the stream " "at the end of the buffer." @@ -1529,8 +1536,8 @@ msgstr "" #: library/io.rst:1095 msgid "" -":class:`StringIO` provides this method in addition to those from :class:" -"`TextIOBase` and :class:`IOBase`:" +":class:`StringIO` provides this method in addition to those " +"from :class:`TextIOBase` and :class:`IOBase`:" msgstr "" #: library/io.rst:1100 @@ -1595,9 +1602,9 @@ 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:" -"`~TextIOBase.tell` and :meth:`~TextIOBase.seek` are both quite slow due to " -"the reconstruction algorithm used." +"handling huge amounts of text data like large log files. " +"Also, :meth:`~TextIOBase.tell` and :meth:`~TextIOBase.seek` are both quite " +"slow due to the reconstruction algorithm used." msgstr "" #: library/io.rst:1158 @@ -1619,10 +1626,10 @@ msgstr "" #: library/io.rst:1167 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." +"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 "" #: library/io.rst:1172 @@ -1635,13 +1642,13 @@ msgstr "" #: library/io.rst:1177 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." +"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 "" #: library/io.rst:1185 diff --git a/library/ipaddress.po b/library/ipaddress.po index 59ef0a99f..6ab67f836 100644 --- a/library/ipaddress.po +++ b/library/ipaddress.po @@ -41,8 +41,8 @@ msgstr "" #: library/ipaddress.rst:22 msgid "" -"This is the full module API reference—for an overview and introduction, see :" -"ref:`ipaddress-howto`." +"This is the full module API reference—for an overview and introduction, " +"see :ref:`ipaddress-howto`." msgstr "" #: library/ipaddress.rst:35 @@ -80,9 +80,9 @@ 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." +"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 "" #: library/ipaddress.rst:77 @@ -294,8 +294,8 @@ msgstr "" #: library/ipaddress.rst:230 msgid "" -"``True`` if the address is unspecified. See :RFC:`5735` (for IPv4) or :RFC:" -"`2373` (for IPv6)." +"``True`` if the address is unspecified. See :RFC:`5735` (for IPv4) " +"or :RFC:`2373` (for IPv6)." msgstr "" #: library/ipaddress.rst:235 @@ -304,8 +304,8 @@ msgstr "" #: library/ipaddress.rst:239 msgid "" -"``True`` if this is a loopback address. See :RFC:`3330` (for IPv4) or :RFC:" -"`2373` (for IPv6)." +"``True`` if this is a loopback address. See :RFC:`3330` (for IPv4) " +"or :RFC:`2373` (for IPv6)." msgstr "" #: library/ipaddress.rst:244 @@ -389,15 +389,15 @@ msgstr "" #: library/ipaddress.rst:340 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`." +"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 "" #: library/ipaddress.rst:347 msgid "" -"For addresses that appear to be IPv4 mapped addresses (starting with ``::" -"FFFF/96``), this property will report the embedded IPv4 address. For any " +"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 "" @@ -555,10 +555,10 @@ msgstr "" 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`. Network objects are :term:`hashable`, so they can be used as " -"keys in dictionaries." +"attributes. All of these are common between :class:`IPv4Network` " +"and :class:`IPv6Network`, so to avoid duplication they are only documented " +"for :class:`IPv4Network`. Network objects are :term:`hashable`, so they can " +"be used as keys in dictionaries." msgstr "" #: library/ipaddress.rst:476 @@ -615,9 +615,9 @@ msgstr "" #: library/ipaddress.rst:728 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." +"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 "" #: library/ipaddress.rst:512 @@ -710,8 +710,9 @@ msgstr "" #: library/ipaddress.rst:608 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." +"from this one. Returns an iterator of network objects. " +"Raises :exc:`ValueError` if *network* is not completely contained in this " +"network." msgstr "" #: library/ipaddress.rst:621 @@ -769,15 +770,16 @@ msgstr "" #: library/ipaddress.rst:708 msgid "" -"Note that currently expanded netmasks are not supported. That means ``2001:" -"db00::0/24`` is a valid argument while ``2001:db00::0/ffff:ff00::`` is not." +"Note that currently expanded netmasks are not supported. That means " +"``2001:db00::0/24`` is a valid argument while ``2001:db00::0/ffff:ff00::`` " +"is not." msgstr "" #: library/ipaddress.rst:712 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``." +"network, with the network address being *address* and the mask being ``/" +"128``." msgstr "" #: library/ipaddress.rst:716 @@ -997,36 +999,36 @@ msgstr "" #: library/ipaddress.rst:948 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." +"*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 "" #: library/ipaddress.rst:961 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." +"*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 "" #: library/ipaddress.rst:969 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." +"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 "" #: library/ipaddress.rst:985 msgid "" -"Return an iterator of the collapsed :class:`IPv4Network` or :class:" -"`IPv6Network` objects. *addresses* is an :term:`iterable` of :class:" -"`IPv4Network` or :class:`IPv6Network` objects. A :exc:`TypeError` is raised " -"if *addresses* contains mixed version objects." +"Return an iterator of the collapsed :class:`IPv4Network` " +"or :class:`IPv6Network` objects. *addresses* is an :term:`iterable` " +"of :class:`IPv4Network` or :class:`IPv6Network` objects. A :exc:`TypeError` " +"is raised if *addresses* contains mixed version objects." msgstr "" #: library/ipaddress.rst:998 diff --git a/library/ipc.po b/library/ipc.po index 999f07604..a0bf8f6c7 100644 --- a/library/ipc.po +++ b/library/ipc.po @@ -28,9 +28,9 @@ msgstr "" #: 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." +"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 "" #: library/ipc.rst:14 diff --git a/library/itertools.po b/library/itertools.po index 1c924bd56..47d810ea3 100644 --- a/library/itertools.po +++ b/library/itertools.po @@ -463,11 +463,11 @@ msgstr "" #: library/itertools.rst:134 msgid "" -"The *function* argument 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:" +"The *function* argument 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:" msgstr "" #: library/itertools.rst:140 @@ -568,9 +568,9 @@ msgstr "" #: library/itertools.rst:223 msgid "" "The output is a subsequence of :func:`product` keeping only entries that are " -"subsequences of the *iterable*. The length of the output is given by :func:" -"`math.comb` which computes ``n! / r! / (n - r)!`` when ``0 ≤ r ≤ n`` or zero " -"when ``r > n``." +"subsequences of the *iterable*. The length of the output is given " +"by :func:`math.comb` which computes ``n! / r! / (n - r)!`` when ``0 ≤ r ≤ " +"n`` or zero when ``r > n``." msgstr "" #: library/itertools.rst:228 @@ -679,8 +679,8 @@ msgstr "" #: library/itertools.rst:319 msgid "" "Make an iterator that returns evenly spaced values beginning with *start*. " -"Can be used with :func:`map` to generate consecutive data points or with :" -"func:`zip` to add sequence numbers. Roughly equivalent to::" +"Can be used with :func:`map` to generate consecutive data points or " +"with :func:`zip` to add sequence numbers. Roughly equivalent to::" msgstr "" #: library/itertools.rst:324 @@ -798,9 +798,9 @@ msgstr "" #: library/itertools.rst:412 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::" +"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 "" #: library/itertools.rst:417 @@ -925,8 +925,8 @@ msgstr "" #: library/itertools.rst:522 msgid "" -"Return successive *r* length `permutations of elements `_ from the *iterable*." +"Return successive *r* length `permutations of elements `_ from the *iterable*." msgstr "" #: library/itertools.rst:525 @@ -938,9 +938,9 @@ msgstr "" #: library/itertools.rst:529 msgid "" "The output is a subsequence of :func:`product` where entries with repeated " -"elements have been filtered out. The length of the output is given by :func:" -"`math.perm` which computes ``n! / (n - r)!`` when ``0 ≤ r ≤ n`` or zero when " -"``r > n``." +"elements have been filtered out. The length of the output is given " +"by :func:`math.perm` which computes ``n! / (n - r)!`` when ``0 ≤ r ≤ n`` or " +"zero when ``r > n``." msgstr "" #: library/itertools.rst:534 @@ -1117,8 +1117,9 @@ msgid "" "the input iterator and there is no way to access it. This could be an issue " "if an application wants to further consume the input iterator after " "*takewhile* has been run to exhaustion. To work around this problem, " -"consider using `more-iterools before_and_after() `_ instead." +"consider using `more-iterools before_and_after() `_ instead." msgstr "" #: library/itertools.rst:674 @@ -1172,8 +1173,8 @@ msgstr "" 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`." +"most or all of the data before another iterator starts, it is faster to " +"use :func:`list` instead of :func:`tee`." msgstr "" #: library/itertools.rst:723 @@ -1217,9 +1218,9 @@ msgstr "" #: library/itertools.rst:755 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 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`)." msgstr "" #: library/itertools.rst:763 @@ -1239,9 +1240,9 @@ msgid "" "``chain.from_iterable`` is related to the concept of flattening. The " "recipes also give ideas about ways that the tools can be combined — for " "example, how ``starmap()`` and ``repeat()`` can work together. The recipes " -"also show patterns for using itertools with the :mod:`operator` and :mod:" -"`collections` modules as well as with the built-in itertools such as " -"``map()``, ``filter()``, ``reversed()``, and ``enumerate()``." +"also show patterns for using itertools with the :mod:`operator` " +"and :mod:`collections` modules as well as with the built-in itertools such " +"as ``map()``, ``filter()``, ``reversed()``, and ``enumerate()``." msgstr "" #: library/itertools.rst:777 @@ -1413,8 +1414,8 @@ msgid "" "def partition(predicate, iterable):\n" " \"\"\"Partition entries into false entries and true entries.\n" "\n" -" If *predicate* is slow, consider wrapping it with functools." -"lru_cache().\n" +" If *predicate* is slow, consider wrapping it with " +"functools.lru_cache().\n" " \"\"\"\n" " # partition(is_odd, range(10)) → 0 2 4 6 8 and 1 3 5 7 9\n" " t1, t2 = tee(iterable)\n" diff --git a/library/json.po b/library/json.po index d1ff5cc72..4ae49de5d 100644 --- a/library/json.po +++ b/library/json.po @@ -26,12 +26,12 @@ msgstr "" #: library/json.rst:14 msgid "" -"`JSON (JavaScript Object Notation) `_, specified by :rfc:" -"`7159` (which obsoletes :rfc:`4627`) and by `ECMA-404 `_, 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]_ )." +"lightweight data interchange format inspired by `JavaScript `_ object literal syntax (although it is " +"not a strict subset of JavaScript [#rfc-errata]_ )." msgstr "" #: library/json.rst:22 @@ -43,8 +43,8 @@ msgstr "" #: library/json.rst:26 msgid "" -":mod:`json` exposes an API familiar to users of the standard library :mod:" -"`marshal` and :mod:`pickle` modules." +":mod:`json` exposes an API familiar to users of the standard " +"library :mod:`marshal` and :mod:`pickle` modules." msgstr "" #: library/json.rst:29 @@ -207,8 +207,9 @@ msgstr "" #: library/json.rst:150 msgid "" -"The :mod:`json` module always produces :class:`str` objects, not :class:" -"`bytes` objects. Therefore, ``fp.write()`` must support :class:`str` input." +"The :mod:`json` module always produces :class:`str` objects, " +"not :class:`bytes` objects. Therefore, ``fp.write()`` must " +"support :class:`str` input." msgstr "" #: library/json.rst:431 @@ -227,11 +228,11 @@ msgstr "" #: library/json.rst:162 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." +"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 "" #: library/json.rst:450 @@ -264,8 +265,8 @@ msgstr "" 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." +"version of the object or raise a :exc:`TypeError`. If not " +"specified, :exc:`TypeError` is raised." msgstr "" #: library/json.rst:191 @@ -276,9 +277,9 @@ msgstr "" #: library/json.rst:194 msgid "" -"To use a custom :class:`JSONEncoder` subclass (e.g. one that overrides the :" -"meth:`~JSONEncoder.default` method to serialize additional types), specify " -"it with the *cls* kwarg; otherwise :class:`JSONEncoder` is used." +"To use a custom :class:`JSONEncoder` subclass (e.g. one that overrides " +"the :meth:`~JSONEncoder.default` method to serialize additional types), " +"specify it with the *cls* kwarg; otherwise :class:`JSONEncoder` is used." msgstr "" #: library/json.rst:276 @@ -296,8 +297,8 @@ msgstr "" #: library/json.rst:212 msgid "" "Serialize *obj* to a JSON formatted :class:`str` using this :ref:`conversion " -"table `. The arguments have the same meaning as in :func:" -"`dump`." +"table `. The arguments have the same meaning as " +"in :func:`dump`." msgstr "" #: library/json.rst:218 @@ -311,9 +312,9 @@ msgstr "" #: library/json.rst:227 msgid "" -"Deserialize *fp* (a ``.read()``-supporting :term:`text file` or :term:" -"`binary file` containing a JSON document) to a Python object using this :ref:" -"`conversion table `." +"Deserialize *fp* (a ``.read()``-supporting :term:`text file` " +"or :term:`binary file` containing a JSON document) to a Python object using " +"this :ref:`conversion table `." msgstr "" #: library/json.rst:231 @@ -321,17 +322,17 @@ 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)." +"be used to implement custom decoders (e.g. `JSON-RPC `_ class hinting)." msgstr "" #: library/json.rst:237 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. If " -"*object_hook* is also defined, the *object_pairs_hook* takes priority." +"return value of *object_pairs_hook* will be used instead of " +"the :class:`dict`. This feature can be used to implement custom decoders. " +"If *object_hook* is also defined, the *object_pairs_hook* takes priority." msgstr "" #: library/json.rst:347 @@ -381,8 +382,8 @@ msgstr "" #: library/json.rst:291 library/json.rst:369 msgid "" -"If the data being deserialized is not a valid JSON document, a :exc:" -"`JSONDecodeError` will be raised." +"If the data being deserialized is not a valid JSON document, " +"a :exc:`JSONDecodeError` will be raised." msgstr "" #: library/json.rst:279 @@ -394,8 +395,8 @@ msgstr "" #: library/json.rst:285 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 `." +"instance containing a JSON document) to a Python object using " +"this :ref:`conversion table `." msgstr "" #: library/json.rst:289 @@ -506,17 +507,17 @@ msgstr "" msgid "" "*object_hook* is an optional function that 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)." +"given :class:`dict`. This can be used to provide custom deserializations " +"(e.g. to support `JSON-RPC `_ class hinting)." msgstr "" #: library/json.rst:341 msgid "" "*object_pairs_hook* is an optional function that 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. If " -"*object_hook* is also defined, the *object_pairs_hook* takes priority." +"return value of *object_pairs_hook* will be used instead of " +"the :class:`dict`. This feature can be used to implement custom decoders. " +"If *object_hook* is also defined, the *object_pairs_hook* takes priority." msgstr "" #: library/json.rst:364 @@ -582,8 +583,8 @@ msgstr "" #: library/json.rst:422 msgid "" -"To extend this to recognize other objects, subclass and implement a :meth:" -"`~JSONEncoder.default` method with another method that returns a " +"To extend this to recognize other objects, subclass and implement " +"a :meth:`~JSONEncoder.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 "" @@ -591,8 +592,9 @@ msgstr "" #: library/json.rst:427 msgid "" "If *skipkeys* is false (the default), a :exc:`TypeError` will be raised when " -"trying to encode keys that are not :class:`str`, :class:`int`, :class:" -"`float` or ``None``. If *skipkeys* is true, such items are simply skipped." +"trying to encode keys that are " +"not :class:`str`, :class:`int`, :class:`float` or ``None``. If *skipkeys* " +"is true, such items are simply skipped." msgstr "" #: library/json.rst:435 @@ -621,14 +623,14 @@ msgstr "" #: library/json.rst:479 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`)." +"object for *o*, or calls the base implementation (to raise " +"a :exc:`TypeError`)." msgstr "" #: library/json.rst:483 msgid "" -"For example, to support arbitrary iterators, you could implement :meth:" -"`~JSONEncoder.default` like this::" +"For example, to support arbitrary iterators, you could " +"implement :meth:`~JSONEncoder.default` like this::" msgstr "" #: library/json.rst:486 @@ -772,8 +774,8 @@ 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." +"By default, this module accepts and outputs (when present in the " +"original :class:`str`) code points for such sequences." msgstr "" #: library/json.rst:594 @@ -909,8 +911,9 @@ msgstr "" #: library/json.rst:683 msgid "" -"If the optional ``infile`` and ``outfile`` arguments are not specified, :" -"data:`sys.stdin` and :data:`sys.stdout` will be used respectively:" +"If the optional ``infile`` and ``outfile`` arguments are not " +"specified, :data:`sys.stdin` and :data:`sys.stdout` will be used " +"respectively:" msgstr "" #: library/json.rst:686 diff --git a/library/keyword.po b/library/keyword.po index 7411c744a..d7c50ce05 100644 --- a/library/keyword.po +++ b/library/keyword.po @@ -26,8 +26,8 @@ msgstr "" #: library/keyword.rst:11 msgid "" -"This module allows a Python program to determine if a string is a :ref:" -"`keyword ` or :ref:`soft keyword `." +"This module allows a Python program to determine if a string is " +"a :ref:`keyword ` or :ref:`soft keyword `." msgstr "" #: library/keyword.rst:17 @@ -37,8 +37,9 @@ msgstr "" #: library/keyword.rst:22 msgid "" "Sequence containing all the :ref:`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." +"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 "" #: library/keyword.rst:29 diff --git a/library/linecache.po b/library/linecache.po index 13bf6c0cd..741251e16 100644 --- a/library/linecache.po +++ b/library/linecache.po @@ -28,9 +28,9 @@ msgstr "" 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." +"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 "" #: library/linecache.rst:18 @@ -53,12 +53,12 @@ msgstr "" #: library/linecache.rst:33 msgid "" -"If a file named *filename* is not found, the function first checks for a :" -"pep:`302` ``__loader__`` in *module_globals*. If there is such a loader and " -"it defines a ``get_source`` method, then that determines the source lines " -"(if ``get_source()`` returns ``None``, then ``''`` is returned). Finally, if " -"*filename* is a relative filename, it is looked up relative to the entries " -"in the module search path, ``sys.path``." +"If a file named *filename* is not found, the function first checks for " +"a :pep:`302` ``__loader__`` in *module_globals*. If there is such a loader " +"and it defines a ``get_source`` method, then that determines the source " +"lines (if ``get_source()`` returns ``None``, then ``''`` is returned). " +"Finally, if *filename* is a relative filename, it is looked up relative to " +"the entries in the module search path, ``sys.path``." msgstr "" #: library/linecache.rst:44 diff --git a/library/locale.po b/library/locale.po index f20a9a07b..7aedc267d 100644 --- a/library/locale.po +++ b/library/locale.po @@ -123,9 +123,9 @@ msgstr "" #: 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." +"``'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 "" #: library/locale.rst:80 @@ -507,8 +507,9 @@ msgstr "" #: library/locale.rst:346 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`." +"containing *language code*, *encoding*. *category* may be one of " +"the :const:`!LC_\\*` values except :const:`LC_ALL`. It defaults " +"to :const:`LC_CTYPE`." msgstr "" #: library/locale.rst:357 @@ -541,8 +542,8 @@ msgstr "" #: library/locale.rst:373 msgid "" -"The function now always returns ``\"utf-8\"`` on Android or if the :ref:" -"`Python UTF-8 Mode ` is enabled." +"The function now always returns ``\"utf-8\"`` on Android or if " +"the :ref:`Python UTF-8 Mode ` is enabled." msgstr "" #: library/locale.rst:380 @@ -662,14 +663,14 @@ msgstr "" #: library/locale.rst:475 msgid "" -"Converts a string into a normalized number string, following the :const:" -"`LC_NUMERIC` settings." +"Converts a string into a normalized number string, following " +"the :const:`LC_NUMERIC` settings." msgstr "" #: library/locale.rst:483 msgid "" -"Converts a normalized number string into a formatted string following the :" -"const:`LC_NUMERIC` settings." +"Converts a normalized number string into a formatted string following " +"the :const:`LC_NUMERIC` settings." msgstr "" #: library/locale.rst:491 @@ -703,14 +704,14 @@ msgstr "" #: library/locale.rst:516 msgid "" -"Locale category for sorting strings. The functions :func:`strcoll` and :" -"func:`strxfrm` of the :mod:`locale` module are affected." +"Locale category for sorting strings. The functions :func:`strcoll` " +"and :func:`strxfrm` of the :mod:`locale` module are affected." msgstr "" #: library/locale.rst:522 msgid "" -"Locale category for the formatting of time. The function :func:`time." -"strftime` follows these conventions." +"Locale category for the formatting of time. The " +"function :func:`time.strftime` follows these conventions." msgstr "" #: library/locale.rst:528 @@ -735,10 +736,10 @@ msgstr "" #: library/locale.rst:545 msgid "" -"Locale category for formatting numbers. The functions :func:" -"`format_string`, :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." +"Locale category for formatting numbers. The " +"functions :func:`format_string`, :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 "" #: library/locale.rst:553 @@ -753,8 +754,8 @@ msgstr "" #: library/locale.rst:562 msgid "" -"This is a symbolic constant used for different values returned by :func:" -"`localeconv`." +"This is a symbolic constant used for different values returned " +"by :func:`localeconv`." msgstr "" #: library/locale.rst:566 @@ -789,9 +790,9 @@ msgstr "" #: library/locale.rst:586 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 " +"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 "" @@ -818,8 +819,8 @@ msgstr "" #: library/locale.rst:605 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_string`, :func:`.str`." +"the special functions defined by this " +"module: :func:`atof`, :func:`atoi`, :func:`format_string`, :func:`.str`." msgstr "" #: library/locale.rst:609 @@ -850,9 +851,9 @@ 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." +"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 "" #: library/locale.rst:638 @@ -862,8 +863,8 @@ msgstr "" #: library/locale.rst:647 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`, " +"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 " diff --git a/library/logging.config.po b/library/logging.config.po index 055ebce44..30e620b33 100644 --- a/library/logging.config.po +++ b/library/logging.config.po @@ -66,10 +66,10 @@ msgstr "" #: 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:" +"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 "" #: library/logging.config.rst:48 @@ -101,11 +101,11 @@ msgstr "" #: 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." +"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 "" #: library/logging.config.rst:64 @@ -126,9 +126,9 @@ 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." +"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 "" #: library/logging.config.rst:82 @@ -143,8 +143,8 @@ msgstr "" #: library/logging.config.rst:90 msgid "" -"It will raise :exc:`FileNotFoundError` if the file doesn't exist and :exc:" -"`RuntimeError` if the file is invalid or empty." +"It will raise :exc:`FileNotFoundError` if the file doesn't exist " +"and :exc:`RuntimeError` if the file is invalid or empty." msgstr "" #: library/logging.config.rst:0 @@ -153,14 +153,14 @@ msgstr "" #: library/logging.config.rst:94 msgid "" -"A filename, or a file-like object, or an instance derived from :class:" -"`~configparser.RawConfigParser`. If a :class:`!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`." +"A filename, or a file-like object, or an instance derived " +"from :class:`~configparser.RawConfigParser`. If a :class:`!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 "" #: library/logging.config.rst:106 @@ -214,13 +214,13 @@ msgstr "" #: library/logging.config.rst:139 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`." +"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 "" #: library/logging.config.rst:148 @@ -337,8 +337,8 @@ 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; " +"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 "" @@ -379,11 +379,11 @@ msgstr "" #: library/logging.config.rst:266 msgid "" "An optional ``class`` key indicates the name of the formatter's class (as a " -"dotted module and class name). The instantiation arguments are as for :" -"class:`~logging.Formatter`, thus this key is most useful for instantiating a " -"customised subclass of :class:`~logging.Formatter`. For example, the " -"alternative class might present exception tracebacks in an expanded or " -"condensed format. If your formatter requires different or extra " +"dotted module and class name). The instantiation arguments are as " +"for :class:`~logging.Formatter`, thus this key is most useful for " +"instantiating a customised subclass of :class:`~logging.Formatter`. For " +"example, the alternative class might present exception tracebacks in an " +"expanded or condensed format. If your formatter requires different or extra " "configuration keys, you should use :ref:`logging-config-dict-userdef`." msgstr "" @@ -459,11 +459,11 @@ msgstr "" #: library/logging.config.rst:322 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``." +"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 "" #: library/logging.config.rst:328 @@ -508,8 +508,8 @@ 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." +"existing configuration with the same semantics as used by the " +"existing :func:`fileConfig` API." msgstr "" #: library/logging.config.rst:360 @@ -521,9 +521,9 @@ msgstr "" #: library/logging.config.rst:363 msgid "" "*disable_existing_loggers* - whether any existing non-root 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``." +"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 "" #: library/logging.config.rst:371 @@ -619,12 +619,12 @@ msgstr "" #: library/logging.config.rst:442 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." +"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 "" #: library/logging.config.rst:450 @@ -680,9 +680,9 @@ 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 " +"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 "" @@ -818,9 +818,9 @@ msgid "" "named ``bar``, problems would result, because the configuration of ``bar`` " "would be attempted before that of ``foo``, and ``foo`` would not yet have " "been configured. However, if the dependent handler were named ``foobar``, it " -"would be configured after ``foo``, with the result that ``cfg://handlers." -"foo`` would resolve to configured handler ``foo``, and not its configuration " -"dictionary." +"would be configured after ``foo``, with the result that ``cfg://" +"handlers.foo`` would resolve to configured handler ``foo``, and not its " +"configuration dictionary." msgstr "" #: library/logging.config.rst:602 @@ -836,10 +836,10 @@ msgid "" "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." +"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 "" #: library/logging.config.rst:617 @@ -870,15 +870,16 @@ msgstr "" #: library/logging.config.rst:639 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:" +"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 "" #: library/logging.config.rst:651 @@ -897,8 +898,8 @@ 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:" +"access by dot or by index, in a similar way to that provided by " +"``str.format``. Thus, given the following snippet:" msgstr "" #: library/logging.config.rst:667 @@ -920,14 +921,14 @@ msgid "" "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." +"``'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 "" #: library/logging.config.rst:693 @@ -948,12 +949,13 @@ msgstr "" 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::" +"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 "" #: library/logging.config.rst:717 @@ -977,14 +979,14 @@ msgstr "" #: library/logging.config.rst:730 msgid "" "If you want to configure a :class:`~logging.handlers.QueueHandler`, noting " -"that this is normally used in conjunction with a :class:`~logging.handlers." -"QueueListener`, you can configure both together. After the configuration, " -"the ``QueueListener`` instance will be available as the :attr:`~logging." -"handlers.QueueHandler.listener` attribute of the created handler, and that " -"in turn will be available to you using :func:`~logging.getHandlerByName` and " -"passing the name you have used for the ``QueueHandler`` in your " -"configuration. The dictionary schema for configuring the pair is shown in " -"the example YAML snippet below." +"that this is normally used in conjunction with " +"a :class:`~logging.handlers.QueueListener`, you can configure both together. " +"After the configuration, the ``QueueListener`` instance will be available as " +"the :attr:`~logging.handlers.QueueHandler.listener` attribute of the created " +"handler, and that in turn will be available to you " +"using :func:`~logging.getHandlerByName` and passing the name you have used " +"for the ``QueueHandler`` in your configuration. The dictionary schema for " +"configuring the pair is shown in the example YAML snippet below." msgstr "" #: library/logging.config.rst:739 @@ -1027,9 +1029,9 @@ msgstr "" #: library/logging.config.rst:763 msgid "" "A string that resolves to a callable which, when called with no arguments, " -"returns the queue instance to use. That callable could be a :class:`queue." -"Queue` subclass or a function which returns a suitable queue instance, such " -"as ``my.module.queue_factory()``." +"returns the queue instance to use. That callable could be " +"a :class:`queue.Queue` subclass or a function which returns a suitable queue " +"instance, such as ``my.module.queue_factory()``." msgstr "" #: library/logging.config.rst:768 @@ -1088,8 +1090,9 @@ msgstr "" #: library/logging.config.rst:794 msgid "" "Any custom queue handler and listener classes will need to be defined with " -"the same initialization signatures as :class:`~logging.handlers." -"QueueHandler` and :class:`~logging.handlers.QueueListener`." +"the same initialization signatures " +"as :class:`~logging.handlers.QueueHandler` " +"and :class:`~logging.handlers.QueueListener`." msgstr "" #: library/logging.config.rst:803 @@ -1098,8 +1101,8 @@ msgstr "" #: library/logging.config.rst:805 msgid "" -"The configuration file format understood by :func:`fileConfig` is based on :" -"mod:`configparser` functionality. The file must contain sections called " +"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 " @@ -1118,12 +1121,12 @@ 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." +"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 "" #: library/logging.config.rst:830 @@ -1216,9 +1219,9 @@ msgstr "" #: library/logging.config.rst:892 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'." +"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 "" #: library/logging.config.rst:896 @@ -1270,8 +1273,8 @@ msgid "" "class=handlers.SysLogHandler\n" "level=ERROR\n" "formatter=form05\n" -"args=(('localhost', handlers.SYSLOG_UDP_PORT), handlers.SysLogHandler." -"LOG_USER)\n" +"args=(('localhost', handlers.SYSLOG_UDP_PORT), " +"handlers.SysLogHandler.LOG_USER)\n" "\n" "[handler_hand06]\n" "class=handlers.NTEventLogHandler\n" @@ -1337,8 +1340,8 @@ 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." +"users with no mutual trust run code on the same machine; see " +"the :func:`listen` documentation for more information." msgstr "" #: library/logging.config.rst:995 diff --git a/library/logging.handlers.po b/library/logging.handlers.po index e0c1e10ac..acadf60bd 100644 --- a/library/logging.handlers.po +++ b/library/logging.handlers.po @@ -44,9 +44,9 @@ msgstr "" #: 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." +"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 "" #: library/logging.handlers.rst:33 @@ -57,30 +57,30 @@ msgstr "" 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)." +"or any file-like object (or, more precisely, any object which " +"supports :meth:`write` and :meth:`flush` methods)." msgstr "" #: 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." +"specified, the instance will use it for logging output; otherwise, " +"*sys.stderr* will be used." msgstr "" #: 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 followed by :attr:`terminator`. If exception " -"information is present, it is formatted using :func:`traceback." -"print_exception` and appended to the stream." +"information is present, it is formatted " +"using :func:`traceback.print_exception` and appended to the stream." msgstr "" #: 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." +"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 "" #: library/logging.handlers.rst:64 @@ -196,8 +196,8 @@ msgstr "" #: library/logging.handlers.rst:153 msgid "" -"See :ref:`library-config` for more information on how to use :class:" -"`NullHandler`." +"See :ref:`library-config` for more information on how to " +"use :class:`NullHandler`." msgstr "" #: library/logging.handlers.rst:159 @@ -206,10 +206,10 @@ msgstr "" #: library/logging.handlers.rst:163 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." +"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 "" #: library/logging.handlers.rst:167 @@ -261,11 +261,11 @@ msgstr "" #: library/logging.handlers.rst:216 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." +"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 "" #: library/logging.handlers.rst:224 @@ -298,10 +298,10 @@ msgid "" "determining the oldest files to delete. For this to happen, the filenames " "should be sortable using the date/time portion of the filename, and a namer " "needs to respect this. (If a namer is wanted that doesn't respect this " -"scheme, it will need to be used in a subclass of :class:" -"`TimedRotatingFileHandler` which overrides the :meth:" -"`~TimedRotatingFileHandler.getFilesToDelete` method to fit in with the " -"custom naming scheme.)" +"scheme, it will need to be used in a subclass " +"of :class:`TimedRotatingFileHandler` which overrides " +"the :meth:`~TimedRotatingFileHandler.getFilesToDelete` method to fit in with " +"the custom naming scheme.)" msgstr "" #: library/logging.handlers.rst:255 @@ -349,18 +349,18 @@ msgstr "" #: library/logging.handlers.rst:287 msgid "" -"The destination filename. This is normally what the source is rotated to, e." -"g. 'test.log.1'." +"The destination filename. This is normally what the source is rotated to, " +"e.g. 'test.log.1'." msgstr "" #: library/logging.handlers.rst:292 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." +"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 "" #: library/logging.handlers.rst:299 @@ -379,8 +379,8 @@ msgstr "" #: library/logging.handlers.rst:310 msgid "" -"The :class:`RotatingFileHandler` class, located in the :mod:`logging." -"handlers` module, supports rotation of disk log files." +"The :class:`RotatingFileHandler` class, located in " +"the :mod:`logging.handlers` module, supports rotation of disk log files." msgstr "" #: library/logging.handlers.rst:316 @@ -396,20 +396,21 @@ msgstr "" #: library/logging.handlers.rst:323 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 " +"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; but if either of *maxBytes* or *backupCount* is zero, rollover never " "occurs, so you generally want to set *backupCount* to at least 1, and have a " "non-zero *maxBytes*. When *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." +"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 "" #: library/logging.handlers.rst:347 library/logging.handlers.rst:453 @@ -428,9 +429,9 @@ msgstr "" #: library/logging.handlers.rst:360 msgid "" -"The :class:`TimedRotatingFileHandler` class, located in the :mod:`logging." -"handlers` module, supports rotation of disk log files at certain timed " -"intervals." +"The :class:`TimedRotatingFileHandler` class, located in " +"the :mod:`logging.handlers` module, supports rotation of disk log files at " +"certain timed intervals." msgstr "" #: library/logging.handlers.rst:367 @@ -554,8 +555,8 @@ msgstr "" #: library/logging.handlers.rst:415 msgid "" -"If *delay* is true, then file opening is deferred until the first call to :" -"meth:`emit`." +"If *delay* is true, then file opening is deferred until the first call " +"to :meth:`emit`." msgstr "" #: library/logging.handlers.rst:418 @@ -638,8 +639,9 @@ 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." +"connection. To unpickle the record at the receiving end into " +"a :class:`~logging.LogRecord`, use the :func:`~logging.makeLogRecord` " +"function." msgstr "" #: library/logging.handlers.rst:499 @@ -652,8 +654,8 @@ msgstr "" #: library/logging.handlers.rst:506 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`)." +"of socket they want. The default implementation creates a TCP socket " +"(:const:`socket.SOCK_STREAM`)." msgstr "" #: library/logging.handlers.rst:513 @@ -682,8 +684,8 @@ msgstr "" #: library/logging.handlers.rst:530 msgid "" "Send a pickled byte-string *packet* to the socket. The format of the sent " -"byte-string is as described in the documentation for :meth:`~SocketHandler." -"makePickle`." +"byte-string is as described in the documentation " +"for :meth:`~SocketHandler.makePickle`." msgstr "" #: library/logging.handlers.rst:534 @@ -765,8 +767,9 @@ msgstr "" 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." +"packet. To unpickle the record at the receiving end into " +"a :class:`~logging.LogRecord`, use the :func:`~logging.makeLogRecord` " +"function." msgstr "" #: library/logging.handlers.rst:597 @@ -799,22 +802,23 @@ msgid "" "``('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`." +"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 "" #: library/logging.handlers.rst:630 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." +"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 "" #: library/logging.handlers.rst:639 @@ -1163,14 +1167,14 @@ msgid "" "*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'``." +"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 "" #: library/logging.handlers.rst:808 @@ -1199,10 +1203,11 @@ 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." +"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 "" #: library/logging.handlers.rst:840 @@ -1241,8 +1246,8 @@ msgid "" "*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.)" +"keyfile and certificate file. (This tuple is passed to " +"the :meth:`smtplib.SMTP.starttls` method.)" msgstr "" #: library/logging.handlers.rst:871 @@ -1279,11 +1284,11 @@ msgstr "" #: library/logging.handlers.rst:897 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." +":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 "" #: library/logging.handlers.rst:906 @@ -1294,8 +1299,8 @@ msgstr "" #: library/logging.handlers.rst:912 msgid "" -"Append the record to the buffer. If :meth:`shouldFlush` returns true, call :" -"meth:`flush` to process the buffer." +"Append the record to the buffer. If :meth:`shouldFlush` returns true, " +"call :meth:`flush` to process the buffer." msgstr "" #: library/logging.handlers.rst:918 @@ -1363,13 +1368,13 @@ 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." +"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 "" #: library/logging.handlers.rst:990 @@ -1379,17 +1384,17 @@ msgstr "" #: library/logging.handlers.rst:995 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." +"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 "" #: library/logging.handlers.rst:1003 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." +"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 "" #: library/logging.handlers.rst:1007 @@ -1435,18 +1440,19 @@ msgstr "" #: library/logging.handlers.rst:1044 library/logging.handlers.rst:1133 msgid "" -"If you are using :mod:`multiprocessing`, you should avoid using :class:" -"`~queue.SimpleQueue` and instead use :class:`multiprocessing.Queue`." +"If you are using :mod:`multiprocessing`, you should avoid " +"using :class:`~queue.SimpleQueue` and instead " +"use :class:`multiprocessing.Queue`." msgstr "" #: library/logging.handlers.rst:1049 msgid "" -"Enqueues the result of preparing the LogRecord. Should an exception occur (e." -"g. because a bounded queue has filled up), the :meth:`~logging.Handler." -"handleError` method is called to handle the error. This can result in the " -"record silently being dropped (if :data:`logging.raiseExceptions` is " -"``False``) or a message printed to ``sys.stderr`` (if :data:`logging." -"raiseExceptions` is ``True``)." +"Enqueues the result of preparing the LogRecord. Should an exception occur " +"(e.g. because a bounded queue has filled up), " +"the :meth:`~logging.Handler.handleError` method is called to handle the " +"error. This can result in the record silently being dropped " +"(if :data:`logging.raiseExceptions` is ``False``) or a message printed to " +"``sys.stderr`` (if :data:`logging.raiseExceptions` is ``True``)." msgstr "" #: library/logging.handlers.rst:1058 @@ -1459,10 +1465,11 @@ msgstr "" msgid "" "The base implementation formats the record to merge the message, arguments, " "exception and stack information, if present. It also removes unpickleable " -"items from the record in-place. Specifically, it overwrites the record's :" -"attr:`msg` and :attr:`message` attributes with the merged message (obtained " -"by calling the handler's :meth:`format` method), and sets the :attr:`args`, :" -"attr:`exc_info` and :attr:`exc_text` attributes to ``None``." +"items from the record in-place. Specifically, it overwrites the " +"record's :attr:`msg` and :attr:`message` attributes with the merged message " +"(obtained by calling the handler's :meth:`format` method), and sets " +"the :attr:`args`, :attr:`exc_info` and :attr:`exc_text` attributes to " +"``None``." msgstr "" #: library/logging.handlers.rst:1069 @@ -1477,8 +1484,8 @@ msgid "" "The base implementation formats the message with arguments, sets the " "``message`` and ``msg`` attributes to the formatted message and sets the " "``args`` and ``exc_text`` attributes to ``None`` to allow pickling and to " -"prevent further attempts at formatting. This means that a handler on the :" -"class:`QueueListener` side won't have the information to do custom " +"prevent further attempts at formatting. This means that a handler on " +"the :class:`QueueListener` side won't have the information to do custom " "formatting, e.g. of exceptions. You may wish to subclass ``QueueHandler`` " "and override this method to e.g. avoid setting ``exc_text`` to ``None``. " "Note that the ``message`` / ``msg`` / ``args`` changes are related to " @@ -1512,9 +1519,9 @@ msgid "" "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`." +"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 "" #: library/logging.handlers.rst:1116 @@ -1534,8 +1541,8 @@ msgid "" "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. The queue is not *required* to have the task " -"tracking API (though it's used if available), which means that you can use :" -"class:`~queue.SimpleQueue` instances for *queue*." +"tracking API (though it's used if available), which means that you can " +"use :class:`~queue.SimpleQueue` instances for *queue*." msgstr "" #: library/logging.handlers.rst:1136 @@ -1578,8 +1585,8 @@ msgstr "" #: library/logging.handlers.rst:1164 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`." +"actual object passed to the handlers is that which is returned " +"from :meth:`prepare`." msgstr "" #: library/logging.handlers.rst:1170 diff --git a/library/logging.po b/library/logging.po index 9176186aa..d4d787b61 100644 --- a/library/logging.po +++ b/library/logging.po @@ -175,15 +175,15 @@ msgid "" "are all descendants of ``foo``. In addition, all loggers are descendants of " "the root logger. 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." +"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 "" #: library/logging.rst:123 msgid "" -"This is the logger's name, and is the value that was passed to :func:" -"`getLogger` to obtain the logger." +"This is the logger's name, and is the value that was passed " +"to :func:`getLogger` to obtain the logger." msgstr "" #: library/logging.rst:186 @@ -325,27 +325,29 @@ msgstr "" #: library/logging.rst:223 msgid "" "Indicates if a message of severity *level* would be processed by this " -"logger. This method checks first the module-level level set by ``logging." -"disable(level)`` and then the logger's effective level as determined by :" -"meth:`getEffectiveLevel`." +"logger. This method checks first the module-level level set by " +"``logging.disable(level)`` and then the logger's effective level as " +"determined by :meth:`getEffectiveLevel`." msgstr "" #: library/logging.rst:231 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." +"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 "" #: library/logging.rst:241 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." +"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 "" #: library/logging.rst:252 @@ -416,19 +418,19 @@ msgstr "" msgid "" "The third optional keyword argument is *stacklevel*, which defaults to " "``1``. If greater than 1, the corresponding number of stack frames are " -"skipped when computing the line number and function name set in the :class:" -"`LogRecord` created for the logging event. This can be used in logging " -"helpers so that the function name, filename and line number recorded are not " -"the information for the helper function/method, but rather its caller. The " -"name of this parameter mirrors the equivalent one in the :mod:`warnings` " -"module." +"skipped when computing the line number and function name set in " +"the :class:`LogRecord` created for the logging event. This can be used in " +"logging helpers so that the function name, filename and line number recorded " +"are not the information for the helper function/method, but rather its " +"caller. The name of this parameter mirrors the equivalent one in " +"the :mod:`warnings` module." msgstr "" #: library/logging.rst:306 msgid "" "The fourth keyword argument is *extra* which can be used to pass a " -"dictionary which is used to populate the :attr:`~object.__dict__` of the :" -"class:`LogRecord` created for the logging event with user-defined " +"dictionary which is used to populate the :attr:`~object.__dict__` of " +"the :class:`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 "" @@ -462,12 +464,12 @@ msgstr "" #: library/logging.rst:329 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 :class:`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." +"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 :class:`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 "" #: library/logging.rst:336 @@ -591,8 +593,8 @@ 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`." +"created locally. Logger-level filtering is applied " +"using :meth:`~Logger.filter`." msgstr "" #: library/logging.rst:450 @@ -706,17 +708,17 @@ msgstr "" #: library/logging.rst:518 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__`." +"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 "" #: library/logging.rst:527 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." +"list of filters to the empty list and creating a lock " +"(using :meth:`createLock`) for serializing access to an I/O mechanism." msgstr "" #: library/logging.rst:534 @@ -776,9 +778,9 @@ msgstr "" #: library/logging.rst:595 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." +"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 "" #: library/logging.rst:603 @@ -791,14 +793,15 @@ msgstr "" #: library/logging.rst:610 msgid "" "This method should be called from handlers when an exception is encountered " -"during an :meth:`emit` call. If the module-level attribute :data:" -"`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 :data:`raiseExceptions` is ``True``, as that " -"is more useful during development)." +"during an :meth:`emit` call. If the module-level " +"attribute :data:`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 :data:`raiseExceptions` is ``True``, as that is more useful during " +"development)." msgstr "" #: library/logging.rst:623 @@ -810,8 +813,8 @@ msgstr "" #: library/logging.rst:629 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`." +"version is intended to be implemented by subclasses and so raises " +"a :exc:`NotImplementedError`." msgstr "" #: library/logging.rst:633 @@ -861,9 +864,9 @@ msgstr "" #: library/logging.rst:663 msgid "" "A format string in the given *style* for the logged output as a whole. The " -"possible mapping keys are drawn from the :class:`LogRecord` object's :ref:" -"`logrecord-attributes`. If not specified, ``'%(message)s'`` is used, which " -"is just the logged message." +"possible mapping keys are drawn from the :class:`LogRecord` " +"object's :ref:`logrecord-attributes`. If not specified, ``'%(message)s'`` is " +"used, which is just the logged message." msgstr "" #: library/logging.rst:671 @@ -887,8 +890,8 @@ msgstr "" #: library/logging.rst:686 msgid "" "If ``True`` (the default), incorrect or mismatched *fmt* and *style* will " -"raise a :exc:`ValueError`; for example, ``logging.Formatter('%(asctime)s - " -"%(message)s', style='{')``." +"raise a :exc:`ValueError`; for example, ``logging.Formatter('%(asctime)s - %" +"(message)s', style='{')``." msgstr "" #: library/logging.rst:691 @@ -916,11 +919,11 @@ msgid "" "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` " +"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 (by setting the *exc_text* " "attribute to ``None``) after a formatter has done its formatting, so that " @@ -939,12 +942,12 @@ 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 format " -"'%Y-%m-%d %H:%M:%S,uuu' is used, where the uuu part is a millisecond value " -"and the other letters are as per the :func:`time.strftime` documentation. " -"An example time in this format is ``2003-01-23 00:29:50,411``. The " -"resulting string is returned." +"follows: if *datefmt* (a string) is specified, it is used " +"with :func:`time.strftime` to format the creation time of the record. " +"Otherwise, the format '%Y-%m-%d %H:%M:%S,uuu' is used, where the uuu part is " +"a millisecond value and the other letters are as per " +"the :func:`time.strftime` documentation. An example time in this format is " +"``2003-01-23 00:29:50,411``. The resulting string is returned." msgstr "" #: library/logging.rst:740 @@ -986,9 +989,9 @@ msgstr "" #: library/logging.rst:773 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." +"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 "" #: library/logging.rst:779 @@ -1074,8 +1077,8 @@ 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 " +"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 "" @@ -1106,10 +1109,10 @@ msgstr "" #: library/logging.rst:874 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)." +":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 "" #: library/logging.rst:882 @@ -1134,8 +1137,8 @@ msgstr "" msgid "" "The :ref:`numeric level ` of the logging event (such as ``10`` for " "``DEBUG``, ``20`` for ``INFO``, etc). Note that this is converted to *two* " -"attributes of the LogRecord: :attr:`!levelno` for the numeric value and :" -"attr:`!levelname` for the corresponding level name." +"attributes of the LogRecord: :attr:`!levelno` for the numeric value " +"and :attr:`!levelname` for the corresponding level name." msgstr "" #: library/logging.rst:903 @@ -1162,8 +1165,9 @@ msgstr "" #: library/logging.rst:920 msgid "" -"An exception tuple with the current exception information, as returned by :" -"func:`sys.exc_info`, or ``None`` if no exception information is available." +"An exception tuple with the current exception information, as returned " +"by :func:`sys.exc_info`, or ``None`` if no exception information is " +"available." msgstr "" #: library/logging.rst:925 @@ -1196,8 +1200,8 @@ msgstr "" #: library/logging.rst:949 msgid "" -"This functionality can be used to inject your own values into a :class:" -"`LogRecord` at creation time. You can use the following pattern::" +"This functionality can be used to inject your own values into " +"a :class:`LogRecord` at creation time. You can use the following pattern::" msgstr "" #: library/logging.rst:952 @@ -1237,8 +1241,8 @@ msgstr "" #: library/logging.rst:980 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 " +"`` 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 "" @@ -1303,8 +1307,8 @@ msgstr "" #: library/logging.rst:1006 msgid "" -"Time when the :class:`LogRecord` was created (as returned by :func:`time." -"time`)." +"Time when the :class:`LogRecord` was created (as returned " +"by :func:`time.time`)." msgstr "" #: library/logging.rst:1009 @@ -1365,8 +1369,8 @@ msgstr "" #: library/logging.rst:1020 msgid "" -"Numeric logging level for the message (:const:`DEBUG`, :const:`INFO`, :const:" -"`WARNING`, :const:`ERROR`, :const:`CRITICAL`)." +"Numeric logging level for the message " +"(:const:`DEBUG`, :const:`INFO`, :const:`WARNING`, :const:`ERROR`, :const:`CRITICAL`)." msgstr "" #: library/logging.rst:1025 @@ -1391,8 +1395,8 @@ msgstr "" #: library/logging.rst:1028 msgid "" -"The logged message, computed as ``msg % args``. This is set when :meth:" -"`Formatter.format` is invoked." +"The logged message, computed as ``msg % args``. This is set " +"when :meth:`Formatter.format` is invoked." msgstr "" #: library/logging.rst:1032 @@ -1557,8 +1561,9 @@ msgstr "" #: library/logging.rst:1079 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 `." +"information into logging calls. For a usage example, see the section " +"on :ref:`adding contextual information to your logging output `." msgstr "" #: library/logging.rst:1085 @@ -1587,20 +1592,18 @@ msgstr "" #: library/logging.rst:1104 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." +"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 "" #: library/logging.rst:1115 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." +"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 "" #: library/logging.rst:1121 @@ -1698,8 +1701,9 @@ msgstr "" #: library/logging.rst:1189 msgid "" -"The only difference is that if the root logger has no handlers, then :func:" -"`basicConfig` is called, prior to calling ``debug`` on the root logger." +"The only difference is that if the root logger has no handlers, " +"then :func:`basicConfig` is called, prior to calling ``debug`` on the root " +"logger." msgstr "" #: library/logging.rst:1192 @@ -1765,10 +1769,10 @@ msgid "" "useful. Its effect is to disable all logging calls of severity *level* 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." +"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 "" #: library/logging.rst:1252 @@ -1781,8 +1785,8 @@ msgstr "" #: library/logging.rst:1257 msgid "" -"The *level* parameter was defaulted to level ``CRITICAL``. See :issue:" -"`28524` for more information about this change." +"The *level* parameter was defaulted to level ``CRITICAL``. " +"See :issue:`28524` for more information about this change." msgstr "" #: library/logging.rst:1263 @@ -1797,8 +1801,8 @@ msgstr "" #: library/logging.rst:1270 msgid "" -"If you are thinking of defining your own levels, please see the section on :" -"ref:`custom-levels`." +"If you are thinking of defining your own levels, please see the section " +"on :ref:`custom-levels`." msgstr "" #: library/logging.rst:1275 @@ -1814,12 +1818,13 @@ msgstr "" #: library/logging.rst:1285 msgid "" -"If *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 *level* is returned. " -"If a numeric value corresponding to one of the defined levels is passed in, " -"the corresponding string representation is returned." +"If *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 *level* is returned. If a numeric value corresponding " +"to one of the defined levels is passed in, the corresponding string " +"representation is returned." msgstr "" #: library/logging.rst:1292 @@ -1839,9 +1844,9 @@ msgstr "" 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`), and " -"vice versa." +"level name displayed in the formatted log output by means of the ``%" +"(levelname)s`` format specifier (see :ref:`logrecord-attributes`), and vice " +"versa." msgstr "" #: library/logging.rst:1305 @@ -1865,18 +1870,19 @@ msgstr "" #: library/logging.rst:1326 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." +"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 "" #: library/logging.rst:1334 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." +"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 "" #: library/logging.rst:1340 @@ -2012,8 +2018,9 @@ msgid "" "If this keyword argument is specified along with *filename*, its value is " "used when the :class:`FileHandler` is created, and thus used when opening " "the output file. If not specified, the value 'backslashreplace' is used. " -"Note that if ``None`` is specified, it will be passed as such to :func:" -"`open`, which means that it will be treated the same as passing 'errors'." +"Note that if ``None`` is specified, it will be passed as such " +"to :func:`open`, which means that it will be treated the same as passing " +"'errors'." msgstr "" #: library/logging.rst:1421 @@ -2052,8 +2059,8 @@ msgstr "" 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 " +"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. After " "this call, as at any other time, do not instantiate loggers directly using " "the subclass: continue to use the :func:`logging.getLogger` API to get your " @@ -2157,13 +2164,13 @@ msgstr "" #: library/logging.rst:1492 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``." +"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 "" #: library/logging.rst:1504 @@ -2202,15 +2209,15 @@ 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`." +"logged to a logger named ``'py.warnings'`` with a severity " +"of :const:`WARNING`." msgstr "" #: library/logging.rst:1530 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)." +"will stop, and warnings will be redirected to their original destinations " +"(i.e. those in effect before ``captureWarnings(True)`` was called)." msgstr "" #: library/logging.rst:1537 @@ -2241,8 +2248,8 @@ msgstr "" #: library/logging.rst:1547 msgid "" -"`Original Python logging package `_" +"`Original Python logging package `_" msgstr "" #: library/logging.rst:1548 diff --git a/library/lzma.po b/library/lzma.po index 8773859e7..4bc2b5ab8 100644 --- a/library/lzma.po +++ b/library/lzma.po @@ -34,10 +34,10 @@ msgstr "" #: library/lzma.rst:21 msgid "" -"The interface provided by this module is very similar to that of the :mod:" -"`bz2` module. Note that :class:`LZMAFile` and :class:`bz2.BZ2File` are *not* " -"thread-safe, so if you need to use a single :class:`LZMAFile` instance from " -"multiple threads, it is necessary to protect it with a lock." +"The interface provided by this module is very similar to that of " +"the :mod:`bz2` module. Note that :class:`LZMAFile` and :class:`bz2.BZ2File` " +"are *not* thread-safe, so if you need to use a single :class:`LZMAFile` " +"instance from multiple threads, it is necessary to protect it with a lock." msgstr "" #: library/lzma.rst:29 @@ -58,10 +58,10 @@ msgstr "" #: 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), in " -"which case the named file is opened, or it can be an existing file object to " -"read from or write to." +"The *filename* argument can be either an actual file name (given as " +"a :class:`str`, :class:`bytes` or :term:`path-like ` " +"object), in which case the named file is opened, or it can be an existing " +"file object to read from or write to." msgstr "" #: library/lzma.rst:46 @@ -94,8 +94,8 @@ msgstr "" #: 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 " +"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 "" @@ -115,10 +115,10 @@ msgstr "" 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). When " -"wrapping an existing file object, the wrapped file will not be closed when " -"the :class:`LZMAFile` is closed." +"the file object to wrap, or the name of the file to open (as " +"a :class:`str`, :class:`bytes` or :term:`path-like ` " +"object). When wrapping an existing file object, the wrapped file will not be " +"closed when the :class:`LZMAFile` is closed." msgstr "" #: library/lzma.rst:83 @@ -144,9 +144,10 @@ msgstr "" #: library/lzma.rst:102 msgid "" -":class:`LZMAFile` supports all the members specified by :class:`io." -"BufferedIOBase`, except for :meth:`~io.BufferedIOBase.detach` and :meth:`~io." -"IOBase.truncate`. Iteration and the :keyword:`with` statement are supported." +":class:`LZMAFile` supports all the members specified " +"by :class:`io.BufferedIOBase`, except for :meth:`~io.BufferedIOBase.detach` " +"and :meth:`~io.IOBase.truncate`. Iteration and the :keyword:`with` statement " +"are supported." msgstr "" #: library/lzma.rst:107 @@ -162,10 +163,10 @@ msgstr "" #: library/lzma.rst:115 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*)." +"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 "" #: library/lzma.rst:120 @@ -189,8 +190,8 @@ msgstr "" #: library/lzma.rst:138 msgid "" -"For a more convenient way of compressing a single chunk of data, see :func:" -"`compress`." +"For a more convenient way of compressing a single chunk of data, " +"see :func:`compress`." msgstr "" #: library/lzma.rst:141 @@ -271,19 +272,20 @@ msgstr "" #: library/lzma.rst:178 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." +"``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 "" #: library/lzma.rst:187 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." +"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 "" #: library/lzma.rst:193 @@ -296,9 +298,9 @@ msgstr "" 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`." +"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 "" #: library/lzma.rst:206 @@ -327,8 +329,8 @@ msgstr "" 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`." +"``.lzma`` files. Other possible values " +"are :const:`FORMAT_XZ`, :const:`FORMAT_ALONE`, and :const:`FORMAT_RAW`." msgstr "" #: library/lzma.rst:225 @@ -342,9 +344,9 @@ msgstr "" #: library/lzma.rst:230 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." +"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 "" #: library/lzma.rst:236 @@ -381,9 +383,9 @@ msgstr "" #: library/lzma.rst:261 msgid "" -"Attempting to decompress data after the end of stream is reached raises an :" -"exc:`EOFError`. Any data found after the end of the stream is ignored and " -"saved in the :attr:`~.unused_data` attribute." +"Attempting to decompress data after the end of stream is reached raises " +"an :exc:`EOFError`. Any data found after the end of the stream is ignored " +"and saved in the :attr:`~.unused_data` attribute." msgstr "" #: library/lzma.rst:265 @@ -392,9 +394,9 @@ msgstr "" #: library/lzma.rst:270 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." +"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 "" #: library/lzma.rst:276 @@ -456,9 +458,10 @@ msgstr "" #: library/lzma.rst:319 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." +":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 "" #: library/lzma.rst:328 @@ -483,8 +486,8 @@ msgstr "" #: library/lzma.rst:338 msgid "" -":const:`FILTER_LZMA2` (for use with :const:`FORMAT_XZ` and :const:" -"`FORMAT_RAW`)" +":const:`FILTER_LZMA2` (for use with :const:`FORMAT_XZ` " +"and :const:`FORMAT_RAW`)" msgstr "" #: library/lzma.rst:340 @@ -574,8 +577,9 @@ msgstr "" #: library/lzma.rst:371 msgid "" -"``mf``: What match finder to use -- :const:`MF_HC3`, :const:`MF_HC4`, :const:" -"`MF_BT2`, :const:`MF_BT3`, or :const:`MF_BT4`." +"``mf``: What match finder to use " +"-- :const:`MF_HC3`, :const:`MF_HC4`, :const:`MF_BT2`, :const:`MF_BT3`, " +"or :const:`MF_BT4`." msgstr "" #: library/lzma.rst:373 diff --git a/library/mailbox.po b/library/mailbox.po index c3ece5fcd..05fadc649 100644 --- a/library/mailbox.po +++ b/library/mailbox.po @@ -27,11 +27,12 @@ msgstr "" #: 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." +"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 "" #: library/mailbox.rst:24 @@ -53,8 +54,9 @@ msgstr "" #: 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." +"instantiated. Instead, format-specific subclasses should inherit " +"from :class:`!Mailbox` and your code should instantiate a particular " +"subclass." msgstr "" #: library/mailbox.rst:41 @@ -101,8 +103,8 @@ msgstr "" 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 :class:`Maildir`; try to avoid using single-file formats such as :" -"class:`mbox` for concurrent writing. If you're modifying a mailbox, you " +"tasks is :class:`Maildir`; try to avoid using single-file formats such " +"as :class:`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 " @@ -120,13 +122,13 @@ msgstr "" #: library/mailbox.rst:89 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." +"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 "" #: library/mailbox.rst:98 @@ -141,15 +143,15 @@ msgstr "" 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." +"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 "" #: library/mailbox.rst:117 msgid "" -"Replace the message corresponding to *key* with *message*. Raise a :exc:" -"`KeyError` exception if no message already corresponds to *key*." +"Replace the message corresponding to *key* with *message*. Raise " +"a :exc:`KeyError` exception if no message already corresponds to *key*." msgstr "" #: library/mailbox.rst:120 @@ -177,9 +179,9 @@ msgstr "" #: library/mailbox.rst:145 msgid "" "Return an :term:`iterator` over representations of all messages. 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." +"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 "" #: library/mailbox.rst:153 @@ -212,10 +214,10 @@ msgstr "" #: library/mailbox.rst:181 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 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 "" @@ -223,8 +225,8 @@ msgstr "" #: library/mailbox.rst:192 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." +"of the appropriate format-specific :class:`Message` subclass, or raise " +"a :exc:`KeyError` exception if no such message exists." msgstr "" #: library/mailbox.rst:199 @@ -281,9 +283,9 @@ msgstr "" 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." +"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 "" #: library/mailbox.rst:262 @@ -291,9 +293,9 @@ 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." +"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 "" #: library/mailbox.rst:272 @@ -303,8 +305,8 @@ msgid "" "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." +"exception will be raised, so in general it is incorrect for *arg* to be " +"a :class:`!Mailbox` instance." msgstr "" #: library/mailbox.rst:282 @@ -375,20 +377,21 @@ msgstr "" #: library/mailbox.rst:339 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." +"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 "" #: library/mailbox.rst:346 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 " +"``'.'`` 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\"." @@ -535,8 +538,8 @@ msgstr "" 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 " +"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 \" " @@ -551,15 +554,15 @@ msgstr "" #: library/mailbox.rst:487 msgid "" -"Using the file after calling :meth:`~Mailbox.flush` or :meth:`~Mailbox." -"close` on the :class:`!mbox` instance may yield unpredictable results or " -"raise an exception." +"Using the file after calling :meth:`~Mailbox.flush` " +"or :meth:`~Mailbox.close` on the :class:`!mbox` instance may yield " +"unpredictable results or raise an exception." msgstr "" #: library/mailbox.rst:704 library/mailbox.rst:755 msgid "" -"Three locking mechanisms are used---dot locking and, if available, the :c:" -"func:`!flock` and :c:func:`!lockf` system calls." +"Three locking mechanisms are used---dot locking and, if available, " +"the :c:func:`!flock` and :c:func:`!lockf` system calls." msgstr "" #: library/mailbox.rst:501 @@ -653,8 +656,8 @@ msgstr "" #: library/mailbox.rst:576 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`." +"dictionary of names mapped to key lists, like returned " +"by :meth:`get_sequences`." msgstr "" #: library/mailbox.rst:583 @@ -683,11 +686,11 @@ msgstr "" #: library/mailbox.rst:606 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." +"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 "" #: library/mailbox.rst:615 @@ -714,8 +717,8 @@ msgstr "" #: library/mailbox.rst:634 msgid "" -"Home page of :program:`nmh`, an updated version of the original :program:" -"`mh`." +"Home page of :program:`nmh`, an updated version of the " +"original :program:`mh`." msgstr "" #: library/mailbox.rst:636 @@ -853,9 +856,9 @@ msgstr "" #: library/mailbox.rst:747 msgid "" -"Using the file after calling :meth:`~Mailbox.flush` or :meth:`~Mailbox." -"close` on the :class:`!MMDF` instance may yield unpredictable results or " -"raise an exception." +"Using the file after calling :meth:`~Mailbox.flush` " +"or :meth:`~Mailbox.close` on the :class:`!MMDF` instance may yield " +"unpredictable results or raise an exception." msgstr "" #: library/mailbox.rst:761 @@ -885,9 +888,9 @@ msgstr "" #: library/mailbox.rst:777 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." +"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 "" #: library/mailbox.rst:781 @@ -896,9 +899,9 @@ msgid "" "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 " +"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 "" @@ -937,16 +940,16 @@ msgstr "" #: library/mailbox.rst:818 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:" +"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 "" #: library/mailbox.rst:997 library/mailbox.rst:1368 @@ -1111,10 +1114,10 @@ msgstr "" #: library/mailbox.rst:922 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:" +"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 "" #: library/mailbox.rst:946 library/mailbox.rst:1068 library/mailbox.rst:1100 @@ -1166,8 +1169,8 @@ msgstr "" #: library/mailbox.rst:942 msgid "" -"When a :class:`!MaildirMessage` instance is created based upon an :class:" -"`MHMessage` instance, the following conversions take place:" +"When a :class:`!MaildirMessage` instance is created based upon " +"an :class:`MHMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1085 library/mailbox.rst:1457 @@ -1198,8 +1201,8 @@ msgstr "" #: library/mailbox.rst:957 msgid "" -"When a :class:`!MaildirMessage` instance is created based upon a :class:" -"`BabylMessage` instance, the following conversions take place:" +"When a :class:`!MaildirMessage` instance is created based upon " +"a :class:`BabylMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1100 library/mailbox.rst:1472 @@ -1305,8 +1308,8 @@ msgid "" "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 :func:`time.strftime`, or ``True`` (to use :" -"func:`time.gmtime`)." +"tuple suitable for passing to :func:`time.strftime`, or ``True`` (to " +"use :func:`time.gmtime`)." msgstr "" #: library/mailbox.rst:1408 @@ -1340,9 +1343,9 @@ msgstr "" #: library/mailbox.rst:1062 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 " +"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 "" @@ -1352,8 +1355,8 @@ msgstr "" #: library/mailbox.rst:1081 msgid "" -"When an :class:`!mboxMessage` instance is created based upon an :class:" -"`MHMessage` instance, the following conversions take place:" +"When an :class:`!mboxMessage` instance is created based upon " +"an :class:`MHMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1102 library/mailbox.rst:1474 @@ -1362,15 +1365,15 @@ msgstr "" #: library/mailbox.rst:1096 msgid "" -"When an :class:`!mboxMessage` instance is created based upon a :class:" -"`BabylMessage` instance, the following conversions take place:" +"When an :class:`!mboxMessage` instance is created based upon " +"a :class:`BabylMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1111 msgid "" -"When a :class:`!mboxMessage` instance is created based upon an :class:" -"`MMDFMessage` instance, the \"From \" line is copied and all flags directly " -"correspond:" +"When a :class:`!mboxMessage` instance is created based upon " +"an :class:`MMDFMessage` instance, the \"From \" line is copied and all flags " +"directly correspond:" msgstr "" #: library/mailbox.rst:1116 @@ -1391,9 +1394,9 @@ msgstr "" 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:" +"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 "" #: library/mailbox.rst:1148 @@ -1438,8 +1441,8 @@ msgstr "" #: library/mailbox.rst:1179 msgid "" -"When an :class:`!MHMessage` instance is created based upon a :class:" -"`MaildirMessage` instance, the following conversions take place:" +"When an :class:`!MHMessage` instance is created based upon " +"a :class:`MaildirMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1311 @@ -1448,10 +1451,10 @@ msgstr "" #: library/mailbox.rst:1192 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:" +"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 "" #: library/mailbox.rst:1329 @@ -1460,8 +1463,8 @@ msgstr "" #: library/mailbox.rst:1208 msgid "" -"When an :class:`!MHMessage` instance is created based upon a :class:" -"`BabylMessage` instance, the following conversions take place:" +"When an :class:`!MHMessage` instance is created based upon " +"a :class:`BabylMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1223 @@ -1560,8 +1563,8 @@ msgstr "" #: library/mailbox.rst:1287 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 " +"*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 "" @@ -1572,16 +1575,16 @@ msgid "" "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 " +"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 "" #: library/mailbox.rst:1305 msgid "" -"When a :class:`!BabylMessage` instance is created based upon a :class:" -"`MaildirMessage` instance, the following conversions take place:" +"When a :class:`!BabylMessage` instance is created based upon " +"a :class:`MaildirMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1317 @@ -1590,16 +1593,16 @@ msgstr "" #: library/mailbox.rst:1320 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:" +"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 "" #: library/mailbox.rst:1336 msgid "" -"When a :class:`!BabylMessage` instance is created based upon an :class:" -"`MHMessage` instance, the following conversions take place:" +"When a :class:`!BabylMessage` instance is created based upon " +"an :class:`MHMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1351 @@ -1634,29 +1637,29 @@ msgstr "" #: library/mailbox.rst:1434 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 " +"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 "" #: library/mailbox.rst:1453 msgid "" -"When an :class:`!MMDFMessage` instance is created based upon an :class:" -"`MHMessage` instance, the following conversions take place:" +"When an :class:`!MMDFMessage` instance is created based upon " +"an :class:`MHMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1468 msgid "" -"When an :class:`!MMDFMessage` instance is created based upon a :class:" -"`BabylMessage` instance, the following conversions take place:" +"When an :class:`!MMDFMessage` instance is created based upon " +"a :class:`BabylMessage` instance, the following conversions take place:" msgstr "" #: library/mailbox.rst:1483 msgid "" -"When an :class:`!MMDFMessage` instance is created based upon an :class:" -"`mboxMessage` instance, the \"From \" line is copied and all flags directly " -"correspond:" +"When an :class:`!MMDFMessage` instance is created based upon " +"an :class:`mboxMessage` instance, the \"From \" line is copied and all flags " +"directly correspond:" msgstr "" #: library/mailbox.rst:1488 diff --git a/library/mailcap.po b/library/mailcap.po index 99d0972da..f9851403d 100644 --- a/library/mailcap.po +++ b/library/mailcap.po @@ -36,9 +36,9 @@ msgid "" "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 " +"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 "" @@ -64,8 +64,8 @@ msgid "" "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." +"body of the given MIME type or alter the existing body data. " +"See :rfc:`1524` for a complete list of these fields." msgstr "" #: library/mailcap.rst:45 @@ -91,9 +91,9 @@ msgstr "" 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." +"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 "" #: library/mailcap.rst:65 diff --git a/library/marshal.po b/library/marshal.po index 24c48c199..f8c8c8493 100644 --- a/library/marshal.po +++ b/library/marshal.po @@ -35,13 +35,13 @@ 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." +"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 "" #: library/marshal.rst:33 @@ -60,8 +60,8 @@ msgid "" "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 " +"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 "" @@ -84,10 +84,10 @@ msgstr "" #: library/marshal.rst:62 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`." +"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 "" #: library/marshal.rst:66 @@ -118,8 +118,9 @@ msgstr "" #: library/marshal.rst:83 msgid "" -"If an object containing an unsupported type was marshalled with :func:" -"`dump`, :func:`load` will substitute ``None`` for the unmarshallable type." +"If an object containing an unsupported type was marshalled " +"with :func:`dump`, :func:`load` will substitute ``None`` for the " +"unmarshallable type." msgstr "" #: library/marshal.rst:88 diff --git a/library/math.po b/library/math.po index b3113cb90..d6c58b7bf 100644 --- a/library/math.po +++ b/library/math.po @@ -64,8 +64,8 @@ msgstr "Sayı teorisi ve temsil fonksiyonları" #: 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 :meth:`x.__ceil__ `, which should return an :class:`~numbers.Integral` value." +"*x*. If *x* is not a float, delegates to :meth:`x.__ceil__ " +"`, which should return an :class:`~numbers.Integral` value." msgstr "" "*x*'in tavanını, yani *x*'ten büyük veya ona eşit en küçük tamsayıyı " "döndürür. Eğer *x* bir float değilse, bir :class:`~numbers.Integral` değeri " @@ -97,8 +97,8 @@ msgstr "" #: library/math.rst:258 msgid "" -"Raises :exc:`TypeError` if either of the arguments are not integers. Raises :" -"exc:`ValueError` if either of the arguments are negative." +"Raises :exc:`TypeError` if either of the arguments are not integers. " +"Raises :exc:`ValueError` if either of the arguments are negative." msgstr "" "Herhangi bir argümanın tamsayı olmaması durumunda :exc:`TypeError` fırlatır. " "Herhangi bir argümanın negatif olması durumunda :exc:`ValueError` fırlatır." @@ -122,8 +122,8 @@ msgid "" "Return *n* factorial as an integer. Raises :exc:`ValueError` if *n* is not " "integral or is negative." msgstr "" -"*n* faktöriyeli tamsayı olarak döndürür. *n* tamsayı değil veya negatifse :" -"exc:`ValueError` fırlatır." +"*n* faktöriyeli tamsayı olarak döndürür. *n* tamsayı değil veya " +"negatifse :exc:`ValueError` fırlatır." #: library/math.rst:74 msgid "Accepting floats with integral values (like ``5.0``) is deprecated." @@ -211,13 +211,13 @@ msgstr "" #, fuzzy msgid "" "For further discussion and two alternative approaches, see the `ASPN " -"cookbook recipes for accurate floating-point summation `_\\." +"cookbook recipes for accurate floating-point summation `_\\." msgstr "" "Daha fazla tartışma ve iki alternatif yaklaşım için, `ASPN cookbook recipes " -"for accurate floating point summation `_ sayfasına bakın." +"for accurate floating point summation `_ sayfasına bakın." #: library/math.rst:126 msgid "" @@ -363,8 +363,8 @@ msgstr "" #: library/math.rst:217 msgid "" -"Return ``x * (2**i)``. This is essentially the inverse of function :func:" -"`frexp`." +"Return ``x * (2**i)``. This is essentially the inverse of " +"function :func:`frexp`." msgstr "" "``x * (2**i)`` döndürür. Bu aslında :func:`frexp` fonksiyonunun tersidir." @@ -484,9 +484,9 @@ msgid "" msgstr "" "Özel durumlar IEEE 754'ü takip eder: özellikle, ``remainder(x, math.inf)`` " "herhangi bir sonlu *x* için *x*'dir ve ``remainder(x, 0)`` ve " -"``remainder(math.inf, x)`` NaN olmayan herhangi bir *x* için :exc:" -"`ValueError` yükseltir. Eğer kalan işleminin sonucu sıfır ise, bu sıfır *x* " -"ile aynı işarete sahip olacaktır." +"``remainder(math.inf, x)`` NaN olmayan herhangi bir *x* " +"için :exc:`ValueError` yükseltir. Eğer kalan işleminin sonucu sıfır ise, bu " +"sıfır *x* ile aynı işarete sahip olacaktır." #: library/math.rst:291 #, fuzzy @@ -524,14 +524,14 @@ msgid "" "Return *x* with the fractional part removed, leaving the integer part. This " "rounds toward 0: ``trunc()`` is equivalent to :func:`floor` for positive " "*x*, and equivalent to :func:`ceil` for negative *x*. If *x* is not a float, " -"delegates to :meth:`x.__trunc__ `, which should return an :" -"class:`~numbers.Integral` value." +"delegates to :meth:`x.__trunc__ `, which should return " +"an :class:`~numbers.Integral` value." msgstr "" "Kesirli kısmı çıkarılmış ve tamsayı kısmı bırakılmış *x* döndürür. Bu 0'a " -"yuvarlanır: ``trunc()`` pozitif *x* için :func:`floor` ve negatif *x* için :" -"func:`ceil` ile eşdeğerdir. Eğer *x* bir float değilse, bir :class:`~numbers." -"Integral` değeri döndürmesi gereken :meth:`x.__trunc__ `'a " -"delege eder." +"yuvarlanır: ``trunc()`` pozitif *x* için :func:`floor` ve negatif *x* " +"için :func:`ceil` ile eşdeğerdir. Eğer *x* bir float değilse, " +"bir :class:`~numbers.Integral` değeri döndürmesi gereken :meth:`x.__trunc__ " +"`'a delege eder." #: library/math.rst:323 msgid "Return the value of the least significant bit of the float *x*:" @@ -553,12 +553,12 @@ msgstr "Eğer *x* pozitif bir sonsuzluk ise, *x* değerini döndürür." #: library/math.rst:328 msgid "" "If *x* is equal to zero, return the smallest positive *denormalized* " -"representable float (smaller than the minimum positive *normalized* float, :" -"data:`sys.float_info.min `)." +"representable float (smaller than the minimum positive *normalized* " +"float, :data:`sys.float_info.min `)." msgstr "" "Eğer *x* sıfıra eşitse, temsil edilebilir en küçük pozitif *normalize* " -"floatı döndürür (minimum pozitif *normalize* floattan daha küçük, :data:`sys." -"float_info.min `)." +"floatı döndürür (minimum pozitif *normalize* floattan daha " +"küçük, :data:`sys.float_info.min `)." #: library/math.rst:331 msgid "" @@ -585,11 +585,11 @@ msgstr "ULP, \"Son Yerdeki Birim\" anlamına gelmektedir." #: library/math.rst:340 msgid "" -"See also :func:`math.nextafter` and :data:`sys.float_info.epsilon `." +"See also :func:`math.nextafter` and :data:`sys.float_info.epsilon " +"`." msgstr "" -"Ayrıca bakınız :func:`math.nextafter` ve :data:`sys.float_info.epsilon `." +"Ayrıca bakınız :func:`math.nextafter` ve :data:`sys.float_info.epsilon " +"`." #: library/math.rst:346 msgid "" @@ -721,8 +721,8 @@ msgid "" "arguments to type :class:`float`. Use ``**`` or the built-in :func:`pow` " "function for computing exact integer powers." msgstr "" -"Yerleşik ``**`` operatörünün aksine, :func:`math.pow` her iki argümanını da :" -"class:`float` türüne dönüştürür. Tam sayı kuvvetlerini hesaplamak için " +"Yerleşik ``**`` operatörünün aksine, :func:`math.pow` her iki argümanını " +"da :class:`float` türüne dönüştürür. Tam sayı kuvvetlerini hesaplamak için " "``**`` veya yerleşik :func:`pow` fonksiyonunu kullanın." #: library/math.rst:445 @@ -764,8 +764,8 @@ msgid "" "Return the arc tangent of *x*, in radians. The result is between ``-pi/2`` " "and ``pi/2``." msgstr "" -"Radyan cinsinden *x*'in yay tanjantını döndürür. Sonuç ``-pi/2`` ile " -"``pi/2`` arasındadır." +"Radyan cinsinden *x*'in yay tanjantını döndürür. Sonuç ``-pi/2`` ile ``pi/" +"2`` arasındadır." #: library/math.rst:479 msgid "" @@ -773,15 +773,15 @@ msgid "" "``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``." +"for the angle. For example, ``atan(1)`` and ``atan2(1, 1)`` are both ``pi/" +"4``, but ``atan2(-1, -1)`` is ``-3*pi/4``." msgstr "" "Radyan cinsinden ``atan(y / x)`` döndürür. Sonuç ``-pi`` ile ``pi`` " "arasındadır. Düzlemde orijinden ``(x, y)`` noktasına kadar olan vektör, " "pozitif X ekseni ile bu açıyı yapar. :func:`atan2` 'nin amacı, her iki " "girdinin de işaretlerinin bilinmesidir, böylece açı için doğru kadranı " -"hesaplayabilir. Örneğin, ``atan(1)`` ve ``atan2(1, 1)`` her ikisi de " -"``pi/4`` 'tür, ancak ``atan2(-1, -1)`` ise ``-3*pi/4`` 'tür." +"hesaplayabilir. Örneğin, ``atan(1)`` ve ``atan2(1, 1)`` her ikisi de ``pi/" +"4`` 'tür, ancak ``atan2(-1, -1)`` ise ``-3*pi/4`` 'tür." #: library/math.rst:489 msgid "Return the cosine of *x* radians." @@ -912,12 +912,13 @@ msgstr "" #, fuzzy msgid "" "The :func:`erf` function can be used to compute traditional statistical " -"functions such as the `cumulative standard normal distribution `_::" +"functions such as the `cumulative standard normal distribution `_::" msgstr "" -":func:`erf` fonksiyonu, `kümülatif standart normal dağılım `_: " -"gibi geleneksel istatistiksel fonksiyonları hesaplamak için kullanılabilir:" +":func:`erf` fonksiyonu, `kümülatif standart normal dağılım `_: gibi geleneksel " +"istatistiksel fonksiyonları hesaplamak için kullanılabilir:" #: library/math.rst:597 msgid "" @@ -936,9 +937,9 @@ msgid "" msgstr "" "*x* 'de tamamlayıcı hata fonksiyonunu döndürür. `Tamamlayıcı hata " "fonksiyonu `_ ``1.0 - erf(x)`` " -"olarak tanımlanır. Birbirinden çıkarmanın `anlamlılık kaybına `_ neden olacağı büyük *x* değerleri " -"için kullanılır.\\" +"olarak tanımlanır. Birbirinden çıkarmanın `anlamlılık kaybına `_ neden olacağı büyük *x* " +"değerleri için kullanılır.\\" #: library/math.rst:617 msgid "" @@ -984,8 +985,8 @@ msgstr "" #: library/math.rst:657 msgid "" -"A floating-point positive infinity. (For negative infinity, use ``-math." -"inf``.) Equivalent to the output of ``float('inf')``." +"A floating-point positive infinity. (For negative infinity, use ``-" +"math.inf``.) Equivalent to the output of ``float('inf')``." msgstr "" "Bir kayan noktalı pozitif sonsuzluk. (Negatif sonsuzluk için ``-math.inf`` " "kullanın.) ``float('inf')`` çıktısına eşdeğerdir." @@ -1016,27 +1017,27 @@ msgstr "Artık her zaman kullanılabilir." 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'))``." +"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 "" ":mod:`math` modülü çoğunlukla platform C matematik kütüphanesi fonksiyonları " "etrafındaki ince sarmalayıcılardan oluşur. İstisnai durumlarda davranış, " "uygun olan yerlerde C99 standardının Ek F'sini takip eder. Mevcut uygulama, " -"``sqrt(-1.0)`` veya ``log(0.0)`` gibi geçersiz işlemler için :exc::exc:" -"`ValueError` (C99 Annex F geçersiz işlem veya sıfıra bölme sinyalini önerir) " -"ve taşan sonuçlar için :exc:`OverflowError` (örneğin, ``exp(1000.0)``) " -"yükseltir. Girdi argümanlarından biri veya daha fazlası NaN olmadığı sürece " -"yukarıdaki fonksiyonların hiçbirinden NaN döndürülmeyecektir; bu durumda, " -"çoğu fonksiyon bir NaN döndürecektir, ancak (yine C99 Ek F'yi takip ederek) " -"bu kuralın bazı istisnaları vardır, örneğin ``pow(float('nan'), 0.0)`` veya " -"``hypot(float('nan'), float('inf'))``." +"``sqrt(-1.0)`` veya ``log(0.0)`` gibi geçersiz işlemler " +"için :exc::exc:`ValueError` (C99 Annex F geçersiz işlem veya sıfıra bölme " +"sinyalini önerir) ve taşan sonuçlar için :exc:`OverflowError` (örneğin, " +"``exp(1000.0)``) yükseltir. Girdi argümanlarından biri veya daha fazlası " +"NaN olmadığı sürece yukarıdaki fonksiyonların hiçbirinden NaN " +"döndürülmeyecektir; bu durumda, çoğu fonksiyon bir NaN döndürecektir, ancak " +"(yine C99 Ek F'yi takip ederek) bu kuralın bazı istisnaları vardır, örneğin " +"``pow(float('nan'), 0.0)`` veya ``hypot(float('nan'), float('inf'))``." #: library/math.rst:703 msgid "" diff --git a/library/mimetypes.po b/library/mimetypes.po index d91adbc75..30810f6ba 100644 --- a/library/mimetypes.po +++ b/library/mimetypes.po @@ -63,8 +63,8 @@ msgstr "" 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 " +"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 "" @@ -94,8 +94,8 @@ msgstr "" #: library/mimetypes.rst:78 msgid "" -"The optional *strict* argument has the same meaning as with the :func:" -"`guess_type` function." +"The optional *strict* argument has the same meaning as with " +"the :func:`guess_type` function." msgstr "" #: library/mimetypes.rst:71 @@ -103,9 +103,9 @@ 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." +"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 "" #: library/mimetypes.rst:80 @@ -181,8 +181,9 @@ msgstr "" 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." +"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 "" #: library/mimetypes.rst:147 @@ -233,9 +234,10 @@ 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." +"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 "" #: library/mimetypes.rst:194 @@ -248,9 +250,10 @@ msgstr "" 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." +"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 "" #: library/mimetypes.rst:209 @@ -271,8 +274,8 @@ msgstr "" 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`." +"second one is for the standard types. They are initialized " +"by :data:`common_types` and :data:`types_map`." msgstr "" #: library/mimetypes.rst:231 @@ -295,8 +298,8 @@ msgstr "" #: library/mimetypes.rst:249 msgid "" -"Load MIME information from a file named *filename*. This uses :meth:" -"`readfp` to parse the file." +"Load MIME information from a file named *filename*. This " +"uses :meth:`readfp` to parse the file." msgstr "" #: library/mimetypes.rst:252 diff --git a/library/mmap.po b/library/mmap.po index e64891afe..6b92cf5ce 100644 --- a/library/mmap.po +++ b/library/mmap.po @@ -33,14 +33,14 @@ msgstr "" #: library/mmap.rst:11 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." +"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 "" #: library/mmap.rst:19 @@ -72,10 +72,10 @@ msgid "" "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." +"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 "" #: library/mmap.rst:46 @@ -113,8 +113,8 @@ msgstr "" 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 :const:" -"`ALLOCATIONGRANULARITY`." +"defaults to 0. *offset* must be a multiple of " +"the :const:`ALLOCATIONGRANULARITY`." msgstr "" #: library/mmap.rst:163 @@ -127,8 +127,8 @@ msgstr "" 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.mmap` is called." +"maximum length of the map will be the current size of the file " +"when :class:`~mmap.mmap` is called." msgstr "" #: library/mmap.rst:82 @@ -204,8 +204,8 @@ msgstr "" #: library/mmap.rst:134 msgid "" -":class:`~mmap.mmap` can also be used as a context manager in a :keyword:" -"`with` statement::" +":class:`~mmap.mmap` can also be used as a context manager in " +"a :keyword:`with` statement::" msgstr "" #: library/mmap.rst:137 @@ -275,8 +275,8 @@ msgid "" "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. *offset* must be a multiple of the :const:" -"`PAGESIZE` or :const:`ALLOCATIONGRANULARITY`." +"extent of the mapping is flushed. *offset* must be a multiple of " +"the :const:`PAGESIZE` or :const:`ALLOCATIONGRANULARITY`." msgstr "" #: library/mmap.rst:201 @@ -295,10 +295,11 @@ msgstr "" #: library/mmap.rst:212 msgid "" "Send advice *option* to the kernel about the memory region beginning at " -"*start* and extending *length* bytes. *option* must be one of the :ref:" -"`MADV_* constants ` available on the system. If *start* " -"and *length* are omitted, the entire mapping is spanned. On some systems " -"(including Linux), *start* must be a multiple of the :const:`PAGESIZE`." +"*start* and extending *length* bytes. *option* must be one of " +"the :ref:`MADV_* constants ` available on the system. If " +"*start* and *length* are omitted, the entire mapping is spanned. On some " +"systems (including Linux), *start* must be a multiple of " +"the :const:`PAGESIZE`." msgstr "" #: library/mmap.rst:219 @@ -370,8 +371,8 @@ msgstr "" 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)." +"``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 "" #: library/mmap.rst:291 @@ -426,10 +427,10 @@ msgstr "" #: library/mmap.rst:376 msgid "" -"These are the various flags that can be passed to :meth:`mmap.mmap`. :data:" -"`MAP_ALIGNED_SUPER` is only available at FreeBSD and :data:`MAP_CONCEAL` is " -"only available at OpenBSD. Note that some options might not be present on " -"some systems." +"These are the various flags that can be passed " +"to :meth:`mmap.mmap`. :data:`MAP_ALIGNED_SUPER` is only available at " +"FreeBSD and :data:`MAP_CONCEAL` is only available at OpenBSD. Note that " +"some options might not be present on some systems." msgstr "" #: library/mmap.rst:380 diff --git a/library/msilib.po b/library/msilib.po index 3b8213411..3278c0703 100644 --- a/library/msilib.po +++ b/library/msilib.po @@ -33,9 +33,9 @@ msgstr "" #: library/msilib.rst:22 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`` " +"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 "" @@ -141,8 +141,8 @@ msgstr "" #: library/msilib.rst:104 msgid "" -"Represents entries in the Binary table; inserting such an object using :func:" -"`add_data` reads the file named *filename* into the table." +"Represents entries in the Binary table; inserting such an object " +"using :func:`add_data` reads the file named *filename* into the table." msgstr "" #: library/msilib.rst:110 @@ -188,14 +188,15 @@ msgstr "" #: library/msilib.rst:149 msgid "" -"Commit the changes pending in the current transaction, by calling :c:func:" -"`MSIDatabaseCommit`." +"Commit the changes pending in the current transaction, by " +"calling :c:func:`MSIDatabaseCommit`." msgstr "" #: library/msilib.rst:155 msgid "" -"Return a new summary information object, by calling :c:func:" -"`MsiGetSummaryInformation`. *count* is the maximum number of updated values." +"Return a new summary information object, by " +"calling :c:func:`MsiGetSummaryInformation`. *count* is the maximum number " +"of updated values." msgstr "" #: library/msilib.rst:161 @@ -225,9 +226,9 @@ msgstr "" #: library/msilib.rst:187 msgid "" -"Return a record describing the columns of the view, through calling :c:func:" -"`MsiViewGetColumnInfo`. *kind* can be either ``MSICOLINFO_NAMES`` or " -"``MSICOLINFO_TYPES``." +"Return a record describing the columns of the view, through " +"calling :c:func:`MsiViewGetColumnInfo`. *kind* can be either " +"``MSICOLINFO_NAMES`` or ``MSICOLINFO_TYPES``." msgstr "" #: library/msilib.rst:194 @@ -257,11 +258,11 @@ msgstr "" msgid "" "`MsiViewExecute `_ `MSIViewGetColumnInfo `_ `MsiViewFetch `_ `MsiViewModify " -"`_ " -"`MsiViewClose `_" +"library/windows/desktop/aa370516.aspx>`_ `MsiViewFetch `_ " +"`MsiViewModify `_ `MsiViewClose `_" msgstr "" #: library/msilib.rst:225 @@ -270,19 +271,20 @@ msgstr "" #: library/msilib.rst:230 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``." +"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 "" #: library/msilib.rst:241 msgid "" -"Return the number of summary properties, through :c:func:" -"`MsiSummaryInfoGetPropertyCount`." +"Return the number of summary properties, " +"through :c:func:`MsiSummaryInfoGetPropertyCount`." msgstr "" #: library/msilib.rst:247 @@ -294,15 +296,15 @@ msgstr "" #: library/msilib.rst:254 msgid "" -"Write the modified properties to the summary information stream, using :c:" -"func:`MsiSummaryInfoPersist`." +"Write the modified properties to the summary information stream, " +"using :c:func:`MsiSummaryInfoPersist`." msgstr "" #: library/msilib.rst:260 msgid "" "`MsiSummaryInfoGetProperty `_ `MsiSummaryInfoGetPropertyCount `_ " +"desktop/aa370409.aspx>`_ `MsiSummaryInfoGetPropertyCount `_ " "`MsiSummaryInfoSetProperty `_ `MsiSummaryInfoPersist `_" @@ -314,8 +316,8 @@ msgstr "" #: library/msilib.rst:273 msgid "" -"Return the number of fields of the record, through :c:func:" -"`MsiRecordGetFieldCount`." +"Return the number of fields of the record, " +"through :c:func:`MsiRecordGetFieldCount`." msgstr "" #: library/msilib.rst:279 @@ -338,8 +340,9 @@ msgstr "" #: library/msilib.rst:297 msgid "" -"Set *field* to the contents of the file named *value*, through :c:func:" -"`MsiRecordSetStream`. *field* must be an integer; *value* a string." +"Set *field* to the contents of the file named *value*, " +"through :c:func:`MsiRecordSetStream`. *field* must be an integer; *value* a " +"string." msgstr "" #: library/msilib.rst:303 @@ -457,9 +460,10 @@ msgstr "" msgid "" "`Directory Table `_ `File Table `_ `Component Table `_ `FeatureComponents Table " -"`_" +"windows/desktop/aa368596.aspx>`_ `Component Table `_ " +"`FeatureComponents Table `_" msgstr "" #: library/msilib.rst:418 @@ -468,10 +472,10 @@ msgstr "" #: library/msilib.rst:423 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`." +"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 "" #: library/msilib.rst:431 @@ -580,8 +584,8 @@ msgid "" "`_ " "`ControlEvent Table `_ `EventMapping Table `_ `RadioButton Table `_" +"us/library/windows/desktop/aa368559.aspx>`_ `RadioButton Table `_" msgstr "" #: library/msilib.rst:542 diff --git a/library/msvcrt.po b/library/msvcrt.po index 76f3b7453..3658fc697 100644 --- a/library/msvcrt.po +++ b/library/msvcrt.po @@ -89,16 +89,17 @@ msgstr "" #: library/msvcrt.rst:70 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`." +"text mode, *flags* should be :const:`os.O_TEXT`; for binary, it should " +"be :const:`os.O_BINARY`." msgstr "" #: library/msvcrt.rst:77 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." +"*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 "" #: library/msvcrt.rst:82 diff --git a/library/multiprocessing.po b/library/multiprocessing.po index f8e0da255..e05a3cf2c 100644 --- a/library/multiprocessing.po +++ b/library/multiprocessing.po @@ -53,14 +53,14 @@ msgstr "" #: library/multiprocessing.rst:25 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 " +"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`, ::" +"module. This basic example of data parallelism " +"using :class:`~multiprocessing.pool.Pool`, ::" msgstr "" #: library/multiprocessing.rst:34 @@ -87,10 +87,10 @@ msgstr "" msgid "" ":class:`concurrent.futures.ProcessPoolExecutor` offers a higher level " "interface to push tasks to a background process without blocking execution " -"of the calling process. Compared to using the :class:`~multiprocessing.pool." -"Pool` interface directly, the :mod:`concurrent.futures` API more readily " -"allows the submission of work to the underlying process pool to be separated " -"from waiting for the results." +"of the calling process. Compared to using " +"the :class:`~multiprocessing.pool.Pool` interface directly, " +"the :mod:`concurrent.futures` API more readily allows the submission of work " +"to the underlying process pool to be separated from waiting for the results." msgstr "" #: library/multiprocessing.rst:59 @@ -99,10 +99,10 @@ msgstr "" #: library/multiprocessing.rst:61 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 ::" +"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 "" #: library/multiprocessing.rst:66 @@ -206,10 +206,10 @@ msgstr "" #: library/multiprocessing.rst:134 msgid "" -"If Python is able to detect that your process has multiple threads, the :" -"func:`os.fork` function that this start method calls internally will raise " -"a :exc:`DeprecationWarning`. Use a different start method. See the :func:`os." -"fork` documentation for further explanation." +"If Python is able to detect that your process has multiple threads, " +"the :func:`os.fork` function that this start method calls internally will " +"raise a :exc:`DeprecationWarning`. Use a different start method. See " +"the :func:`os.fork` documentation for further explanation." msgstr "" #: library/multiprocessing.rst:140 @@ -250,15 +250,15 @@ msgstr "" msgid "" "On POSIX using the *spawn* or *forkserver* start methods will also start a " "*resource tracker* process which tracks the unlinked named system resources " -"(such as named semaphores or :class:`~multiprocessing.shared_memory." -"SharedMemory` objects) created by processes of the program. When all " -"processes have exited the resource tracker unlinks any remaining tracked " -"object. Usually there should be none, but if a process was killed by a " -"signal there may be some \"leaked\" resources. (Neither leaked semaphores " -"nor shared memory segments will be automatically unlinked until the next " -"reboot. This is problematic for both objects because the system allows only " -"a limited number of named semaphores, and shared memory segments occupy some " -"space in the main memory.)" +"(such as named semaphores " +"or :class:`~multiprocessing.shared_memory.SharedMemory` objects) created by " +"processes of the program. When all processes have exited the resource " +"tracker unlinks any remaining tracked object. Usually there should be none, " +"but if a process was killed by a signal there may be some \"leaked\" " +"resources. (Neither leaked semaphores nor shared memory segments will be " +"automatically unlinked until the next reboot. This is problematic for both " +"objects because the system allows only a limited number of named semaphores, " +"and shared memory segments occupy some space in the main memory.)" msgstr "" #: library/multiprocessing.rst:178 @@ -321,8 +321,9 @@ msgstr "" #: library/multiprocessing.rst:221 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." +"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 "" #: library/multiprocessing.rst:227 @@ -370,8 +371,8 @@ msgstr "" #: library/multiprocessing.rst:256 msgid "" -"Queues are thread and process safe. Any object put into a :mod:" -"`~multiprocessing` queue will be serialized." +"Queues are thread and process safe. Any object put into " +"a :mod:`~multiprocessing` queue will be serialized." msgstr "" #: library/multiprocessing.rst:259 @@ -403,17 +404,18 @@ msgstr "" #: library/multiprocessing.rst:277 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." +"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 "" #: library/multiprocessing.rst:285 msgid "" -"The :meth:`~Connection.send` method serializes the the object and :meth:" -"`~Connection.recv` re-creates the object." +"The :meth:`~Connection.send` method serializes the the object " +"and :meth:`~Connection.recv` re-creates the object." msgstr "" #: library/multiprocessing.rst:289 @@ -464,8 +466,8 @@ msgstr "" #: library/multiprocessing.rst:321 msgid "" -"However, if you really do need to use some shared data then :mod:" -"`multiprocessing` provides a couple of ways of doing so." +"However, if you really do need to use some shared data " +"then :mod:`multiprocessing` provides a couple of ways of doing so." msgstr "" #: library/multiprocessing.rst:324 @@ -474,8 +476,8 @@ msgstr "" #: library/multiprocessing.rst:326 msgid "" -"Data can be stored in a shared memory map using :class:`Value` or :class:" -"`Array`. For example, the following code ::" +"Data can be stored in a shared memory map using :class:`Value` " +"or :class:`Array`. For example, the following code ::" msgstr "" #: library/multiprocessing.rst:329 @@ -519,9 +521,9 @@ msgstr "" #: library/multiprocessing.rst:357 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." +"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 "" #: library/multiprocessing.rst:361 @@ -537,11 +539,9 @@ msgstr "" #: library/multiprocessing.rst:367 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, ::" +"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 "" #: library/multiprocessing.rst:373 @@ -636,8 +636,8 @@ msgid "" " try:\n" " print(res.get(timeout=1))\n" " except TimeoutError:\n" -" print(\"We lacked patience and got a multiprocessing." -"TimeoutError\")\n" +" print(\"We lacked patience and got a " +"multiprocessing.TimeoutError\")\n" "\n" " print(\"For the moment, the pool remains available for more work\")\n" "\n" @@ -696,8 +696,8 @@ msgstr "" #: library/multiprocessing.rst:491 msgid "" -"The :mod:`multiprocessing` package mostly replicates the API of the :mod:" -"`threading` module." +"The :mod:`multiprocessing` package mostly replicates the API of " +"the :mod:`threading` module." msgstr "" #: library/multiprocessing.rst:496 @@ -706,23 +706,23 @@ msgstr "" #: library/multiprocessing.rst:501 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`." +"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 "" #: library/multiprocessing.rst:505 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." +"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 "" #: library/multiprocessing.rst:516 @@ -815,9 +815,9 @@ msgstr "" #: library/multiprocessing.rst:576 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." +"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 "" #: library/multiprocessing.rst:583 @@ -832,8 +832,8 @@ msgstr "" #: library/multiprocessing.rst:590 msgid "" -"The process's daemon flag, a Boolean value. This must be set before :meth:" -"`start` is called." +"The process's daemon flag, a Boolean value. This must be set " +"before :meth:`start` is called." msgstr "" #: library/multiprocessing.rst:593 @@ -915,9 +915,9 @@ msgstr "" #: library/multiprocessing.rst:643 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." +"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 "" #: library/multiprocessing.rst:647 @@ -929,9 +929,10 @@ msgstr "" #: library/multiprocessing.rst:655 msgid "" -"Terminate the process. On POSIX this is done using the :py:const:`~signal." -"SIGTERM` signal; on Windows :c:func:`!TerminateProcess` is used. Note that " -"exit handlers and finally clauses, etc., will not be executed." +"Terminate the process. On POSIX this is done using " +"the :py:const:`~signal.SIGTERM` signal; on Windows :c:func:`!" +"TerminateProcess` is used. Note that exit handlers and finally clauses, " +"etc., will not be executed." msgstr "" #: library/multiprocessing.rst:659 @@ -963,9 +964,10 @@ msgstr "" #: library/multiprocessing.rst:686 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." +"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 "" #: library/multiprocessing.rst:690 @@ -1036,25 +1038,25 @@ 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." +"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 "" #: library/multiprocessing.rst:746 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." +"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 "" #: library/multiprocessing.rst:751 msgid "" -"One difference from other Python queue implementations, is that :mod:" -"`multiprocessing` queues serializes all objects that are put into them " -"using :mod:`pickle`. The object return by the get method is a re-created " -"object that does not share memory with the original object." +"One difference from other Python queue implementations, is " +"that :mod:`multiprocessing` queues serializes all objects that are put into " +"them using :mod:`pickle`. The object return by the get method is a re-" +"created object that does not share memory with the original object." msgstr "" #: library/multiprocessing.rst:756 @@ -1065,9 +1067,10 @@ msgstr "" #: library/multiprocessing.rst:761 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`." +":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 "" #: library/multiprocessing.rst:768 @@ -1105,9 +1108,9 @@ msgstr "" #: library/multiprocessing.rst:794 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." +"not used :meth:`JoinableQueue.cancel_join_thread " +"`), then that process will not " +"terminate until all buffered items have been flushed to the pipe." msgstr "" #: library/multiprocessing.rst:799 @@ -1121,20 +1124,21 @@ msgstr "" #: library/multiprocessing.rst:804 msgid "" -"Note that a queue created using a manager does not have this issue. See :" -"ref:`multiprocessing-programming`." +"Note that a queue created using a manager does not have this issue. " +"See :ref:`multiprocessing-programming`." msgstr "" #: library/multiprocessing.rst:807 msgid "" -"For an example of the usage of queues for interprocess communication see :" -"ref:`multiprocessing-examples`." +"For an example of the usage of queues for interprocess communication " +"see :ref:`multiprocessing-examples`." msgstr "" #: library/multiprocessing.rst:813 msgid "" -"Returns a pair ``(conn1, conn2)`` of :class:`~multiprocessing.connection." -"Connection` objects representing the ends of a pipe." +"Returns a pair ``(conn1, conn2)`` " +"of :class:`~multiprocessing.connection.Connection` objects representing the " +"ends of a pipe." msgstr "" #: library/multiprocessing.rst:817 @@ -1212,8 +1216,8 @@ msgstr "" #: library/multiprocessing.rst:868 msgid "" -"If the queue is closed, :exc:`ValueError` is raised instead of :exc:" -"`AssertionError`." +"If the queue is closed, :exc:`ValueError` is raised instead " +"of :exc:`AssertionError`." msgstr "" #: library/multiprocessing.rst:874 @@ -1227,14 +1231,14 @@ msgid "" "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)." +"return an item if one is immediately available, else raise " +"the :exc:`queue.Empty` exception (*timeout* is ignored in that case)." msgstr "" #: library/multiprocessing.rst:886 msgid "" -"If the queue is closed, :exc:`ValueError` is raised instead of :exc:" -"`OSError`." +"If the queue is closed, :exc:`ValueError` is raised instead " +"of :exc:`OSError`." msgstr "" #: library/multiprocessing.rst:892 @@ -1243,8 +1247,9 @@ msgstr "" #: library/multiprocessing.rst:894 msgid "" -":class:`multiprocessing.Queue` has a few additional methods not found in :" -"class:`queue.Queue`. These methods are usually unnecessary for most code:" +":class:`multiprocessing.Queue` has a few additional methods not found " +"in :class:`queue.Queue`. These methods are usually unnecessary for most " +"code:" msgstr "" #: library/multiprocessing.rst:900 @@ -1265,8 +1270,8 @@ msgstr "" #: library/multiprocessing.rst:911 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." +"attempt to join the queue's background thread. The process can " +"call :meth:`cancel_join_thread` to make :meth:`join_thread` do nothing." msgstr "" #: library/multiprocessing.rst:917 @@ -1306,8 +1311,9 @@ msgstr "" #: library/multiprocessing.rst:945 msgid "" -"A queue must not be used anymore after it is closed. For example, :meth:" -"`get`, :meth:`put` and :meth:`empty` methods must no longer be called." +"A queue must not be used anymore after it is closed. For " +"example, :meth:`get`, :meth:`put` and :meth:`empty` methods must no longer " +"be called." msgstr "" #: library/multiprocessing.rst:953 @@ -1387,8 +1393,8 @@ msgstr "" #: library/multiprocessing.rst:1011 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))``" +"use. The number of usable CPUs can be obtained with " +"``len(os.sched_getaffinity(0))``" msgstr "" #: library/multiprocessing.rst:1015 @@ -1460,22 +1466,22 @@ msgstr "" 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'``. Not all platforms support all methods. See :ref:" -"`multiprocessing-start-methods`." +"``'forkserver'``. Not all platforms support all methods. " +"See :ref:`multiprocessing-start-methods`." msgstr "" #: library/multiprocessing.rst:1072 msgid "" -"Return a context object which has the same attributes as the :mod:" -"`multiprocessing` module." +"Return a context object which has the same attributes as " +"the :mod:`multiprocessing` module." msgstr "" #: library/multiprocessing.rst:1075 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. See :" -"ref:`multiprocessing-start-methods`." +"*method* should be ``'fork'``, ``'spawn'``, " +"``'forkserver'``. :exc:`ValueError` is raised if the specified start method " +"is not available. See :ref:`multiprocessing-start-methods`." msgstr "" #: library/multiprocessing.rst:1084 @@ -1542,18 +1548,18 @@ msgstr "" #: library/multiprocessing.rst:1129 msgid "" -"Only meaningful when using the ``'forkserver'`` start method. See :ref:" -"`multiprocessing-start-methods`." +"Only meaningful when using the ``'forkserver'`` start method. " +"See :ref:`multiprocessing-start-methods`." msgstr "" #: library/multiprocessing.rst:1136 msgid "" "Set the method which should be used to start child processes. The *method* " -"argument can be ``'fork'``, ``'spawn'`` or ``'forkserver'``. Raises :exc:" -"`RuntimeError` if the start method has already been set and *force* is not " -"``True``. If *method* is ``None`` and *force* is ``True`` then the start " -"method is set to ``None``. If *method* is ``None`` and *force* is ``False`` " -"then the context is set to the default context." +"argument can be ``'fork'``, ``'spawn'`` or ``'forkserver'``. " +"Raises :exc:`RuntimeError` if the start method has already been set and " +"*force* is not ``True``. If *method* is ``None`` and *force* is ``True`` " +"then the start method is set to ``None``. If *method* is ``None`` and " +"*force* is ``False`` then the context is set to the default context." msgstr "" #: library/multiprocessing.rst:1143 @@ -1568,10 +1574,9 @@ msgstr "" #: library/multiprocessing.rst:1153 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`." +":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 "" #: library/multiprocessing.rst:1160 @@ -1586,8 +1591,8 @@ msgstr "" #: library/multiprocessing.rst:1167 msgid "" -"Connection objects are usually created using :func:`Pipe ` -- see also :ref:`multiprocessing-listeners-clients`." +"Connection objects are usually created using :func:`Pipe " +"` -- see also :ref:`multiprocessing-listeners-clients`." msgstr "" #: library/multiprocessing.rst:1175 @@ -1604,9 +1609,10 @@ msgstr "" #: library/multiprocessing.rst:1183 msgid "" -"Return an object sent from the other end of the connection using :meth:" -"`send`. Blocks until there is something to receive. Raises :exc:`EOFError` " -"if there is nothing left to receive and the other end was closed." +"Return an object sent from the other end of the connection " +"using :meth:`send`. Blocks until there is something to receive. " +"Raises :exc:`EOFError` if there is nothing left to receive and the other end " +"was closed." msgstr "" #: library/multiprocessing.rst:1190 @@ -1634,8 +1640,8 @@ msgstr "" #: library/multiprocessing.rst:1206 msgid "" -"Note that multiple connection objects may be polled at once by using :func:" -"`multiprocessing.connection.wait`." +"Note that multiple connection objects may be polled at once by " +"using :func:`multiprocessing.connection.wait`." msgstr "" #: library/multiprocessing.rst:1211 @@ -1646,28 +1652,28 @@ msgstr "" 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 MiB+, though it depends on the OS) may raise a :" -"exc:`ValueError` exception" +"buffers (approximately 32 MiB+, though it depends on the OS) may raise " +"a :exc:`ValueError` exception" msgstr "" #: library/multiprocessing.rst:1220 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." +"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 "" #: library/multiprocessing.rst:1225 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." +"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 "" #: library/multiprocessing.rst:1229 msgid "" -"This function used to raise :exc:`IOError`, which is now an alias of :exc:" -"`OSError`." +"This function used to raise :exc:`IOError`, which is now an alias " +"of :exc:`OSError`." msgstr "" #: library/multiprocessing.rst:1236 @@ -1700,9 +1706,10 @@ msgstr "" #: library/multiprocessing.rst:1255 msgid "" -"Connection objects also now support the context management protocol -- see :" -"ref:`typecontextmanager`. :meth:`~contextmanager.__enter__` returns the " -"connection object, and :meth:`~contextmanager.__exit__` calls :meth:`close`." +"Connection objects also now support the context management protocol -- " +"see :ref:`typecontextmanager`. :meth:`~contextmanager.__enter__` returns " +"the connection object, and :meth:`~contextmanager.__exit__` " +"calls :meth:`close`." msgstr "" #: library/multiprocessing.rst:1259 @@ -1740,8 +1747,8 @@ msgstr "" 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`." +"methods after performing some sort of authentication. " +"See :ref:`multiprocessing-auth-keys`." msgstr "" #: library/multiprocessing.rst:1295 @@ -1758,8 +1765,8 @@ msgstr "" #: library/multiprocessing.rst:1305 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." +"program as they are in a multithreaded program. See the documentation " +"for :mod:`threading` module." msgstr "" #: library/multiprocessing.rst:1309 @@ -1774,8 +1781,8 @@ msgstr "" #: library/multiprocessing.rst:1320 msgid "" -"A bounded semaphore object: a close analog of :class:`threading." -"BoundedSemaphore`." +"A bounded semaphore object: a close analog " +"of :class:`threading.BoundedSemaphore`." msgstr "" #: library/multiprocessing.rst:1323 library/multiprocessing.rst:1461 @@ -1813,10 +1820,10 @@ 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." +"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 "" #: library/multiprocessing.rst:1355 @@ -1925,9 +1932,9 @@ msgstr "" #: library/multiprocessing.rst:1435 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`." +"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 "" #: library/multiprocessing.rst:1442 @@ -1942,8 +1949,8 @@ msgstr "" #: library/multiprocessing.rst:1450 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 " +"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`." @@ -1962,9 +1969,9 @@ msgstr "" #: library/multiprocessing.rst:1471 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 " +"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 "" @@ -1988,8 +1995,9 @@ msgstr "" #: library/multiprocessing.rst:1490 library/multiprocessing.rst:1577 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." +"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 "" #: library/multiprocessing.rst:1494 @@ -2049,11 +2057,11 @@ msgstr "" #: library/multiprocessing.rst:1527 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\"." +"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 "" #: library/multiprocessing.rst:1534 @@ -2102,9 +2110,9 @@ msgstr "" #: library/multiprocessing.rst:1569 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." +"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 "" #: library/multiprocessing.rst:1575 @@ -2113,9 +2121,9 @@ msgstr "" #: library/multiprocessing.rst:1581 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." +"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 "" #: library/multiprocessing.rst:1585 @@ -2135,11 +2143,11 @@ msgstr "" #: library/multiprocessing.rst:1595 library/multiprocessing.rst:1611 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\"." +"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 "" #: library/multiprocessing.rst:1607 @@ -2158,15 +2166,15 @@ msgstr "" #: library/multiprocessing.rst:1627 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." +"to synchronize access. If *lock* is ``None`` (the default) then " +"a :class:`multiprocessing.RLock` object is created automatically." msgstr "" #: library/multiprocessing.rst:1631 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." +"object it wraps: :meth:`get_obj` returns the wrapped object " +"and :meth:`get_lock` returns the lock object used for synchronization." msgstr "" #: library/multiprocessing.rst:1635 @@ -2319,8 +2327,8 @@ msgstr "" #: library/multiprocessing.rst:1726 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:" +"their parent process exits. The manager classes are defined in " +"the :mod:`multiprocessing.managers` module:" msgstr "" #: library/multiprocessing.rst:1732 @@ -2329,9 +2337,9 @@ msgstr "" #: library/multiprocessing.rst:1734 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." +"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 "" #: library/multiprocessing.rst:1737 @@ -2356,8 +2364,8 @@ msgstr "" #: library/multiprocessing.rst:1748 msgid "" -"*ctx* is a context object, or ``None`` (use the current context). See the :" -"func:`get_context` function." +"*ctx* is a context object, or ``None`` (use the current context). See " +"the :func:`get_context` function." msgstr "" #: library/multiprocessing.rst:1751 @@ -2381,8 +2389,8 @@ msgstr "" #: library/multiprocessing.rst:1766 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::" +"the control of the Manager. The :class:`Server` object supports " +"the :meth:`serve_forever` method::" msgstr "" #: library/multiprocessing.rst:1770 @@ -2410,8 +2418,8 @@ msgstr "" #: library/multiprocessing.rst:1787 msgid "" -"Stop the process used by the manager. This is only available if :meth:" -"`start` has been used to start the server process." +"Stop the process used by the manager. This is only available " +"if :meth:`start` has been used to start the server process." msgstr "" #: library/multiprocessing.rst:1790 @@ -2448,22 +2456,23 @@ msgstr "" #: library/multiprocessing.rst:1810 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 ``'_'``.)" +"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 "" #: library/multiprocessing.rst:1819 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." +"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 "" #: library/multiprocessing.rst:1826 @@ -2483,9 +2492,9 @@ msgstr "" #: library/multiprocessing.rst:1836 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 " +"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 "" @@ -2498,8 +2507,8 @@ msgstr "" #: library/multiprocessing.rst:1847 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`." +"of processes. Objects of this type are returned " +"by :func:`multiprocessing.Manager`." msgstr "" #: library/multiprocessing.rst:1851 @@ -2528,8 +2537,8 @@ msgstr "" #: library/multiprocessing.rst:1872 msgid "" -"If *lock* is supplied then it should be a proxy for a :class:`threading." -"Lock` or :class:`threading.RLock` object." +"If *lock* is supplied then it should be a proxy for " +"a :class:`threading.Lock` or :class:`threading.RLock` object." msgstr "" #: library/multiprocessing.rst:1880 @@ -2781,9 +2790,9 @@ msgstr "" #: library/multiprocessing.rst:2070 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`:" +"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 "" #: library/multiprocessing.rst:2075 @@ -2843,9 +2852,9 @@ msgstr "" #: library/multiprocessing.rst:2118 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." +"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 "" #: library/multiprocessing.rst:2124 @@ -2903,10 +2912,10 @@ msgstr "" #: library/multiprocessing.rst:2156 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`." +"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 "" #: library/multiprocessing.rst:2161 @@ -3004,9 +3013,9 @@ msgstr "" #: library/multiprocessing.rst:2229 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." +"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 "" #: library/multiprocessing.rst:2235 @@ -3059,8 +3068,8 @@ msgstr "" #: library/multiprocessing.rst:2273 msgid "" -"A variant of the :meth:`apply` method which returns a :class:" -"`~multiprocessing.pool.AsyncResult` object." +"A variant of the :meth:`apply` method which returns " +"a :class:`~multiprocessing.pool.AsyncResult` object." msgstr "" #: library/multiprocessing.rst:2276 library/multiprocessing.rst:2307 @@ -3107,8 +3116,8 @@ msgstr "" #: library/multiprocessing.rst:2304 msgid "" -"A variant of the :meth:`.map` method which returns a :class:" -"`~multiprocessing.pool.AsyncResult` object." +"A variant of the :meth:`.map` method which returns " +"a :class:`~multiprocessing.pool.AsyncResult` object." msgstr "" #: library/multiprocessing.rst:2321 @@ -3171,29 +3180,30 @@ msgstr "" #: library/multiprocessing.rst:2371 msgid "" -"Wait for the worker processes to exit. One must call :meth:`close` or :meth:" -"`terminate` before using :meth:`join`." +"Wait for the worker processes to exit. One must call :meth:`close` " +"or :meth:`terminate` before using :meth:`join`." msgstr "" #: library/multiprocessing.rst:2374 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`." +"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 "" #: library/multiprocessing.rst:2382 msgid "" -"The class of the result returned by :meth:`Pool.apply_async` and :meth:`Pool." -"map_async`." +"The class of the result returned by :meth:`Pool.apply_async` " +"and :meth:`Pool.map_async`." msgstr "" #: library/multiprocessing.rst:2387 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`." +"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 "" #: library/multiprocessing.rst:2394 @@ -3206,14 +3216,14 @@ msgstr "" #: library/multiprocessing.rst:2402 msgid "" -"Return whether the call completed without raising an exception. Will raise :" -"exc:`ValueError` if the result is not ready." +"Return whether the call completed without raising an exception. Will " +"raise :exc:`ValueError` if the result is not ready." msgstr "" #: library/multiprocessing.rst:2405 msgid "" -"If the result is not ready, :exc:`ValueError` is raised instead of :exc:" -"`AssertionError`." +"If the result is not ready, :exc:`ValueError` is raised instead " +"of :exc:`AssertionError`." msgstr "" #: library/multiprocessing.rst:2409 @@ -3244,8 +3254,8 @@ msgid "" "computer is *very* slow\n" "\n" " result = pool.apply_async(time.sleep, (10,))\n" -" print(result.get(timeout=1)) # raises multiprocessing." -"TimeoutError" +" print(result.get(timeout=1)) # raises " +"multiprocessing.TimeoutError" msgstr "" #: library/multiprocessing.rst:2436 @@ -3254,8 +3264,8 @@ msgstr "" #: library/multiprocessing.rst:2441 msgid "" -"Usually message passing between processes is done using queues or by using :" -"class:`~Connection` objects returned by :func:`~multiprocessing.Pipe`." +"Usually message passing between processes is done using queues or by " +"using :class:`~Connection` objects returned by :func:`~multiprocessing.Pipe`." msgstr "" #: library/multiprocessing.rst:2445 @@ -3288,8 +3298,8 @@ msgstr "" #: library/multiprocessing.rst:2466 msgid "" -"If a welcome message is not received, then :exc:`~multiprocessing." -"AuthenticationError` is raised." +"If a welcome message is not received, " +"then :exc:`~multiprocessing.AuthenticationError` is raised." msgstr "" #: library/multiprocessing.rst:2471 @@ -3309,9 +3319,9 @@ msgstr "" msgid "" "If *authkey* is given and not ``None``, it should be a byte string and will " "be used as the secret key for an HMAC-based authentication challenge. No " -"authentication is done if *authkey* is ``None``. :exc:`~multiprocessing." -"AuthenticationError` is raised if authentication fails. See :ref:" -"`multiprocessing-auth-keys`." +"authentication is done if *authkey* is " +"``None``. :exc:`~multiprocessing.AuthenticationError` is raised if " +"authentication fails. See :ref:`multiprocessing-auth-keys`." msgstr "" #: library/multiprocessing.rst:2486 @@ -3384,9 +3394,10 @@ msgstr "" #: library/multiprocessing.rst:2543 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`." +"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 "" #: library/multiprocessing.rst:2550 @@ -3413,8 +3424,8 @@ msgstr "" #: library/multiprocessing.rst:2561 msgid "" -"the :attr:`~multiprocessing.Process.sentinel` attribute of a :class:" -"`~multiprocessing.Process` object." +"the :attr:`~multiprocessing.Process.sentinel` attribute of " +"a :class:`~multiprocessing.Process` object." msgstr "" #: library/multiprocessing.rst:2564 @@ -3425,18 +3436,19 @@ msgstr "" #: library/multiprocessing.rst:2567 msgid "" -"**POSIX**: ``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." +"**POSIX**: ``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 "" #: library/multiprocessing.rst:2573 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:`~io.IOBase.fileno` method which returns a socket handle or pipe " +"Win32 function ``WaitForMultipleObjects()``) or it can be an object with " +"a :meth:`~io.IOBase.fileno` method which returns a socket handle or pipe " "handle. (Note that pipe handles and socket handles are **not** waitable " "handles.)" msgstr "" @@ -3588,18 +3600,18 @@ msgstr "" #: library/multiprocessing.rst:2694 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." +"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 "" #: library/multiprocessing.rst:2702 msgid "" -"Suitable authentication keys can also be generated by using :func:`os." -"urandom`." +"Suitable authentication keys can also be generated by " +"using :func:`os.urandom`." msgstr "" #: library/multiprocessing.rst:2706 @@ -3608,10 +3620,10 @@ msgstr "" #: library/multiprocessing.rst:2708 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." +"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 "" #: library/multiprocessing.rst:2715 @@ -3679,10 +3691,10 @@ msgstr "" #: library/multiprocessing.rst:2764 msgid "" -"In particular, the ``Pool`` function provided by :mod:`multiprocessing." -"dummy` returns an instance of :class:`ThreadPool`, which is a subclass of :" -"class:`Pool` that supports all the same method calls but uses a pool of " -"worker threads rather than worker processes." +"In particular, the ``Pool`` function provided " +"by :mod:`multiprocessing.dummy` returns an instance of :class:`ThreadPool`, " +"which is a subclass of :class:`Pool` that supports all the same method calls " +"but uses a pool of worker threads rather than worker processes." msgstr "" #: library/multiprocessing.rst:2772 @@ -3691,8 +3703,8 @@ msgid "" "can be submitted. :class:`ThreadPool` instances are fully interface " "compatible with :class:`Pool` instances, and their resources must also be " "properly managed, either by using the pool as a context manager or by " -"calling :meth:`~multiprocessing.pool.Pool.close` and :meth:`~multiprocessing." -"pool.Pool.terminate` manually." +"calling :meth:`~multiprocessing.pool.Pool.close` " +"and :meth:`~multiprocessing.pool.Pool.terminate` manually." msgstr "" #: library/multiprocessing.rst:2779 @@ -3709,20 +3721,20 @@ msgstr "" #: library/multiprocessing.rst:2789 msgid "" "A :class:`ThreadPool` shares the same interface as :class:`Pool`, which is " -"designed around a pool of processes and predates the introduction of the :" -"class:`concurrent.futures` module. As such, it inherits some operations " -"that don't make sense for a pool backed by threads, and it has its own type " -"for representing the status of asynchronous jobs, :class:`AsyncResult`, that " -"is not understood by any other libraries." +"designed around a pool of processes and predates the introduction of " +"the :class:`concurrent.futures` module. As such, it inherits some " +"operations that don't make sense for a pool backed by threads, and it has " +"its own type for representing the status of asynchronous " +"jobs, :class:`AsyncResult`, that is not understood by any other libraries." msgstr "" #: library/multiprocessing.rst:2796 msgid "" -"Users should generally prefer to use :class:`concurrent.futures." -"ThreadPoolExecutor`, which has a simpler interface that was designed around " -"threads from the start, and which returns :class:`concurrent.futures.Future` " -"instances that are compatible with many other libraries, including :mod:" -"`asyncio`." +"Users should generally prefer to " +"use :class:`concurrent.futures.ThreadPoolExecutor`, which has a simpler " +"interface that was designed around threads from the start, and which " +"returns :class:`concurrent.futures.Future` instances that are compatible " +"with many other libraries, including :mod:`asyncio`." msgstr "" #: library/multiprocessing.rst:2806 @@ -3793,9 +3805,9 @@ msgid "" "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." +"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 "" #: library/multiprocessing.rst:2847 @@ -3804,12 +3816,12 @@ msgstr "" #: library/multiprocessing.rst:2849 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." +"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 "" #: library/multiprocessing.rst:2857 @@ -3826,9 +3838,9 @@ msgstr "" #: library/multiprocessing.rst:2865 msgid "" -"Therefore it is probably best to only consider using :meth:`Process." -"terminate ` on processes which never use " -"any shared resources." +"Therefore it is probably best to only consider " +"using :meth:`Process.terminate ` on " +"processes which never use any shared resources." msgstr "" #: library/multiprocessing.rst:2869 @@ -3839,9 +3851,10 @@ msgstr "" 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.)" +"the underlying pipe. (The child process can call " +"the :meth:`Queue.cancel_join_thread " +"` method of the queue to avoid " +"this behaviour.)" msgstr "" #: library/multiprocessing.rst:2877 @@ -3874,8 +3887,8 @@ msgstr "" #: library/multiprocessing.rst:2897 msgid "" -"A fix here would be to swap the last two lines (or simply remove the ``p." -"join()`` line)." +"A fix here would be to swap the last two lines (or simply remove the " +"``p.join()`` line)." msgstr "" #: library/multiprocessing.rst:2900 @@ -3962,9 +3975,10 @@ 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." +"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 "" #: library/multiprocessing.rst:2957 @@ -4008,8 +4022,8 @@ msgstr "" 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." +"instances will be picklable when the :meth:`Process.start " +"` method is called." msgstr "" #: library/multiprocessing.rst:2984 @@ -4020,8 +4034,8 @@ msgstr "" 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." +"in the parent process at the time that :meth:`Process.start " +"` was called." msgstr "" #: library/multiprocessing.rst:2991 @@ -4304,8 +4318,8 @@ msgid "" " try:\n" " print(list(pool.imap(f, list(range(10)))))\n" " except ZeroDivisionError:\n" -" print('\\tGot ZeroDivisionError as expected from list(pool." -"imap())')\n" +" print('\\tGot ZeroDivisionError as expected from " +"list(pool.imap())')\n" " else:\n" " raise AssertionError('expected ZeroDivisionError')\n" "\n" @@ -4323,8 +4337,8 @@ msgid "" " raise AssertionError('expected ZeroDivisionError')\n" "\n" " assert i == 9\n" -" print('\\tGot ZeroDivisionError as expected from IMapIterator." -"next()')\n" +" print('\\tGot ZeroDivisionError as expected from " +"IMapIterator.next()')\n" " print()\n" "\n" " #\n" diff --git a/library/multiprocessing.shared_memory.po b/library/multiprocessing.shared_memory.po index 42723cca7..364f9c1ec 100644 --- a/library/multiprocessing.shared_memory.po +++ b/library/multiprocessing.shared_memory.po @@ -32,9 +32,9 @@ msgid "" "management of shared memory to be accessed by one or more processes on a " "multicore or symmetric multiprocessor (SMP) machine. To assist with the " "life-cycle management of shared memory especially across distinct processes, " -"a :class:`~multiprocessing.managers.BaseManager` subclass, :class:" -"`~multiprocessing.managers.SharedMemoryManager`, is also provided in the :" -"mod:`multiprocessing.managers` module." +"a :class:`~multiprocessing.managers.BaseManager` " +"subclass, :class:`~multiprocessing.managers.SharedMemoryManager`, is also " +"provided in the :mod:`multiprocessing.managers` module." msgstr "" #: library/multiprocessing.shared_memory.rst:26 @@ -163,9 +163,9 @@ msgstr "" #: library/multiprocessing.shared_memory.rst:133 msgid "" -"The following example demonstrates a practical use of the :class:" -"`SharedMemory` class with `NumPy arrays `_, accessing " -"the same :class:`!numpy.ndarray` from two distinct Python shells:" +"The following example demonstrates a practical use of " +"the :class:`SharedMemory` class with `NumPy arrays `_, " +"accessing the same :class:`!numpy.ndarray` from two distinct Python shells:" msgstr "" #: library/multiprocessing.shared_memory.rst:137 @@ -226,13 +226,13 @@ msgid "" "SharedMemoryManager` instance causes a new process to be started. This new " "process's sole purpose is to manage the life cycle of all shared memory " "blocks created through it. To trigger the release of all shared memory " -"blocks managed by that process, call :meth:`~multiprocessing.managers." -"BaseManager.shutdown` on the instance. This triggers a :meth:" -"`~multiprocessing.shared_memory.SharedMemory.unlink` call on all of the :" -"class:`SharedMemory` objects managed by that process and then stops the " -"process itself. By creating :class:`!SharedMemory` instances through a :" -"class:`!SharedMemoryManager`, we avoid the need to manually track and " -"trigger the freeing of shared memory resources." +"blocks managed by that process, " +"call :meth:`~multiprocessing.managers.BaseManager.shutdown` on the instance. " +"This triggers a :meth:`~multiprocessing.shared_memory.SharedMemory.unlink` " +"call on all of the :class:`SharedMemory` objects managed by that process and " +"then stops the process itself. By creating :class:`!SharedMemory` instances " +"through a :class:`!SharedMemoryManager`, we avoid the need to manually track " +"and trigger the freeing of shared memory resources." msgstr "" #: library/multiprocessing.shared_memory.rst:202 @@ -264,8 +264,8 @@ msgstr "" #: library/multiprocessing.shared_memory.rst:222 msgid "" -"The following example demonstrates the basic mechanisms of a :class:" -"`~multiprocessing.managers.SharedMemoryManager`:" +"The following example demonstrates the basic mechanisms of " +"a :class:`~multiprocessing.managers.SharedMemoryManager`:" msgstr "" #: library/multiprocessing.shared_memory.rst:225 @@ -308,8 +308,8 @@ msgstr "" #: library/multiprocessing.shared_memory.rst:259 msgid "" -"When using a :class:`~multiprocessing.managers.SharedMemoryManager` in a :" -"keyword:`with` statement, the shared memory blocks created using that " +"When using a :class:`~multiprocessing.managers.SharedMemoryManager` in " +"a :keyword:`with` statement, the shared memory blocks created using that " "manager are all released when the :keyword:`!with` statement's code block " "finishes execution." msgstr "" @@ -363,17 +363,17 @@ msgstr "" #: library/multiprocessing.shared_memory.rst:288 msgid "" "*name* is the unique name for the requested shared memory, as described in " -"the definition for :class:`SharedMemory`. When attaching to an existing :" -"class:`!ShareableList`, specify its shared memory block's unique name while " -"leaving *sequence* set to ``None``." +"the definition for :class:`SharedMemory`. When attaching to an " +"existing :class:`!ShareableList`, specify its shared memory block's unique " +"name while leaving *sequence* set to ``None``." msgstr "" #: library/multiprocessing.shared_memory.rst:295 msgid "" "A known issue exists for :class:`bytes` and :class:`str` values. If they end " "with ``\\x00`` nul bytes or characters, those may be *silently stripped* " -"when fetching them by index from the :class:`!ShareableList`. This ``." -"rstrip(b'\\x00')`` behavior is considered a bug and may go away in the " +"when fetching them by index from the :class:`!ShareableList`. This " +"``.rstrip(b'\\x00')`` behavior is considered a bug and may go away in the " "future. See :gh:`106939`." msgstr "" diff --git a/library/netrc.po b/library/netrc.po index d8451b478..8494a6975 100644 --- a/library/netrc.po +++ b/library/netrc.po @@ -39,12 +39,12 @@ msgid "" "be read. Otherwise, a :exc:`FileNotFoundError` exception will be raised. " "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`." +"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 "" #: library/netrc.rst:34 @@ -53,8 +53,8 @@ msgstr "" #: library/netrc.rst:36 msgid "" -":func:`os.path.expanduser` is used to find the location of the :file:`." -"netrc` file when *file* is not passed as argument." +":func:`os.path.expanduser` is used to find the location of " +"the :file:`.netrc` file when *file* is not passed as argument." msgstr "" #: library/netrc.rst:40 diff --git a/library/nis.po b/library/nis.po index ec9146c79..3b353f9af 100644 --- a/library/nis.po +++ b/library/nis.po @@ -55,10 +55,10 @@ msgstr "" #: library/nis.rst:31 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)." +"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 "" #: library/nis.rst:48 diff --git a/library/nntplib.po b/library/nntplib.po index 6cf088419..c8fea7e0a 100644 --- a/library/nntplib.po +++ b/library/nntplib.po @@ -32,8 +32,8 @@ msgstr "" 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`." +"reader or poster, or automated news processors. It is compatible " +"with :rfc:`3977` as well as the older :rfc:`977` and :rfc:`2980`." msgstr "" #: includes/wasm-notavail.rst:3 @@ -56,8 +56,8 @@ msgstr "" #: library/nntplib.rst:46 msgid "" ">>> s = nntplib.NNTP('news.gmane.io')\n" -">>> resp, count, first, last, name = s.group('gmane.comp.python." -"committers')\n" +">>> resp, count, first, last, name = " +"s.group('gmane.comp.python.committers')\n" ">>> print('Group', name, 'has', count, 'articles, range', first, 'to', " "last)\n" "Group gmane.comp.python.committers has 1096 articles, range 1 to 1096\n" @@ -104,17 +104,17 @@ 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 " +"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.:" +"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 "" #: library/nntplib.rst:137 @@ -125,9 +125,9 @@ msgstr "" #: library/nntplib.rst:109 library/nntplib.rst:141 msgid "" -"All commands will raise an :ref:`auditing event ` ``nntplib." -"putline`` with arguments ``self`` and ``line``, where ``line`` is the bytes " -"about to be sent to the remote host." +"All commands will raise an :ref:`auditing event ` " +"``nntplib.putline`` with arguments ``self`` and ``line``, where ``line`` is " +"the bytes about to be sent to the remote host." msgstr "" #: library/nntplib.rst:113 @@ -140,19 +140,19 @@ msgstr "" #: library/nntplib.rst:152 msgid "" -"If the *timeout* parameter is set to be zero, it will raise a :class:" -"`ValueError` to prevent the creation of a non-blocking socket." +"If the *timeout* parameter is set to be zero, it will raise " +"a :class:`ValueError` to prevent the creation of a non-blocking socket." msgstr "" #: library/nntplib.rst:125 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`." +"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 "" #: library/nntplib.rst:133 @@ -163,8 +163,9 @@ msgstr "" #: library/nntplib.rst:147 msgid "" -"The class now supports hostname check with :attr:`ssl.SSLContext." -"check_hostname` and *Server Name Indication* (see :data:`ssl.HAS_SNI`)." +"The class now supports hostname check " +"with :attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* " +"(see :data:`ssl.HAS_SNI`)." msgstr "" #: library/nntplib.rst:158 @@ -219,14 +220,14 @@ msgstr "" #: library/nntplib.rst:206 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." +"server. In practice, this should be ``2`` for servers " +"advertising :rfc:`3977` compliance and ``1`` for others." msgstr "" #: library/nntplib.rst:214 msgid "" -"A string describing the software name and version of the NNTP server, or :" -"const:`None` if not advertised by the server." +"A string describing the software name and version of the NNTP server, " +"or :const:`None` if not advertised by the server." msgstr "" #: library/nntplib.rst:220 @@ -272,52 +273,55 @@ msgstr "" #: library/nntplib.rst:254 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`` " +"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 "" #: library/nntplib.rst:268 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." +"*password* are ``None`` and *usenetrc* is true, credentials from " +"``~/.netrc`` will be used if possible." msgstr "" #: library/nntplib.rst:272 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." +"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 "" #: library/nntplib.rst:283 msgid "" "Send a ``STARTTLS`` command. This will enable encryption on the NNTP " -"connection. The *context* argument is optional and should be a :class:`ssl." -"SSLContext` object. Please read :ref:`ssl-security` for best practices." +"connection. The *context* argument is optional and should be " +"a :class:`ssl.SSLContext` object. Please read :ref:`ssl-security` for best " +"practices." msgstr "" #: library/nntplib.rst:288 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." +"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 "" #: library/nntplib.rst:295 msgid "" -"The method now supports hostname check with :attr:`ssl.SSLContext." -"check_hostname` and *Server Name Indication* (see :data:`ssl.HAS_SNI`)." +"The method now supports hostname check " +"with :attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* " +"(see :data:`ssl.HAS_SNI`)." msgstr "" #: library/nntplib.rst:302 msgid "" -"Send a ``NEWGROUPS`` command. The *date* argument should be a :class:" -"`datetime.date` or :class:`datetime.datetime` object. Return a pair " +"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." @@ -421,8 +425,8 @@ msgid "" "*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." +"starting from *first* to the last article in the current group, " +"or :const:`None` to select the current article in the current group." msgstr "" #: library/nntplib.rst:396 @@ -505,12 +509,12 @@ msgstr "" #: library/nntplib.rst:462 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." +"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 "" #: library/nntplib.rst:487 @@ -530,8 +534,8 @@ 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 " +"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 "" @@ -592,9 +596,9 @@ msgstr "" #: library/nntplib.rst:561 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." +"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 "" #: library/nntplib.rst:569 diff --git a/library/numbers.po b/library/numbers.po index e531cc38f..dc96abb39 100644 --- a/library/numbers.po +++ b/library/numbers.po @@ -26,10 +26,10 @@ msgstr "" #: 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 are " -"intended to be instantiated." +"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 are intended to be instantiated." msgstr "" #: library/numbers.rst:18 @@ -45,9 +45,9 @@ msgstr "" #: 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 ``!" +"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 "" @@ -73,29 +73,30 @@ msgstr "" #: 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 ``>=``." +"In short, those are: a conversion " +"to :class:`float`, :func:`math.trunc`, :func:`round`, :func:`math.floor`, :func:`math.ceil`, :func:`divmod`, " +"``//``, ``%``, ``<``, ``<=``, ``>``, and ``>=``." msgstr "" #: library/numbers.rst:55 msgid "" -"Real also provides defaults for :func:`complex`, :attr:`~Complex.real`, :" -"attr:`~Complex.imag`, and :meth:`~Complex.conjugate`." +"Real also provides defaults " +"for :func:`complex`, :attr:`~Complex.real`, :attr:`~Complex.imag`, " +"and :meth:`~Complex.conjugate`." msgstr "" #: library/numbers.rst:61 msgid "" -"Subtypes :class:`Real` and adds :attr:`~Rational.numerator` and :attr:" -"`~Rational.denominator` properties. It also provides a default for :func:" -"`float`." +"Subtypes :class:`Real` and adds :attr:`~Rational.numerator` " +"and :attr:`~Rational.denominator` properties. It also provides a default " +"for :func:`float`." msgstr "" #: library/numbers.rst:65 msgid "" "The :attr:`~Rational.numerator` and :attr:`~Rational.denominator` values " -"should be instances of :class:`Integral` and should be in lowest terms with :" -"attr:`~Rational.denominator` positive." +"should be instances of :class:`Integral` and should be in lowest terms " +"with :attr:`~Rational.denominator` positive." msgstr "" #: library/numbers.rst:75 @@ -105,9 +106,10 @@ msgstr "" #: library/numbers.rst:80 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 :func:`pow` with modulus " -"and bit-string operations: ``<<``, ``>>``, ``&``, ``^``, ``|``, ``~``." +"defaults for :func:`float`, :attr:`~Rational.numerator`, " +"and :attr:`~Rational.denominator`. Adds abstract methods for :func:`pow` " +"with modulus and bit-string operations: ``<<``, ``>>``, ``&``, ``^``, ``|``, " +"``~``." msgstr "" #: library/numbers.rst:88 @@ -118,8 +120,8 @@ msgstr "" msgid "" "Implementers 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::" +"the real numbers. For example, :class:`fractions.Fraction` " +"implements :func:`hash` as follows::" msgstr "" #: library/numbers.rst:95 @@ -163,8 +165,9 @@ 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:`~object." -"__add__` and :meth:`~object.__radd__` should be defined as::" +"there. For subtypes of :class:`Integral`, this means " +"that :meth:`~object.__add__` and :meth:`~object.__radd__` should be defined " +"as::" msgstr "" #: library/numbers.rst:132 @@ -196,10 +199,10 @@ msgstr "" #: library/numbers.rst:157 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 <: " +"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 "" @@ -212,9 +215,9 @@ msgstr "" msgid "" "If ``A`` falls back to the boilerplate code, and it were to return a value " "from :meth:`~object.__add__`, we'd miss the possibility that ``B`` defines a " -"more intelligent :meth:`~object.__radd__`, so the boilerplate should return :" -"data:`NotImplemented` from :meth:`!__add__`. (Or ``A`` may not implement :" -"meth:`!__add__` at all.)" +"more intelligent :meth:`~object.__radd__`, so the boilerplate should " +"return :data:`NotImplemented` from :meth:`!__add__`. (Or ``A`` may not " +"implement :meth:`!__add__` at all.)" msgstr "" #: library/numbers.rst:172 @@ -239,17 +242,17 @@ msgstr "" #: library/numbers.rst:182 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:`~object.__radd__` s land there, so ``a+b == " -"b+a``." +"then the appropriate shared operation is the one involving the built " +"in :class:`complex`, and both :meth:`~object.__radd__` s land there, so " +"``a+b == b+a``." msgstr "" #: library/numbers.rst:187 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::" +"reverse instances of any given operator. For " +"example, :class:`fractions.Fraction` uses::" msgstr "" #: library/numbers.rst:192 diff --git a/library/numeric.po b/library/numeric.po index 87941361d..d0fae6a20 100644 --- a/library/numeric.po +++ b/library/numeric.po @@ -25,8 +25,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, " +"various mathematical functions for floating-point and complex numbers. " +"The :mod:`decimal` module supports exact representations of decimal numbers, " "using arbitrary precision arithmetic." msgstr "" diff --git a/library/operator.po b/library/operator.po index 5b1b4792d..25e0d3b6c 100644 --- a/library/operator.po +++ b/library/operator.po @@ -27,12 +27,12 @@ msgstr "" #: 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``. Many function names are " -"those used for special methods, without the double underscores. For " -"backward compatibility, many of these have a variant with the double " -"underscores kept. The variants without the double underscores are preferred " -"for clarity." +"corresponding to the intrinsic operators of Python. For example, " +"``operator.add(x, y)`` is equivalent to the expression ``x+y``. Many " +"function names are those used for special methods, without the double " +"underscores. For backward compatibility, many of these have a variant with " +"the double underscores kept. The variants without the double underscores are " +"preferred for clarity." msgstr "" #: library/operator.rst:25 @@ -54,8 +54,8 @@ msgid "" "``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." +"which may or may not be interpretable as a Boolean value. " +"See :ref:`comparisons` for more information about rich comparisons." msgstr "" #: library/operator.rst:54 @@ -68,8 +68,8 @@ msgstr "" 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:`~object.__bool__` and :meth:" -"`~object.__len__` methods.)" +"operation. The result is affected by the :meth:`~object.__bool__` " +"and :meth:`~object.__len__` methods.)" msgstr "" #: library/operator.rst:69 @@ -242,8 +242,8 @@ msgstr "" #: library/operator.rst:279 msgid "" -"After ``f = attrgetter('name', 'date')``, the call ``f(b)`` returns ``(b." -"name, b.date)``." +"After ``f = attrgetter('name', 'date')``, the call ``f(b)`` returns " +"``(b.name, b.date)``." msgstr "" #: library/operator.rst:282 @@ -308,9 +308,10 @@ msgstr "" #: library/operator.rst:329 msgid "" -"The items can be any type accepted by the operand's :meth:`~object." -"__getitem__` method. Dictionaries accept any :term:`hashable` value. " -"Lists, tuples, and strings accept an index or a slice:" +"The items can be any type accepted by the " +"operand's :meth:`~object.__getitem__` method. Dictionaries accept " +"any :term:`hashable` value. Lists, tuples, and strings accept an index or a " +"slice:" msgstr "" #: library/operator.rst:343 diff --git a/library/optparse.po b/library/optparse.po index 94a560d55..7d27415bd 100644 --- a/library/optparse.po +++ b/library/optparse.po @@ -33,12 +33,12 @@ msgstr "" #: 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." +"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 "" #: library/optparse.rst:26 @@ -152,10 +152,10 @@ msgstr "" #: 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:]``\"." +"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 "" #: library/optparse.rst:106 @@ -166,10 +166,10 @@ msgstr "" 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-" +"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 "" @@ -218,9 +218,9 @@ msgstr "" #: 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:" +"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 "" #: library/optparse.rst:142 @@ -433,8 +433,9 @@ msgstr "" 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." +"refer to *encountering an option* on the command line; in " +"reality, :mod:`optparse` encounters *option strings* and looks up options " +"from them." msgstr "" #: library/optparse.rst:283 @@ -449,9 +450,9 @@ msgstr "" #: library/optparse.rst:288 msgid "" -"(If you like, you can pass a custom argument list to :meth:`~OptionParser." -"parse_args`, but that's rarely necessary: by default it uses ``sys." -"argv[1:]``.)" +"(If you like, you can pass a custom argument list " +"to :meth:`~OptionParser.parse_args`, but that's rarely necessary: by default " +"it uses ``sys.argv[1:]``.)" msgstr "" #: library/optparse.rst:291 @@ -474,9 +475,9 @@ msgstr "" #: 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." +"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 "" #: library/optparse.rst:309 @@ -486,11 +487,11 @@ msgstr "" #: 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``." +"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 "" #: library/optparse.rst:318 @@ -625,8 +626,8 @@ msgstr "" #: 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``." +"``options.verbose`` to ``True``; when it encounters ``-q``, " +"``options.verbose`` is set to ``False``." msgstr "" #: library/optparse.rst:402 @@ -671,8 +672,8 @@ msgstr "" #: library/optparse.rst:418 msgid "" -"These are covered in section :ref:`optparse-reference-guide`, and section :" -"ref:`optparse-option-callbacks`." +"These are covered in section :ref:`optparse-reference-guide`, and " +"section :ref:`optparse-option-callbacks`." msgstr "" #: library/optparse.rst:425 @@ -737,8 +738,8 @@ msgstr "" #: 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:" -"`~OptionParser.parse_args`::" +"of OptionParser, which you can call at any time before " +"calling :meth:`~OptionParser.parse_args`::" msgstr "" #: library/optparse.rst:459 @@ -861,11 +862,11 @@ msgstr "" #: library/optparse.rst:538 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::" +"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 "" #: library/optparse.rst:545 @@ -924,21 +925,22 @@ msgstr "" #: library/optparse.rst:576 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." +":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 "" #: library/optparse.rst:580 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." +"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 "" #: library/optparse.rst:583 msgid "" -"Continuing with the parser defined in the previous section, adding an :class:" -"`OptionGroup` to a parser is easy::" +"Continuing with the parser defined in the previous section, adding " +"an :class:`OptionGroup` to a parser is easy::" msgstr "" #: library/optparse.rst:586 @@ -1036,8 +1038,8 @@ msgstr "" #: library/optparse.rst:661 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``." +"*opt_str* (e.g. ``'-o'`` or ``'--option'``) belongs. If there's no " +"such :class:`OptionGroup`, return ``None``." msgstr "" #: library/optparse.rst:668 @@ -1058,10 +1060,10 @@ msgstr "" #: library/optparse.rst:676 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." +"``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 "" #: library/optparse.rst:682 @@ -1104,8 +1106,9 @@ msgid "" "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." +"are dealt with in the usual way: raise an exception " +"(either :exc:`optparse.OptionError` or :exc:`TypeError`) and let the program " +"crash." msgstr "" #: library/optparse.rst:716 @@ -1163,15 +1166,15 @@ msgstr "" #: library/optparse.rst:752 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." +"option involved in the error; be sure to do the same when " +"calling :func:`OptionParser.error` from your application code." msgstr "" #: library/optparse.rst:756 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." +"needs, you'll need to subclass OptionParser and override " +"its :meth:`~OptionParser.exit` and/or :meth:`~OptionParser.error` methods." msgstr "" #: library/optparse.rst:764 @@ -1342,8 +1345,9 @@ msgstr "" #: library/optparse.rst:865 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:" +"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 "" #: library/optparse.rst:869 @@ -1377,10 +1381,10 @@ msgstr "" #: library/optparse.rst:886 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.)" +"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 "" #: library/optparse.rst:895 @@ -1396,8 +1400,8 @@ msgstr "" #: library/optparse.rst:901 msgid "" -"The canonical way to create an :class:`Option` instance is with the :meth:" -"`add_option` method of :class:`OptionParser`." +"The canonical way to create an :class:`Option` instance is with " +"the :meth:`add_option` method of :class:`OptionParser`." msgstr "" #: library/optparse.rst:907 @@ -1482,17 +1486,18 @@ msgstr "" #: library/optparse.rst:956 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``, which is an instance of :class:`optparse.Values`." +"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``, which is an instance " +"of :class:`optparse.Values`." msgstr "" #: library/optparse.rst:962 msgid "" "An object holding parsed argument names and values as attributes. Normally " "created by calling when calling :meth:`OptionParser.parse_args`, and can be " -"overridden by a custom subclass passed to the *values* argument of :meth:" -"`OptionParser.parse_args` (as described in :ref:`optparse-parsing-" +"overridden by a custom subclass passed to the *values* argument " +"of :meth:`OptionParser.parse_args` (as described in :ref:`optparse-parsing-" "arguments`)." msgstr "" @@ -1572,9 +1577,9 @@ msgstr "" #: library/optparse.rst:1012 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 " +"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 "" @@ -1625,8 +1630,8 @@ msgstr "" #: library/optparse.rst:1051 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`." +"option is seen. If > 1, :mod:`optparse` will store a tuple of values " +"to :attr:`~Option.dest`." msgstr "" #: library/optparse.rst:1057 @@ -1680,15 +1685,15 @@ msgstr "" #: library/optparse.rst:1101 msgid "" -"``\"store\"`` [relevant: :attr:`~Option.type`, :attr:`~Option.dest`, :attr:" -"`~Option.nargs`, :attr:`~Option.choices`]" +"``\"store\"`` " +"[relevant: :attr:`~Option.type`, :attr:`~Option.dest`, :attr:`~Option.nargs`, :attr:`~Option.choices`]" msgstr "" #: library/optparse.rst:1104 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 " +"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." @@ -1744,8 +1749,8 @@ msgstr "" #: library/optparse.rst:1136 msgid "" -"``\"store_const\"`` [required: :attr:`~Option.const`; relevant: :attr:" -"`~Option.dest`]" +"``\"store_const\"`` [required: :attr:`~Option.const`; " +"relevant: :attr:`~Option.dest`]" msgstr "" #: library/optparse.rst:1139 @@ -1776,8 +1781,8 @@ msgstr "" #: library/optparse.rst:1156 msgid "" -"A special case of ``\"store_const\"`` that stores ``True`` to :attr:`~Option." -"dest`." +"A special case of ``\"store_const\"`` that stores ``True`` " +"to :attr:`~Option.dest`." msgstr "" #: library/optparse.rst:1159 @@ -1796,8 +1801,8 @@ msgstr "" #: library/optparse.rst:1168 msgid "" -"``\"append\"`` [relevant: :attr:`~Option.type`, :attr:`~Option.dest`, :attr:" -"`~Option.nargs`, :attr:`~Option.choices`]" +"``\"append\"`` " +"[relevant: :attr:`~Option.type`, :attr:`~Option.dest`, :attr:`~Option.nargs`, :attr:`~Option.choices`]" msgstr "" #: library/optparse.rst:1171 @@ -1861,8 +1866,8 @@ msgstr "" #: library/optparse.rst:1206 msgid "" -"``\"append_const\"`` [required: :attr:`~Option.const`; relevant: :attr:" -"`~Option.dest`]" +"``\"append_const\"`` [required: :attr:`~Option.const`; " +"relevant: :attr:`~Option.dest`]" msgstr "" #: library/optparse.rst:1209 @@ -1910,9 +1915,8 @@ msgstr "" #: library/optparse.rst:1234 msgid "" -"``\"callback\"`` [required: :attr:`~Option.callback`; relevant: :attr:" -"`~Option.type`, :attr:`~Option.nargs`, :attr:`~Option.callback_args`, :attr:" -"`~Option.callback_kwargs`]" +"``\"callback\"`` [required: :attr:`~Option.callback`; " +"relevant: :attr:`~Option.type`, :attr:`~Option.nargs`, :attr:`~Option.callback_args`, :attr:`~Option.callback_kwargs`]" msgstr "" #: library/optparse.rst:1238 @@ -1998,9 +2002,9 @@ 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." +"``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 "" #: library/optparse.rst:1302 @@ -2056,11 +2060,11 @@ msgstr "" #: library/optparse.rst:1329 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." +"``\"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 "" #: library/optparse.rst:1339 @@ -2069,8 +2073,8 @@ msgstr "" #: library/optparse.rst:1341 msgid "" -"The whole point of creating and populating an OptionParser is to call its :" -"meth:`~OptionParser.parse_args` method." +"The whole point of creating and populating an OptionParser is to call " +"its :meth:`~OptionParser.parse_args` method." msgstr "" #: library/optparse.rst:1346 @@ -2257,8 +2261,8 @@ msgstr "" #: library/optparse.rst:1458 msgid "" -"assume option conflicts are a programming error and raise :exc:" -"`OptionConflictError`" +"assume option conflicts are a programming error and " +"raise :exc:`OptionConflictError`" msgstr "" #: library/optparse.rst:1461 @@ -2361,8 +2365,8 @@ msgstr "" 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." +"is replaced with the name of the current program. Does nothing if " +"``self.usage`` is empty or not defined." msgstr "" #: library/optparse.rst:1535 @@ -2373,11 +2377,11 @@ msgstr "" #: library/optparse.rst:1540 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::" +"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 "" #: library/optparse.rst:1546 @@ -2435,10 +2439,10 @@ msgstr "" #: library/optparse.rst:1585 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::" +"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 "" #: library/optparse.rst:1589 @@ -2460,9 +2464,9 @@ msgstr "" #: library/optparse.rst:1600 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::" +"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 "" #: library/optparse.rst:1605 @@ -2486,9 +2490,9 @@ msgstr "" #: library/optparse.rst:1613 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." +"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 "" #: library/optparse.rst:1618 @@ -2556,10 +2560,10 @@ msgstr "" 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." +"``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 "" #: library/optparse.rst:1659 @@ -2581,8 +2585,8 @@ 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:`~OptionParser." -"parse_args`.)" +"become ``args``, the second return value " +"of :meth:`~OptionParser.parse_args`.)" msgstr "" #: library/optparse.rst:1669 @@ -2611,8 +2615,8 @@ msgstr "" #: library/optparse.rst:1683 msgid "" -"is a tuple of arbitrary positional arguments supplied via the :attr:`~Option." -"callback_args` option attribute." +"is a tuple of arbitrary positional arguments supplied via " +"the :attr:`~Option.callback_args` option attribute." msgstr "" #: library/optparse.rst:1686 @@ -2621,8 +2625,8 @@ msgstr "" #: library/optparse.rst:1687 msgid "" -"is a dictionary of arbitrary keyword arguments supplied via :attr:`~Option." -"callback_kwargs`." +"is a dictionary of arbitrary keyword arguments supplied " +"via :attr:`~Option.callback_kwargs`." msgstr "" #: library/optparse.rst:1694 @@ -2746,8 +2750,9 @@ msgid "" "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." +"must be convertible to that type; if you further " +"define :attr:`~Option.nargs`, then the option takes :attr:`~Option.nargs` " +"arguments." msgstr "" #: library/optparse.rst:1788 @@ -2781,9 +2786,9 @@ 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:" +"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 "" #: library/optparse.rst:1814 @@ -2864,16 +2869,16 @@ msgstr "" #: library/optparse.rst:1874 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`." +"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 "" #: library/optparse.rst:1880 msgid "" -"A tuple of type names; in your subclass, simply define a new tuple :attr:" -"`TYPES` that builds on the standard one." +"A tuple of type names; in your subclass, simply define a new " +"tuple :attr:`TYPES` that builds on the standard one." msgstr "" #: library/optparse.rst:1885 @@ -2955,9 +2960,9 @@ msgstr "" #: library/optparse.rst:1931 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.)" +"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 "" #: library/optparse.rst:1936 @@ -2993,8 +2998,8 @@ msgstr "" #: library/optparse.rst:1956 msgid "" -"Adding new actions is a bit trickier, because you have to understand that :" -"mod:`optparse` has a couple of classifications for actions:" +"Adding new actions is a bit trickier, because you have to understand " +"that :mod:`optparse` has a couple of classifications for actions:" msgstr "" #: library/optparse.rst:1959 @@ -3004,8 +3009,8 @@ msgstr "" #: library/optparse.rst:1960 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." +"the current OptionValues instance; these options require " +"a :attr:`~Option.dest` attribute to be supplied to the Option constructor." msgstr "" #: library/optparse.rst:1964 @@ -3056,8 +3061,9 @@ msgstr "" #: library/optparse.rst:1996 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." +"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 "" #: library/optparse.rst:1999 @@ -3111,15 +3117,15 @@ msgstr "" #: library/optparse.rst:2031 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`." +"value somewhere, so it goes in both :attr:`~Option.STORE_ACTIONS` " +"and :attr:`~Option.TYPED_ACTIONS`." msgstr "" #: library/optparse.rst:2035 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." +"``\"extend\"`` actions, we put the ``\"extend\"`` action " +"in :attr:`~Option.ALWAYS_TYPED_ACTIONS` as well." msgstr "" #: library/optparse.rst:2039 @@ -3149,8 +3155,8 @@ msgid "" "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." +"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 "" #: library/optparse.rst:2060 diff --git a/library/os.path.po b/library/os.path.po index 9e84f9dda..e58b63461 100644 --- a/library/os.path.po +++ b/library/os.path.po @@ -56,12 +56,12 @@ msgstr "" #: library/os.path.rst:37 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:" +"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 "" #: library/os.path.rst:45 @@ -74,10 +74,9 @@ msgstr "" #: library/os.path.rst:51 msgid "" -":func:`exists`, :func:`lexists`, :func:`isdir`, :func:`isfile`, :func:" -"`islink`, and :func:`ismount` now return ``False`` instead of raising an " -"exception for paths that contain characters or bytes unrepresentable at the " -"OS level." +":func:`exists`, :func:`lexists`, :func:`isdir`, :func:`isfile`, :func:`islink`, " +"and :func:`ismount` now return ``False`` instead of raising an exception for " +"paths that contain characters or bytes unrepresentable at the OS level." msgstr "" #: library/os.path.rst:59 @@ -162,8 +161,8 @@ msgstr "" #: library/os.path.rst:145 msgid "" "Return ``True`` if *path* refers to an existing path, including broken " -"symbolic links. Equivalent to :func:`exists` on platforms lacking :func:" -"`os.lstat`." +"symbolic links. Equivalent to :func:`exists` on platforms " +"lacking :func:`os.lstat`." msgstr "" #: library/os.path.rst:157 @@ -174,10 +173,11 @@ msgstr "" #: 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." +"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 "" #: library/os.path.rst:167 @@ -216,9 +216,9 @@ msgstr "" #: library/os.path.rst:201 msgid "" "Return the time of last access of *path*. The return value is a floating-" -"point 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." +"point 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 "" #: library/os.path.rst:208 @@ -333,9 +333,9 @@ msgid "" "On Windows, the drive is not reset when a rooted path segment (e.g., " "``r'\\foo'``) is encountered. If a segment is on a different drive or is an " "absolute path, all previous segments are ignored and the drive 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`." +"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 "" #: library/os.path.rst:340 @@ -441,9 +441,10 @@ msgstr "" #: library/os.path.rst:446 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`." +"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 "" #: library/os.path.rst:460 diff --git a/library/os.po b/library/os.po index 1772ec1da..181d29912 100644 --- a/library/os.po +++ b/library/os.po @@ -29,10 +29,10 @@ 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." +"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 "" #: library/os.rst:19 @@ -71,10 +71,10 @@ msgstr "" msgid "" "On WebAssembly platforms ``wasm32-emscripten`` and ``wasm32-wasi``, large " "parts of the :mod:`os` module are not available or behave differently. API " -"related to processes (e.g. :func:`~os.fork`, :func:`~os.execve`), signals (e." -"g. :func:`~os.kill`, :func:`~os.wait`), and resources (e.g. :func:`~os." -"nice`) are not available. Others like :func:`~os.getuid` and :func:`~os." -"getpid` are emulated or stubs." +"related to processes (e.g. :func:`~os.fork`, :func:`~os.execve`), signals " +"(e.g. :func:`~os.kill`, :func:`~os.wait`), and resources " +"(e.g. :func:`~os.nice`) are not available. Others like :func:`~os.getuid` " +"and :func:`~os.getpid` are emulated or stubs." msgstr "" #: library/os.rst:47 @@ -122,9 +122,9 @@ msgstr "" #: library/os.rst:82 msgid "" "The :term:`filesystem encoding and error handler` are configured at Python " -"startup by the :c:func:`PyConfig_Read` function: see :c:member:`~PyConfig." -"filesystem_encoding` and :c:member:`~PyConfig.filesystem_errors` members of :" -"c:type:`PyConfig`." +"startup by the :c:func:`PyConfig_Read` function: " +"see :c:member:`~PyConfig.filesystem_encoding` " +"and :c:member:`~PyConfig.filesystem_errors` members of :c:type:`PyConfig`." msgstr "" #: library/os.rst:87 @@ -140,8 +140,8 @@ msgstr "" msgid "" "The :term:`file system encoding ` " "must guarantee to successfully decode all bytes below 128. If the file " -"system encoding fails to provide this guarantee, API functions can raise :" -"exc:`UnicodeError`." +"system encoding fails to provide this guarantee, API functions can " +"raise :exc:`UnicodeError`." msgstr "" #: library/os.rst:100 @@ -195,9 +195,9 @@ msgstr "" #: library/os.rst:127 msgid "" -"Note that the standard stream settings in UTF-8 mode can be overridden by :" -"envvar:`PYTHONIOENCODING` (just as they can be in the default locale-aware " -"mode)." +"Note that the standard stream settings in UTF-8 mode can be overridden " +"by :envvar:`PYTHONIOENCODING` (just as they can be in the default locale-" +"aware mode)." msgstr "" #: library/os.rst:131 @@ -255,8 +255,8 @@ msgstr "" #: library/os.rst:159 msgid "" -"See also the :ref:`UTF-8 mode on Windows ` and the :term:" -"`filesystem encoding and error handler`." +"See also the :ref:`UTF-8 mode on Windows ` and " +"the :term:`filesystem encoding and error handler`." msgstr "" #: library/os.rst:164 @@ -325,9 +325,9 @@ msgstr "" 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 :data:" -"`os.environ`, except for changes made by modifying :data:`os.environ` " -"directly." +"Changes to the environment made after this time are not reflected " +"in :data:`os.environ`, except for changes made by " +"modifying :data:`os.environ` directly." msgstr "" #: library/os.rst:196 @@ -365,10 +365,10 @@ msgstr "" #: library/os.rst:220 msgid "" -"You can delete items in this mapping to unset environment variables. :func:" -"`unsetenv` will be called automatically when an item is deleted from :data:" -"`os.environ`, and when one of the :meth:`pop` or :meth:`clear` methods is " -"called." +"You can delete items in this mapping to unset environment " +"variables. :func:`unsetenv` will be called automatically when an item is " +"deleted from :data:`os.environ`, and when one of the :meth:`pop` " +"or :meth:`clear` methods is called." msgstr "" #: library/os.rst:241 @@ -379,9 +379,9 @@ msgstr "" #: library/os.rst:231 msgid "" "Bytes version of :data:`environ`: a :term:`mapping` object where both keys " -"and values are :class:`bytes` objects representing the process environment. :" -"data:`environ` and :data:`environb` are synchronized (modifying :data:" -"`environb` updates :data:`environ`, and vice versa)." +"and values are :class:`bytes` objects representing the process " +"environment. :data:`environ` and :data:`environb` are synchronized " +"(modifying :data:`environb` updates :data:`environ`, and vice versa)." msgstr "" #: library/os.rst:236 @@ -396,8 +396,9 @@ msgstr "" #: library/os.rst:255 msgid "" -"Encode :term:`path-like ` *filename* to the :term:" -"`filesystem encoding and error handler`; return :class:`bytes` unchanged." +"Encode :term:`path-like ` *filename* to " +"the :term:`filesystem encoding and error handler`; return :class:`bytes` " +"unchanged." msgstr "" #: library/os.rst:259 @@ -412,8 +413,9 @@ msgstr "" #: library/os.rst:270 msgid "" -"Decode the :term:`path-like ` *filename* from the :term:" -"`filesystem encoding and error handler`; return :class:`str` unchanged." +"Decode the :term:`path-like ` *filename* from " +"the :term:`filesystem encoding and error handler`; return :class:`str` " +"unchanged." msgstr "" #: library/os.rst:274 @@ -451,10 +453,10 @@ msgstr "" #: library/os.rst:312 msgid "" "Return the value of the environment variable *key* as a string if it exists, " -"or *default* if it doesn't. *key* is a string. Note that since :func:" -"`getenv` uses :data:`os.environ`, the mapping of :func:`getenv` is similarly " -"also captured on import, and the function may not reflect future environment " -"changes." +"or *default* if it doesn't. *key* is a string. Note that " +"since :func:`getenv` uses :data:`os.environ`, the mapping of :func:`getenv` " +"is similarly also captured on import, and the function may not reflect " +"future environment changes." msgstr "" #: library/os.rst:318 @@ -467,10 +469,10 @@ msgstr "" #: library/os.rst:327 msgid "" "Return the value of the environment variable *key* as bytes if it exists, or " -"*default* if it doesn't. *key* must be bytes. Note that since :func:" -"`getenvb` uses :data:`os.environb`, the mapping of :func:`getenvb` is " -"similarly also captured on import, and the function may not reflect future " -"environment changes." +"*default* if it doesn't. *key* must be bytes. Note that " +"since :func:`getenvb` uses :data:`os.environb`, the mapping " +"of :func:`getenvb` is similarly also captured on import, and the function " +"may not reflect future environment changes." msgstr "" #: library/os.rst:334 @@ -532,18 +534,19 @@ msgid "" "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`." +"limited to 16. The deployment target " +"value, :const:`MACOSX_DEPLOYMENT_TARGET`, can be obtained " +"with :func:`sysconfig.get_config_var`." msgstr "" #: library/os.rst:419 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 :func:`getpass." -"getuser` since the latter checks the environment variables :envvar:`LOGNAME` " -"or :envvar:`USERNAME` to find out who the user is, and falls back to ``pwd." -"getpwuid(os.getuid())[0]`` to get the login name of the current real user id." +"process. For most purposes, it is more useful to " +"use :func:`getpass.getuser` since the latter checks the environment " +"variables :envvar:`LOGNAME` or :envvar:`USERNAME` to find out who the user " +"is, and falls back to ``pwd.getpwuid(os.getuid())[0]`` to get the login name " +"of the current real user id." msgstr "" #: library/os.rst:431 @@ -573,13 +576,13 @@ msgstr "" #: library/os.rst:472 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." +"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 "" #: library/os.rst:501 @@ -613,8 +616,8 @@ msgstr "" #: library/os.rst:554 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`." +"changes to the environment affect subprocesses started " +"with :func:`os.system`, :func:`popen` or :func:`fork` and :func:`execv`." msgstr "" #: library/os.rst:558 @@ -622,9 +625,9 @@ msgid "" "Assignments to items in :data:`os.environ` are automatically translated into " "corresponding calls to :func:`putenv`; however, calls to :func:`putenv` " "don't update :data:`os.environ`, so it is actually preferable to assign to " -"items of :data:`os.environ`. This also applies to :func:`getenv` and :func:" -"`getenvb`, which respectively use :data:`os.environ` and :data:`os.environb` " -"in their implementations." +"items of :data:`os.environ`. This also applies to :func:`getenv` " +"and :func:`getenvb`, which respectively use :data:`os.environ` " +"and :data:`os.environb` in their implementations." msgstr "" #: library/os.rst:566 @@ -666,15 +669,16 @@ msgstr "" #: library/os.rst:604 msgid "" "On macOS, 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()." +"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 "" #: library/os.rst:611 msgid "" -"Reassociate the current thread with a Linux namespace. See the :manpage:" -"`setns(2)` and :manpage:`namespaces(7)` man pages for more details." +"Reassociate the current thread with a Linux namespace. See " +"the :manpage:`setns(2)` and :manpage:`namespaces(7)` man pages for more " +"details." msgstr "" #: library/os.rst:615 @@ -688,13 +692,14 @@ msgstr "" #: library/os.rst:622 msgid "" -"Since Linux 5.8, *fd* may refer to a PID file descriptor obtained from :func:" -"`~os.pidfd_open`. In this case, ``setns()`` reassociates the calling thread " -"into one or more of the same namespaces as the thread referred to by *fd*. " -"This is subject to any constraints imposed by *nstype*, which is a bit mask " -"combining one or more of the :ref:`CLONE_NEW* constants `, e.g. ``setns(fd, os.CLONE_NEWUTS | os.CLONE_NEWPID)``. The caller's " -"memberships in unspecified namespaces are left unchanged." +"Since Linux 5.8, *fd* may refer to a PID file descriptor obtained " +"from :func:`~os.pidfd_open`. In this case, ``setns()`` reassociates the " +"calling thread into one or more of the same namespaces as the thread " +"referred to by *fd*. This is subject to any constraints imposed by *nstype*, " +"which is a bit mask combining one or more of the :ref:`CLONE_NEW* constants " +"`, e.g. ``setns(fd, os.CLONE_NEWUTS | " +"os.CLONE_NEWPID)``. The caller's memberships in unspecified namespaces are " +"left unchanged." msgstr "" #: library/os.rst:631 @@ -736,15 +741,15 @@ msgstr "" #: library/os.rst:668 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." +"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 "" #: library/os.rst:685 @@ -825,8 +830,9 @@ msgstr "" #: library/os.rst:777 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." +"five-tuple " +"containing :attr:`sysname`, :attr:`nodename`, :attr:`release`, :attr:`version`, " +"and :attr:`machine` in that order." msgstr "" #: library/os.rst:782 @@ -845,8 +851,8 @@ msgstr "" #: library/os.rst:798 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`." +"environment affect subprocesses started " +"with :func:`os.system`, :func:`popen` or :func:`fork` and :func:`execv`." msgstr "" #: library/os.rst:802 @@ -871,11 +877,11 @@ msgstr "" msgid "" "Disassociate parts of the process execution context, and move them into a " "newly created namespace. See the :manpage:`unshare(2)` man page for more " -"details. The *flags* argument is a bit mask, combining zero or more of the :" -"ref:`CLONE_* constants `, that specifies which parts " -"of the execution context should be unshared from their existing associations " -"and moved to a new namespace. If the *flags* argument is ``0``, no changes " -"are made to the calling process's execution context." +"details. The *flags* argument is a bit mask, combining zero or more of " +"the :ref:`CLONE_* constants `, that specifies which " +"parts of the execution context should be unshared from their existing " +"associations and moved to a new namespace. If the *flags* argument is ``0``, " +"no changes are made to the calling process's execution context." msgstr "" #: library/os.rst:832 @@ -895,8 +901,8 @@ msgstr "" #: library/os.rst:861 msgid "" -"These functions create new :term:`file objects `. (See also :" -"func:`~os.open` for opening file descriptors.)" +"These functions create new :term:`file objects `. (See " +"also :func:`~os.open` for opening file descriptors.)" msgstr "" #: library/os.rst:867 @@ -942,8 +948,8 @@ msgstr "" 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." +"\"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 "" #: library/os.rst:907 @@ -972,8 +978,8 @@ msgstr "" #: library/os.rst:924 msgid "" "In Linux kernel older than 5.3, the files pointed to by *src* and *dst* must " -"reside in the same filesystem, otherwise an :exc:`OSError` is raised with :" -"attr:`~OSError.errno` set to :const:`errno.EXDEV`." +"reside in the same filesystem, otherwise an :exc:`OSError` is raised " +"with :attr:`~OSError.errno` set to :const:`errno.EXDEV`." msgstr "" #: library/os.rst:928 @@ -1024,8 +1030,8 @@ msgstr "" #: library/os.rst:967 msgid "" -"Return a duplicate of file descriptor *fd*. The new file descriptor is :ref:" -"`non-inheritable `." +"Return a duplicate of file descriptor *fd*. The new file descriptor " +"is :ref:`non-inheritable `." msgstr "" #: library/os.rst:970 @@ -1077,8 +1083,9 @@ msgstr "" #: library/os.rst:1012 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)``." +"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 "" #: library/os.rst:2091 library/os.rst:2179 @@ -1112,8 +1119,8 @@ msgstr "" 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." +"included in ``pathconf_names``, an :exc:`OSError` is raised " +"with :const:`errno.EINVAL` for the error number." msgstr "" #: library/os.rst:1051 @@ -1158,8 +1165,8 @@ msgstr "" #: library/os.rst:1091 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)``." +"most *length* bytes in size. As of Python 3.3, this is equivalent to " +"``os.truncate(fd, length)``." msgstr "" #: library/os.rst:1095 @@ -1174,8 +1181,8 @@ msgstr "" #: library/os.rst:1105 msgid "" -"Get the blocking mode of the file descriptor: ``False`` if the :data:" -"`O_NONBLOCK` flag is set, ``True`` if the flag is cleared." +"Get the blocking mode of the file descriptor: ``False`` if " +"the :data:`O_NONBLOCK` flag is set, ``True`` if the flag is cleared." msgstr "" #: library/os.rst:1108 @@ -1199,8 +1206,8 @@ msgstr "" #: library/os.rst:1130 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* " +"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 "" @@ -1334,8 +1341,8 @@ msgstr "" 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." +"are defined in the :mod:`os` module. In particular, on Windows " +"adding :const:`O_BINARY` is needed to open files in binary mode." msgstr "" #: library/os.rst:1239 @@ -1353,9 +1360,9 @@ msgstr "" #: library/os.rst:1249 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`." +"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 "" #: library/os.rst:2331 library/os.rst:2442 library/os.rst:2545 @@ -1366,8 +1373,8 @@ msgstr "" #: library/os.rst:1576 library/os.rst:4798 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)." +"exception, the function now retries the system call instead of raising " +"an :exc:`InterruptedError` exception (see :pep:`475` for the rationale)." msgstr "" #: library/os.rst:1963 library/os.rst:2026 library/os.rst:2112 @@ -1380,12 +1387,12 @@ msgstr "" #: library/os.rst:1265 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." +"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 "" #: library/os.rst:1280 @@ -1410,8 +1417,8 @@ msgstr "" #: library/os.rst:1313 msgid "" -"Add :data:`O_EVTONLY`, :data:`O_FSYNC`, :data:`O_SYMLINK` and :data:" -"`O_NOFOLLOW_ANY` constants." +"Add :data:`O_EVTONLY`, :data:`O_FSYNC`, :data:`O_SYMLINK` " +"and :data:`O_NOFOLLOW_ANY` constants." msgstr "" #: library/os.rst:1327 @@ -1448,9 +1455,9 @@ msgstr "" #: library/os.rst:1365 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." +"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 "" #: library/os.rst:1378 @@ -1464,10 +1471,9 @@ 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`." +"*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 "" #: library/os.rst:1408 @@ -1490,10 +1496,11 @@ msgstr "" #: library/os.rst:1431 msgid "" -"Read from a file descriptor *fd* at a position of *offset* into mutable :" -"term:`bytes-like objects ` *buffers*, leaving the file " -"offset unchanged. 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." +"Read from a file descriptor *fd* at a position of *offset* into " +"mutable :term:`bytes-like objects ` *buffers*, leaving " +"the file offset unchanged. 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." msgstr "" #: library/os.rst:1506 @@ -1540,8 +1547,8 @@ msgstr "" #: library/os.rst:1463 msgid "" "If some data was successfully read, it will return the number of bytes read. " -"If no bytes were read, it will return ``-1`` and set errno to :const:`errno." -"EAGAIN`." +"If no bytes were read, it will return ``-1`` and set errno " +"to :const:`errno.EAGAIN`." msgstr "" #: library/os.rst:1474 @@ -1569,10 +1576,10 @@ msgstr "" #: library/os.rst:1500 msgid "" "Write the *buffers* contents to file descriptor *fd* at an offset *offset*, " -"leaving the file offset unchanged. *buffers* must be a sequence of :term:" -"`bytes-like objects `. Buffers are processed in array " -"order. Entire contents of the first buffer is written before proceeding to " -"the second, and so on." +"leaving the file offset unchanged. *buffers* must be a sequence " +"of :term:`bytes-like objects `. Buffers are processed in " +"array order. Entire contents of the first buffer is written before " +"proceeding to the second, and so on." msgstr "" #: library/os.rst:1509 @@ -1626,8 +1633,8 @@ 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." +"or :func:`fdopen`, or :data:`sys.stdin`, use its :meth:`~file.read` " +"or :meth:`~file.readline` methods." msgstr "" #: library/os.rst:1585 @@ -1639,8 +1646,8 @@ msgstr "" #: library/os.rst:1589 msgid "" -"The first function notation is supported by all platforms that define :func:" -"`sendfile`." +"The first function notation is supported by all platforms that " +"define :func:`sendfile`." msgstr "" #: library/os.rst:1592 @@ -1677,8 +1684,8 @@ msgstr "" #: library/os.rst:1612 msgid "" -"For a higher-level wrapper of :func:`sendfile`, see :meth:`socket.socket." -"sendfile`." +"For a higher-level wrapper of :func:`sendfile`, " +"see :meth:`socket.socket.sendfile`." msgstr "" #: library/os.rst:1617 @@ -1700,8 +1707,9 @@ msgstr "" #: library/os.rst:1644 msgid "" -"Set the blocking mode of the specified file descriptor. Set the :data:" -"`O_NONBLOCK` flag if blocking is ``False``, clear the flag otherwise." +"Set the blocking mode of the specified file descriptor. Set " +"the :data:`O_NONBLOCK` flag if blocking is ``False``, clear the flag " +"otherwise." msgstr "" #: library/os.rst:1647 @@ -1716,8 +1724,8 @@ msgid "" "is ``None``, then *src* is read from the current position; respectively for " "*offset_dst*. The offset associated to the file descriptor that refers to a " "pipe must be ``None``. The files pointed to by *src* and *dst* must reside " -"in the same filesystem, otherwise an :exc:`OSError` is raised with :attr:" -"`~OSError.errno` set to :const:`errno.EXDEV`." +"in the same filesystem, otherwise an :exc:`OSError` is raised " +"with :attr:`~OSError.errno` set to :const:`errno.EXDEV`." msgstr "" #: library/os.rst:1673 @@ -1772,9 +1780,9 @@ msgstr "" 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." +"\"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 "" #: library/os.rst:1760 @@ -1907,8 +1915,8 @@ msgstr "" msgid "" "You can check whether or not *path* can be specified as a file descriptor " "for a particular function on your platform using :data:`os.supports_fd`. If " -"this functionality is unavailable, using it will raise a :exc:" -"`NotImplementedError`." +"this functionality is unavailable, using it will raise " +"a :exc:`NotImplementedError`." msgstr "" #: library/os.rst:1881 @@ -1957,10 +1965,10 @@ msgid "" "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." +"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 "" #: library/os.rst:1922 @@ -2040,8 +2048,9 @@ msgstr "" #: library/os.rst:1986 msgid "" -"This function can raise :exc:`OSError` and subclasses such as :exc:" -"`FileNotFoundError`, :exc:`PermissionError`, and :exc:`NotADirectoryError`." +"This function can raise :exc:`OSError` and subclasses such " +"as :exc:`FileNotFoundError`, :exc:`PermissionError`, " +"and :exc:`NotADirectoryError`." msgstr "" #: library/os.rst:2122 @@ -2058,8 +2067,8 @@ msgstr "" #: library/os.rst:2001 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):" +"combination (bitwise OR) of the following values (as defined in " +"the :mod:`stat` module):" msgstr "" #: library/os.rst:2004 @@ -2210,9 +2219,9 @@ msgstr "" #: library/os.rst:2084 library/os.rst:3472 msgid "" -"This function can support :ref:`specifying a file descriptor `, :" -"ref:`paths relative to directory descriptors ` and :ref:`not " -"following symlinks `." +"This function can support :ref:`specifying a file descriptor " +"`, :ref:`paths relative to directory descriptors ` " +"and :ref:`not following symlinks `." msgstr "" #: library/os.rst:2062 @@ -2273,16 +2282,16 @@ msgstr "" #: library/os.rst:2144 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)``." +"not follow symbolic links. As of Python 3.3, this is equivalent to " +"``os.chflags(path, flags, follow_symlinks=False)``." msgstr "" #: library/os.rst:2158 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)``." +"for possible values of *mode*. As of Python 3.3, this is equivalent to " +"``os.chmod(path, mode, follow_symlinks=False)``." msgstr "" #: library/os.rst:2163 @@ -2305,8 +2314,8 @@ msgstr "" #: library/os.rst:2191 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 `." +"supply :ref:`paths relative to directory descriptors `, " +"and :ref:`not following symlinks `." msgstr "" #: library/os.rst:2195 @@ -2403,10 +2412,10 @@ msgstr "" #: library/os.rst:2270 msgid "" -"*volume* must be represented as a GUID path, like those returned by :func:" -"`os.listvolumes`. Volumes may be mounted in multiple locations or not at " -"all. In the latter case, the list will be empty. Mount points that are not " -"associated with a volume will not be returned by this function." +"*volume* must be represented as a GUID path, like those returned " +"by :func:`os.listvolumes`. Volumes may be mounted in multiple locations or " +"not at all. In the latter case, the list will be empty. Mount points that " +"are not associated with a volume will not be returned by this function." msgstr "" #: library/os.rst:2276 @@ -2453,14 +2462,14 @@ msgstr "" #: library/os.rst:2311 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." +"Similar to :func:`~os.stat`, but does not follow symbolic links. Return " +"a :class:`stat_result` object." msgstr "" #: library/os.rst:2315 msgid "" -"On platforms that do not support symbolic links, this is an alias for :func:" -"`~os.stat`." +"On platforms that do not support symbolic links, this is an alias " +"for :func:`~os.stat`." msgstr "" #: library/os.rst:2318 @@ -2483,8 +2492,8 @@ msgstr "" msgid "" "On Windows, now opens reparse points that represent another path (name " "surrogates), including symbolic links and directory junctions. Other kinds " -"of reparse points are resolved by the operating system as for :func:`~os." -"stat`." +"of reparse points are resolved by the operating system as " +"for :func:`~os.stat`." msgstr "" #: library/os.rst:2346 @@ -2567,10 +2576,10 @@ msgstr "" #: library/os.rst:2413 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`." +"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 "" #: library/os.rst:2421 @@ -2599,23 +2608,23 @@ msgstr "" 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." +"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 "" #: library/os.rst:2473 msgid "" -"Extract the device major number from a raw device number (usually the :attr:" -"`st_dev` or :attr:`st_rdev` field from :c:struct:`stat`)." +"Extract the device major number from a raw device number (usually " +"the :attr:`st_dev` or :attr:`st_rdev` field from :c:struct:`stat`)." msgstr "" #: library/os.rst:2479 msgid "" -"Extract the device minor number from a raw device number (usually the :attr:" -"`st_dev` or :attr:`st_rdev` field from :c:struct:`stat`)." +"Extract the device minor number from a raw device number (usually " +"the :attr:`st_dev` or :attr:`st_rdev` field from :c:struct:`stat`)." msgstr "" #: library/os.rst:2485 @@ -2649,22 +2658,23 @@ msgstr "" 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)``." +"relative, it may be converted to an absolute pathname using " +"``os.path.join(os.path.dirname(path), result)``." msgstr "" #: library/os.rst:2528 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." +"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 "" #: library/os.rst:2536 msgid "" -"When trying to resolve a path that may contain links, use :func:`~os.path." -"realpath` to properly handle recursion and platform differences." +"When trying to resolve a path that may contain links, " +"use :func:`~os.path.realpath` to properly handle recursion and platform " +"differences." msgstr "" #: library/os.rst:2548 @@ -2684,9 +2694,9 @@ msgstr "" #: library/os.rst:2560 msgid "" -"Remove (delete) the file *path*. If *path* is a directory, an :exc:" -"`OSError` is raised. Use :func:`rmdir` to remove directories. If the file " -"does not exist, a :exc:`FileNotFoundError` is raised." +"Remove (delete) the file *path*. If *path* is a directory, " +"an :exc:`OSError` is raised. Use :func:`rmdir` to remove directories. If " +"the file does not exist, a :exc:`FileNotFoundError` is raised." msgstr "" #: library/os.rst:2677 library/os.rst:3366 @@ -2734,14 +2744,14 @@ msgstr "" #: library/os.rst:2606 msgid "" "On Windows, if *dst* exists a :exc:`FileExistsError` is always raised. The " -"operation may fail if *src* and *dst* are on different filesystems. Use :" -"func:`shutil.move` to support moves to a different filesystem." +"operation may fail if *src* and *dst* are on different filesystems. " +"Use :func:`shutil.move` to support moves to a different filesystem." msgstr "" #: library/os.rst:2610 msgid "" -"On Unix, if *src* is a file and *dst* is a directory or vice-versa, an :exc:" -"`IsADirectoryError` or a :exc:`NotADirectoryError` will be raised " +"On Unix, if *src* is a file and *dst* is a directory or vice-versa, " +"an :exc:`IsADirectoryError` or a :exc:`NotADirectoryError` will be raised " "respectively. If both are directories and *dst* is empty, *dst* will be " "silently replaced. If *dst* is a non-empty directory, an :exc:`OSError` is " "raised. If both are files, *dst* will be replaced silently if the user has " @@ -2758,8 +2768,8 @@ msgstr "" #: library/os.rst:2622 msgid "" -"If you want cross-platform overwriting of the destination, use :func:" -"`replace`." +"If you want cross-platform overwriting of the destination, " +"use :func:`replace`." msgstr "" #: library/os.rst:2645 library/os.rst:2662 @@ -2804,8 +2814,8 @@ msgstr "" msgid "" "Remove (delete) the directory *path*. If the directory does not exist or is " "not empty, a :exc:`FileNotFoundError` or an :exc:`OSError` is raised " -"respectively. In order to remove whole directory trees, :func:`shutil." -"rmtree` can be used." +"respectively. In order to remove whole directory " +"trees, :func:`shutil.rmtree` can be used." msgstr "" #: library/os.rst:2680 @@ -2829,11 +2839,12 @@ 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." +"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 "" #: library/os.rst:2708 @@ -2890,17 +2901,17 @@ msgid "" "pubs.opengroup.org/onlinepubs/009695399/functions/opendir.html>`_ and " "`readdir() `_ functions. On Windows, it uses the Win32 `FindFirstFileW " -"`_ and `FindNextFileW `_ functions." +"`_ and `FindNextFileW `_ functions." msgstr "" #: library/os.rst:2757 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." +"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 "" #: library/os.rst:2763 @@ -2958,25 +2969,25 @@ msgstr "" #: library/os.rst:2798 msgid "" "The :attr:`name` attribute will be ``bytes`` if the :func:`scandir` *path* " -"argument is of type ``bytes`` and ``str`` otherwise. Use :func:`~os." -"fsdecode` to decode byte filenames." +"argument is of type ``bytes`` and ``str`` otherwise. " +"Use :func:`~os.fsdecode` to decode byte filenames." msgstr "" #: library/os.rst:2804 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. " -"If the :func:`scandir` *path* argument was a :ref:`file descriptor " -"`, the :attr:`path` attribute is the same as the :attr:`name` " -"attribute." +"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. If the :func:`scandir` *path* argument was a :ref:`file " +"descriptor `, the :attr:`path` attribute is the same as " +"the :attr:`name` attribute." msgstr "" #: library/os.rst:2811 msgid "" "The :attr:`path` attribute will be ``bytes`` if the :func:`scandir` *path* " -"argument is of type ``bytes`` and ``str`` otherwise. Use :func:`~os." -"fsdecode` to decode byte filenames." +"argument is of type ``bytes`` and ``str`` otherwise. " +"Use :func:`~os.fsdecode` to decode byte filenames." msgstr "" #: library/os.rst:2817 @@ -2985,8 +2996,9 @@ msgstr "" #: library/os.rst:2819 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." +"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 "" #: library/os.rst:2823 @@ -3028,8 +3040,8 @@ msgstr "" #: library/os.rst:2877 msgid "" -"This method can raise :exc:`OSError`, such as :exc:`PermissionError`, but :" -"exc:`FileNotFoundError` is caught and not raised." +"This method can raise :exc:`OSError`, such as :exc:`PermissionError`, " +"but :exc:`FileNotFoundError` is caught and not raised." msgstr "" #: library/os.rst:2852 @@ -3061,8 +3073,8 @@ msgstr "" #: library/os.rst:2869 msgid "" -"The result is cached on the ``os.DirEntry`` object. Call :func:`os.path." -"islink` to fetch up-to-date information." +"The result is cached on the ``os.DirEntry`` object. " +"Call :func:`os.path.islink` to fetch up-to-date information." msgstr "" #: library/os.rst:2872 @@ -3082,8 +3094,8 @@ msgstr "" #: library/os.rst:2886 msgid "" -"The result is cached on the ``os.DirEntry`` object. Call :func:`os.path." -"isjunction` to fetch up-to-date information." +"The result is cached on the ``os.DirEntry`` object. " +"Call :func:`os.path.isjunction` to fetch up-to-date information." msgstr "" #: library/os.rst:2893 @@ -3102,8 +3114,8 @@ msgstr "" #: library/os.rst:2902 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 " +"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 "" @@ -3124,8 +3136,8 @@ msgstr "" #: library/os.rst:2918 msgid "" -"Added support for the :class:`~os.PathLike` interface. Added support for :" -"class:`bytes` paths on Windows." +"Added support for the :class:`~os.PathLike` interface. Added support " +"for :class:`bytes` paths on Windows." msgstr "" #: library/os.rst:2922 @@ -3138,11 +3150,11 @@ msgstr "" #: library/os.rst:2931 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 or bytes -- directly or indirectly through the :class:" -"`PathLike` interface -- or as an open file descriptor. Return a :class:" -"`stat_result` object." +"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 or bytes -- directly or indirectly through " +"the :class:`PathLike` interface -- or as an open file descriptor. Return " +"a :class:`stat_result` object." msgstr "" #: library/os.rst:2937 @@ -3153,8 +3165,8 @@ msgstr "" #: library/os.rst:3806 library/os.rst:3838 library/os.rst:3858 msgid "" -"This function can support :ref:`specifying a file descriptor ` and :" -"ref:`not following symlinks `." +"This function can support :ref:`specifying a file descriptor ` " +"and :ref:`not following symlinks `." msgstr "" #: library/os.rst:2943 @@ -3165,10 +3177,10 @@ msgid "" "the operating system is unable to follow will be opened directly. When " "following a chain of multiple links, this may result in the original link " "being returned instead of the non-link that prevented full traversal. To " -"obtain stat results for the final path in this case, use the :func:`os.path." -"realpath` function to resolve the path name as far as possible and call :" -"func:`lstat` on the result. This does not apply to dangling symlinks or " -"junction points, which will raise the usual exceptions." +"obtain stat results for the final path in this case, use " +"the :func:`os.path.realpath` function to resolve the path name as far as " +"possible and call :func:`lstat` on the result. This does not apply to " +"dangling symlinks or junction points, which will raise the usual exceptions." msgstr "" #: library/os.rst:3726 @@ -3209,9 +3221,9 @@ msgstr "" #: library/os.rst:2989 msgid "" -"Object whose attributes correspond roughly to the members of the :c:struct:" -"`stat` structure. It is used for the result of :func:`os.stat`, :func:`os." -"fstat` and :func:`os.lstat`." +"Object whose attributes correspond roughly to the members of " +"the :c:struct:`stat` structure. It is used for the result " +"of :func:`os.stat`, :func:`os.fstat` and :func:`os.lstat`." msgstr "" #: library/os.rst:2993 @@ -3324,25 +3336,26 @@ msgstr "" #: library/os.rst:3093 msgid "" -"The exact meaning and resolution of the :attr:`st_atime`, :attr:`st_mtime`, :" -"attr:`st_ctime` and :attr:`st_birthtime` attributes depend on the operating " -"system and the file system. For example, on Windows systems using the 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." +"The exact meaning and resolution of " +"the :attr:`st_atime`, :attr:`st_mtime`, :attr:`st_ctime` " +"and :attr:`st_birthtime` attributes depend on the operating system and the " +"file system. For example, on Windows systems using the 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 "" #: library/os.rst:3100 msgid "" -"Similarly, although :attr:`st_atime_ns`, :attr:`st_mtime_ns`, :attr:" -"`st_ctime_ns` and :attr:`st_birthtime_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`, :attr:`st_ctime` and :attr:" -"`st_birthtime` 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`, :attr:`st_ctime_ns` and :attr:" -"`st_birthtime_ns`." +"Similarly, " +"although :attr:`st_atime_ns`, :attr:`st_mtime_ns`, :attr:`st_ctime_ns` " +"and :attr:`st_birthtime_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`, :attr:`st_ctime` " +"and :attr:`st_birthtime` 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`, :attr:`st_ctime_ns` " +"and :attr:`st_birthtime_ns`." msgstr "" #: library/os.rst:3110 @@ -3353,8 +3366,8 @@ msgstr "" #: library/os.rst:3115 msgid "" -"Number of 512-byte blocks allocated for file. This may be smaller than :attr:" -"`st_size`/512 when the file has holes." +"Number of 512-byte blocks allocated for file. This may be smaller " +"than :attr:`st_size`/512 when the file has holes." msgstr "" #: library/os.rst:3120 @@ -3416,16 +3429,16 @@ msgstr "" msgid "" "Windows file attributes: ``dwFileAttributes`` member of the " "``BY_HANDLE_FILE_INFORMATION`` structure returned by :c:func:`!" -"GetFileInformationByHandle`. See the :const:`!FILE_ATTRIBUTE_* ` constants in the :mod:`stat` module." +"GetFileInformationByHandle`. See the :const:`!FILE_ATTRIBUTE_* " +"` constants in the :mod:`stat` module." msgstr "" #: library/os.rst:3174 msgid "" -"When :attr:`st_file_attributes` has the :const:`~stat." -"FILE_ATTRIBUTE_REPARSE_POINT` set, this field contains the tag identifying " -"the type of reparse point. See the :const:`IO_REPARSE_TAG_* ` constants in the :mod:`stat` module." +"When :attr:`st_file_attributes` has " +"the :const:`~stat.FILE_ATTRIBUTE_REPARSE_POINT` set, this field contains the " +"tag identifying the type of reparse point. See the :const:`IO_REPARSE_TAG_* " +"` constants in the :mod:`stat` module." msgstr "" #: library/os.rst:3179 @@ -3439,12 +3452,11 @@ msgstr "" 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:struct:`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." +"portable) members of the :c:struct:`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 "" #: library/os.rst:3192 @@ -3461,8 +3473,8 @@ msgstr "" #: library/os.rst:3202 msgid "" -"On Windows, the :attr:`st_mode` member now identifies special files as :" -"const:`S_IFCHR`, :const:`S_IFIFO` or :const:`S_IFBLK` as appropriate." +"On Windows, the :attr:`st_mode` member now identifies special files " +"as :const:`S_IFCHR`, :const:`S_IFIFO` or :const:`S_IFBLK` as appropriate." msgstr "" #: library/os.rst:3207 @@ -3494,9 +3506,7 @@ 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:struct:`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`, :attr:`f_fsid`." +"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`, :attr:`f_fsid`." msgstr "" #: library/os.rst:3232 @@ -3510,14 +3520,15 @@ msgstr "" #: library/os.rst:3237 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)." +"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 "" #: library/os.rst:3250 @@ -3526,10 +3537,8 @@ msgstr "" #: library/os.rst:3256 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." +"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 "" #: library/os.rst:3265 @@ -3571,8 +3580,8 @@ msgid "" "A :class:`set` object indicating whether :func:`os.access` permits " "specifying ``True`` for its *effective_ids* parameter on the local platform. " "(Specifying ``False`` for *effective_ids* is always supported on all " -"platforms.) If the local platform supports it, the collection will contain :" -"func:`os.access`; otherwise it will be empty." +"platforms.) If the local platform supports it, the collection will " +"contain :func:`os.access`; otherwise it will be empty." msgstr "" #: library/os.rst:3302 @@ -3604,8 +3613,8 @@ msgstr "" msgid "" "To determine 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 evaluates to ``True`` if :" -"func:`os.chdir` accepts open file descriptors for *path* on your local " +"``supports_fd``. As an example, this expression evaluates to ``True`` " +"if :func:`os.chdir` accepts open file descriptors for *path* on your local " "platform::" msgstr "" @@ -3631,8 +3640,8 @@ msgid "" "To check whether a particular function accepts ``False`` for its " "*follow_symlinks* parameter, use the ``in`` operator on " "``supports_follow_symlinks``. As an example, this expression evaluates to " -"``True`` if you may specify ``follow_symlinks=False`` when calling :func:`os." -"stat` on the local platform::" +"``True`` if you may specify ``follow_symlinks=False`` when " +"calling :func:`os.stat` on the local platform::" msgstr "" #: library/os.rst:3351 @@ -3739,12 +3748,12 @@ msgstr "" #: library/os.rst:3465 msgid "" -"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 :" -"func:`utime`." +"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 :func:`utime`." msgstr "" #: library/os.rst:3476 @@ -3987,10 +3996,10 @@ msgstr "" #: library/os.rst:3698 msgid "" "Create and return an event file descriptor. The file descriptors supports " -"raw :func:`read` and :func:`write` with a buffer size of 8, :func:`~select." -"select`, :func:`~select.poll` and similar. See man page :manpage:" -"`eventfd(2)` for more information. By default, the new file descriptor is :" -"ref:`non-inheritable `." +"raw :func:`read` and :func:`write` with a buffer size of " +"8, :func:`~select.select`, :func:`~select.poll` and similar. See man " +"page :manpage:`eventfd(2)` for more information. By default, the new file " +"descriptor is :ref:`non-inheritable `." msgstr "" #: library/os.rst:3704 @@ -4009,8 +4018,8 @@ msgstr "" #: library/os.rst:3712 msgid "" -"If :const:`EFD_SEMAPHORE` is specified and the event counter is non-zero, :" -"func:`eventfd_read` returns 1 and decrements the counter by one." +"If :const:`EFD_SEMAPHORE` is specified and the event counter is non-" +"zero, :func:`eventfd_read` returns 1 and decrements the counter by one." msgstr "" #: library/os.rst:3715 @@ -4022,15 +4031,15 @@ msgstr "" #: library/os.rst:3719 msgid "" -"If the event counter is zero and :const:`EFD_NONBLOCK` is not specified, :" -"func:`eventfd_read` blocks." +"If the event counter is zero and :const:`EFD_NONBLOCK` is not " +"specified, :func:`eventfd_read` blocks." msgstr "" #: library/os.rst:3722 msgid "" ":func:`eventfd_write` increments the event counter. Write blocks if the " -"write operation would increment the counter to a value larger than 2\\ :sup:" -"`64`\\ -\\ 2." +"write operation would increment the counter to a value larger than " +"2\\ :sup:`64`\\ -\\ 2." msgstr "" #: library/os.rst:3728 @@ -4089,9 +4098,9 @@ msgstr "" #: library/os.rst:3801 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." +"*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 "" #: library/os.rst:3809 @@ -4121,9 +4130,9 @@ msgstr "" #: library/os.rst:3833 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 :term:" -"`filesystem encoding and error handler`." +"*attribute* should be bytes or str (directly or indirectly through " +"the :class:`PathLike` interface). If it is a string, it is encoded with " +"the :term:`filesystem encoding and error handler`." msgstr "" #: library/os.rst:3841 @@ -4139,9 +4148,9 @@ msgid "" "indirectly through the :class:`PathLike` interface). If it is a str, it is " "encoded with the :term:`filesystem encoding and error handler`. *flags* may " "be :data:`XATTR_REPLACE` or :data:`XATTR_CREATE`. If :data:`XATTR_REPLACE` " -"is given and the attribute does not exist, ``ENODATA`` will be raised. If :" -"data:`XATTR_CREATE` is given and the attribute already exists, the attribute " -"will not be created and ``EEXISTS`` will be raised." +"is given and the attribute does not exist, ``ENODATA`` will be raised. " +"If :data:`XATTR_CREATE` is given and the attribute already exists, the " +"attribute will not be created and ``EEXISTS`` will be raised." msgstr "" #: library/os.rst:3863 @@ -4198,8 +4207,8 @@ 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`." +"function will not call the Python signal handler registered " +"for :const:`SIGABRT` with :func:`signal.signal`." msgstr "" #: library/os.rst:3917 @@ -4221,9 +4230,9 @@ msgstr "" #: library/os.rst:3926 msgid "" -"See the `Microsoft documentation `_ for more information about how " -"DLLs are loaded." +"See the `Microsoft documentation `_ for more information about how DLLs " +"are loaded." msgstr "" #: library/os.rst:3930 @@ -4259,8 +4268,8 @@ msgstr "" 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." +"files, you should flush them using :func:`sys.stdout.flush` " +"or :func:`os.fsync` before calling an :func:`exec\\* ` function." msgstr "" #: library/os.rst:3967 @@ -4278,16 +4287,17 @@ msgstr "" #: library/os.rst:3976 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. Relative paths must include at least one slash, " -"even on Windows, as plain names will not be resolved." +"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. Relative paths must " +"include at least one slash, even on Windows, as plain names will not be " +"resolved." msgstr "" #: library/os.rst:3987 @@ -4295,18 +4305,18 @@ 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." +"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 "" #: library/os.rst:3994 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`." +"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 "" #: library/os.rst:3999 @@ -4317,8 +4327,8 @@ msgstr "" #: library/os.rst:4003 msgid "" -"Added support for specifying *path* as an open file descriptor for :func:" -"`execve`." +"Added support for specifying *path* as an open file descriptor " +"for :func:`execve`." msgstr "" #: library/os.rst:4012 @@ -4463,14 +4473,14 @@ msgstr "" #: library/os.rst:4178 msgid "" -"Calling ``fork()`` in a subinterpreter is no longer supported (:exc:" -"`RuntimeError` is raised)." +"Calling ``fork()`` in a subinterpreter is no longer supported " +"(:exc:`RuntimeError` is raised)." msgstr "" #: library/os.rst:4182 msgid "" -"If Python is able to detect that your process has multiple threads, :func:" -"`os.fork` now raises a :exc:`DeprecationWarning`." +"If Python is able to detect that your process has multiple " +"threads, :func:`os.fork` now raises a :exc:`DeprecationWarning`." msgstr "" #: library/os.rst:4186 @@ -4514,15 +4524,15 @@ msgstr "" #: library/os.rst:4222 msgid "" -"Calling ``forkpty()`` in a subinterpreter is no longer supported (:exc:" -"`RuntimeError` is raised)." +"Calling ``forkpty()`` in a subinterpreter is no longer supported " +"(:exc:`RuntimeError` is raised)." msgstr "" #: library/os.rst:4226 msgid "" "If Python is able to detect that your process has multiple threads, this now " -"raises a :exc:`DeprecationWarning`. See the longer explanation on :func:`os." -"fork`." +"raises a :exc:`DeprecationWarning`. See the longer explanation " +"on :func:`os.fork`." msgstr "" #: library/os.rst:4240 @@ -4533,10 +4543,10 @@ msgstr "" #: library/os.rst:4243 msgid "" -"Windows: The :const:`signal.CTRL_C_EVENT` and :const:`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 " +"Windows: The :const:`signal.CTRL_C_EVENT` " +"and :const:`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." @@ -4597,9 +4607,9 @@ 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 " -"have 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." +"have 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 "" #: library/os.rst:4321 @@ -4636,9 +4646,9 @@ msgstr "" #: library/os.rst:4346 msgid "" -":func:`popen` is a simple wrapper around :class:`subprocess.Popen`. Use :" -"class:`subprocess.Popen` or :func:`subprocess.run` to control options like " -"encodings." +":func:`popen` is a simple wrapper around :class:`subprocess.Popen`. " +"Use :class:`subprocess.Popen` or :func:`subprocess.run` to control options " +"like encodings." msgstr "" #: library/os.rst:4355 @@ -4652,8 +4662,8 @@ msgstr "" #: library/os.rst:4359 msgid "" -"The positional-only arguments *path*, *args*, and *env* are similar to :func:" -"`execve`." +"The positional-only arguments *path*, *args*, and *env* are similar " +"to :func:`execve`." msgstr "" #: library/os.rst:4362 @@ -4701,8 +4711,8 @@ msgid "" "These tuples correspond to the C library :c:func:`!" "posix_spawn_file_actions_addopen`, :c:func:`!" "posix_spawn_file_actions_addclose`, and :c:func:`!" -"posix_spawn_file_actions_adddup2` API calls used to prepare for the :c:func:" -"`!posix_spawn` call itself." +"posix_spawn_file_actions_adddup2` API calls used to prepare for " +"the :c:func:`!posix_spawn` call itself." msgstr "" #: library/os.rst:4396 @@ -4728,9 +4738,9 @@ msgstr "" #: library/os.rst:4410 msgid "" "If the *setsid* argument is ``True``, it will create a new session ID for " -"``posix_spawn``. *setsid* requires :c:macro:`!POSIX_SPAWN_SETSID` or :c:" -"macro:`!POSIX_SPAWN_SETSID_NP` flag. Otherwise, :exc:`NotImplementedError` " -"is raised." +"``posix_spawn``. *setsid* requires :c:macro:`!POSIX_SPAWN_SETSID` " +"or :c:macro:`!POSIX_SPAWN_SETSID_NP` flag. " +"Otherwise, :exc:`NotImplementedError` is raised." msgstr "" #: library/os.rst:4415 @@ -4781,9 +4791,9 @@ msgstr "" #: library/os.rst:4459 msgid "" -"Register callables to be executed when a new child process is forked using :" -"func:`os.fork` or similar process cloning APIs. The parameters are optional " -"and keyword-only. Each specifies a different call point." +"Register callables to be executed when a new child process is forked " +"using :func:`os.fork` or similar process cloning APIs. The parameters are " +"optional and keyword-only. Each specifies a different call point." msgstr "" #: library/os.rst:4464 @@ -4817,8 +4827,9 @@ msgstr "" #: library/os.rst:4478 msgid "" "Note that :c:func:`fork` calls made by third-party C code may not call those " -"functions, unless it explicitly calls :c:func:`PyOS_BeforeFork`, :c:func:" -"`PyOS_AfterFork_Parent` and :c:func:`PyOS_AfterFork_Child`." +"functions, unless it explicitly " +"calls :c:func:`PyOS_BeforeFork`, :c:func:`PyOS_AfterFork_Parent` " +"and :c:func:`PyOS_AfterFork_Child`." msgstr "" #: library/os.rst:4482 @@ -4833,8 +4844,8 @@ msgstr "" 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.)" +"is preferable to using these functions. Check especially " +"the :ref:`subprocess-replacements` section.)" msgstr "" #: library/os.rst:4505 @@ -4866,15 +4877,15 @@ msgstr "" #: library/os.rst:4523 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." +"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 "" #: library/os.rst:4533 @@ -4882,11 +4893,12 @@ 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``." +"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 "" #: library/os.rst:4542 @@ -4921,9 +4933,9 @@ msgstr "" #: library/os.rst:4567 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." +"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 "" #: library/os.rst:4577 @@ -4938,11 +4950,11 @@ msgstr "" #: library/os.rst:4589 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." +"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 "" #: library/os.rst:4600 @@ -4952,9 +4964,9 @@ msgstr "" #: library/os.rst:4602 msgid "" "When *operation* is not specified, 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." +"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 "" #: library/os.rst:4607 @@ -5018,8 +5030,8 @@ msgstr "" #: library/os.rst:4642 msgid "" -"Added the *arguments*, *cwd* and *show_cmd* arguments, and the ``os." -"startfile/2`` audit event." +"Added the *arguments*, *cwd* and *show_cmd* arguments, and the " +"``os.startfile/2`` audit event." msgstr "" #: library/os.rst:4649 @@ -5042,10 +5054,10 @@ msgstr "" #: library/os.rst:4660 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." +"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 "" #: library/os.rst:4666 @@ -5104,8 +5116,8 @@ msgstr "" #: library/os.rst:4695 msgid "" -"See the Unix manual page :manpage:`times(2)` and `times(3) `_ manual page on Unix or `the " +"See the Unix manual page :manpage:`times(2)` and `times(3) `_ manual page on Unix or `the " "GetProcessTimes MSDN `_ on Windows. On " "Windows, only :attr:`!user` and :attr:`!system` are known; the other " @@ -5136,8 +5148,8 @@ msgstr "" #: library/os.rst:4725 msgid "" "The other :func:`!wait*` functions documented below can be used to wait for " -"the completion of a specific child process and have more options. :func:" -"`waitpid` is the only one also available on Windows." +"the completion of a specific child process and have more " +"options. :func:`waitpid` is the only one also available on Windows." msgstr "" #: library/os.rst:4732 @@ -5146,22 +5158,22 @@ msgstr "" #: library/os.rst:4734 msgid "" -"*idtype* can be :data:`P_PID`, :data:`P_PGID`, :data:`P_ALL`, or (on Linux) :" -"data:`P_PIDFD`. The interpretation of *id* depends on it; see their " +"*idtype* can be :data:`P_PID`, :data:`P_PGID`, :data:`P_ALL`, or (on " +"Linux) :data:`P_PIDFD`. The interpretation of *id* depends on it; see their " "individual descriptions." msgstr "" #: library/os.rst:4737 msgid "" -"*options* is an OR combination of flags. At least one of :data:`WEXITED`, :" -"data:`WSTOPPED` or :data:`WCONTINUED` is required; :data:`WNOHANG` and :data:" -"`WNOWAIT` are additional optional flags." +"*options* is an OR combination of flags. At least one " +"of :data:`WEXITED`, :data:`WSTOPPED` or :data:`WCONTINUED` is " +"required; :data:`WNOHANG` and :data:`WNOWAIT` are additional optional flags." msgstr "" #: library/os.rst:4741 msgid "" -"The return value is an object representing the data contained in the :c:type:" -"`siginfo_t` structure with the following attributes:" +"The return value is an object representing the data contained in " +"the :c:type:`siginfo_t` structure with the following attributes:" msgstr "" #: library/os.rst:4744 @@ -5236,9 +5248,9 @@ msgid "" "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." +"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 "" #: library/os.rst:4806 @@ -5299,8 +5311,8 @@ msgstr "" #: library/os.rst:4858 msgid "" -"This *options* flag for :func:`waitpid`, :func:`wait3`, :func:`wait4`, and :" -"func:`waitid` causes child processes to be reported if they have been " +"This *options* flag for :func:`waitpid`, :func:`wait3`, :func:`wait4`, " +"and :func:`waitid` causes child processes to be reported if they have been " "continued from a job control stop since they were last reported." msgstr "" @@ -5402,15 +5414,15 @@ msgstr "" #: library/os.rst:4962 msgid "" -":func:`WIFEXITED`, :func:`WEXITSTATUS`, :func:`WIFSIGNALED`, :func:" -"`WTERMSIG`, :func:`WIFSTOPPED`, :func:`WSTOPSIG` functions." +":func:`WIFEXITED`, :func:`WEXITSTATUS`, :func:`WIFSIGNALED`, :func:`WTERMSIG`, :func:`WIFSTOPPED`, :func:`WSTOPSIG` " +"functions." msgstr "" #: library/os.rst:4970 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." +"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 "" #: library/os.rst:4976 @@ -5425,9 +5437,9 @@ msgstr "" #: library/os.rst:4986 msgid "" -"Return ``True`` if a stopped child has been resumed by delivery of :const:" -"`~signal.SIGCONT` (if the process has been continued from a job control " -"stop), otherwise return ``False``." +"Return ``True`` if a stopped child has been resumed by delivery " +"of :const:`~signal.SIGCONT` (if the process has been continued from a job " +"control stop), otherwise return ``False``." msgstr "" #: library/os.rst:4990 @@ -5532,9 +5544,9 @@ msgstr "" #: library/os.rst:5096 msgid "" -"This class represents tunable scheduling parameters used in :func:" -"`sched_setparam`, :func:`sched_setscheduler`, and :func:`sched_getparam`. It " -"is immutable." +"This class represents tunable scheduling parameters used " +"in :func:`sched_setparam`, :func:`sched_setscheduler`, " +"and :func:`sched_getparam`. It is immutable." msgstr "" #: library/os.rst:5100 @@ -5635,8 +5647,8 @@ msgstr "" 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." +"included in ``confstr_names``, an :exc:`OSError` is raised " +"with :const:`errno.EINVAL` for the error number." msgstr "" #: library/os.rst:5200 @@ -5701,24 +5713,24 @@ msgstr "" #: library/os.rst:5258 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`." +"directory. This is ``'.'`` for Windows and POSIX. Also available " +"via :mod:`os.path`." msgstr "" #: library/os.rst:5266 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`." +"directory. This is ``'..'`` for Windows and POSIX. Also available " +"via :mod:`os.path`." msgstr "" #: library/os.rst:5275 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`." +"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 "" #: library/os.rst:5285 @@ -5744,18 +5756,18 @@ msgstr "" #: library/os.rst:5309 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`." +"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 "" #: library/os.rst:5316 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." +"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 "" #: library/os.rst:5325 @@ -5766,9 +5778,9 @@ msgstr "" #: library/os.rst:5336 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." +"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 "" #: library/os.rst:5344 @@ -5798,8 +5810,8 @@ msgstr "" #: library/os.rst:5360 msgid "" "The flags argument is a bit mask that can contain zero or more of the " -"following values ORed together: :py:const:`os.GRND_RANDOM` and :py:data:" -"`GRND_NONBLOCK`." +"following values ORed together: :py:const:`os.GRND_RANDOM` " +"and :py:data:`GRND_NONBLOCK`." msgstr "" #: library/os.rst:5364 diff --git a/library/ossaudiodev.po b/library/ossaudiodev.po index bfb235fca..ae3d3cf5c 100644 --- a/library/ossaudiodev.po +++ b/library/ossaudiodev.po @@ -42,8 +42,8 @@ msgstr "" #: library/ossaudiodev.rst:54 msgid "" -"`Open Sound System Programmer's Guide `_" +"`Open Sound System Programmer's Guide `_" msgstr "" #: library/ossaudiodev.rst:55 @@ -68,10 +68,10 @@ msgstr "" #: library/ossaudiodev.rst:68 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`.)" +"(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 "" #: library/ossaudiodev.rst:72 @@ -83,11 +83,11 @@ msgstr "" #: library/ossaudiodev.rst:79 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." +"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 "" #: library/ossaudiodev.rst:85 @@ -194,10 +194,10 @@ 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." +"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 "" #: library/ossaudiodev.rst:181 @@ -315,8 +315,8 @@ msgstr "" 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`." +"devices only support :const:`AFMT_U8`; the most common format used today " +"is :const:`AFMT_S16_LE`." msgstr "" #: library/ossaudiodev.rst:238 @@ -419,8 +419,8 @@ msgid "" "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`)." +"device driver (i.e., the same as the return values " +"of :meth:`setfmt`, :meth:`channels`, and :meth:`speed`)." msgstr "" #: library/ossaudiodev.rst:311 @@ -503,11 +503,12 @@ msgstr "" #: library/ossaudiodev.rst:382 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::" +"(\"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 "" #: library/ossaudiodev.rst:389 @@ -520,18 +521,19 @@ msgstr "" #: library/ossaudiodev.rst:394 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." +"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 "" #: library/ossaudiodev.rst:402 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)." +"monophonic or not supported by the mixer (use in combination " +"with :meth:`controls` to determine which)." msgstr "" #: library/ossaudiodev.rst:407 @@ -557,8 +559,8 @@ msgstr "" #: library/ossaudiodev.rst:424 msgid "" -"Raises :exc:`OSSAudioError` if an invalid control is specified, or :exc:" -"`OSError` if an unsupported control is specified." +"Raises :exc:`OSSAudioError` if an invalid control is specified, " +"or :exc:`OSError` if an unsupported control is specified." msgstr "" #: library/ossaudiodev.rst:430 @@ -585,9 +587,9 @@ msgstr "" #: library/ossaudiodev.rst:448 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::" +"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 "" #: library/ossaudiodev.rst:453 diff --git a/library/pathlib.po b/library/pathlib.po index 6d36fea7d..49a4e0eb4 100644 --- a/library/pathlib.po +++ b/library/pathlib.po @@ -75,8 +75,8 @@ msgstr "" #: library/pathlib.rst:48 msgid "" -"For low-level path manipulation on strings, you can also use the :mod:`os." -"path` module." +"For low-level path manipulation on strings, you can also use " +"the :mod:`os.path` module." msgstr "" #: library/pathlib.rst:53 @@ -203,8 +203,8 @@ msgstr "" #: library/pathlib.rst:128 msgid "" -"If a segment is an absolute path, all previous segments are ignored (like :" -"func:`os.path.join`)::" +"If a segment is an absolute path, all previous segments are ignored " +"(like :func:`os.path.join`)::" msgstr "" #: library/pathlib.rst:131 @@ -217,8 +217,8 @@ msgstr "" #: library/pathlib.rst:136 msgid "" -"On Windows, the drive is not reset when a rooted relative path segment (e." -"g., ``r'\\foo'``) is encountered::" +"On Windows, the drive is not reset when a rooted relative path segment " +"(e.g., ``r'\\foo'``) is encountered::" msgstr "" #: library/pathlib.rst:139 @@ -367,8 +367,8 @@ msgstr "" #: library/pathlib.rst:240 msgid "" -"A path object can be used anywhere an object implementing :class:`os." -"PathLike` is accepted::" +"A path object can be used anywhere an object " +"implementing :class:`os.PathLike` is accepted::" msgstr "" #: library/pathlib.rst:243 @@ -501,8 +501,8 @@ msgstr "" #: library/pathlib.rst:332 msgid "" -"If the path starts with more than two successive slashes, :class:`~pathlib." -"PurePosixPath` collapses them::" +"If the path starts with more than two successive " +"slashes, :class:`~pathlib.PurePosixPath` collapses them::" msgstr "" #: library/pathlib.rst:335 @@ -518,8 +518,8 @@ msgstr "" #: library/pathlib.rst:344 msgid "" "This behavior conforms to *The Open Group Base Specifications Issue 6*, " -"paragraph `4.11 Pathname Resolution `_:" +"paragraph `4.11 Pathname Resolution `_:" msgstr "" #: library/pathlib.rst:348 @@ -872,8 +872,8 @@ msgstr "" msgid "" "When *walk_up* is false (the default), the path must start with *other*. " "When the argument is true, ``..`` entries may be added to form the relative " -"path. In all other cases, such as the paths referencing different drives, :" -"exc:`ValueError` is raised.::" +"path. In all other cases, such as the paths referencing different " +"drives, :exc:`ValueError` is raised.::" msgstr "" #: library/pathlib.rst:633 @@ -1100,8 +1100,8 @@ msgstr "" #: library/pathlib.rst:821 msgid "" "Return a new path with expanded ``~`` and ``~user`` constructs, as returned " -"by :meth:`os.path.expanduser`. If a home directory can't be resolved, :exc:" -"`RuntimeError` is raised." +"by :meth:`os.path.expanduser`. If a home directory can't be " +"resolved, :exc:`RuntimeError` is raised." msgstr "" #: library/pathlib.rst:827 @@ -1113,8 +1113,8 @@ msgstr "" #: library/pathlib.rst:836 msgid "" -"Return a new path object representing the current directory (as returned by :" -"func:`os.getcwd`)::" +"Return a new path object representing the current directory (as returned " +"by :func:`os.getcwd`)::" msgstr "" #: library/pathlib.rst:839 @@ -1171,8 +1171,8 @@ msgid "" "If the path doesn't exist and *strict* is ``True``, :exc:`FileNotFoundError` " "is raised. If *strict* is ``False``, the path is resolved as far as " "possible and any remainder is appended without checking whether it exists. " -"If an infinite loop is encountered along the resolution path, :exc:" -"`RuntimeError` is raised." +"If an infinite loop is encountered along the resolution " +"path, :exc:`RuntimeError` is raised." msgstr "" #: library/pathlib.rst:878 @@ -1181,8 +1181,8 @@ msgstr "" #: library/pathlib.rst:884 msgid "" -"Return the path to which the symbolic link points (as returned by :func:`os." -"readlink`)::" +"Return the path to which the symbolic link points (as returned " +"by :func:`os.readlink`)::" msgstr "" #: library/pathlib.rst:887 @@ -1199,9 +1199,7 @@ msgstr "" #: library/pathlib.rst:900 msgid "" -":meth:`~Path.exists`, :meth:`~Path.is_dir`, :meth:`~Path.is_file`, :meth:" -"`~Path.is_mount`, :meth:`~Path.is_symlink`, :meth:`~Path.is_block_device`, :" -"meth:`~Path.is_char_device`, :meth:`~Path.is_fifo`, :meth:`~Path.is_socket` " +":meth:`~Path.exists`, :meth:`~Path.is_dir`, :meth:`~Path.is_file`, :meth:`~Path.is_mount`, :meth:`~Path.is_symlink`, :meth:`~Path.is_block_device`, :meth:`~Path.is_char_device`, :meth:`~Path.is_fifo`, :meth:`~Path.is_socket` " "now return ``False`` instead of raising an exception for paths that contain " "characters unrepresentable at the OS level." msgstr "" @@ -1339,8 +1337,8 @@ msgstr "" #: library/pathlib.rst:1045 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`." +"be either a Path object, or a string. The semantics are similar " +"to :func:`os.path.samefile` and :func:`os.path.samestat`." msgstr "" #: library/pathlib.rst:1049 @@ -1483,8 +1481,8 @@ msgstr "" #: library/pathlib.rst:1177 msgid "" ">>> sorted(Path('.').glob('*.py'))\n" -"[PosixPath('pathlib.py'), PosixPath('setup.py'), PosixPath('test_pathlib." -"py')]\n" +"[PosixPath('pathlib.py'), PosixPath('setup.py'), " +"PosixPath('test_pathlib.py')]\n" ">>> sorted(Path('.').glob('*/*.py'))\n" "[PosixPath('docs/conf.py')]" msgstr "" @@ -1509,8 +1507,9 @@ msgstr "" #: library/pathlib.rst:1193 msgid "" "This method calls :meth:`Path.is_dir` on the top-level directory and " -"propagates any :exc:`OSError` exception that is raised. Subsequent :exc:" -"`OSError` exceptions from scanning directories are suppressed." +"propagates any :exc:`OSError` exception that is raised. " +"Subsequent :exc:`OSError` exceptions from scanning directories are " +"suppressed." msgstr "" #: library/pathlib.rst:1229 @@ -1541,9 +1540,9 @@ msgstr "" #: library/pathlib.rst:1218 msgid "" -"Glob the given relative *pattern* recursively. This is like calling :func:" -"`Path.glob` with \"``**/``\" added in front of the *pattern*, where " -"*patterns* are the same as for :mod:`fnmatch`::" +"Glob the given relative *pattern* recursively. This is like " +"calling :func:`Path.glob` with \"``**/``\" added in front of the *pattern*, " +"where *patterns* are the same as for :mod:`fnmatch`::" msgstr "" #: library/pathlib.rst:1222 @@ -1599,14 +1598,15 @@ msgstr "" #: library/pathlib.rst:1269 msgid "" "When *top_down* is true, the caller can modify the *dirnames* list in-place " -"(for example, using :keyword:`del` or slice assignment), and :meth:`Path." -"walk` will only recurse into the subdirectories whose names remain in " -"*dirnames*. This can be used to prune the search, or to impose a specific " -"order of visiting, or even to inform :meth:`Path.walk` about directories the " -"caller creates or renames before it resumes :meth:`Path.walk` again. " -"Modifying *dirnames* when *top_down* is false has no effect on the behavior " -"of :meth:`Path.walk` since the directories in *dirnames* have already been " -"generated by the time *dirnames* is yielded to the caller." +"(for example, using :keyword:`del` or slice assignment), " +"and :meth:`Path.walk` will only recurse into the subdirectories whose names " +"remain in *dirnames*. This can be used to prune the search, or to impose a " +"specific order of visiting, or even to inform :meth:`Path.walk` about " +"directories the caller creates or renames before it " +"resumes :meth:`Path.walk` again. Modifying *dirnames* when *top_down* is " +"false has no effect on the behavior of :meth:`Path.walk` since the " +"directories in *dirnames* have already been generated by the time *dirnames* " +"is yielded to the caller." msgstr "" #: library/pathlib.rst:1279 @@ -1630,8 +1630,9 @@ msgstr "" #: library/pathlib.rst:1292 msgid "" "Be aware that setting *follow_symlinks* to true can lead to infinite " -"recursion if a link points to a parent directory of itself. :meth:`Path." -"walk` does not keep track of the directories it has already visited." +"recursion if a link points to a parent directory of " +"itself. :meth:`Path.walk` does not keep track of the directories it has " +"already visited." msgstr "" #: library/pathlib.rst:1297 @@ -1658,8 +1659,8 @@ msgstr "" #: library/pathlib.rst:1311 msgid "" "from pathlib import Path\n" -"for root, dirs, files in Path(\"cpython/Lib/concurrent\")." -"walk(on_error=print):\n" +"for root, dirs, files in Path(\"cpython/Lib/" +"concurrent\").walk(on_error=print):\n" " print(\n" " root,\n" " \"consumes\",\n" @@ -1700,14 +1701,14 @@ msgid "" "Create a file at this given path. If *mode* is given, it is combined with " "the process's ``umask`` value to determine the file mode and access flags. " "If the file already exists, the function succeeds when *exist_ok* is true " -"(and its modification time is updated to the current time), otherwise :exc:" -"`FileExistsError` is raised." +"(and its modification time is updated to the current time), " +"otherwise :exc:`FileExistsError` is raised." msgstr "" #: library/pathlib.rst:1352 msgid "" -"The :meth:`~Path.open`, :meth:`~Path.write_text` and :meth:`~Path." -"write_bytes` methods are often used to create files." +"The :meth:`~Path.open`, :meth:`~Path.write_text` " +"and :meth:`~Path.write_bytes` methods are often used to create files." msgstr "" #: library/pathlib.rst:1358 @@ -1726,8 +1727,8 @@ msgstr "" #: library/pathlib.rst:1367 msgid "" -"If *parents* is false (the default), a missing parent raises :exc:" -"`FileNotFoundError`." +"If *parents* is false (the default), a missing parent " +"raises :exc:`FileNotFoundError`." msgstr "" #: library/pathlib.rst:1370 @@ -1792,11 +1793,11 @@ msgstr "" #: library/pathlib.rst:1423 msgid "" -"Rename this file or directory to the given *target*, and return a new :class:" -"`!Path` instance pointing to *target*. On Unix, if *target* exists and is a " -"file, it will be replaced silently if the user has permission. On Windows, " -"if *target* exists, :exc:`FileExistsError` will be raised. *target* can be " -"either a string or another path object::" +"Rename this file or directory to the given *target*, and return a " +"new :class:`!Path` instance pointing to *target*. On Unix, if *target* " +"exists and is a file, it will be replaced silently if the user has " +"permission. On Windows, if *target* exists, :exc:`FileExistsError` will be " +"raised. *target* can be either a string or another path object::" msgstr "" #: library/pathlib.rst:1429 @@ -1814,8 +1815,8 @@ msgstr "" #: library/pathlib.rst:1454 msgid "" "The target path may be absolute or relative. Relative paths are interpreted " -"relative to the current working directory, *not* the directory of the :class:" -"`!Path` object." +"relative to the current working directory, *not* the directory of " +"the :class:`!Path` object." msgstr "" #: library/pathlib.rst:1442 @@ -1830,15 +1831,15 @@ msgstr "" #: library/pathlib.rst:1450 msgid "" -"Rename this file or directory to the given *target*, and return a new :class:" -"`!Path` instance pointing to *target*. If *target* points to an existing " -"file or empty directory, it will be unconditionally replaced." +"Rename this file or directory to the given *target*, and return a " +"new :class:`!Path` instance pointing to *target*. If *target* points to an " +"existing file or empty directory, it will be unconditionally replaced." msgstr "" #: library/pathlib.rst:1464 msgid "" -"Remove this file or symbolic link. If the path points to a directory, use :" -"func:`Path.rmdir` instead." +"Remove this file or symbolic link. If the path points to a directory, " +"use :func:`Path.rmdir` instead." msgstr "" #: library/pathlib.rst:1467 @@ -1910,8 +1911,8 @@ msgstr "" #: library/pathlib.rst:1527 msgid "" -"Below is a table mapping various :mod:`os` functions to their corresponding :" -"class:`PurePath`/:class:`Path` equivalent." +"Below is a table mapping various :mod:`os` functions to their " +"corresponding :class:`PurePath`/:class:`Path` equivalent." msgstr "" #: library/pathlib.rst:1531 @@ -2185,15 +2186,15 @@ msgstr "" #: library/pathlib.rst:1572 msgid "" ":func:`os.path.expanduser` returns the path unchanged if the home directory " -"can't be resolved, whereas :meth:`Path.expanduser` raises :exc:" -"`RuntimeError`." +"can't be resolved, whereas :meth:`Path.expanduser` " +"raises :exc:`RuntimeError`." msgstr "" #: library/pathlib.rst:1575 msgid "" ":func:`os.path.abspath` removes \"``..``\" components without resolving " -"symlinks, which may change the meaning of the path, whereas :meth:`Path." -"absolute` leaves any \"``..``\" components in the path." +"symlinks, which may change the meaning of the path, " +"whereas :meth:`Path.absolute` leaves any \"``..``\" components in the path." msgstr "" #: library/pathlib.rst:1578 diff --git a/library/pdb.po b/library/pdb.po index bcf2a2714..7e1685a9d 100644 --- a/library/pdb.po +++ b/library/pdb.po @@ -36,9 +36,10 @@ msgstr "" #: 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`." +"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 "" #: library/pdb.rst:32 @@ -206,8 +207,8 @@ msgid "" "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.)" +"module :mod:`__main__` is used. (See the explanation of the built-" +"in :func:`exec` or :func:`eval` functions.)" msgstr "" #: library/pdb.rst:144 @@ -247,8 +248,8 @@ msgstr "" #: library/pdb.rst:178 msgid "" -"Enter post-mortem debugging of the traceback found in :data:`sys." -"last_traceback`." +"Enter post-mortem debugging of the traceback found " +"in :data:`sys.last_traceback`." msgstr "" #: library/pdb.rst:182 @@ -278,16 +279,16 @@ msgstr "" #: library/pdb.rst:198 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 :pdbcmd:" -"`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." +"user presses :kbd:`Ctrl-C` on the console) when you give " +"a :pdbcmd:`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 "" #: library/pdb.rst:203 msgid "" -"The *readrc* argument defaults to true and controls whether Pdb will load ." -"pdbrc files from the filesystem." +"The *readrc* argument defaults to true and controls whether Pdb will " +"load .pdbrc files from the filesystem." msgstr "" #: library/pdb.rst:206 @@ -414,8 +415,8 @@ msgstr "" #: library/pdb.rst:294 msgid "" -":file:`.pdbrc` can now contain commands that continue debugging, such as :" -"pdbcmd:`continue` or :pdbcmd:`next`. Previously, these commands had no " +":file:`.pdbrc` can now contain commands that continue debugging, such " +"as :pdbcmd:`continue` or :pdbcmd:`next`. Previously, these commands had no " "effect." msgstr "" @@ -553,13 +554,13 @@ msgstr "" #: library/pdb.rst:399 msgid "" -"Specifying any command resuming execution (currently :pdbcmd:`continue`, :" -"pdbcmd:`step`, :pdbcmd:`next`, :pdbcmd:`return`, :pdbcmd:`jump`, :pdbcmd:" -"`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." +"Specifying any command resuming execution " +"(currently :pdbcmd:`continue`, :pdbcmd:`step`, :pdbcmd:`next`, :pdbcmd:`return`, :pdbcmd:`jump`, :pdbcmd:`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 "" #: library/pdb.rst:408 @@ -621,8 +622,8 @@ msgstr "" #: library/pdb.rst:452 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." +"possible to jump into the middle of a :keyword:`for` loop or out of " +"a :keyword:`finally` clause." msgstr "" #: library/pdb.rst:458 @@ -785,8 +786,8 @@ msgstr "" #: library/pdb.rst:592 msgid "" -"As an example, here are two useful aliases (especially when placed in the :" -"file:`.pdbrc` file)::" +"As an example, here are two useful aliases (especially when placed in " +"the :file:`.pdbrc` file)::" msgstr "" #: library/pdb.rst:595 @@ -816,8 +817,8 @@ msgstr "" #: library/pdb.rst:615 msgid "" -"To set a global variable, you can prefix the assignment command with a :" -"keyword:`global` statement on the same line, e.g.:" +"To set a global variable, you can prefix the assignment command with " +"a :keyword:`global` statement on the same line, e.g.:" msgstr "" #: library/pdb.rst:618 @@ -830,8 +831,8 @@ msgstr "" msgid "" "Restart the debugged Python program. If *args* 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`." +"History, breakpoints, actions and debugger options are " +"preserved. :pdbcmd:`restart` is an alias for :pdbcmd:`run`." msgstr "" #: library/pdb.rst:633 diff --git a/library/pickle.po b/library/pickle.po index 610b63306..dd4fef07b 100644 --- a/library/pickle.po +++ b/library/pickle.po @@ -29,9 +29,9 @@ 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 " +"*\"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 "" @@ -71,8 +71,8 @@ msgstr "" 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." +"Python objects. :mod:`marshal` exists primarily to support " +"Python's :file:`.pyc` files." msgstr "" #: library/pickle.rst:57 @@ -112,14 +112,14 @@ msgstr "" #: library/pickle.rst:77 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 provided a compatible pickle protocol is " -"chosen and pickling and unpickling code deals with Python 2 to Python 3 type " -"differences if your data is crossing that unique breaking change language " -"boundary." +"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 provided a compatible pickle " +"protocol is chosen and pickling and unpickling code deals with Python 2 to " +"Python 3 type differences if your data is crossing that unique breaking " +"change language boundary." msgstr "" #: library/pickle.rst:90 @@ -154,8 +154,8 @@ 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 `);" +"introspection facilities; complex cases can be tackled by " +"implementing :ref:`specific object APIs `);" msgstr "" #: library/pickle.rst:110 @@ -225,9 +225,9 @@ msgstr "" #: library/pickle.rst:153 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 was the " -"default protocol in Python 3.0--3.7." +"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 was " +"the default protocol in Python 3.0--3.7." msgstr "" #: library/pickle.rst:157 @@ -247,9 +247,9 @@ msgstr "" #: library/pickle.rst:168 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 " +"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 " @@ -266,10 +266,10 @@ msgstr "" #: library/pickle.rst:183 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." +"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 "" #: library/pickle.rst:188 @@ -279,8 +279,9 @@ msgstr "" #: library/pickle.rst:193 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." +"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 "" #: library/pickle.rst:200 @@ -375,8 +376,8 @@ msgstr "" #: library/pickle.rst:275 msgid "" -"Common base class for the other pickling exceptions. It inherits from :exc:" -"`Exception`." +"Common base class for the other pickling exceptions. It inherits " +"from :exc:`Exception`." msgstr "" #: library/pickle.rst:280 @@ -406,8 +407,8 @@ msgstr "" #: library/pickle.rst:296 msgid "" -"The :mod:`pickle` module exports three classes, :class:`Pickler`, :class:" -"`Unpickler` and :class:`PickleBuffer`:" +"The :mod:`pickle` module exports three " +"classes, :class:`Pickler`, :class:`Unpickler` and :class:`PickleBuffer`:" msgstr "" #: library/pickle.rst:301 @@ -425,8 +426,8 @@ msgstr "" #: library/pickle.rst:308 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 " +"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 "" @@ -492,12 +493,12 @@ msgstr "" #: library/pickle.rst:358 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 " +"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." +"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 "" #: library/pickle.rst:367 @@ -509,8 +510,8 @@ msgid "" "Special reducer that can be defined in :class:`Pickler` subclasses. This " "method has priority over any reducer in the :attr:`dispatch_table`. It " "should conform to the same interface as a :meth:`~object.__reduce__` method, " -"and can optionally return :data:`NotImplemented` to fallback on :attr:" -"`dispatch_table`-registered reducers to pickle ``obj``." +"and can optionally return :data:`NotImplemented` to fallback " +"on :attr:`dispatch_table`-registered reducers to pickle ``obj``." msgstr "" #: library/pickle.rst:379 @@ -543,10 +544,10 @@ msgstr "" msgid "" "The argument *file* must have three methods, a read() method that takes an " "integer argument, a readinto() method that takes a buffer argument and a " -"readline() method that requires no arguments, as in the :class:`io." -"BufferedIOBase` interface. 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." +"readline() method that requires no arguments, as in " +"the :class:`io.BufferedIOBase` interface. 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 "" #: library/pickle.rst:408 @@ -558,9 +559,9 @@ msgid "" "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. Using ``encoding='latin1'`` is " -"required for unpickling NumPy arrays and instances of :class:`~datetime." -"datetime`, :class:`~datetime.date` and :class:`~datetime.time` pickled by " -"Python 2." +"required for unpickling NumPy arrays and instances " +"of :class:`~datetime.datetime`, :class:`~datetime.date` " +"and :class:`~datetime.time` pickled by Python 2." msgstr "" #: library/pickle.rst:419 @@ -593,8 +594,8 @@ msgstr "" #: library/pickle.rst:443 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." +"the persistent ID *pid*. If an invalid persistent ID is encountered, " +"an :exc:`UnpicklingError` should be raised." msgstr "" #: library/pickle.rst:451 @@ -608,8 +609,8 @@ msgstr "" #: library/pickle.rst:456 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." +"how they can be loaded, potentially reducing security risks. Refer " +"to :ref:`pickle-restrict` for details." msgstr "" #: library/pickle.rst:460 @@ -620,16 +621,16 @@ msgstr "" #: library/pickle.rst:464 msgid "" -"A wrapper for a buffer representing picklable data. *buffer* must be a :ref:" -"`buffer-providing ` object, such as a :term:`bytes-like " -"object` or a N-dimensional array." +"A wrapper for a buffer representing picklable data. *buffer* must be " +"a :ref:`buffer-providing ` object, such as a :term:`bytes-" +"like object` or a N-dimensional array." msgstr "" #: library/pickle.rst:468 msgid "" ":class:`PickleBuffer` is itself a buffer provider, therefore it is possible " -"to pass it to other APIs expecting a buffer-providing object, such as :class:" -"`memoryview`." +"to pass it to other APIs expecting a buffer-providing object, such " +"as :class:`memoryview`." msgstr "" #: library/pickle.rst:472 @@ -661,8 +662,8 @@ msgstr "" #: library/pickle.rst:497 msgid "" -"built-in constants (``None``, ``True``, ``False``, ``Ellipsis``, and :data:" -"`NotImplemented`);" +"built-in constants (``None``, ``True``, ``False``, ``Ellipsis``, " +"and :data:`NotImplemented`);" msgstr "" #: library/pickle.rst:500 @@ -690,8 +691,9 @@ msgstr "" #: library/pickle.rst:511 msgid "" -"instances of such classes whose the result of calling :meth:`~object." -"__getstate__` is picklable (see section :ref:`pickle-inst` for details)." +"instances of such classes whose the result of " +"calling :meth:`~object.__getstate__` is picklable (see section :ref:`pickle-" +"inst` for details)." msgstr "" #: library/pickle.rst:514 @@ -699,18 +701,18 @@ 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`." +"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 "" #: library/pickle.rst:521 msgid "" -"Note that functions (built-in and user-defined) are pickled by fully :term:" -"`qualified name`, not by value. [#]_ This means that only the function name " -"is pickled, along with the name of the containing module and classes. " -"Neither the function's code, nor any of its function attributes are " -"pickled. Thus the defining module must be importable in the unpickling " +"Note that functions (built-in and user-defined) are pickled by " +"fully :term:`qualified name`, not by value. [#]_ This means that only the " +"function name is pickled, along with the name of the containing module and " +"classes. 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 "" @@ -745,8 +747,8 @@ msgid "" "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:`~object." -"__setstate__` method." +"that suitable conversions can be made by the " +"class's :meth:`~object.__setstate__` method." msgstr "" #: library/pickle.rst:553 @@ -763,10 +765,11 @@ msgstr "" 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:`~object." -"__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::" +"via introspection. When a class instance is unpickled, " +"its :meth:`~object.__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 "" #: library/pickle.rst:567 @@ -788,12 +791,12 @@ msgstr "" #: library/pickle.rst:580 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." +"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 "" #: library/pickle.rst:588 @@ -822,8 +825,8 @@ msgstr "" #: library/pickle.rst:605 msgid "" -"Before Python 3.6, :meth:`__getnewargs__` was called instead of :meth:" -"`__getnewargs_ex__` in protocols 2 and 3." +"Before Python 3.6, :meth:`__getnewargs__` was called instead " +"of :meth:`__getnewargs_ex__` in protocols 2 and 3." msgstr "" #: library/pickle.rst:612 @@ -836,36 +839,36 @@ msgstr "" #: library/pickle.rst:617 msgid "" -"For a class that has no instance :attr:`~object.__dict__` and no :attr:" -"`~object.__slots__`, the default state is ``None``." +"For a class that has no instance :attr:`~object.__dict__` and " +"no :attr:`~object.__slots__`, the default state is ``None``." msgstr "" #: library/pickle.rst:620 msgid "" -"For a class that has an instance :attr:`~object.__dict__` and no :attr:" -"`~object.__slots__`, the default state is ``self.__dict__``." +"For a class that has an instance :attr:`~object.__dict__` and " +"no :attr:`~object.__slots__`, the default state is ``self.__dict__``." msgstr "" #: library/pickle.rst:623 msgid "" -"For a class that has an instance :attr:`~object.__dict__` and :attr:`~object." -"__slots__`, the default state is a tuple consisting of two dictionaries: " -"``self.__dict__``, and a dictionary mapping slot names to slot values. Only " -"slots that have a value are included in the latter." +"For a class that has an instance :attr:`~object.__dict__` " +"and :attr:`~object.__slots__`, the default state is a tuple consisting of " +"two dictionaries: ``self.__dict__``, and a dictionary mapping slot names to " +"slot values. Only slots that have a value are included in the latter." msgstr "" #: library/pickle.rst:629 msgid "" -"For a class that has :attr:`~object.__slots__` and no instance :attr:" -"`~object.__dict__`, the default state is a tuple whose first item is " -"``None`` and whose second item is a dictionary mapping slot names to slot " -"values described in the previous bullet." +"For a class that has :attr:`~object.__slots__` and no " +"instance :attr:`~object.__dict__`, the default state is a tuple whose first " +"item is ``None`` and whose second item is a dictionary mapping slot names to " +"slot values described in the previous bullet." msgstr "" #: library/pickle.rst:634 msgid "" -"Added the default implementation of the ``__getstate__()`` method in the :" -"class:`object` class." +"Added the default implementation of the ``__getstate__()`` method in " +"the :class:`object` class." msgstr "" #: library/pickle.rst:641 @@ -878,32 +881,32 @@ msgstr "" #: library/pickle.rst:648 msgid "" -"If :meth:`__reduce__` returns a state with value ``None`` at pickling, the :" -"meth:`__setstate__` method will not be called upon unpickling." +"If :meth:`__reduce__` returns a state with value ``None`` at pickling, " +"the :meth:`__setstate__` method will not be called upon unpickling." msgstr "" #: library/pickle.rst:652 msgid "" "Refer to the section :ref:`pickle-state` for more information about how to " -"use the methods :meth:`~object.__getstate__` and :meth:`~object." -"__setstate__`." +"use the methods :meth:`~object.__getstate__` " +"and :meth:`~object.__setstate__`." msgstr "" #: library/pickle.rst:657 msgid "" -"At unpickling time, some methods like :meth:`~object.__getattr__`, :meth:" -"`~object.__getattribute__`, or :meth:`~object.__setattr__` may be called " -"upon the instance. In case those methods rely on some internal invariant " -"being true, the type should implement :meth:`~object.__new__` to establish " -"such an invariant, as :meth:`~object.__init__` is not called when unpickling " -"an instance." +"At unpickling time, some methods " +"like :meth:`~object.__getattr__`, :meth:`~object.__getattribute__`, " +"or :meth:`~object.__setattr__` may be called upon the instance. In case " +"those methods rely on some internal invariant being true, the type should " +"implement :meth:`~object.__new__` to establish such an invariant, " +"as :meth:`~object.__init__` is not called when unpickling an instance." msgstr "" #: library/pickle.rst:666 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:`~object.__reduce__` special method. The copy protocol provides a " +"In fact, these methods are part of the copy protocol which implements " +"the :meth:`~object.__reduce__` special method. The copy protocol provides a " "unified interface for retrieving the data necessary for pickling and copying " "objects. [#]_" msgstr "" @@ -912,10 +915,11 @@ msgstr "" msgid "" "Although powerful, implementing :meth:`~object.__reduce__` directly in your " "classes is error prone. For this reason, class designers should use the " -"high-level interface (i.e., :meth:`~object.__getnewargs_ex__`, :meth:" -"`~object.__getstate__` and :meth:`~object.__setstate__`) whenever possible. " -"We will show, however, cases where using :meth:`!__reduce__` is the only " -"option or leads to more efficient pickling or both." +"high-level interface " +"(i.e., :meth:`~object.__getnewargs_ex__`, :meth:`~object.__getstate__` " +"and :meth:`~object.__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 "" #: library/pickle.rst:681 @@ -954,10 +958,10 @@ msgstr "" #: library/pickle.rst:702 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." +"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 "" #: library/pickle.rst:707 @@ -965,8 +969,8 @@ 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 :" -"ref:`append and extend methods ` with the appropriate " +"for list subclasses, but may be used by other classes as long as they " +"have :ref:`append and 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.)" @@ -985,8 +989,8 @@ msgid "" "Optionally, a callable with a ``(obj, state)`` signature. This callable " "allows the user to programmatically control the state-updating behavior of a " "specific object, instead of using ``obj``'s static :meth:`__setstate__` " -"method. If not ``None``, this callable will have priority over ``obj``'s :" -"meth:`__setstate__`." +"method. If not ``None``, this callable will have priority over " +"``obj``'s :meth:`__setstate__`." msgstr "" #: library/pickle.rst:728 @@ -997,10 +1001,11 @@ msgstr "" 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." +"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 "" #: library/pickle.rst:746 @@ -1020,8 +1025,8 @@ msgstr "" 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." +"pickler and unpickler, :meth:`~Pickler.persistent_id` " +"and :meth:`~Unpickler.persistent_load` respectively." msgstr "" #: library/pickle.rst:763 @@ -1037,9 +1042,9 @@ msgstr "" #: library/pickle.rst:770 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." +"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 "" #: library/pickle.rst:774 @@ -1111,8 +1116,8 @@ msgid "" " # Initialize and populate our database.\n" " conn = sqlite3.connect(\":memory:\")\n" " cursor = conn.cursor()\n" -" cursor.execute(\"CREATE TABLE memos(key INTEGER PRIMARY KEY, task " -"TEXT)\")\n" +" cursor.execute(\"CREATE TABLE memos(key INTEGER PRIMARY KEY, task TEXT)" +"\")\n" " tasks = (\n" " 'give food to fish',\n" " 'prepare group meeting',\n" @@ -1305,18 +1310,18 @@ msgstr "" #: library/pickle.rst:902 msgid "" -"If both the :attr:`~Pickler.dispatch_table` and :meth:`~Pickler." -"reducer_override` are defined, then :meth:`~Pickler.reducer_override` method " -"takes priority." +"If both the :attr:`~Pickler.dispatch_table` " +"and :meth:`~Pickler.reducer_override` are defined, " +"then :meth:`~Pickler.reducer_override` method takes priority." msgstr "" #: library/pickle.rst:907 msgid "" "For performance reasons, :meth:`~Pickler.reducer_override` may not be called " "for the following objects: ``None``, ``True``, ``False``, and exact " -"instances of :class:`int`, :class:`float`, :class:`bytes`, :class:`str`, :" -"class:`dict`, :class:`set`, :class:`frozenset`, :class:`list` and :class:" -"`tuple`." +"instances " +"of :class:`int`, :class:`float`, :class:`bytes`, :class:`str`, :class:`dict`, :class:`set`, :class:`frozenset`, :class:`list` " +"and :class:`tuple`." msgstr "" #: library/pickle.rst:913 @@ -1384,10 +1389,10 @@ msgstr "" #: library/pickle.rst:967 msgid "" -"The large data objects to be pickled must implement a :meth:`~object." -"__reduce_ex__` method specialized for protocol 5 and higher, which returns " -"a :class:`PickleBuffer` instance (instead of e.g. a :class:`bytes` object) " -"for any large data." +"The large data objects to be pickled must implement " +"a :meth:`~object.__reduce_ex__` method specialized for protocol 5 and " +"higher, which returns a :class:`PickleBuffer` instance (instead of e.g. " +"a :class:`bytes` object) for any large data." msgstr "" #: library/pickle.rst:972 @@ -1405,28 +1410,29 @@ msgstr "" #: library/pickle.rst:981 msgid "" -"A communications system can enable custom handling of the :class:" -"`PickleBuffer` objects generated when serializing an object graph." +"A communications system can enable custom handling of " +"the :class:`PickleBuffer` objects generated when serializing an object graph." msgstr "" #: library/pickle.rst:984 msgid "" -"On the sending side, it needs to pass a *buffer_callback* argument to :class:" -"`Pickler` (or to the :func:`dump` or :func:`dumps` function), which will be " -"called with each :class:`PickleBuffer` generated while pickling the object " -"graph. Buffers accumulated by the *buffer_callback* will not see their data " -"copied into the pickle stream, only a cheap marker will be inserted." +"On the sending side, it needs to pass a *buffer_callback* argument " +"to :class:`Pickler` (or to the :func:`dump` or :func:`dumps` function), " +"which will be called with each :class:`PickleBuffer` generated while " +"pickling the object graph. Buffers accumulated by the *buffer_callback* " +"will not see their data copied into the pickle stream, only a cheap marker " +"will be inserted." msgstr "" #: library/pickle.rst:991 msgid "" -"On the receiving side, it needs to pass a *buffers* argument to :class:" -"`Unpickler` (or to the :func:`load` or :func:`loads` function), which is an " -"iterable of the buffers which were passed to *buffer_callback*. That " -"iterable should produce buffers in the same order as they were passed to " -"*buffer_callback*. Those buffers will provide the data expected by the " -"reconstructors of the objects whose pickling produced the original :class:" -"`PickleBuffer` objects." +"On the receiving side, it needs to pass a *buffers* argument " +"to :class:`Unpickler` (or to the :func:`load` or :func:`loads` function), " +"which is an iterable of the buffers which were passed to *buffer_callback*. " +"That iterable should produce buffers in the same order as they were passed " +"to *buffer_callback*. Those buffers will provide the data expected by the " +"reconstructors of the objects whose pickling produced the " +"original :class:`PickleBuffer` objects." msgstr "" #: library/pickle.rst:999 @@ -1553,17 +1559,17 @@ msgstr "" #: library/pickle.rst:1086 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." +"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 "" #: library/pickle.rst:1092 msgid "" -"Here is an example of an unpickler allowing only few safe classes from the :" -"mod:`builtins` module to be loaded::" +"Here is an example of an unpickler allowing only few safe classes from " +"the :mod:`builtins` module to be loaded::" msgstr "" #: library/pickle.rst:1095 @@ -1729,8 +1735,8 @@ msgstr "" #: library/pickle.rst:1214 msgid "" -"The exception raised will likely be an :exc:`ImportError` or an :exc:" -"`AttributeError` but it could be something else." +"The exception raised will likely be an :exc:`ImportError` or " +"an :exc:`AttributeError` but it could be something else." msgstr "" #: library/pickle.rst:1217 diff --git a/library/pickletools.po b/library/pickletools.po index 527c723b4..fec64f586 100644 --- a/library/pickletools.po +++ b/library/pickletools.po @@ -29,9 +29,9 @@ 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." +"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 "" #: library/pickletools.rst:23 diff --git a/library/pkgutil.po b/library/pkgutil.po index 46d308af5..ae6ec86e7 100644 --- a/library/pkgutil.po +++ b/library/pkgutil.po @@ -49,20 +49,21 @@ msgstr "" #: library/pkgutil.rst:28 msgid "" "For each directory on :data:`sys.path` that has a subdirectory that matches " -"the package name, add the subdirectory to the package's :attr:`~module." -"__path__`. This is useful if one wants to distribute different parts of a " -"single logical package as multiple directories." +"the package name, add the subdirectory to the " +"package's :attr:`~module.__path__`. This is useful if one wants to " +"distribute different parts of a single logical package as multiple " +"directories." msgstr "" #: library/pkgutil.rst:34 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 skipping blank lines and ignoring comments, 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)." +"*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 skipping blank lines and ignoring comments, 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 "" #: library/pkgutil.rst:42 @@ -74,11 +75,11 @@ msgstr "" #: library/pkgutil.rst:46 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)." +"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 "" #: library/pkgutil.rst:54 @@ -87,10 +88,10 @@ msgstr "" #: library/pkgutil.rst:56 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:`importlib.machinery." -"ModuleSpec`." +"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:`importlib.machinery.ModuleSpec`." msgstr "" #: library/pkgutil.rst:82 library/pkgutil.rst:121 library/pkgutil.rst:181 @@ -119,8 +120,8 @@ msgstr "" #: library/pkgutil.rst:79 msgid "" -"The cache (or part of it) can be cleared manually if a rescan of :data:`sys." -"path_hooks` is necessary." +"The cache (or part of it) can be cleared manually if a rescan " +"of :data:`sys.path_hooks` is necessary." msgstr "" #: library/pkgutil.rst:89 @@ -177,8 +178,8 @@ msgstr "" 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`." +"for :class:`importlib.machinery.FileFinder` " +"and :class:`zipimport.zipimporter`." msgstr "" #: library/pkgutil.rst:149 @@ -198,9 +199,9 @@ msgstr "" 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." +"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 "" #: library/pkgutil.rst:166 @@ -222,12 +223,12 @@ msgstr "" #: library/pkgutil.rst:190 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 ``/``)." +"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 "" #: library/pkgutil.rst:197 @@ -251,10 +252,11 @@ msgstr "" #: library/pkgutil.rst:206 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. In particular, the :term:`loader` " -"for :term:`namespace packages ` does not support :meth:" -"`get_data `." +"which does not support :meth:`get_data " +"`, then ``None`` is returned. In " +"particular, the :term:`loader` for :term:`namespace packages ` does not support :meth:`get_data " +"`." msgstr "" #: library/pkgutil.rst:215 @@ -263,9 +265,9 @@ msgstr "" #: library/pkgutil.rst:217 msgid "" -"This functionality is used in numerous places in the standard library (see :" -"issue:`12915`) - and equivalent functionality is also in widely used third-" -"party packages such as setuptools, Django and Pyramid." +"This functionality is used in numerous places in the standard library " +"(see :issue:`12915`) - and equivalent functionality is also in widely used " +"third-party packages such as setuptools, Django and Pyramid." msgstr "" #: library/pkgutil.rst:221 diff --git a/library/platform.po b/library/platform.po index 466fa7747..f8f6a796b 100644 --- a/library/platform.po +++ b/library/platform.po @@ -208,8 +208,9 @@ msgstr "" #: library/platform.rst:167 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`." +"containing six " +"attributes: :attr:`system`, :attr:`node`, :attr:`release`, :attr:`version`, :attr:`machine`, " +"and :attr:`processor`." msgstr "" #: library/platform.rst:171 @@ -218,8 +219,9 @@ msgstr "" #: library/platform.rst:173 msgid "" -"Note: the first two attribute names differ from the names presented by :func:" -"`os.uname`, where they are named :attr:`sysname` and :attr:`nodename`." +"Note: the first two attribute names differ from the names presented " +"by :func:`os.uname`, where they are named :attr:`sysname` " +"and :attr:`nodename`." msgstr "" #: library/platform.rst:177 @@ -268,8 +270,8 @@ 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." +"also state ``'Checked'`` which means the OS version uses debugging code, " +"i.e. code that checks arguments, ranges, etc." msgstr "" #: library/platform.rst:220 diff --git a/library/plistlib.po b/library/plistlib.po index 9bdf94b26..9da6572d7 100644 --- a/library/plistlib.po +++ b/library/plistlib.po @@ -40,14 +40,14 @@ msgstr "" #: library/plistlib.rst:27 msgid "" -"To write out and to parse a plist file, use the :func:`dump` and :func:" -"`load` functions." +"To write out and to parse a plist file, use the :func:`dump` " +"and :func:`load` functions." msgstr "" #: library/plistlib.rst:30 msgid "" -"To work with plist data in bytes objects, use :func:`dumps` and :func:" -"`loads`." +"To work with plist data in bytes objects, use :func:`dumps` " +"and :func:`loads`." msgstr "" #: library/plistlib.rst:33 @@ -179,8 +179,9 @@ msgstr "" #: library/plistlib.rst:121 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." +"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 "" #: library/plistlib.rst:128 diff --git a/library/poplib.po b/library/poplib.po index b3cea5fc4..ad3181433 100644 --- a/library/poplib.po +++ b/library/poplib.po @@ -27,9 +27,9 @@ msgstr "" #: 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 " +"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 "" @@ -45,8 +45,9 @@ msgstr "" 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." +"mailserver supports IMAP, you would be better off using " +"the :class:`imaplib.IMAP4` class, as IMAP servers tend to be better " +"implemented." msgstr "" #: includes/wasm-notavail.rst:3 @@ -81,15 +82,15 @@ msgstr "" #: library/poplib.rst:48 library/poplib.rst:70 msgid "" -"All commands will raise an :ref:`auditing event ` ``poplib." -"putline`` with arguments ``self`` and ``line``, where ``line`` is the bytes " -"about to be sent to the remote host." +"All commands will raise an :ref:`auditing event ` " +"``poplib.putline`` with arguments ``self`` and ``line``, where ``line`` is " +"the bytes about to be sent to the remote host." msgstr "" #: library/poplib.rst:82 msgid "" -"If the *timeout* parameter is set to be zero, it will raise a :class:" -"`ValueError` to prevent the creation of a non-blocking socket." +"If the *timeout* parameter is set to be zero, it will raise " +"a :class:`ValueError` to prevent the creation of a non-blocking socket." msgstr "" #: library/poplib.rst:58 @@ -109,8 +110,9 @@ msgstr "" #: library/poplib.rst:77 msgid "" -"The class now supports hostname check with :attr:`ssl.SSLContext." -"check_hostname` and *Server Name Indication* (see :const:`ssl.HAS_SNI`)." +"The class now supports hostname check " +"with :attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* " +"(see :const:`ssl.HAS_SNI`)." msgstr "" #: library/poplib.rst:86 @@ -284,8 +286,9 @@ msgstr "" #: library/poplib.rst:241 msgid "" -"This method supports hostname checking via :attr:`ssl.SSLContext." -"check_hostname` and *Server Name Indication* (see :const:`ssl.HAS_SNI`)." +"This method supports hostname checking " +"via :attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* " +"(see :const:`ssl.HAS_SNI`)." msgstr "" #: library/poplib.rst:248 diff --git a/library/posix.po b/library/posix.po index 738d782d1..164c84092 100644 --- a/library/posix.po +++ b/library/posix.po @@ -33,15 +33,15 @@ msgstr "" #: library/posix.rst:18 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." +"**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 "" #: library/posix.rst:27 @@ -57,10 +57,10 @@ msgstr "" #: library/posix.rst:42 msgid "" "Several operating systems (including AIX and Solaris) provide support for " -"files that are larger than 2 GiB from a C programming model where :c:expr:" -"`int` and :c:expr:`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`." +"files that are larger than 2 GiB from a C programming model " +"where :c:expr:`int` and :c:expr:`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 "" #: library/posix.rst:48 @@ -112,8 +112,8 @@ 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`." +"variable assignments and export statements to the command string " +"for :func:`~os.system` or :func:`~os.popen`." msgstr "" #: library/posix.rst:85 @@ -123,10 +123,10 @@ msgstr "" #: library/posix.rst:90 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." +"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 "" #: library/posix.rst:16 diff --git a/library/pprint.po b/library/pprint.po index 89d580bb5..c9c4993ef 100644 --- a/library/pprint.po +++ b/library/pprint.po @@ -60,9 +60,9 @@ msgstr "" #: library/pprint.rst:41 msgid "" "Prints the formatted representation of *object*, followed by a newline. This " -"function may be used in the interactive interpreter instead of the :func:" -"`print` function for inspecting values. Tip: you can reassign ``print = " -"pprint.pp`` for use within a scope." +"function may be used in the interactive interpreter instead of " +"the :func:`print` function for inspecting values. Tip: you can reassign " +"``print = pprint.pp`` for use within a scope." msgstr "" #: library/pprint.rst:0 @@ -75,8 +75,9 @@ msgstr "" #: library/pprint.rst:49 msgid "" -"A file-like object to which the output will be written by calling its :meth:" -"`!write` method. If ``None`` (the default), :data:`sys.stdout` is used." +"A file-like object to which the output will be written by calling " +"its :meth:`!write` method. If ``None`` (the default), :data:`sys.stdout` is " +"used." msgstr "" #: library/pprint.rst:55 @@ -150,11 +151,12 @@ msgstr "" #: library/pprint.rst:140 msgid "" "Return a string representation of *object*, protected against recursion in " -"some common data structures, namely instances of :class:`dict`, :class:" -"`list` and :class:`tuple` or subclasses whose ``__repr__`` has not been " -"overridden. If the representation of object exposes a recursive entry, the " -"recursive reference will be represented as ````. The representation is not otherwise formatted." +"some common data structures, namely instances " +"of :class:`dict`, :class:`list` and :class:`tuple` or subclasses whose " +"``__repr__`` has not been overridden. If the representation of object " +"exposes a recursive entry, the recursive reference will be represented as " +"````. The representation is not " +"otherwise formatted." msgstr "" #: library/pprint.rst:153 @@ -215,9 +217,9 @@ msgstr "" 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``." +"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 "" #: library/pprint.rst:235 @@ -256,8 +258,8 @@ msgstr "" #: library/pprint.rst:264 msgid "" "To demonstrate several uses of the :func:`~pprint.pp` function and its " -"parameters, let's fetch information about a project from `PyPI `_::" +"parameters, let's fetch information about a project from `PyPI `_::" msgstr "" #: library/pprint.rst:267 diff --git a/library/profile.po b/library/profile.po index 892c42224..f6931e829 100644 --- a/library/profile.po +++ b/library/profile.po @@ -52,20 +52,21 @@ msgstr "" #: 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." +":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 "" #: 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." +"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 "" #: library/profile.rst:51 @@ -555,20 +556,21 @@ msgid "" "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." +"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 "" #: library/profile.rst:372 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." +"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 "" #: library/profile.rst:382 @@ -756,12 +758,12 @@ msgstr "" 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 ``SortKey." -"NFL`` and ``SortKey.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, ``SortKey." -"NFL`` does a numeric compare of the line numbers. In fact, " +"ascending order (alphabetical). The subtle distinction between " +"``SortKey.NFL`` and ``SortKey.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, " +"``SortKey.NFL`` does a numeric compare of the line numbers. In fact, " "``sort_stats(SortKey.NFL)`` is the same as ``sort_stats(SortKey.NAME, " "SortKey.FILENAME, SortKey.LINE)``." msgstr "" @@ -794,9 +796,10 @@ msgstr "" #: library/profile.rst:477 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`)." +"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 "" #: library/profile.rst:482 @@ -1102,8 +1105,8 @@ msgstr "" #: library/profile.rst:697 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`." +"make precise measurements of process or wall-clock time. For example, " +"see :func:`time.perf_counter`." msgstr "" #: library/profile.rst:16 diff --git a/library/py_compile.po b/library/py_compile.po index f91ff61d7..dc5eb21f8 100644 --- a/library/py_compile.po +++ b/library/py_compile.po @@ -64,9 +64,9 @@ msgid "" "The *doraise* and *quiet* arguments determine how errors are handled while " "compiling file. If *quiet* is 0 or 1, and *doraise* is false, the default " "behaviour is enabled: an error string is written to ``sys.stderr``, and the " -"function returns ``None`` instead of a path. If *doraise* is true, a :exc:" -"`PyCompileError` is raised instead. However if *quiet* is 2, no message is " -"written, and *doraise* has no effect." +"function returns ``None`` instead of a path. If *doraise* is true, " +"a :exc:`PyCompileError` is raised instead. However if *quiet* is 2, no " +"message is written, and *doraise* has no effect." msgstr "" #: library/py_compile.rst:53 @@ -81,8 +81,8 @@ msgstr "" #: library/py_compile.rst:60 msgid "" -"*optimize* controls the optimization level and is passed to the built-in :" -"func:`compile` function. The default of ``-1`` selects the optimization " +"*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 "" @@ -90,8 +90,8 @@ msgstr "" msgid "" "*invalidation_mode* should be a member of the :class:`PycInvalidationMode` " "enum and controls how the generated bytecode cache is invalidated at " -"runtime. The default is :attr:`PycInvalidationMode.CHECKED_HASH` if the :" -"envvar:`SOURCE_DATE_EPOCH` environment variable is set, otherwise the " +"runtime. The default is :attr:`PycInvalidationMode.CHECKED_HASH` if " +"the :envvar:`SOURCE_DATE_EPOCH` environment variable is set, otherwise the " "default is :attr:`PycInvalidationMode.TIMESTAMP`." msgstr "" @@ -115,8 +115,8 @@ msgstr "" msgid "" "The *invalidation_mode* parameter was added as specified in :pep:`552`. If " "the :envvar:`SOURCE_DATE_EPOCH` environment variable is set, " -"*invalidation_mode* will be forced to :attr:`PycInvalidationMode." -"CHECKED_HASH`." +"*invalidation_mode* will be forced " +"to :attr:`PycInvalidationMode.CHECKED_HASH`." msgstr "" #: library/py_compile.rst:88 diff --git a/library/pydoc.po b/library/pydoc.po index 5b9b232ca..f83232c08 100644 --- a/library/pydoc.po +++ b/library/pydoc.po @@ -38,8 +38,8 @@ msgid "" "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`)." +"the source file, or at the top of the module " +"(see :func:`inspect.getcomments`)." msgstr "" #: library/pydoc.rst:30 @@ -78,9 +78,10 @@ msgstr "" #: library/pydoc.rst:54 msgid "" "When printing output to the console, :program:`pydoc` attempts to paginate " -"the output for easier reading. If either the :envvar:`MANPAGER` or the :" -"envvar:`PAGER` environment variable is set, :program:`pydoc` will use its " -"value as a pagination program. When both are set, :envvar:`MANPAGER` is used." +"the output for easier reading. If either the :envvar:`MANPAGER` or " +"the :envvar:`PAGER` environment variable is set, :program:`pydoc` will use " +"its value as a pagination program. When both are set, :envvar:`MANPAGER` is " +"used." msgstr "" #: library/pydoc.rst:59 @@ -101,11 +102,11 @@ msgstr "" #: library/pydoc.rst:68 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:" -"`python -m 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." +"machine that will serve documentation to visiting web " +"browsers. :program:`python -m 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 "" #: library/pydoc.rst:74 @@ -136,11 +137,11 @@ msgstr "" #: library/pydoc.rst:91 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." +"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 "" #: library/pydoc.rst:98 @@ -153,8 +154,9 @@ msgstr "" #: library/pydoc.rst:104 msgid "" -":mod:`!pydoc` now uses :func:`inspect.signature` rather than :func:`inspect." -"getfullargspec` to extract signature information from callables." +":mod:`!pydoc` now uses :func:`inspect.signature` rather " +"than :func:`inspect.getfullargspec` to extract signature information from " +"callables." msgstr "" #: library/pydoc.rst:109 diff --git a/library/pyexpat.po b/library/pyexpat.po index 6b2b2721d..d48c92396 100644 --- a/library/pyexpat.po +++ b/library/pyexpat.po @@ -30,12 +30,12 @@ msgstr "" #: 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." +"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 "" #: library/pyexpat.rst:38 @@ -50,8 +50,9 @@ msgstr "" #: 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." +"The exception raised when Expat reports an error. See " +"section :ref:`expaterror-objects` for more information on interpreting Expat " +"errors." msgstr "" #: library/pyexpat.rst:52 @@ -126,10 +127,10 @@ msgstr "" #: 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." +"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 "" #: library/pyexpat.rst:115 @@ -168,15 +169,15 @@ msgstr "" 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." +"this value will be passed through as the *base* argument to " +"the :func:`ExternalEntityRefHandler`, :func:`NotationDeclHandler`, " +"and :func:`UnparsedEntityDeclHandler` functions." msgstr "" #: 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." +"Returns a string containing the base set by a previous call " +"to :meth:`SetBase`, or ``None`` if :meth:`SetBase` hasn't been called." msgstr "" #: library/pyexpat.rst:160 @@ -190,19 +191,19 @@ msgstr "" 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." +"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 "" #: 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." +"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 "" #: library/pyexpat.rst:184 @@ -211,8 +212,8 @@ msgid "" "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." +"will still be called, but the :attr:`StartDoctypeDeclHandler` " +"and :attr:`EndDoctypeDeclHandler` will not be called." msgstr "" #: library/pyexpat.rst:191 @@ -254,8 +255,8 @@ msgstr "" #: library/pyexpat.rst:220 msgid "" "Note that :meth:`SetReparseDeferralEnabled` has been backported to some " -"prior releases of CPython as a security fix. Check for availability of :" -"meth:`SetReparseDeferralEnabled` using :func:`hasattr` if used in code " +"prior releases of CPython as a security fix. Check for availability " +"of :meth:`SetReparseDeferralEnabled` using :func:`hasattr` if used in code " "running across a variety of Python versions." msgstr "" @@ -279,12 +280,12 @@ msgstr "" #: library/pyexpat.rst:248 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. Note that when it is false, data that does not contain " -"newlines may be chunked too." +"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. Note that when it is false, data that does not " +"contain newlines may be chunked too." msgstr "" #: library/pyexpat.rst:259 @@ -319,8 +320,8 @@ msgstr "" 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." +"values once a call to :meth:`Parse` or :meth:`ParseFile` has raised " +"an :exc:`xml.parsers.expat.ExpatError` exception." msgstr "" #: library/pyexpat.rst:292 @@ -329,9 +330,9 @@ msgstr "" #: library/pyexpat.rst:297 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." +"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 "" #: library/pyexpat.rst:304 @@ -366,11 +367,11 @@ msgstr "" #: library/pyexpat.rst:333 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." +"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 "" #: library/pyexpat.rst:342 @@ -424,9 +425,10 @@ msgstr "" #: library/pyexpat.rst:389 msgid "" "Called for the start of every element. *name* is a string containing the " -"element name, and *attributes* is the element attributes. If :attr:" -"`ordered_attributes` is true, this is a list (see :attr:`ordered_attributes` " -"for a full description). Otherwise it's a dictionary mapping names to values." +"element name, and *attributes* is the element attributes. " +"If :attr:`ordered_attributes` is true, this is a list " +"(see :attr:`ordered_attributes` for a full description). Otherwise it's a " +"dictionary mapping names to values." msgstr "" #: library/pyexpat.rst:398 @@ -441,20 +443,20 @@ msgstr "" msgid "" "Called for character data. This will be called for normal character data, " "CDATA marked content, and ignorable whitespace. Applications which must " -"distinguish these cases can use the :attr:`StartCdataSectionHandler`, :attr:" -"`EndCdataSectionHandler`, and :attr:`ElementDeclHandler` callbacks to " -"collect the required information. Note that the character data may be " -"chunked even if it is short and so you may receive more than one call to :" -"meth:`CharacterDataHandler`. Set the :attr:`buffer_text` instance attribute " -"to ``True`` to avoid that." +"distinguish these cases can use " +"the :attr:`StartCdataSectionHandler`, :attr:`EndCdataSectionHandler`, " +"and :attr:`ElementDeclHandler` callbacks to collect the required " +"information. Note that the character data may be chunked even if it is short " +"and so you may receive more than one call to :meth:`CharacterDataHandler`. " +"Set the :attr:`buffer_text` instance attribute to ``True`` to avoid that." msgstr "" #: library/pyexpat.rst:420 msgid "" "Called for unparsed (NDATA) entity declarations. This is only present for " -"version 1.2 of the Expat library; for more recent versions, use :attr:" -"`EntityDeclHandler` instead. (The underlying function in the Expat library " -"has been declared obsolete.)" +"version 1.2 of the Expat library; for more recent versions, " +"use :attr:`EntityDeclHandler` instead. (The underlying function in the " +"Expat library has been declared obsolete.)" msgstr "" #: library/pyexpat.rst:428 @@ -487,10 +489,10 @@ msgstr "" msgid "" "Called when the closing tag is reached for an element that contained a " "namespace declaration. This is called once for each namespace declaration " -"on the element in the reverse of the order for which the :attr:" -"`StartNamespaceDeclHandler` was called to indicate the start of each " -"namespace declaration's scope. Calls to this handler are made after the " -"corresponding :attr:`EndElementHandler` for the end of the element." +"on the element in the reverse of the order for which " +"the :attr:`StartNamespaceDeclHandler` was called to indicate the start of " +"each namespace declaration's scope. Calls to this handler are made after " +"the corresponding :attr:`EndElementHandler` for the end of the element." msgstr "" #: library/pyexpat.rst:464 @@ -501,9 +503,9 @@ msgstr "" #: library/pyexpat.rst:470 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." +"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 "" #: library/pyexpat.rst:477 @@ -550,14 +552,15 @@ msgid "" "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." +"an integer; if it returns ``0``, the parser will raise " +"an :const:`XML_ERROR_EXTERNAL_ENTITY_HANDLING` error, otherwise parsing will " +"continue." msgstr "" #: library/pyexpat.rst:520 msgid "" -"If this handler is not provided, external entities are reported by the :attr:" -"`DefaultHandler` callback, if provided." +"If this handler is not provided, external entities are reported by " +"the :attr:`DefaultHandler` callback, if provided." msgstr "" #: library/pyexpat.rst:527 @@ -570,9 +573,9 @@ msgstr "" #: library/pyexpat.rst:537 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::" +"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 "" #: library/pyexpat.rst:541 @@ -670,9 +673,9 @@ msgstr "" #: library/pyexpat.rst:621 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." +"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 "" #: library/pyexpat.rst:625 @@ -733,8 +736,8 @@ msgid "" "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}]`." +"comparing its :attr:`code` attribute " +"with :samp:`errors.codes[errors.XML_ERROR_{CONSTANT_NAME}]`." msgstr "" #: library/pyexpat.rst:704 @@ -840,8 +843,8 @@ msgstr "" #: library/pyexpat.rst:828 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``." +"declared itself to be in the XML declaration, and " +"the :attr:`NotStandaloneHandler` was set and returned ``0``." msgstr "" #: library/pyexpat.rst:841 @@ -854,8 +857,8 @@ msgstr "" #: library/pyexpat.rst:848 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`." +"changed before parsing has started. This is (currently) only raised " +"by :meth:`UseForeignDTD`." msgstr "" #: library/pyexpat.rst:855 @@ -939,8 +942,8 @@ msgstr "" 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." +"www.w3.org/TR/2006/REC-xml11-20060816/#NT-EncodingDecl and https://" +"www.iana.org/assignments/character-sets/character-sets.xhtml." msgstr "" #: library/pyexpat.rst:26 diff --git a/library/queue.po b/library/queue.po index fce9cdfea..137061259 100644 --- a/library/queue.po +++ b/library/queue.po @@ -120,14 +120,16 @@ msgstr "" #: library/queue.rst:84 msgid "" -"Exception raised when non-blocking :meth:`~Queue.get` (or :meth:`~Queue." -"get_nowait`) is called on a :class:`Queue` object which is empty." +"Exception raised when non-blocking :meth:`~Queue.get` " +"(or :meth:`~Queue.get_nowait`) is called on a :class:`Queue` object which is " +"empty." msgstr "" #: library/queue.rst:91 msgid "" -"Exception raised when non-blocking :meth:`~Queue.put` (or :meth:`~Queue." -"put_nowait`) is called on a :class:`Queue` object which is full." +"Exception raised when non-blocking :meth:`~Queue.put` " +"(or :meth:`~Queue.put_nowait`) is called on a :class:`Queue` object which is " +"full." msgstr "" #: library/queue.rst:99 @@ -136,8 +138,8 @@ msgstr "" #: library/queue.rst:101 msgid "" -"Queue objects (:class:`Queue`, :class:`LifoQueue`, or :class:" -"`PriorityQueue`) provide the public methods described below." +"Queue objects (:class:`Queue`, :class:`LifoQueue`, " +"or :class:`PriorityQueue`) provide the public methods described below." msgstr "" #: library/queue.rst:107 @@ -194,8 +196,8 @@ msgid "" "Prior to 3.0 on POSIX systems, and for all versions on Windows, if *block* " "is true and *timeout* is ``None``, this operation goes into an " "uninterruptible wait on an underlying lock. This means that no exceptions " -"can occur, and in particular a SIGINT will not trigger a :exc:" -"`KeyboardInterrupt`." +"can occur, and in particular a SIGINT will not trigger " +"a :exc:`KeyboardInterrupt`." msgstr "" #: library/queue.rst:268 @@ -211,8 +213,9 @@ msgstr "" #: library/queue.rst:169 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." +"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 "" #: library/queue.rst:173 @@ -235,10 +238,10 @@ msgstr "" #: library/queue.rst:185 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." +"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 "" #: library/queue.rst:191 @@ -312,8 +315,8 @@ msgstr "" #: library/queue.rst:252 msgid "" -"Equivalent to ``put(item, block=False)``, provided for compatibility with :" -"meth:`Queue.put_nowait`." +"Equivalent to ``put(item, block=False)``, provided for compatibility " +"with :meth:`Queue.put_nowait`." msgstr "" #: library/queue.rst:273 @@ -329,7 +332,7 @@ msgstr "" #: library/queue.rst:277 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 and also " -"support indexing." +"queues with fast atomic :meth:`~collections.deque.append` " +"and :meth:`~collections.deque.popleft` operations that do not require " +"locking and also support indexing." msgstr "" diff --git a/library/quopri.po b/library/quopri.po index 08ae6a340..3412b1652 100644 --- a/library/quopri.po +++ b/library/quopri.po @@ -48,13 +48,13 @@ msgstr "" #: 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 non-optional flag which " -"controls whether to encode embedded spaces and tabs; 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`." +"printable data to the *output* file. *input* and *output* must " +"be :term:`binary file objects `. *quotetabs*, a non-optional " +"flag which controls whether to encode embedded spaces and tabs; 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 "" #: library/quopri.rst:48 diff --git a/library/random.po b/library/random.po index d9142ed1d..9d84d779e 100644 --- a/library/random.po +++ b/library/random.po @@ -121,9 +121,9 @@ msgstr "" #: library/random.rst:77 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." +"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 "" #: library/random.rst:80 @@ -140,8 +140,9 @@ msgstr "" #: library/random.rst:87 msgid "" -"The *seed* must be one of the following types: ``None``, :class:`int`, :" -"class:`float`, :class:`str`, :class:`bytes`, or :class:`bytearray`." +"The *seed* must be one of the following types: " +"``None``, :class:`int`, :class:`float`, :class:`str`, :class:`bytes`, " +"or :class:`bytearray`." msgstr "" #: library/random.rst:94 @@ -167,8 +168,8 @@ msgstr "" #: library/random.rst:112 msgid "" -"This method should not be used for generating security tokens. Use :func:" -"`secrets.token_bytes` instead." +"This method should not be used for generating security tokens. " +"Use :func:`secrets.token_bytes` instead." msgstr "" #: library/random.rst:119 @@ -206,8 +207,8 @@ msgstr "" #: library/random.rst:140 msgid "" "Automatic conversion of non-integer types is no longer supported. Calls such " -"as ``randrange(10.0)`` and ``randrange(Fraction(10, 1))`` now raise a :exc:" -"`TypeError`." +"as ``randrange(10.0)`` and ``randrange(Fraction(10, 1))`` now raise " +"a :exc:`TypeError`." msgstr "" #: library/random.rst:147 @@ -220,8 +221,9 @@ msgstr "" msgid "" "Returns a non-negative Python integer with *k* random bits. This method is " "supplied with the Mersenne Twister 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." +"also provide it as an optional part of the API. When " +"available, :meth:`getrandbits` enables :meth:`randrange` to handle " +"arbitrarily large ranges." msgstr "" #: library/random.rst:158 @@ -275,11 +277,11 @@ msgstr "" #: library/random.rst:195 msgid "" "For a given seed, the :func:`choices` function with equal weighting " -"typically produces a different sequence than repeated calls to :func:" -"`choice`. The algorithm used by :func:`choices` uses floating-point " -"arithmetic for internal consistency and speed. The algorithm used by :func:" -"`choice` defaults to integer arithmetic with repeated selections to avoid " -"small biases from round-off error." +"typically produces a different sequence than repeated calls " +"to :func:`choice`. The algorithm used by :func:`choices` uses floating-" +"point arithmetic for internal consistency and speed. The algorithm used " +"by :func:`choice` defaults to integer arithmetic with repeated selections to " +"avoid small biases from round-off error." msgstr "" #: library/random.rst:204 @@ -372,9 +374,9 @@ msgstr "" #: library/random.rst:266 msgid "" -"`Binomial distribution `_. Return the number of successes for *n* independent trials with the " -"probability of success in each trial being *p*:" +"`Binomial distribution `_. Return the number of successes for *n* " +"independent trials with the probability of success in each trial being *p*:" msgstr "" #: library/random.rst:271 @@ -531,8 +533,8 @@ msgstr "" #: library/random.rst:409 msgid "" "Formerly the *seed* could be any hashable object. Now it is limited to: " -"``None``, :class:`int`, :class:`float`, :class:`str`, :class:`bytes`, or :" -"class:`bytearray`." +"``None``, :class:`int`, :class:`float`, :class:`str`, :class:`bytes`, " +"or :class:`bytearray`." msgstr "" #: library/random.rst:414 @@ -572,8 +574,8 @@ msgstr "" #: library/random.rst:441 msgid "" -"Override this method in subclasses to customise the :meth:`~random." -"getrandbits` behaviour of :class:`!Random` instances." +"Override this method in subclasses to customise " +"the :meth:`~random.getrandbits` behaviour of :class:`!Random` instances." msgstr "" #: library/random.rst:447 @@ -582,8 +584,8 @@ msgid "" "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." +"ignored. The :meth:`getstate` and :meth:`setstate` methods " +"raise :exc:`NotImplementedError` if called." msgstr "" #: library/random.rst:456 @@ -785,11 +787,11 @@ msgstr "" #: library/random.rst:604 msgid "" -"`Economics Simulation `_ a simulation of a marketplace by `Peter Norvig `_ that shows effective use of many of the tools and distributions " -"provided by this module (gauss, uniform, sample, betavariate, choice, " -"triangular, and randrange)." +"`Economics Simulation `_ a simulation of a marketplace by `Peter Norvig `_ that shows effective use of many of the tools and " +"distributions provided by this module (gauss, uniform, sample, betavariate, " +"choice, triangular, and randrange)." msgstr "" #: library/random.rst:611 @@ -833,8 +835,8 @@ msgid "" "def random_combination_with_replacement(iterable, r):\n" " \"Choose r elements with replacement. Order the result to match the " "iterable.\"\n" -" # Result will be in set(itertools." -"combinations_with_replacement(iterable, r)).\n" +" # Result will be in " +"set(itertools.combinations_with_replacement(iterable, r)).\n" " pool = tuple(iterable)\n" " n = len(pool)\n" " indices = sorted(random.choices(range(n), k=r))\n" @@ -904,6 +906,6 @@ msgstr "" msgid "" "`Generating Pseudo-random Floating-Point Values `_ a paper by Allen B. Downey describing " -"ways to generate more fine-grained floats than normally generated by :func:`." -"random`." +"ways to generate more fine-grained floats than normally generated " +"by :func:`.random`." msgstr "" diff --git a/library/re.po b/library/re.po index a1225c886..53a010fe0 100644 --- a/library/re.po +++ b/library/re.po @@ -32,12 +32,12 @@ msgstr "" #: library/re.rst:17 msgid "" -"Both patterns and strings to be searched can be Unicode strings (:class:" -"`str`) as well as 8-bit strings (:class:`bytes`). However, Unicode strings " -"and 8-bit strings cannot be mixed: that is, you cannot match a Unicode " -"string with a bytes 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." +"Both patterns and strings to be searched can be Unicode strings " +"(:class:`str`) as well as 8-bit strings (:class:`bytes`). However, Unicode " +"strings and 8-bit strings cannot be mixed: that is, you cannot match a " +"Unicode string with a bytes 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 "" #: library/re.rst:24 @@ -175,10 +175,10 @@ msgid "" "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." +"``'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 "" #: library/re.rst:125 @@ -368,12 +368,12 @@ msgstr "" #: library/re.rst:264 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." +"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 "" #: library/re.rst:271 @@ -549,13 +549,13 @@ msgid "" "Attempts to match ``...`` as if it was a separate regular expression, and if " "successful, continues to match the rest of the pattern following it. If the " "subsequent pattern fails to match, the stack can only be unwound to a point " -"*before* the ``(?>...)`` because once exited, the expression, known as an :" -"dfn:`atomic group`, has thrown away all stack points within itself. Thus, " -"``(?>.*).`` would never match anything because first the ``.*`` would match " -"all characters possible, then, having nothing left to match, the final ``.`` " -"would fail to match. Since there are no stack points saved in the Atomic " -"Group, and there is no stack point before it, the entire expression would " -"thus fail to match." +"*before* the ``(?>...)`` because once exited, the expression, known as " +"an :dfn:`atomic group`, has thrown away all stack points within itself. " +"Thus, ``(?>.*).`` would never match anything because first the ``.*`` would " +"match all characters possible, then, having nothing left to match, the final " +"``.`` would fail to match. Since there are no stack points saved in the " +"Atomic Group, and there is no stack point before it, the entire expression " +"would thus fail to match." msgstr "" #: library/re.rst:407 @@ -683,8 +683,8 @@ msgid "" "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:" +"will most likely want to use the :func:`search` function rather than " +"the :func:`match` function:" msgstr "" #: library/re.rst:480 @@ -777,9 +777,9 @@ msgstr "" #: library/re.rst:550 msgid "" "The default word characters in Unicode (str) patterns are Unicode " -"alphanumerics and the underscore, but this can be changed by using the :py:" -"const:`~re.ASCII` flag. Word boundaries are determined by the current locale " -"if the :py:const:`~re.LOCALE` flag is used." +"alphanumerics and the underscore, but this can be changed by using " +"the :py:const:`~re.ASCII` flag. Word boundaries are determined by the " +"current locale if the :py:const:`~re.LOCALE` flag is used." msgstr "" #: library/re.rst:558 @@ -859,10 +859,10 @@ msgstr "" #: library/re.rst:609 msgid "" -"Matches Unicode whitespace characters (as defined by :py:meth:`str." -"isspace`). This includes ``[ \\t\\n\\r\\f\\v]``, and also many other " -"characters, for example the non-breaking spaces mandated by typography rules " -"in many languages." +"Matches Unicode whitespace characters (as defined " +"by :py:meth:`str.isspace`). This includes ``[ \\t\\n\\r\\f\\v]``, and also " +"many other characters, for example the non-breaking spaces mandated by " +"typography rules in many languages." msgstr "" #: library/re.rst:613 @@ -921,8 +921,8 @@ msgstr "" #: library/re.rst:647 msgid "" "Matches any character which is not a word character. This is the opposite of " -"``\\w``. By default, matches non-underscore (``_``) characters for which :py:" -"meth:`str.isalnum` returns ``False``." +"``\\w``. By default, matches non-underscore (``_``) characters for " +"which :py:meth:`str.isalnum` returns ``False``." msgstr "" #: library/re.rst:652 @@ -1040,8 +1040,9 @@ msgstr "" msgid "" "The :py:const:`~re.U` flag still exists for backward compatibility, but is " "redundant in Python 3 since matches are Unicode by default for ``str`` " -"patterns, and Unicode matching isn't allowed for bytes patterns. :py:const:" -"`~re.UNICODE` and the inline flag ``(?u)`` are similarly redundant." +"patterns, and Unicode matching isn't allowed for bytes " +"patterns. :py:const:`~re.UNICODE` and the inline flag ``(?u)`` are similarly " +"redundant." msgstr "" #: library/re.rst:754 @@ -1070,8 +1071,8 @@ msgid "" "Note that when the Unicode patterns ``[a-z]`` or ``[A-Z]`` are used in " "combination with the :const:`IGNORECASE` flag, they will match the 52 ASCII " "letters and 4 additional non-ASCII letters: 'İ' (U+0130, Latin capital " -"letter I with dot above), 'ı' (U+0131, Latin small letter dotless i), " -"'ſ' (U+017F, Latin small letter long s) and 'K' (U+212A, Kelvin sign). If " +"letter I with dot above), 'ı' (U+0131, Latin small letter dotless i), 'ſ' " +"(U+017F, Latin small letter long s) and 'K' (U+212A, Kelvin sign). If " "the :py:const:`~re.ASCII` flag is used, only letters 'a' to 'z' and 'A' to " "'Z' are matched." msgstr "" @@ -1198,8 +1199,9 @@ msgstr "" #: library/re.rst:882 msgid "" "Compile a regular expression pattern into a :ref:`regular expression object " -"`, which can be used for matching using its :func:`~Pattern." -"match`, :func:`~Pattern.search` and other methods, described below." +"`, which can be used for matching using " +"its :func:`~Pattern.match`, :func:`~Pattern.search` and other methods, " +"described below." msgstr "" #: library/re.rst:919 library/re.rst:948 library/re.rst:1023 @@ -1237,19 +1239,19 @@ msgstr "" #: library/re.rst:906 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." +"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 "" #: library/re.rst:914 msgid "" "Scan through *string* looking for the first location where the regular " -"expression *pattern* produces a match, and return a corresponding :class:" -"`~re.Match`. 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." +"expression *pattern* produces a match, and return a " +"corresponding :class:`~re.Match`. 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 "" #: library/re.rst:926 @@ -1411,8 +1413,8 @@ msgid "" "...\n" ">>> re.sub('-{1,2}', dashrepl, 'pro----gram-files')\n" "'pro--gram files'\n" -">>> re.sub(r'\\sAND\\s', ' & ', 'Baked Beans And Spam', flags=re." -"IGNORECASE)\n" +">>> re.sub(r'\\sAND\\s', ' & ', 'Baked Beans And Spam', " +"flags=re.IGNORECASE)\n" "'Baked Beans & Spam'" msgstr "" @@ -1626,8 +1628,8 @@ msgstr "" #: library/re.rst:1279 msgid "" -"The optional *pos* and *endpos* parameters have the same meaning as for the :" -"meth:`~Pattern.search` method. ::" +"The optional *pos* and *endpos* parameters have the same meaning as for " +"the :meth:`~Pattern.search` method. ::" msgstr "" #: library/re.rst:1264 @@ -1642,8 +1644,8 @@ msgstr "" #: library/re.rst:1269 msgid "" -"If you want to locate a match anywhere in *string*, use :meth:`~Pattern." -"search` instead (see also :ref:`search-vs-match`)." +"If you want to locate a match anywhere in *string*, " +"use :meth:`~Pattern.search` instead (see also :ref:`search-vs-match`)." msgstr "" #: library/re.rst:1275 @@ -1692,9 +1694,10 @@ msgstr "" #: library/re.rst:1322 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 :py:const:`~re.UNICODE` if the pattern is a Unicode string." +"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 :py:const:`~re.UNICODE` if the pattern is a Unicode " +"string." msgstr "" #: library/re.rst:1329 @@ -1724,9 +1727,10 @@ msgstr "" #: library/re.rst:1354 msgid "" -"Match objects always have a boolean value of ``True``. Since :meth:`~Pattern." -"match` and :meth:`~Pattern.search` return ``None`` when there is no match, " -"you can test whether there was a match with a simple ``if`` statement::" +"Match objects always have a boolean value of ``True``. " +"Since :meth:`~Pattern.match` and :meth:`~Pattern.search` return ``None`` " +"when there is no match, you can test whether there was a match with a simple " +"``if`` statement::" msgstr "" #: library/re.rst:1359 @@ -1788,8 +1792,8 @@ msgstr "" 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." +"string argument is not used as a group name in the pattern, " +"an :exc:`IndexError` exception is raised." msgstr "" #: library/re.rst:1413 @@ -1925,9 +1929,9 @@ msgstr "" #: library/re.rst:1504 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." +"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 "" #: library/re.rst:1509 @@ -1951,16 +1955,17 @@ msgstr "" #: library/re.rst:1526 msgid "" -"The value of *pos* which was passed to the :meth:`~Pattern.search` or :meth:" -"`~Pattern.match` method of a :ref:`regex object `. This is the " -"index into the string at which the RE engine started looking for a match." +"The value of *pos* which was passed to the :meth:`~Pattern.search` " +"or :meth:`~Pattern.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 "" #: library/re.rst:1533 msgid "" -"The value of *endpos* which was passed to the :meth:`~Pattern.search` or :" -"meth:`~Pattern.match` method of a :ref:`regex object `. This is " -"the index into the string beyond which the RE engine will not go." +"The value of *endpos* which was passed to the :meth:`~Pattern.search` " +"or :meth:`~Pattern.match` method of a :ref:`regex object `. " +"This is the index into the string beyond which the RE engine will not go." msgstr "" #: library/re.rst:1540 @@ -1980,8 +1985,9 @@ msgstr "" #: library/re.rst:1555 msgid "" -"The :ref:`regular expression object ` whose :meth:`~Pattern." -"match` or :meth:`~Pattern.search` method produced this match instance." +"The :ref:`regular expression object ` " +"whose :meth:`~Pattern.match` or :meth:`~Pattern.search` method produced this " +"match instance." msgstr "" #: library/re.rst:1561 @@ -2058,8 +2064,8 @@ msgstr "" #: library/re.rst:1611 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::" +"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 "" #: library/re.rst:1614 @@ -2087,9 +2093,9 @@ msgstr "" #: library/re.rst:1634 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 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 "" diff --git a/library/readline.po b/library/readline.po index c3964398b..62f02e757 100644 --- a/library/readline.po +++ b/library/readline.po @@ -27,8 +27,8 @@ msgid "" "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." +"interpreter's interactive prompt and the prompts offered by the built-" +"in :func:`input` function." msgstr "" #: library/readline.rst:20 @@ -87,8 +87,8 @@ msgstr "" #: library/readline.rst:60 msgid "" -"Execute the init line provided in the *string* argument. This calls :c:func:" -"`rl_parse_and_bind` in the underlying library." +"Execute the init line provided in the *string* argument. This " +"calls :c:func:`rl_parse_and_bind` in the underlying library." msgstr "" #: library/readline.rst:66 @@ -114,8 +114,9 @@ msgstr "" #: library/readline.rst:84 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." +"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 "" #: library/readline.rst:91 @@ -142,24 +143,25 @@ msgstr "" #: library/readline.rst:110 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." +"file. The default filename is :file:`~/.history`. This " +"calls :c:func:`write_history` in the underlying library." msgstr "" #: library/readline.rst:117 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." +"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 "" #: library/readline.rst:129 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." +"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 "" #: library/readline.rst:137 @@ -275,8 +277,9 @@ msgstr "" 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." +"*text* string comes from the first parameter to " +"the :c:data:`rl_attempted_completion_function` callback of the underlying " +"library." msgstr "" #: library/readline.rst:251 @@ -287,18 +290,19 @@ msgstr "" #: library/readline.rst:256 msgid "" -"Get the type of completion being attempted. This returns the :c:data:" -"`rl_completion_type` variable in the underlying library as an integer." +"Get the type of completion being attempted. This returns " +"the :c:data:`rl_completion_type` variable in the underlying library as an " +"integer." msgstr "" #: library/readline.rst:264 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. The " -"values may be different in the same input editing scenario based on the " -"underlying C readline implementation. Ex: libedit is known to behave " -"differently than libreadline." +"the *start* and *end* arguments passed to " +"the :c:data:`rl_attempted_completion_function` callback of the underlying " +"library. The values may be different in the same input editing scenario " +"based on the underlying C readline implementation. Ex: libedit is known to " +"behave differently than libreadline." msgstr "" #: library/readline.rst:275 @@ -352,8 +356,8 @@ msgstr "" #: library/readline.rst:318 msgid "" -"This code is actually automatically run when Python is run in :ref:" -"`interactive mode ` (see :ref:`rlcompleter-config`)." +"This code is actually automatically run when Python is run " +"in :ref:`interactive mode ` (see :ref:`rlcompleter-config`)." msgstr "" #: library/readline.rst:321 diff --git a/library/reprlib.po b/library/reprlib.po index 03cc96608..dbfe5926b 100644 --- a/library/reprlib.po +++ b/library/reprlib.po @@ -76,9 +76,10 @@ msgstr "" #: library/reprlib.rst:48 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." +"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 "" #: library/reprlib.rst:56 @@ -252,10 +253,10 @@ msgstr "" #: library/reprlib.rst:224 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)``." +"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 "" #: library/reprlib.rst:234 @@ -264,8 +265,8 @@ msgstr "" #: library/reprlib.rst:236 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 " +"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 "" diff --git a/library/resource.po b/library/resource.po index e20ee6847..50187b66d 100644 --- a/library/resource.po +++ b/library/resource.po @@ -97,10 +97,10 @@ 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." +"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 "" #: library/resource.rst:78 @@ -137,9 +137,9 @@ msgstr "" #: library/resource.rst:98 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." +"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 "" #: library/resource.rst:102 @@ -257,9 +257,9 @@ msgstr "" 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 `tuning(7) `__ for a complete description of " -"this sysctl." +"the vm.overcommit sysctl is set. Please see `tuning(7) `__ for a complete " +"description of this sysctl." msgstr "" #: library/resource.rst:258 @@ -282,8 +282,8 @@ msgstr "" 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." +"parameter. The *who* parameter should be specified using one of " +"the :const:`!RUSAGE_\\*` constants described below." msgstr "" #: library/resource.rst:285 @@ -325,9 +325,9 @@ 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:" +"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 "" #: library/resource.rst:314 @@ -549,9 +549,9 @@ msgstr "" #: library/resource.rst:358 msgid "" -"The following :const:`!RUSAGE_\\*` symbols are passed to the :func:" -"`getrusage` function to specify which processes information should be " -"provided for." +"The following :const:`!RUSAGE_\\*` symbols are passed to " +"the :func:`getrusage` function to specify which processes information should " +"be provided for." msgstr "" #: library/resource.rst:364 diff --git a/library/rlcompleter.po b/library/rlcompleter.po index ca25dc79c..d10e81c44 100644 --- a/library/rlcompleter.po +++ b/library/rlcompleter.po @@ -49,20 +49,20 @@ msgid "" ">>> import readline\n" ">>> readline.parse_and_bind(\"tab: complete\")\n" ">>> readline. \n" -"readline.__doc__ readline.get_line_buffer( readline." -"read_init_file(\n" -"readline.__file__ readline.insert_text( readline." -"set_completer(\n" +"readline.__doc__ " +"readline.get_line_buffer( readline.read_init_file(\n" +"readline.__file__ " +"readline.insert_text( readline.set_completer(\n" "readline.__name__ readline.parse_and_bind(\n" ">>> readline." msgstr "" #: library/rlcompleter.rst:33 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`)." +"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 "" #: library/rlcompleter.rst:38 @@ -89,8 +89,9 @@ msgstr "" #: library/rlcompleter.rst:56 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)." +"will complete from names currently defined " +"in :mod:`__main__`, :mod:`builtins` and keywords (as defined by " +"the :mod:`keyword` module)." msgstr "" #: library/rlcompleter.rst:60 diff --git a/library/runpy.po b/library/runpy.po index cedb280b5..efa5bd944 100644 --- a/library/runpy.po +++ b/library/runpy.po @@ -87,31 +87,31 @@ msgstr "" #: 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." +"``__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 "" #: 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*)." +"(that is, ``__spec__.name`` will always be *mod_name* or ``mod_name + " +"'.__main__``, never *run_name*)." msgstr "" #: library/runpy.rst:66 msgid "" -"``__file__``, ``__cached__``, ``__loader__`` and ``__package__`` are :ref:" -"`set as normal ` based on the module spec." +"``__file__``, ``__cached__``, ``__loader__`` and ``__package__`` " +"are :ref:`set as normal ` based on the module spec." msgstr "" #: 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." +"``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 "" #: library/runpy.rst:75 @@ -141,8 +141,8 @@ msgstr "" 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``." +"well as ensuring the real module name is always accessible as " +"``__spec__.name``." msgstr "" #: library/runpy.rst:96 @@ -156,9 +156,9 @@ 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 :data:`sys.path` entry containing a :mod:" -"`__main__` module (e.g. a zipfile containing a top-level ``__main__.py`` " -"file)." +"compiled bytecode file or a valid :data:`sys.path` entry containing " +"a :mod:`__main__` module (e.g. a zipfile containing a top-level " +"``__main__.py`` file)." msgstr "" #: library/runpy.rst:113 @@ -183,8 +183,8 @@ msgstr "" #: library/runpy.rst:133 msgid "" -"``__name__`` is set to *run_name* if this optional argument is not :const:" -"`None` and to ``''`` otherwise." +"``__name__`` is set to *run_name* if this optional argument is " +"not :const:`None` and to ``''`` otherwise." msgstr "" #: library/runpy.rst:136 @@ -200,15 +200,15 @@ msgid "" "If the supplied path is a reference to a valid :data:`sys.path` entry, then " "``__spec__`` will be set appropriately for the imported :mod:`__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." +"``__file__``, ``__cached__``, ``__loader__`` and ``__package__`` will " +"be :ref:`set as normal ` based on the module spec." msgstr "" #: library/runpy.rst:147 msgid "" -"A number of alterations are also made to the :mod:`sys` module. Firstly, :" -"data:`sys.path` may be altered as described above. ``sys.argv[0]`` is " -"updated with the value of ``path_name`` and ``sys.modules[__name__]`` is " +"A number of alterations are also made to the :mod:`sys` module. " +"Firstly, :data:`sys.path` may be altered as described above. ``sys.argv[0]`` " +"is updated with the value of ``path_name`` 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." diff --git a/library/security_warnings.po b/library/security_warnings.po index ccb3abb4f..cea16cebe 100644 --- a/library/security_warnings.po +++ b/library/security_warnings.po @@ -26,8 +26,8 @@ msgstr "" #: library/security_warnings.rst:10 msgid "" -":mod:`base64`: :ref:`base64 security considerations ` in :" -"rfc:`4648`" +":mod:`base64`: :ref:`base64 security considerations ` " +"in :rfc:`4648`" msgstr "" #: library/security_warnings.rst:12 @@ -105,9 +105,9 @@ msgstr "" #: library/security_warnings.rst:36 msgid "" "The :option:`-I` command line option can be used to run Python in isolated " -"mode. When it cannot be used, the :option:`-P` option or the :envvar:" -"`PYTHONSAFEPATH` environment variable can be used to not prepend a " -"potentially unsafe path to :data:`sys.path` such as the current directory, " +"mode. When it cannot be used, the :option:`-P` option or " +"the :envvar:`PYTHONSAFEPATH` environment variable can be used to not prepend " +"a potentially unsafe path to :data:`sys.path` such as the current directory, " "the script's directory or an empty string." msgstr "" diff --git a/library/select.po b/library/select.po index c94f113c2..9a10bf1c0 100644 --- a/library/select.po +++ b/library/select.po @@ -24,11 +24,11 @@ msgstr "" 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." +"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 "" #: library/select.rst:20 @@ -72,9 +72,10 @@ msgstr "" #: library/select.rst:44 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." +"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 "" #: library/select.rst:79 library/select.rst:106 @@ -114,9 +115,9 @@ msgstr "" #: library/select.rst:75 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." +"``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 "" #: library/select.rst:81 @@ -145,14 +146,16 @@ msgstr "" #: library/select.rst:103 msgid "" -"(Only supported on BSD.) Returns a kernel queue object; see section :ref:" -"`kqueue-objects` below for the methods supported by kqueue objects." +"(Only supported on BSD.) Returns a kernel queue object; see " +"section :ref:`kqueue-objects` below for the methods supported by kqueue " +"objects." msgstr "" #: library/select.rst:114 msgid "" -"(Only supported on BSD.) Returns a kernel event object; see section :ref:" -"`kevent-objects` below for the methods supported by kevent objects." +"(Only supported on BSD.) Returns a kernel event object; see " +"section :ref:`kevent-objects` below for the methods supported by kevent " +"objects." msgstr "" #: library/select.rst:120 @@ -197,11 +200,11 @@ msgstr "" #: library/select.rst:145 msgid "" "Among the acceptable object types in the iterables 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)." +"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 "" #: library/select.rst:156 @@ -222,9 +225,10 @@ msgstr "" #: library/select.rst:170 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." +"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 "" #: library/select.rst:175 @@ -261,10 +265,10 @@ msgstr "" #: library/select.rst:390 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 " +"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 "" @@ -272,8 +276,8 @@ msgstr "" 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`." +"default value is a combination of the " +"constants :const:`POLLIN`, :const:`POLLPRI`, and :const:`POLLOUT`." msgstr "" #: library/select.rst:231 @@ -291,9 +295,9 @@ msgstr "" #: library/select.rst:434 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." +"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 "" #: library/select.rst:250 @@ -307,13 +311,14 @@ 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." +"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 "" #: library/select.rst:277 @@ -516,9 +521,10 @@ msgstr "" #: library/select.rst:396 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." +"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 "" #: library/select.rst:404 @@ -588,14 +594,14 @@ msgstr "" 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." +"was never registered causes an :exc:`OSError` exception with " +"errno :const:`ENOENT` to be raised." msgstr "" #: library/select.rst:438 msgid "" -"Attempting to remove a file descriptor that was never registered causes a :" -"exc:`KeyError` exception to be raised." +"Attempting to remove a file descriptor that was never registered causes " +"a :exc:`KeyError` exception to be raised." msgstr "" #: library/select.rst:444 @@ -603,13 +609,14 @@ 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." +"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 "" #: library/select.rst:465 diff --git a/library/selectors.po b/library/selectors.po index bdf27bfe8..fccc4d4bd 100644 --- a/library/selectors.po +++ b/library/selectors.po @@ -38,10 +38,11 @@ msgstr "" #: 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:`~io.IOBase.fileno` method, or a raw file descriptor. " +"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:`~io.IOBase.fileno` method, or a raw file descriptor. " "See :term:`file object`." msgstr "" @@ -151,11 +152,12 @@ 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." +"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 "" #: library/selectors.rst:108 @@ -171,9 +173,9 @@ msgstr "" #: library/selectors.rst:115 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." +"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 "" #: library/selectors.rst:121 @@ -188,10 +190,10 @@ msgstr "" #: library/selectors.rst:126 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)." +"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 "" #: library/selectors.rst:133 @@ -207,9 +209,9 @@ msgstr "" #: library/selectors.rst:139 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." +"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 "" #: library/selectors.rst:145 @@ -313,8 +315,8 @@ msgstr "" #: library/selectors.rst:227 msgid "" -"This returns the file descriptor used by the underlying :func:`select." -"devpoll` object." +"This returns the file descriptor used by the " +"underlying :func:`select.devpoll` object." msgstr "" #: library/selectors.rst:234 @@ -323,8 +325,8 @@ msgstr "" #: library/selectors.rst:238 msgid "" -"This returns the file descriptor used by the underlying :func:`select." -"kqueue` object." +"This returns the file descriptor used by the " +"underlying :func:`select.kqueue` object." msgstr "" #: library/selectors.rst:243 diff --git a/library/shelve.po b/library/shelve.po index 5c39263da..5bf954852 100644 --- a/library/shelve.po +++ b/library/shelve.po @@ -40,8 +40,8 @@ msgid "" "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`." +"*flag* parameter has the same interpretation as the *flag* parameter " +"of :func:`dbm.open`." msgstr "" #: library/shelve.rst:28 @@ -57,13 +57,13 @@ msgid "" "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)." +"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 "" #: library/shelve.rst:148 @@ -77,9 +77,9 @@ msgstr "" #: library/shelve.rst:53 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::" +"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 "" #: library/shelve.rst:57 @@ -205,15 +205,15 @@ msgstr "" #: library/shelve.rst:155 msgid "" -"A subclass of :class:`Shelf` which exposes :meth:`!first`, :meth:`!next`, :" -"meth:`!previous`, :meth:`!last` and :meth:`!set_location` methods. These 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." +"A subclass of :class:`Shelf` which exposes :meth:`!first`, :meth:`!" +"next`, :meth:`!previous`, :meth:`!last` and :meth:`!set_location` methods. " +"These 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 "" #: library/shelve.rst:169 @@ -221,9 +221,9 @@ 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." +"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 "" #: library/shelve.rst:180 diff --git a/library/shlex.po b/library/shlex.po index f4065c436..02ecd4f33 100644 --- a/library/shlex.po +++ b/library/shlex.po @@ -38,12 +38,12 @@ msgstr "" #: 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." +"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 "" #: library/shlex.rst:33 @@ -85,8 +85,8 @@ msgstr "" #: library/shlex.rst:69 msgid "" -"Consider using functions that pass command arguments with lists such as :" -"func:`subprocess.run` with ``shell=False``." +"Consider using functions that pass command arguments with lists such " +"as :func:`subprocess.run` with ``shell=False``." msgstr "" #: library/shlex.rst:72 @@ -109,25 +109,26 @@ msgstr "" 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. " +"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. " "*punctuation_chars* can be set only upon :class:`~shlex.shlex` instance " "creation and can't be modified later." msgstr "" @@ -202,8 +203,9 @@ msgstr "" 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." +"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 "" #: library/shlex.rst:193 @@ -258,10 +260,10 @@ msgstr "" 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 " +"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. If :attr:`whitespace_split` is set to ``True``, this will have no " "effect." @@ -299,15 +301,15 @@ msgstr "" 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. When used in combination with :" -"attr:`punctuation_chars`, tokens will be split on whitespace in addition to " -"those characters." +"tokens in a similar way to shell arguments. When used in combination " +"with :attr:`punctuation_chars`, tokens will be split on whitespace in " +"addition to those characters." msgstr "" #: library/shlex.rst:279 msgid "" -"The :attr:`punctuation_chars` attribute was made compatible with the :attr:" -"`whitespace_split` attribute." +"The :attr:`punctuation_chars` attribute was made compatible with " +"the :attr:`whitespace_split` attribute." msgstr "" #: library/shlex.rst:286 @@ -434,19 +436,20 @@ msgstr "" #: library/shlex.rst:378 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;" +"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 "" #: library/shlex.rst:382 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." +"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 "" #: library/shlex.rst:390 @@ -532,14 +535,14 @@ msgstr "" #: library/shlex.rst:450 msgid "" "However, to match the shell as closely as possible, it is recommended to " -"always use ``posix`` and :attr:`~shlex.whitespace_split` when using :attr:" -"`~shlex.punctuation_chars`, which will negate :attr:`~shlex.wordchars` " -"entirely." +"always use ``posix`` and :attr:`~shlex.whitespace_split` when " +"using :attr:`~shlex.punctuation_chars`, which will " +"negate :attr:`~shlex.wordchars` entirely." msgstr "" #: library/shlex.rst:455 msgid "" "For best effect, ``punctuation_chars`` should be set in conjunction with " -"``posix=True``. (Note that ``posix=False`` is the default for :class:`~shlex." -"shlex`.)" +"``posix=True``. (Note that ``posix=False`` is the default " +"for :class:`~shlex.shlex`.)" msgstr "" diff --git a/library/shutil.po b/library/shutil.po index e6dfca1f2..858e247a4 100644 --- a/library/shutil.po +++ b/library/shutil.po @@ -34,8 +34,8 @@ msgstr "" #: library/shutil.rst:25 msgid "" -"Even the higher-level file copying functions (:func:`shutil.copy`, :func:" -"`shutil.copy2`) cannot copy all file metadata." +"Even the higher-level file copying functions " +"(:func:`shutil.copy`, :func:`shutil.copy2`) cannot copy all file metadata." msgstr "" #: library/shutil.rst:28 @@ -129,10 +129,10 @@ msgid "" "like object>` or 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." +"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 "" #: library/shutil.rst:179 @@ -182,9 +182,9 @@ msgstr "" #: library/shutil.rst:140 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.)" +"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 "" #: library/shutil.rst:145 @@ -250,15 +250,16 @@ msgid "" "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 raises an exception because it cannot preserve file metadata." +"unavailable, :func:`copy2` will preserve all the metadata it " +"can; :func:`copy2` never raises an exception because it cannot preserve file " +"metadata." msgstr "" #: library/shutil.rst:204 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." +":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 "" #: library/shutil.rst:212 @@ -270,9 +271,9 @@ msgstr "" #: library/shutil.rst:224 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." +"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 "" #: library/shutil.rst:233 @@ -299,9 +300,9 @@ msgstr "" #: library/shutil.rst:245 msgid "" "When *symlinks* is false, if the file pointed to 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 " +"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 "" @@ -334,8 +335,8 @@ msgstr "" #: library/shutil.rst:269 msgid "" -"If *dirs_exist_ok* is false (the default) and *dst* already exists, a :exc:" -"`FileExistsError` is raised. If *dirs_exist_ok* is true, the copying " +"If *dirs_exist_ok* is false (the default) and *dst* already exists, " +"a :exc:`FileExistsError` is raised. If *dirs_exist_ok* is true, the copying " "operation will continue if it encounters existing directories, and files " "within the *dst* tree will be overwritten by corresponding files from the " "*src* tree." @@ -473,9 +474,9 @@ msgstr "" msgid "" "If *copy_function* is given, it must be a callable that takes two arguments, " "*src* and the destination, and will be used to copy *src* to the destination " -"if :func:`os.rename` cannot be used. If the source is a directory, :func:" -"`copytree` is called, passing it the *copy_function*. The default " -"*copy_function* is :func:`copy2`. Using :func:`~shutil.copy` as the " +"if :func:`os.rename` cannot be used. If the source is a " +"directory, :func:`copytree` is called, passing it the *copy_function*. The " +"default *copy_function* is :func:`copy2`. Using :func:`~shutil.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 "" @@ -557,9 +558,9 @@ msgstr "" #: library/shutil.rst:442 msgid "" "*path* is a \"``PATH`` string\" specifying the directories to look in, " -"delimited by :data:`os.pathsep`. When no *path* is specified, the :envvar:" -"`PATH` environment variable is read from :data:`os.environ`, falling back " -"to :data:`os.defpath` if it is not set." +"delimited by :data:`os.pathsep`. When no *path* is specified, " +"the :envvar:`PATH` environment variable is read from :data:`os.environ`, " +"falling back to :data:`os.defpath` if it is not set." msgstr "" #: library/shutil.rst:447 @@ -636,12 +637,12 @@ msgstr "" #: library/shutil.rst:501 msgid "" -"Starting from Python 3.8, all functions involving a file copy (:func:" -"`copyfile`, :func:`~shutil.copy`, :func:`copy2`, :func:`copytree`, and :func:" -"`move`) may use platform-specific \"fast-copy\" syscalls in order to copy " -"the file more efficiently (see :issue:`33671`). \"fast-copy\" means that the " -"copying operation occurs within the kernel, avoiding the use of userspace " -"buffers in Python as in \"``outfd.write(infd.read())``\"." +"Starting from Python 3.8, all functions involving a file copy " +"(:func:`copyfile`, :func:`~shutil.copy`, :func:`copy2`, :func:`copytree`, " +"and :func:`move`) may use platform-specific \"fast-copy\" syscalls in order " +"to copy the file more efficiently (see :issue:`33671`). \"fast-copy\" means " +"that the copying operation occurs within the kernel, avoiding the use of " +"userspace buffers in Python as in \"``outfd.write(infd.read())``\"." msgstr "" #: library/shutil.rst:509 @@ -655,15 +656,15 @@ msgstr "" #: library/shutil.rst:513 msgid "" "On Windows :func:`shutil.copyfile` uses a bigger default buffer size (1 MiB " -"instead of 64 KiB) and a :func:`memoryview`-based variant of :func:`shutil." -"copyfileobj` is used." +"instead of 64 KiB) and a :func:`memoryview`-based variant " +"of :func:`shutil.copyfileobj` is used." msgstr "" #: library/shutil.rst:517 msgid "" "If the fast-copy operation fails and no data was written in the destination " -"file then shutil will silently fallback on using less efficient :func:" -"`copyfileobj` function internally." +"file then shutil will silently fallback on using less " +"efficient :func:`copyfileobj` function internally." msgstr "" #: library/shutil.rst:526 @@ -756,8 +757,8 @@ msgstr "" msgid "" "*format* is the archive format: one of \"zip\" (if the :mod:`zlib` module is " "available), \"tar\", \"gztar\" (if the :mod:`zlib` module is available), " -"\"bztar\" (if the :mod:`bz2` module is available), or \"xztar\" (if the :mod:" -"`lzma` module is available)." +"\"bztar\" (if the :mod:`bz2` module is available), or \"xztar\" (if " +"the :mod:`lzma` module is available)." msgstr "" #: library/shutil.rst:595 @@ -809,10 +810,10 @@ msgstr "" #: library/shutil.rst:622 msgid "" -"This function is not thread-safe when custom archivers registered with :func:" -"`register_archive_format` do not support the *root_dir* argument. In this " -"case it temporarily changes the current working directory of the process to " -"*root_dir* to perform archiving." +"This function is not thread-safe when custom archivers registered " +"with :func:`register_archive_format` do not support the *root_dir* " +"argument. In this case it temporarily changes the current working directory " +"of the process to *root_dir* to perform archiving." msgstr "" #: library/shutil.rst:628 @@ -919,10 +920,11 @@ msgstr "" #: library/shutil.rst:691 msgid "" "*format* is the archive format: one of \"zip\", \"tar\", \"gztar\", " -"\"bztar\", or \"xztar\". 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." +"\"bztar\", or \"xztar\". 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 "" #: library/shutil.rst:698 @@ -960,8 +962,8 @@ msgstr "" #: library/shutil.rst:723 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." +"*extensions* is a list of extensions corresponding to the format, like " +"``.zip`` for Zip files." msgstr "" #: library/shutil.rst:727 @@ -981,8 +983,8 @@ msgstr "" #: library/shutil.rst:732 msgid "" -"possibly a *filter* keyword argument, if it was given to :func:" -"`unpack_archive`;" +"possibly a *filter* keyword argument, if it was given " +"to :func:`unpack_archive`;" msgstr "" #: library/shutil.rst:734 @@ -1084,8 +1086,8 @@ msgstr "" #: library/shutil.rst:814 msgid "" -"In the final archive, :file:`please_add.txt` should be included, but :file:" -"`do_not_add.txt` should not. Therefore we use the following::" +"In the final archive, :file:`please_add.txt` should be included, " +"but :file:`do_not_add.txt` should not. Therefore we use the following::" msgstr "" #: library/shutil.rst:817 @@ -1131,8 +1133,8 @@ msgstr "" #: library/shutil.rst:848 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`." +"terminal connected to :data:`sys.__stdout__` is queried by " +"invoking :func:`os.get_terminal_size`." msgstr "" #: library/shutil.rst:852 diff --git a/library/signal.po b/library/signal.po index a4953e6e3..0ef53f823 100644 --- a/library/signal.po +++ b/library/signal.po @@ -46,8 +46,8 @@ msgstr "" 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." +"underlying implementation), with the exception of the handler " +"for :const:`SIGCHLD`, which follows the underlying implementation." msgstr "" #: library/signal.rst:29 @@ -72,12 +72,12 @@ msgstr "" #: library/signal.rst:42 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." +"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 "" #: library/signal.rst:49 @@ -120,13 +120,13 @@ msgstr "" #: library/signal.rst:75 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 ` (:" -"class:`Signals`, :class:`Handlers` and :class:`Sigmasks` respectively). :" -"func:`getsignal`, :func:`pthread_sigmask`, :func:`sigpending` and :func:" -"`sigwait` functions return human-readable :class:`enums ` as :" -"class:`Signals` objects." +"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 ` " +"(:class:`Signals`, :class:`Handlers` and :class:`Sigmasks` " +"respectively). :func:`getsignal`, :func:`pthread_sigmask`, :func:`sigpending` " +"and :func:`sigwait` functions return human-readable :class:`enums " +"` as :class:`Signals` objects." msgstr "" #: library/signal.rst:85 @@ -140,14 +140,14 @@ msgstr "" #: library/signal.rst:95 msgid "" -":class:`enum.IntEnum` collection the constants :const:`SIG_DFL` and :const:" -"`SIG_IGN`." +":class:`enum.IntEnum` collection the constants :const:`SIG_DFL` " +"and :const:`SIG_IGN`." msgstr "" #: library/signal.rst:101 msgid "" -":class:`enum.IntEnum` collection the constants :const:`SIG_BLOCK`, :const:" -"`SIG_UNBLOCK` and :const:`SIG_SETMASK`." +":class:`enum.IntEnum` collection the " +"constants :const:`SIG_BLOCK`, :const:`SIG_UNBLOCK` and :const:`SIG_SETMASK`." msgstr "" #: library/signal.rst:136 library/signal.rst:148 library/signal.rst:160 @@ -265,8 +265,8 @@ msgstr "" #: library/signal.rst:219 msgid "" -"On architectures where the signal is available. See the man page :manpage:" -"`signal(7)` for further information." +"On architectures where the signal is available. See the man " +"page :manpage:`signal(7)` for further information." msgstr "" #: library/signal.rst:226 @@ -291,9 +291,10 @@ msgid "" "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." +"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 "" #: library/signal.rst:259 @@ -310,8 +311,8 @@ msgstr "" #: library/signal.rst:279 msgid "" -"One more than the number of the highest signal number. Use :func:" -"`valid_signals` to get valid signal numbers." +"One more than the number of the highest signal number. " +"Use :func:`valid_signals` to get valid signal numbers." msgstr "" #: library/signal.rst:285 @@ -358,16 +359,16 @@ msgstr "" #: library/signal.rst:329 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`." +"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 "" #: library/signal.rst:334 msgid "" -"This error used to be a subtype of :exc:`IOError`, which is now an alias of :" -"exc:`OSError`." +"This error used to be a subtype of :exc:`IOError`, which is now an alias " +"of :exc:`OSError`." msgstr "" #: library/signal.rst:339 @@ -392,19 +393,19 @@ msgstr "" #: library/signal.rst:358 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." +"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 "" #: library/signal.rst:369 msgid "" -"Returns the description of signal *signalnum*, such as \"Interrupt\" for :" -"const:`SIGINT`. Returns :const:`None` if *signalnum* has no description. " -"Raises :exc:`ValueError` if *signalnum* is invalid." +"Returns the description of signal *signalnum*, such as \"Interrupt\" " +"for :const:`SIGINT`. Returns :const:`None` if *signalnum* has no " +"description. Raises :exc:`ValueError` if *signalnum* is invalid." msgstr "" #: library/signal.rst:378 @@ -426,8 +427,8 @@ msgstr "" #: library/signal.rst:394 msgid "" -"See also :func:`sigwait`, :func:`sigwaitinfo`, :func:`sigtimedwait` and :" -"func:`sigpending`." +"See also :func:`sigwait`, :func:`sigwaitinfo`, :func:`sigtimedwait` " +"and :func:`sigpending`." msgstr "" #: library/signal.rst:400 @@ -517,9 +518,9 @@ msgstr "" #: library/signal.rst:462 msgid "" -"*mask* is a set of signal numbers (e.g. {:const:`signal.SIGINT`, :const:" -"`signal.SIGTERM`}). Use :func:`~signal.valid_signals` for a full mask " -"including all signals." +"*mask* is a set of signal numbers (e.g. " +"{:const:`signal.SIGINT`, :const:`signal.SIGTERM`}). " +"Use :func:`~signal.valid_signals` for a full mask including all signals." msgstr "" #: library/signal.rst:466 @@ -538,20 +539,21 @@ msgstr "" #: library/signal.rst:483 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 (if *interval* is non-zero). The " -"interval timer specified by *which* can be cleared by setting *seconds* to " -"zero." +"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 (if *interval* is non-zero). The interval timer specified " +"by *which* can be cleared by setting *seconds* to zero." msgstr "" #: library/signal.rst:490 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`." +"deliver :const:`SIGALRM`, :const:`signal.ITIMER_VIRTUAL` " +"sends :const:`SIGVTALRM`, and :const:`signal.ITIMER_PROF` will " +"deliver :const:`SIGPROF`." msgstr "" #: library/signal.rst:496 @@ -560,8 +562,8 @@ msgstr "" #: library/signal.rst:498 msgid "" -"Attempting to pass an invalid interval timer will cause an :exc:" -"`ItimerError`." +"Attempting to pass an invalid interval timer will cause " +"an :exc:`ItimerError`." msgstr "" #: library/signal.rst:506 @@ -651,9 +653,9 @@ 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)` for further " -"information.)" +"previous signal handler will be returned (see the description " +"of :func:`getsignal` above). (See the Unix man page :manpage:`signal(2)` " +"for further information.)" msgstr "" #: library/signal.rst:583 @@ -666,10 +668,10 @@ msgstr "" #: library/signal.rst:588 msgid "" -"On Windows, :func:`signal` can only be called with :const:`SIGABRT`, :const:" -"`SIGFPE`, :const:`SIGILL`, :const:`SIGINT`, :const:`SIGSEGV`, :const:" -"`SIGTERM`, or :const:`SIGBREAK`. A :exc:`ValueError` will be raised in any " -"other case. Note that not all systems define the same set of signal names; " +"On Windows, :func:`signal` can only be called " +"with :const:`SIGABRT`, :const:`SIGFPE`, :const:`SIGILL`, :const:`SIGINT`, :const:`SIGSEGV`, :const:`SIGTERM`, " +"or :const:`SIGBREAK`. 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 "" @@ -703,8 +705,9 @@ msgstr "" #: library/signal.rst:622 msgid "" -"See also :func:`pause`, :func:`pthread_sigmask`, :func:`sigpending`, :func:" -"`sigwaitinfo` and :func:`sigtimedwait`." +"See " +"also :func:`pause`, :func:`pthread_sigmask`, :func:`sigpending`, :func:`sigwaitinfo` " +"and :func:`sigtimedwait`." msgstr "" #: library/signal.rst:630 @@ -714,16 +717,16 @@ msgid "" "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*." +"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 "" #: library/signal.rst:639 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`." +"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 "" #: library/signal.rst:646 @@ -802,11 +805,11 @@ msgstr "" #: library/signal.rst:709 msgid "" -"Piping output of your program to tools like :manpage:`head(1)` will cause a :" -"const:`SIGPIPE` signal to be sent to your process when the receiver of its " -"standard output closes early. This results in an exception like :code:" -"`BrokenPipeError: [Errno 32] Broken pipe`. To handle this case, wrap your " -"entry point to catch this exception as follows::" +"Piping output of your program to tools like :manpage:`head(1)` will cause " +"a :const:`SIGPIPE` signal to be sent to your process when the receiver of " +"its standard output closes early. This results in an exception " +"like :code:`BrokenPipeError: [Errno 32] Broken pipe`. To handle this case, " +"wrap your entry point to catch this exception as follows::" msgstr "" #: library/signal.rst:715 @@ -881,9 +884,9 @@ msgstr "" #: library/signal.rst:771 msgid "" -"For many programs, especially those that merely want to exit on :exc:" -"`KeyboardInterrupt`, this is not a problem, but applications that are " -"complex or require high reliability should avoid raising exceptions from " +"For many programs, especially those that merely want to exit " +"on :exc:`KeyboardInterrupt`, this is not a problem, but applications that " +"are complex or require high reliability should avoid raising exceptions from " "signal handlers. They should also avoid catching :exc:`KeyboardInterrupt` as " "a means of gracefully shutting down. Instead, they should install their " "own :const:`SIGINT` handler. Below is an example of an HTTP server that " diff --git a/library/site.po b/library/site.po index 55919ce2c..0c164603d 100644 --- a/library/site.po +++ b/library/site.po @@ -44,8 +44,8 @@ msgstr "" #: library/site.rst:25 msgid "" -"Importing the module used to trigger paths manipulation even when using :" -"option:`-S`." +"Importing the module used to trigger paths manipulation even when " +"using :option:`-S`." msgstr "" #: library/site.rst:32 @@ -69,23 +69,23 @@ 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 \"true\" (case-insensitive), the " -"system-level prefixes will not be searched for site-packages; otherwise they " -"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 \"true\" (case-" +"insensitive), the system-level prefixes will not be searched for site-" +"packages; otherwise they will." msgstr "" #: library/site.rst:57 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." +"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 "" #: library/site.rst:67 @@ -102,12 +102,13 @@ msgstr "" #: library/site.rst:82 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::" +"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 "" #: library/site.rst:90 @@ -144,10 +145,11 @@ msgstr "" #: library/site.rst:108 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." +"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 "" #: library/site.rst:114 @@ -156,16 +158,16 @@ msgstr "" #: library/site.rst:118 msgid "" -"After these path manipulations, an attempt is made to import a module named :" -"mod:`sitecustomize`, which can perform arbitrary site-specific " +"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` or " "its subclass exception, and the exception's :attr:`~ImportError.name` " "attribute equals to ``'sitecustomize'``, 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 other exception causes a silent and perhaps " -"mysterious failure of the process." +"Windows (which is used by default to start IDLE), attempted output " +"from :mod:`sitecustomize` is ignored. Any other exception causes a silent " +"and perhaps mysterious failure of the process." msgstr "" #: library/site.rst:130 @@ -174,21 +176,21 @@ msgstr "" #: library/site.rst:134 msgid "" -"After this, an attempt is made to import a module named :mod:" -"`usercustomize`, which can perform arbitrary user-specific customizations, " -"if :data:`~site.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`. If this import fails with an :" -"exc:`ImportError` or its subclass exception, and the exception's :attr:" -"`~ImportError.name` attribute equals to ``'usercustomize'``, it is silently " -"ignored." +"After this, an attempt is made to import a module " +"named :mod:`usercustomize`, which can perform arbitrary user-specific " +"customizations, if :data:`~site.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`. If this " +"import fails with an :exc:`ImportError` or its subclass exception, and the " +"exception's :attr:`~ImportError.name` attribute equals to " +"``'usercustomize'``, it is silently ignored." msgstr "" #: library/site.rst:142 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." +"are empty, and the path manipulations are skipped; however the import " +"of :mod:`sitecustomize` and :mod:`usercustomize` is still attempted." msgstr "" #: library/site.rst:151 @@ -198,13 +200,13 @@ msgstr "" #: library/site.rst:153 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." +"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 "" #: library/site.rst:162 @@ -223,31 +225,33 @@ msgstr "" 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." +"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 "" #: library/site.rst:186 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 macOS " -"builds, :file:`~/Library/Python/{X.Y}/lib/python/site-packages` for macOS " -"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." +"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 " +"macOS builds, :file:`~/Library/Python/{X.Y}/lib/python/site-packages` for " +"macOS 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 "" #: library/site.rst:197 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 macOS non-framework builds, :file:`~/Library/Python/{X.Y}" -"` for macOS framework builds, and :file:`{%APPDATA%}\\\\Python` for " -"Windows. This value is used to compute the installation directories for " -"scripts, data files, Python modules, etc. for the :ref:`user installation " -"scheme `. See also :envvar:`PYTHONUSERBASE`." +"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 macOS non-framework builds, :file:`~/" +"Library/Python/{X.Y}` for macOS framework builds, and :file:`{%APPDATA%}\\" +"\\Python` for Windows. This value is used to compute the installation " +"directories for scripts, data files, Python modules, etc. for the :ref:`user " +"installation scheme `. See " +"also :envvar:`PYTHONUSERBASE`." msgstr "" #: library/site.rst:209 @@ -274,16 +278,17 @@ msgstr "" #: library/site.rst:232 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`." +"initialized yet, this function will also set it, " +"respecting :envvar:`PYTHONUSERBASE`." msgstr "" #: library/site.rst:241 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 :data:`USER_BASE`. To determine if the user-specific site-" -"packages was added to ``sys.path`` :data:`ENABLE_USER_SITE` should be used." +"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 :data:`USER_BASE`. To determine if the user-" +"specific site-packages was added to ``sys.path`` :data:`ENABLE_USER_SITE` " +"should be used." msgstr "" #: library/site.rst:253 @@ -304,10 +309,10 @@ msgstr "" #: library/site.rst:265 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`." +"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 "" #: library/site.rst:272 diff --git a/library/smtplib.po b/library/smtplib.po index 3b65ae630..b7a20a956 100644 --- a/library/smtplib.po +++ b/library/smtplib.po @@ -50,30 +50,32 @@ msgid "" "*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:`TimeoutError` 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." +"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:`TimeoutError` " +"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 "" #: library/smtplib.rst:44 msgid "" -"For normal use, you should only require the initialization/connect, :meth:" -"`sendmail`, and :meth:`SMTP.quit` methods. An example is included below." +"For normal use, you should only require the initialization/" +"connect, :meth:`sendmail`, and :meth:`SMTP.quit` methods. An example is " +"included below." msgstr "" #: library/smtplib.rst:48 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.::" +"like this, the SMTP ``QUIT`` command is issued automatically when " +"the :keyword:`!with` statement exits. E.g.::" msgstr "" #: library/smtplib.rst:52 @@ -88,9 +90,9 @@ msgstr "" #: library/smtplib.rst:61 msgid "" -"All commands will raise an :ref:`auditing event ` ``smtplib.SMTP." -"send`` with arguments ``self`` and ``data``, where ``data`` is the bytes " -"about to be sent to the remote host." +"All commands will raise an :ref:`auditing event ` " +"``smtplib.SMTP.send`` with arguments ``self`` and ``data``, where ``data`` " +"is the bytes about to be sent to the remote host." msgstr "" #: library/smtplib.rst:65 @@ -107,16 +109,16 @@ msgstr "" #: library/smtplib.rst:74 msgid "" -"If the *timeout* parameter is set to be zero, it will raise a :class:" -"`ValueError` to prevent the creation of a non-blocking socket." +"If the *timeout* parameter is set to be zero, it will raise " +"a :class:`ValueError` to prevent the creation of a non-blocking socket." msgstr "" #: library/smtplib.rst:81 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 " +"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, " @@ -135,14 +137,15 @@ msgstr "" #: library/smtplib.rst:98 msgid "" -"The class now supports hostname check with :attr:`ssl.SSLContext." -"check_hostname` and *Server Name Indication* (see :const:`ssl.HAS_SNI`)." +"The class now supports hostname check " +"with :attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* " +"(see :const:`ssl.HAS_SNI`)." msgstr "" #: library/smtplib.rst:103 msgid "" -"If the *timeout* parameter is set to be zero, it will raise a :class:" -"`ValueError` to prevent the creation of a non-blocking socket" +"If the *timeout* parameter is set to be zero, it will raise " +"a :class:`ValueError` to prevent the creation of a non-blocking socket" msgstr "" #: library/smtplib.rst:403 @@ -152,11 +155,11 @@ msgstr "" #: library/smtplib.rst:113 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 '/'." +"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 "" #: library/smtplib.rst:120 @@ -201,9 +204,9 @@ msgstr "" #: library/smtplib.rst:157 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." +"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 "" #: library/smtplib.rst:164 @@ -297,8 +300,8 @@ msgstr "" #: library/smtplib.rst:239 msgid "" -"If the connection to the server is lost while waiting for the reply, :exc:" -"`SMTPServerDisconnected` will be raised." +"If the connection to the server is lost while waiting for the " +"reply, :exc:`SMTPServerDisconnected` will be raised." msgstr "" #: library/smtplib.rst:245 @@ -340,9 +343,9 @@ msgid "" "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)." +"``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 "" #: library/smtplib.rst:279 @@ -485,10 +488,10 @@ msgstr "" #: library/smtplib.rst:372 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." +"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 "" #: library/smtplib.rst:378 @@ -509,8 +512,8 @@ msgstr "" #: library/smtplib.rst:393 msgid "" -"If *keyfile* and *certfile* are provided, they are used to create an :class:" -"`ssl.SSLContext`." +"If *keyfile* and *certfile* are provided, they are used to create " +"an :class:`ssl.SSLContext`." msgstr "" #: library/smtplib.rst:396 @@ -540,14 +543,16 @@ msgstr "" #: library/smtplib.rst:418 msgid "" -"The method now supports hostname check with :attr:`SSLContext." -"check_hostname` and *Server Name Indicator* (see :const:`~ssl.HAS_SNI`)." +"The method now supports hostname check " +"with :attr:`SSLContext.check_hostname` and *Server Name Indicator* " +"(see :const:`~ssl.HAS_SNI`)." msgstr "" #: library/smtplib.rst:423 msgid "" -"The error raised for lack of STARTTLS support is now the :exc:" -"`SMTPNotSupportedError` subclass instead of the base :exc:`SMTPException`." +"The error raised for lack of STARTTLS support is now " +"the :exc:`SMTPNotSupportedError` subclass instead of the " +"base :exc:`SMTPException`." msgstr "" #: library/smtplib.rst:431 @@ -673,28 +678,29 @@ msgid "" "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." +"*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 "" #: library/smtplib.rst:520 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*." +"``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 "" #: library/smtplib.rst:534 @@ -762,8 +768,8 @@ msgstr "" #: library/smtplib.rst:590 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`." +"construct an email message, which you can then send " +"via :meth:`~smtplib.SMTP.send_message`; see :ref:`email-examples`." msgstr "" #: library/smtplib.rst:11 diff --git a/library/sndhdr.po b/library/sndhdr.po index 877561e79..3d985b179 100644 --- a/library/sndhdr.po +++ b/library/sndhdr.po @@ -34,25 +34,25 @@ msgstr "" 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." +"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 "" #: library/sndhdr.rst:40 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." +"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 "" #: library/sndhdr.rst:54 @@ -171,8 +171,9 @@ msgstr "" #: library/sndhdr.rst:88 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``." +"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 "" #: library/sndhdr.rst:92 diff --git a/library/socket.po b/library/socket.po index b2165d771..4b37fb181 100644 --- a/library/socket.po +++ b/library/socket.po @@ -63,8 +63,8 @@ msgid "" "call and library interface for sockets to Python's object-oriented style: " "the :func:`~socket.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 " +"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 "" @@ -134,10 +134,10 @@ msgstr "" msgid "" "For IPv4 addresses, two special forms are accepted instead of a host " "address: ``''`` represents :const:`INADDR_ANY`, which is used to bind to all " -"interfaces, 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." +"interfaces, 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 "" #: library/socket.rst:83 @@ -460,8 +460,8 @@ msgstr "" #: library/socket.rst:272 msgid "" "Non-blocking mode is supported through :meth:`~socket.setblocking`. A " -"generalization of this based on timeouts is supported through :meth:`~socket." -"settimeout`." +"generalization of this based on timeouts is supported " +"through :meth:`~socket.settimeout`." msgstr "" #: library/socket.rst:278 @@ -487,11 +487,12 @@ msgstr "" #: library/socket.rst:296 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." +"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 "" #: library/socket.rst:317 library/socket.rst:330 @@ -515,10 +516,10 @@ msgstr "" #: library/socket.rst:324 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\"." +"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 "" #: library/socket.rst:333 @@ -531,8 +532,8 @@ msgstr "" #: library/socket.rst:340 msgid "" -"The AF_* and SOCK_* constants are now :class:`AddressFamily` and :class:" -"`SocketKind` :class:`.IntEnum` collections." +"The AF_* and SOCK_* constants are now :class:`AddressFamily` " +"and :class:`SocketKind` :class:`.IntEnum` collections." msgstr "" #: library/socket.rst:349 @@ -552,8 +553,8 @@ msgstr "" #: library/socket.rst:366 msgid "" -"These constants represent the socket types, used for the second argument to :" -"func:`~socket.socket`. More constants may be available depending on the " +"These constants represent the socket types, used for the second argument " +"to :func:`~socket.socket`. More constants may be available depending on the " "system. (Only :const:`SOCK_STREAM` and :const:`SOCK_DGRAM` appear to be " "generally useful.)" msgstr "" @@ -567,18 +568,18 @@ msgstr "" #: library/socket.rst:380 msgid "" -"`Secure File Descriptor Handling `_ for a more thorough explanation." +"`Secure File Descriptor Handling `_ for a more thorough explanation." msgstr "" #: library/socket.rst:404 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:`~socket.setsockopt` and :meth:" -"`~socket.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." +"are generally used in arguments to the :meth:`~socket.setsockopt` " +"and :meth:`~socket.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 "" #: library/socket.rst:411 @@ -760,8 +761,8 @@ msgstr "" #: library/socket.rst:657 msgid "" -"Constant to optimize CPU locality, to be used in conjunction with :data:" -"`SO_REUSEPORT`." +"Constant to optimize CPU locality, to be used in conjunction " +"with :data:`SO_REUSEPORT`." msgstr "" #: library/socket.rst:677 @@ -796,14 +797,14 @@ msgstr "" #: library/socket.rst:717 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`, :const:`AF_PACKET`, 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`, :const:`CAN_BCM`, :const:`CAN_ISOTP` or :const:" -"`CAN_J1939`." +"number. The address family should be :const:`AF_INET` (the " +"default), :const:`AF_INET6`, :const:`AF_UNIX`, :const:`AF_CAN`, :const:`AF_PACKET`, " +"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`, :const:`CAN_BCM`, :const:`CAN_ISOTP` " +"or :const:`CAN_J1939`." msgstr "" #: library/socket.rst:727 @@ -812,9 +813,9 @@ msgid "" "auto-detected from the specified file descriptor. Auto-detection can be " "overruled by calling the function with explicit *family*, *type*, or *proto* " "arguments. This only affects how Python represents e.g. the return value " -"of :meth:`socket.getpeername` but not the actual OS resource. 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`." +"of :meth:`socket.getpeername` but not the actual OS resource. " +"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 "" #: library/socket.rst:882 library/socket.rst:1483 @@ -949,21 +950,21 @@ msgstr "" msgid "" "*family* should be either :data:`AF_INET` or :data:`AF_INET6`. *backlog* is " "the queue size passed to :meth:`socket.listen`; if not specified , a default " -"reasonable value is chosen. *reuse_port* dictates whether to set the :data:" -"`SO_REUSEPORT` socket option." +"reasonable value is chosen. *reuse_port* dictates whether to set " +"the :data:`SO_REUSEPORT` socket option." msgstr "" #: library/socket.rst:836 msgid "" "If *dualstack_ipv6* is true and the platform supports it the socket will be " -"able to accept both IPv4 and IPv6 connections, else it will raise :exc:" -"`ValueError`. Most POSIX platforms and Windows are supposed to support this " -"functionality. When this functionality is enabled the address returned by :" -"meth:`socket.getpeername` when an IPv4 connection occurs will be an IPv6 " -"address represented as an IPv4-mapped IPv6 address. If *dualstack_ipv6* is " -"false it will explicitly disable this functionality on platforms that enable " -"it by default (e.g. Linux). This parameter can be used in conjunction with :" -"func:`has_dualstack_ipv6`:" +"able to accept both IPv4 and IPv6 connections, else it will " +"raise :exc:`ValueError`. Most POSIX platforms and Windows are supposed to " +"support this functionality. When this functionality is enabled the address " +"returned by :meth:`socket.getpeername` when an IPv4 connection occurs will " +"be an IPv6 address represented as an IPv4-mapped IPv6 address. If " +"*dualstack_ipv6* is false it will explicitly disable this functionality on " +"platforms that enable it by default (e.g. Linux). This parameter can be used " +"in conjunction with :func:`has_dualstack_ipv6`:" msgstr "" #: library/socket.rst:849 @@ -995,12 +996,12 @@ msgstr "" msgid "" "Duplicate the file descriptor *fd* (an integer as returned by a file " "object's :meth:`~io.IOBase.fileno` method) and build a socket object from " -"the result. Address family, socket type and protocol number are as for the :" -"func:`~socket.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 " +"the result. Address family, socket type and protocol number are as for " +"the :func:`~socket.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 "" @@ -1064,12 +1065,13 @@ msgstr "" msgid "" "In these tuples, *family*, *type*, *proto* are all integers and are meant to " "be passed to the :func:`~socket.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, flowinfo, scope_id)`` 4-tuple for :const:" -"`AF_INET6`), and is meant to be passed to the :meth:`socket.connect` method." +"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, flowinfo, scope_id)`` 4-tuple " +"for :const:`AF_INET6`), and is meant to be passed to " +"the :meth:`socket.connect` method." msgstr "" #: library/socket.rst:949 @@ -1168,8 +1170,8 @@ msgid "" "(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." +"qualified domain name, use the " +"function :func:`getfqdn`. :func:`gethostbyaddr` supports both IPv4 and IPv6." msgstr "" #: library/socket.rst:1031 @@ -1206,10 +1208,11 @@ msgstr "" #: library/socket.rst:1055 msgid "" "Translate an internet protocol name (for example, ``'icmp'``) to a constant " -"suitable for passing as the (optional) third argument to the :func:`~socket." -"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." +"suitable for passing as the (optional) third argument to " +"the :func:`~socket.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 "" #: library/socket.rst:1066 @@ -1288,9 +1291,9 @@ msgstr "" #: library/socket.rst:1133 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`." +"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 "" #: library/socket.rst:1137 @@ -1321,17 +1324,17 @@ msgstr "" 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:struct:`in_addr` (similar to :func:" -"`inet_aton`) or :c:struct:`in6_addr`." +"protocol calls for an object of type :c:struct:`in_addr` (similar " +"to :func:`inet_aton`) or :c:struct:`in6_addr`." msgstr "" #: library/socket.rst:1166 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`." +"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 "" #: library/socket.rst:1194 @@ -1349,10 +1352,11 @@ msgstr "" #: library/socket.rst:1187 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`." +"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 "" #: library/socket.rst:1209 @@ -1360,10 +1364,10 @@ 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." +"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 "" #: library/socket.rst:1712 library/socket.rst:1864 @@ -1402,8 +1406,9 @@ msgstr "" #: library/socket.rst:1257 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." +"socket module is first imported, the default is ``None``. " +"See :meth:`~socket.settimeout` for possible values and their respective " +"meanings." msgstr "" #: library/socket.rst:1265 @@ -1458,8 +1463,8 @@ msgstr "" #: library/socket.rst:1304 msgid "" -"Return a network interface index number corresponding to an interface name. :" -"exc:`OSError` if no interface with the given name exists." +"Return a network interface index number corresponding to an interface " +"name. :exc:`OSError` if no interface with the given name exists." msgstr "" #: library/socket.rst:1333 @@ -1468,15 +1473,15 @@ msgstr "" #: library/socket.rst:1321 msgid "" -"Return a network interface name corresponding to an interface index number. :" -"exc:`OSError` if no interface with the given index exists." +"Return a network interface name corresponding to an interface index " +"number. :exc:`OSError` if no interface with the given index exists." msgstr "" #: library/socket.rst:1338 msgid "" "Send the list of file descriptors *fds* over an :const:`AF_UNIX` socket " -"*sock*. The *fds* parameter is a sequence of file descriptors. Consult :meth:" -"`~socket.sendmsg` for the documentation of these parameters." +"*sock*. The *fds* parameter is a sequence of file descriptors. " +"Consult :meth:`~socket.sendmsg` for the documentation of these parameters." msgstr "" #: library/socket.rst:1358 @@ -1488,8 +1493,8 @@ msgstr "" #: library/socket.rst:1352 msgid "" "Receive up to *maxfds* file descriptors from an :const:`AF_UNIX` socket " -"*sock*. Return ``(msg, list(fds), flags, addr)``. Consult :meth:`~socket." -"recvmsg` for the documentation of these parameters." +"*sock*. Return ``(msg, list(fds), flags, addr)``. " +"Consult :meth:`~socket.recvmsg` for the documentation of these parameters." msgstr "" #: library/socket.rst:1365 @@ -1502,8 +1507,9 @@ msgstr "" #: library/socket.rst:1373 msgid "" -"Socket objects have the following methods. Except for :meth:`~socket." -"makefile`, these correspond to Unix system calls applicable to sockets." +"Socket objects have the following methods. Except " +"for :meth:`~socket.makefile`, these correspond to Unix system calls " +"applicable to sockets." msgstr "" #: library/socket.rst:1377 @@ -1529,8 +1535,8 @@ msgstr "" #: library/socket.rst:1870 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)." +"exception, the method now retries the system call instead of raising " +"an :exc:`InterruptedError` exception (see :pep:`475` for the rationale)." msgstr "" #: library/socket.rst:1402 @@ -1563,8 +1569,8 @@ msgstr "" #: library/socket.rst:1422 msgid "" -":exc:`OSError` is now raised if an error occurs when the underlying :c:func:" -"`close` call is made." +":exc:`OSError` is now raised if an error occurs when the " +"underlying :c:func:`close` call is made." msgstr "" #: library/socket.rst:1428 @@ -1585,9 +1591,9 @@ msgid "" "If the connection is interrupted by a signal, the method waits until the " "connection completes, or raise a :exc:`TimeoutError` 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)." +"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 "" #: library/socket.rst:1466 @@ -1598,8 +1604,8 @@ msgstr "" #: library/socket.rst:1448 msgid "" -"The method now waits until the connection completes instead of raising an :" -"exc:`InterruptedError` exception if the connection is interrupted by a " +"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 "" @@ -1662,15 +1668,15 @@ msgstr "" #: library/socket.rst:1526 msgid "" -"Return the value of the given socket option (see the Unix man page :manpage:" -"`getsockopt(2)`). The needed symbolic constants (:ref:`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)." +"Return the value of the given socket option (see the Unix man " +"page :manpage:`getsockopt(2)`). The needed symbolic constants (:ref:`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 "" #: library/socket.rst:1540 @@ -1685,8 +1691,8 @@ msgstr "" #: library/socket.rst:1550 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`." +"``None`` if no timeout is set. This reflects the last call " +"to :meth:`setblocking` or :meth:`settimeout`." msgstr "" #: library/socket.rst:0 @@ -1700,8 +1706,9 @@ msgstr "" #: library/socket.rst:1559 msgid "" "The :meth:`ioctl` method is a limited interface to the WSAIoctl system " -"interface. Please refer to the `Win32 documentation `_ for more information." +"interface. Please refer to the `Win32 documentation `_ for more " +"information." msgstr "" #: library/socket.rst:1564 @@ -1747,8 +1754,8 @@ msgstr "" #: library/socket.rst:1601 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." +"original socket unless all other file objects have been closed " +"and :meth:`socket.close` has been called on the socket object." msgstr "" #: library/socket.rst:1607 @@ -1763,9 +1770,9 @@ 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*. A returned empty bytes object indicates " -"that the client has disconnected. See the Unix manual page :manpage:" -"`recv(2)` for the meaning of the optional argument *flags*; it defaults to " -"zero." +"that the client has disconnected. See the Unix manual " +"page :manpage:`recv(2)` for the meaning of the optional argument *flags*; it " +"defaults to zero." msgstr "" #: library/socket.rst:1622 @@ -1787,8 +1794,8 @@ msgstr "" #: library/socket.rst:1644 msgid "" "For multicast IPv6 address, first item of *address* does not contain " -"``%scope_id`` part anymore. In order to get full IPv6 address use :func:" -"`getnameinfo`." +"``%scope_id`` part anymore. In order to get full IPv6 address " +"use :func:`getnameinfo`." msgstr "" #: library/socket.rst:1651 @@ -1823,20 +1830,21 @@ msgid "" "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:expr:`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." +"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:expr:`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 "" #: library/socket.rst:1686 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." +"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 "" #: library/socket.rst:1693 @@ -1844,8 +1852,8 @@ 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`. ::" +"conditions such as unrelated control messages being received). See " +"also :meth:`sendmsg`. ::" msgstr "" #: library/socket.rst:1699 @@ -1857,25 +1865,26 @@ msgid "" " msg, ancdata, flags, addr = sock.recvmsg(msglen, socket.CMSG_LEN(maxfds " "* fds.itemsize))\n" " for cmsg_level, cmsg_type, cmsg_data in ancdata:\n" -" if cmsg_level == socket.SOL_SOCKET and cmsg_type == socket." -"SCM_RIGHTS:\n" +" if cmsg_level == socket.SOL_SOCKET and cmsg_type == " +"socket.SCM_RIGHTS:\n" " # Append data, ignoring any truncated integers at the end.\n" -" fds.frombytes(cmsg_data[:len(cmsg_data) - (len(cmsg_data) % fds." -"itemsize)])\n" +" fds.frombytes(cmsg_data[:len(cmsg_data) - (len(cmsg_data) % " +"fds.itemsize)])\n" " return msg, list(fds)" msgstr "" #: library/socket.rst:1724 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`." +"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 "" #: library/socket.rst:1735 @@ -1969,9 +1978,9 @@ msgstr "" 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 " +"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 " @@ -1987,8 +1996,8 @@ msgstr "" #: library/socket.rst:1853 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` " +"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 "" @@ -1997,8 +2006,8 @@ msgid "" "import socket, array\n" "\n" "def send_fds(sock, msg, fds):\n" -" return sock.sendmsg([msg], [(socket.SOL_SOCKET, socket.SCM_RIGHTS, array." -"array(\"i\", fds))])" +" return sock.sendmsg([msg], [(socket.SOL_SOCKET, socket.SCM_RIGHTS, " +"array.array(\"i\", fds))])" msgstr "" #: library/socket.rst:1866 @@ -2016,16 +2025,17 @@ msgstr "" #: library/socket.rst:1886 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." +"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 "" #: library/socket.rst:1902 @@ -2055,17 +2065,17 @@ msgstr "" #: library/socket.rst:1919 msgid "" -"The method no longer applies :const:`SOCK_NONBLOCK` flag on :attr:`socket." -"type`." +"The method no longer applies :const:`SOCK_NONBLOCK` flag " +"on :attr:`socket.type`." msgstr "" #: library/socket.rst:1926 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-" +"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 "" @@ -2077,21 +2087,22 @@ msgstr "" #: library/socket.rst:1935 msgid "" -"The method no longer toggles :const:`SOCK_NONBLOCK` flag on :attr:`socket." -"type`." +"The method no longer toggles :const:`SOCK_NONBLOCK` flag " +"on :attr:`socket.type`." msgstr "" #: library/socket.rst:1948 msgid "" -"Set the value of the given socket option (see the Unix manual page :manpage:" -"`setsockopt(2)`). The needed symbolic constants are defined in this module " -"(:ref:`!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 :c:func:`setsockopt` " -"C function with ``optval=NULL`` and ``optlen=optlen``." +"Set the value of the given socket option (see the Unix manual " +"page :manpage:`setsockopt(2)`). The needed symbolic constants are defined " +"in this module (:ref:`!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 :c:func:`setsockopt` C function with ``optval=NULL`` and " +"``optlen=optlen``." msgstr "" #: library/socket.rst:1961 @@ -2100,10 +2111,10 @@ msgstr "" #: library/socket.rst:1969 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." +"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 "" #: library/socket.rst:1979 @@ -2111,16 +2122,17 @@ 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." +"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 "" #: library/socket.rst:1991 msgid "" -"Note that there are no methods :meth:`read` or :meth:`write`; use :meth:" -"`~socket.recv` and :meth:`~socket.send` without *flags* argument instead." +"Note that there are no methods :meth:`read` or :meth:`write`; " +"use :meth:`~socket.recv` and :meth:`~socket.send` without *flags* argument " +"instead." msgstr "" #: library/socket.rst:1994 @@ -2190,10 +2202,10 @@ msgstr "" 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." +"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 "" #: library/socket.rst:2053 @@ -2202,9 +2214,9 @@ msgstr "" #: library/socket.rst:2055 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:" +"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 "" #: library/socket.rst:2059 @@ -2229,13 +2241,14 @@ msgstr "" 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.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." -"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`." +"a client using it. Note that a server must perform the " +"sequence :func:`~socket.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.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 "" #: library/socket.rst:2083 @@ -2331,8 +2344,8 @@ msgid "" "HOST = 'daring.cwi.nl' # The remote host\n" "PORT = 50007 # The same port as used by the server\n" "s = None\n" -"for res in socket.getaddrinfo(HOST, PORT, socket.AF_UNSPEC, socket." -"SOCK_STREAM):\n" +"for res in socket.getaddrinfo(HOST, PORT, socket.AF_UNSPEC, " +"socket.SOCK_STREAM):\n" " af, socktype, proto, canonname, sa = res\n" " try:\n" " s = socket.socket(af, socktype, proto)\n" @@ -2468,8 +2481,8 @@ msgstr "" #: library/socket.rst:2269 msgid "" -"There is a :mod:`socket` flag to set, in order to prevent this, :const:" -"`socket.SO_REUSEADDR`::" +"There is a :mod:`socket` flag to set, in order to prevent " +"this, :const:`socket.SO_REUSEADDR`::" msgstr "" #: library/socket.rst:2272 diff --git a/library/socketserver.po b/library/socketserver.po index 3e43e15d3..32c8d071c 100644 --- a/library/socketserver.po +++ b/library/socketserver.po @@ -88,9 +88,9 @@ msgid "" "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)." +"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 "" #: library/socketserver.rst:64 @@ -101,8 +101,8 @@ msgid "" "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." +"meaning that Python will not exit until all threads created " +"by :class:`ThreadingMixIn` have exited." msgstr "" #: library/socketserver.rst:73 @@ -160,9 +160,9 @@ msgstr "" #: library/socketserver.rst:112 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." +"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 "" #: library/socketserver.rst:116 @@ -187,18 +187,18 @@ msgstr "" #: library/socketserver.rst:131 msgid "" -"For :class:`ThreadingMixIn` use daemonic threads by setting :data:" -"`ThreadingMixIn.daemon_threads ` to ``True`` to not wait " -"until threads complete." +"For :class:`ThreadingMixIn` use daemonic threads by " +"setting :data:`ThreadingMixIn.daemon_threads ` to ``True`` " +"to not wait until threads complete." msgstr "" #: library/socketserver.rst:137 msgid "" -":meth:`ForkingMixIn.server_close ` and :meth:" -"`ThreadingMixIn.server_close ` now waits until all " -"child processes and non-daemonic threads complete. Add a new :attr:" -"`ForkingMixIn.block_on_close ` class attribute to opt-in for " -"the pre-3.7 behaviour." +":meth:`ForkingMixIn.server_close ` " +"and :meth:`ThreadingMixIn.server_close ` now waits " +"until all child processes and non-daemonic threads complete. Add a " +"new :attr:`ForkingMixIn.block_on_close ` class attribute to " +"opt-in for the pre-3.7 behaviour." msgstr "" #: library/socketserver.rst:153 @@ -213,13 +213,13 @@ msgstr "" #: library/socketserver.rst:159 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`." +"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 "" #: library/socketserver.rst:167 @@ -247,8 +247,8 @@ 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." +"doing an explicit fork in the request handler " +"class :meth:`~BaseRequestHandler.handle` method." msgstr "" #: library/socketserver.rst:185 @@ -271,8 +271,8 @@ msgstr "" 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." +"done in subclasses. The two parameters are stored in the " +"respective :attr:`server_address` and :attr:`RequestHandlerClass` attributes." msgstr "" #: library/socketserver.rst:210 @@ -285,12 +285,13 @@ msgstr "" #: library/socketserver.rst:217 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." +"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 "" #: library/socketserver.rst:229 @@ -316,9 +317,9 @@ msgstr "" #: library/socketserver.rst:251 msgid "" -"Tell the :meth:`serve_forever` loop to stop and wait until it does. :meth:" -"`shutdown` must be called while :meth:`serve_forever` is running in a " -"different thread otherwise it will deadlock." +"Tell the :meth:`serve_forever` loop to stop and wait until it " +"does. :meth:`shutdown` must be called while :meth:`serve_forever` is running " +"in a different thread otherwise it will deadlock." msgstr "" #: library/socketserver.rst:258 @@ -340,9 +341,9 @@ msgstr "" #: library/socketserver.rst:275 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: " +"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 "" @@ -357,8 +358,8 @@ msgstr "" #: library/socketserver.rst:293 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." +"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 "" #: library/socketserver.rst:299 @@ -372,8 +373,8 @@ msgstr "" #: library/socketserver.rst:308 msgid "" -"The type of socket used by the server; :const:`socket.SOCK_STREAM` and :" -"const:`socket.SOCK_DGRAM` are two common values." +"The type of socket used by the server; :const:`socket.SOCK_STREAM` " +"and :const:`socket.SOCK_DGRAM` are two common values." msgstr "" #: library/socketserver.rst:314 @@ -426,10 +427,10 @@ msgstr "" #: library/socketserver.rst:362 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." +"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 "" #: library/socketserver.rst:374 @@ -482,8 +483,8 @@ 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:`request`; the client " -"address as :attr:`client_address`; and the server instance as :attr:" -"`server`, in case it needs access to per-server information." +"address as :attr:`client_address`; and the server instance " +"as :attr:`server`, in case it needs access to per-server information." msgstr "" #: library/socketserver.rst:424 @@ -516,21 +517,21 @@ msgstr "" #: library/socketserver.rst:455 msgid "" -"These :class:`BaseRequestHandler` subclasses override the :meth:" -"`~BaseRequestHandler.setup` and :meth:`~BaseRequestHandler.finish` methods, " -"and provide :attr:`rfile` and :attr:`wfile` attributes." +"These :class:`BaseRequestHandler` subclasses override " +"the :meth:`~BaseRequestHandler.setup` and :meth:`~BaseRequestHandler.finish` " +"methods, and provide :attr:`rfile` and :attr:`wfile` attributes." msgstr "" #: library/socketserver.rst:461 msgid "" -"A file object from which receives the request is read. Support the :class:" -"`io.BufferedIOBase` readable interface." +"A file object from which receives the request is read. Support " +"the :class:`io.BufferedIOBase` readable interface." msgstr "" #: library/socketserver.rst:466 msgid "" -"A file object to which the reply is written. Support the :class:`io." -"BufferedIOBase` writable interface" +"A file object to which the reply is written. Support " +"the :class:`io.BufferedIOBase` writable interface" msgstr "" #: library/socketserver.rst:470 @@ -730,8 +731,8 @@ msgstr "" #: library/socketserver.rst:630 msgid "" -"To build asynchronous handlers, use the :class:`ThreadingMixIn` and :class:" -"`ForkingMixIn` classes." +"To build asynchronous handlers, use the :class:`ThreadingMixIn` " +"and :class:`ForkingMixIn` classes." msgstr "" #: library/socketserver.rst:633 @@ -752,8 +753,8 @@ msgid "" " response = bytes(\"{}: {}\".format(cur_thread.name, data), 'ascii')\n" " self.request.sendall(response)\n" "\n" -"class ThreadedTCPServer(socketserver.ThreadingMixIn, socketserver." -"TCPServer):\n" +"class ThreadedTCPServer(socketserver.ThreadingMixIn, " +"socketserver.TCPServer):\n" " pass\n" "\n" "def client(ip, port, message):\n" diff --git a/library/spwd.po b/library/spwd.po index 9880be176..0823bc0d1 100644 --- a/library/spwd.po +++ b/library/spwd.po @@ -178,8 +178,8 @@ msgstr "" #: library/spwd.rst:55 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." +"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 "" #: library/spwd.rst:58 diff --git a/library/sqlite3.po b/library/sqlite3.po index 855bd328d..abac79b16 100644 --- a/library/sqlite3.po +++ b/library/sqlite3.po @@ -37,8 +37,8 @@ msgstr "" #: library/sqlite3.rst:32 msgid "" "The :mod:`!sqlite3` module was written by Gerhard Häring. It provides an " -"SQL interface compliant with the DB-API 2.0 specification described by :pep:" -"`249`, and requires SQLite 3.7.15 or newer." +"SQL interface compliant with the DB-API 2.0 specification described " +"by :pep:`249`, and requires SQLite 3.7.15 or newer." msgstr "" #: library/sqlite3.rst:36 @@ -125,8 +125,8 @@ msgstr "" #: library/sqlite3.rst:89 msgid "" "In order to execute SQL statements and fetch results from SQL queries, we " -"will need to use a database cursor. Call :meth:`con.cursor() ` to create the :class:`Cursor`:" +"will need to use a database cursor. Call :meth:`con.cursor() " +"` to create the :class:`Cursor`:" msgstr "" #: library/sqlite3.rst:93 @@ -139,8 +139,8 @@ msgid "" "database table ``movie`` with columns for title, release year, and review " "score. For simplicity, we can just use column names in the table declaration " "-- thanks to the `flexible typing`_ feature of SQLite, specifying the data " -"types is optional. Execute the ``CREATE TABLE`` statement by calling :meth:" -"`cur.execute(...) `:" +"types is optional. Execute the ``CREATE TABLE`` statement by " +"calling :meth:`cur.execute(...) `:" msgstr "" #: library/sqlite3.rst:106 @@ -152,9 +152,9 @@ msgid "" "We can verify that the new table has been created by querying the " "``sqlite_master`` table built-in to SQLite, which should now contain an " "entry for the ``movie`` table definition (see `The Schema Table`_ for " -"details). Execute that query by calling :meth:`cur.execute(...) `, assign the result to ``res``, and call :meth:`res.fetchone() " -"` to fetch the resulting row:" +"details). Execute that query by calling :meth:`cur.execute(...) " +"`, assign the result to ``res``, and " +"call :meth:`res.fetchone() ` to fetch the resulting row:" msgstr "" #: library/sqlite3.rst:121 @@ -166,9 +166,10 @@ msgstr "" #: library/sqlite3.rst:127 msgid "" -"We can see that the table has been created, as the query returns a :class:" -"`tuple` containing the table's name. If we query ``sqlite_master`` for a non-" -"existent table ``spam``, :meth:`!res.fetchone` will return ``None``:" +"We can see that the table has been created, as the query returns " +"a :class:`tuple` containing the table's name. If we query ``sqlite_master`` " +"for a non-existent table ``spam``, :meth:`!res.fetchone` will return " +"``None``:" msgstr "" #: library/sqlite3.rst:132 @@ -181,8 +182,8 @@ msgstr "" #: library/sqlite3.rst:138 msgid "" "Now, add two rows of data supplied as SQL literals by executing an " -"``INSERT`` statement, once again by calling :meth:`cur.execute(...) `:" +"``INSERT`` statement, once again by calling :meth:`cur.execute(...) " +"`:" msgstr "" #: library/sqlite3.rst:142 @@ -198,8 +199,8 @@ msgstr "" msgid "" "The ``INSERT`` statement implicitly opens a transaction, which needs to be " "committed before changes are saved in the database (see :ref:`sqlite3-" -"controlling-transactions` for details). Call :meth:`con.commit() ` on the connection object to commit the transaction:" +"controlling-transactions` for details). Call :meth:`con.commit() " +"` on the connection object to commit the transaction:" msgstr "" #: library/sqlite3.rst:156 @@ -210,8 +211,8 @@ msgstr "" msgid "" "We can verify that the data was inserted correctly by executing a ``SELECT`` " "query. Use the now-familiar :meth:`cur.execute(...) ` to " -"assign the result to ``res``, and call :meth:`res.fetchall() ` to return all resulting rows:" +"assign the result to ``res``, and call :meth:`res.fetchall() " +"` to return all resulting rows:" msgstr "" #: library/sqlite3.rst:166 @@ -229,8 +230,8 @@ msgstr "" #: library/sqlite3.rst:175 msgid "" -"Now, insert three more rows by calling :meth:`cur.executemany(...) `:" +"Now, insert three more rows by calling :meth:`cur.executemany(...) " +"`:" msgstr "" #: library/sqlite3.rst:178 @@ -278,9 +279,10 @@ msgstr "" #: library/sqlite3.rst:211 msgid "" -"Finally, verify that the database has been written to disk by calling :meth:" -"`con.close() ` to close the existing connection, opening a " -"new one, creating a new cursor, then querying the database:" +"Finally, verify that the database has been written to disk by " +"calling :meth:`con.close() ` to close the existing " +"connection, opening a new one, creating a new cursor, then querying the " +"database:" msgstr "" #: library/sqlite3.rst:216 @@ -358,9 +360,9 @@ msgstr "" #: library/sqlite3.rst:277 msgid "" -"How many seconds the connection should wait before raising an :exc:" -"`OperationalError` when a table is locked. If another connection opens a " -"transaction to modify a table, that table will be locked until the " +"How many seconds the connection should wait before raising " +"an :exc:`OperationalError` when a table is locked. If another connection " +"opens a transaction to modify a table, that table will be locked until the " "transaction is committed. Default five seconds." msgstr "" @@ -369,22 +371,22 @@ msgid "" "Control whether and how data types not :ref:`natively supported by SQLite " "` are looked up to be converted to Python types, using the " "converters registered with :func:`register_converter`. Set it to any " -"combination (using ``|``, bitwise or) of :const:`PARSE_DECLTYPES` and :const:" -"`PARSE_COLNAMES` to enable this. Column names takes precedence over declared " -"types if both flags are set. Types cannot be detected for generated fields " -"(for example ``max(data)``), even when the *detect_types* parameter is set; :" -"class:`str` will be returned instead. By default (``0``), type detection is " -"disabled." +"combination (using ``|``, bitwise or) of :const:`PARSE_DECLTYPES` " +"and :const:`PARSE_COLNAMES` to enable this. Column names takes precedence " +"over declared types if both flags are set. Types cannot be detected for " +"generated fields (for example ``max(data)``), even when the *detect_types* " +"parameter is set; :class:`str` will be returned instead. By default (``0``), " +"type detection is disabled." msgstr "" #: library/sqlite3.rst:298 msgid "" -"Control legacy transaction handling behaviour. See :attr:`Connection." -"isolation_level` and :ref:`sqlite3-transaction-control-isolation-level` for " -"more information. Can be ``\"DEFERRED\"`` (default), ``\"EXCLUSIVE\"`` or " -"``\"IMMEDIATE\"``; or ``None`` to disable opening transactions implicitly. " -"Has no effect unless :attr:`Connection.autocommit` is set to :const:" -"`~sqlite3.LEGACY_TRANSACTION_CONTROL` (the default)." +"Control legacy transaction handling behaviour. " +"See :attr:`Connection.isolation_level` and :ref:`sqlite3-transaction-control-" +"isolation-level` for more information. Can be ``\"DEFERRED\"`` (default), " +"``\"EXCLUSIVE\"`` or ``\"IMMEDIATE\"``; or ``None`` to disable opening " +"transactions implicitly. Has no effect unless :attr:`Connection.autocommit` " +"is set to :const:`~sqlite3.LEGACY_TRANSACTION_CONTROL` (the default)." msgstr "" #: library/sqlite3.rst:308 @@ -419,11 +421,11 @@ msgstr "" #: library/sqlite3.rst:335 msgid "" -"Control :pep:`249` transaction handling behaviour. See :attr:`Connection." -"autocommit` and :ref:`sqlite3-transaction-control-autocommit` for more " -"information. *autocommit* currently defaults to :const:`~sqlite3." -"LEGACY_TRANSACTION_CONTROL`. The default will change to ``False`` in a " -"future Python release." +"Control :pep:`249` transaction handling behaviour. " +"See :attr:`Connection.autocommit` and :ref:`sqlite3-transaction-control-" +"autocommit` for more information. *autocommit* currently defaults " +"to :const:`~sqlite3.LEGACY_TRANSACTION_CONTROL`. The default will change to " +"``False`` in a future Python release." msgstr "" #: library/sqlite3.rst:0 @@ -630,8 +632,8 @@ msgstr "" #: library/sqlite3.rst:501 msgid "" -"Version number of the runtime SQLite library as a :class:`tuple` of :class:" -"`integers `." +"Version number of the runtime SQLite library as a :class:`tuple` " +"of :class:`integers `." msgstr "" #: library/sqlite3.rst:506 @@ -748,8 +750,8 @@ msgstr "" #: library/sqlite3.rst:580 msgid "" -"These constants are used for the :meth:`Connection.setconfig` and :meth:" -"`~Connection.getconfig` methods." +"These constants are used for the :meth:`Connection.setconfig` " +"and :meth:`~Connection.getconfig` methods." msgstr "" #: library/sqlite3.rst:583 @@ -773,8 +775,9 @@ msgstr "" #: library/sqlite3.rst:601 msgid "" "Each open SQLite database is represented by a ``Connection`` object, which " -"is created using :func:`sqlite3.connect`. Their main purpose is creating :" -"class:`Cursor` objects, and :ref:`sqlite3-controlling-transactions`." +"is created using :func:`sqlite3.connect`. Their main purpose is " +"creating :class:`Cursor` objects, and :ref:`sqlite3-controlling-" +"transactions`." msgstr "" #: library/sqlite3.rst:608 @@ -788,8 +791,9 @@ msgstr "" #: library/sqlite3.rst:615 msgid "" "Create and return a :class:`Cursor` object. The cursor method accepts a " -"single optional parameter *factory*. If supplied, this must be a :term:" -"`callable` returning an instance of :class:`Cursor` or its subclasses." +"single optional parameter *factory*. If supplied, this must be " +"a :term:`callable` returning an instance of :class:`Cursor` or its " +"subclasses." msgstr "" #: library/sqlite3.rst:622 @@ -838,17 +842,17 @@ msgstr "" #: library/sqlite3.rst:657 msgid "" "Commit any pending transaction to the database. If :attr:`autocommit` is " -"``True``, or there is no open transaction, this method does nothing. If :" -"attr:`!autocommit` is ``False``, a new transaction is implicitly opened if a " -"pending transaction was committed by this method." +"``True``, or there is no open transaction, this method does nothing. " +"If :attr:`!autocommit` is ``False``, a new transaction is implicitly opened " +"if a pending transaction was committed by this method." msgstr "" #: library/sqlite3.rst:665 msgid "" "Roll back to the start of any pending transaction. If :attr:`autocommit` is " -"``True``, or there is no open transaction, this method does nothing. If :" -"attr:`!autocommit` is ``False``, a new transaction is implicitly opened if a " -"pending transaction was rolled back by this method." +"``True``, or there is no open transaction, this method does nothing. " +"If :attr:`!autocommit` is ``False``, a new transaction is implicitly opened " +"if a pending transaction was rolled back by this method." msgstr "" #: library/sqlite3.rst:673 @@ -1164,17 +1168,17 @@ msgstr "" #: library/sqlite3.rst:931 msgid "" "Call this method from a different thread to abort any queries that might be " -"executing on the connection. Aborted queries will raise an :exc:" -"`OperationalError`." +"executing on the connection. Aborted queries will raise " +"an :exc:`OperationalError`." msgstr "" #: library/sqlite3.rst:938 msgid "" "Register :term:`callable` *authorizer_callback* to be invoked for each " "attempt to access a column of a table in the database. The callback should " -"return one of :const:`SQLITE_OK`, :const:`SQLITE_DENY`, or :const:" -"`SQLITE_IGNORE` to signal how access to the column should be handled by the " -"underlying SQLite library." +"return one of :const:`SQLITE_OK`, :const:`SQLITE_DENY`, " +"or :const:`SQLITE_IGNORE` to signal how access to the column should be " +"handled by the underlying SQLite library." msgstr "" #: library/sqlite3.rst:945 @@ -1234,10 +1238,11 @@ msgstr "" msgid "" "The only argument passed to the callback is the statement (as :class:`str`) " "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 :ref:`transaction management " -"` of the :mod:`!sqlite3` module and the " -"execution of triggers defined in the current database." +"that the backend does not only run statements passed to " +"the :meth:`Cursor.execute` methods. Other sources include " +"the :ref:`transaction management ` of " +"the :mod:`!sqlite3` module and the execution of triggers defined in the " +"current database." msgstr "" #: library/sqlite3.rst:990 @@ -1265,8 +1270,8 @@ msgid "" "The :mod:`!sqlite3` module is not built with loadable extension support by " "default, because some platforms (notably macOS) have SQLite libraries which " "are compiled without this feature. To get loadable extension support, you " -"must pass the :option:`--enable-loadable-sqlite-extensions` option to :" -"program:`configure`." +"must pass the :option:`--enable-loadable-sqlite-extensions` option " +"to :program:`configure`." msgstr "" #: library/sqlite3.rst:1019 @@ -1343,8 +1348,8 @@ msgstr "" #: library/sqlite3.rst:1086 msgid "" "Return an :term:`iterator` to dump the database as SQL source code. Useful " -"when saving an in-memory database for later restoration. Similar to the ``." -"dump`` command in the :program:`sqlite3` shell." +"when saving an in-memory database for later restoration. Similar to the " +"``.dump`` command in the :program:`sqlite3` shell." msgstr "" #: library/sqlite3.rst:1092 @@ -1446,8 +1451,8 @@ msgstr "" #: library/sqlite3.rst:1189 msgid "" -"Example, query the maximum length of an SQL statement for :class:" -"`Connection` ``con`` (the default is 1000000000):" +"Example, query the maximum length of an SQL statement " +"for :class:`Connection` ``con`` (the default is 1000000000):" msgstr "" #: library/sqlite3.rst:1199 @@ -1526,10 +1531,10 @@ msgstr "" #: library/sqlite3.rst:1293 msgid "" -"Deserialize a :meth:`serialized ` database into a :class:" -"`Connection`. This method causes the database connection to disconnect from " -"database *name*, and reopen *name* as an in-memory database based on the " -"serialization contained in *data*." +"Deserialize a :meth:`serialized ` database into " +"a :class:`Connection`. This method causes the database connection to " +"disconnect from database *name*, and reopen *name* as an in-memory database " +"based on the serialization contained in *data*." msgstr "" #: library/sqlite3.rst:1299 @@ -1568,9 +1573,9 @@ msgstr "" #: library/sqlite3.rst:1328 msgid "" -"``False``: Select :pep:`249`-compliant transaction behaviour, implying that :" -"mod:`!sqlite3` ensures a transaction is always open. Use :meth:`commit` and :" -"meth:`rollback` to close transactions." +"``False``: Select :pep:`249`-compliant transaction behaviour, implying " +"that :mod:`!sqlite3` ensures a transaction is always open. " +"Use :meth:`commit` and :meth:`rollback` to close transactions." msgstr "" #: library/sqlite3.rst:1332 @@ -1579,8 +1584,8 @@ msgstr "" #: library/sqlite3.rst:1334 msgid "" -"``True``: Use SQLite's `autocommit mode`_. :meth:`commit` and :meth:" -"`rollback` have no effect in this mode." +"``True``: Use SQLite's `autocommit mode`_. :meth:`commit` " +"and :meth:`rollback` have no effect in this mode." msgstr "" #: library/sqlite3.rst:1337 @@ -1605,8 +1610,8 @@ msgstr "" #: library/sqlite3.rst:1350 msgid "" -"The :attr:`isolation_level` attribute has no effect unless :attr:" -"`autocommit` is :data:`LEGACY_TRANSACTION_CONTROL`." +"The :attr:`isolation_level` attribute has no effect " +"unless :attr:`autocommit` is :data:`LEGACY_TRANSACTION_CONTROL`." msgstr "" #: library/sqlite3.rst:1357 @@ -1648,10 +1653,10 @@ msgstr "" #: library/sqlite3.rst:1387 msgid "" "The initial :attr:`~Cursor.row_factory` for :class:`Cursor` objects created " -"from this connection. Assigning to this attribute does not affect the :attr:" -"`!row_factory` of existing cursors belonging to this connection, only new " -"ones. Is ``None`` by default, meaning each row is returned as a :class:" -"`tuple`." +"from this connection. Assigning to this attribute does not affect " +"the :attr:`!row_factory` of existing cursors belonging to this connection, " +"only new ones. Is ``None`` by default, meaning each row is returned as " +"a :class:`tuple`." msgstr "" #: library/sqlite3.rst:1680 library/sqlite3.rst:1703 @@ -1683,15 +1688,15 @@ msgstr "" msgid "" "A ``Cursor`` object represents a `database cursor`_ which is used to execute " "SQL statements, and manage the context of a fetch operation. Cursors are " -"created using :meth:`Connection.cursor`, or by using any of the :ref:" -"`connection shortcut methods `." +"created using :meth:`Connection.cursor`, or by using any of " +"the :ref:`connection shortcut methods `." msgstr "" #: library/sqlite3.rst:1423 msgid "" -"Cursor objects are :term:`iterators `, meaning that if you :meth:" -"`~Cursor.execute` a ``SELECT`` query, you can simply iterate over the cursor " -"to fetch the resulting rows:" +"Cursor objects are :term:`iterators `, meaning that if " +"you :meth:`~Cursor.execute` a ``SELECT`` query, you can simply iterate over " +"the cursor to fetch the resulting rows:" msgstr "" #: library/sqlite3.rst:1434 @@ -1706,8 +1711,8 @@ msgstr "" #: library/sqlite3.rst:1455 msgid "" -"Execute a single SQL statement, optionally binding Python values using :ref:" -"`placeholders `." +"Execute a single SQL statement, optionally binding Python values " +"using :ref:`placeholders `." msgstr "" #: library/sqlite3.rst:1459 @@ -1727,18 +1732,19 @@ msgstr "" #: library/sqlite3.rst:1472 msgid "" -"If :attr:`~Connection.autocommit` is :data:`LEGACY_TRANSACTION_CONTROL`, :" -"attr:`~Connection.isolation_level` is not ``None``, *sql* is an ``INSERT``, " -"``UPDATE``, ``DELETE``, or ``REPLACE`` statement, and there is no open " -"transaction, a transaction is implicitly opened before executing *sql*." +"If :attr:`~Connection.autocommit` " +"is :data:`LEGACY_TRANSACTION_CONTROL`, :attr:`~Connection.isolation_level` " +"is not ``None``, *sql* is an ``INSERT``, ``UPDATE``, ``DELETE``, or " +"``REPLACE`` statement, and there is no open transaction, a transaction is " +"implicitly opened before executing *sql*." msgstr "" #: library/sqlite3.rst:1481 msgid "" ":exc:`DeprecationWarning` is emitted if :ref:`named placeholders ` are used and *parameters* is a sequence instead of a :class:" -"`dict`. Starting with Python 3.14, :exc:`ProgrammingError` will be raised " -"instead." +"placeholders>` are used and *parameters* is a sequence instead of " +"a :class:`dict`. Starting with Python 3.14, :exc:`ProgrammingError` will be " +"raised instead." msgstr "" #: library/sqlite3.rst:1487 @@ -1797,11 +1803,11 @@ msgstr "" #: library/sqlite3.rst:1543 msgid "" -"Execute the SQL statements in *sql_script*. If the :attr:`~Connection." -"autocommit` is :data:`LEGACY_TRANSACTION_CONTROL` and there is a pending " -"transaction, an implicit ``COMMIT`` statement is executed first. No other " -"implicit transaction control is performed; any transaction control must be " -"added to *sql_script*." +"Execute the SQL statements in *sql_script*. If " +"the :attr:`~Connection.autocommit` is :data:`LEGACY_TRANSACTION_CONTROL` and " +"there is a pending transaction, an implicit ``COMMIT`` statement is executed " +"first. No other implicit transaction control is performed; any transaction " +"control must be added to *sql_script*." msgstr "" #: library/sqlite3.rst:1551 @@ -1862,9 +1868,9 @@ msgstr "" #: library/sqlite3.rst:1601 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." +"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 "" #: library/sqlite3.rst:1610 @@ -1873,17 +1879,17 @@ msgstr "" #: library/sqlite3.rst:1614 msgid "" -"Read/write attribute that controls the number of rows returned by :meth:" -"`fetchmany`. The default value is 1 which means a single row would be " -"fetched per call." +"Read/write attribute that controls the number of rows returned " +"by :meth:`fetchmany`. The default value is 1 which means a single row would " +"be fetched per call." msgstr "" #: library/sqlite3.rst:1619 msgid "" "Read-only attribute that provides the SQLite database :class:`Connection` " -"belonging to the cursor. A :class:`Cursor` object created by calling :meth:" -"`con.cursor() ` will have a :attr:`connection` attribute " -"that refers to *con*:" +"belonging to the cursor. A :class:`Cursor` object created by " +"calling :meth:`con.cursor() ` will have " +"a :attr:`connection` attribute that refers to *con*:" msgstr "" #: library/sqlite3.rst:1624 @@ -1946,8 +1952,8 @@ msgstr "" #: library/sqlite3.rst:1675 msgid "" "Defaults to what :attr:`Connection.row_factory` was set to when the :class:`!" -"Cursor` was created. Assigning to this attribute does not affect :attr:" -"`Connection.row_factory` of the parent connection." +"Cursor` was created. Assigning to this attribute does not " +"affect :attr:`Connection.row_factory` of the parent connection." msgstr "" #: library/sqlite3.rst:1691 @@ -1956,10 +1962,10 @@ msgstr "" #: library/sqlite3.rst:1695 msgid "" -"A :class:`!Row` instance serves as a highly optimized :attr:`~Connection." -"row_factory` for :class:`Connection` objects. It supports iteration, " -"equality testing, :func:`len`, and :term:`mapping` access by column name and " -"index." +"A :class:`!Row` instance serves as a highly " +"optimized :attr:`~Connection.row_factory` for :class:`Connection` objects. " +"It supports iteration, equality testing, :func:`len`, and :term:`mapping` " +"access by column name and index." msgstr "" #: library/sqlite3.rst:1700 @@ -1971,8 +1977,8 @@ msgstr "" #: library/sqlite3.rst:1707 msgid "" "Return a :class:`list` of column names as :class:`strings `. " -"Immediately after a query, it is the first member of each tuple in :attr:" -"`Cursor.description`." +"Immediately after a query, it is the first member of each tuple " +"in :attr:`Cursor.description`." msgstr "" #: library/sqlite3.rst:1711 @@ -1986,9 +1992,9 @@ msgstr "" #: library/sqlite3.rst:1724 msgid "" "A :class:`Blob` instance is a :term:`file-like object` that can read and " -"write data in an SQLite :abbr:`BLOB (Binary Large OBject)`. Call :func:" -"`len(blob) ` to get the size (number of bytes) of the blob. Use indices " -"and :term:`slices ` for direct access to the blob data." +"write data in an SQLite :abbr:`BLOB (Binary Large OBject)`. " +"Call :func:`len(blob) ` to get the size (number of bytes) of the blob. " +"Use indices and :term:`slices ` for direct access to the blob data." msgstr "" #: library/sqlite3.rst:1729 @@ -2025,24 +2031,24 @@ msgstr "" #: library/sqlite3.rst:1762 msgid "" -"The blob will be unusable from this point onward. An :class:`~sqlite3." -"Error` (or subclass) exception will be raised if any further operation is " -"attempted with the blob." +"The blob will be unusable from this point onward. " +"An :class:`~sqlite3.Error` (or subclass) exception will be raised if any " +"further operation is attempted with the blob." msgstr "" #: library/sqlite3.rst:1768 msgid "" "Read *length* bytes of data from the blob at the current offset position. If " "the end of the blob is reached, the data up to :abbr:`EOF (End of File)` " -"will be returned. When *length* is not specified, or is negative, :meth:" -"`~Blob.read` will read until the end of the blob." +"will be returned. When *length* is not specified, or is " +"negative, :meth:`~Blob.read` will read until the end of the blob." msgstr "" #: library/sqlite3.rst:1776 msgid "" "Write *data* to the blob at the current offset. This function cannot change " -"the blob length. Writing beyond the end of the blob will raise :exc:" -"`ValueError`." +"the blob length. Writing beyond the end of the blob will " +"raise :exc:`ValueError`." msgstr "" #: library/sqlite3.rst:1782 @@ -2099,8 +2105,8 @@ msgstr "" #: library/sqlite3.rst:1828 msgid "" -"The numeric error code from the `SQLite API `_" +"The numeric error code from the `SQLite API `_" msgstr "" #: library/sqlite3.rst:1835 @@ -2156,8 +2162,8 @@ msgstr "" msgid "" "Exception raised for :mod:`!sqlite3` API programming errors, for example " "supplying the wrong number of bindings to a query, or trying to operate on a " -"closed :class:`Connection`. ``ProgrammingError`` is a subclass of :exc:" -"`DatabaseError`." +"closed :class:`Connection`. ``ProgrammingError`` is a subclass " +"of :exc:`DatabaseError`." msgstr "" #: library/sqlite3.rst:1889 @@ -2278,8 +2284,8 @@ msgstr "" #: library/sqlite3.rst:1962 msgid "" -"A converter for :ref:`declared ` \"date\" types to :" -"class:`datetime.date` objects." +"A converter for :ref:`declared ` \"date\" types " +"to :class:`datetime.date` objects." msgstr "" #: library/sqlite3.rst:1964 @@ -2533,8 +2539,8 @@ msgstr "" #: library/sqlite3.rst:2195 msgid "" -"Both: set *detect_types* to ``sqlite3.PARSE_DECLTYPES | sqlite3." -"PARSE_COLNAMES``. Column names take precedence over declared types." +"Both: set *detect_types* to ``sqlite3.PARSE_DECLTYPES | " +"sqlite3.PARSE_COLNAMES``. Column names take precedence over declared types." msgstr "" #: library/sqlite3.rst:2199 @@ -2635,14 +2641,14 @@ msgstr "" #: library/sqlite3.rst:2318 msgid "" -"Using the :meth:`~Connection.execute`, :meth:`~Connection.executemany`, and :" -"meth:`~Connection.executescript` methods of the :class:`Connection` class, " -"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." +"Using the :meth:`~Connection.execute`, :meth:`~Connection.executemany`, " +"and :meth:`~Connection.executescript` methods of the :class:`Connection` " +"class, 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 "" #: library/sqlite3.rst:2327 @@ -2695,15 +2701,15 @@ msgstr "" #: library/sqlite3.rst:2377 msgid "" "The context manager neither implicitly opens a new transaction nor closes " -"the connection. If you need a closing context manager, consider using :meth:" -"`contextlib.closing`." +"the connection. If you need a closing context manager, consider " +"using :meth:`contextlib.closing`." msgstr "" #: library/sqlite3.rst:2381 msgid "" "con = sqlite3.connect(\":memory:\")\n" -"con.execute(\"CREATE TABLE lang(id INTEGER PRIMARY KEY, name VARCHAR " -"UNIQUE)\")\n" +"con.execute(\"CREATE TABLE lang(id INTEGER PRIMARY KEY, name VARCHAR UNIQUE)" +"\")\n" "\n" "# Successful, con.commit() is called automatically afterwards\n" "with con:\n" @@ -2787,17 +2793,17 @@ msgstr "" #: library/sqlite3.rst:2461 msgid "" -"By default, :mod:`!sqlite3` represents each row as a :class:`tuple`. If a :" -"class:`!tuple` does not suit your needs, you can use the :class:`sqlite3." -"Row` class or a custom :attr:`~Cursor.row_factory`." +"By default, :mod:`!sqlite3` represents each row as a :class:`tuple`. If " +"a :class:`!tuple` does not suit your needs, you can use " +"the :class:`sqlite3.Row` class or a custom :attr:`~Cursor.row_factory`." msgstr "" #: library/sqlite3.rst:2466 msgid "" -"While :attr:`!row_factory` exists as an attribute both on the :class:" -"`Cursor` and the :class:`Connection`, it is recommended to set :class:" -"`Connection.row_factory`, so all cursors created from the connection will " -"use the same row factory." +"While :attr:`!row_factory` exists as an attribute both on " +"the :class:`Cursor` and the :class:`Connection`, it is recommended to " +"set :class:`Connection.row_factory`, so all cursors created from the " +"connection will use the same row factory." msgstr "" #: library/sqlite3.rst:2471 @@ -2904,9 +2910,9 @@ msgstr "" #: library/sqlite3.rst:2551 msgid "" -"With some adjustments, the above recipe can be adapted to use a :class:" -"`~dataclasses.dataclass`, or any other custom class, instead of a :class:" -"`~collections.namedtuple`." +"With some adjustments, the above recipe can be adapted to use " +"a :class:`~dataclasses.dataclass`, or any other custom class, instead of " +"a :class:`~collections.namedtuple`." msgstr "" #: library/sqlite3.rst:2559 @@ -2917,8 +2923,8 @@ msgstr "" msgid "" "By default, :mod:`!sqlite3` uses :class:`str` to adapt SQLite values with " "the ``TEXT`` data type. This works well for UTF-8 encoded text, but it might " -"fail for other encodings and invalid UTF-8. You can use a custom :attr:" -"`~Connection.text_factory` to handle such cases." +"fail for other encodings and invalid UTF-8. You can use a " +"custom :attr:`~Connection.text_factory` to handle such cases." msgstr "" #: library/sqlite3.rst:2567 @@ -2927,9 +2933,9 @@ msgid "" "table columns with the ``TEXT`` data type containing non-UTF-8 encodings, or " "even arbitrary data. To demonstrate, let's assume we have a database with " "ISO-8859-2 (Latin-2) encoded text, for example a table of Czech-English " -"dictionary entries. Assuming we now have a :class:`Connection` instance :py:" -"data:`!con` connected to this database, we can decode the Latin-2 encoded " -"text using this :attr:`~Connection.text_factory`:" +"dictionary entries. Assuming we now have a :class:`Connection` " +"instance :py:data:`!con` connected to this database, we can decode the " +"Latin-2 encoded text using this :attr:`~Connection.text_factory`:" msgstr "" #: library/sqlite3.rst:2576 @@ -2978,9 +2984,9 @@ msgstr "" #: library/sqlite3.rst:2619 msgid "" -"The recommended way of controlling transaction behaviour is through the :" -"attr:`Connection.autocommit` attribute, which should preferably be set using " -"the *autocommit* parameter of :func:`connect`." +"The recommended way of controlling transaction behaviour is through " +"the :attr:`Connection.autocommit` attribute, which should preferably be set " +"using the *autocommit* parameter of :func:`connect`." msgstr "" #: library/sqlite3.rst:2624 @@ -2991,11 +2997,11 @@ msgstr "" #: library/sqlite3.rst:2628 msgid "" -":mod:`!sqlite3` ensures that a transaction is always open, so :func:" -"`connect`, :meth:`Connection.commit`, and :meth:`Connection.rollback` will " -"implicitly open a new transaction (immediately after closing the pending " -"one, for the latter two). :mod:`!sqlite3` uses ``BEGIN DEFERRED`` statements " -"when opening transactions." +":mod:`!sqlite3` ensures that a transaction is always open, " +"so :func:`connect`, :meth:`Connection.commit`, " +"and :meth:`Connection.rollback` will implicitly open a new transaction " +"(immediately after closing the pending one, for the latter two). :mod:`!" +"sqlite3` uses ``BEGIN DEFERRED`` statements when opening transactions." msgstr "" #: library/sqlite3.rst:2633 @@ -3008,8 +3014,8 @@ msgstr "" #: library/sqlite3.rst:2635 msgid "" -"An implicit rollback is performed if the database is :meth:`~Connection." -"close`-ed with pending changes." +"An implicit rollback is performed if the database " +"is :meth:`~Connection.close`-ed with pending changes." msgstr "" #: library/sqlite3.rst:2638 @@ -3017,15 +3023,16 @@ msgid "" "Set *autocommit* to ``True`` to enable SQLite's `autocommit mode`_. In this " "mode, :meth:`Connection.commit` and :meth:`Connection.rollback` have no " "effect. Note that SQLite's autocommit mode is distinct from the :pep:`249`-" -"compliant :attr:`Connection.autocommit` attribute; use :attr:`Connection." -"in_transaction` to query the low-level SQLite autocommit mode." +"compliant :attr:`Connection.autocommit` attribute; " +"use :attr:`Connection.in_transaction` to query the low-level SQLite " +"autocommit mode." msgstr "" #: library/sqlite3.rst:2646 msgid "" "Set *autocommit* to :data:`LEGACY_TRANSACTION_CONTROL` to leave transaction " -"control behaviour to the :attr:`Connection.isolation_level` attribute. See :" -"ref:`sqlite3-transaction-control-isolation-level` for more information." +"control behaviour to the :attr:`Connection.isolation_level` attribute. " +"See :ref:`sqlite3-transaction-control-isolation-level` for more information." msgstr "" #: library/sqlite3.rst:2655 @@ -3034,31 +3041,31 @@ msgstr "" #: library/sqlite3.rst:2659 msgid "" -"The recommended way of controlling transactions is via the :attr:" -"`~Connection.autocommit` attribute. See :ref:`sqlite3-transaction-control-" -"autocommit`." +"The recommended way of controlling transactions is via " +"the :attr:`~Connection.autocommit` attribute. See :ref:`sqlite3-transaction-" +"control-autocommit`." msgstr "" #: library/sqlite3.rst:2663 msgid "" -"If :attr:`Connection.autocommit` is set to :data:" -"`LEGACY_TRANSACTION_CONTROL` (the default), transaction behaviour is " -"controlled using the :attr:`Connection.isolation_level` attribute. " +"If :attr:`Connection.autocommit` is set " +"to :data:`LEGACY_TRANSACTION_CONTROL` (the default), transaction behaviour " +"is controlled using the :attr:`Connection.isolation_level` attribute. " "Otherwise, :attr:`!isolation_level` has no effect." msgstr "" #: library/sqlite3.rst:2669 msgid "" "If the connection attribute :attr:`~Connection.isolation_level` is not " -"``None``, new transactions are implicitly opened before :meth:`~Cursor." -"execute` and :meth:`~Cursor.executemany` executes ``INSERT``, ``UPDATE``, " -"``DELETE``, or ``REPLACE`` statements; for other statements, no implicit " -"transaction handling is performed. Use the :meth:`~Connection.commit` and :" -"meth:`~Connection.rollback` methods to respectively commit and roll back " -"pending transactions. You can choose the underlying `SQLite transaction " -"behaviour`_ — that is, whether and what type of ``BEGIN`` statements :mod:`!" -"sqlite3` implicitly executes – via the :attr:`~Connection.isolation_level` " -"attribute." +"``None``, new transactions are implicitly opened " +"before :meth:`~Cursor.execute` and :meth:`~Cursor.executemany` executes " +"``INSERT``, ``UPDATE``, ``DELETE``, or ``REPLACE`` statements; for other " +"statements, no implicit transaction handling is performed. Use " +"the :meth:`~Connection.commit` and :meth:`~Connection.rollback` methods to " +"respectively commit and roll back pending transactions. You can choose the " +"underlying `SQLite transaction behaviour`_ — that is, whether and what type " +"of ``BEGIN`` statements :mod:`!sqlite3` implicitly executes – via " +"the :attr:`~Connection.isolation_level` attribute." msgstr "" #: library/sqlite3.rst:2682 @@ -3067,8 +3074,8 @@ msgid "" "are implicitly opened at all. This leaves the underlying SQLite library in " "`autocommit mode`_, but also allows the user to perform their own " "transaction handling using explicit SQL statements. The underlying SQLite " -"library autocommit mode can be queried using the :attr:`~Connection." -"in_transaction` attribute." +"library autocommit mode can be queried using " +"the :attr:`~Connection.in_transaction` attribute." msgstr "" #: library/sqlite3.rst:2690 @@ -3086,8 +3093,8 @@ msgstr "" #: library/sqlite3.rst:2698 msgid "" -"The recommended way of controlling transactions is now via the :attr:" -"`~Connection.autocommit` attribute." +"The recommended way of controlling transactions is now via " +"the :attr:`~Connection.autocommit` attribute." msgstr "" #: library/sqlite3.rst:1450 diff --git a/library/ssl.po b/library/ssl.po index fa1a99248..ff9aaf0eb 100644 --- a/library/ssl.po +++ b/library/ssl.po @@ -115,9 +115,10 @@ msgstr "" #: library/ssl.rst:77 msgid "" -"Instances of :class:`SSLSocket` must be created using the :meth:`SSLContext." -"wrap_socket` method. The helper function :func:`create_default_context` " -"returns a new context with secure default settings." +"Instances of :class:`SSLSocket` must be created using " +"the :meth:`SSLContext.wrap_socket` method. The helper " +"function :func:`create_default_context` returns a new context with secure " +"default settings." msgstr "" #: library/ssl.rst:82 @@ -198,13 +199,13 @@ msgstr "" #: library/ssl.rst:139 msgid "" -"The settings are: :data:`PROTOCOL_TLS_CLIENT` or :data:" -"`PROTOCOL_TLS_SERVER`, :data:`OP_NO_SSLv2`, and :data:`OP_NO_SSLv3` with " -"high encryption cipher suites without RC4 and without unauthenticated cipher " -"suites. Passing :const:`~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 " +"The settings are: :data:`PROTOCOL_TLS_CLIENT` " +"or :data:`PROTOCOL_TLS_SERVER`, :data:`OP_NO_SSLv2`, and :data:`OP_NO_SSLv3` " +"with high encryption cipher suites without RC4 and without unauthenticated " +"cipher suites. Passing :const:`~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 "" @@ -224,8 +225,8 @@ msgstr "" #: library/ssl.rst:157 msgid "" -"If your application needs specific settings, you should create a :class:" -"`SSLContext` and apply the settings yourself." +"If your application needs specific settings, you should create " +"a :class:`SSLContext` and apply the settings yourself." msgstr "" #: library/ssl.rst:161 @@ -234,9 +235,9 @@ msgid "" "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::" +"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 "" #: library/ssl.rst:170 @@ -263,8 +264,9 @@ msgstr "" #: library/ssl.rst:191 msgid "" -"The context now uses :data:`PROTOCOL_TLS_CLIENT` or :data:" -"`PROTOCOL_TLS_SERVER` protocol instead of generic :data:`PROTOCOL_TLS`." +"The context now uses :data:`PROTOCOL_TLS_CLIENT` " +"or :data:`PROTOCOL_TLS_SERVER` protocol instead of " +"generic :data:`PROTOCOL_TLS`." msgstr "" #: library/ssl.rst:197 @@ -361,11 +363,11 @@ msgstr "" #: library/ssl.rst:297 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." +"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 "" #: library/ssl.rst:303 @@ -383,9 +385,9 @@ msgstr "" #: library/ssl.rst:314 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." +"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 "" #: library/ssl.rst:321 @@ -444,11 +446,11 @@ msgid "" "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 *cafile* parameter in :meth:`SSLContext." -"load_verify_locations`. The call will attempt to validate the server " -"certificate against that set of root certificates, and will fail if the " -"validation attempt fails. A timeout can be specified with the ``timeout`` " -"parameter." +"same format as used for the *cafile* parameter " +"in :meth:`SSLContext.load_verify_locations`. The call will attempt to " +"validate the server certificate against that set of root certificates, and " +"will fail if the validation attempt fails. A timeout can be specified with " +"the ``timeout`` parameter." msgstr "" #: library/ssl.rst:377 @@ -457,8 +459,8 @@ msgstr "" #: library/ssl.rst:380 msgid "" -"The default *ssl_version* is changed from :data:`PROTOCOL_SSLv3` to :data:" -"`PROTOCOL_TLS` for maximum compatibility with modern servers." +"The default *ssl_version* is changed from :data:`PROTOCOL_SSLv3` " +"to :data:`PROTOCOL_TLS` for maximum compatibility with modern servers." msgstr "" #: library/ssl.rst:384 @@ -526,10 +528,11 @@ msgstr "" #: library/ssl.rst:419 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." +"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 "" #: library/ssl.rst:1555 library/ssl.rst:1853 @@ -552,8 +555,9 @@ msgstr "" #: library/ssl.rst:442 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." +"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 "" #: library/ssl.rst:453 @@ -568,10 +572,11 @@ msgstr "" #: library/ssl.rst:461 msgid "" -"Possible value for :attr:`SSLContext.verify_mode`. Except for :const:" -"`PROTOCOL_TLS_CLIENT`, it is the default mode. With client-side sockets, " -"just about any cert is accepted. Validation errors, such as untrusted or " -"expired cert, are ignored and do not abort the TLS/SSL handshake." +"Possible value for :attr:`SSLContext.verify_mode`. Except " +"for :const:`PROTOCOL_TLS_CLIENT`, it is the default mode. With client-side " +"sockets, just about any cert is accepted. Validation errors, such as " +"untrusted or expired cert, are ignored and do not abort the TLS/SSL " +"handshake." msgstr "" #: library/ssl.rst:467 @@ -586,9 +591,10 @@ msgstr "" #: library/ssl.rst:474 msgid "" -"Possible value for :attr:`SSLContext.verify_mode`. In client mode, :const:" -"`CERT_OPTIONAL` has the same meaning as :const:`CERT_REQUIRED`. It is " -"recommended to use :const:`CERT_REQUIRED` for client-side sockets instead." +"Possible value for :attr:`SSLContext.verify_mode`. In client " +"mode, :const:`CERT_OPTIONAL` has the same meaning as :const:`CERT_REQUIRED`. " +"It is recommended to use :const:`CERT_REQUIRED` for client-side sockets " +"instead." msgstr "" #: library/ssl.rst:479 @@ -602,20 +608,21 @@ msgstr "" #: library/ssl.rst:504 msgid "" -"Use of this setting requires a valid set of CA certificates to be passed to :" -"meth:`SSLContext.load_verify_locations`." +"Use of this setting requires a valid set of CA certificates to be passed " +"to :meth:`SSLContext.load_verify_locations`." msgstr "" #: library/ssl.rst:490 msgid "" "Possible value for :attr:`SSLContext.verify_mode`. 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 " +"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. This mode is **not** sufficient to verify a certificate in " -"client mode as it does not match hostnames. :attr:`~SSLContext." -"check_hostname` must be enabled as well to verify the authenticity of a " -"cert. :const:`PROTOCOL_TLS_CLIENT` uses :const:`CERT_REQUIRED` and enables :" -"attr:`~SSLContext.check_hostname` by default." +"client mode as it does not match " +"hostnames. :attr:`~SSLContext.check_hostname` must be enabled as well to " +"verify the authenticity of a cert. :const:`PROTOCOL_TLS_CLIENT` " +"uses :const:`CERT_REQUIRED` and enables :attr:`~SSLContext.check_hostname` " +"by default." msgstr "" #: library/ssl.rst:500 @@ -641,8 +648,8 @@ msgid "" "Possible value for :attr:`SSLContext.verify_flags`. In this mode, only the " "peer cert is checked but none 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 CRL has been loaded with :attr:`SSLContext." -"load_verify_locations`, validation will fail." +"ancestor CA). If no proper CRL has been loaded " +"with :attr:`SSLContext.load_verify_locations`, validation will fail." msgstr "" #: library/ssl.rst:533 @@ -693,8 +700,8 @@ msgstr "" #: library/ssl.rst:586 msgid "" "TLS clients and servers require different default settings for secure " -"communication. The generic TLS protocol constant is deprecated in favor of :" -"data:`PROTOCOL_TLS_CLIENT` and :data:`PROTOCOL_TLS_SERVER`." +"communication. The generic TLS protocol constant is deprecated in favor " +"of :data:`PROTOCOL_TLS_CLIENT` and :data:`PROTOCOL_TLS_SERVER`." msgstr "" #: library/ssl.rst:592 @@ -736,9 +743,9 @@ msgstr "" #: library/ssl.rst:627 msgid "" "OpenSSL has deprecated all version specific protocols. Use the default " -"protocol :data:`PROTOCOL_TLS_SERVER` or :data:`PROTOCOL_TLS_CLIENT` with :" -"attr:`SSLContext.minimum_version` and :attr:`SSLContext.maximum_version` " -"instead." +"protocol :data:`PROTOCOL_TLS_SERVER` or :data:`PROTOCOL_TLS_CLIENT` " +"with :attr:`SSLContext.minimum_version` " +"and :attr:`SSLContext.maximum_version` instead." msgstr "" #: library/ssl.rst:635 @@ -799,8 +806,9 @@ msgstr "" #: library/ssl.rst:703 msgid "" -"The option is deprecated since OpenSSL 1.1.0, use the new :attr:`SSLContext." -"minimum_version` and :attr:`SSLContext.maximum_version` instead." +"The option is deprecated since OpenSSL 1.1.0, use the " +"new :attr:`SSLContext.minimum_version` " +"and :attr:`SSLContext.maximum_version` instead." msgstr "" #: library/ssl.rst:710 @@ -1034,8 +1042,8 @@ msgstr "" #: library/ssl.rst:954 msgid "" -"Used as the return value of the callback function in :meth:`SSLContext." -"set_servername_callback`." +"Used as the return value of the callback function " +"in :meth:`SSLContext.set_servername_callback`." msgstr "" #: library/ssl.rst:961 @@ -1044,18 +1052,18 @@ msgstr "" #: library/ssl.rst:967 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)." +"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 "" #: library/ssl.rst:976 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)." +"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 "" #: library/ssl.rst:985 @@ -1064,8 +1072,9 @@ msgstr "" #: library/ssl.rst:991 msgid "" -":class:`enum.IntEnum` collection of SSL and TLS versions for :attr:" -"`SSLContext.maximum_version` and :attr:`SSLContext.minimum_version`." +":class:`enum.IntEnum` collection of SSL and TLS versions " +"for :attr:`SSLContext.maximum_version` " +"and :attr:`SSLContext.minimum_version`." msgstr "" #: library/ssl.rst:999 @@ -1081,8 +1090,8 @@ msgstr "" #: library/ssl.rst:1013 msgid "" -"All :class:`TLSVersion` members except :attr:`TLSVersion.TLSv1_2` and :attr:" -"`TLSVersion.TLSv1_3` are deprecated." +"All :class:`TLSVersion` members except :attr:`TLSVersion.TLSv1_2` " +"and :attr:`TLSVersion.TLSv1_3` are deprecated." msgstr "" #: library/ssl.rst:1018 @@ -1126,9 +1135,7 @@ msgid ":meth:`~socket.socket.getsockopt`, :meth:`~socket.socket.setsockopt`" msgstr "" #: library/ssl.rst:1032 -msgid "" -":meth:`~socket.socket.gettimeout`, :meth:`~socket.socket.settimeout`, :meth:" -"`~socket.socket.setblocking`" +msgid ":meth:`~socket.socket.gettimeout`, :meth:`~socket.socket.settimeout`, :meth:`~socket.socket.setblocking`" msgstr "" #: library/ssl.rst:1034 @@ -1171,8 +1178,8 @@ msgstr "" #: library/ssl.rst:1049 msgid "" -"Instances of :class:`SSLSocket` must be created using the :meth:`SSLContext." -"wrap_socket` method." +"Instances of :class:`SSLSocket` must be created using " +"the :meth:`SSLContext.wrap_socket` method." msgstr "" #: library/ssl.rst:1052 @@ -1188,15 +1195,16 @@ msgstr "" #: library/ssl.rst:1060 msgid "" -"It is deprecated to create a :class:`SSLSocket` instance directly, use :meth:" -"`SSLContext.wrap_socket` to wrap a socket." +"It is deprecated to create a :class:`SSLSocket` instance directly, " +"use :meth:`SSLContext.wrap_socket` to wrap a socket." msgstr "" #: library/ssl.rst:1064 msgid "" -":class:`SSLSocket` instances must to created with :meth:`~SSLContext." -"wrap_socket`. In earlier versions, it was possible to create instances " -"directly. This was never documented or officially supported." +":class:`SSLSocket` instances must to created " +"with :meth:`~SSLContext.wrap_socket`. In earlier versions, it was possible " +"to create instances directly. This was never documented or officially " +"supported." msgstr "" #: library/ssl.rst:1070 @@ -1219,8 +1227,8 @@ msgstr "" #: library/ssl.rst:1083 msgid "" -"Raise :exc:`SSLWantReadError` or :exc:`SSLWantWriteError` if the socket is :" -"ref:`non-blocking ` and the read would block." +"Raise :exc:`SSLWantReadError` or :exc:`SSLWantWriteError` if the socket " +"is :ref:`non-blocking ` and the read would block." msgstr "" #: library/ssl.rst:1086 @@ -1248,8 +1256,8 @@ msgstr "" #: library/ssl.rst:1102 msgid "" -"Raise :exc:`SSLWantReadError` or :exc:`SSLWantWriteError` if the socket is :" -"ref:`non-blocking ` and the write would block." +"Raise :exc:`SSLWantReadError` or :exc:`SSLWantWriteError` if the socket " +"is :ref:`non-blocking ` and the write would block." msgstr "" #: library/ssl.rst:1105 @@ -1273,14 +1281,15 @@ 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." +"active SSL connection, i.e. the handshake was completed " +"and :meth:`SSLSocket.unwrap` was not called." msgstr "" #: library/ssl.rst:1123 msgid "" -"Normally you should use the socket API methods like :meth:`~socket.socket." -"recv` and :meth:`~socket.socket.send` instead of these methods." +"Normally you should use the socket API methods " +"like :meth:`~socket.socket.recv` and :meth:`~socket.socket.send` instead of " +"these methods." msgstr "" #: library/ssl.rst:1129 @@ -1289,9 +1298,9 @@ msgstr "" #: library/ssl.rst:1131 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." +"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 "" #: library/ssl.rst:1136 @@ -1302,17 +1311,17 @@ msgstr "" #: library/ssl.rst:1140 msgid "" -"Hostname or IP address is matched by OpenSSL during handshake. The function :" -"func:`match_hostname` is no longer used. In case OpenSSL refuses a hostname " -"or IP address, the handshake is aborted early and a TLS alert message is " -"sent to the peer." +"Hostname or IP address is matched by OpenSSL during handshake. The " +"function :func:`match_hostname` is no longer used. In case OpenSSL refuses a " +"hostname or IP address, the handshake is aborted early and a TLS alert " +"message is sent to the peer." msgstr "" #: library/ssl.rst:1148 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`." +"return ``None``. If the SSL handshake hasn't been done yet, " +"raise :exc:`ValueError`." msgstr "" #: library/ssl.rst:1152 @@ -1376,9 +1385,9 @@ msgstr "" #: library/ssl.rst:1194 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`)." +"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 "" #: library/ssl.rst:1199 @@ -1442,17 +1451,18 @@ msgstr "" 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." +"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 "" #: library/ssl.rst:1255 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." +"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 "" #: library/ssl.rst:1265 @@ -1480,8 +1490,8 @@ msgstr "" msgid "" "Requests post-handshake authentication (PHA) from a TLS 1.3 client. PHA can " "only be initiated for a TLS 1.3 connection from a server-side socket, after " -"the initial TLS handshake and with PHA enabled on both sides, see :attr:" -"`SSLContext.post_handshake_auth`." +"the initial TLS handshake and with PHA enabled on both sides, " +"see :attr:`SSLContext.post_handshake_auth`." msgstr "" #: library/ssl.rst:1291 @@ -1493,8 +1503,8 @@ msgstr "" #: library/ssl.rst:1295 msgid "" -"If any precondition isn't met (e.g. not TLS 1.3, PHA not enabled), an :exc:" -"`SSLError` is raised." +"If any precondition isn't met (e.g. not TLS 1.3, PHA not enabled), " +"an :exc:`SSLError` is raised." msgstr "" #: library/ssl.rst:1299 @@ -1538,16 +1548,16 @@ msgstr "" msgid "" "The attribute is now always ASCII text. When ``server_hostname`` is an " "internationalized domain name (IDN), this attribute now stores the A-label " -"form (``\"xn--pythn-mua.org\"``), rather than the U-label form (``\"pythön." -"org\"``)." +"form (``\"xn--pythn-mua.org\"``), rather than the U-label form " +"(``\"pythön.org\"``)." msgstr "" #: library/ssl.rst:1347 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." +"performed. For client sockets the session can be set " +"before :meth:`~SSLSocket.do_handshake` has been called to reuse a session." msgstr "" #: library/ssl.rst:1360 @@ -1673,28 +1683,27 @@ msgstr "" #: library/ssl.rst:1409 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`, 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." +"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`, " +"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." msgstr "" #: library/ssl.rst:1419 msgid "" ":class:`SSLContext` without protocol argument is deprecated. The context " -"class will either require :data:`PROTOCOL_TLS_CLIENT` or :data:" -"`PROTOCOL_TLS_SERVER` protocol in the future." +"class will either require :data:`PROTOCOL_TLS_CLIENT` " +"or :data:`PROTOCOL_TLS_SERVER` protocol in the future." msgstr "" #: library/ssl.rst:1425 msgid "" "The default cipher suites now include only secure AES and ChaCha20 ciphers " "with forward secrecy and security level 2. RSA and DH keys with less than " -"2048 bits and ECC keys with less than 224 bits are prohibited. :data:" -"`PROTOCOL_TLS`, :data:`PROTOCOL_TLS_CLIENT`, and :data:`PROTOCOL_TLS_SERVER` " -"use TLS 1.2 as minimum TLS version." +"2048 bits and ECC keys with less than 224 bits are " +"prohibited. :data:`PROTOCOL_TLS`, :data:`PROTOCOL_TLS_CLIENT`, " +"and :data:`PROTOCOL_TLS_SERVER` use TLS 1.2 as minimum TLS version." msgstr "" #: library/ssl.rst:1433 @@ -1777,9 +1786,9 @@ msgstr "" 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 all systems it calls :meth:`SSLContext." -"set_default_verify_paths`. In the future the method may load CA certificates " -"from other locations, too." +"system stores. On all systems it " +"calls :meth:`SSLContext.set_default_verify_paths`. In the future the method " +"may load CA certificates from other locations, too." msgstr "" #: library/ssl.rst:1499 @@ -1794,8 +1803,9 @@ msgstr "" #: library/ssl.rst:1509 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." +"other peers' certificates when :data:`verify_mode` is other " +"than :data:`CERT_NONE`. At least one of *cafile* or *capath* must be " +"specified." msgstr "" #: library/ssl.rst:1513 @@ -1849,8 +1859,8 @@ msgstr "" #: library/ssl.rst:1552 msgid "" -"Get a list of enabled ciphers. The list is in order of cipher priority. See :" -"meth:`SSLContext.set_ciphers`." +"Get a list of enabled ciphers. The list is in order of cipher priority. " +"See :meth:`SSLContext.set_ciphers`." msgstr "" #: library/ssl.rst:1557 @@ -1911,16 +1921,16 @@ msgstr "" #: library/ssl.rst:1609 msgid "" -"TLS 1.3 cipher suites cannot be disabled with :meth:`~SSLContext." -"set_ciphers`." +"TLS 1.3 cipher suites cannot be disabled " +"with :meth:`~SSLContext.set_ciphers`." msgstr "" #: library/ssl.rst:1614 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 " +"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 "" @@ -1938,9 +1948,9 @@ msgid "" "ordered by preference. The selection of a protocol will happen during the " "handshake, and will play out according to the `Application Layer Protocol " "Negotiation `_. After a successful handshake, the :meth:" -"`SSLSocket.selected_npn_protocol` method will return the agreed-upon " -"protocol." +"Layer_Protocol_Negotiation>`_. After a successful handshake, " +"the :meth:`SSLSocket.selected_npn_protocol` method will return the agreed-" +"upon protocol." msgstr "" #: library/ssl.rst:1636 @@ -1977,36 +1987,37 @@ msgstr "" #: library/ssl.rst:1664 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." +"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 "" #: library/ssl.rst:1669 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`. The :meth:`SSLSocket." -"getpeercert`, :meth:`SSLSocket.cipher` and :meth:`SSLSocket.compression` " -"methods require that the TLS connection has progressed beyond the TLS Client " -"Hello and therefore will not return meaningful values nor can they be called " -"safely." +"methods and attributes are usable " +"like :meth:`SSLSocket.selected_alpn_protocol` and :attr:`SSLSocket.context`. " +"The :meth:`SSLSocket.getpeercert`, :meth:`SSLSocket.cipher` " +"and :meth:`SSLSocket.compression` methods require that the TLS connection " +"has progressed beyond the TLS Client Hello and therefore will not return " +"meaningful values nor can they be called safely." msgstr "" #: library/ssl.rst:1677 msgid "" "The *sni_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`." +"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 "" #: library/ssl.rst:1683 msgid "" "If an exception is raised from the *sni_callback* function the TLS " -"connection will terminate with a fatal TLS alert message :const:" -"`ALERT_DESCRIPTION_HANDSHAKE_FAILURE`." +"connection will terminate with a fatal TLS alert " +"message :const:`ALERT_DESCRIPTION_HANDSHAKE_FAILURE`." msgstr "" #: library/ssl.rst:1687 @@ -2042,8 +2053,8 @@ msgstr "" #: library/ssl.rst:1714 msgid "" -"This setting doesn't apply to client sockets. You can also use the :data:" -"`OP_SINGLE_DH_USE` option to further improve security." +"This setting doesn't apply to client sockets. You can also use " +"the :data:`OP_SINGLE_DH_USE` option to further improve security." msgstr "" #: library/ssl.rst:1721 @@ -2057,8 +2068,8 @@ msgstr "" #: library/ssl.rst:1727 msgid "" -"This setting doesn't apply to client sockets. You can also use the :data:" -"`OP_SINGLE_ECDH_USE` option to further improve security." +"This setting doesn't apply to client sockets. You can also use " +"the :data:`OP_SINGLE_ECDH_USE` option to further improve security." msgstr "" #: library/ssl.rst:1730 @@ -2077,10 +2088,11 @@ msgstr "" #: library/ssl.rst:1742 msgid "" -"Wrap an existing Python socket *sock* and return an instance of :attr:" -"`SSLContext.sslsocket_class` (default :class:`SSLSocket`). The returned SSL " -"socket is tied to the context, its settings and certificates. *sock* must be " -"a :const:`~socket.SOCK_STREAM` socket; other socket types are unsupported." +"Wrap an existing Python socket *sock* and return an instance " +"of :attr:`SSLContext.sslsocket_class` (default :class:`SSLSocket`). The " +"returned SSL socket is tied to the context, its settings and certificates. " +"*sock* must be a :const:`~socket.SOCK_STREAM` socket; other socket types are " +"unsupported." msgstr "" #: library/ssl.rst:1748 @@ -2096,8 +2108,8 @@ msgid "" "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. The method may raise :" -"exc:`SSLError`." +"connections accepted via the :meth:`accept` method. The method may " +"raise :exc:`SSLError`." msgstr "" #: library/ssl.rst:1759 @@ -2113,20 +2125,20 @@ msgstr "" 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." +"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 "" #: library/ssl.rst:1772 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." +"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 "" #: library/ssl.rst:1779 @@ -2135,8 +2147,8 @@ msgstr "" #: library/ssl.rst:1781 msgid "" -"To wrap an :class:`SSLSocket` in another :class:`SSLSocket`, use :meth:" -"`SSLContext.wrap_bio`." +"To wrap an :class:`SSLSocket` in another :class:`SSLSocket`, " +"use :meth:`SSLContext.wrap_bio`." msgstr "" #: library/ssl.rst:1784 @@ -2157,15 +2169,15 @@ msgstr "" #: library/ssl.rst:1797 msgid "" -"The return type of :meth:`SSLContext.wrap_socket`, defaults to :class:" -"`SSLSocket`. The attribute can be overridden on instance of class in order " -"to return a custom subclass of :class:`SSLSocket`." +"The return type of :meth:`SSLContext.wrap_socket`, defaults " +"to :class:`SSLSocket`. The attribute can be overridden on instance of class " +"in order to return a custom subclass of :class:`SSLSocket`." msgstr "" #: library/ssl.rst:1806 msgid "" -"Wrap the BIO objects *incoming* and *outgoing* and return an instance of :" -"attr:`SSLContext.sslobject_class` (default :class:`SSLObject`). The SSL " +"Wrap the BIO objects *incoming* and *outgoing* and return an instance " +"of :attr:`SSLContext.sslobject_class` (default :class:`SSLObject`). The SSL " "routines will read input data from the incoming BIO and write data to the " "outgoing BIO." msgstr "" @@ -2184,9 +2196,9 @@ msgstr "" #: library/ssl.rst:1823 msgid "" -"The return type of :meth:`SSLContext.wrap_bio`, defaults to :class:" -"`SSLObject`. The attribute can be overridden on instance of class in order " -"to return a custom subclass of :class:`SSLObject`." +"The return type of :meth:`SSLContext.wrap_bio`, defaults " +"to :class:`SSLObject`. The attribute can be overridden on instance of class " +"in order to return a custom subclass of :class:`SSLObject`." msgstr "" #: library/ssl.rst:1831 @@ -2208,14 +2220,15 @@ msgstr "" #: library/ssl.rst:1842 msgid "" "Whether to match the peer cert's 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 " +"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. Enabling hostname checking automatically sets :attr:`~SSLContext." -"verify_mode` from :data:`CERT_NONE` to :data:`CERT_REQUIRED`. It cannot be " -"set back to :data:`CERT_NONE` as long as hostname checking is enabled. The :" -"data:`PROTOCOL_TLS_CLIENT` protocol enables hostname checking by default. " -"With other protocols, hostname checking must be enabled explicitly." +"hostname. Enabling hostname checking automatically " +"sets :attr:`~SSLContext.verify_mode` from :data:`CERT_NONE` " +"to :data:`CERT_REQUIRED`. It cannot be set back to :data:`CERT_NONE` as " +"long as hostname checking is enabled. The :data:`PROTOCOL_TLS_CLIENT` " +"protocol enables hostname checking by default. With other protocols, " +"hostname checking must be enabled explicitly." msgstr "" #: library/ssl.rst:1855 @@ -2234,10 +2247,10 @@ msgstr "" #: library/ssl.rst:1870 msgid "" -":attr:`~SSLContext.verify_mode` is now automatically changed to :data:" -"`CERT_REQUIRED` when hostname checking is enabled and :attr:`~SSLContext." -"verify_mode` is :data:`CERT_NONE`. Previously the same operation would have " -"failed with a :exc:`ValueError`." +":attr:`~SSLContext.verify_mode` is now automatically changed " +"to :data:`CERT_REQUIRED` when hostname checking is enabled " +"and :attr:`~SSLContext.verify_mode` is :data:`CERT_NONE`. Previously the " +"same operation would have failed with a :exc:`ValueError`." msgstr "" #: library/ssl.rst:1877 @@ -2253,18 +2266,20 @@ msgstr "" msgid "" "A :class:`TLSVersion` enum member representing the highest supported TLS " "version. The value defaults to :attr:`TLSVersion.MAXIMUM_SUPPORTED`. The " -"attribute is read-only for protocols other than :attr:`PROTOCOL_TLS`, :attr:" -"`PROTOCOL_TLS_CLIENT`, and :attr:`PROTOCOL_TLS_SERVER`." +"attribute is read-only for protocols other " +"than :attr:`PROTOCOL_TLS`, :attr:`PROTOCOL_TLS_CLIENT`, " +"and :attr:`PROTOCOL_TLS_SERVER`." msgstr "" #: library/ssl.rst:1892 msgid "" -"The attributes :attr:`~SSLContext.maximum_version`, :attr:`~SSLContext." -"minimum_version` and :attr:`SSLContext.options` all affect the supported SSL " -"and TLS versions of the context. The implementation does not prevent invalid " -"combination. For example a context with :attr:`OP_NO_TLSv1_2` in :attr:" -"`~SSLContext.options` and :attr:`~SSLContext.maximum_version` set to :attr:" -"`TLSVersion.TLSv1_2` will not be able to establish a TLS 1.2 connection." +"The " +"attributes :attr:`~SSLContext.maximum_version`, :attr:`~SSLContext.minimum_version` " +"and :attr:`SSLContext.options` all affect the supported SSL and TLS versions " +"of the context. The implementation does not prevent invalid combination. For " +"example a context with :attr:`OP_NO_TLSv1_2` in :attr:`~SSLContext.options` " +"and :attr:`~SSLContext.maximum_version` set to :attr:`TLSVersion.TLSv1_2` " +"will not be able to establish a TLS 1.2 connection." msgstr "" #: library/ssl.rst:1905 @@ -2275,16 +2290,16 @@ msgstr "" #: library/ssl.rst:1912 msgid "" -"Control the number of TLS 1.3 session tickets of a :attr:" -"`PROTOCOL_TLS_SERVER` context. The setting has no impact on TLS 1.0 to 1.2 " -"connections." +"Control the number of TLS 1.3 session tickets of " +"a :attr:`PROTOCOL_TLS_SERVER` context. The setting has no impact on TLS 1.0 " +"to 1.2 connections." msgstr "" #: library/ssl.rst:1920 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." +"default value is :data:`OP_ALL`, but you can specify other options such " +"as :data:`OP_NO_SSLv2` by ORing them together." msgstr "" #: library/ssl.rst:1924 @@ -2294,8 +2309,8 @@ msgstr "" #: library/ssl.rst:1932 msgid "" "All ``OP_NO_SSL*`` and ``OP_NO_TLS*`` options have been deprecated since " -"Python 3.7. Use :attr:`SSLContext.minimum_version` and :attr:`SSLContext." -"maximum_version` instead." +"Python 3.7. Use :attr:`SSLContext.minimum_version` " +"and :attr:`SSLContext.maximum_version` instead." msgstr "" #: library/ssl.rst:1938 @@ -2316,8 +2331,9 @@ msgstr "" msgid "" "When enabled on server-side sockets, :attr:`SSLContext.verify_mode` must be " "set to :data:`CERT_OPTIONAL` or :data:`CERT_REQUIRED`, too. The actual " -"client cert exchange is delayed until :meth:`SSLSocket." -"verify_client_post_handshake` is called and some I/O is performed." +"client cert exchange is delayed " +"until :meth:`SSLSocket.verify_client_post_handshake` is called and some I/O " +"is performed." msgstr "" #: library/ssl.rst:1956 @@ -2348,9 +2364,9 @@ msgstr "" #: library/ssl.rst:1982 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)." +"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)." msgstr "" #: library/ssl.rst:1988 @@ -2360,8 +2376,8 @@ msgstr "" #: library/ssl.rst:1996 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`." +"verification fails. This attribute must be one " +"of :data:`CERT_NONE`, :data:`CERT_OPTIONAL` or :data:`CERT_REQUIRED`." msgstr "" #: library/ssl.rst:2000 @@ -2468,9 +2484,9 @@ msgid "" "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`." +"platform's certificates file can be used by " +"calling :meth:`SSLContext.load_default_certs`, this is done automatically " +"with :func:`.create_default_context`." msgstr "" #: library/ssl.rst:2089 @@ -2609,8 +2625,8 @@ msgstr "" #: library/ssl.rst:2181 msgid "" -"When you use the context to connect to a server, :const:`CERT_REQUIRED` and :" -"attr:`~SSLContext.check_hostname` validate the server certificate: it " +"When you use the context to connect to a server, :const:`CERT_REQUIRED` " +"and :attr:`~SSLContext.check_hostname` validate the server certificate: it " "ensures that the server certificate was signed with one of the CA " "certificates, checks the signature for correctness, and verifies other " "properties like validity and identity of the hostname::" @@ -2643,10 +2659,10 @@ msgid "" "{'OCSP': ('http://ocsp.digicert.com',),\n" " 'caIssuers': ('http://cacerts.digicert.com/" "DigiCertSHA2ExtendedValidationServerCA.crt',),\n" -" 'crlDistributionPoints': ('http://crl3.digicert.com/sha2-ev-server-g1." -"crl',\n" -" 'http://crl4.digicert.com/sha2-ev-server-g1." -"crl'),\n" +" 'crlDistributionPoints': ('http://crl3.digicert.com/sha2-ev-server-" +"g1.crl',\n" +" 'http://crl4.digicert.com/sha2-ev-server-" +"g1.crl'),\n" " 'issuer': ((('countryName', 'US'),),\n" " (('organizationName', 'DigiCert Inc'),),\n" " (('organizationalUnitName', 'www.digicert.com'),),\n" @@ -2741,8 +2757,9 @@ msgstr "" #: library/ssl.rst:2282 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::" +"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 "" #: library/ssl.rst:2286 @@ -2801,10 +2818,10 @@ 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 " +"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 "" @@ -2820,8 +2837,8 @@ msgid "" "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`." +"and :meth:`SSLSocket.send` failures, and retry after another call " +"to :func:`~select.select`." msgstr "" #: library/ssl.rst:2346 @@ -2835,16 +2852,16 @@ msgstr "" #: library/ssl.rst:2352 msgid "" -"(of course, similar provisions apply when using other primitives such as :" -"func:`~select.poll`, or those in the :mod:`selectors` module)" +"(of course, similar provisions apply when using other primitives such " +"as :func:`~select.poll`, or those in the :mod:`selectors` module)" msgstr "" #: library/ssl.rst:2355 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::" +"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 "" #: library/ssl.rst:2360 @@ -2863,9 +2880,10 @@ msgstr "" 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." +"the :mod:`selectors` module and " +"handles :exc:`SSLWantWriteError`, :exc:`SSLWantReadError` " +"and :exc:`BlockingIOError` exceptions. It runs the SSL handshake " +"asynchronously as well." msgstr "" #: library/ssl.rst:2380 @@ -2874,8 +2892,8 @@ msgstr "" #: library/ssl.rst:2384 msgid "" -"Ever since the SSL module was introduced in Python 2.6, the :class:" -"`SSLSocket` class has provided two related but distinct areas of " +"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 "" @@ -2900,11 +2918,11 @@ 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." +"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 "" #: library/ssl.rst:2406 @@ -3033,8 +3051,8 @@ msgstr "" #: library/ssl.rst:2454 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." +"that are in violation of the protocol are reported via " +"the :exc:`SSLEOFError` exception." msgstr "" #: library/ssl.rst:2458 @@ -3045,9 +3063,9 @@ msgstr "" #: library/ssl.rst:2461 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." +"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 "" #: library/ssl.rst:2465 @@ -3057,15 +3075,16 @@ msgstr "" #: library/ssl.rst:2467 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." +"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 "" #: library/ssl.rst:2472 msgid "" -":class:`SSLObject` instances must be created with :meth:`~SSLContext." -"wrap_bio`. In earlier versions, it was possible to create instances " -"directly. This was never documented or officially supported." +":class:`SSLObject` instances must be created " +"with :meth:`~SSLContext.wrap_bio`. In earlier versions, it was possible to " +"create instances directly. This was never documented or officially supported." msgstr "" #: library/ssl.rst:2478 @@ -3135,11 +3154,11 @@ msgstr "" #: library/ssl.rst:2540 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." +"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 "" #: library/ssl.rst:2547 @@ -3159,16 +3178,16 @@ msgstr "" #: library/ssl.rst:2556 msgid "" -"If a client certificate is needed for the connection, it can be added with :" -"meth:`SSLContext.load_cert_chain`." +"If a client certificate is needed for the connection, it can be added " +"with :meth:`SSLContext.load_cert_chain`." msgstr "" #: library/ssl.rst:2559 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." +"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 "" #: library/ssl.rst:2565 @@ -3181,23 +3200,23 @@ msgstr "" #: library/ssl.rst:2570 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 the 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. This common " -"check is automatically performed when :attr:`SSLContext.check_hostname` is " -"enabled." +"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 " +"the 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. This common check is automatically performed " +"when :attr:`SSLContext.check_hostname` is enabled." msgstr "" #: library/ssl.rst:2582 msgid "" -"Hostname matchings is now performed by OpenSSL. Python no longer uses :func:" -"`match_hostname`." +"Hostname matchings is now performed by OpenSSL. Python no longer " +"uses :func:`match_hostname`." msgstr "" #: library/ssl.rst:2586 @@ -3216,9 +3235,9 @@ msgstr "" 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." +"recommended to use :const:`PROTOCOL_TLS_CLIENT` " +"or :const:`PROTOCOL_TLS_SERVER` as the protocol version. SSLv2 and SSLv3 are " +"disabled by default." msgstr "" #: library/ssl.rst:2602 @@ -3231,9 +3250,9 @@ msgstr "" #: library/ssl.rst:2607 msgid "" "The SSL context created above will only allow TLSv1.3 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." +"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 "" #: library/ssl.rst:2614 @@ -3243,14 +3262,14 @@ msgstr "" #: library/ssl.rst:2616 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." +"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 "" #: library/ssl.rst:2627 @@ -3281,9 +3300,9 @@ msgstr "" #: library/ssl.rst:2648 msgid "" "TLS 1.3 uses a disjunct set of cipher suites. All AES-GCM and ChaCha20 " -"cipher suites are enabled by default. The method :meth:`SSLContext." -"set_ciphers` cannot enable or disable any TLS 1.3 ciphers yet, but :meth:" -"`SSLContext.get_ciphers` returns them." +"cipher suites are enabled by default. The " +"method :meth:`SSLContext.set_ciphers` cannot enable or disable any TLS 1.3 " +"ciphers yet, but :meth:`SSLContext.get_ciphers` returns them." msgstr "" #: library/ssl.rst:2652 diff --git a/library/stat.po b/library/stat.po index 3407df959..5a93c4689 100644 --- a/library/stat.po +++ b/library/stat.po @@ -214,11 +214,12 @@ 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." +"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 "" #: library/stat.rst:207 @@ -279,8 +280,8 @@ msgstr "" #: library/stat.rst:262 msgid "" -"The following flags can also be used in the *mode* argument of :func:`os." -"chmod`:" +"The following flags can also be used in the *mode* argument " +"of :func:`os.chmod`:" msgstr "" #: library/stat.rst:266 @@ -355,9 +356,9 @@ msgstr "" #: 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." +"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 "" #: library/stat.rst:341 @@ -374,8 +375,8 @@ msgstr "" #: library/stat.rst:351 msgid "" -"The following flags can be used in the *flags* argument of :func:`os." -"chflags`:" +"The following flags can be used in the *flags* argument " +"of :func:`os.chflags`:" msgstr "" #: library/stat.rst:355 @@ -423,10 +424,10 @@ msgstr "" #: 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." +"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 "" #: library/stat.rst:429 diff --git a/library/statistics.po b/library/statistics.po index f94304295..2aaa9068b 100644 --- a/library/statistics.po +++ b/library/statistics.po @@ -41,13 +41,13 @@ msgstr "" #: library/statistics.rst:31 msgid "" -"Unless explicitly noted, 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. Collections with a mix of 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, for " -"example: ``map(float, input_data)``." +"Unless explicitly noted, 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. Collections with a mix of " +"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, for example: ``map(float, input_data)``." msgstr "" #: library/statistics.rst:39 @@ -328,8 +328,8 @@ msgstr "" #: library/statistics.rst:166 msgid "" -"This runs faster than the :func:`mean` function and it always returns a :" -"class:`float`. The *data* may be a sequence or iterable. If the input " +"This runs faster than the :func:`mean` function and it always returns " +"a :class:`float`. The *data* may be a sequence or iterable. If the input " "dataset is empty, raises a :exc:`StatisticsError`." msgstr "" @@ -356,8 +356,8 @@ msgstr "" #: library/statistics.rst:186 msgid "" -"If *weights* is supplied, it must be the same length as the *data* or a :exc:" -"`ValueError` will be raised." +"If *weights* is supplied, it must be the same length as the *data* or " +"a :exc:`ValueError` will be raised." msgstr "" #: library/statistics.rst:259 @@ -501,8 +501,9 @@ msgstr "" #: library/statistics.rst:294 msgid "" -"Return the low median of numeric data. If *data* is empty, :exc:" -"`StatisticsError` is raised. *data* can be a sequence or iterable." +"Return the low median of numeric data. If *data* is " +"empty, :exc:`StatisticsError` is raised. *data* can be a sequence or " +"iterable." msgstr "" #: library/statistics.rst:297 @@ -883,9 +884,9 @@ msgstr "" #: library/statistics.rst:579 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." +"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 "" #: library/statistics.rst:585 @@ -965,8 +966,8 @@ msgstr "" #: library/statistics.rst:640 msgid "" -"Both inputs must be of the same length (no less than two), otherwise :exc:" -"`StatisticsError` is raised." +"Both inputs must be of the same length (no less than two), " +"otherwise :exc:`StatisticsError` is raised." msgstr "" #: library/statistics.rst:645 @@ -1049,8 +1050,8 @@ msgstr "" #: library/statistics.rst:712 msgid "" -"Return the slope and intercept of `simple linear regression `_ parameters estimated using " +"Return the slope and intercept of `simple linear regression `_ parameters estimated using " "ordinary least squares. Simple linear regression describes the relationship " "between an independent variable *x* and a dependent variable *y* in terms of " "this linear function:" @@ -1071,8 +1072,8 @@ msgstr "" #: library/statistics.rst:726 msgid "" "Both inputs must be of the same length (no less than two), and the " -"independent variable *x* cannot be constant; otherwise a :exc:" -"`StatisticsError` is raised." +"independent variable *x* cannot be constant; otherwise " +"a :exc:`StatisticsError` is raised." msgstr "" #: library/statistics.rst:730 @@ -1150,15 +1151,15 @@ msgstr "" #: library/statistics.rst:788 msgid "" ":class:`NormalDist` is a tool for creating and manipulating normal " -"distributions of a `random variable `_. It is a class that treats the mean and " -"standard deviation of data measurements as a single entity." +"distributions of a `random variable `_. It is a class that treats the mean and standard " +"deviation of data measurements as a single entity." msgstr "" #: library/statistics.rst:794 msgid "" -"Normal distributions arise from the `Central Limit Theorem `_ and have a wide range of " +"Normal distributions arise from the `Central Limit Theorem `_ and have a wide range of " "applications in statistics." msgstr "" @@ -1260,8 +1261,8 @@ msgstr "" msgid "" "Compute the inverse cumulative distribution function, also known as the " "`quantile function `_ or " -"the `percent-point `_ " +"the `percent-point `_ " "function. Mathematically, it is written ``x : P(X <= x) = p``." msgstr "" @@ -1325,8 +1326,8 @@ msgid "" "Since normal distributions arise from additive effects of independent " "variables, it is possible to `add and subtract two independent normally " "distributed random variables `_ represented as instances of :" -"class:`NormalDist`. For example:" +"Sum_of_normally_distributed_random_variables>`_ represented as instances " +"of :class:`NormalDist`. For example:" msgstr "" #: library/statistics.rst:935 @@ -1461,8 +1462,8 @@ msgstr "" #: library/statistics.rst:1043 msgid "" -"Wikipedia has a `nice example of a Naive Bayesian Classifier `_. The " +"Wikipedia has a `nice example of a Naive Bayesian Classifier `_. The " "challenge is to predict a person's gender from measurements of normally " "distributed features including height, weight, and foot size." msgstr "" diff --git a/library/stdtypes.po b/library/stdtypes.po index 128b201c9..f96a0ae50 100644 --- a/library/stdtypes.po +++ b/library/stdtypes.po @@ -58,8 +58,8 @@ msgstr "" "Bazı işlemler birkaç nesne türü tarafından desteklenir; özellikle, tüm " "nesneler eşitlik için karşılaştırılabilir, doğruluk değeri için test " "edilebilir ve bir dizeye dönüştürülebilir (:func:`repr` fonksiyonu veya " -"hafif farklı olan :func:`str` fonksiyonu ile). İkinci fonksiyon, bir nesne :" -"func:`print` ile yazdırıldığında dolaylı olarak kullanılır." +"hafif farklı olan :func:`str` fonksiyonu ile). İkinci fonksiyon, bir " +"nesne :func:`print` ile yazdırıldığında dolaylı olarak kullanılır." #: library/stdtypes.rst:32 msgid "Truth Value Testing" @@ -67,8 +67,8 @@ msgstr "Doğruluk Değeri Testi" #: 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." +"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." msgstr "" "Herhangi bir nesne, :keyword:`if` veya :keyword:`while` koşulunda veya " "aşağıdaki Boolean işlemlerinin işleneni olarak kullanımında doğruluk değeri " @@ -77,15 +77,15 @@ msgstr "" #: library/stdtypes.rst:46 #, fuzzy msgid "" -"By default, an object is considered true unless its class defines either a :" -"meth:`~object.__bool__` method that returns ``False`` or a :meth:`~object." -"__len__` method that returns zero, when called with the object. [1]_ Here " -"are most of the built-in objects considered false:" +"By default, an object is considered true unless its class defines either " +"a :meth:`~object.__bool__` method that returns ``False`` or " +"a :meth:`~object.__len__` method that returns zero, when called with the " +"object. [1]_ Here are most of the built-in objects considered false:" msgstr "" "Varsayılan olarak, bir nesne, sınıfı \"False\" döndüren bir :meth:`__bool__` " -"metodunu veya nesneyle birlikte çağrıldığında sıfır döndüren bir :meth:" -"`__len__` metodunu tanımlamadıkça doğru kabul edilir. [1]_ Yanlış olarak " -"kabul edilen yerleşik nesnelerin çoğu:" +"metodunu veya nesneyle birlikte çağrıldığında sıfır döndüren " +"bir :meth:`__len__` metodunu tanımlamadıkça doğru kabul edilir. [1]_ Yanlış " +"olarak kabul edilen yerleşik nesnelerin çoğu:" #: library/stdtypes.rst:56 #, fuzzy @@ -315,8 +315,8 @@ msgstr "" "olarak karşılaştırılmaz. ``==`` operatörü her zaman tanımlanır, ancak bazı " "nesne türleri için (örneğin, sınıf nesneleri) :keyword:`is` ile eş değerdir. " "``<``, ``<=``, ``>`` ve ``>=`` operatörleri yalnızca anlamlı oldukları yerde " -"tanımlanır; örneğin, argümanlardan biri karmaşık bir sayı olduğunda bir :exc:" -"`TypeError` hatası oluştururlar." +"tanımlanır; örneğin, argümanlardan biri karmaşık bir sayı olduğunda " +"bir :exc:`TypeError` hatası oluştururlar." #: library/stdtypes.rst:181 msgid "" @@ -330,17 +330,18 @@ msgstr "" 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:`~object.__lt__`, :meth:`~object.__le__`, :meth:`~object." -"__gt__`, and :meth:`~object.__ge__` (in general, :meth:`~object.__lt__` and :" -"meth:`~object.__eq__` are sufficient, if you want the conventional meanings " -"of the comparison operators)." +"the " +"methods :meth:`~object.__lt__`, :meth:`~object.__le__`, :meth:`~object.__gt__`, " +"and :meth:`~object.__ge__` (in general, :meth:`~object.__lt__` " +"and :meth:`~object.__eq__` are sufficient, if you want the conventional " +"meanings of the comparison operators)." msgstr "" "Bir sınıfın örnekleri, sınıf yeterli metotları tanımlamadıkça, aynı sınıfın " -"diğer örneklerine veya diğer nesne türlerine göre sıralanamaz :meth:`~object." -"__lt__`, :meth:`~object.__le__` , :meth:`~object.__gt__` ve :meth:`~object." -"__ge__` (karşılaştırma operatörlerin geleneksel anlamlarını istiyorsanız, :" -"meth:`~object.__lt__` ve :meth:`~object.__eq__` genellikle yeterli " -"olacaktır)." +"diğer örneklerine veya diğer nesne türlerine göre " +"sıralanamaz :meth:`~object.__lt__`, :meth:`~object.__le__` , :meth:`~object.__gt__` " +"ve :meth:`~object.__ge__` (karşılaştırma operatörlerin geleneksel " +"anlamlarını istiyorsanız, :meth:`~object.__lt__` ve :meth:`~object.__eq__` " +"genellikle yeterli olacaktır)." #: library/stdtypes.rst:191 msgid "" @@ -355,13 +356,13 @@ msgstr "" #: library/stdtypes.rst:199 #, fuzzy msgid "" -"Two more operations with the same syntactic priority, :keyword:`in` and :" -"keyword:`not in`, are supported by types that are :term:`iterable` or " +"Two more operations with the same syntactic priority, :keyword:`in` " +"and :keyword:`not in`, are supported by types that are :term:`iterable` or " "implement the :meth:`~object.__contains__` method." msgstr "" -"Aynı söz dizimsel önceliğe sahip iki işlem daha, :keyword:`in` ve :keyword:" -"`not in`, :term:`iterable` olan veya :meth:`__contains__` metodunu uygulayan " -"türler tarafından desteklenir." +"Aynı söz dizimsel önceliğe sahip iki işlem daha, :keyword:`in` " +"ve :keyword:`not in`, :term:`iterable` olan veya :meth:`__contains__` " +"metodunu uygulayan türler tarafından desteklenir." #: library/stdtypes.rst:206 msgid "Numeric Types --- :class:`int`, :class:`float`, :class:`complex`" @@ -375,12 +376,13 @@ msgid "" "subtype of integers. Integers have unlimited precision. Floating-point " "numbers are usually implemented using :c:expr:`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 the additional " -"numeric types :mod:`fractions.Fraction`, for rationals, and :mod:`decimal." -"Decimal`, for floating-point numbers with user-definable precision.)" +"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 the additional numeric types :mod:`fractions.Fraction`, for " +"rationals, and :mod:`decimal.Decimal`, for floating-point numbers with user-" +"definable precision.)" msgstr "" "Üç farklı sayısal tür vardır: :dfn:`integers`, :dfn:`floating point " "numbers`, ve :dfn:`complex numbers`. Ayrıca, Booleanlar tam sayıların bir " @@ -390,9 +392,10 @@ msgstr "" "hakkında bilgi :data:`sys.float_info` içinde mevcuttur. Karmaşık sayıların " "her biri bir gerçel sayı olan gerçek ve sanal birer kısımları vardır. Bu " "parçaları *z* karmaşık sayısından ayıklamak için ``z.real`` ve ``z.imag`` " -"kullanın. (Standart kütüphane, rasyonel sayılar için :mod:`fractions." -"Fraction` ve kullanıcı tarafından tanımlanabilen hassasiyete sahip gerçel " -"sayılar için :mod:`decimal.Decimal` ek sayısal türlerini içerir.)" +"kullanın. (Standart kütüphane, rasyonel sayılar " +"için :mod:`fractions.Fraction` ve kullanıcı tarafından tanımlanabilen " +"hassasiyete sahip gerçel sayılar için :mod:`decimal.Decimal` ek sayısal " +"türlerini içerir.)" #: library/stdtypes.rst:238 #, fuzzy @@ -691,8 +694,8 @@ msgid "" "DerivedNumericType.txt>`_ for a complete list of code points with the ``Nd`` " "property." msgstr "" -"``Nd`` özelliğine sahip kod noktalarının tam listesi için https://www." -"unicode.org/Public/14.0.0/ucd/extracted/DerivedNumericType.txt adresine " +"``Nd`` özelliğine sahip kod noktalarının tam listesi için https://" +"www.unicode.org/Public/14.0.0/ucd/extracted/DerivedNumericType.txt adresine " "bakın." #: library/stdtypes.rst:362 @@ -858,8 +861,8 @@ msgstr "" #: library/stdtypes.rst:446 msgid "" "Performing these calculations with at least one extra sign extension bit in " -"a finite two's complement representation (a working bit-width of ``1 + max(x." -"bit_length(), y.bit_length())`` or more) is sufficient to get the same " +"a finite two's complement representation (a working bit-width of ``1 + " +"max(x.bit_length(), y.bit_length())`` or more) is sufficient to get the same " "result as if there were an infinite number of sign bits." msgstr "" "Bu hesaplamaları, sonlu ikinin tümleyen temsilinde en az bir ekstra işaret " @@ -901,8 +904,8 @@ 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``." +"logarithm, then ``k = 1 + int(log(abs(x), 2))``. If ``x`` is zero, then " +"``x.bit_length()`` returns ``0``." msgstr "" "Daha doğrusu, ``x`` sıfırdan farklıysa, ``x.bit_length()``, ``2**(k-1) <= " "abs(x) < 2**k`` olacak şekilde benzersiz ``k`` pozitif tam sayısıdır. Aynı " @@ -953,9 +956,9 @@ msgstr "Bir tam sayıyı temsil eden bir bayt dizisi döndürür." #: library/stdtypes.rst:519 msgid "" -"The integer is represented using *length* bytes, and defaults to 1. An :exc:" -"`OverflowError` is raised if the integer is not representable with the given " -"number of bytes." +"The integer is represented using *length* bytes, and defaults to 1. " +"An :exc:`OverflowError` is raised if the integer is not representable with " +"the given number of bytes." msgstr "" "Tam sayı, *length* bayt kullanılarak temsil edilir ve varsayılan olarak " "birdir. Tam sayı verilen bayt sayısıyla gösterilemezse :exc:`OverflowError` " @@ -1040,8 +1043,8 @@ msgid "" "integer, and defaults to ``\"big\"``. 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." +"array. To request the native byte order of the host system, " +"use :data:`sys.byteorder` as the byte order value." msgstr "" "*byteorder* argümanı, tam sayıyı temsil etmek için kullanılan bayt sırasını " "belirler. *byteorder* ``\"big\"`` ise, en önemli bayt, bayt dizisinin " @@ -1091,8 +1094,8 @@ msgstr "" #: library/stdtypes.rst:618 msgid "" -"Returns ``True``. Exists for duck type compatibility with :meth:`float." -"is_integer`." +"Returns ``True``. Exists for duck type compatibility " +"with :meth:`float.is_integer`." msgstr "" #: library/stdtypes.rst:623 @@ -1111,8 +1114,8 @@ msgstr "" #, fuzzy msgid "" "Return a pair of integers whose ratio is exactly equal to the original " -"float. The ratio is in lowest terms and has a positive denominator. Raises :" -"exc:`OverflowError` on infinities and a :exc:`ValueError` on NaNs." +"float. The ratio is in lowest terms and has a positive denominator. " +"Raises :exc:`OverflowError` on infinities and a :exc:`ValueError` on NaNs." msgstr "" "Oranı tam olarak orijinal gerçel sayıya eşit ve pozitif bir paydaya sahip " "bir çift tam sayı döndürür. Sonsuzluklarda :exc:`OverflowError` ve NaN'lerde " @@ -1171,11 +1174,12 @@ msgstr "" #: library/stdtypes.rst:669 msgid "" -"Note that :meth:`float.hex` is an instance method, while :meth:`float." -"fromhex` is a class method." +"Note that :meth:`float.hex` is an instance method, " +"while :meth:`float.fromhex` is a class method." msgstr "" -":meth:`float.hex` 'in bir örnek (instance) metodu olduğunu, :meth:`float." -"fromhex` 'in ise bir sınıf (class) metodu olduğunu unutmayın." +":meth:`float.hex` 'in bir örnek (instance) metodu " +"olduğunu, :meth:`float.fromhex` 'in ise bir sınıf (class) metodu olduğunu " +"unutmayın." #: library/stdtypes.rst:672 msgid "A hexadecimal string takes the form::" @@ -1204,11 +1208,11 @@ msgstr "" "birlikte ondalık tam sayıdır. Büyük/küçük harf önemli değildir ve tam sayı " "veya kesirde en az bir onaltılık basamak olmalıdır. Bu söz dizimi, C99 " "standardının 6.4.4.2 bölümünde belirtilen söz dizimine ve ayrıca Java " -"1.5'ten itibaren kullanılan söz dizimine benzer. Özellikle, :meth:`float." -"hex` 'in çıktısı, C veya Java kodunda bir onaltılık gerçel değişmezi olarak " -"kullanılabilir ve C'nin ``%a`` biçim karakteri veya Java'nın ``Double." -"toHexString`` 'i tarafından üretilen onaltılık dizeler :meth:`float.fromhex` " -"tarafından kabul edilir." +"1.5'ten itibaren kullanılan söz dizimine benzer. " +"Özellikle, :meth:`float.hex` 'in çıktısı, C veya Java kodunda bir onaltılık " +"gerçel değişmezi olarak kullanılabilir ve C'nin ``%a`` biçim karakteri veya " +"Java'nın ``Double.toHexString`` 'i tarafından üretilen onaltılık " +"dizeler :meth:`float.fromhex` tarafından kabul edilir." #: library/stdtypes.rst:689 msgid "" @@ -1250,29 +1254,31 @@ msgstr "Sayısal türlerin hashlemesi" #, fuzzy 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:`~object." -"__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:`~sys.hash_info." -"modulus` attribute of :data:`sys.hash_info`." +"that ``hash(x) == hash(y)`` whenever ``x == y`` (see " +"the :meth:`~object.__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:`~sys.hash_info.modulus` attribute " +"of :data:`sys.hash_info`." msgstr "" "Muhtemelen farklı türlerdeki ``x`` ve ``y`` sayıları için, ``x == y`` " -"olduğunda ``hash(x) == hash(y)`` olması bir gerekliliktir (bkz. :meth:" -"`~object.__hash__`). Çeşitli sayısal türler arasında uygulama kolaylığı ve " -"verimlilik için (:class:`int`, :class:`float`, :class:`decimal.Decimal` ve :" -"class:`fractions.Fraction` dahil) Python'un sayısal türler için hash'i, " +"olduğunda ``hash(x) == hash(y)`` olması bir gerekliliktir " +"(bkz. :meth:`~object.__hash__`). Çeşitli sayısal türler arasında uygulama " +"kolaylığı ve verimlilik için " +"(:class:`int`, :class:`float`, :class:`decimal.Decimal` " +"ve :class:`fractions.Fraction` dahil) Python'un sayısal türler için hash'i, " "herhangi bir rasyonel sayı için tanımlanmış tek bir matematiksel fonksiyona " "dayanır ve bu nedenle :class:`int` ve :class:`fractions.Fraction` 'ın tüm " "örnekleri ve :class:`float` ve :class:`decimal.Decimal` öğelerinin tüm sonlu " "örnekleri için geçerlidir. Esasen, bu fonksiyon sabit bir asal sayı olan " -"``P`` için ``reduction modulo`` ``P`` ile verilir. ``P`` değeri Python'a :" -"data:`sys.hash_info` 'nun :attr:`modulus` özelliği olarak sunulur." +"``P`` için ``reduction modulo`` ``P`` ile verilir. ``P`` değeri " +"Python'a :data:`sys.hash_info` 'nun :attr:`modulus` özelliği olarak sunulur." #: library/stdtypes.rst:726 msgid "" @@ -1330,10 +1336,11 @@ msgstr "" #, fuzzy 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``." +"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 "" "Bir :class:`complex` sayı ``z`` için, gerçek ve sanal parçaların hash " "değerleri, ``hash(z.real) + sys.hash_info.imag * hash(z.imag)`` , ``reduced " @@ -1344,12 +1351,12 @@ msgstr "" #: library/stdtypes.rst:756 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`::" +"the built-in hash, for computing the hash of a rational " +"number, :class:`float`, or :class:`complex`::" msgstr "" -"Yukarıdaki kuralları açıklığa kavuşturmak için, :class:`float` veya :class:" -"`complex` olan rasyonel bir sayının ``hash`` 'ini hesaplamak için gömülü " -"``hash`` 'e eş değer örnek Python kodu::" +"Yukarıdaki kuralları açıklığa kavuşturmak için, :class:`float` " +"veya :class:`complex` olan rasyonel bir sayının ``hash`` 'ini hesaplamak " +"için gömülü ``hash`` 'e eş değer örnek Python kodu::" #: library/stdtypes.rst:761 msgid "" @@ -1393,8 +1400,8 @@ msgid "" "def hash_complex(z):\n" " \"\"\"Compute the hash of a complex number z.\"\"\"\n" "\n" -" hash_value = hash_float(z.real) + sys.hash_info.imag * hash_float(z." -"imag)\n" +" hash_value = hash_float(z.real) + sys.hash_info.imag * " +"hash_float(z.imag)\n" " # do a signed reduction modulo 2**sys.hash_info.width\n" " M = 2**(sys.hash_info.width - 1)\n" " hash_value = (hash_value & (M - 1)) - (hash_value & M)\n" @@ -1461,8 +1468,8 @@ msgstr "" #: library/stdtypes.rst:858 msgid "" -"One method needs to be defined for container objects to provide :term:" -"`iterable` support:" +"One method needs to be defined for container objects to " +"provide :term:`iterable` support:" msgstr "" "Container nesnelerinin :term:`iterable` desteği sağlaması için bir metodun " "tanımlanması gerekir:" @@ -1474,9 +1481,9 @@ msgid "" "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." +"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 "" "Bir :term:`iterator` nesnesi döndürür. Nesnenin aşağıda açıklanan " "yineleyici protokolünü desteklemesi gerekir. Bir container, farklı yineleme " @@ -1484,8 +1491,8 @@ msgstr "" "istemek için ek yöntemler sağlanabilir. (Birden çok yineleme biçimini " "destekleyen bir nesneye örnek olarak hem genişlik öncelikli hem de derinlik " "öncelikli geçişi destekleyen bir ağaç yapısı verilebilir.) Bu metot, Python/" -"C API'sindeki Python nesneleri için tür yapısının :c:member:`~PyTypeObject." -"tp_iter` yuvasına karşılık gelir." +"C API'sindeki Python nesneleri için tür " +"yapısının :c:member:`~PyTypeObject.tp_iter` yuvasına karşılık gelir." #: library/stdtypes.rst:874 msgid "" @@ -1498,9 +1505,10 @@ msgstr "" #: library/stdtypes.rst:880 msgid "" "Return the :term:`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." +"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 "" ":term:`iterator` nesnesinin kendisini döndürür. Bu, hem containerların hem " "de yineleyicilerin :keyword:`for` ve :keyword:`in` ifadeleriyle birlikte " @@ -1515,10 +1523,10 @@ msgid "" "the :c:member:`~PyTypeObject.tp_iternext` slot of the type structure for " "Python objects in the Python/C API." msgstr "" -":term:`iterator` 'den sonraki öğeyi döndürür. Başka öğe yoksa, :exc:" -"`StopIteration` hatasını verir. Bu metot, Python/C API'sindeki Python " -"nesneleri için tür yapısının :c:member:`~PyTypeObject.tp_iternext` yuvasına " -"karşılık gelir." +":term:`iterator` 'den sonraki öğeyi döndürür. Başka öğe " +"yoksa, :exc:`StopIteration` hatasını verir. Bu metot, Python/C API'sindeki " +"Python nesneleri için tür yapısının :c:member:`~PyTypeObject.tp_iternext` " +"yuvasına karşılık gelir." #: library/stdtypes.rst:894 msgid "" @@ -1534,8 +1542,8 @@ msgstr "" #: library/stdtypes.rst:899 msgid "" -"Once an iterator's :meth:`~iterator.__next__` method raises :exc:" -"`StopIteration`, it must continue to do so on subsequent calls. " +"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 "" "Bir yineleyicinin :meth:`~iterator.__next__` metodu :exc:`StopIteration` " @@ -1559,10 +1567,10 @@ msgid "" msgstr "" "Python'un :term:`generator`\\s, yineleyici protokolünü uygulamak için uygun " "bir yol sağlar. Bir container nesnesinin :meth:`__iter__` metodu bir " -"oluşturucu olarak uygulanırsa, otomatik olarak :meth:`__iter__` ve :meth:" -"`~generator.__next__` metotlarını sağlayan bir yineleyici nesne (teknik " -"olarak bir oluşturucu nesnesi) döndürür. Oluşturucular hakkında daha fazla " -"bilgi :ref:`the documentation for the yield expression ` " +"oluşturucu olarak uygulanırsa, otomatik olarak :meth:`__iter__` " +"ve :meth:`~generator.__next__` metotlarını sağlayan bir yineleyici nesne " +"(teknik olarak bir oluşturucu nesnesi) döndürür. Oluşturucular hakkında daha " +"fazla bilgi :ref:`the documentation for the yield expression ` " "adresinde bulunabilir." #: library/stdtypes.rst:921 @@ -1576,9 +1584,9 @@ msgid "" "` and :ref:`text strings ` are described in dedicated " "sections." msgstr "" -"Üç temel dizi türü vardır: listeler, demetler ve aralık nesneleri. :ref:" -"`binary data ` ve :ref:`text strings ` 'in işlenmesi " -"için uyarlanmış ek dizi türleri, özel bölümlerde açıklanmıştır." +"Üç temel dizi türü vardır: listeler, demetler ve aralık " +"nesneleri. :ref:`binary data ` ve :ref:`text strings ` " +"'in işlenmesi için uyarlanmış ek dizi türleri, özel bölümlerde açıklanmıştır." #: library/stdtypes.rst:932 msgid "Common Sequence Operations" @@ -1592,9 +1600,9 @@ msgid "" "sequence types." msgstr "" "Aşağıdaki tablodaki işlemler, hem değiştirilebilir hem de değiştirilemez " -"olan çoğu dizi türü tarafından desteklenir. :class:`collections.abc." -"Sequence` ABC, bu işlemleri özel dize türlerinde doğru şekilde uygulamayı " -"kolaylaştırmak için sağlanmıştır." +"olan çoğu dizi türü tarafından " +"desteklenir. :class:`collections.abc.Sequence` ABC, bu işlemleri özel dize " +"türlerinde doğru şekilde uygulamayı kolaylaştırmak için sağlanmıştır." #: library/stdtypes.rst:941 msgid "" @@ -1753,16 +1761,16 @@ msgstr "" "listeler, karşılık gelen öğeler ile sözlükbilimsel olarak karşılaştırılır. " "Bu, eşit karşılaştırma yapılabilmesi için her öğenin eşit olarak " "karşılaştırması gerektiği ve iki dizinin aynı türde ve aynı uzunlukta olması " -"gerektiği anlamına gelir. (Tüm ayrıntılar için dil referansındaki :ref:" -"`comparisons` bölümüne bakın.)" +"gerektiği anlamına gelir. (Tüm ayrıntılar için dil " +"referansındaki :ref:`comparisons` bölümüne bakın.)" #: library/stdtypes.rst:1010 msgid "" "Forward and reversed iterators over mutable sequences access values using an " "index. That index will continue to march forward (or backward) even if the " -"underlying sequence is mutated. The iterator terminates only when an :exc:" -"`IndexError` or a :exc:`StopIteration` is encountered (or when the index " -"drops below zero)." +"underlying sequence is mutated. The iterator terminates only when " +"an :exc:`IndexError` or a :exc:`StopIteration` is encountered (or when the " +"index drops below zero)." msgstr "" #: library/stdtypes.rst:1019 @@ -1886,9 +1894,9 @@ msgstr "" #: library/stdtypes.rst:1084 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" +"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 "" ":class:`str` nesnelerini birleştiriyorsanız, bir liste oluşturabilir ve " "sonunda :meth:`str.join` kullanabilir veya bir :class:`io.StringIO` örneğine " @@ -1896,15 +1904,16 @@ msgstr "" #: library/stdtypes.rst:1088 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" +"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 "" -":class:`bytes` nesnelerini birleştiriyorsanız, benzer şekilde :meth:`bytes." -"join` veya :class:`io.BytesIO` kullanabilir veya bir :class:`bytearray` " -"nesnesiyle yerinde birleştirme yapabilirsiniz. :class:`bytearray` nesneleri " -"değiştirilebilirdir ve verimli bir aşırı tahsis mekanizmasına sahiptir" +":class:`bytes` nesnelerini birleştiriyorsanız, benzer " +"şekilde :meth:`bytes.join` veya :class:`io.BytesIO` kullanabilir veya " +"bir :class:`bytearray` nesnesiyle yerinde birleştirme " +"yapabilirsiniz. :class:`bytearray` nesneleri değiştirilebilirdir ve verimli " +"bir aşırı tahsis mekanizmasına sahiptir" #: library/stdtypes.rst:1093 msgid "if concatenating :class:`tuple` objects, extend a :class:`list` instead" @@ -1949,8 +1958,8 @@ msgstr "Değiştirilemez Dizi Tipleri" #: library/stdtypes.rst:1122 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." +"not also implemented by mutable sequence types is support for " +"the :func:`hash` built-in." msgstr "" "Değiştirilemez dizi türlerinin genellikle uyguladığı ve aynı zamanda " "değişken dizi türleri tarafından uygulanmayan tek işlem, gömülü :func:`hash` " @@ -1959,12 +1968,12 @@ msgstr "" #: library/stdtypes.rst:1126 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." +"to be used as :class:`dict` keys and stored in :class:`set` " +"and :class:`frozenset` instances." msgstr "" -"Bu destek, :class:`tuple` örnekleri gibi değiştirilemez dizilerin :class:" -"`dict` anahtarları olarak kullanılmasına, :class:`set` ve :class:`frozenset` " -"örneklerinde saklanmasına izin verir." +"Bu destek, :class:`tuple` örnekleri gibi değiştirilemez " +"dizilerin :class:`dict` anahtarları olarak kullanılmasına, :class:`set` " +"ve :class:`frozenset` örneklerinde saklanmasına izin verir." #: library/stdtypes.rst:1130 #, fuzzy @@ -1972,8 +1981,8 @@ msgid "" "Attempting to hash an immutable sequence that contains unhashable values " "will result in :exc:`TypeError`." msgstr "" -"Hash edilemez değerler içeren değiştirilemez bir diziyi hashlemeye çalışmak :" -"exc:`TypeError` ile sonuçlanır." +"Hash edilemez değerler içeren değiştirilemez bir diziyi hashlemeye " +"çalışmak :exc:`TypeError` ile sonuçlanır." #: library/stdtypes.rst:1137 msgid "Mutable Sequence Types" @@ -2163,15 +2172,15 @@ msgstr "" 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`). :meth:`!copy` is not part of the :class:" -"`collections.abc.MutableSequence` ABC, but most concrete mutable sequence " -"classes provide it." +"as :class:`dict` and :class:`set`). :meth:`!copy` is not part of " +"the :class:`collections.abc.MutableSequence` ABC, but most concrete mutable " +"sequence classes provide it." msgstr "" ":meth:`clear` ve :meth:`!copy`, dilimleme işlemlerini desteklemeyen " "değiştirilebilir containerların (örneğin :class:`dict` ve :class:`set` gibi) " -"arayüzleriyle tutarlılık için dahil edilmiştir. :meth:`!copy`, :class:" -"`collections.abc.MutableSequence` ABC'nin bir parçası değildir, ancak çoğu " -"somut değiştirilebilir dizi sınıfı bunu sağlar." +"arayüzleriyle tutarlılık için dahil edilmiştir. :meth:`!" +"copy`, :class:`collections.abc.MutableSequence` ABC'nin bir parçası " +"değildir, ancak çoğu somut değiştirilebilir dizi sınıfı bunu sağlar." #: library/stdtypes.rst:1245 msgid ":meth:`clear` and :meth:`!copy` methods." @@ -2179,10 +2188,11 @@ msgstr ":meth:`clear` ve :meth:`!copy` metotları." #: library/stdtypes.rst:1249 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`." +"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 "" "*n* değeri bir tam sayıdır veya :meth:`~object.__index__` uygulayan bir " "nesnedir. *n* 'nin sıfır ve negatif değerleri diziyi temizler. Dizideki " @@ -2275,8 +2285,8 @@ msgstr "" #: library/stdtypes.rst:1298 msgid "" -":meth:`sort` accepts two arguments that can only be passed by keyword (:ref:" -"`keyword-only arguments `):" +":meth:`sort` accepts two arguments that can only be passed by keyword " +"(:ref:`keyword-only arguments `):" msgstr "" ":meth:`sort` yalnızca anahtar kelime tarafından iletilebilen iki argümanı " "kabul eder (:ref:`keyword-only arguments `):" @@ -2340,8 +2350,8 @@ msgstr "" msgid "" "For sorting examples and a brief sorting tutorial, see :ref:`sortinghowto`." msgstr "" -"Sıralama örnekleri ve kısa bir sıralama eğitimi için bkz. :ref:" -"`sortinghowto`." +"Sıralama örnekleri ve kısa bir sıralama eğitimi için " +"bkz. :ref:`sortinghowto`." #: library/stdtypes.rst:1328 msgid "" @@ -2364,14 +2374,14 @@ 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)." +"homogeneous data is needed (such as allowing storage in a :class:`set` " +"or :class:`dict` instance)." msgstr "" "Tuple'lar, tipik olarak heterojen veri koleksiyonlarını depolamak için " "kullanılan değiştirilemez dizilerdir (örneğin, gömülü :func:`enumerate` " "tarafından üretilen 2 tuple). Tuple'lar, değiştirilemez bir homojen veri " -"dizisinin gerekli olduğu durumlarda da kullanılır (bir :class:`set` veya :" -"class:`dict` örneğinde depolamaya izin vermek gibi)." +"dizisinin gerekli olduğu durumlarda da kullanılır (bir :class:`set` " +"veya :class:`dict` örneğinde depolamaya izin vermek gibi)." #: library/stdtypes.rst:1349 msgid "Tuples may be constructed in a number of ways:" @@ -2456,8 +2466,8 @@ msgstr "" #: library/stdtypes.rst:1392 msgid "" -"The arguments to the range constructor must be integers (either built-in :" -"class:`int` or any object that implements the :meth:`~object.__index__` " +"The arguments to the range constructor must be integers (either built-" +"in :class:`int` or any object that implements the :meth:`~object.__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." @@ -2499,8 +2509,8 @@ msgstr "" #: library/stdtypes.rst:1411 msgid "" "Ranges containing absolute values larger than :data:`sys.maxsize` are " -"permitted but some features (such as :func:`len`) may raise :exc:" -"`OverflowError`." +"permitted but some features (such as :func:`len`) may " +"raise :exc:`OverflowError`." msgstr "" ":data:`sys.maxsize` 'dan büyük mutlak değerler içeren aralıklara izin " "verilir, ancak bazı özellikler (:func:`len` gibi), :exc:`OverflowError` " @@ -2558,8 +2568,8 @@ msgstr "*step* parametresinin değeri (veya parametre sağlanmadıysa ``1``)" #: library/stdtypes.rst:1451 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 " +"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)." @@ -2592,15 +2602,15 @@ msgstr "" "Aralık nesnelerini ``==`` ve ``!=`` ile eşitlik açısından test etmek, " "bunları diziler olarak karşılaştırır. Yani, aynı değer dizisini temsil " "ediyorlarsa, iki aralık nesnesi eşit kabul edilir. (Eşit karşılaştıran iki " -"aralık nesnesinin farklı :attr:`~range.start`, :attr:`~range.stop` ve :attr:" -"`~range.step` niteliklerine sahip olabileceğini unutmayın, örneğin " +"aralık nesnesinin farklı :attr:`~range.start`, :attr:`~range.stop` " +"ve :attr:`~range.step` niteliklerine sahip olabileceğini unutmayın, örneğin " "``range(0) == range(2, 1, 3)`` veya ``range(0, 3, 2) == range(0, 4, 2)``.)" #: library/stdtypes.rst:1484 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." +"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 "" "Dizi ABC'sini uygular, Dilimleme ve negatif indekslemeyi destekler, Tüm " "öğeleri yinelemek yerine sabit zamanda üyelik için :class:`int` nesnelerini " @@ -2639,9 +2649,9 @@ msgstr "Metin Sırası Türü --- :class:`str`" #: library/stdtypes.rst:1514 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:" +"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 "" "Python'da metinsel veriler :class:`str` nesneleri veya :dfn:`strings` ile " "işlenir. Dizeler, Unicode kod noktalarının değişmez :ref:`dizgeleridir " @@ -2688,8 +2698,8 @@ msgid "" msgstr "" "Desteklenen kaçış dizileri ve çoğu kaçış dizisi işlemeyi devre dışı bırakan " "``r`` (\"raw\", Türkçesiyle \"ham\") ön eki dahil olmak üzere dize " -"değişmezinin çeşitli biçimleri hakkında daha fazla bilgi için bkz. :ref:" -"`strings`." +"değişmezinin çeşitli biçimleri hakkında daha fazla bilgi için " +"bkz. :ref:`strings`." #: library/stdtypes.rst:1534 msgid "" @@ -2710,13 +2720,13 @@ msgstr "" #: library/stdtypes.rst:1543 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." +"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 "" -"Değiştirilebilir bir dize türü de yoktur, ancak :meth:`str.join` veya :class:" -"`io.StringIO` birden çok parçadan dizeleri verimli bir şekilde oluşturmak " -"için kullanılabilir." +"Değiştirilebilir bir dize türü de yoktur, ancak :meth:`str.join` " +"veya :class:`io.StringIO` birden çok parçadan dizeleri verimli bir şekilde " +"oluşturmak için kullanılabilir." #: library/stdtypes.rst:1547 msgid "" @@ -2742,29 +2752,30 @@ msgstr "" #: library/stdtypes.rst:1563 #, fuzzy msgid "" -"If neither *encoding* nor *errors* is given, ``str(object)`` returns :meth:" -"`type(object).__str__(object) `, 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 :func:" -"`repr(object) `." +"If neither *encoding* nor *errors* is given, ``str(object)`` " +"returns :meth:`type(object).__str__(object) `, 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 :func:`repr(object) `." msgstr "" -"Ne *kodlama* ne de *hatalar* verilmezse, ``str(object)`` :meth:`object." -"__str__() ` döndürür; bu, *object* ifadesinin \"gayriresmi\" " -"veya güzel yazdırılabilir dize temsilidir. Dize nesneleri için bu, dizenin " -"kendisidir. *object*'in bir :meth:`~object.__str__` metodu yoksa, :func:" -"`str`, :meth:`repr(object) ` döndürmeye geri döner." +"Ne *kodlama* ne de *hatalar* verilmezse, " +"``str(object)`` :meth:`object.__str__() ` döndürür; bu, " +"*object* ifadesinin \"gayriresmi\" veya güzel yazdırılabilir dize " +"temsilidir. Dize nesneleri için bu, dizenin kendisidir. *object*'in " +"bir :meth:`~object.__str__` metodu yoksa, :func:`str`, :meth:`repr(object) " +"` döndürmeye geri döner." #: library/stdtypes.rst:1575 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 " +"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." +"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 "" "*kodlama* veya *hatalar* 'dan en az biri verilirse, *nesne* bir :term:`bytes-" "like object` olmalıdır (ör. :class:`bytes` veya :class:`bytearray`). Bu " @@ -2782,10 +2793,10 @@ msgid "" "string representation (see also the :option:`-b` command-line option to " "Python). For example::" msgstr "" -"Bir :class:`bytes` nesnesini *kodlama* veya *hatalar* argümanları olmadan :" -"func:`str` 'ye iletmek, gayriresmi dize temsilini döndürmenin ilk durumuna " -"girer (ayrıca bkz. Python için :option:`-b` komut satırı seçeneği). " -"Örneğin::" +"Bir :class:`bytes` nesnesini *kodlama* veya *hatalar* argümanları " +"olmadan :func:`str` 'ye iletmek, gayriresmi dize temsilini döndürmenin ilk " +"durumuna girer (ayrıca bkz. Python için :option:`-b` komut satırı " +"seçeneği). Örneğin::" #: library/stdtypes.rst:1589 msgid "" @@ -2795,15 +2806,16 @@ msgstr "" #: library/stdtypes.rst:1592 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." +"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 "" -"``str`` sınıfı ve metotları hakkında daha fazla bilgi için aşağıdaki :ref:" -"`textseq` ve :ref:`string-methods` bölümüne bakın. Biçimlendirilmiş " -"dizelerin çıktısını almak için :ref:`f-strings` ve :ref:`formatstrings` " -"bölümlerine bakın. Ayrıca, :ref:`stringservices` bölümüne de bakın." +"``str`` sınıfı ve metotları hakkında daha fazla bilgi için " +"aşağıdaki :ref:`textseq` ve :ref:`string-methods` bölümüne bakın. " +"Biçimlendirilmiş dizelerin çıktısını almak için :ref:`f-strings` " +"ve :ref:`formatstrings` bölümlerine bakın. Ayrıca, :ref:`stringservices` " +"bölümüne de bakın." #: library/stdtypes.rst:1604 msgid "String Methods" @@ -2821,18 +2833,18 @@ msgstr "" #, fuzzy 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`)." +"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 "" "Ayrıca dizeler, biri büyük ölçüde esneklik ve özelleştirme sağlayan ve " -"diğeri daha dar bir tür aralığını işleyen (bkz. :meth:`str.format`, :ref:" -"`formatstrings` ve :ref:`string-formatting`) ve doğru kullanımı biraz daha " -"zor olan C ``printf`` stili biçimlendirmesine dayanan iki dize biçimlendirme " -"stilini destekler, ancak genellikle işleyebileceği durumlar için daha " -"hızlıdır (:ref:`old-string-formatting`)." +"diğeri daha dar bir tür aralığını işleyen " +"(bkz. :meth:`str.format`, :ref:`formatstrings` ve :ref:`string-formatting`) " +"ve doğru kullanımı biraz daha zor olan C ``printf`` stili biçimlendirmesine " +"dayanan iki dize biçimlendirme stilini destekler, ancak genellikle " +"işleyebileceği durumlar için daha hızlıdır (:ref:`old-string-formatting`)." #: library/stdtypes.rst:1619 msgid "" @@ -2876,14 +2888,14 @@ 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\"``." +"already lowercase, :meth:`lower` would do nothing to " +"``'ß'``; :meth:`casefold` converts it to ``\"ss\"``." msgstr "" "Büyük harf katlama, harf küçültmeye (lowercasing) benzer ancak daha " "agresiftir, çünkü bir dizedeki tüm büyük/küçük harf ayrımlarını kaldırmayı " "amaçlar. Örneğin, Almanca küçük harf ``'ß'``, ``\"ss\"`` ile eş değerdir. " -"Zaten küçük harf olduğundan, :meth:`lower` ``'ß'`` için hiçbir şey yapmaz; :" -"meth:`casefold` onu ``\"ss\"`` biçimine dönüştürür." +"Zaten küçük harf olduğundan, :meth:`lower` ``'ß'`` için hiçbir şey " +"yapmaz; :meth:`casefold` onu ``\"ss\"`` biçimine dönüştürür." #: library/stdtypes.rst:1644 #, fuzzy @@ -2936,21 +2948,21 @@ msgid "" "*errors* controls how encoding errors are handled. If ``'strict'`` (the " "default), a :exc:`UnicodeError` exception is raised. Other possible values " "are ``'ignore'``, ``'replace'``, ``'xmlcharrefreplace'``, " -"``'backslashreplace'`` and any other name registered via :func:`codecs." -"register_error`. See :ref:`error-handlers` for details." +"``'backslashreplace'`` and any other name registered " +"via :func:`codecs.register_error`. See :ref:`error-handlers` for details." msgstr "" "*errors* kodlama hatalarının nasıl ele alınacağını kontrol eder. Eğer " "``'strict'`` (varsayılan) ise, bir :exc:`UnicodeError` istisnası " "oluşturulur. Diğer olası değerler ``'ignore'``, ``'replace'``, " -"``'xmlcharrefreplace'``, ``'backslashreplace'`` ve :func:`codecs." -"register_error` ile kaydedilen diğer isimlerdir. Ayrıntılar için :ref:`error-" -"handlers` bölümüne bakınız." +"``'xmlcharrefreplace'``, ``'backslashreplace'`` " +"ve :func:`codecs.register_error` ile kaydedilen diğer isimlerdir. Ayrıntılar " +"için :ref:`error-handlers` bölümüne bakınız." #: library/stdtypes.rst:1683 msgid "" "For performance reasons, the value of *errors* is not checked for validity " -"unless an encoding error actually occurs, :ref:`devmode` is enabled or a :" -"ref:`debug build ` is used." +"unless an encoding error actually occurs, :ref:`devmode` is enabled or " +"a :ref:`debug build ` is used." msgstr "" #: library/stdtypes.rst:2834 @@ -2959,8 +2971,8 @@ msgstr "" #: library/stdtypes.rst:2837 msgid "" -"The value of the *errors* argument is now checked in :ref:`devmode` and in :" -"ref:`debug mode `." +"The value of the *errors* argument is now checked in :ref:`devmode` and " +"in :ref:`debug mode `." msgstr "" "*errors* şimdi :ref:`devmode` ve :ref:`hata ayıklama modunda ` " "kontrol edilir." @@ -3017,8 +3029,8 @@ msgstr "" #: library/stdtypes.rst:1733 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::" +"position of *sub*. To check if *sub* is a substring or not, use " +"the :keyword:`in` operator::" msgstr "" ":meth:`~str.find` metodu yalnızca *sub* öğesinin konumunu bilmeniz " "gerekiyorsa kullanılmalıdır. *sub* 'ın bir alt dize olup olmadığını kontrol " @@ -3056,16 +3068,18 @@ msgstr "" #: library/stdtypes.rst:1757 msgid "" -"When formatting a number (:class:`int`, :class:`float`, :class:`complex`, :" -"class:`decimal.Decimal` and subclasses) with the ``n`` type (ex: ``'{:n}'." -"format(1234)``), the function temporarily sets the ``LC_CTYPE`` locale to " -"the ``LC_NUMERIC`` locale to decode ``decimal_point`` and ``thousands_sep`` " -"fields of :c:func:`localeconv` if they are non-ASCII or longer than 1 byte, " -"and the ``LC_NUMERIC`` locale is different than the ``LC_CTYPE`` locale. " -"This temporary change affects other threads." -msgstr "" -"Bir sayıyı (:class:`int`, :class:`float`, :class:`complex`, :class:`decimal." -"Decimal` ve alt sınıfları) ``n`` türüyle biçimlendirirken (örn: ``'{:n}'. " +"When formatting a number " +"(:class:`int`, :class:`float`, :class:`complex`, :class:`decimal.Decimal` " +"and subclasses) with the ``n`` type (ex: ``'{:n}'.format(1234)``), the " +"function temporarily sets the ``LC_CTYPE`` locale to the ``LC_NUMERIC`` " +"locale to decode ``decimal_point`` and ``thousands_sep`` fields " +"of :c:func:`localeconv` if they are non-ASCII or longer than 1 byte, and the " +"``LC_NUMERIC`` locale is different than the ``LC_CTYPE`` locale. This " +"temporary change affects other threads." +msgstr "" +"Bir sayıyı " +"(:class:`int`, :class:`float`, :class:`complex`, :class:`decimal.Decimal` ve " +"alt sınıfları) ``n`` türüyle biçimlendirirken (örn: ``'{:n}'. " "format(1234)``), işlev :c:func:`localeconv` öğesinin ``decimal_point`` ve " "``thousands_sep`` alanlarını ASCII değilse veya 1 bayttan uzunsa ve " "``LC_NUMERIC`` yerel ayarı ``LC_CTYPE`` yerel ayarından farklıysa kod çözmek " @@ -3103,8 +3117,8 @@ msgstr "" 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()``." +"alphanumeric if one of the following returns ``True``: ``c.isalpha()``, " +"``c.isdecimal()``, ``c.isdigit()``, or ``c.isnumeric()``." msgstr "" "Dizedeki tüm karakterler alfanümerikse ve en az bir karakter varsa ``True``, " "aksi takdirde ``False`` döndürür. Bir ``c`` karakteri, aşağıdakilerden biri " @@ -3116,12 +3130,12 @@ msgstr "" 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\", " +"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 section 4.10 'Letters, Alphabetic, and Ideographic' " -"of the Unicode Standard `_." +"of the Unicode Standard `_." msgstr "" "Dizedeki tüm karakterler alfabetikse ve en az bir karakter varsa ``True``, " "aksi takdirde ``False`` döndürür. Alfabetik karakterler, Unicode karakter " @@ -3184,8 +3198,8 @@ msgid "" ":func:`keyword.iskeyword` can be used to test whether string ``s`` is a " "reserved identifier, such as :keyword:`def` and :keyword:`class`." msgstr "" -":func:`keyword.iskeyword` çağrısı yaparak ``s`` dizesinin :keyword:`def` ve :" -"keyword:`class` gibi ayrılmış bir tanımlayıcı olup olmadığını test eder." +":func:`keyword.iskeyword` çağrısı yaparak ``s`` dizesinin :keyword:`def` " +"ve :keyword:`class` gibi ayrılmış bir tanımlayıcı olup olmadığını test eder." #: library/stdtypes.rst:1850 msgid "Example: ::" @@ -3240,9 +3254,9 @@ msgstr "" "olarak kabul edilen ASCII boşluğu (0x20) dışında, Unicode karakter " "veritabanında \"Diğer\" veya \"Ayırıcı\" olarak tanımlanan karakterlerdir. " "(Bu bağlamda, yazdırılabilir karakterlerin :func:`repr` bir dize üzerinde " -"çağrıldığında kaçılmaması gereken karakterler olduğunu unutmayın. Bunun :" -"data:`sys.stdout` veya :data:`sys.stderr` dosyalarına yazılan dizelerin " -"işlenmesiyle bir ilgisi yoktur)" +"çağrıldığında kaçılmaması gereken karakterler olduğunu unutmayın. " +"Bunun :data:`sys.stdout` veya :data:`sys.stderr` dosyalarına yazılan " +"dizelerin işlenmesiyle bir ilgisi yoktur)" #: library/stdtypes.rst:1890 msgid "" @@ -3254,9 +3268,10 @@ msgstr "" #: library/stdtypes.rst:1893 msgid "" -"A character is *whitespace* if in the Unicode character database (see :mod:" -"`unicodedata`), either its general category is ``Zs`` (\"Separator, " -"space\"), or its bidirectional class is one of ``WS``, ``B``, or ``S``." +"A character is *whitespace* if in the Unicode character database " +"(see :mod:`unicodedata`), either its general category is ``Zs`` " +"(\"Separator, space\"), or its bidirectional class is one of ``WS``, ``B``, " +"or ``S``." msgstr "" "Bir karakter, genel kategorisi ``Zs`` (“Ayırıcı, boşluk”) ya da çift yönlü " "sınıfı ``WS``, ``B`` veya ``S``’den biri ise Unicode karakter veritabanında " @@ -3284,8 +3299,8 @@ msgstr "" #: library/stdtypes.rst:1926 msgid "" -"Return a string which is the concatenation of the strings in *iterable*. A :" -"exc:`TypeError` will be raised if there are any non-string values in " +"Return a string which is the concatenation of the strings in *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 "" @@ -3363,8 +3378,8 @@ msgstr "" #: library/stdtypes.rst:1972 msgid "" -"This static method returns a translation table usable for :meth:`str." -"translate`." +"This static method returns a translation table usable " +"for :meth:`str.translate`." msgstr "" "Bu statik yöntem :meth:`str.translate` için kullanılabilecek bir çeviri " "tablosu döndürür." @@ -3565,9 +3580,9 @@ 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 " -"as a single delimiter (to split with multiple delimiters, use :func:`re." -"split`). Splitting an empty string with a specified separator returns " -"``['']``." +"as a single delimiter (to split with multiple delimiters, " +"use :func:`re.split`). Splitting an empty string with a specified separator " +"returns ``['']``." msgstr "" "*sep* verilirse, ardışık sınırlayıcılar birlikte gruplanmaz ve boş dizeleri " "sınırladıkları kabul edilir (örneğin, ``'1,,2'.split(',')``, ``['1', '', " @@ -3833,8 +3848,8 @@ msgstr "" #: library/stdtypes.rst:2228 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``." +"and vice versa. Note that it is not necessarily true that " +"``s.swapcase().swapcase() == s``." msgstr "" "Büyük harf karakterleri küçük harfe dönüştürülmüş veya tam tersi yapılmış " "dizenin bir kopyasını döndürür. ``s.swapcase().swapcase() == s`` ifadesinin " @@ -3904,12 +3919,12 @@ msgstr "" 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:`~object.__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." +"indexing via :meth:`~object.__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 "" "Her karakterin verilen çeviri tablosu aracılığıyla eşlendiği dizgenin bir " "kopyasını döndürür. Tablo, :meth:`__getitem__` aracılığıyla indeksleme " @@ -4319,16 +4334,16 @@ msgstr "" #: library/stdtypes.rst:2515 msgid "" -"Binary Sequence Types --- :class:`bytes`, :class:`bytearray`, :class:" -"`memoryview`" +"Binary Sequence Types " +"--- :class:`bytes`, :class:`bytearray`, :class:`memoryview`" msgstr "" #: library/stdtypes.rst:2523 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." +"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 "" #: library/stdtypes.rst:2528 @@ -4711,22 +4726,22 @@ msgstr "" msgid "" "*errors* controls how decoding errors are handled. If ``'strict'`` (the " "default), a :exc:`UnicodeError` exception is raised. Other possible values " -"are ``'ignore'``, ``'replace'``, and any other name registered via :func:" -"`codecs.register_error`. See :ref:`error-handlers` for details." +"are ``'ignore'``, ``'replace'``, and any other name registered " +"via :func:`codecs.register_error`. See :ref:`error-handlers` for details." msgstr "" #: library/stdtypes.rst:2824 msgid "" "For performance reasons, the value of *errors* is not checked for validity " -"unless a decoding error actually occurs, :ref:`devmode` is enabled or a :ref:" -"`debug build ` is used." +"unless a decoding error actually occurs, :ref:`devmode` is enabled or " +"a :ref:`debug build ` is used." msgstr "" #: library/stdtypes.rst:2830 msgid "" -"Passing the *encoding* argument to :class:`str` allows decoding any :term:" -"`bytes-like object` directly, without needing to make a temporary :class:`!" -"bytes` or :class:`!bytearray` object." +"Passing the *encoding* argument to :class:`str` allows decoding " +"any :term:`bytes-like object` directly, without needing to make a " +"temporary :class:`!bytes` or :class:`!bytearray` object." msgstr "" #: library/stdtypes.rst:2845 @@ -4752,8 +4767,8 @@ msgstr "" #: library/stdtypes.rst:2866 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::" +"position of *sub*. To check if *sub* is a substring or not, use " +"the :keyword:`in` operator::" msgstr "" #: library/stdtypes.rst:2870 @@ -4780,10 +4795,10 @@ msgstr "" #: library/stdtypes.rst:2904 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." +"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 "" #: library/stdtypes.rst:2915 @@ -5277,10 +5292,10 @@ msgstr "" #: library/stdtypes.rst:3435 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." +"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 "" #: library/stdtypes.rst:3449 @@ -5377,8 +5392,8 @@ msgid "" "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." +"zero or more elements of *values*. The effect is similar to using " +"the :c:func:`sprintf` in the C language." msgstr "" #: library/stdtypes.rst:3564 @@ -5591,8 +5606,8 @@ msgstr "" #: library/stdtypes.rst:3840 msgid "" -"memoryview is now registered automatically with :class:`collections.abc." -"Sequence`" +"memoryview is now registered automatically " +"with :class:`collections.abc.Sequence`" msgstr "" #: library/stdtypes.rst:3844 @@ -5612,8 +5627,9 @@ msgstr "" #: library/stdtypes.rst:3855 msgid "" -"For the subset of :mod:`struct` format strings currently supported by :meth:" -"`tolist`, ``v`` and ``w`` are equal if ``v.tolist() == w.tolist()``::" +"For the subset of :mod:`struct` format strings currently supported " +"by :meth:`tolist`, ``v`` and ``w`` are equal if ``v.tolist() == " +"w.tolist()``::" msgstr "" #: library/stdtypes.rst:3858 @@ -5738,8 +5754,8 @@ msgstr "" #: library/stdtypes.rst:3948 msgid "" -":meth:`tolist` now supports all single character native formats in :mod:" -"`struct` module syntax as well as multi-dimensional representations." +":meth:`tolist` now supports all single character native formats " +"in :mod:`struct` module syntax as well as multi-dimensional representations." msgstr "" #: library/stdtypes.rst:3955 @@ -5766,8 +5782,8 @@ msgstr "" #: library/stdtypes.rst:3974 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 " +"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 "" @@ -5818,10 +5834,10 @@ msgstr "" #: library/stdtypes.rst:4013 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. " -"Note that all byte lengths may depend on the operating system." +"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. Note that all byte lengths may depend on the operating system." msgstr "" #: library/stdtypes.rst:4019 @@ -6063,15 +6079,15 @@ msgid "" "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.)" +"in :class:`dict`, :class:`list`, and :class:`tuple` classes, and " +"the :mod:`collections` module.)" msgstr "" "Bir :dfn:`set` nesnesi, farklı :term:`hashable` nesnelerinin sıralanmamış " "bir koleksiyonudur. Yaygın kullanımları arasında üyelik sınaması, bir " "diziden yinelenenlerin kaldırılması ve kesişim, birleşim, fark ve simetrik " "fark gibi matematiksel işlemlerin hesaplanması yer alır. (Diğer kapsayıcılar " -"için yerleşik :class:`dict`, :class:`list` ve :class:`tuple` sınıflarına ve :" -"mod:`collections` modülüne bakın)" +"için yerleşik :class:`dict`, :class:`list` ve :class:`tuple` sınıflarına " +"ve :mod:`collections` modülüne bakın)" #: library/stdtypes.rst:4233 msgid "" @@ -6087,22 +6103,23 @@ msgstr "" #: library/stdtypes.rst:4238 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 " +"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 "" -"Şu anda iki yerleşik set türü vardır, :class:`set` ve :class:`frozenset`. :" -"class:`set` türü değişkendir --- içeriği :meth:`~set.add` ve :meth:`~set." -"remove` gibi yöntemler kullanılarak değiştirilebilir. Değiştirilebilir " -"olduğu için hash değeri yoktur ve bir sözlük anahtarı ya da başka bir " -"kümenin elemanı olarak kullanılamaz. :class:`frozenset` türü değişmezdir ve :" -"term:`hashable` --- içeriği oluşturulduktan sonra değiştirilemez; bu nedenle " -"bir sözlük anahtarı veya başka bir kümenin öğesi olarak kullanılabilir." +"Şu anda iki yerleşik set türü vardır, :class:`set` " +"ve :class:`frozenset`. :class:`set` türü değişkendir --- " +"içeriği :meth:`~set.add` ve :meth:`~set.remove` gibi yöntemler kullanılarak " +"değiştirilebilir. Değiştirilebilir olduğu için hash değeri yoktur ve bir " +"sözlük anahtarı ya da başka bir kümenin elemanı olarak " +"kullanılamaz. :class:`frozenset` türü değişmezdir ve :term:`hashable` --- " +"içeriği oluşturulduktan sonra değiştirilemez; bu nedenle bir sözlük anahtarı " +"veya başka bir kümenin öğesi olarak kullanılabilir." #: library/stdtypes.rst:4246 msgid "" @@ -6234,19 +6251,19 @@ msgstr "Kümenin yüzeysel bir kopyasını döndürür." #: library/stdtypes.rst:4332 msgid "" -"Note, the non-operator versions of :meth:`union`, :meth:`intersection`, :" -"meth:`difference`, :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 "" -"Not: :meth:`union`, :meth:`intersection`, :meth:`difference`, :meth:" -"`symmetric_difference`, :meth:`issubset` ve :meth:`issuperset` metotlarının " -"operatörsüz versiyonları herhangi bir yinelenebiliri argüman olarak kabul " -"edecektir. Buna karşılık, operatör tabanlı benzerleri argümanlarının küme " -"olmasını gerektirir. Bu, daha okunabilir ``set('abc').intersection('cbs')`` " -"yerine ``set('abc') & 'cbs'`` gibi hataya açık yapıları engeller.\n" +"Note, the non-operator versions " +"of :meth:`union`, :meth:`intersection`, :meth:`difference`, :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 "" +"Not: :meth:`union`, :meth:`intersection`, :meth:`difference`, :meth:`symmetric_difference`, :meth:`issubset` " +"ve :meth:`issuperset` metotlarının operatörsüz versiyonları herhangi bir " +"yinelenebiliri argüman olarak kabul edecektir. Buna karşılık, operatör " +"tabanlı benzerleri argümanlarının küme olmasını gerektirir. Bu, daha " +"okunabilir ``set('abc').intersection('cbs')`` yerine ``set('abc') & 'cbs'`` " +"gibi hataya açık yapıları engeller.\n" "\n" "Translated with www.DeepL.com/Translator (free version)" @@ -6296,8 +6313,9 @@ msgid "" "Since sets only define partial ordering (subset relationships), the output " "of the :meth:`list.sort` method is undefined for lists of sets." msgstr "" -"Kümeler yalnızca kısmi sıralama (alt küme ilişkileri) tanımladığından, :meth:" -"`list.sort` yönteminin çıktısı küme listeleri için tanımsızdır." +"Kümeler yalnızca kısmi sıralama (alt küme ilişkileri) " +"tanımladığından, :meth:`list.sort` yönteminin çıktısı küme listeleri için " +"tanımsızdır." #: library/stdtypes.rst:4358 msgid "Set elements, like dictionary keys, must be :term:`hashable`." @@ -6350,8 +6368,8 @@ msgid "" "Remove element *elem* from the set. Raises :exc:`KeyError` if *elem* is not " "contained in the set." msgstr "" -"Kümeden *elem* elemanını kaldırır. Eğer *elem* kümede bulunmuyorsa :exc:" -"`KeyError` değerini yükseltir." +"Kümeden *elem* elemanını kaldırır. Eğer *elem* kümede " +"bulunmuyorsa :exc:`KeyError` değerini yükseltir." #: library/stdtypes.rst:4398 msgid "Remove element *elem* from the set if it is present." @@ -6362,8 +6380,8 @@ msgid "" "Remove and return an arbitrary element from the set. Raises :exc:`KeyError` " "if the set is empty." msgstr "" -"Kümeden rastgele bir elemanı kaldırır ve döndürür. Küme boşsa :exc:" -"`KeyError` değerini yükseltir." +"Kümeden rastgele bir elemanı kaldırır ve döndürür. Küme " +"boşsa :exc:`KeyError` değerini yükseltir." #: library/stdtypes.rst:4407 msgid "Remove all elements from the set." @@ -6371,10 +6389,10 @@ msgstr "Kümeden tüm öğeleri kaldırın." #: library/stdtypes.rst:4410 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." +"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 "" "Not: :meth:`update`, :meth:`intersection_update`, :meth:`difference_update` " "ve :meth:`symmetric_difference_update` metotlarının operatör olmayan " @@ -6383,9 +6401,10 @@ msgstr "" #: library/stdtypes.rst:4415 #, fuzzy msgid "" -"Note, the *elem* argument to the :meth:`~object.__contains__`, :meth:" -"`remove`, and :meth:`discard` methods may be a set. To support searching " -"for an equivalent frozenset, a temporary one is created from *elem*." +"Note, the *elem* argument to " +"the :meth:`~object.__contains__`, :meth:`remove`, and :meth:`discard` " +"methods may be a set. To support searching for an equivalent frozenset, a " +"temporary one is created from *elem*." msgstr "" "Not: :meth:`__contains__`, :meth:`remove` ve :meth:`discard` yöntemlerinin " "*elem* argümanı bir küme olabilir. Eş değer bir frozenset aramayı " @@ -6399,23 +6418,24 @@ msgstr "Mapping Types --- :class:`dict`" 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.)" +"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 "" "Bir :term:`mapping` nesnesi :term:`hashable` değerlerini rastgele nesnelere " "eşler. Eşlemeler değiştirilebilir nesnelerdir. Şu anda sadece bir standart " -"eşleme türü vardır, :dfn:`dictionary`. (Diğer kapsayıcılar için yerleşik :" -"class:`list`, :class:`set` ve :class:`tuple` sınıflarına ve :mod:" -"`collections` modülüne bakın)." +"eşleme türü vardır, :dfn:`dictionary`. (Diğer kapsayıcılar için " +"yerleşik :class:`list`, :class:`set` ve :class:`tuple` sınıflarına " +"ve :mod:`collections` modülüne bakın)." #: library/stdtypes.rst:4440 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. Values that compare equal (such as ``1``, ``1.0``, " -"and ``True``) can be used interchangeably to index the same dictionary entry." +"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. Values that compare equal (such as ``1``, " +"``1.0``, and ``True``) can be used interchangeably to index the same " +"dictionary entry." msgstr "" "Bir sözlüğün anahtarları *neredeyse* rastgele değerlerdir. :term:`hashable` " "olmayan değerler, yani listeler, sözlükler veya diğer değişken türleri " @@ -6523,9 +6543,9 @@ msgid "" "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::" +"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 "" #: library/stdtypes.rst:4519 @@ -6544,9 +6564,9 @@ msgstr "" #: library/stdtypes.rst:4530 msgid "" -"The example above shows part of the implementation of :class:`collections." -"Counter`. A different ``__missing__`` method is used by :class:`collections." -"defaultdict`." +"The example above shows part of the implementation " +"of :class:`collections.Counter`. A different ``__missing__`` method is used " +"by :class:`collections.defaultdict`." msgstr "" #: library/stdtypes.rst:4536 @@ -6617,8 +6637,8 @@ msgstr "" #: library/stdtypes.rst:4592 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." +"*default*. If *default* is not given and *key* is not in the dictionary, " +"a :exc:`KeyError` is raised." msgstr "" #: library/stdtypes.rst:4598 @@ -6630,8 +6650,8 @@ msgstr "" #: library/stdtypes.rst:4601 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`." +"often used in set algorithms. If the dictionary is empty, " +"calling :meth:`popitem` raises a :exc:`KeyError`." msgstr "" #: library/stdtypes.rst:4605 @@ -6761,8 +6781,8 @@ msgstr "" #: library/stdtypes.rst:4705 msgid "" -":class:`types.MappingProxyType` can be used to create a read-only view of a :" -"class:`dict`." +":class:`types.MappingProxyType` can be used to create a read-only view of " +"a :class:`dict`." msgstr "" #: library/stdtypes.rst:4712 @@ -6771,10 +6791,10 @@ msgstr "" #: library/stdtypes.rst:4714 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." +"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 "" #: library/stdtypes.rst:4719 @@ -6796,9 +6816,9 @@ msgstr "" #: library/stdtypes.rst:4731 msgid "" "Keys and values are iterated over in insertion order. 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()]``." +"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 "" #: library/stdtypes.rst:4736 @@ -6915,8 +6935,9 @@ msgstr "" #: library/stdtypes.rst:4838 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." +"object`. File objects return themselves from __enter__() to " +"allow :func:`open` to be used as the context expression in a :keyword:`with` " +"statement." msgstr "" #: library/stdtypes.rst:4842 @@ -6954,8 +6975,8 @@ 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:`~object." -"__exit__` method has actually failed." +"context management code to easily detect whether or not " +"an :meth:`~object.__exit__` method has actually failed." msgstr "" #: library/stdtypes.rst:4870 @@ -6972,9 +6993,10 @@ 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:" -"`~contextmanager.__enter__` and :meth:`~contextmanager.__exit__` methods, " -"rather than the iterator produced by an undecorated generator function." +"decorator, it will return a context manager implementing the " +"necessary :meth:`~contextmanager.__enter__` " +"and :meth:`~contextmanager.__exit__` methods, rather than the iterator " +"produced by an undecorated generator function." msgstr "" #: library/stdtypes.rst:4883 @@ -6988,14 +7010,14 @@ msgstr "" #: library/stdtypes.rst:4891 msgid "" -"Type Annotation Types --- :ref:`Generic Alias `, :ref:" -"`Union `" +"Type Annotation Types --- :ref:`Generic Alias `, :ref:`Union `" msgstr "" #: library/stdtypes.rst:4896 msgid "" -"The core built-in types for :term:`type annotations ` are :ref:" -"`Generic Alias ` and :ref:`Union `." +"The core built-in types for :term:`type annotations ` " +"are :ref:`Generic Alias ` and :ref:`Union `." msgstr "" #: library/stdtypes.rst:4903 @@ -7031,8 +7053,8 @@ msgid "" "For a container class, the argument(s) supplied to a :ref:`subscription " "` of the class may indicate the type(s) of the elements an " "object contains. For example, ``set[bytes]`` can be used in type annotations " -"to signify a :class:`set` in which all the elements are of type :class:" -"`bytes`." +"to signify a :class:`set` in which all the elements are of " +"type :class:`bytes`." msgstr "" #: library/stdtypes.rst:4931 @@ -7055,17 +7077,17 @@ msgstr "" #: library/stdtypes.rst:4943 msgid "" "If ``y = re.search(b'bar', b'bar')``, (note the ``b`` for :class:`bytes`), " -"``y`` will also be an instance of ``re.Match``, but the return values of ``y." -"group(0)`` and ``y[0]`` will both be of type :class:`bytes`. In type " +"``y`` will also be an instance of ``re.Match``, but the return values of " +"``y.group(0)`` and ``y[0]`` will both be of type :class:`bytes`. In type " "annotations, we would represent this variety of :ref:`re.Match ` objects with ``re.Match[bytes]``." msgstr "" #: library/stdtypes.rst:4949 msgid "" -"``GenericAlias`` objects are instances of the class :class:`types." -"GenericAlias`, which can also be used to create ``GenericAlias`` objects " -"directly." +"``GenericAlias`` objects are instances of the " +"class :class:`types.GenericAlias`, which can also be used to create " +"``GenericAlias`` objects directly." msgstr "" "``GenericAlias`` nesneleri, doğrudan ``GenericAlias`` nesneleri oluşturmak " "için de kullanılabilen :class:`types.GenericAlias` sınıfının örnekleridir." @@ -7096,8 +7118,8 @@ msgid "" msgstr "" "Anahtar türünü ve değer türünü temsil eden iki tür parametresi bekleyen " "genel bir tür olan :class:`dict` kullanarak :term:`mapping` nesneleri için " -"başka bir örnek. Bu örnekte, fonksiyon :class:`str` türünde anahtarları ve :" -"class:`int` türünde değerleri olan bir ``dict`` bekler::" +"başka bir örnek. Bu örnekte, fonksiyon :class:`str` türünde anahtarları " +"ve :class:`int` türünde değerleri olan bir ``dict`` bekler::" #: library/stdtypes.rst:4968 msgid "" @@ -7201,8 +7223,9 @@ msgid "" "items in the ``GenericAlias`` object's :attr:`~genericalias.__args__`. ::" msgstr "" "Ancak, bu tür ifadeler :ref:`type variables ` kullanıldığında " -"geçerlidir. Dizin, ``GenericAlias`` nesnesinin :attr:`~genericalias." -"__args__` öğesindeki tür değişkeni öğeleri kadar öğeye sahip olmalıdır::" +"geçerlidir. Dizin, ``GenericAlias`` " +"nesnesinin :attr:`~genericalias.__args__` öğesindeki tür değişkeni öğeleri " +"kadar öğeye sahip olmalıdır::" #: library/stdtypes.rst:5020 msgid "" @@ -7494,12 +7517,14 @@ msgstr "" #: library/stdtypes.rst:5125 msgid "" "A ``GenericAlias`` object with :class:`typing.ParamSpec` parameters may not " -"have correct ``__parameters__`` after substitution because :class:`typing." -"ParamSpec` is intended primarily for static type checking." +"have correct ``__parameters__`` after substitution " +"because :class:`typing.ParamSpec` is intended primarily for static type " +"checking." msgstr "" "``GenericAlias`` nesnesi ile :class:`typing.ParamSpec` parametreleri " -"değiştirildikten sonra doğru ``__parameters__`` olmayabilir çünkü :class:" -"`typing.ParamSpec` öncelikle statik tip kontrolü için tasarlanmıştır." +"değiştirildikten sonra doğru ``__parameters__`` olmayabilir " +"çünkü :class:`typing.ParamSpec` öncelikle statik tip kontrolü için " +"tasarlanmıştır." #: library/stdtypes.rst:5132 msgid "" @@ -7523,14 +7548,14 @@ msgstr "" #: library/stdtypes.rst:5144 msgid "" "Introducing the ability to natively parameterize standard-library classes, " -"provided they implement the special class method :meth:`~object." -"__class_getitem__`." +"provided they implement the special class " +"method :meth:`~object.__class_getitem__`." msgstr "" #: library/stdtypes.rst:5148 msgid "" -":ref:`Generics`, :ref:`user-defined generics ` and :" -"class:`typing.Generic`" +":ref:`Generics`, :ref:`user-defined generics ` " +"and :class:`typing.Generic`" msgstr "" #: library/stdtypes.rst:5149 @@ -7548,8 +7573,8 @@ msgid "" "A union object holds the value of the ``|`` (bitwise or) operation on " "multiple :ref:`type objects `. These types are intended " "primarily for :term:`type annotations `. The union type " -"expression enables cleaner type hinting syntax compared to :data:`typing." -"Union`." +"expression enables cleaner type hinting syntax compared " +"to :data:`typing.Union`." msgstr "" "Bir birleşim nesnesi, birden çok :ref:`type objects ` " "üzerinde ``|`` (bitsel veya) işleminin değerini tutar. Bu türler öncelikle " @@ -7561,8 +7586,8 @@ msgstr "" msgid "" "Defines a union object which holds types *X*, *Y*, and so forth. ``X | Y`` " "means either X or Y. It is equivalent to ``typing.Union[X, Y]``. For " -"example, the following function expects an argument of type :class:`int` or :" -"class:`float`::" +"example, the following function expects an argument of type :class:`int` " +"or :class:`float`::" msgstr "" "*X*, *Y* vb. türleri tutan bir birleşim nesnesi tanımlar. ``X | Y`` X veya Y " "anlamına gelir. Bu, ``typing.Union[X, Y]`` ile eş değerdir. Örneğin, " @@ -7663,9 +7688,9 @@ msgstr "" #: library/stdtypes.rst:5230 msgid "" -"The user-exposed type for the union object can be accessed from :data:`types." -"UnionType` and used for :func:`isinstance` checks. An object cannot be " -"instantiated from the type::" +"The user-exposed type for the union object can be accessed " +"from :data:`types.UnionType` and used for :func:`isinstance` checks. An " +"object cannot be instantiated from the type::" msgstr "" "Union nesnesinin kullanıcıya açık türüne :data:`types.UnionType` adresinden " "erişilebilir ve :func:`isinstance` kontrolleri için kullanılabilir. Bir " @@ -7732,10 +7757,10 @@ msgstr "Modüller" 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 " +"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 "" "Bir modül üzerindeki tek özel işlem öznitelik erişimidir: ``m.name``, burada " @@ -7751,10 +7776,10 @@ 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." +"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 "" "Her modülün özel bir niteliği :attr:`~object.__dict__` 'dir. Bu, modülün " "sembol tablosunu içeren sözlüktür. Bu sözlüğü değiştirmek aslında modülün " @@ -7766,9 +7791,9 @@ msgstr "" #: library/stdtypes.rst:5297 msgid "" -"Modules built into the interpreter are written like this: ````. If loaded from a file, they are written as ````." +"Modules built into the interpreter are written like this: ````. If loaded from a file, they are written as ````." msgstr "" "Yorumlayıcıda yerleşik olarak bulunan modüller şu şekilde yazılır: ````. Eğer bir dosyadan yüklenmişlerse, ``` (such as :meth:" -"`append` on lists) and :ref:`class instance method `. " -"Built-in methods are described with the types that support them." +"are two flavors: :ref:`built-in methods ` (such " +"as :meth:`append` on lists) and :ref:`class instance method `. Built-in methods are described with the types that support them." msgstr "" "Yöntemler, nitelik gösterimi kullanılarak çağrılan işlevlerdir. İki çeşidi " "vardır: yerleşik yöntemler (listelerde :meth:`append` gibi) ve sınıf örneği " @@ -7832,14 +7857,14 @@ msgstr "" #, fuzzy 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 :ref:" -"`instance method `) object. When called, it will add the " -"``self`` argument to the argument list. Bound methods have two special read-" -"only attributes: :attr:`m.__self__ ` is the object on which " -"the method operates, and :attr:`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)``." +"instance, you get a special object: a :dfn:`bound method` (also " +"called :ref:`instance method `) object. When called, it " +"will add the ``self`` argument to the argument list. Bound methods have two " +"special read-only attributes: :attr:`m.__self__ ` is the " +"object on which the method operates, and :attr:`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 "" "Bir yönteme (bir sınıf ad alanında tanımlanmış bir fonksiyon) bir örnek " "üzerinden erişirseniz, özel bir nesne elde edersiniz: bir :dfn:`bound " @@ -7862,8 +7887,8 @@ msgid "" "underlying function object:" msgstr "" "Fonksiyon nesneleri gibi, bağlı metot nesneleri de keyfi nitelikler almayı " -"destekler. Ancak, yöntem nitelikleri aslında temel işlev nesnesinde (``meth." -"__func__``) saklandığından, bağlı yöntemlerde yöntem niteliklerinin " +"destekler. Ancak, yöntem nitelikleri aslında temel işlev nesnesinde " +"(``meth.__func__``) saklandığından, bağlı yöntemlerde yöntem niteliklerinin " "ayarlanmasına izin verilmez. Bir yöntem üzerinde bir öznitelik ayarlamaya " "çalışmak :exc:`AttributeError` ile sonuçlanır. Bir yöntem özniteliğini " "ayarlamak için, bunu temel işlev nesnesi üzerinde açıkça ayarlamanız " @@ -7901,8 +7926,8 @@ msgid "" "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:" -"`~function.__code__` attribute. See also the :mod:`code` module." +"function and can be extracted from function objects through " +"their :attr:`~function.__code__` attribute. See also the :mod:`code` module." msgstr "" "Kod nesneleri, uygulama tarafından bir fonksiyon gövdesi gibi \"sözde " "derlenmiş\" çalıştırılabilir Python kodunu temsil etmek için kullanılır. " @@ -7918,8 +7943,9 @@ msgid "" "` ``object.__getattr__`` with arguments ``obj`` and " "``\"__code__\"``." msgstr "" -"``__code__`` 'e erişmek,``obj`` ve ``\"__code__\"`` argümanlarıyla :ref:" -"`denetim etkinliği ` ``object.__getattr__`` oluşturur." +"``__code__`` 'e erişmek,``obj`` ve ``\"__code__\"`` " +"argümanlarıyla :ref:`denetim etkinliği ` ``object.__getattr__`` " +"oluşturur." #: library/stdtypes.rst:5399 msgid "" @@ -7978,14 +8004,14 @@ msgstr "Üç Nokta Nesnesi" #: library/stdtypes.rst:5440 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." +"no special operations. There is exactly one ellipsis object, " +"named :const:`Ellipsis` (a built-in name). ``type(Ellipsis)()`` produces " +"the :const:`Ellipsis` singleton." msgstr "" "Bu nesne genellikle dilimleme tarafından kullanılır (bkz. :ref:`slicings`). " "Özel operasyonları desteklemez. Tam olarak :const:`Ellipsis` (yerleşik bir " -"ad) adında bir elips nesnesi vardır. ``type(Ellipsis)()``, :const:" -"`Ellipsis` singletonunu üretir." +"ad) adında bir elips nesnesi vardır. ``type(Ellipsis)" +"()``, :const:`Ellipsis` singletonunu üretir." #: library/stdtypes.rst:5445 msgid "It is written as ``Ellipsis`` or ``...``." @@ -8000,12 +8026,12 @@ msgstr "NotImplemented Nesnesi" 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 :data:`NotImplemented` object. :code:" -"`type(NotImplemented)()` produces the singleton instance." +"more information. There is exactly one :data:`NotImplemented` " +"object. :code:`type(NotImplemented)()` produces the singleton instance." msgstr "" "Bu nesne, desteklemedikleri türlerde çalışmaları istendiğinde " -"karşılaştırmalardan ve ikili işlemlerden döndürülür. Daha fazla bilgi için :" -"ref:`comparisons` sayfasına bakın. Tam olarak bir ``NotImplemented`` " +"karşılaştırmalardan ve ikili işlemlerden döndürülür. Daha fazla bilgi " +"için :ref:`comparisons` sayfasına bakın. Tam olarak bir ``NotImplemented`` " "nesnesi vardır. ``type(NotImplemented)()``, singleton örneğini üretir." #: library/stdtypes.rst:5458 @@ -8034,8 +8060,8 @@ msgstr "Özel Özellikler" #: library/stdtypes.rst:5476 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." +"types, where they are relevant. Some of these are not reported by " +"the :func:`dir` built-in function." msgstr "" "Uygulama, ilgili oldukları çeşitli nesne türlerine birkaç özel salt okunur " "öznitelik ekler. Bunlardan bazıları :func:`dir` yerleşik işlevi tarafından " @@ -8051,8 +8077,8 @@ msgid "" "The :term:`qualified name` of the class, function, method, descriptor, or " "generator instance." msgstr "" -"Sınıf, fonksiyon, yöntem, tanımlayıcı veya üretici örneğinin :term:" -"`qualified name`." +"Sınıf, fonksiyon, yöntem, tanımlayıcı veya üretici " +"örneğinin :term:`qualified name`." #: library/stdtypes.rst:5497 msgid "The name of the module in which a class or function was defined." @@ -8065,9 +8091,9 @@ msgstr "" #: library/stdtypes.rst:5507 msgid "" -"The :ref:`type parameters ` of generic classes, functions, and :" -"ref:`type aliases `. For classes and functions that are not " -"generic, this will be an empty tuple." +"The :ref:`type parameters ` of generic classes, functions, " +"and :ref:`type aliases `. For classes and functions that are " +"not generic, this will be an empty tuple." msgstr "" #: library/stdtypes.rst:5517 @@ -8076,10 +8102,10 @@ msgstr "" #: library/stdtypes.rst:5519 msgid "" -"CPython has a global limit for converting between :class:`int` and :class:" -"`str` to mitigate denial of service attacks. This limit *only* applies to " -"decimal or other non-power-of-two number bases. Hexadecimal, octal, and " -"binary conversions are unlimited. The limit can be configured." +"CPython has a global limit for converting between :class:`int` " +"and :class:`str` to mitigate denial of service attacks. This limit *only* " +"applies to decimal or other non-power-of-two number bases. Hexadecimal, " +"octal, and binary conversions are unlimited. The limit can be configured." msgstr "" #: library/stdtypes.rst:5524 @@ -8135,10 +8161,10 @@ msgstr "" #: library/stdtypes.rst:5559 msgid "" -"The default limit is 4300 digits as provided in :data:`sys.int_info." -"default_max_str_digits `. The lowest limit that can be " -"configured is 640 digits as provided in :data:`sys.int_info." -"str_digits_check_threshold `." +"The default limit is 4300 digits as provided " +"in :data:`sys.int_info.default_max_str_digits `. The lowest " +"limit that can be configured is 640 digits as provided " +"in :data:`sys.int_info.str_digits_check_threshold `." msgstr "" #: library/stdtypes.rst:5564 @@ -8162,8 +8188,8 @@ msgstr "" #: library/stdtypes.rst:5581 msgid "" -"The limitation only applies to potentially slow conversions between :class:" -"`int` and :class:`str` or :class:`bytes`:" +"The limitation only applies to potentially slow conversions " +"between :class:`int` and :class:`str` or :class:`bytes`:" msgstr "" #: library/stdtypes.rst:5584 @@ -8242,17 +8268,18 @@ msgstr "" #: library/stdtypes.rst:5611 msgid "" -":data:`sys.flags.int_max_str_digits` contains the value of :envvar:" -"`PYTHONINTMAXSTRDIGITS` or :option:`-X int_max_str_digits <-X>`. If both the " -"env var and the ``-X`` option are set, the ``-X`` option takes precedence. A " -"value of *-1* indicates that both were unset, thus a value of :data:`sys." -"int_info.default_max_str_digits` was used during initialization." +":data:`sys.flags.int_max_str_digits` contains the value " +"of :envvar:`PYTHONINTMAXSTRDIGITS` or :option:`-X int_max_str_digits <-X>`. " +"If both the env var and the ``-X`` option are set, the ``-X`` option takes " +"precedence. A value of *-1* indicates that both were unset, thus a value " +"of :data:`sys.int_info.default_max_str_digits` was used during " +"initialization." msgstr "" #: library/stdtypes.rst:5617 msgid "" -"From code, you can inspect the current limit and set a new one using these :" -"mod:`sys` APIs:" +"From code, you can inspect the current limit and set a new one using " +"these :mod:`sys` APIs:" msgstr "" #: library/stdtypes.rst:5620 @@ -8264,8 +8291,8 @@ msgstr "" #: library/stdtypes.rst:5624 msgid "" -"Information about the default and minimum can be found in :data:`sys." -"int_info`:" +"Information about the default and minimum can be found " +"in :data:`sys.int_info`:" msgstr "" #: library/stdtypes.rst:5626 @@ -8342,8 +8369,8 @@ msgid "" "Additional information on these special methods may be found in the Python " "Reference Manual (:ref:`customization`)." msgstr "" -"Bu özel yöntemler hakkında daha fazla bilgi Python Referans El Kitabında (:" -"ref:`customization`) bulunabilir." +"Bu özel yöntemler hakkında daha fazla bilgi Python Referans El Kitabında " +"(:ref:`customization`) bulunabilir." #: library/stdtypes.rst:5677 msgid "" @@ -8364,9 +8391,9 @@ msgid "" "\"Lu\" (Letter, uppercase), \"Ll\" (Letter, lowercase), or \"Lt\" (Letter, " "titlecase)." msgstr "" -"Harfli karakterler, genel kategori özelliği \"Lu\" (Harf, büyük), " -"\"Ll\" (Harf, küçük harf) veya \"Lt\" (Harf, başlık) karakterlerinden biri " -"olan karakterlerdir." +"Harfli karakterler, genel kategori özelliği \"Lu\" (Harf, büyük), \"Ll\" " +"(Harf, küçük harf) veya \"Lt\" (Harf, başlık) karakterlerinden biri olan " +"karakterlerdir." #: library/stdtypes.rst:5685 msgid "" @@ -9216,24 +9243,25 @@ msgstr "" #~ msgstr "" #~ "Sözlükler, ``key: value`` çiftlerinin virgülle ayrılmış bir listesini " #~ "parantez içine yerleştirerek oluşturulabilir, örneğin: ``{'jack': 4098, " -#~ "'sjoerd': 4127}`` veya ``{4098: 'jack', 4127: 'sjoerd'}`` veya :class:" -#~ "`dict` yapıcısı ile oluşturulabilir." +#~ "'sjoerd': 4127}`` veya ``{4098: 'jack', 4127: 'sjoerd'}`` " +#~ "veya :class:`dict` yapıcısı ile oluşturulabilir." #~ msgid "" #~ "``GenericAlias`` objects are created by subscripting a class (usually a " -#~ "container), such as ``list[int]``. They are intended primarily for :term:" -#~ "`type annotations `." +#~ "container), such as ``list[int]``. They are intended primarily " +#~ "for :term:`type annotations `." #~ msgstr "" #~ "``GenericAlias`` nesneleri, ``list[int]`` gibi bir sınıfın (genellikle " -#~ "bir kapsayıcı) alt kodlanmasıyla oluşturulur. Bunlar öncelikle :term:" -#~ "`type annotations ` için tasarlanmıştır." +#~ "bir kapsayıcı) alt kodlanmasıyla oluşturulur. Bunlar " +#~ "öncelikle :term:`type annotations ` için tasarlanmıştır." #~ msgid "" #~ "Usually, the :ref:`subscription ` of container objects " #~ "calls the method :meth:`__getitem__` of the object. However, the " -#~ "subscription of some containers' classes may call the classmethod :meth:" -#~ "`__class_getitem__` of the class instead. The classmethod :meth:" -#~ "`__class_getitem__` should return a ``GenericAlias`` object." +#~ "subscription of some containers' classes may call the " +#~ "classmethod :meth:`__class_getitem__` of the class instead. The " +#~ "classmethod :meth:`__class_getitem__` should return a ``GenericAlias`` " +#~ "object." #~ msgstr "" #~ "Genellikle, kapsayıcı nesnelerinin :ref:`subscription `, " #~ "nesnenin :meth:`__getitem__` yöntemini çağırır. Ancak, bazı konteyner " @@ -9246,9 +9274,9 @@ msgstr "" #~ "take precedence over the :meth:`__class_getitem__` defined in the class " #~ "(see :pep:`560` for more details)." #~ msgstr "" -#~ "Sınıfın üst sınıfının :meth:`__getitem__`'i mevcutsa, sınıfta tanımlanan :" -#~ "meth:`__class_getitem__`'e göre öncelikli olacaktır (daha fazla ayrıntı " -#~ "için :pep:`560`'a bakın)." +#~ "Sınıfın üst sınıfının :meth:`__getitem__`'i mevcutsa, sınıfta " +#~ "tanımlanan :meth:`__class_getitem__`'e göre öncelikli olacaktır (daha " +#~ "fazla ayrıntı için :pep:`560`'a bakın)." #~ msgid "" #~ ":meth:`__class_getitem__` -- Used to implement parameterized generics." diff --git a/library/string.po b/library/string.po index e4cfb62af..9eacdc3f7 100644 --- a/library/string.po +++ b/library/string.po @@ -42,9 +42,9 @@ msgstr "" #: library/string.rst:26 msgid "" -"The concatenation of the :const:`ascii_lowercase` and :const:" -"`ascii_uppercase` constants described below. This value is not locale-" -"dependent." +"The concatenation of the :const:`ascii_lowercase` " +"and :const:`ascii_uppercase` constants described below. This value is not " +"locale-dependent." msgstr "" #: library/string.rst:32 @@ -80,8 +80,9 @@ msgstr "" #: 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`." +"combination " +"of :const:`digits`, :const:`ascii_letters`, :const:`punctuation`, " +"and :const:`whitespace`." msgstr "" #: library/string.rst:71 @@ -112,8 +113,8 @@ msgstr "" #: 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`." +"positional and keyword arguments. It is just a wrapper that " +"calls :meth:`vformat`." msgstr "" #: library/string.rst:98 @@ -127,9 +128,10 @@ 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." +"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 "" #: library/string.rst:112 @@ -160,9 +162,9 @@ msgstr "" 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 " +"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 "" @@ -176,9 +178,9 @@ msgstr "" #: 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." +"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 "" #: library/string.rst:149 @@ -192,14 +194,14 @@ msgstr "" 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." +"looked up after :meth:`get_value` returns by calling the built-" +"in :func:`getattr` function." msgstr "" #: 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." +"If the index or keyword refers to an item that does not exist, then " +"an :exc:`IndexError` or :exc:`KeyError` should be raised." msgstr "" #: library/string.rst:163 @@ -208,8 +210,9 @@ msgid "" "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." +"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 "" #: library/string.rst:173 @@ -278,9 +281,9 @@ msgid "" "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 :meth:`~object.__getitem__`." +"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 :meth:`~object.__getitem__`." msgstr "" #: library/string.rst:242 @@ -317,15 +320,15 @@ msgid "" "the job of formatting a value is done by the :meth:`~object.__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:" -"`~object.__format__`, the normal formatting logic is bypassed." +"formatting. By converting the value to a string before " +"calling :meth:`~object.__format__`, the normal formatting logic is bypassed." msgstr "" #: library/string.rst:265 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`." +"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 "" #: library/string.rst:269 @@ -374,10 +377,10 @@ msgstr "" #: library/string.rst:298 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." +"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 "" #: library/string.rst:305 @@ -695,8 +698,8 @@ msgstr "" #: library/string.rst:498 msgid "" -"The available presentation types for :class:`float` and :class:`~decimal." -"Decimal` values are:" +"The available presentation types for :class:`float` " +"and :class:`~decimal.Decimal` values are:" msgstr "" #: library/string.rst:504 @@ -710,9 +713,9 @@ msgid "" "exponent. The coefficient has one digit before and ``p`` digits after the " "decimal point, for a total of ``p + 1`` significant digits. With no " "precision given, uses a precision of ``6`` digits after the decimal point " -"for :class:`float`, and shows all coefficient digits for :class:`~decimal." -"Decimal`. If ``p=0``, the decimal point is omitted unless the ``#`` option " -"is used." +"for :class:`float`, and shows all coefficient digits " +"for :class:`~decimal.Decimal`. If ``p=0``, the decimal point is omitted " +"unless the ``#`` option is used." msgstr "" #: library/string.rst:515 @@ -776,12 +779,12 @@ msgstr "" #: library/string.rst:550 msgid "" -"With no precision given, uses a precision of ``6`` significant digits for :" -"class:`float`. For :class:`~decimal.Decimal`, the coefficient of the result " -"is formed from the coefficient digits of the value; scientific notation is " -"used for values smaller than ``1e-6`` in absolute value and values where the " -"place value of the least significant digit is larger than 1, and fixed-point " -"notation is used otherwise." +"With no precision given, uses a precision of ``6`` significant digits " +"for :class:`float`. For :class:`~decimal.Decimal`, the coefficient of the " +"result is formed from the coefficient digits of the value; scientific " +"notation is used for values smaller than ``1e-6`` in absolute value and " +"values where the place value of the least significant digit is larger than " +"1, and fixed-point notation is used otherwise." msgstr "" #: library/string.rst:559 @@ -964,8 +967,8 @@ msgid "" "'+3.140000; -3.140000'\n" ">>> '{: f}; {: f}'.format(3.14, -3.14) # show a space for positive numbers\n" "' 3.140000; -3.140000'\n" -">>> '{:-f}; {:-f}'.format(3.14, -3.14) # show only the minus -- same as '{:" -"f}; {:f}'\n" +">>> '{:-f}; {:-f}'.format(3.14, -3.14) # show only the minus -- same as " +"'{:f}; {:f}'\n" "'3.140000; -3.140000'" msgstr "" @@ -1059,12 +1062,13 @@ msgstr "" #: library/string.rst:738 msgid "" -"Template strings provide simpler string substitutions as described in :pep:" -"`292`. A primary use case for template strings is for internationalization " -"(i18n) since in that context, the simpler syntax and functionality makes it " -"easier to translate than other built-in string formatting facilities in " -"Python. As an example of a library built on template strings for i18n, see " -"the `flufl.i18n `_ package." +"Template strings provide simpler string substitutions as described " +"in :pep:`292`. A primary use case for template strings is for " +"internationalization (i18n) since in that context, the simpler syntax and " +"functionality makes it easier to translate than other built-in string " +"formatting facilities in Python. As an example of a library built on " +"template strings for i18n, see the `flufl.i18n `_ package." msgstr "" #: library/string.rst:748 @@ -1096,8 +1100,8 @@ msgstr "" #: library/string.rst:763 msgid "" -"Any other appearance of ``$`` in the string will result in a :exc:" -"`ValueError` being raised." +"Any other appearance of ``$`` in the string will result in " +"a :exc:`ValueError` being raised." msgstr "" #: library/string.rst:766 @@ -1140,8 +1144,8 @@ msgstr "" #: library/string.rst:802 msgid "" -"Returns false if the template has invalid placeholders that will cause :meth:" -"`substitute` to raise :exc:`ValueError`." +"Returns false if the template has invalid placeholders that will " +"cause :meth:`substitute` to raise :exc:`ValueError`." msgstr "" #: library/string.rst:810 @@ -1195,10 +1199,10 @@ msgstr "" 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. Note further that you cannot change the " -"delimiter after class creation (i.e. a different delimiter must be set in " -"the subclass's class namespace)." +"*not* be a regular expression, as the implementation will " +"call :meth:`re.escape` on this string as needed. Note further that you " +"cannot change the delimiter after class creation (i.e. a different delimiter " +"must be set in the subclass's class namespace)." msgstr "" #: library/string.rst:852 @@ -1285,11 +1289,11 @@ msgstr "" #: library/string.rst:910 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." +"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 "" #: library/string.rst:195 diff --git a/library/stringprep.po b/library/stringprep.po index 5b83d0289..eee22a8dc 100644 --- a/library/stringprep.po +++ b/library/stringprep.po @@ -57,11 +57,11 @@ msgstr "" #: 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." +"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 "" #: library/stringprep.rst:44 diff --git a/library/struct.po b/library/struct.po index eb403ee03..862e7bc75 100644 --- a/library/struct.po +++ b/library/struct.po @@ -50,12 +50,12 @@ msgstr "" #: library/struct.rst:35 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." +"*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 "" #: library/struct.rst:44 @@ -243,8 +243,8 @@ msgstr "" msgid "" "Native byte order is big-endian or little-endian, depending on the host " "system. For example, Intel x86, AMD64 (x86-64), and Apple M1 are little-" -"endian; IBM z and many legacy architectures are big-endian. Use :data:`sys." -"byteorder` to check the endianness of your system." +"endian; IBM z and many legacy architectures are big-endian. " +"Use :data:`sys.byteorder` to check the endianness of your system." msgstr "" #: library/struct.rst:179 @@ -255,8 +255,8 @@ msgstr "" #: library/struct.rst:182 msgid "" -"Standard size depends only on the format character; see the table in the :" -"ref:`format-characters` section." +"Standard size depends only on the format character; see the table in " +"the :ref:`format-characters` section." msgstr "" #: library/struct.rst:185 @@ -648,13 +648,13 @@ 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." +"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 "" #: library/struct.rst:335 @@ -688,8 +688,8 @@ msgstr "" 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." +"``'Q'``), if ``x`` is outside the valid range for that format " +"then :exc:`struct.error` is raised." msgstr "" #: library/struct.rst:359 @@ -1000,8 +1000,8 @@ msgstr "" #: library/struct.rst:591 msgid "" "Identical to the :func:`unpack_from` function, using the compiled format. " -"The buffer's size in bytes, starting at position *offset*, must be at least :" -"attr:`size`." +"The buffer's size in bytes, starting at position *offset*, must be at " +"least :attr:`size`." msgstr "" #: library/struct.rst:598 diff --git a/library/subprocess.po b/library/subprocess.po index c9763f280..36e46544b 100644 --- a/library/subprocess.po +++ b/library/subprocess.po @@ -93,19 +93,20 @@ msgid "" "the internal :class:`Popen` object is automatically created with *stdout* " "and *stderr* both set to :data:`~subprocess.PIPE`. The *stdout* and *stderr* " "arguments may not be supplied at the same time as *capture_output*. If you " -"wish to capture and combine both streams into one, set *stdout* to :data:" -"`~subprocess.PIPE` and *stderr* to :data:`~subprocess.STDOUT`, instead of " -"using *capture_output*." +"wish to capture and combine both streams into one, set *stdout* " +"to :data:`~subprocess.PIPE` and *stderr* to :data:`~subprocess.STDOUT`, " +"instead of using *capture_output*." msgstr "" #: library/subprocess.rst:62 msgid "" -"A *timeout* may be specified in seconds, it is internally passed on 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. The initial process creation itself " -"cannot be interrupted on many platform APIs so you are not guaranteed to see " -"a timeout exception until at least after however long process creation takes." +"A *timeout* may be specified in seconds, it is internally passed on " +"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. The initial process creation " +"itself cannot be interrupted on many platform APIs so you are not guaranteed " +"to see a timeout exception until at least after however long process " +"creation takes." msgstr "" #: library/subprocess.rst:70 @@ -113,16 +114,17 @@ 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 *text* is true. When used, the " -"internal :class:`Popen` object is automatically created with *stdin* set to :" -"data:`~subprocess.PIPE`, and the *stdin* argument may not be used as well." +"internal :class:`Popen` object is automatically created with *stdin* set " +"to :data:`~subprocess.PIPE`, and the *stdin* argument may not be used as " +"well." msgstr "" #: library/subprocess.rst:77 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." +"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 "" #: library/subprocess.rst:82 @@ -140,8 +142,8 @@ msgid "" "variables for the new process; these are used instead of the default " "behavior of inheriting the current process' environment. It is passed " "directly to :class:`Popen`. This mapping can be str to str on any platform " -"or bytes to bytes on POSIX platforms much like :data:`os.environ` or :data:" -"`os.environb`." +"or bytes to bytes on POSIX platforms much like :data:`os.environ` " +"or :data:`os.environb`." msgstr "" #: library/subprocess.rst:95 @@ -179,8 +181,8 @@ msgstr "" msgid "" "Changed Windows shell search order for ``shell=True``. The current directory " "and ``%PATH%`` are replaced with ``%COMSPEC%`` and ``%SystemRoot%" -"\\System32\\cmd.exe``. As a result, dropping a malicious program named ``cmd." -"exe`` into a current directory no longer works." +"\\System32\\cmd.exe``. As a result, dropping a malicious program named " +"``cmd.exe`` into a current directory no longer works." msgstr "" #: library/subprocess.rst:130 @@ -207,9 +209,9 @@ msgstr "" #: library/subprocess.rst:146 msgid "" -"Captured stdout from the child process. A bytes sequence, or a string if :" -"func:`run` was called with an encoding, errors, or text=True. ``None`` if " -"stdout was not captured." +"Captured stdout from the child process. A bytes sequence, or a string " +"if :func:`run` was called with an encoding, errors, or text=True. ``None`` " +"if stdout was not captured." msgstr "" #: library/subprocess.rst:150 @@ -220,9 +222,9 @@ msgstr "" #: library/subprocess.rst:156 msgid "" -"Captured stderr from the child process. A bytes sequence, or a string if :" -"func:`run` was called with an encoding, errors, or text=True. ``None`` if " -"stderr was not captured." +"Captured stderr from the child process. A bytes sequence, or a string " +"if :func:`run` was called with an encoding, errors, or text=True. ``None`` " +"if stderr was not captured." msgstr "" #: library/subprocess.rst:162 @@ -270,10 +272,11 @@ msgstr "" #: library/subprocess.rst:211 msgid "" -"Output of the child process if it was captured by :func:`run` or :func:" -"`check_output`. Otherwise, ``None``. This is always :class:`bytes` when " -"any output was captured regardless of the ``text=True`` setting. It may " -"remain ``None`` instead of ``b''`` when no output was observed." +"Output of the child process if it was captured by :func:`run` " +"or :func:`check_output`. Otherwise, ``None``. This is " +"always :class:`bytes` when any output was captured regardless of the " +"``text=True`` setting. It may remain ``None`` instead of ``b''`` when no " +"output was observed." msgstr "" #: library/subprocess.rst:256 @@ -294,9 +297,9 @@ msgstr "" #: library/subprocess.rst:235 msgid "" -"Subclass of :exc:`SubprocessError`, raised when a process run by :func:" -"`check_call`, :func:`check_output`, or :func:`run` (with ``check=True``) " -"returns a non-zero exit status." +"Subclass of :exc:`SubprocessError`, raised when a process run " +"by :func:`check_call`, :func:`check_output`, or :func:`run` (with " +"``check=True``) returns a non-zero exit status." msgstr "" #: library/subprocess.rst:242 @@ -307,8 +310,8 @@ msgstr "" #: library/subprocess.rst:251 msgid "" -"Output of the child process if it was captured by :func:`run` or :func:" -"`check_output`. Otherwise, ``None``." +"Output of the child process if it was captured by :func:`run` " +"or :func:`check_output`. Otherwise, ``None``." msgstr "" #: library/subprocess.rst:260 @@ -347,10 +350,10 @@ msgid "" "descriptor (a positive integer), and an existing :term:`file object` with a " "valid file descriptor. With the default settings of ``None``, no " "redirection will occur. :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. 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*." +"should be created. :data:`DEVNULL` indicates that the special " +"file :data:`os.devnull` will be used. 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 "" #: library/subprocess.rst:299 @@ -386,9 +389,9 @@ msgstr "" #: library/subprocess.rst:322 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." +"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 "" #: library/subprocess.rst:326 @@ -399,17 +402,18 @@ msgid "" "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`)." +"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 "" #: library/subprocess.rst:336 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." +"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 "" #: library/subprocess.rst:465 @@ -437,16 +441,16 @@ msgstr "" #: library/subprocess.rst:368 msgid "" -"Execute a child program in a new process. On POSIX, the class uses :meth:" -"`os.execvpe`-like behavior to execute the child program. On Windows, the " -"class uses the Windows ``CreateProcess()`` function. The arguments to :" -"class:`Popen` are as follows." +"Execute a child program in a new process. On POSIX, the class " +"uses :meth:`os.execvpe`-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 "" #: library/subprocess.rst:373 msgid "" -"*args* should be a sequence of program arguments or else a single string or :" -"term:`path-like object`. By default, the program to execute is the first " +"*args* should be a sequence of program arguments or else a single string " +"or :term:`path-like object`. 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 " @@ -557,8 +561,8 @@ msgid "" "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::" +"be treated as additional arguments to the shell itself. That is to " +"say, :class:`Popen` does the equivalent of::" msgstr "" #: library/subprocess.rst:455 @@ -598,8 +602,8 @@ msgstr "" #: library/subprocess.rst:477 msgid "" -"negative bufsize (the default) means the system default of io." -"DEFAULT_BUFFER_SIZE will be used." +"negative bufsize (the default) means the system default of " +"io.DEFAULT_BUFFER_SIZE will be used." msgstr "" #: library/subprocess.rst:480 @@ -642,10 +646,10 @@ msgid "" "descriptor (a positive integer), and an existing :term:`file object` with a " "valid file descriptor. With the default settings of ``None``, no " "redirection will occur. :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. 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*." +"should be created. :data:`DEVNULL` indicates that the special " +"file :data:`os.devnull` will be used. 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 "" #: library/subprocess.rst:523 @@ -687,8 +691,8 @@ msgstr "" #: library/subprocess.rst:552 msgid "" "On Windows, if *close_fds* is true then no handles will be inherited by the " -"child process unless explicitly passed in the ``handle_list`` element of :" -"attr:`STARTUPINFO.lpAttributeList`, or by standard handle redirection." +"child process unless explicitly passed in the ``handle_list`` element " +"of :attr:`STARTUPINFO.lpAttributeList`, or by standard handle redirection." msgstr "" #: library/subprocess.rst:556 @@ -699,16 +703,16 @@ msgstr "" #: library/subprocess.rst:560 msgid "" -"On Windows the default for *close_fds* was changed from :const:`False` to :" -"const:`True` when redirecting the standard handles. It's now possible to set " -"*close_fds* to :const:`True` when redirecting the standard handles." +"On Windows the default for *close_fds* was changed from :const:`False` " +"to :const:`True` when redirecting the standard handles. It's now possible to " +"set *close_fds* to :const:`True` when redirecting the standard handles." msgstr "" #: library/subprocess.rst:565 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)" +"the parent and child. Providing any *pass_fds* forces *close_fds* to " +"be :const:`True`. (POSIX only)" msgstr "" #: library/subprocess.rst:569 @@ -718,10 +722,10 @@ msgstr "" #: library/subprocess.rst:572 msgid "" "If *cwd* is not ``None``, the function changes the working directory to " -"*cwd* before executing the child. *cwd* can be a string, bytes or :term:" -"`path-like ` object. On POSIX, the function looks for " -"*executable* (or for the first item in *args*) relative to *cwd* if the " -"executable path is a relative path." +"*cwd* before executing the child. *cwd* can be a string, bytes " +"or :term:`path-like ` object. On POSIX, the function " +"looks for *executable* (or for the first item in *args*) relative to *cwd* " +"if the executable path is a relative path." msgstr "" #: library/subprocess.rst:578 @@ -806,8 +810,8 @@ 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. This mapping can be " -"str to str on any platform or bytes to bytes on POSIX platforms much like :" -"data:`os.environ` or :data:`os.environb`." +"str to str on any platform or bytes to bytes on POSIX platforms much " +"like :data:`os.environ` or :data:`os.environb`." msgstr "" #: library/subprocess.rst:650 @@ -920,8 +924,8 @@ msgstr "" #: library/subprocess.rst:703 msgid "" -"Popen and the other functions in this module that use it raise an :ref:" -"`auditing event ` ``subprocess.Popen`` with arguments " +"Popen and the other functions in this module that use it raise " +"an :ref:`auditing event ` ``subprocess.Popen`` with arguments " "``executable``, ``args``, ``cwd``, and ``env``. The value for ``args`` may " "be a single string or a list of strings, depending on platform." msgstr "" @@ -941,8 +945,8 @@ msgid "" "Popen can use :func:`os.posix_spawn` in some cases for better performance. " "On Windows Subsystem for Linux and QEMU User Emulation, Popen constructor " "using :func:`os.posix_spawn` no longer raise an exception on errors like " -"missing program, but the child process fails with a non-zero :attr:`~Popen." -"returncode`." +"missing program, but the child process fails with a non-" +"zero :attr:`~Popen.returncode`." msgstr "" #: library/subprocess.rst:724 @@ -959,11 +963,11 @@ msgstr "" 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. Note that, when ``shell=True``, :exc:" -"`OSError` will be raised by the child only if the selected shell itself was " -"not found. To determine if the shell failed to find the requested " -"application, it is necessary to check the return code or output from the " -"subprocess." +"prepare for :exc:`OSError` exceptions. Note that, when " +"``shell=True``, :exc:`OSError` will be raised by the child only if the " +"selected shell itself was not found. To determine if the shell failed to " +"find the requested application, it is necessary to check the return code or " +"output from the subprocess." msgstr "" #: library/subprocess.rst:736 @@ -974,15 +978,16 @@ msgstr "" #: library/subprocess.rst:739 msgid "" -":func:`check_call` and :func:`check_output` will raise :exc:" -"`CalledProcessError` if the called process returns a non-zero return code." +":func:`check_call` and :func:`check_output` will " +"raise :exc:`CalledProcessError` if the called process returns a non-zero " +"return code." msgstr "" #: library/subprocess.rst:743 msgid "" -"All of the functions and methods that accept a *timeout* parameter, such as :" -"func:`run` and :meth:`Popen.communicate` will raise :exc:`TimeoutExpired` if " -"the timeout expires before the process exits." +"All of the functions and methods that accept a *timeout* parameter, such " +"as :func:`run` and :meth:`Popen.communicate` will " +"raise :exc:`TimeoutExpired` if the timeout expires before the process exits." msgstr "" #: library/subprocess.rst:747 @@ -1018,8 +1023,8 @@ msgid "" "this library. This could result in arguments being parsed according to shell " "rules, but without any escaping added by Python. If you are intentionally " "launching a batch file with arguments from untrusted sources, consider " -"passing ``shell=True`` to allow Python to escape special characters. See :gh:" -"`114539` for additional discussion." +"passing ``shell=True`` to allow Python to escape special characters. " +"See :gh:`114539` for additional discussion." msgstr "" #: library/subprocess.rst:777 @@ -1032,21 +1037,21 @@ msgstr "" #: library/subprocess.rst:784 msgid "" -"Check if child process has terminated. Set and return :attr:`~Popen." -"returncode` attribute. Otherwise, returns ``None``." +"Check if child process has terminated. Set and " +"return :attr:`~Popen.returncode` attribute. Otherwise, returns ``None``." msgstr "" #: library/subprocess.rst:790 msgid "" -"Wait for child process to terminate. Set and return :attr:`~Popen." -"returncode` attribute." +"Wait for child process to terminate. Set and " +"return :attr:`~Popen.returncode` attribute." msgstr "" #: library/subprocess.rst:793 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." +"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 "" #: library/subprocess.rst:799 @@ -1061,8 +1066,8 @@ msgstr "" msgid "" "When the ``timeout`` parameter is not ``None``, then (on POSIX) 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`." +"the :mod:`asyncio` module for an asynchronous wait: " +"see :class:`asyncio.create_subprocess_exec`." msgstr "" #: library/subprocess.rst:852 library/subprocess.rst:1233 @@ -1096,9 +1101,9 @@ msgstr "" #: library/subprocess.rst:832 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." +"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 "" #: library/subprocess.rst:836 @@ -1195,10 +1200,10 @@ msgstr "" #: library/subprocess.rst:922 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." +"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 "" #: library/subprocess.rst:930 @@ -1255,8 +1260,8 @@ msgstr "" #: library/subprocess.rst:971 msgid "" "si = subprocess.STARTUPINFO()\n" -"si.dwFlags = subprocess.STARTF_USESTDHANDLES | subprocess." -"STARTF_USESHOWWINDOW" +"si.dwFlags = subprocess.STARTF_USESTDHANDLES | " +"subprocess.STARTF_USESHOWWINDOW" msgstr "" #: library/subprocess.rst:976 @@ -1291,15 +1296,15 @@ msgstr "" #: library/subprocess.rst:1003 msgid "" -":data:`SW_HIDE` is provided for this attribute. It is used when :class:" -"`Popen` is called with ``shell=True``." +":data:`SW_HIDE` is provided for this attribute. It is used " +"when :class:`Popen` is called with ``shell=True``." msgstr "" #: library/subprocess.rst:1008 msgid "" "A dictionary of additional attributes for process creation as given in " -"``STARTUPINFOEX``, see `UpdateProcThreadAttribute `__." +"``STARTUPINFOEX``, see `UpdateProcThreadAttribute `__." msgstr "" #: library/subprocess.rst:1012 @@ -1318,9 +1323,9 @@ msgstr "" #: library/subprocess.rst:1018 msgid "" -"The handles must be temporarily made inheritable by :func:`os." -"set_handle_inheritable` when passed to the :class:`Popen` constructor, else :" -"class:`OSError` will be raised with Windows error " +"The handles must be temporarily made inheritable " +"by :func:`os.set_handle_inheritable` when passed to the :class:`Popen` " +"constructor, else :class:`OSError` will be raised with Windows error " "``ERROR_INVALID_PARAMETER`` (87)." msgstr "" @@ -1328,9 +1333,9 @@ msgstr "" msgid "" "In a multithreaded process, use caution to avoid leaking handles that are " "marked inheritable when combining this feature with concurrent calls to " -"other process creation functions that inherit all handles such as :func:`os." -"system`. This also applies to standard handle redirection, which " -"temporarily creates inheritable handles." +"other process creation functions that inherit all handles such " +"as :func:`os.system`. This also applies to standard handle redirection, " +"which temporarily creates inheritable handles." msgstr "" #: library/subprocess.rst:1035 @@ -1365,9 +1370,9 @@ msgstr "" #: library/subprocess.rst:1060 msgid "" -"Specifies that the :attr:`STARTUPINFO.hStdInput`, :attr:`STARTUPINFO." -"hStdOutput`, and :attr:`STARTUPINFO.hStdError` attributes contain additional " -"information." +"Specifies that " +"the :attr:`STARTUPINFO.hStdInput`, :attr:`STARTUPINFO.hStdOutput`, " +"and :attr:`STARTUPINFO.hStdError` attributes contain additional information." msgstr "" #: library/subprocess.rst:1066 @@ -1508,10 +1513,11 @@ msgstr "" #: library/subprocess.rst:1208 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. If :func:`check_call` was unable " -"to start the process it will propagate the exception that was raised." +"code was zero then return, otherwise raise :exc:`CalledProcessError`. " +"The :exc:`CalledProcessError` object will have the return code in " +"the :attr:`~CalledProcessError.returncode` attribute. If :func:`check_call` " +"was unable to start the process it will propagate the exception that was " +"raised." msgstr "" #: library/subprocess.rst:1217 @@ -1524,10 +1530,10 @@ msgstr "" #: library/subprocess.rst:1252 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." +"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 "" #: library/subprocess.rst:1257 @@ -1542,10 +1548,10 @@ msgstr "" msgid "" "The arguments shown above are merely some common ones. The full function " "signature is largely the same as that of :func:`run` - most arguments are " -"passed directly through to that interface. One API deviation from :func:" -"`run` behavior exists: passing ``input=None`` will behave the same as " -"``input=b''`` (or ``input=''``, depending on other arguments) rather than " -"using the parent's standard input file handle." +"passed directly through to that interface. One API deviation " +"from :func:`run` behavior exists: passing ``input=None`` will behave the " +"same as ``input=b''`` (or ``input=''``, depending on other arguments) rather " +"than using the parent's standard input file handle." msgstr "" #: library/subprocess.rst:1268 @@ -1564,8 +1570,8 @@ msgstr "" #: library/subprocess.rst:1276 msgid "" -"To also capture standard error in the result, use ``stderr=subprocess." -"STDOUT``::" +"To also capture standard error in the result, use " +"``stderr=subprocess.STDOUT``::" msgstr "" #: library/subprocess.rst:1279 @@ -1598,16 +1604,16 @@ msgstr "" #: library/subprocess.rst:1317 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." +"executed program cannot be found; the \"b\" replacements " +"raise :exc:`OSError` instead." msgstr "" #: library/subprocess.rst:1321 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." +"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 "" #: library/subprocess.rst:1326 @@ -1685,15 +1691,15 @@ msgstr "" #: library/subprocess.rst:1382 msgid "" -"The :func:`call` return value is encoded differently to that of :func:`os." -"system`." +"The :func:`call` return value is encoded differently to that " +"of :func:`os.system`." msgstr "" #: library/subprocess.rst:1385 msgid "" "The :func:`os.system` function ignores SIGINT and SIGQUIT signals while the " -"command is running, but the caller must do this separately when using the :" -"mod:`subprocess` module." +"command is running, but the caller must do this separately when using " +"the :mod:`subprocess` module." msgstr "" #: library/subprocess.rst:1389 @@ -1705,8 +1711,8 @@ msgid "" "try:\n" " retcode = call(\"mycmd\" + \" myarg\", shell=True)\n" " if retcode < 0:\n" -" print(\"Child was terminated by signal\", -retcode, file=sys." -"stderr)\n" +" print(\"Child was terminated by signal\", -retcode, " +"file=sys.stderr)\n" " else:\n" " print(\"Child returned\", retcode, file=sys.stderr)\n" "except OSError as e:\n" @@ -1846,8 +1852,8 @@ msgstr "" #: library/subprocess.rst:1500 msgid "" -":class:`popen2.Popen3` and :class:`popen2.Popen4` basically work as :class:" -"`subprocess.Popen`, except that:" +":class:`popen2.Popen3` and :class:`popen2.Popen4` basically work " +"as :class:`subprocess.Popen`, except that:" msgstr "" #: library/subprocess.rst:1503 @@ -1918,8 +1924,8 @@ msgstr "" #: library/subprocess.rst:1549 msgid "" "The function now returns (exitcode, output) instead of (status, output) as " -"it did in Python 3.3.3 and earlier. exitcode has the same value as :attr:" -"`~Popen.returncode`." +"it did in Python 3.3.3 and earlier. exitcode has the same value " +"as :attr:`~Popen.returncode`." msgstr "" #: library/subprocess.rst:1558 @@ -2011,8 +2017,8 @@ msgstr "" #: library/subprocess.rst:1624 msgid "" "If you ever encounter a presumed highly unusual situation where you need to " -"prevent ``vfork()`` from being used by Python, you can set the :const:" -"`subprocess._USE_VFORK` attribute to a false value." +"prevent ``vfork()`` from being used by Python, you can set " +"the :const:`subprocess._USE_VFORK` attribute to a false value." msgstr "" #: library/subprocess.rst:1630 @@ -2022,9 +2028,9 @@ msgstr "" #: library/subprocess.rst:1632 msgid "" "Setting this has no impact on use of ``posix_spawn()`` which could use " -"``vfork()`` internally within its libc implementation. There is a similar :" -"const:`subprocess._USE_POSIX_SPAWN` attribute if you need to prevent use of " -"that." +"``vfork()`` internally within its libc implementation. There is a " +"similar :const:`subprocess._USE_POSIX_SPAWN` attribute if you need to " +"prevent use of that." msgstr "" #: library/subprocess.rst:1639 diff --git a/library/sunau.po b/library/sunau.po index 4d136a123..83b470a4e 100644 --- a/library/sunau.po +++ b/library/sunau.po @@ -33,8 +33,8 @@ msgstr "" #: library/sunau.rst:18 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`." +"format. Note that this module is interface-compatible with the " +"modules :mod:`aifc` and :mod:`wave`." msgstr "" #: library/sunau.rst:22 @@ -230,8 +230,8 @@ msgstr "" #: library/sunau.rst:154 msgid "" "Returns a :func:`~collections.namedtuple` ``(nchannels, sampwidth, " -"framerate, nframes, comptype, compname)``, equivalent to output of the :meth:" -"`get\\*` methods." +"framerate, nframes, comptype, compname)``, equivalent to output of " +"the :meth:`get\\*` methods." msgstr "" #: library/sunau.rst:161 @@ -253,8 +253,8 @@ msgstr "" #: library/sunau.rst:176 msgid "" -"Set the file pointer to the specified position. Only values returned from :" -"meth:`tell` should be used for *pos*." +"Set the file pointer to the specified position. Only values returned " +"from :meth:`tell` should be used for *pos*." msgstr "" #: library/sunau.rst:182 @@ -265,8 +265,8 @@ msgstr "" #: library/sunau.rst:185 msgid "" -"The following two functions are defined for compatibility with the :mod:" -"`aifc`, and don't do anything interesting." +"The following two functions are defined for compatibility with " +"the :mod:`aifc`, and don't do anything interesting." msgstr "" #: library/sunau.rst:191 @@ -324,8 +324,8 @@ msgstr "" #: 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." +"Return current position in the file, with the same disclaimer for " +"the :meth:`AU_read.tell` and :meth:`AU_read.setpos` methods." msgstr "" #: library/sunau.rst:252 @@ -350,6 +350,6 @@ msgstr "" #: library/sunau.rst:272 msgid "" -"Note that it is invalid to set any parameters after calling :meth:" -"`writeframes` or :meth:`writeframesraw`." +"Note that it is invalid to set any parameters after " +"calling :meth:`writeframes` or :meth:`writeframesraw`." msgstr "" diff --git a/library/symtable.po b/library/symtable.po index 7e9f57661..1d0785eb3 100644 --- a/library/symtable.po +++ b/library/symtable.po @@ -76,8 +76,8 @@ msgid "" "``'top'`` if the table is global (:meth:`get_type` returns ``'module'``). " "For type parameter scopes (which are used for generic classes, functions, " "and type aliases), it is the name of the underlying class, function, or type " -"alias. For type alias scopes, it is the name of the type alias. For :class:" -"`~typing.TypeVar` bound scopes, it is the name of the ``TypeVar``." +"alias. For type alias scopes, it is the name of the type alias. " +"For :class:`~typing.TypeVar` bound scopes, it is the name of the ``TypeVar``." msgstr "" #: library/symtable.rst:65 @@ -100,8 +100,8 @@ msgstr "" #: library/symtable.rst:82 msgid "" -"Return a view object containing the names of symbols in the table. See the :" -"ref:`documentation of view objects `." +"Return a view object containing the names of symbols in the table. See " +"the :ref:`documentation of view objects `." msgstr "" #: library/symtable.rst:87 @@ -118,8 +118,8 @@ msgstr "" #: library/symtable.rst:100 msgid "" -"A namespace for a function or method. This class inherits from :class:" -"`SymbolTable`." +"A namespace for a function or method. This class inherits " +"from :class:`SymbolTable`." msgstr "" #: library/symtable.rst:105 diff --git a/library/sys.monitoring.po b/library/sys.monitoring.po index 788e663b6..f0cc853df 100644 --- a/library/sys.monitoring.po +++ b/library/sys.monitoring.po @@ -204,8 +204,8 @@ msgstr "" #: library/sys.monitoring.rst:145 msgid "" -"An exception is raised, except those that cause a :monitoring-event:" -"`STOP_ITERATION` event." +"An exception is raised, except those that cause a :monitoring-" +"event:`STOP_ITERATION` event." msgstr "" #: library/sys.monitoring.rst:149 @@ -319,9 +319,9 @@ msgstr "" #: library/sys.monitoring.rst:200 msgid "" "The :monitoring-event:`C_RETURN` and :monitoring-event:`C_RAISE` events are " -"controlled by the :monitoring-event:`CALL` event. :monitoring-event:" -"`C_RETURN` and :monitoring-event:`C_RAISE` events will only be seen if the " -"corresponding :monitoring-event:`CALL` event is being monitored." +"controlled by the :monitoring-event:`CALL` event. :monitoring-" +"event:`C_RETURN` and :monitoring-event:`C_RAISE` events will only be seen if " +"the corresponding :monitoring-event:`CALL` event is being monitored." msgstr "" #: library/sys.monitoring.rst:206 @@ -360,8 +360,8 @@ msgstr "" #: library/sys.monitoring.rst:222 msgid "" -":pep:`PEP 380 <380#use-of-stopiteration-to-return-values>` specifies that a :" -"exc:`StopIteration` exception is raised when returning a value from a " +":pep:`PEP 380 <380#use-of-stopiteration-to-return-values>` specifies that " +"a :exc:`StopIteration` exception is raised when returning a value from a " "generator or coroutine. However, this is a very inefficient way to return a " "value, so some Python implementations, notably CPython 3.12+, do not raise " "an exception unless it would be visible to other code." @@ -402,8 +402,8 @@ msgstr "" #: library/sys.monitoring.rst:253 msgid "" -"Activates all events which are set in *event_set*. Raises a :exc:" -"`ValueError` if *tool_id* is not in use." +"Activates all events which are set in *event_set*. Raises " +"a :exc:`ValueError` if *tool_id* is not in use." msgstr "" #: library/sys.monitoring.rst:256 @@ -446,9 +446,10 @@ msgstr "" #: library/sys.monitoring.rst:285 msgid "" -"Local events can be disabled for a specific code location by returning :data:" -"`sys.monitoring.DISABLE` from a callback function. This does not change " -"which events are set, or any other code locations for the same event." +"Local events can be disabled for a specific code location by " +"returning :data:`sys.monitoring.DISABLE` from a callback function. This does " +"not change which events are set, or any other code locations for the same " +"event." msgstr "" #: library/sys.monitoring.rst:289 @@ -486,8 +487,8 @@ msgstr "" #: library/sys.monitoring.rst:316 msgid "" -"Functions can be unregistered by calling ``sys.monitoring." -"register_callback(tool_id, event, None)``." +"Functions can be unregistered by calling " +"``sys.monitoring.register_callback(tool_id, event, None)``." msgstr "" #: library/sys.monitoring.rst:319 @@ -496,8 +497,8 @@ msgstr "" #: library/sys.monitoring.rst:321 msgid "" -"Registering or unregistering a callback function will generate a :func:`sys." -"audit` event." +"Registering or unregistering a callback function will generate " +"a :func:`sys.audit` event." msgstr "" #: library/sys.monitoring.rst:325 @@ -537,8 +538,8 @@ msgstr "" #: library/sys.monitoring.rst:343 msgid "" -":monitoring-event:`CALL`, :monitoring-event:`C_RAISE` and :monitoring-event:" -"`C_RETURN`::" +":monitoring-event:`CALL`, :monitoring-event:`C_RAISE` and :monitoring-" +"event:`C_RETURN`::" msgstr "" #: library/sys.monitoring.rst:345 @@ -554,9 +555,9 @@ msgstr "" #: library/sys.monitoring.rst:349 msgid "" -":monitoring-event:`RAISE`, :monitoring-event:`RERAISE`, :monitoring-event:" -"`EXCEPTION_HANDLED`, :monitoring-event:`PY_UNWIND`, :monitoring-event:" -"`PY_THROW` and :monitoring-event:`STOP_ITERATION`::" +":monitoring-event:`RAISE`, :monitoring-event:`RERAISE`, :monitoring-" +"event:`EXCEPTION_HANDLED`, :monitoring-event:`PY_UNWIND`, :monitoring-" +"event:`PY_THROW` and :monitoring-event:`STOP_ITERATION`::" msgstr "" #: library/sys.monitoring.rst:352 diff --git a/library/sys.po b/library/sys.po index 41153f80d..51a88fdad 100644 --- a/library/sys.po +++ b/library/sys.po @@ -68,8 +68,8 @@ msgid "" "particular, malicious code can trivially disable or bypass hooks added using " "this function. At a minimum, any security-sensitive hooks must be added " "using the C API :c:func:`PySys_AddAuditHook` before initialising the " -"runtime, and any modules allowing arbitrary memory modification (such as :" -"mod:`ctypes`) should be completely removed or closely monitored." +"runtime, and any modules allowing arbitrary memory modification (such " +"as :mod:`ctypes`) should be completely removed or closely monitored." msgstr "" #: library/sys.rst:51 @@ -155,8 +155,8 @@ msgstr "" #: library/sys.rst:119 msgid "" -"Hooks are added using the :func:`sys.addaudithook` or :c:func:" -"`PySys_AddAuditHook` functions." +"Hooks are added using the :func:`sys.addaudithook` " +"or :c:func:`PySys_AddAuditHook` functions." msgstr "" #: library/sys.rst:122 @@ -173,24 +173,26 @@ msgstr "" #: library/sys.rst:133 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)." +"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 "" #: library/sys.rst:147 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 " +"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)." +"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 "" #: library/sys.rst:160 @@ -220,9 +222,10 @@ msgstr "" #: library/sys.rst:180 msgid "" -"Tracing is suspended while calling a tracing function set by :func:" -"`settrace` or :func:`setprofile` to avoid infinite recursion. :func:`!" -"call_tracing` enables explicit recursion of the tracing function." +"Tracing is suspended while calling a tracing function set " +"by :func:`settrace` or :func:`setprofile` to avoid infinite " +"recursion. :func:`!call_tracing` enables explicit recursion of the tracing " +"function." msgstr "" #: library/sys.rst:187 @@ -307,29 +310,30 @@ msgstr "" #: library/sys.rst:246 msgid "" -"The default implementation first consults the environment variable :envvar:" -"`PYTHONBREAKPOINT`. If that is set to ``\"0\"`` then this function returns " -"immediately; i.e. it is a no-op. If the environment variable is not set, or " -"is set to the empty string, ``pdb.set_trace()`` is called. Otherwise this " -"variable should name a function to run, using Python's dotted-import " -"nomenclature, e.g. ``package.subpackage.module.function``. In this case, " +"The default implementation first consults the environment " +"variable :envvar:`PYTHONBREAKPOINT`. If that is set to ``\"0\"`` then this " +"function returns immediately; i.e. it is a no-op. If the environment " +"variable is not set, or is set to the empty string, ``pdb.set_trace()`` is " +"called. Otherwise this variable should name a function to run, using " +"Python's dotted-import nomenclature, e.g. " +"``package.subpackage.module.function``. In this case, " "``package.subpackage.module`` would be imported and the resulting module " "must have a callable named ``function()``. This is run, passing in " -"``*args`` and ``**kws``, and whatever ``function()`` returns, ``sys." -"breakpointhook()`` returns to the built-in :func:`breakpoint` function." +"``*args`` and ``**kws``, and whatever ``function()`` returns, " +"``sys.breakpointhook()`` returns to the built-in :func:`breakpoint` function." msgstr "" #: library/sys.rst:258 msgid "" -"Note that if anything goes wrong while importing the callable named by :" -"envvar:`PYTHONBREAKPOINT`, a :exc:`RuntimeWarning` is reported and the " +"Note that if anything goes wrong while importing the callable named " +"by :envvar:`PYTHONBREAKPOINT`, a :exc:`RuntimeWarning` is reported and the " "breakpoint is ignored." msgstr "" #: library/sys.rst:262 msgid "" -"Also note that if ``sys.breakpointhook()`` is overridden programmatically, :" -"envvar:`PYTHONBREAKPOINT` is *not* consulted." +"Also note that if ``sys.breakpointhook()`` is overridden " +"programmatically, :envvar:`PYTHONBREAKPOINT` is *not* consulted." msgstr "" #: library/sys.rst:269 @@ -357,19 +361,19 @@ msgstr "" #: library/sys.rst:293 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." +"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 "" #: library/sys.rst:299 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``." +"``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 "" #: library/sys.rst:303 @@ -405,9 +409,9 @@ msgstr "" 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." +"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 "" #: library/sys.rst:338 @@ -456,9 +460,9 @@ msgstr "" #: library/sys.rst:375 msgid "" "This value is initially set based on the value of the :option:`-X` " -"``pycache_prefix=PATH`` command-line option or the :envvar:" -"`PYTHONPYCACHEPREFIX` environment variable (command-line takes precedence). " -"If neither are set, it is ``None``." +"``pycache_prefix=PATH`` command-line option or " +"the :envvar:`PYTHONPYCACHEPREFIX` environment variable (command-line takes " +"precedence). If neither are set, it is ``None``." msgstr "" #: library/sys.rst:385 @@ -483,15 +487,15 @@ msgid "" "``type``, ``value``, ``traceback`` when an uncaught exception occurs. If no " "hook has been set, ``hook`` may be ``None``. If any hook raises an exception " "derived from :class:`RuntimeError` the call to the hook will be suppressed. " -"Otherwise, the audit hook exception will be reported as unraisable and ``sys." -"excepthook`` will be called." +"Otherwise, the audit hook exception will be reported as unraisable and " +"``sys.excepthook`` will be called." msgstr "" #: library/sys.rst:405 msgid "" "The :func:`sys.unraisablehook` function handles unraisable exceptions and " -"the :func:`threading.excepthook` function handles exception raised by :func:" -"`threading.Thread.run`." +"the :func:`threading.excepthook` function handles exception raised " +"by :func:`threading.Thread.run`." msgstr "" #: library/sys.rst:415 @@ -527,11 +531,11 @@ msgstr "" msgid "" "This function returns the old-style representation of the handled exception. " "If an exception ``e`` is currently handled (so :func:`exception` would " -"return ``e``), :func:`exc_info` returns the tuple ``(type(e), e, e." -"__traceback__)``. That is, a tuple containing the type of the exception (a " -"subclass of :exc:`BaseException`), the exception itself, and a :ref:" -"`traceback object ` which typically encapsulates the call " -"stack at the point where the exception last occurred." +"return ``e``), :func:`exc_info` returns the tuple ``(type(e), e, " +"e.__traceback__)``. That is, a tuple containing the type of the exception (a " +"subclass of :exc:`BaseException`), the exception itself, and " +"a :ref:`traceback object ` which typically encapsulates " +"the call stack at the point where the exception last occurred." msgstr "" #: library/sys.rst:453 @@ -544,8 +548,8 @@ msgstr "" msgid "" "The ``type`` and ``traceback`` fields are now derived from the ``value`` " "(the exception instance), so when an exception is modified while it is being " -"handled, the changes are reflected in the results of subsequent calls to :" -"func:`exc_info`." +"handled, the changes are reflected in the results of subsequent calls " +"to :func:`exc_info`." msgstr "" #: library/sys.rst:464 @@ -554,18 +558,18 @@ msgid "" "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``." +"(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 "" #: library/sys.rst:475 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`." +"the Python installation will still be available, " +"via :data:`base_exec_prefix`." msgstr "" #: library/sys.rst:483 @@ -609,9 +613,9 @@ msgstr "" #: library/sys.rst:511 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." +"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 "" #: library/sys.rst:519 @@ -894,8 +898,8 @@ msgstr "" #: library/sys.rst:688 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 " +"``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 "" @@ -937,8 +941,9 @@ 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." +"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 "" #: library/sys.rst:730 @@ -973,8 +978,8 @@ msgid "" "Get the :term:`filesystem encoding `: " "the encoding used with the :term:`filesystem error handler ` to convert between Unicode filenames and bytes " -"filenames. The filesystem error handler is returned from :func:" -"`getfilesystemencodeerrors`." +"filenames. The filesystem error handler is returned " +"from :func:`getfilesystemencodeerrors`." msgstr "" #: library/sys.rst:776 @@ -994,9 +999,9 @@ msgstr "" #: library/sys.rst:812 msgid "" "The :term:`filesystem encoding and error handler` are configured at Python " -"startup by the :c:func:`PyConfig_Read` function: see :c:member:`~PyConfig." -"filesystem_encoding` and :c:member:`~PyConfig.filesystem_errors` members of :" -"c:type:`PyConfig`." +"startup by the :c:func:`PyConfig_Read` function: " +"see :c:member:`~PyConfig.filesystem_encoding` " +"and :c:member:`~PyConfig.filesystem_errors` members of :c:type:`PyConfig`." msgstr "" #: library/sys.rst:789 @@ -1005,8 +1010,8 @@ msgstr "" #: library/sys.rst:792 msgid "" -"Windows is no longer guaranteed to return ``'mbcs'``. See :pep:`529` and :" -"func:`_enablelegacywindowsfsencoding` for more information." +"Windows is no longer guaranteed to return ``'mbcs'``. See :pep:`529` " +"and :func:`_enablelegacywindowsfsencoding` for more information." msgstr "" #: library/sys.rst:796 @@ -1019,8 +1024,8 @@ msgid "" "Get the :term:`filesystem error handler `: the error handler used with the :term:`filesystem encoding " "` to convert between Unicode " -"filenames and bytes filenames. The filesystem encoding is returned from :" -"func:`getfilesystemencoding`." +"filenames and bytes filenames. The filesystem encoding is returned " +"from :func:`getfilesystemencoding`." msgstr "" #: library/sys.rst:821 @@ -1055,8 +1060,8 @@ msgstr "" 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`." +"causing an overflow of the C stack and crashing Python. It can be set " +"by :func:`setrecursionlimit`." msgstr "" #: library/sys.rst:852 @@ -1095,8 +1100,8 @@ msgstr "" #: library/sys.rst:873 msgid "" -"Return the interpreter's \"thread switch interval\"; see :func:" -"`setswitchinterval`." +"Return the interpreter's \"thread switch interval\"; " +"see :func:`setswitchinterval`." msgstr "" #: library/sys.rst:881 @@ -1158,9 +1163,9 @@ msgid "" "*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." +"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 "" #: library/sys.rst:948 @@ -1237,12 +1242,12 @@ msgstr "" #: library/sys.rst:990 msgid "" -"Returns an *asyncgen_hooks* object, which is similar to a :class:" -"`~collections.namedtuple` of the form ``(firstiter, finalizer)``, where " -"*firstiter* and *finalizer* are expected to be either ``None`` or functions " -"which take an :term:`asynchronous generator iterator` as an argument, and " -"are used to schedule finalization of an asynchronous generator by an event " -"loop." +"Returns an *asyncgen_hooks* object, which is similar to " +"a :class:`~collections.namedtuple` of the form ``(firstiter, finalizer)``, " +"where *firstiter* and *finalizer* are expected to be either ``None`` or " +"functions which take an :term:`asynchronous generator iterator` as an " +"argument, and are used to schedule finalization of an asynchronous generator " +"by an event loop." msgstr "" #: library/sys.rst:997 @@ -1257,8 +1262,8 @@ msgstr "" #: library/sys.rst:1007 msgid "" -"Get the current coroutine origin tracking depth, as set by :func:" -"`set_coroutine_origin_tracking_depth`." +"Get the current coroutine origin tracking depth, as set " +"by :func:`set_coroutine_origin_tracking_depth`." msgstr "" #: library/sys.rst:1699 @@ -1367,8 +1372,8 @@ msgstr "" #: library/sys.rst:1102 msgid "" -"*hexversion* is the implementation version in hexadecimal format, like :data:" -"`sys.hexversion`." +"*hexversion* is the implementation version in hexadecimal format, " +"like :data:`sys.hexversion`." msgstr "" #: library/sys.rst:1105 @@ -1384,10 +1389,10 @@ msgstr "" 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." +"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 "" #: library/sys.rst:1123 @@ -1420,14 +1425,15 @@ msgstr "" #: library/sys.rst:1147 msgid "" -"The minimum non-zero value for :func:`sys.set_int_max_str_digits`, :envvar:" -"`PYTHONINTMAXSTRDIGITS`, or :option:`-X int_max_str_digits <-X>`." +"The minimum non-zero value " +"for :func:`sys.set_int_max_str_digits`, :envvar:`PYTHONINTMAXSTRDIGITS`, " +"or :option:`-X int_max_str_digits <-X>`." msgstr "" #: library/sys.rst:1154 msgid "" -"Added :attr:`~int_info.default_max_str_digits` and :attr:`~int_info." -"str_digits_check_threshold`." +"Added :attr:`~int_info.default_max_str_digits` " +"and :attr:`~int_info.str_digits_check_threshold`." msgstr "" #: library/sys.rst:1160 @@ -1483,8 +1489,8 @@ msgstr "" #: library/sys.rst:1212 msgid "" "These three variables are deprecated; use :data:`sys.last_exc` instead. They " -"hold the legacy representation of ``sys.last_exc``, as returned from :func:" -"`exc_info` above." +"hold the legacy representation of ``sys.last_exc``, as returned " +"from :func:`exc_info` above." msgstr "" #: library/sys.rst:1218 @@ -1509,15 +1515,16 @@ msgstr "" #: library/sys.rst:1236 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. By default, it holds entries that " -"implement Python's default import semantics. 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:`~module.__path__` attribute is " -"passed in as a second argument. The method returns a :term:`module spec`, or " -"``None`` if the module cannot be found." +"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. By default, it " +"holds entries that implement Python's default import semantics. " +"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:`~module.__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 "" #: library/sys.rst:1249 @@ -1526,8 +1533,8 @@ msgstr "" #: library/sys.rst:1250 msgid "" -"The abstract base class defining the interface of finder objects on :data:" -"`meta_path`." +"The abstract base class defining the interface of finder objects " +"on :data:`meta_path`." msgstr "" #: library/sys.rst:1252 @@ -1542,15 +1549,15 @@ msgstr "" #: library/sys.rst:1259 msgid "" -":term:`Module specs ` were introduced in Python 3.4, by :pep:" -"`451`." +":term:`Module specs ` were introduced in Python 3.4, " +"by :pep:`451`." msgstr "" #: library/sys.rst:1264 msgid "" -"Removed the fallback that looked for a :meth:`!find_module` method if a :" -"data:`meta_path` entry didn't have a :meth:`~importlib.abc.MetaPathFinder." -"find_spec` method." +"Removed the fallback that looked for a :meth:`!find_module` method if " +"a :data:`meta_path` entry didn't have " +"a :meth:`~importlib.abc.MetaPathFinder.find_spec` method." msgstr "" #: library/sys.rst:1270 @@ -1625,15 +1632,15 @@ msgstr "" #: library/sys.rst:1321 msgid "" -"Module :mod:`site` This describes how to use .pth files to extend :data:`sys." -"path`." +"Module :mod:`site` This describes how to use .pth files to " +"extend :data:`sys.path`." msgstr "" #: library/sys.rst:1326 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`." +"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 "" #: library/sys.rst:1341 @@ -1778,8 +1785,8 @@ msgstr "" #: library/sys.rst:1402 msgid "" "It is equal to ``\"lib\"`` on most platforms. On Fedora and SuSE, it is " -"equal to ``\"lib64\"`` on 64-bit platforms which gives the following ``sys." -"path`` paths (where ``X.Y`` is the Python ``major.minor`` version):" +"equal to ``\"lib64\"`` on 64-bit platforms which gives the following " +"``sys.path`` paths (where ``X.Y`` is the Python ``major.minor`` version):" msgstr "" #: library/sys.rst:1406 @@ -1797,8 +1804,8 @@ msgstr "" #: library/sys.rst:1411 msgid "" -"``/usr/lib/pythonX.Y/site-packages/`` (always use ``lib``, not :data:`sys." -"platlibdir`): Third-party modules" +"``/usr/lib/pythonX.Y/site-packages/`` (always use ``lib``, " +"not :data:`sys.platlibdir`): Third-party modules" msgstr "" #: library/sys.rst:1413 @@ -1840,15 +1847,15 @@ msgid "" "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 (:samp:`RTLD_{xxx}` constants, e." -"g. :const:`os.RTLD_LAZY`)." +"values can be found in the :mod:`os` module (:samp:`RTLD_{xxx}` constants, " +"e.g. :const:`os.RTLD_LAZY`)." msgstr "" #: library/sys.rst:1464 msgid "" "Set the :ref:`integer string conversion length limitation " -"` used by this interpreter. See also :func:" -"`get_int_max_str_digits`." +"` used by this interpreter. See " +"also :func:`get_int_max_str_digits`." msgstr "" #: library/sys.rst:1476 @@ -1868,9 +1875,9 @@ msgstr "" #: library/sys.rst:1488 msgid "" -"The same tracing mechanism is used for :func:`!setprofile` as :func:" -"`settrace`. To trace calls with :func:`!setprofile` inside a tracing " -"function (e.g. in a debugger breakpoint), see :func:`call_tracing`." +"The same tracing mechanism is used for :func:`!setprofile` " +"as :func:`settrace`. To trace calls with :func:`!setprofile` inside a " +"tracing function (e.g. in a debugger breakpoint), see :func:`call_tracing`." msgstr "" #: library/sys.rst:1492 @@ -1955,8 +1962,8 @@ msgstr "" #: library/sys.rst:1532 msgid "" -"If the new limit is too low at the current recursion depth, a :exc:" -"`RecursionError` exception is raised." +"If the new limit is too low at the current recursion depth, " +"a :exc:`RecursionError` exception is raised." msgstr "" #: library/sys.rst:1535 @@ -1981,8 +1988,8 @@ 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 register a trace function " -"using :func:`settrace` for each thread being debugged or use :func:" -"`threading.settrace`." +"using :func:`settrace` for each thread being debugged or " +"use :func:`threading.settrace`." msgstr "" #: library/sys.rst:1564 @@ -2068,9 +2075,9 @@ msgid "" "The interpreter is about to execute a new opcode (see :mod:`dis` for opcode " "details). The local trace function is called; *arg* is ``None``; the return " "value specifies the new local trace function. Per-opcode events are not " -"emitted by default: they must be explicitly requested by setting :attr:" -"`~frame.f_trace_opcodes` to :const:`True` on the :ref:`frame `." +"emitted by default: they must be explicitly requested by " +"setting :attr:`~frame.f_trace_opcodes` to :const:`True` on the :ref:`frame " +"`." msgstr "" #: library/sys.rst:1620 @@ -2086,11 +2093,11 @@ msgid "" "it being set indirectly via the return value from an already installed trace " "function. This is also required for activating the trace function on the " "current frame, which :func:`settrace` doesn't do. Note that in order for " -"this to work, a global tracing function must have been installed with :func:" -"`settrace` in order to enable the runtime tracing machinery, but it doesn't " -"need to be the same tracing function (e.g. it could be a low overhead " -"tracing function that simply returns ``None`` to disable itself immediately " -"on each frame)." +"this to work, a global tracing function must have been installed " +"with :func:`settrace` in order to enable the runtime tracing machinery, but " +"it doesn't need to be the same tracing function (e.g. it could be a low " +"overhead tracing function that simply returns ``None`` to disable itself " +"immediately on each frame)." msgstr "" #: library/sys.rst:1634 @@ -2113,8 +2120,8 @@ msgstr "" #: library/sys.rst:1647 msgid "" -"``'opcode'`` event type added; :attr:`~frame.f_trace_lines` and :attr:" -"`~frame.f_trace_opcodes` attributes added to frames" +"``'opcode'`` event type added; :attr:`~frame.f_trace_lines` " +"and :attr:`~frame.f_trace_opcodes` attributes added to frames" msgstr "" #: library/sys.rst:1650 @@ -2127,8 +2134,8 @@ msgstr "" #: library/sys.rst:1658 msgid "" -"Accepts two optional keyword arguments which are callables that accept an :" -"term:`asynchronous generator iterator` as an argument. The *firstiter* " +"Accepts two optional keyword arguments which are callables that accept " +"an :term:`asynchronous generator iterator` as an argument. The *firstiter* " "callable will be called when an asynchronous generator is iterated for the " "first time. The *finalizer* will be called when an asynchronous generator is " "about to be garbage collected." @@ -2136,14 +2143,14 @@ msgstr "" #: library/sys.rst:1664 msgid "" -"Raises an :ref:`auditing event ` ``sys." -"set_asyncgen_hooks_firstiter`` with no arguments." +"Raises an :ref:`auditing event ` " +"``sys.set_asyncgen_hooks_firstiter`` with no arguments." msgstr "" #: library/sys.rst:1666 msgid "" -"Raises an :ref:`auditing event ` ``sys." -"set_asyncgen_hooks_finalizer`` with no arguments." +"Raises an :ref:`auditing event ` " +"``sys.set_asyncgen_hooks_finalizer`` with no arguments." msgstr "" #: library/sys.rst:1668 @@ -2155,8 +2162,8 @@ msgstr "" #: library/sys.rst:1671 msgid "" "See :pep:`525` for more details, and for a reference example of a " -"*finalizer* method see the implementation of ``asyncio.Loop." -"shutdown_asyncgens`` in :source:`Lib/asyncio/base_events.py`" +"*finalizer* method see the implementation of " +"``asyncio.Loop.shutdown_asyncgens`` in :source:`Lib/asyncio/base_events.py`" msgstr "" #: library/sys.rst:1683 @@ -2219,8 +2226,8 @@ msgstr "" #: library/sys.rst:1743 msgid "" -"See also :func:`sys.getfilesystemencoding` and :func:`sys." -"getfilesystemencodeerrors`." +"See also :func:`sys.getfilesystemencoding` " +"and :func:`sys.getfilesystemencodeerrors`." msgstr "" #: library/sys.rst:1748 @@ -2235,8 +2242,8 @@ msgstr "" #: library/sys.rst:1758 msgid "" -"``stdin`` is used for all interactive input (including calls to :func:" -"`input`);" +"``stdin`` is used for all interactive input (including calls " +"to :func:`input`);" msgstr "" #: library/sys.rst:1760 @@ -2257,8 +2264,9 @@ msgstr "" #: library/sys.rst:1768 msgid "" -"The encoding and error handling are is initialized from :c:member:`PyConfig." -"stdio_encoding` and :c:member:`PyConfig.stdio_errors`." +"The encoding and error handling are is initialized " +"from :c:member:`PyConfig.stdio_encoding` " +"and :c:member:`PyConfig.stdio_errors`." msgstr "" #: library/sys.rst:1771 @@ -2281,11 +2289,12 @@ msgstr "" #: library/sys.rst:1785 msgid "" -"Under all platforms, you can override the character encoding by setting the :" -"envvar:`PYTHONIOENCODING` environment variable before starting Python or by " -"using the new :option:`-X` ``utf8`` command line option and :envvar:" -"`PYTHONUTF8` environment variable. However, for the Windows console, this " -"only applies when :envvar:`PYTHONLEGACYWINDOWSSTDIO` is also set." +"Under all platforms, you can override the character encoding by setting " +"the :envvar:`PYTHONIOENCODING` environment variable before starting Python " +"or by using the new :option:`-X` ``utf8`` command line option " +"and :envvar:`PYTHONUTF8` environment variable. However, for the Windows " +"console, this only applies when :envvar:`PYTHONLEGACYWINDOWSSTDIO` is also " +"set." msgstr "" #: library/sys.rst:1792 @@ -2293,8 +2302,8 @@ msgid "" "When interactive, the ``stdout`` stream is line-buffered. Otherwise, it is " "block-buffered like regular text files. The ``stderr`` stream is line-" "buffered in both cases. You can make both streams unbuffered by passing " -"the :option:`-u` command-line option or setting the :envvar:" -"`PYTHONUNBUFFERED` environment variable." +"the :option:`-u` command-line option or setting " +"the :envvar:`PYTHONUNBUFFERED` environment variable." msgstr "" #: library/sys.rst:1798 @@ -2462,8 +2471,8 @@ msgstr "" #: library/sys.rst:1909 msgid "" "The default hook formats :attr:`!err_msg` and :attr:`!object` as: " -"``f'{err_msg}: {object!r}'``; use \"Exception ignored in\" error message if :" -"attr:`!err_msg` is ``None``." +"``f'{err_msg}: {object!r}'``; use \"Exception ignored in\" error message " +"if :attr:`!err_msg` is ``None``." msgstr "" #: library/sys.rst:1913 @@ -2520,8 +2529,8 @@ msgid "" "*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." +"also be accessed by name, so ``sys.version_info[0]`` is equivalent to " +"``sys.version_info.major`` and so on." msgstr "" #: library/sys.rst:1964 diff --git a/library/sys_path_init.po b/library/sys_path_init.po index 70fd3c84f..9e08c43d9 100644 --- a/library/sys_path_init.po +++ b/library/sys_path_init.po @@ -30,8 +30,8 @@ msgstr "" msgid "" "The first entry in the module search path is the directory that contains the " "input script, if there is one. Otherwise, the first entry is the current " -"directory, which is the case when executing the interactive shell, a :option:" -"`-c` command, or :option:`-m` module." +"directory, which is the case when executing the interactive shell, " +"a :option:`-c` command, or :option:`-m` module." msgstr "" #: library/sys_path_init.rst:14 @@ -72,25 +72,25 @@ msgstr "" #: library/sys_path_init.rst:37 msgid "" "Once ``home`` is determined, the ``prefix`` directory is found by first " -"looking for :file:`python{majorversion}{minorversion}.zip` (``python311." -"zip``). On Windows the zip archive is searched for in ``home`` and on Unix " -"the archive is expected to be in :file:`lib`. Note that the expected zip " -"archive location is added to the module search path even if the archive does " -"not exist. If no archive was found, Python on Windows will continue the " -"search for ``prefix`` by looking for :file:`Lib\\\\os.py`. Python on Unix " -"will look for :file:`lib/python{majorversion}.{minorversion}/os.py` (``lib/" -"python3.11/os.py``). On Windows ``prefix`` and ``exec_prefix`` are the same, " -"however on other platforms :file:`lib/python{majorversion}.{minorversion}/" -"lib-dynload` (``lib/python3.11/lib-dynload``) is searched for and used as an " -"anchor for ``exec_prefix``. On some platforms :file:`lib` may be :file:" -"`lib64` or another value, see :data:`sys.platlibdir` and :envvar:" -"`PYTHONPLATLIBDIR`." +"looking for :file:`python{majorversion}{minorversion}.zip` " +"(``python311.zip``). On Windows the zip archive is searched for in ``home`` " +"and on Unix the archive is expected to be in :file:`lib`. Note that the " +"expected zip archive location is added to the module search path even if the " +"archive does not exist. If no archive was found, Python on Windows will " +"continue the search for ``prefix`` by looking for :file:`Lib\\\\os.py`. " +"Python on Unix will look for :file:`lib/python{majorversion}.{minorversion}/" +"os.py` (``lib/python3.11/os.py``). On Windows ``prefix`` and ``exec_prefix`` " +"are the same, however on other platforms :file:`lib/python{majorversion}." +"{minorversion}/lib-dynload` (``lib/python3.11/lib-dynload``) is searched for " +"and used as an anchor for ``exec_prefix``. On some platforms :file:`lib` may " +"be :file:`lib64` or another value, see :data:`sys.platlibdir` " +"and :envvar:`PYTHONPLATLIBDIR`." msgstr "" #: library/sys_path_init.rst:50 msgid "" -"Once found, ``prefix`` and ``exec_prefix`` are available at :data:`sys." -"prefix` and :data:`sys.exec_prefix` respectively." +"Once found, ``prefix`` and ``exec_prefix`` are available " +"at :data:`sys.prefix` and :data:`sys.exec_prefix` respectively." msgstr "" #: library/sys_path_init.rst:53 @@ -103,8 +103,9 @@ msgstr "" #: library/sys_path_init.rst:60 msgid "" -"Certain command line options may further affect path calculations. See :" -"option:`-E`, :option:`-I`, :option:`-s` and :option:`-S` for further details." +"Certain command line options may further affect path calculations. " +"See :option:`-E`, :option:`-I`, :option:`-s` and :option:`-S` for further " +"details." msgstr "" #: library/sys_path_init.rst:64 @@ -167,11 +168,12 @@ msgstr "" #: library/sys_path_init.rst:100 msgid "" -"If Python is embedded within another application :c:func:" -"`Py_InitializeFromConfig` and the :c:type:`PyConfig` structure can be used " -"to initialize Python. The path specific details are described at :ref:`init-" -"path-config`. Alternatively the older :c:func:`Py_SetPath` can be used to " -"bypass the initialization of the module search path." +"If Python is embedded within another " +"application :c:func:`Py_InitializeFromConfig` and the :c:type:`PyConfig` " +"structure can be used to initialize Python. The path specific details are " +"described at :ref:`init-path-config`. Alternatively the " +"older :c:func:`Py_SetPath` can be used to bypass the initialization of the " +"module search path." msgstr "" #: library/sys_path_init.rst:107 diff --git a/library/sysconfig.po b/library/sysconfig.po index 0c7aeffe7..e62c17d5b 100644 --- a/library/sysconfig.po +++ b/library/sysconfig.po @@ -101,10 +101,10 @@ msgstr "" #: library/sysconfig.rst:70 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`. The schemes are used by package installers to determine where to " -"copy files to." +"and on the installation options. These schemes are stored " +"in :mod:`sysconfig` under unique identifiers based on the value returned " +"by :const:`os.name`. The schemes are used by package installers to determine " +"where to copy files to." msgstr "" #: library/sysconfig.rst:75 @@ -126,8 +126,8 @@ msgstr "" #: library/sysconfig.rst:81 msgid "" "*posix_user*: scheme for POSIX platforms, when the *user* option is used. " -"This scheme defines paths located under the user's home directory (:const:" -"`site.USER_BASE`)." +"This scheme defines paths located under the user's home directory " +"(:const:`site.USER_BASE`)." msgstr "" #: library/sysconfig.rst:84 @@ -225,8 +225,8 @@ msgstr "" msgid "" "Files will be installed into subdirectories of :const:`site.USER_BASE` " "(written as :file:`{userbase}` hereafter). This scheme installs pure Python " -"modules and extension modules in the same location (also known as :const:" -"`site.USER_SITE`)." +"modules and extension modules in the same location (also known " +"as :const:`site.USER_SITE`)." msgstr "" #: library/sysconfig.rst:126 @@ -339,8 +339,8 @@ 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 " +"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 "" @@ -459,8 +459,8 @@ msgstr "" #: library/sysconfig.rst:265 msgid "" -"Return a tuple containing all schemes currently supported in :mod:" -"`sysconfig`." +"Return a tuple containing all schemes currently supported " +"in :mod:`sysconfig`." msgstr "" #: library/sysconfig.rst:271 @@ -512,14 +512,14 @@ msgstr "" #: library/sysconfig.rst:307 msgid "" -"End users should not use this function, but :func:`get_default_scheme` and :" -"func:`get_preferred_scheme` instead." +"End users should not use this function, but :func:`get_default_scheme` " +"and :func:`get_preferred_scheme` instead." msgstr "" #: library/sysconfig.rst:315 msgid "" -"Return a tuple containing all path names currently supported in :mod:" -"`sysconfig`." +"Return a tuple containing all path names currently supported " +"in :mod:`sysconfig`." msgstr "" #: library/sysconfig.rst:321 @@ -549,9 +549,9 @@ msgstr "" #: library/sysconfig.rst:334 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." +"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 "" #: library/sysconfig.rst:338 @@ -594,8 +594,8 @@ msgstr "" #: library/sysconfig.rst:360 msgid "" -"If *scheme* is not an existing scheme, :func:`get_paths` will raise a :exc:" -"`KeyError`." +"If *scheme* is not an existing scheme, :func:`get_paths` will raise " +"a :exc:`KeyError`." msgstr "" #: library/sysconfig.rst:365 @@ -740,9 +740,9 @@ msgstr "" #: library/sysconfig.rst:461 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`." +"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 "" #: library/sysconfig.rst:14 diff --git a/library/syslog.po b/library/syslog.po index c3b3127ed..a78df6c03 100644 --- a/library/syslog.po +++ b/library/syslog.po @@ -34,8 +34,8 @@ msgstr "" #: library/syslog.rst:16 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`." +"library that can speak to a syslog server is available in " +"the :mod:`logging.handlers` module as :class:`SysLogHandler`." msgstr "" #: library/syslog.rst:20 @@ -54,8 +54,8 @@ msgstr "" #: library/syslog.rst:33 msgid "" -"If :func:`openlog` has not been called prior to the call to :func:`syslog`, :" -"func:`openlog` will be called with no arguments." +"If :func:`openlog` has not been called prior to the call " +"to :func:`syslog`, :func:`openlog` will be called with no arguments." msgstr "" #: library/syslog.rst:36 @@ -75,16 +75,16 @@ msgstr "" msgid "" "This function is restricted in subinterpreters. (Only code that runs in " "multiple interpreters is affected and the restriction is not relevant for " -"most users.) :func:`openlog` must be called in the main interpreter before :" -"func:`syslog` may be used in a subinterpreter. Otherwise it will raise :exc:" -"`RuntimeError`." +"most users.) :func:`openlog` must be called in the main interpreter " +"before :func:`syslog` may be used in a subinterpreter. Otherwise it will " +"raise :exc:`RuntimeError`." msgstr "" #: library/syslog.rst:53 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." +"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 "" #: library/syslog.rst:57 @@ -113,8 +113,8 @@ msgstr "" msgid "" "This function is restricted in subinterpreters. (Only code that runs in " "multiple interpreters is affected and the restriction is not relevant for " -"most users.) This may only be called in the main interpreter. It will raise :" -"exc:`RuntimeError` if called in a subinterpreter." +"most users.) This may only be called in the main interpreter. It will " +"raise :exc:`RuntimeError` if called in a subinterpreter." msgstr "" #: library/syslog.rst:80 @@ -126,8 +126,8 @@ msgstr "" 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." +"(if :func:`openlog` hasn't already been called), and *ident* and " +"other :func:`openlog` parameters are reset to defaults." msgstr "" #: library/syslog.rst:87 @@ -161,10 +161,7 @@ msgid "Priority levels (high to low):" msgstr "" #: library/syslog.rst:111 -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`." +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 "" #: library/syslog.rst:115 @@ -173,10 +170,9 @@ msgstr "" #: library/syslog.rst:116 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`." +":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 "" #: library/syslog.rst:122 @@ -186,8 +182,8 @@ msgstr "" #: library/syslog.rst:123 msgid "" ":const:`LOG_PID`, :const:`LOG_CONS`, :const:`LOG_NDELAY`, and, if defined in " -"````, :const:`LOG_ODELAY`, :const:`LOG_NOWAIT`, and :const:" -"`LOG_PERROR`." +"````, :const:`LOG_ODELAY`, :const:`LOG_NOWAIT`, " +"and :const:`LOG_PERROR`." msgstr "" #: library/syslog.rst:129 diff --git a/library/tabnanny.po b/library/tabnanny.po index 57574115c..85b4daaca 100644 --- a/library/tabnanny.po +++ b/library/tabnanny.po @@ -67,8 +67,8 @@ msgstr "" #: library/tabnanny.rst:57 msgid "" -"This function is used by :func:`check` to process tokens generated by the :" -"mod:`tokenize` module." +"This function is used by :func:`check` to process tokens generated by " +"the :mod:`tokenize` module." msgstr "" #: library/tabnanny.rst:66 diff --git a/library/tarfile.po b/library/tarfile.po index bf6b3b766..d69ee7010 100644 --- a/library/tarfile.po +++ b/library/tarfile.po @@ -144,8 +144,8 @@ msgstr "" #: library/tarfile.rst:71 msgid "" -"Create a tarfile exclusively without compression. Raise a :exc:" -"`FileExistsError` exception if it already exists." +"Create a tarfile exclusively without compression. Raise " +"a :exc:`FileExistsError` exception if it already exists." msgstr "" #: library/tarfile.rst:76 @@ -223,9 +223,9 @@ msgstr "" #: library/tarfile.rst:100 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." +"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 "" #: library/tarfile.rst:105 @@ -252,13 +252,14 @@ 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:`~io.RawIOBase.read` or :meth:`~io.RawIOBase.write` method (depending " -"on the *mode*) that works with bytes. *bufsize* specifies the blocksize and " -"defaults to ``20 * 512`` bytes. Use this variant in combination with e.g. " -"``sys.stdin.buffer``, 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:" +"will be done on the file. If given, *fileobj* may be any object that has " +"a :meth:`~io.RawIOBase.read` or :meth:`~io.RawIOBase.write` method " +"(depending on the *mode*) that works with bytes. *bufsize* specifies the " +"blocksize and defaults to ``20 * 512`` bytes. Use this variant in " +"combination with e.g. ``sys.stdin.buffer``, 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 "" #: library/tarfile.rst:129 @@ -361,9 +362,9 @@ msgstr "" #: library/tarfile.rst:177 msgid "" -"Return :const:`True` if *name* is a tar archive file, that the :mod:" -"`tarfile` module can read. *name* may be a :class:`str`, file, or file-like " -"object." +"Return :const:`True` if *name* is a tar archive file, that " +"the :mod:`tarfile` module can read. *name* may be a :class:`str`, file, or " +"file-like object." msgstr "" #: library/tarfile.rst:180 @@ -392,8 +393,8 @@ msgstr "" #: library/tarfile.rst:206 msgid "" -"Is raised for the limitations that are typical for stream-like :class:" -"`TarFile` objects." +"Is raised for the limitations that are typical for stream-" +"like :class:`TarFile` objects." msgstr "" #: library/tarfile.rst:212 @@ -413,8 +414,8 @@ msgstr "" #: library/tarfile.rst:228 msgid "" -"Information about the member that the filter refused to extract, as :ref:" -"`TarInfo `." +"Information about the member that the filter refused to extract, " +"as :ref:`TarInfo `." msgstr "" #: library/tarfile.rst:233 @@ -495,9 +496,9 @@ msgstr "" #: library/tarfile.rst:306 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." +"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 "" #: library/tarfile.rst:313 @@ -514,14 +515,14 @@ msgstr "" #: library/tarfile.rst:328 msgid "" -"The default format for creating archives. This is currently :const:" -"`PAX_FORMAT`." +"The default format for creating archives. This is " +"currently :const:`PAX_FORMAT`." msgstr "" #: library/tarfile.rst:330 msgid "" -"The default format for new archives was changed to :const:`PAX_FORMAT` from :" -"const:`GNU_FORMAT`." +"The default format for new archives was changed to :const:`PAX_FORMAT` " +"from :const:`GNU_FORMAT`." msgstr "" #: library/tarfile.rst:337 @@ -561,17 +562,17 @@ 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." +"in a tar archive several times. Each archive member is represented by " +"a :class:`TarInfo` object, see :ref:`tarinfo-objects` for details." msgstr "" #: library/tarfile.rst:359 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." +"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 "" #: library/tarfile.rst:365 @@ -655,8 +656,8 @@ msgstr "" 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." +"to be handled. The default settings will work for most users. See " +"section :ref:`tar-unicode` for in-depth information." msgstr "" #: library/tarfile.rst:416 @@ -713,9 +714,9 @@ msgstr "" #: library/tarfile.rst:471 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." +"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 "" #: library/tarfile.rst:478 @@ -782,8 +783,8 @@ msgstr "" #: library/tarfile.rst:524 msgid "" -"The *numeric_owner* and *filter* arguments are the same as for :meth:" -"`extractall`." +"The *numeric_owner* and *filter* arguments are the same as " +"for :meth:`extractall`." msgstr "" #: library/tarfile.rst:529 @@ -815,12 +816,12 @@ msgstr "" #: library/tarfile.rst:566 msgid "" -"If *errorlevel* is ``0``, errors are ignored when using :meth:`TarFile." -"extract` and :meth:`TarFile.extractall`. Nevertheless, they appear as error " -"messages in the debug output when *debug* is greater than 0. If ``1`` (the " -"default), all *fatal* errors are raised as :exc:`OSError` or :exc:" -"`FilterError` exceptions. If ``2``, all *non-fatal* errors are raised as :" -"exc:`TarError` exceptions as well." +"If *errorlevel* is ``0``, errors are ignored when " +"using :meth:`TarFile.extract` and :meth:`TarFile.extractall`. Nevertheless, " +"they appear as error messages in the debug output when *debug* is greater " +"than 0. If ``1`` (the default), all *fatal* errors are raised " +"as :exc:`OSError` or :exc:`FilterError` exceptions. If ``2``, all *non-" +"fatal* errors are raised as :exc:`TarError` exceptions as well." msgstr "" #: library/tarfile.rst:574 @@ -831,9 +832,9 @@ msgstr "" #: library/tarfile.rst:577 msgid "" -"Custom :ref:`extraction filters ` should raise :" -"exc:`FilterError` for *fatal* errors and :exc:`ExtractError` for *non-fatal* " -"ones." +"Custom :ref:`extraction filters ` should " +"raise :exc:`FilterError` for *fatal* errors and :exc:`ExtractError` for *non-" +"fatal* ones." msgstr "" #: library/tarfile.rst:581 @@ -845,8 +846,8 @@ msgstr "" #: library/tarfile.rst:588 msgid "" "The :ref:`extraction filter ` used as a default " -"for the *filter* argument of :meth:`~TarFile.extract` and :meth:`~TarFile." -"extractall`." +"for the *filter* argument of :meth:`~TarFile.extract` " +"and :meth:`~TarFile.extractall`." msgstr "" #: library/tarfile.rst:592 @@ -884,12 +885,12 @@ 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`. Recursion adds entries in sorted order. If *filter* is given, 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." +"recursively by default. This can be avoided by setting *recursive* " +"to :const:`False`. Recursion adds entries in sorted order. If *filter* is " +"given, 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 "" #: library/tarfile.rst:629 @@ -919,10 +920,10 @@ msgstr "" 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." +"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 "" #: library/tarfile.rst:666 @@ -949,18 +950,18 @@ msgstr "" #: library/tarfile.rst:687 msgid "" -":class:`TarInfo` objects are returned by :class:`TarFile`'s methods :meth:" -"`~TarFile.getmember`, :meth:`~TarFile.getmembers` and :meth:`~TarFile." -"gettarinfo`." +":class:`TarInfo` objects are returned by :class:`TarFile`'s " +"methods :meth:`~TarFile.getmember`, :meth:`~TarFile.getmembers` " +"and :meth:`~TarFile.gettarinfo`." msgstr "" #: library/tarfile.rst:691 msgid "" -"Modifying the objects returned by :meth:`~TarFile.getmember` or :meth:" -"`~TarFile.getmembers` will affect all subsequent operations on the archive. " -"For cases where this is unwanted, you can use :mod:`copy.copy() ` or " -"call the :meth:`~TarInfo.replace` method to create a modified copy in one " -"step." +"Modifying the objects returned by :meth:`~TarFile.getmember` " +"or :meth:`~TarFile.getmembers` will affect all subsequent operations on the " +"archive. For cases where this is unwanted, you can use :mod:`copy.copy() " +"` or call the :meth:`~TarInfo.replace` method to create a modified " +"copy in one step." msgstr "" #: library/tarfile.rst:697 @@ -1022,14 +1023,15 @@ msgstr "" #: library/tarfile.rst:751 msgid "" -"Time of last modification in seconds since the :ref:`epoch `, as in :" -"attr:`os.stat_result.st_mtime`." +"Time of last modification in seconds since the :ref:`epoch `, as " +"in :attr:`os.stat_result.st_mtime`." msgstr "" #: library/tarfile.rst:767 library/tarfile.rst:810 library/tarfile.rst:832 msgid "" -"Can be set to ``None`` for :meth:`~TarFile.extract` and :meth:`~TarFile." -"extractall`, causing extraction to skip applying this attribute." +"Can be set to ``None`` for :meth:`~TarFile.extract` " +"and :meth:`~TarFile.extractall`, causing extraction to skip applying this " +"attribute." msgstr "" #: library/tarfile.rst:763 @@ -1038,11 +1040,10 @@ msgstr "" #: library/tarfile.rst:773 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." +"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 "" #: library/tarfile.rst:783 @@ -1116,8 +1117,8 @@ msgstr "" #: library/tarfile.rst:888 msgid "" -"By default, a deep copy is made. If *deep* is false, the copy is shallow, i." -"e. ``pax_headers`` and any custom attributes are shared with the original " +"By default, a deep copy is made. If *deep* is false, the copy is shallow, " +"i.e. ``pax_headers`` and any custom attributes are shared with the original " "``TarInfo`` object." msgstr "" @@ -1193,8 +1194,8 @@ msgstr "" #: library/tarfile.rst:964 msgid "" -"The *filter* argument to :meth:`TarFile.extract` or :meth:`~TarFile." -"extractall` can be:" +"The *filter* argument to :meth:`TarFile.extract` " +"or :meth:`~TarFile.extractall` can be:" msgstr "" #: library/tarfile.rst:967 @@ -1214,8 +1215,8 @@ msgstr "" #: library/tarfile.rst:976 msgid "" "the string ``'data'``: Ignore or block most features specific to UNIX-like " -"filesystems. Intended for extracting cross-platform data archives. See :func:" -"`data_filter` for details." +"filesystems. Intended for extracting cross-platform data archives. " +"See :func:`data_filter` for details." msgstr "" #: library/tarfile.rst:980 @@ -1237,9 +1238,9 @@ msgstr "" #: library/tarfile.rst:989 msgid "" -"A callable which will be called for each extracted member with a :ref:" -"`TarInfo ` describing the member and the destination path " -"to where the archive is extracted (i.e. the same path is used for all " +"A callable which will be called for each extracted member with " +"a :ref:`TarInfo ` describing the member and the destination " +"path to where the archive is extracted (i.e. the same path is used for all " "members)::" msgstr "" @@ -1265,10 +1266,10 @@ msgstr "" #: library/tarfile.rst:1003 msgid "" -"raise an exception to abort the operation or skip the member, depending on :" -"attr:`~TarFile.errorlevel`. Note that when extraction is aborted, :meth:" -"`~TarFile.extractall` may leave the archive partially extracted. It does not " -"attempt to clean up." +"raise an exception to abort the operation or skip the member, depending " +"on :attr:`~TarFile.errorlevel`. Note that when extraction is " +"aborted, :meth:`~TarFile.extractall` may leave the archive partially " +"extracted. It does not attempt to clean up." msgstr "" #: library/tarfile.rst:1009 @@ -1313,8 +1314,8 @@ msgstr "" #: library/tarfile.rst:1032 msgid "" -"Clear high mode bits (setuid, setgid, sticky) and group/other write bits (:" -"const:`~stat.S_IWGRP` | :const:`~stat.S_IWOTH`)." +"Clear high mode bits (setuid, setgid, sticky) and group/other write bits " +"(:const:`~stat.S_IWGRP` | :const:`~stat.S_IWOTH`)." msgstr "" #: library/tarfile.rst:1068 @@ -1334,8 +1335,8 @@ msgstr "" #: library/tarfile.rst:1045 msgid "" -"This raises :class:`~tarfile.AbsoluteLinkError` or :class:`~tarfile." -"LinkOutsideDestinationError`." +"This raises :class:`~tarfile.AbsoluteLinkError` " +"or :class:`~tarfile.LinkOutsideDestinationError`." msgstr "" #: library/tarfile.rst:1048 @@ -1356,14 +1357,15 @@ msgstr "" #: library/tarfile.rst:1057 msgid "" -"Set the owner read and write permissions (:const:`~stat.S_IRUSR` | :const:" -"`~stat.S_IWUSR`)." +"Set the owner read and write permissions (:const:`~stat.S_IRUSR` " +"| :const:`~stat.S_IWUSR`)." msgstr "" #: library/tarfile.rst:1059 msgid "" -"Remove the group & other executable permission (:const:`~stat.S_IXGRP` | :" -"const:`~stat.S_IXOTH`) if the owner doesn’t have it (:const:`~stat.S_IXUSR`)." +"Remove the group & other executable permission (:const:`~stat.S_IXGRP` " +"| :const:`~stat.S_IXOTH`) if the owner doesn’t have it " +"(:const:`~stat.S_IXUSR`)." msgstr "" #: library/tarfile.rst:1063 @@ -1409,9 +1411,9 @@ msgstr "" #: library/tarfile.rst:1093 msgid "" -"Extract to a :func:`new temporary directory ` to prevent e." -"g. exploiting pre-existing links, and to make it easier to clean up after a " -"failed extraction." +"Extract to a :func:`new temporary directory ` to prevent " +"e.g. exploiting pre-existing links, and to make it easier to clean up after " +"a failed extraction." msgstr "" #: library/tarfile.rst:1096 @@ -1585,8 +1587,9 @@ msgstr "" #: library/tarfile.rst:1200 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:" +"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 "" #: library/tarfile.rst:1203 @@ -1603,8 +1606,8 @@ msgstr "" #: library/tarfile.rst:1213 msgid "" -"If you want to extract a tar archive into the current directory, use the :" -"option:`-e` option:" +"If you want to extract a tar archive into the current directory, use " +"the :option:`-e` option:" msgstr "" #: library/tarfile.rst:1216 diff --git a/library/telnetlib.po b/library/telnetlib.po index 1e77a021c..9ba4a10c7 100644 --- a/library/telnetlib.po +++ b/library/telnetlib.po @@ -86,9 +86,9 @@ msgstr "" #: library/telnetlib.rst:52 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::" +"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 "" #: library/telnetlib.rst:56 @@ -243,8 +243,8 @@ msgstr "" #: library/telnetlib.rst:189 msgid "" -"This method used to raise :exc:`socket.error`, which is now an alias of :exc:" -"`OSError`." +"This method used to raise :exc:`socket.error`, which is now an alias " +"of :exc:`OSError`." msgstr "" #: library/telnetlib.rst:196 @@ -261,9 +261,9 @@ msgstr "" #: library/telnetlib.rst:208 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 " +"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 "" diff --git a/library/tempfile.po b/library/tempfile.po index edc4b8f9e..1e6a5a555 100644 --- a/library/tempfile.po +++ b/library/tempfile.po @@ -27,11 +27,12 @@ msgstr "" #: 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 :term:`context " -"managers `. :func:`mkstemp` and :func:`mkdtemp` are lower-" -"level functions which require manual cleanup." +"supported " +"platforms. :class:`TemporaryFile`, :class:`NamedTemporaryFile`, :class:`TemporaryDirectory`, " +"and :class:`SpooledTemporaryFile` are high-level interfaces which provide " +"automatic cleanup and can be used as :term:`context managers `. :func:`mkstemp` and :func:`mkdtemp` are lower-level functions " +"which require manual cleanup." msgstr "" #: library/tempfile.rst:24 @@ -63,9 +64,9 @@ msgstr "" #: library/tempfile.rst:44 msgid "" -"The resulting object can be used as a :term:`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." +"The resulting object can be used as a :term:`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 "" #: library/tempfile.rst:49 @@ -195,10 +196,10 @@ msgstr "" #: library/tempfile.rst:121 msgid "" "*delete* is true but *delete_on_close* is false. Note, that in this case the " -"additional opens that do not share delete access (e.g. created via builtin :" -"func:`open`) must be closed before exiting the context manager, else the :" -"func:`os.unlink` call on context manager exit will fail with a :exc:" -"`PermissionError`." +"additional opens that do not share delete access (e.g. created via " +"builtin :func:`open`) must be closed before exiting the context manager, " +"else the :func:`os.unlink` call on context manager exit will fail with " +"a :exc:`PermissionError`." msgstr "" #: library/tempfile.rst:127 @@ -226,8 +227,8 @@ msgid "" "This class 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:`~io.IOBase.fileno` method is called, at which point the " -"contents are written to disk and operation proceeds as with :func:" -"`TemporaryFile`." +"contents are written to disk and operation proceeds as " +"with :func:`TemporaryFile`." msgstr "" #: library/tempfile.rst:156 @@ -258,8 +259,8 @@ msgstr "" #: library/tempfile.rst:180 msgid "" -"This class securely creates a temporary directory using the same rules as :" -"func:`mkdtemp`. The resulting object can be used as a :term:`context " +"This class securely creates a temporary directory using the same rules " +"as :func:`mkdtemp`. The resulting object can be used as a :term:`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." @@ -336,8 +337,8 @@ msgstr "" #: library/tempfile.rst:239 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." +"otherwise, a default prefix is used. The default is the return value " +"of :func:`gettempprefix` or :func:`gettempprefixb`, as appropriate." msgstr "" #: library/tempfile.rst:243 @@ -399,8 +400,8 @@ msgstr "" #: library/tempfile.rst:285 msgid "" -"The *prefix*, *suffix*, and *dir* arguments are the same as for :func:" -"`mkstemp`." +"The *prefix*, *suffix*, and *dir* arguments are the same as " +"for :func:`mkstemp`." msgstr "" #: library/tempfile.rst:288 @@ -449,8 +450,8 @@ msgstr "" #: library/tempfile.rst:325 msgid "" -"On all other platforms, the directories :file:`/tmp`, :file:`/var/tmp`, and :" -"file:`/usr/tmp`, in that order." +"On all other platforms, the directories :file:`/tmp`, :file:`/var/tmp`, " +"and :file:`/usr/tmp`, in that order." msgstr "" #: library/tempfile.rst:328 @@ -510,11 +511,11 @@ msgstr "" #: library/tempfile.rst:375 msgid "" "Beware that if you set ``tempdir`` to a bytes value, there is a nasty side " -"effect: The global default return type of :func:`mkstemp` and :func:" -"`mkdtemp` changes to bytes when no explicit ``prefix``, ``suffix``, or " -"``dir`` arguments of type str are supplied. Please do not write code " -"expecting or depending on this. This awkward behavior is maintained for " -"compatibility with the historical implementation." +"effect: The global default return type of :func:`mkstemp` " +"and :func:`mkdtemp` changes to bytes when no explicit ``prefix``, " +"``suffix``, or ``dir`` arguments of type str are supplied. Please do not " +"write code expecting or depending on this. This awkward behavior is " +"maintained for compatibility with the historical implementation." msgstr "" #: library/tempfile.rst:386 diff --git a/library/termios.po b/library/termios.po index 9a76d4e01..abdf624cc 100644 --- a/library/termios.po +++ b/library/termios.po @@ -35,8 +35,9 @@ msgstr "" #: library/termios.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 a :term:`file object`, such as ``sys.stdin`` itself." +"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 "" #: library/termios.rst:25 @@ -111,17 +112,17 @@ msgstr "" #: library/termios.rst:91 msgid "" "Return a tuple ``(ws_row, ws_col)`` containing the tty window size for file " -"descriptor *fd*. Requires :const:`termios.TIOCGWINSZ` or :const:`termios." -"TIOCGSIZE`." +"descriptor *fd*. Requires :const:`termios.TIOCGWINSZ` " +"or :const:`termios.TIOCGSIZE`." msgstr "" #: library/termios.rst:100 msgid "" "Set the tty window size for file descriptor *fd* from *winsize*, which is a " -"two-item tuple ``(ws_row, ws_col)`` like the one returned by :func:" -"`tcgetwinsize`. Requires at least one of the pairs (:const:`termios." -"TIOCGWINSZ`, :const:`termios.TIOCSWINSZ`); (:const:`termios.TIOCGSIZE`, :" -"const:`termios.TIOCSSIZE`) to be defined." +"two-item tuple ``(ws_row, ws_col)`` like the one returned " +"by :func:`tcgetwinsize`. Requires at least one of the pairs " +"(:const:`termios.TIOCGWINSZ`, :const:`termios.TIOCSWINSZ`); " +"(:const:`termios.TIOCGSIZE`, :const:`termios.TIOCSSIZE`) to be defined." msgstr "" #: library/termios.rst:111 @@ -139,9 +140,9 @@ msgstr "" #: library/termios.rst:120 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::" +"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 "" #: library/termios.rst:125 diff --git a/library/test.po b/library/test.po index ed2c26ef5..e6b21f9f2 100644 --- a/library/test.po +++ b/library/test.po @@ -32,9 +32,9 @@ msgstr "" #: 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." +"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 "" #: library/test.rst:23 @@ -120,9 +120,9 @@ msgstr "" #: 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." +"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 "" #: library/test.rst:92 @@ -213,11 +213,11 @@ msgstr "" #: 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:`!" +"When using this pattern, remember that all classes that inherit " +"from :class:`unittest.TestCase` are run as tests. The :class:`!" "TestFuncAcceptsSequencesMixin` 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`." +"data and so can't be run by itself, thus it does not inherit " +"from :class:`unittest.TestCase`." msgstr "" #: library/test.rst:153 @@ -238,14 +238,14 @@ msgid "" "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." +"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 "" #: library/test.rst:178 @@ -265,9 +265,9 @@ msgstr "" 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." +"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 "" #: library/test.rst:197 @@ -293,8 +293,8 @@ msgstr "" #: library/test.rst:217 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 " +"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 "" @@ -312,8 +312,8 @@ msgstr "" #: library/test.rst:233 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`." +"detailed information is desired about a running test. *verbose* is set " +"by :mod:`test.regrtest`." msgstr "" #: library/test.rst:240 @@ -343,9 +343,9 @@ msgstr "" #: library/test.rst:262 msgid "" -"The timeout should be long enough for :meth:`~socket.socket.connect`, :meth:" -"`~socket.socket.recv` and :meth:`~socket.socket.send` methods of :class:" -"`socket.socket`." +"The timeout should be long enough " +"for :meth:`~socket.socket.connect`, :meth:`~socket.socket.recv` " +"and :meth:`~socket.socket.send` methods of :class:`socket.socket`." msgstr "" #: library/test.rst:266 @@ -369,8 +369,8 @@ msgstr "" #: library/test.rst:278 msgid "" "Usually, a timeout using :data:`INTERNET_TIMEOUT` should not mark a test as " -"failed, but skip the test instead: see :func:`~test.support.socket_helper." -"transient_internet`." +"failed, but skip the test instead: " +"see :func:`~test.support.socket_helper.transient_internet`." msgstr "" #: library/test.rst:282 @@ -419,8 +419,8 @@ msgstr "" #: library/test.rst:310 msgid "" -"See also :data:`LOOPBACK_TIMEOUT`, :data:`INTERNET_TIMEOUT` and :data:" -"`SHORT_TIMEOUT`." +"See also :data:`LOOPBACK_TIMEOUT`, :data:`INTERNET_TIMEOUT` " +"and :data:`SHORT_TIMEOUT`." msgstr "" #: library/test.rst:316 @@ -475,9 +475,9 @@ msgstr "" #: library/test.rst:374 msgid "" -"Set to ``True`` if Python is built without docstrings (the :c:macro:" -"`WITH_DOC_STRINGS` macro is not defined). See the :option:`configure --" -"without-doc-strings <--without-doc-strings>` option." +"Set to ``True`` if Python is built without docstrings " +"(the :c:macro:`WITH_DOC_STRINGS` macro is not defined). See " +"the :option:`configure --without-doc-strings <--without-doc-strings>` option." msgstr "" #: library/test.rst:378 @@ -486,9 +486,9 @@ msgstr "" #: library/test.rst:383 msgid "" -"Set to ``True`` if function docstrings are available. See the :option:" -"`python -OO <-O>` option, which strips docstrings of functions implemented " -"in Python." +"Set to ``True`` if function docstrings are available. See " +"the :option:`python -OO <-O>` option, which strips docstrings of functions " +"implemented in Python." msgstr "" #: library/test.rst:386 @@ -672,8 +672,8 @@ msgstr "" #: library/test.rst:543 msgid "" -"Return the original stdout set by :func:`record_original_stdout` or ``sys." -"stdout`` if it's not set." +"Return the original stdout set by :func:`record_original_stdout` or " +"``sys.stdout`` if it's not set." msgstr "" #: library/test.rst:549 @@ -690,8 +690,8 @@ msgstr "" #: library/test.rst:563 msgid "" -"A context managers that temporarily replaces the named stream with :class:" -"`io.StringIO` object." +"A context managers that temporarily replaces the named stream " +"with :class:`io.StringIO` object." msgstr "" #: library/test.rst:566 @@ -785,9 +785,9 @@ msgstr "" #: library/test.rst:641 msgid "" -"Call the ``flush()`` method on :data:`sys.stdout` and then on :data:`sys." -"stderr`. It can be used to make sure that the logs order is consistent " -"before writing into stderr." +"Call the ``flush()`` method on :data:`sys.stdout` and then " +"on :data:`sys.stderr`. It can be used to make sure that the logs order is " +"consistent before writing into stderr." msgstr "" #: library/test.rst:650 @@ -838,9 +838,9 @@ msgstr "" #: library/test.rst:692 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." +"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 "" #: library/test.rst:699 @@ -990,8 +990,8 @@ msgstr "" #: library/test.rst:849 msgid "" -"Context manager catching unraisable exception using :func:`sys." -"unraisablehook`." +"Context manager catching unraisable exception " +"using :func:`sys.unraisablehook`." msgstr "" #: library/test.rst:852 @@ -1061,8 +1061,8 @@ msgstr "" #: library/test.rst:912 msgid "" -"Run *code* in subinterpreter. Raise :exc:`unittest.SkipTest` if :mod:" -"`tracemalloc` is enabled." +"Run *code* in subinterpreter. Raise :exc:`unittest.SkipTest` " +"if :mod:`tracemalloc` is enabled." msgstr "" #: library/test.rst:918 @@ -1098,9 +1098,9 @@ msgstr "" #: library/test.rst:942 msgid "" "The *extra* argument can be a set of names that wouldn't otherwise be " -"automatically detected as \"public\", like objects without a proper :attr:" -"`~definition.__module__` attribute. If provided, it will be added to the " -"automatically detected ones." +"automatically detected as \"public\", like objects without a " +"proper :attr:`~definition.__module__` attribute. If provided, it will be " +"added to the automatically detected ones." msgstr "" #: library/test.rst:946 @@ -1146,10 +1146,10 @@ msgstr "" #: library/test.rst:988 msgid "" -"This function returns a context manager that will change the global :func:" -"`sys.set_int_max_str_digits` setting for the duration of the context to " -"allow execution of test code that needs a different limit on the number of " -"digits when converting between an integer and string." +"This function returns a context manager that will change the " +"global :func:`sys.set_int_max_str_digits` setting for the duration of the " +"context to allow execution of test code that needs a different limit on the " +"number of digits when converting between an integer and string." msgstr "" #: library/test.rst:996 @@ -1170,8 +1170,9 @@ msgstr "" #: library/test.rst:1007 msgid "" -"On UNIX, :func:`resource.setrlimit` is used to set :const:`resource." -"RLIMIT_CORE`'s soft limit to 0 to prevent coredump file creation." +"On UNIX, :func:`resource.setrlimit` is used to " +"set :const:`resource.RLIMIT_CORE`'s soft limit to 0 to prevent coredump file " +"creation." msgstr "" #: library/test.rst:1011 @@ -1222,11 +1223,11 @@ msgstr "" 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." +"``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 "" #: library/test.rst:1070 @@ -1236,10 +1237,10 @@ msgid "" "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." +"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 "" #: library/test.rst:1084 @@ -1247,12 +1248,13 @@ 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." +"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 "" #: library/test.rst:1095 @@ -1265,8 +1267,8 @@ msgstr "" #: library/test.rst:1103 msgid "" -"Bind a Unix socket, raising :exc:`unittest.SkipTest` if :exc:" -"`PermissionError` is raised." +"Bind a Unix socket, raising :exc:`unittest.SkipTest` " +"if :exc:`PermissionError` is raised." msgstr "" #: library/test.rst:1109 @@ -1369,8 +1371,8 @@ msgstr "" #: library/test.rst:1191 msgid "" -"*kw* is extra keyword args to pass to :func:`subprocess.Popen`. Returns a :" -"class:`subprocess.Popen` object." +"*kw* is extra keyword args to pass to :func:`subprocess.Popen`. Returns " +"a :class:`subprocess.Popen` object." msgstr "" #: library/test.rst:1197 @@ -1487,8 +1489,8 @@ msgstr "" #: library/test.rst:1312 msgid "" -"Context manager catching :class:`threading.Thread` exception using :func:" -"`threading.excepthook`." +"Context manager catching :class:`threading.Thread` exception " +"using :func:`threading.excepthook`." msgstr "" #: library/test.rst:1315 @@ -1597,9 +1599,10 @@ msgstr "" #: library/test.rst:1411 msgid "" -"Simple :term:`path-like object`. It implements the :meth:`~os.PathLike." -"__fspath__` method which just returns the *path* argument. If *path* is an " -"exception, it will be raised in :meth:`!__fspath__`." +"Simple :term:`path-like object`. It implements " +"the :meth:`~os.PathLike.__fspath__` method which just returns the *path* " +"argument. If *path* is an exception, it will be raised in :meth:`!" +"__fspath__`." msgstr "" #: library/test.rst:1419 @@ -1661,10 +1664,10 @@ msgstr "" #: library/test.rst:1481 msgid "" -"Call :func:`shutil.rmtree` on *path* or call :func:`os.lstat` and :func:`os." -"rmdir` to remove a path and its contents. As with :func:`rmdir`, on Windows " -"platforms this is wrapped with a wait loop that checks for the existence of " -"the files." +"Call :func:`shutil.rmtree` on *path* or call :func:`os.lstat` " +"and :func:`os.rmdir` to remove a path and its contents. As " +"with :func:`rmdir`, on Windows platforms this is wrapped with a wait loop " +"that checks for the existence of the files." msgstr "" #: library/test.rst:1489 @@ -1685,8 +1688,8 @@ msgstr "" 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`." +"If *name* is ``None``, the temporary directory is created " +"using :func:`tempfile.mkdtemp`." msgstr "" #: library/test.rst:1507 @@ -1704,10 +1707,10 @@ msgstr "" #: library/test.rst:1517 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." +"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 "" #: library/test.rst:1525 @@ -1827,8 +1830,8 @@ msgstr "" #: library/test.rst:1628 msgid "" "A context manager to force import to return a new module reference. This is " -"useful for testing module-level behaviors, such as the emission of a :exc:" -"`DeprecationWarning` on import. Example usage::" +"useful for testing module-level behaviors, such as the emission of " +"a :exc:`DeprecationWarning` on import. Example usage::" msgstr "" #: library/test.rst:1632 @@ -1867,10 +1870,11 @@ msgstr "" #: library/test.rst:1662 msgid "" -"Suppress warnings that are instances of *category*, which must be :exc:" -"`Warning` or a subclass. Roughly equivalent to :func:`warnings." -"catch_warnings` with :meth:`warnings.simplefilter('ignore', " -"category=category) `. For example::" +"Suppress warnings that are instances of *category*, which must " +"be :exc:`Warning` or a subclass. Roughly equivalent " +"to :func:`warnings.catch_warnings` " +"with :meth:`warnings.simplefilter('ignore', category=category) " +"`. For example::" msgstr "" #: library/test.rst:1668 @@ -1893,18 +1897,18 @@ msgid "" "Test also that the :exc:`SyntaxWarning` is emitted only once, and that it " "will be converted to a :exc:`SyntaxError` when turned into error. *testcase* " "is the :mod:`unittest` instance for the test. *errtext* is the regular " -"expression which should match the string representation of the emitted :exc:" -"`SyntaxWarning` and raised :exc:`SyntaxError`. If *lineno* is not ``None``, " -"compares to the line of the warning and exception. If *offset* is not " -"``None``, compares to the offset of the exception." +"expression which should match the string representation of the " +"emitted :exc:`SyntaxWarning` and raised :exc:`SyntaxError`. If *lineno* is " +"not ``None``, compares to the line of the warning and exception. If *offset* " +"is not ``None``, compares to the offset of the exception." msgstr "" #: library/test.rst:1698 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 " +"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 "" @@ -1999,6 +2003,6 @@ msgstr "" #: library/test.rst:1764 msgid "" -"Class used to record warnings for unit tests. See documentation of :func:" -"`check_warnings` above for more details." +"Class used to record warnings for unit tests. See documentation " +"of :func:`check_warnings` above for more details." msgstr "" diff --git a/library/textwrap.po b/library/textwrap.po index d08c1800f..e3de7015c 100644 --- a/library/textwrap.po +++ b/library/textwrap.po @@ -26,11 +26,11 @@ msgstr "" #: 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 " +"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." +"should be good enough; otherwise, you should use an instance " +"of :class:`TextWrapper` for efficiency." msgstr "" #: library/textwrap.rst:27 @@ -42,14 +42,14 @@ msgstr "" #: library/textwrap.rst:31 msgid "" -"Optional keyword arguments correspond to the instance attributes of :class:" -"`TextWrapper`, documented below." +"Optional keyword arguments correspond to the instance attributes " +"of :class:`TextWrapper`, documented below." msgstr "" #: library/textwrap.rst:34 msgid "" -"See the :meth:`TextWrapper.wrap` method for additional details on how :func:" -"`wrap` behaves." +"See the :meth:`TextWrapper.wrap` method for additional details on " +"how :func:`wrap` behaves." msgstr "" #: library/textwrap.rst:45 @@ -64,8 +64,8 @@ msgstr "" #: library/textwrap.rst:50 msgid "" -"In particular, :func:`fill` accepts exactly the same keyword arguments as :" -"func:`wrap`." +"In particular, :func:`fill` accepts exactly the same keyword arguments " +"as :func:`wrap`." msgstr "" #: library/textwrap.rst:58 @@ -92,11 +92,12 @@ msgstr "" #: library/textwrap.rst:72 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." +"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 "" #: library/textwrap.rst:82 @@ -177,18 +178,18 @@ msgstr "" #: library/textwrap.rst:134 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." +":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 "" #: library/textwrap.rst:140 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." +"hyphenated words; only then will long words be broken if necessary, " +"unless :attr:`TextWrapper.break_long_words` is set to false." msgstr "" #: library/textwrap.rst:146 @@ -228,9 +229,9 @@ msgstr "" #: library/textwrap.rst:167 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." +"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 "" #: library/textwrap.rst:175 @@ -248,8 +249,8 @@ msgstr "" #: library/textwrap.rst:190 msgid "" -"(default: ``True``) If true, after tab expansion but before wrapping, the :" -"meth:`wrap` method will replace each whitespace character with a single " +"(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 "" @@ -367,11 +368,11 @@ msgstr "" #: library/textwrap.rst:300 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." +"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 "" #: library/textwrap.rst:309 diff --git a/library/threading.po b/library/threading.po index 2788bc50c..fd713ab3c 100644 --- a/library/threading.po +++ b/library/threading.po @@ -67,9 +67,10 @@ msgid "" "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." +"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 "" #: library/threading.rst:226 includes/wasm-notavail.rst:3 @@ -196,10 +197,10 @@ msgstr "" #: library/threading.rst:137 msgid "" "Return a list of all :class:`Thread` objects currently active. The list " -"includes daemonic threads and dummy thread objects created by :func:" -"`current_thread`. It excludes terminated threads and threads that have not " -"yet been started. However, the main thread is always part of the result, " -"even when terminated." +"includes daemonic threads and dummy thread objects created " +"by :func:`current_thread`. It excludes terminated threads and threads that " +"have not yet been started. However, the main thread is always part of the " +"result, even when terminated." msgstr "" #: library/threading.rst:146 @@ -260,9 +261,9 @@ msgid "" "*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 " +"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 " @@ -285,8 +286,8 @@ msgstr "" 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`." +"Specifying a timeout greater than this value will raise " +"an :exc:`OverflowError`." msgstr "" #: library/threading.rst:243 @@ -366,8 +367,8 @@ msgstr "" 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." +"normally, or by raising an unhandled exception. " +"The :meth:`~Thread.is_alive` method tests whether the thread is alive." msgstr "" #: library/threading.rst:299 @@ -385,9 +386,9 @@ msgstr "" #: library/threading.rst:306 msgid "" -"If the :meth:`~Thread.run` method raises an exception, :func:`threading." -"excepthook` is called to handle it. By default, :func:`threading.excepthook` " -"ignores silently :exc:`SystemExit`." +"If the :meth:`~Thread.run` method raises an " +"exception, :func:`threading.excepthook` is called to handle it. By " +"default, :func:`threading.excepthook` ignores silently :exc:`SystemExit`." msgstr "" #: library/threading.rst:310 @@ -515,8 +516,8 @@ msgstr "" #: library/threading.rst:389 msgid "" -"Using list or tuple as the *args* argument which passed to the :class:" -"`Thread` could achieve the same effect." +"Using list or tuple as the *args* argument which passed to " +"the :class:`Thread` could achieve the same effect." msgstr "" #: library/threading.rst:392 @@ -548,8 +549,8 @@ msgid "" "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." +"whether a timeout happened -- if the thread is still alive, " +"the :meth:`~Thread.join` call timed out." msgstr "" #: library/threading.rst:418 @@ -625,8 +626,8 @@ msgid "" "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``." +"and therefore all threads created in the main thread default " +"to :attr:`~Thread.daemon` = ``False``." msgstr "" #: library/threading.rst:486 @@ -648,22 +649,22 @@ msgstr "" 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." +"synchronization primitive available, implemented directly by " +"the :mod:`_thread` extension module." msgstr "" #: library/threading.rst:507 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." +"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 "" #: library/threading.rst:518 @@ -673,9 +674,9 @@ msgstr "" #: library/threading.rst:520 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." +"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 "" #: library/threading.rst:525 @@ -778,16 +779,16 @@ msgstr "" #: library/threading.rst:597 msgid "" -"Threads call a lock's :meth:`~RLock.acquire` method to lock it, and its :" -"meth:`~Lock.release` method to unlock it." +"Threads call a lock's :meth:`~RLock.acquire` method to lock it, and " +"its :meth:`~Lock.release` method to unlock it." msgstr "" #: library/threading.rst:602 msgid "" "Reentrant locks support the :ref:`context management protocol `, " -"so it is recommended to use :keyword:`with` instead of manually calling :" -"meth:`~RLock.acquire` and :meth:`~RLock.release` to handle acquiring and " -"releasing the lock for a block of code." +"so it is recommended to use :keyword:`with` instead of manually " +"calling :meth:`~RLock.acquire` and :meth:`~RLock.release` to handle " +"acquiring and releasing the lock for a block of code." msgstr "" #: library/threading.rst:607 @@ -894,9 +895,9 @@ msgstr "" #: library/threading.rst:682 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 not " -"acquired." +"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 " +"not acquired." msgstr "" #: library/threading.rst:692 @@ -915,25 +916,26 @@ msgstr "" 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." +"duration of the enclosed block. The :meth:`~Condition.acquire` " +"and :meth:`~Condition.release` methods also call the corresponding methods " +"of the associated lock." msgstr "" #: library/threading.rst:705 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." +"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 "" #: library/threading.rst:711 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." +"the condition variable, if any are waiting. " +"The :meth:`~Condition.notify_all` method wakes up all threads waiting for " +"the condition variable." msgstr "" #: library/threading.rst:715 @@ -950,11 +952,11 @@ 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::" +"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 "" #: library/threading.rst:730 @@ -976,8 +978,8 @@ 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 " +"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 "" @@ -991,11 +993,11 @@ msgstr "" #: library/threading.rst:753 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." +"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 "" #: library/threading.rst:761 @@ -1052,12 +1054,12 @@ msgstr "" #: library/threading.rst:796 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." +"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 "" #: library/threading.rst:804 @@ -1107,8 +1109,8 @@ msgstr "" #: library/threading.rst:835 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." +"calling thread has not acquired the lock when this method is called, " +"a :exc:`RuntimeError` is raised." msgstr "" #: library/threading.rst:839 @@ -1134,10 +1136,10 @@ msgstr "" #: library/threading.rst:853 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." +"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 "" #: library/threading.rst:858 @@ -1152,17 +1154,17 @@ msgstr "" 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`)." +"Dijkstra (he used the names ``P()`` and ``V()`` instead " +"of :meth:`~Semaphore.acquire` and :meth:`~Semaphore.release`)." msgstr "" #: library/threading.rst:871 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`." +"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 "" #: library/threading.rst:877 @@ -1202,10 +1204,10 @@ msgstr "" #: library/threading.rst:903 msgid "" -"If the internal counter is zero on entry, block until awoken by a call to :" -"meth:`~Semaphore.release`. Once awoken (and the counter is greater than 0), " -"decrement the counter by 1 and return ``True``. Exactly one thread will be " -"awoken by each call to :meth:`~Semaphore.release`. The order in which " +"If the internal counter is zero on entry, block until awoken by a call " +"to :meth:`~Semaphore.release`. Once awoken (and the counter is greater than " +"0), decrement the counter by 1 and return ``True``. Exactly one thread will " +"be awoken by each call to :meth:`~Semaphore.release`. The order in which " "threads are awoken should not be relied on." msgstr "" @@ -1237,10 +1239,10 @@ msgstr "" #: library/threading.rst:932 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." +"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 "" #: library/threading.rst:945 @@ -1297,17 +1299,18 @@ msgstr "" #: library/threading.rst:978 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." +"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 "" #: library/threading.rst:985 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." +"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 "" #: library/threading.rst:995 @@ -1355,9 +1358,9 @@ msgstr "" #: library/threading.rst:1032 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." +"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 "" #: library/threading.rst:1036 @@ -1527,8 +1530,8 @@ msgstr "" #: library/threading.rst:1165 msgid "" -"This exception, a subclass of :exc:`RuntimeError`, is raised when the :class:" -"`Barrier` object is reset or broken." +"This exception, a subclass of :exc:`RuntimeError`, is raised when " +"the :class:`Barrier` object is reset or broken." msgstr "" #: library/threading.rst:1172 @@ -1566,9 +1569,9 @@ msgstr "" #: library/threading.rst:1191 msgid "" -"Currently, :class:`Lock`, :class:`RLock`, :class:`Condition`, :class:" -"`Semaphore`, and :class:`BoundedSemaphore` objects may be used as :keyword:" -"`with` statement context managers." +"Currently, :class:`Lock`, :class:`RLock`, :class:`Condition`, :class:`Semaphore`, " +"and :class:`BoundedSemaphore` objects may be used as :keyword:`with` " +"statement context managers." msgstr "" #: library/threading.rst:173 diff --git a/library/time.po b/library/time.po index 739e19225..74e457b00 100644 --- a/library/time.po +++ b/library/time.po @@ -127,31 +127,31 @@ msgstr "" 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 " +"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 "" "Öte yandan, :func:`.time` ve :func:`sleep` fonksiyonlarının hassasiyetleri " "diğer Unix karşılıklarından daha iyidir: zamanlar kayan noktalı sayılar " "olarak ifade edilirler, :func:`.time` mevcut en doğru zamanı döndürür " -"(mevcut olduğu yerde Unix :c:func:`gettimeofday` kullanarak), ve :func:" -"`sleep` sıfıra eşit olmayan kesirli zamanı kabul eder (Unix :c:func:" -"`select`, mümkün olduğunda bunu uygulamak için kullanılır)." +"(mevcut olduğu yerde Unix :c:func:`gettimeofday` kullanarak), " +"ve :func:`sleep` sıfıra eşit olmayan kesirli zamanı kabul eder " +"(Unix :c:func:`select`, mümkün olduğunda bunu uygulamak için kullanılır)." #: library/time.rst:78 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." +"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 "" ":func:`gmtime`, :func:`localtime`, ve :func:`strptime`, tarafından " "döndürülen ve :func:`asctime`, :func:`mktime` ve :func:`strftime`, " -"tarafından kabul edilen zaman değeri 9 tam sayılık bir dizidir. :func:" -"`gmtime`, :func:`localtime`, ve :func:`strptime` tarafından döndürülen " -"değerler ayrıca ayrı alanlar için ayrı öznitelik isimleri sunar." +"tarafından kabul edilen zaman değeri 9 tam sayılık bir " +"dizidir. :func:`gmtime`, :func:`localtime`, ve :func:`strptime` tarafından " +"döndürülen değerler ayrıca ayrı alanlar için ayrı öznitelik isimleri sunar." #: library/time.rst:84 msgid "See :class:`struct_time` for a description of these objects." @@ -161,9 +161,9 @@ msgstr "" #: library/time.rst:86 #, fuzzy msgid "" -"The :class:`struct_time` type was extended to provide the :attr:" -"`~struct_time.tm_gmtoff` and :attr:`~struct_time.tm_zone` attributes when " -"platform supports corresponding ``struct tm`` members." +"The :class:`struct_time` type was extended to provide " +"the :attr:`~struct_time.tm_gmtoff` and :attr:`~struct_time.tm_zone` " +"attributes when platform supports corresponding ``struct tm`` members." msgstr "" ":class:`struct_time` türü :attr:`tm_gmtoff` ve :attr:`tm_zone` " "özniteliklerini platform ``struct tm``'e ilişkin üyeleri desteklediğinde " @@ -172,8 +172,8 @@ msgstr "" #: library/time.rst:92 #, fuzzy msgid "" -"The :class:`struct_time` attributes :attr:`~struct_time.tm_gmtoff` and :attr:" -"`~struct_time.tm_zone` are now available on all platforms." +"The :class:`struct_time` attributes :attr:`~struct_time.tm_gmtoff` " +"and :attr:`~struct_time.tm_zone` are now available on all platforms." msgstr "" ":class:`struct_time` öznitelikleri :attr:`tm_gmtoff` ve :attr:`tm_zone` " "artık bütün platformlarda mevcut." @@ -230,10 +230,11 @@ msgstr "Fonksiyonlar" #: library/time.rst:123 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'``. The day field is two characters long and is space " -"padded if the day is a single digit, e.g.: ``'Wed Jun 9 04:26:40 1993'``." +"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'``. The day field is two characters long and is " +"space padded if the day is a single digit, e.g.: ``'Wed Jun 9 04:26:40 " +"1993'``." msgstr "" ":func:`gmtime` veya :func:`localtime` tarafından döndürülen bir zamanı " "temsil eden bir demet veya :class:`struct_time` öğesini şu forma sahip bir " @@ -315,11 +316,11 @@ msgstr "" #: library/time.rst:171 msgid "" -"Use :func:`clock_gettime_ns` to avoid the precision loss caused by the :" -"class:`float` type." +"Use :func:`clock_gettime_ns` to avoid the precision loss caused by " +"the :class:`float` type." msgstr "" -":class:`float` türü sebebiyle oluşan kesinlik kaybından kaçınmak için :func:" -"`clock_gettime_ns` kullanın." +":class:`float` türü sebebiyle oluşan kesinlik kaybından kaçınmak " +"için :func:`clock_gettime_ns` kullanın." #: library/time.rst:181 msgid "Similar to :func:`clock_gettime` but return time as nanoseconds." @@ -329,19 +330,19 @@ msgstr "" #: library/time.rst:190 msgid "" -"Set the time of the specified clock *clk_id*. Currently, :data:" -"`CLOCK_REALTIME` is the only accepted value for *clk_id*." +"Set the time of the specified clock *clk_id*. " +"Currently, :data:`CLOCK_REALTIME` is the only accepted value for *clk_id*." msgstr "" "Belirtilen *clk_id* saatinin zamanını ayarla. Şu anda, *clk_id* için kabul " "edilen tek değer :data:`CLOCK_REALTIME`'dır." #: library/time.rst:193 msgid "" -"Use :func:`clock_settime_ns` to avoid the precision loss caused by the :" -"class:`float` type." +"Use :func:`clock_settime_ns` to avoid the precision loss caused by " +"the :class:`float` type." msgstr "" -":class:`float` türü sebebiyle oluşan kesinlik kaybından kaçınmak için :func:" -"`clock_settime_ns` kullanın." +":class:`float` türü sebebiyle oluşan kesinlik kaybından kaçınmak " +"için :func:`clock_settime_ns` kullanın." #: library/time.rst:203 msgid "Similar to :func:`clock_settime` but set time with nanoseconds." @@ -362,10 +363,10 @@ msgstr "" #: library/time.rst:217 msgid "" -"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`." +"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 "" "*secs* veya :const:`None` sağlanmamışsa, :func:`.time` tarafından döndürülen " "mevcut zaman kullanılır. ``ctime(secs)`` ``asctime(localtime(secs))``'e " @@ -433,19 +434,19 @@ msgstr "*resolution*: Saatin saniyeler halindeki netliği (:class:`float`)" #: library/time.rst:250 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." +"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 "" "epoch_ 'dan bu yana saniye olarak ifade edilen bir zamanı, dst bayrağının " "her zaman sıfır olduğu UTC'de bir :class:`struct_time`'a dönüştürün. *secs* " "sağlanmazsa veya :const:`None`, :func:`.time` tarafından döndürülen geçerli " -"zaman kullanılır. Saniyenin kesirleri dikkate alınmaz. :class:" -"`struct_time` nesnesinin açıklaması için yukarıya bakın. Bu fonksiyonun " -"tersi için :func:`calendar.timegm` konusuna bakın." +"zaman kullanılır. Saniyenin kesirleri dikkate " +"alınmaz. :class:`struct_time` nesnesinin açıklaması için yukarıya bakın. Bu " +"fonksiyonun tersi için :func:`calendar.timegm` konusuna bakın." #: library/time.rst:260 msgid "" @@ -462,35 +463,36 @@ msgstr "" msgid "" ":func:`localtime` may raise :exc:`OverflowError`, if the timestamp is " "outside 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 " +"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 " "between 1970 and 2038." msgstr "" "Eğer zaman damgası C :c:func:`localtime` veya :c:func:`gmtime` fonksiyonları " -"tarafından sağlanan değer aralıkları içerisinde değilse :func:`localtime` :" -"exc:`OverflowError` yükseltebilir, ve :c:func:`localtime` üzerinde :exc:" -"`OSError` veya :c:func:`gmtime` hatasını. Bunun 1970 ile 2038 arasındaki " -"yıllarla sınırlı olması yaygın bir durumdur." +"tarafından sağlanan değer aralıkları içerisinde " +"değilse :func:`localtime` :exc:`OverflowError` yükseltebilir, " +"ve :c:func:`localtime` üzerinde :exc:`OSError` veya :c:func:`gmtime` " +"hatasını. Bunun 1970 ile 2038 arasındaki yıllarla sınırlı olması yaygın bir " +"durumdur." #: library/time.rst:273 #, fuzzy 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 " +"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 " +"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 "" "Bu, :func:`localtime`'ın ters fonksiyonudur. Argümanı :class:`struct_time` " "veya tam 9-demet (dst bayrağı gerekli olduğundan; bilinmiyorsa dst bayrağı " -"olarak ``-1`` kullanın), zamanı *local* zamanda ifade eder, UTC değil. :" -"func:`.time` ile uyumluluk için bir kayan noktalı sayı döndürür. Giriş " -"değeri geçerli bir zaman olarak gösterilemiyorsa, :exc:`OverflowError` veya :" -"exc:`ValueError` yükseltilir (geçersiz değerin Python veya temel C " +"olarak ``-1`` kullanın), zamanı *local* zamanda ifade eder, UTC " +"değil. :func:`.time` ile uyumluluk için bir kayan noktalı sayı döndürür. " +"Giriş değeri geçerli bir zaman olarak gösterilemiyorsa, :exc:`OverflowError` " +"veya :exc:`ValueError` yükseltilir (geçersiz değerin Python veya temel C " "kitaplıkları tarafından yakalanıp yakalanmadığına bağlıdır). Bir zaman " "oluşturabileceği en erken tarih, platforma bağlıdır." @@ -508,11 +510,11 @@ msgstr "" #: library/time.rst:290 msgid "" -"Use :func:`monotonic_ns` to avoid the precision loss caused by the :class:" -"`float` type." +"Use :func:`monotonic_ns` to avoid the precision loss caused by " +"the :class:`float` type." msgstr "" -":class:`float` türünün sebep olduğu kesinlik kaybından kaçınmak için :func:" -"`monotonic_ns` kullanın." +":class:`float` türünün sebep olduğu kesinlik kaybından kaçınmak " +"için :func:`monotonic_ns` kullanın." #: library/time.rst:295 msgid "The function is now always available and always system-wide." @@ -544,11 +546,11 @@ msgstr "" #: library/time.rst:319 msgid "" -"Use :func:`perf_counter_ns` to avoid the precision loss caused by the :class:" -"`float` type." +"Use :func:`perf_counter_ns` to avoid the precision loss caused by " +"the :class:`float` type." msgstr "" -":class:`float` türü sebebiyle oluşan kesinlik kaybından kaçınmak için :func:" -"`perf_counter_ns` kullanın." +":class:`float` türü sebebiyle oluşan kesinlik kaybından kaçınmak " +"için :func:`perf_counter_ns` kullanın." #: library/time.rst:324 msgid "On Windows, the function is now system-wide." @@ -575,11 +577,11 @@ msgstr "" #: library/time.rst:347 msgid "" -"Use :func:`process_time_ns` to avoid the precision loss caused by the :class:" -"`float` type." +"Use :func:`process_time_ns` to avoid the precision loss caused by " +"the :class:`float` type." msgstr "" -":class:`float` türü sebebiyle oluşan kesinlik kaybından kaçınmak için :func:" -"`process_time_ns` kullanın." +":class:`float` türü sebebiyle oluşan kesinlik kaybından kaçınmak " +"için :func:`process_time_ns` kullanın." #: library/time.rst:354 msgid "Similar to :func:`process_time` but return time as nanoseconds." @@ -673,18 +675,18 @@ msgstr "" #: library/time.rst:398 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." +"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 "" ":func:`gmtime` veya :func:`localtime` tarafından döndürülen bir zamanı " "temsil eden bir demet veya :class:`struct_time`'ı *format* bağımsız " -"değişkeni tarafından belirtilen bir dizeye dönüştürün. *t* sağlanmazsa, :" -"func:`localtime` tarafından döndürülen geçerli saat kullanılır. *format* " -"bir dize olmalıdır. :exc:`ValueError`, *t* içindeki herhangi bir alan izin " -"verilen aralığın dışındaysa yükseltilir." +"değişkeni tarafından belirtilen bir dizeye dönüştürün. *t* " +"sağlanmazsa, :func:`localtime` tarafından döndürülen geçerli saat " +"kullanılır. *format* bir dize olmalıdır. :exc:`ValueError`, *t* içindeki " +"herhangi bir alan izin verilen aralığın dışındaysa yükseltilir." #: library/time.rst:404 msgid "" @@ -986,10 +988,10 @@ msgstr "Notlar:" #: library/time.rst:514 msgid "" -"The ``%f`` format directive only applies to :func:`strptime`, not to :func:" -"`strftime`. However, see also :meth:`datetime.datetime.strptime` and :meth:" -"`datetime.datetime.strftime` where the ``%f`` format directive :ref:`applies " -"to microseconds `." +"The ``%f`` format directive only applies to :func:`strptime`, not " +"to :func:`strftime`. However, see also :meth:`datetime.datetime.strptime` " +"and :meth:`datetime.datetime.strftime` where the ``%f`` format " +"directive :ref:`applies to microseconds `." msgstr "" #: library/time.rst:520 @@ -1039,13 +1041,13 @@ msgstr "" 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." +"of format codes supported on your platform, consult " +"the :manpage:`strftime(3)` documentation." msgstr "" "Belirli platformlarda ek yönergeler desteklenebilir, ancak yalnızca burada " "listelenenlerin ANSI C tarafından standartlaştırılmış bir anlamı vardır. " -"Platformunuzda desteklenen tüm biçim kodlarını görmek için :manpage:" -"`strftime(3)` belgelerine bakın." +"Platformunuzda desteklenen tüm biçim kodlarını görmek " +"için :manpage:`strftime(3)` belgelerine bakın." #: library/time.rst:546 msgid "" @@ -1065,18 +1067,18 @@ msgid "" "is a :class:`struct_time` as returned by :func:`gmtime` or :func:`localtime`." msgstr "" "Bir biçime göre bir zamanı temsil eden bir dizeyi ayrıştırın. Dönüş " -"değeri, :func:`gmtime` veya :func:`localtime` tarafından döndürülen bir :" -"class:`struct_time` şeklindedir." +"değeri, :func:`gmtime` veya :func:`localtime` tarafından döndürülen " +"bir :class:`struct_time` şeklindedir." #: library/time.rst:561 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." +"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 "" "*format* parametresi, :func:`strftime` tarafından kullanılanlarla aynı " "yönergeleri kullanır; varsayılan olarak :func:`ctime` tarafından döndürülen " @@ -1118,10 +1120,10 @@ msgstr "" #: library/time.rst:590 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:" +"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 "" ":func:`gmtime`, :func:`localtime` ve :func:`strptime` tarafından döndürülen " "zaman değeri dizisinin türü. :term:`named tuple` arayüzüne sahip bir " @@ -1247,13 +1249,13 @@ msgstr "" #: library/time.rst:652 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." +"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 "" ":class:`struct_time` bekleyen bir fonksiyona yanlış uzunluğa sahip bir demet " -"iletildiğinde, veya yanlış türde elemanlara sahip olmak, bir :exc:" -"`TypeError` yükseltir." +"iletildiğinde, veya yanlış türde elemanlara sahip olmak, " +"bir :exc:`TypeError` yükseltir." #: library/time.rst:658 #, fuzzy @@ -1261,14 +1263,14 @@ msgid "" "Return the time in seconds since the epoch_ as a floating-point number. The " "handling of `leap seconds`_ is platform dependent. On Windows and most Unix " "systems, the leap seconds are not counted towards the time in seconds since " -"the epoch_. This is commonly referred to as `Unix time `_." +"the epoch_. This is commonly referred to as `Unix time `_." msgstr "" "epoch_ 'dan bu yana geçen süreyi kayan noktalı bir sayı olarak saniye " "cinsinden döndürür. `leap seconds`_ 'ın ele alınması platforma bağlıdır. " "Windows'ta ve çoğu Unix sisteminde, artık saniyeler, epoch_'dan bu yana " -"saniye cinsinden süreye dahil edilmez. Bu genellikle `Unix time `_ olarak anılır." +"saniye cinsinden süreye dahil edilmez. Bu genellikle `Unix time `_ olarak anılır." #: library/time.rst:664 #, fuzzy @@ -1287,11 +1289,11 @@ msgstr "" #: library/time.rst:670 msgid "" "The number returned by :func:`.time` may be converted into a more common " -"time format (i.e. year, month, day, hour, etc...) in UTC by passing it to :" -"func:`gmtime` function or in local time by passing it to the :func:" -"`localtime` function. In both cases a :class:`struct_time` object is " -"returned, from which the components of the calendar date may be accessed as " -"attributes." +"time format (i.e. year, month, day, hour, etc...) in UTC by passing it " +"to :func:`gmtime` function or in local time by passing it to " +"the :func:`localtime` function. In both cases a :class:`struct_time` object " +"is returned, from which the components of the calendar date may be accessed " +"as attributes." msgstr "" ":func:`.time` tarafından döndürülen sayı UTC'de :func:`gmtime` fonksiyonuna " "geçirerek veya yerel saatte :func:`localtime` fonksiyonuna geçirerek daha " @@ -1304,8 +1306,8 @@ msgid "" "Use :func:`time_ns` to avoid the precision loss caused by the :class:`float` " "type." msgstr "" -":class:`float` türünden kaynaklanan kesinlik kaybından kaçınmak için :func:" -"`time_ns` kullanınız." +":class:`float` türünden kaynaklanan kesinlik kaybından kaçınmak " +"için :func:`time_ns` kullanınız." #: library/time.rst:683 msgid "" @@ -1331,11 +1333,11 @@ msgstr "" #: library/time.rst:702 msgid "" -"Use :func:`thread_time_ns` to avoid the precision loss caused by the :class:" -"`float` type." +"Use :func:`thread_time_ns` to avoid the precision loss caused by " +"the :class:`float` type." msgstr "" -":class:`float` türünün neden olduğu kesinlik kaybını önlemek için :func:" -"`thread_time_ns` kullanın." +":class:`float` türünün neden olduğu kesinlik kaybını önlemek " +"için :func:`thread_time_ns` kullanın." #: library/time.rst:707 msgid "Unix systems supporting ``CLOCK_THREAD_CPUTIME_ID``." @@ -1369,8 +1371,8 @@ msgstr "" #: library/time.rst:733 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." +"affect the output of functions like :func:`localtime` without " +"calling :func:`tzset`, this behavior should not be relied on." msgstr "" "Çoğu durumda, :envvar:`TZ` ortam değişkenini değiştirmek, :func:`localtime` " "gibi işlevlerin çıktısını :func:`tzset` çağırmadan etkileyebilirse de, bu " @@ -1511,9 +1513,9 @@ msgstr "" "dilimi kurallarını belirlemek için sistemin zoneinfo (:manpage:`tzfile(5)`) " "veritabanını kullanmak daha uygundur. Bunu yapmak için, :envvar:`TZ` çevre " "değişkenini gerekli saat dilimi veri dosyasının konumuna ayarlayınız, " -"sistemlerin 'zoneinfo' saat dilimi veritabanının köküne göre, genellikle :" -"file:`/usr/share/zoneinfo` konumunda bulunur. Örnek olarak, ``'US/" -"Eastern'``, ``'Australia/Melbourne'``, ``'Egypt'`` veya ``'Europe/" +"sistemlerin 'zoneinfo' saat dilimi veritabanının köküne göre, " +"genellikle :file:`/usr/share/zoneinfo` konumunda bulunur. Örnek olarak, " +"``'US/Eastern'``, ``'Australia/Melbourne'``, ``'Egypt'`` veya ``'Europe/" "Amsterdam'``. ::" #: library/time.rst:797 @@ -1534,8 +1536,8 @@ msgstr "Saat Kimliği Sabitleri" #: library/time.rst:812 msgid "" -"These constants are used as parameters for :func:`clock_getres` and :func:" -"`clock_gettime`." +"These constants are used as parameters for :func:`clock_getres` " +"and :func:`clock_gettime`." msgstr "" "Şu sabitler :func:`clock_getres` ve :func:`clock_gettime` için parametre " "olarak kullanılırlar." @@ -1631,8 +1633,8 @@ msgstr "" #: library/time.rst:919 msgid "" -"The following constant is the only parameter that can be sent to :func:" -"`clock_settime`." +"The following constant is the only parameter that can be sent " +"to :func:`clock_settime`." msgstr "" "Aşağıdaki sabit :func:`clock_settime`'a gönderilebilecek tek parametredir." @@ -1689,19 +1691,21 @@ msgstr "" #: library/time.rst:961 #, fuzzy msgid "" -"For the above Timezone constants (:data:`altzone`, :data:`daylight`, :data:" -"`timezone`, and :data:`tzname`), the value is determined by the timezone " -"rules in effect at module load time or the last time :func:`tzset` is called " -"and may be incorrect for times in the past. It is recommended to use the :" -"attr:`~struct_time.tm_gmtoff` and :attr:`~struct_time.tm_zone` results from :" -"func:`localtime` to obtain timezone information." -msgstr "" -"Yukarıdaki Saat Dilimi sabitleri için (:data:`altzone`, :data:`daylight`, :" -"data:`timezone` ve :data:`tzname`), değer, modül yükleme zamanında geçerli " -"olan saat dilimi kurallarına göre belirlenir veya son kez :func:`tzset` " -"çağrılır ve geçmişteki zamanlar için yanlış olabilir. Saat dilimi bilgisi " -"almak için :func:`localtime`'den :attr:`tm_gmtoff` ve :attr:`tm_zone` " -"sonuçlarının kullanılması önerilir." +"For the above Timezone constants " +"(:data:`altzone`, :data:`daylight`, :data:`timezone`, and :data:`tzname`), " +"the value is determined by the timezone rules in effect at module load time " +"or the last time :func:`tzset` is called and may be incorrect for times in " +"the past. It is recommended to use the :attr:`~struct_time.tm_gmtoff` " +"and :attr:`~struct_time.tm_zone` results from :func:`localtime` to obtain " +"timezone information." +msgstr "" +"Yukarıdaki Saat Dilimi sabitleri için " +"(:data:`altzone`, :data:`daylight`, :data:`timezone` ve :data:`tzname`), " +"değer, modül yükleme zamanında geçerli olan saat dilimi kurallarına göre " +"belirlenir veya son kez :func:`tzset` çağrılır ve geçmişteki zamanlar için " +"yanlış olabilir. Saat dilimi bilgisi almak " +"için :func:`localtime`'den :attr:`tm_gmtoff` ve :attr:`tm_zone` sonuçlarının " +"kullanılması önerilir." #: library/time.rst:970 msgid "Module :mod:`datetime`" @@ -1718,11 +1722,12 @@ msgstr ":mod:`locale` modülü" #: library/time.rst:974 msgid "" "Internationalization services. The locale setting affects the " -"interpretation of many format specifiers in :func:`strftime` and :func:" -"`strptime`." +"interpretation of many format specifiers in :func:`strftime` " +"and :func:`strptime`." msgstr "" -"Uluslararasılaştırma servisleri. Yerel ayar, :func:`strftime` ve :func:" -"`strptime` içindeki birçok biçim belirticisinin yorumlanmasını etkiler." +"Uluslararasılaştırma servisleri. Yerel ayar, :func:`strftime` " +"ve :func:`strptime` içindeki birçok biçim belirticisinin yorumlanmasını " +"etkiler." #: library/time.rst:977 msgid "Module :mod:`calendar`" @@ -1754,8 +1759,8 @@ msgstr "" "dakika farkına genişleyen ``%z`` çıkışı, tüm ANSI C kütüphaneleri tarafından " "desteklenmez. Ayrıca, orijinal 1982 :rfc:`822` standardının katı bir " "okuması, iki basamaklı bir yıl gerektirir (``%y`` yerine ``%y``), ancak " -"uygulama 2000 yılından çok önce 4 basamaklı yıllara taşındı. Bundan sonra :" -"rfc:`822` geçerliliğini yitirdi ve 4 basamaklı yıl önce :rfc:`1123` " +"uygulama 2000 yılından çok önce 4 basamaklı yıllara taşındı. Bundan " +"sonra :rfc:`822` geçerliliğini yitirdi ve 4 basamaklı yıl önce :rfc:`1123` " "tarafından önerildi ve ardından :rfc:`2822` tarafından zorunlu kılındı." #: library/time.rst:22 diff --git a/library/timeit.po b/library/timeit.po index 041ba39bc..97bfcad74 100644 --- a/library/timeit.po +++ b/library/timeit.po @@ -81,8 +81,8 @@ msgstr "" #: library/timeit.rst:52 msgid "" "Note however that :func:`.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." +"repetitions only when the command-line interface is used. In " +"the :ref:`timeit-examples` section you can find more advanced examples." msgstr "" #: library/timeit.rst:60 @@ -144,9 +144,9 @@ msgstr "" #: library/timeit.rst:111 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." +"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 "" #: library/timeit.rst:115 @@ -323,8 +323,8 @@ msgstr "" 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 5 repetitions 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 5 repetitions is " "probably enough in most cases. You can use :func:`time.process_time` to " "measure CPU time." msgstr "" @@ -352,8 +352,8 @@ msgid "" "$ python -m timeit -s \"text = 'sample string'; char = 'g'\" \"char in " "text\"\n" "5000000 loops, best of 5: 0.0877 usec per loop\n" -"$ python -m timeit -s \"text = 'sample string'; char = 'g'\" \"text." -"find(char)\"\n" +"$ python -m timeit -s \"text = 'sample string'; char = 'g'\" " +"\"text.find(char)\"\n" "1000000 loops, best of 5: 0.342 usec per loop" msgstr "" @@ -397,8 +397,9 @@ msgstr "" #: library/timeit.rst:312 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:" +"lines. Here we compare the cost of using :func:`hasattr` " +"vs. :keyword:`try`/:keyword:`except` to test for missing and present object " +"attributes:" msgstr "" #: library/timeit.rst:316 diff --git a/library/tk.po b/library/tk.po index ae6b491dd..22dbf4ad0 100644 --- a/library/tk.po +++ b/library/tk.po @@ -24,28 +24,28 @@ msgstr "Tk ile Grafik Kullanıcı Arayüzleri" 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." +"programmers using the :mod:`tkinter` package, and its extension, " +"the :mod:`tkinter.tix` and the :mod:`tkinter.ttk` modules." msgstr "" "Tk/Tcl uzun zamandır Python'ın ayrılmaz bir parçası olmuştur. Python " -"programcılarının :mod:`tkinter` paketini ve onun uzantısı olan :mod:`tkinter." -"tix` ve :mod:`tkinter.ttk` modüllerini kullanarak programcıların " -"kullanabilecekleri sağlam ve platformdan bağımsız bir pencereleme araç seti " -"sunar." +"programcılarının :mod:`tkinter` paketini ve onun uzantısı " +"olan :mod:`tkinter.tix` ve :mod:`tkinter.ttk` modüllerini kullanarak " +"programcıların kullanabilecekleri sağlam ve platformdan bağımsız bir " +"pencereleme araç seti sunar." #: 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." +"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." msgstr "" -":mod:`tkinter` paketi Tcl/Tk üzerinde ince bir nesne yönelimli katmandır. :" -"mod:`tkinter` kullanmak için Tcl kodu yazmanıza gerek yoktur, ancak Tk " -"belgelerine ve bazen de Tcl belgelerine başvurmanız gerekecektir. :mod:" -"`tkinter`, Tk widget'larını Python sınıfları olarak uygulayan bir dizi " -"sarmalayıcıdır." +":mod:`tkinter` paketi Tcl/Tk üzerinde ince bir nesne yönelimli " +"katmandır. :mod:`tkinter` kullanmak için Tcl kodu yazmanıza gerek yoktur, " +"ancak Tk belgelerine ve bazen de Tcl belgelerine başvurmanız " +"gerekecektir. :mod:`tkinter`, Tk widget'larını Python sınıfları olarak " +"uygulayan bir dizi sarmalayıcıdır." #: library/tk.rst:24 msgid "" @@ -64,8 +64,8 @@ msgstr "" "mevcuttur. Ayrıca :mod:`tkinter` modası geçmiş ve eski bir görünüme sahip " "olmasına rağmen, Tk 8.5'te bu durum büyük ölçüde geliştirilmiştir. Bununla " "birlikte, ilginizi çekebilecek başka birçok GUI kütüphanesi vardır. Python " -"wiki, birkaç alternatif `GUI geliştirme çerçevesi ve aracını `_ sizler için listeler." +"wiki, birkaç alternatif `GUI geliştirme çerçevesi ve aracını `_ sizler için listeler." #: library/tk.rst:7 msgid "GUI" diff --git a/library/tkinter.colorchooser.po b/library/tkinter.colorchooser.po index e64a5bc50..5ae575f6b 100644 --- a/library/tkinter.colorchooser.po +++ b/library/tkinter.colorchooser.po @@ -28,8 +28,8 @@ msgstr "" msgid "" "The :mod:`tkinter.colorchooser` module provides the :class:`Chooser` class " "as an interface to the native color picker dialog. ``Chooser`` implements a " -"modal color choosing dialog window. The ``Chooser`` class inherits from the :" -"class:`~tkinter.commondialog.Dialog` class." +"modal color choosing dialog window. The ``Chooser`` class inherits from " +"the :class:`~tkinter.commondialog.Dialog` class." msgstr "" #: library/tkinter.colorchooser.rst:21 diff --git a/library/tkinter.messagebox.po b/library/tkinter.messagebox.po index 75e1cdd5a..85cad9032 100644 --- a/library/tkinter.messagebox.po +++ b/library/tkinter.messagebox.po @@ -175,14 +175,16 @@ msgstr "" #: library/tkinter.messagebox.rst:104 msgid "" -"Ask if operation should proceed. Shows buttons :data:`OK` and :data:" -"`CANCEL`. Returns ``True`` if the answer is ok and ``False`` otherwise." +"Ask if operation should proceed. Shows buttons :data:`OK` " +"and :data:`CANCEL`. Returns ``True`` if the answer is ok and ``False`` " +"otherwise." msgstr "" #: library/tkinter.messagebox.rst:109 msgid "" -"Ask if operation should be retried. Shows buttons :data:`RETRY` and :data:" -"`CANCEL`. Return ``True`` if the answer is yes and ``False`` otherwise." +"Ask if operation should be retried. Shows buttons :data:`RETRY` " +"and :data:`CANCEL`. Return ``True`` if the answer is yes and ``False`` " +"otherwise." msgstr "" #: library/tkinter.messagebox.rst:114 @@ -223,8 +225,8 @@ msgstr "" #: library/tkinter.messagebox.rst:168 msgid "" -"Displays two buttons whose symbolic names are :data:`RETRY` and :data:" -"`CANCEL`." +"Displays two buttons whose symbolic names are :data:`RETRY` " +"and :data:`CANCEL`." msgstr "" #: library/tkinter.messagebox.rst:174 @@ -234,8 +236,8 @@ msgstr "" #: library/tkinter.messagebox.rst:180 msgid "" -"Displays three buttons whose symbolic names are :data:`YES`, :data:`NO` and :" -"data:`CANCEL`." +"Displays three buttons whose symbolic names are :data:`YES`, :data:`NO` " +"and :data:`CANCEL`." msgstr "" #: library/tkinter.messagebox.rst:185 diff --git a/library/tkinter.po b/library/tkinter.po index 1af8219ba..b232dd10a 100644 --- a/library/tkinter.po +++ b/library/tkinter.po @@ -188,10 +188,11 @@ msgstr "" #: library/tkinter.rst:93 msgid "" "Tk is a `Tcl package `_ implemented in C " -"that adds custom commands to create and manipulate GUI widgets. Each :class:" -"`Tk` object embeds its own Tcl interpreter instance with Tk loaded into it. " -"Tk's widgets are very customizable, though at the cost of a dated " -"appearance. Tk uses Tcl's event queue to generate and process GUI events." +"that adds custom commands to create and manipulate GUI widgets. " +"Each :class:`Tk` object embeds its own Tcl interpreter instance with Tk " +"loaded into it. Tk's widgets are very customizable, though at the cost of a " +"dated appearance. Tk uses Tcl's event queue to generate and process GUI " +"events." msgstr "" #: library/tkinter.rst:99 @@ -208,8 +209,8 @@ msgstr "" #: library/tkinter.rst:105 msgid "" -"Internally, Tk and Ttk use facilities of the underlying operating system, i." -"e., Xlib on Unix/X11, Cocoa on macOS, GDI on Windows." +"Internally, Tk and Ttk use facilities of the underlying operating system, " +"i.e., Xlib on Unix/X11, Cocoa on macOS, GDI on Windows." msgstr "" #: library/tkinter.rst:108 @@ -322,11 +323,11 @@ msgstr "" #: library/tkinter.rst:161 msgid "" -":class:`Tk` reads and interprets profile files, named :file:`.{className}." -"tcl` and :file:`.{baseName}.tcl`, into the Tcl interpreter and calls :func:" -"`exec` on the contents of :file:`.{className}.py` and :file:`.{baseName}." -"py`. The path for the profile files is the :envvar:`HOME` environment " -"variable or, if that isn't defined, then :data:`os.curdir`." +":class:`Tk` reads and interprets profile files, named :file:`." +"{className}.tcl` and :file:`.{baseName}.tcl`, into the Tcl interpreter and " +"calls :func:`exec` on the contents of :file:`.{className}.py` and :file:`." +"{baseName}.py`. The path for the profile files is the :envvar:`HOME` " +"environment variable or, if that isn't defined, then :data:`os.curdir`." msgstr "" #: library/tkinter.rst:170 @@ -361,8 +362,8 @@ msgid "" "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." +"window created (and the Tk subsystem initialized) by calling " +"its :meth:`loadtk` method." msgstr "" #: library/tkinter.rst:203 @@ -466,8 +467,8 @@ msgstr "" #: library/tkinter.rst:246 msgid "" -"Python's Integrated Development and Learning Environment (IDLE). Based on :" -"mod:`tkinter`." +"Python's Integrated Development and Learning Environment (IDLE). Based " +"on :mod:`tkinter`." msgstr "" #: library/tkinter.rst:249 @@ -477,8 +478,8 @@ msgstr "" #: library/tkinter.rst:250 msgid "" "Symbolic constants that can be used in place of strings when passing various " -"parameters to Tkinter calls. Automatically imported by the main :mod:" -"`tkinter` module." +"parameters to Tkinter calls. Automatically imported by the " +"main :mod:`tkinter` module." msgstr "" #: library/tkinter.rst:254 @@ -570,9 +571,10 @@ msgstr "" #: library/tkinter.rst:309 msgid "" -"The next line creates a label widget holding a static text string. The :meth:" -"`grid` method is used to specify the relative layout (position) of the label " -"within its containing frame widget, similar to how tables in HTML work." +"The next line creates a label widget holding a static text string. " +"The :meth:`grid` method is used to specify the relative layout (position) of " +"the label within its containing frame widget, similar to how tables in HTML " +"work." msgstr "" #: library/tkinter.rst:313 @@ -602,8 +604,8 @@ msgstr "" #: library/tkinter.rst:327 msgid "" "A Tkinter user interface is made up of individual *widgets*. Each widget is " -"represented as a Python object, instantiated from classes like :class:`ttk." -"Frame`, :class:`ttk.Label`, and :class:`ttk.Button`." +"represented as a Python object, instantiated from classes " +"like :class:`ttk.Frame`, :class:`ttk.Label`, and :class:`ttk.Button`." msgstr "" #: library/tkinter.rst:331 @@ -682,8 +684,8 @@ msgid "" "ttk::frame .frm -padding 10\n" "grid .frm\n" "grid [ttk::label .frm.lbl -text \"Hello World!\"] -column 0 -row 0\n" -"grid [ttk::button .frm.btn -text \"Quit\" -command \"destroy .\"] -column 1 -" -"row 0" +"grid [ttk::button .frm.btn -text \"Quit\" -command \"destroy .\"] -column 1 " +"-row 0" msgstr "" #: library/tkinter.rst:377 @@ -841,26 +843,26 @@ msgstr "" msgid "" "In the official Tcl/Tk reference documentation, you'll find most operations " "that look like method calls on the man page for a specific widget (e.g., " -"you'll find the :meth:`invoke` method on the `ttk::button `_ man page), while functions that take a " -"widget as a parameter often have their own man page (e.g., `grid `_)." +"you'll find the :meth:`invoke` method on the `ttk::button `_ man page), while functions " +"that take a widget as a parameter often have their own man page (e.g., `grid " +"`_)." msgstr "" #: library/tkinter.rst:487 msgid "" -"You'll find many common options and methods in the `options `_ or `ttk::widget `_ man pages, while others are found in the man " -"page for a specific widget class." +"You'll find many common options and methods in the `options `_ or `ttk::widget `_ man pages, while others are " +"found in the man page for a specific widget class." msgstr "" #: library/tkinter.rst:492 msgid "" -"You'll also find that many Tkinter methods have compound names, e.g., :func:" -"`winfo_x`, :func:`winfo_height`, :func:`winfo_viewable`. You'd find " -"documentation for all of these in the `winfo `_ man page." +"You'll also find that many Tkinter methods have compound names, " +"e.g., :func:`winfo_x`, :func:`winfo_height`, :func:`winfo_viewable`. You'd " +"find documentation for all of these in the `winfo `_ man page." msgstr "" #: library/tkinter.rst:498 @@ -868,8 +870,8 @@ msgid "" "Somewhat confusingly, there are also methods on all Tkinter widgets that " "don't actually operate on the widget, but operate at a global scope, " "independent of any widget. Examples are methods for accessing the clipboard " -"or the system bell. (They happen to be implemented as methods in the base :" -"class:`Widget` class that all Tkinter widgets inherit from)." +"or the system bell. (They happen to be implemented as methods in the " +"base :class:`Widget` class that all Tkinter widgets inherit from)." msgstr "" #: library/tkinter.rst:507 @@ -904,14 +906,14 @@ msgstr "" #: library/tkinter.rst:524 msgid "" "Tcl/Tk applications are normally event-driven, meaning that after " -"initialization, the interpreter runs an event loop (i.e. :func:`Tk." -"mainloop`) and responds to events. Because it is single-threaded, event " -"handlers must respond quickly, otherwise they will block other events from " -"being processed. To avoid this, any long-running computations should not run " -"in an event handler, but are either broken into smaller pieces using timers, " -"or run in another thread. This is different from many GUI toolkits where the " -"GUI runs in a completely separate thread from all application code including " -"event handlers." +"initialization, the interpreter runs an event loop " +"(i.e. :func:`Tk.mainloop`) and responds to events. Because it is single-" +"threaded, event handlers must respond quickly, otherwise they will block " +"other events from being processed. To avoid this, any long-running " +"computations should not run in an event handler, but are either broken into " +"smaller pieces using timers, or run in another thread. This is different " +"from many GUI toolkits where the GUI runs in a completely separate thread " +"from all application code including event handlers." msgstr "" #: library/tkinter.rst:533 @@ -927,17 +929,17 @@ msgstr "" #: library/tkinter.rst:539 msgid "" -"Tcl/Tk libraries can be built so they are not thread-aware. In this case, :" -"mod:`tkinter` calls the library from the originating Python thread, even if " -"this is different than the thread that created the Tcl interpreter. A global " -"lock ensures only one call occurs at a time." +"Tcl/Tk libraries can be built so they are not thread-aware. In this " +"case, :mod:`tkinter` calls the library from the originating Python thread, " +"even if this is different than the thread that created the Tcl interpreter. " +"A global lock ensures only one call occurs at a time." msgstr "" #: library/tkinter.rst:544 msgid "" -"While :mod:`tkinter` allows you to create more than one instance of a :class:" -"`Tk` object (with its own interpreter), all interpreters that are part of " -"the same thread share a common event queue, which gets ugly fast. In " +"While :mod:`tkinter` allows you to create more than one instance of " +"a :class:`Tk` object (with its own interpreter), all interpreters that are " +"part of the same thread share a common event queue, which gets ugly fast. In " "practice, don't create more than one instance of :class:`Tk` at a time. " "Otherwise, it's best to create them in separate threads and ensure you're " "running a thread-aware Tcl/Tk build." @@ -1010,8 +1012,8 @@ 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." +"particular widget. The Standard Options are documented on " +"the :manpage:`options(3)` man page." msgstr "" #: library/tkinter.rst:596 @@ -1258,12 +1260,12 @@ msgstr "" #: library/tkinter.rst:711 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." +"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 "" #: library/tkinter.rst:898 @@ -1322,10 +1324,10 @@ 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." +"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 "" #: library/tkinter.rst:769 @@ -1535,9 +1537,9 @@ msgstr "" #: library/tkinter.rst:883 msgid "" -"is a string that denotes the target kind of event. (See the :manpage:" -"`bind(3tk)` man page, and page 201 of John Ousterhout's book, :title-" -"reference:`Tcl and the Tk Toolkit (2nd edition)`, for details)." +"is a string that denotes the target kind of event. (See " +"the :manpage:`bind(3tk)` man page, and page 201 of John Ousterhout's " +"book, :title-reference:`Tcl and the Tk Toolkit (2nd edition)`, for details)." msgstr "" #: library/tkinter.rst:887 @@ -1860,12 +1862,12 @@ msgstr "" #: library/tkinter.rst:1015 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)``." +"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 "" #: library/tkinter.rst:1026 diff --git a/library/tkinter.scrolledtext.po b/library/tkinter.scrolledtext.po index de7e6bcef..e17bbd9fc 100644 --- a/library/tkinter.scrolledtext.po +++ b/library/tkinter.scrolledtext.po @@ -36,9 +36,9 @@ msgstr "" 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." +"acquired from the :class:`Frame` object. This allows " +"the :class:`ScrolledText` widget to be used directly to achieve most normal " +"geometry management behavior." msgstr "" #: library/tkinter.scrolledtext.rst:24 diff --git a/library/tkinter.tix.po b/library/tkinter.tix.po index 81a9adda2..c3147662f 100644 --- a/library/tkinter.tix.po +++ b/library/tkinter.tix.po @@ -26,8 +26,8 @@ msgstr "" #: library/tkinter.tix.rst:13 msgid "" -"This Tk extension is unmaintained and should not be used in new code. Use :" -"mod:`tkinter.ttk` instead." +"This Tk extension is unmaintained and should not be used in new code. " +"Use :mod:`tkinter.ttk` instead." msgstr "" #: library/tkinter.tix.rst:19 @@ -38,9 +38,9 @@ msgid "" "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." +"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 "" #: library/tkinter.tix.rst:29 @@ -81,8 +81,8 @@ msgstr "" #: library/tkinter.tix.rst:46 msgid "" -"`Tix Development Applications `_" +"`Tix Development Applications `_" msgstr "" #: library/tkinter.tix.rst:47 @@ -104,11 +104,11 @@ msgstr "" #: 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`::" +"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 "" #: library/tkinter.tix.rst:67 @@ -138,8 +138,9 @@ msgstr "" #: library/tkinter.tix.rst:83 msgid "" -"`Tix `_ introduces over 40 widget classes to the :mod:`tkinter` repertoire." +"`Tix `_ introduces over 40 widget classes to the :mod:`tkinter` " +"repertoire." msgstr "" #: library/tkinter.tix.rst:88 @@ -317,9 +318,10 @@ msgstr "" #: library/tkinter.tix.rst:335 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." +"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 "" #: library/tkinter.tix.rst:347 @@ -356,8 +358,8 @@ msgid "" "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." +"through these pages by choosing the name of the desired page in " +"the :attr:`hlist` subwidget." msgstr "" #: library/tkinter.tix.rst:406 @@ -380,18 +382,18 @@ msgstr "" #: library/tkinter.tix.rst:432 msgid "" -"`pixmap `_ capabilities to all :mod:`tkinter.tix` and :mod:`tkinter` widgets to " -"create color images from XPM files." +"`pixmap `_ capabilities to all :mod:`tkinter.tix` and :mod:`tkinter` " +"widgets to create color images from XPM files." msgstr "" #: library/tkinter.tix.rst:441 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 " +"`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 "" @@ -416,8 +418,8 @@ msgstr "" #: library/tkinter.tix.rst:479 msgid "" -"The `Form `_ geometry manager based on attachment rules for all Tk widgets." +"The `Form `_ geometry manager based on attachment rules for all Tk widgets." msgstr "" #: library/tkinter.tix.rst:485 @@ -465,21 +467,22 @@ msgstr "" #: library/tkinter.tix.rst:524 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." +"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 "" #: library/tkinter.tix.rst:534 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." +"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 "" #: library/tkinter.tix.rst:544 @@ -495,16 +498,16 @@ msgstr "" #: library/tkinter.tix.rst:554 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." +"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 "" #: library/tkinter.tix.rst:567 @@ -529,8 +532,8 @@ msgstr "" 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." +"sets using the :meth:`tix_config` method. Instead, " +"the :meth:`tix_resetoptions` method must be used." msgstr "" #: library/tkinter.tix.rst:11 diff --git a/library/tkinter.ttk.po b/library/tkinter.ttk.po index 5ce73a4f5..babef5a53 100644 --- a/library/tkinter.ttk.po +++ b/library/tkinter.ttk.po @@ -73,11 +73,9 @@ msgstr "" #: library/tkinter.ttk.rst:43 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." +"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 "" #: library/tkinter.ttk.rst:49 @@ -92,8 +90,8 @@ msgstr "" #: library/tkinter.ttk.rst:59 msgid "" -"`Converting existing applications to use Tile widgets `_" +"`Converting existing applications to use Tile widgets `_" msgstr "" #: library/tkinter.ttk.rst:60 @@ -108,13 +106,11 @@ msgstr "" #: library/tkinter.ttk.rst:67 msgid "" -"Ttk comes with 18 widgets, twelve 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`, :class:`Scrollbar`, and :class:" -"`Spinbox`. 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`." +"Ttk comes with 18 widgets, twelve 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`, :class:`Scrollbar`, " +"and :class:`Spinbox`. 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 "" #: library/tkinter.ttk.rst:75 @@ -522,11 +518,10 @@ msgstr "" #: library/tkinter.ttk.rst:300 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`, " +"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 "" @@ -650,12 +645,11 @@ msgstr "" #: library/tkinter.ttk.rst:388 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.xview`, it has some other " -"methods, described at :class:`ttk.Spinbox`." +"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.xview`, " +"it has some other methods, described at :class:`ttk.Spinbox`." msgstr "" #: library/tkinter.ttk.rst:405 @@ -822,8 +816,8 @@ msgstr "" #: library/tkinter.ttk.rst:523 msgid "" -"Specifies an image to display in the tab. See the option image described in :" -"class:`Widget`." +"Specifies an image to display in the tab. See the option image described " +"in :class:`Widget`." msgstr "" #: library/tkinter.ttk.rst:526 @@ -835,8 +829,8 @@ msgstr "" #: library/tkinter.ttk.rst:530 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." +"string. The underlined character is used for mnemonic activation " +"if :meth:`Notebook.enable_traversal` is called." msgstr "" #: library/tkinter.ttk.rst:538 @@ -1092,9 +1086,9 @@ msgstr "" #: library/tkinter.ttk.rst:705 msgid "" -"Begin autoincrement mode: schedules a recurring timer event that calls :meth:" -"`Progressbar.step` every *interval* milliseconds. If omitted, *interval* " -"defaults to 50 milliseconds." +"Begin autoincrement mode: schedules a recurring timer event that " +"calls :meth:`Progressbar.step` every *interval* milliseconds. If omitted, " +"*interval* defaults to 50 milliseconds." msgstr "" #: library/tkinter.ttk.rst:712 @@ -1107,8 +1101,8 @@ msgstr "" #: library/tkinter.ttk.rst:719 msgid "" -"Stop autoincrement mode: cancels any recurring timer event initiated by :" -"meth:`Progressbar.start` for this progress bar." +"Stop autoincrement mode: cancels any recurring timer event initiated " +"by :meth:`Progressbar.start` for this progress bar." msgstr "" #: library/tkinter.ttk.rst:724 @@ -1215,8 +1209,8 @@ msgstr "" #: library/tkinter.ttk.rst:795 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`." +"the options described in `Scrollable Widget Options`_ and the " +"methods :meth:`Treeview.xview` and :meth:`Treeview.yview`." msgstr "" #: library/tkinter.ttk.rst:810 @@ -1887,8 +1881,8 @@ msgid "" "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())." +"style option. If you don't know the class name of a widget, use the " +"method :meth:`Misc.winfo_class` (somewidget.winfo_class())." msgstr "" #: library/tkinter.ttk.rst:1275 @@ -2168,9 +2162,9 @@ msgstr "" 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." +"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 "" #: library/tkinter.ttk.rst:1474 diff --git a/library/token.po b/library/token.po index 096fe9525..2f71a8b59 100644 --- a/library/token.po +++ b/library/token.po @@ -301,8 +301,8 @@ msgstr "" #: library/token.rst:92 msgid "" -"Added :data:`TYPE_COMMENT`, :data:`TYPE_IGNORE`, :data:`COLONEQUAL`. Added :" -"data:`AWAIT` and :data:`ASYNC` tokens back (they're needed to support " +"Added :data:`TYPE_COMMENT`, :data:`TYPE_IGNORE`, :data:`COLONEQUAL`. " +"Added :data:`AWAIT` and :data:`ASYNC` tokens back (they're needed to support " "parsing older Python versions for :func:`ast.parse` with ``feature_version`` " "set to 6 or lower)." msgstr "" diff --git a/library/tokenize.po b/library/tokenize.po index 2e9fb4594..d935657f6 100644 --- a/library/tokenize.po +++ b/library/tokenize.po @@ -34,18 +34,18 @@ msgstr "" #: library/tokenize.rst:19 msgid "" -"To simplify token stream handling, all :ref:`operator ` and :ref:" -"`delimiter ` tokens and :data:`Ellipsis` 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`." +"To simplify token stream handling, all :ref:`operator ` " +"and :ref:`delimiter ` tokens and :data:`Ellipsis` 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 "" #: library/tokenize.rst:28 msgid "" "Note that the functions in this module are only designed to parse " -"syntactically valid Python code (code that does not raise when parsed using :" -"func:`ast.parse`). The behavior of the functions in this module is " +"syntactically valid Python code (code that does not raise when parsed " +"using :func:`ast.parse`). The behavior of the functions in this module is " "**undefined** when providing invalid Python code and it can change at any " "point." msgstr "" @@ -61,9 +61,9 @@ msgstr "" #: library/tokenize.rst:41 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." +"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 "" #: library/tokenize.rst:46 @@ -112,14 +112,14 @@ msgstr "" #: library/tokenize.rst:77 msgid "" -"The result is an iterator yielding named tuples, exactly like :func:`." -"tokenize`. It does not yield an :data:`~token.ENCODING` token." +"The result is an iterator yielding named tuples, exactly " +"like :func:`.tokenize`. It does not yield an :data:`~token.ENCODING` token." msgstr "" #: library/tokenize.rst:80 msgid "" -"All constants from the :mod:`token` module are also exported from :mod:" -"`tokenize`." +"All constants from the :mod:`token` module are also exported " +"from :mod:`tokenize`." msgstr "" #: library/tokenize.rst:83 @@ -187,14 +187,14 @@ msgstr "" #: library/tokenize.rst:126 msgid "" -"Use :func:`.open` to open Python source files: it uses :func:" -"`detect_encoding` to detect the file encoding." +"Use :func:`.open` to open Python source files: it " +"uses :func:`detect_encoding` to detect the file encoding." msgstr "" #: library/tokenize.rst:132 msgid "" -"Open a file in read only mode using the encoding detected by :func:" -"`detect_encoding`." +"Open a file in read only mode using the encoding detected " +"by :func:`detect_encoding`." msgstr "" #: library/tokenize.rst:139 diff --git a/library/tomllib.po b/library/tomllib.po index 24843d620..e910a344a 100644 --- a/library/tomllib.po +++ b/library/tomllib.po @@ -52,17 +52,17 @@ msgstr "" #: library/tomllib.rst:39 msgid "" "Read a TOML file. The first argument should be a readable and binary file " -"object. Return a :class:`dict`. Convert TOML types to Python using this :ref:" -"`conversion table `." +"object. Return a :class:`dict`. Convert TOML types to Python using " +"this :ref:`conversion table `." msgstr "" #: library/tomllib.rst:43 msgid "" "*parse_float* will be called with the string of every TOML float to be " "decoded. By default, this is equivalent to ``float(num_str)``. This can be " -"used to use another datatype or parser for TOML floats (e.g. :class:`decimal." -"Decimal`). The callable must not return a :class:`dict` or a :class:`list`, " -"else a :exc:`ValueError` is raised." +"used to use another datatype or parser for TOML floats " +"(e.g. :class:`decimal.Decimal`). The callable must not return " +"a :class:`dict` or a :class:`list`, else a :exc:`ValueError` is raised." msgstr "" #: library/tomllib.rst:58 @@ -174,8 +174,8 @@ msgstr "" #: library/tomllib.rst:108 msgid "" -"datetime.datetime (``tzinfo`` attribute set to an instance of ``datetime." -"timezone``)" +"datetime.datetime (``tzinfo`` attribute set to an instance of " +"``datetime.timezone``)" msgstr "" #: library/tomllib.rst:110 diff --git a/library/trace.po b/library/trace.po index b6898e1d7..fde100d7f 100644 --- a/library/trace.po +++ b/library/trace.po @@ -81,11 +81,11 @@ msgstr "" #: library/trace.rst:51 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." +"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 "" #: library/trace.rst:61 @@ -105,9 +105,9 @@ msgstr "" #: library/trace.rst:76 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." +"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 "" #: library/trace.rst:82 @@ -126,8 +126,8 @@ msgstr "" #: library/trace.rst:96 msgid "" -"Directory where the report files go. The coverage report for ``package." -"module`` is written to file :file:`{dir}/{package}/{module}.cover`." +"Directory where the report files go. The coverage report for " +"``package.module`` is written to file :file:`{dir}/{package}/{module}.cover`." msgstr "" #: library/trace.rst:101 diff --git a/library/traceback.po b/library/traceback.po index c580d326e..61fab9d1a 100644 --- a/library/traceback.po +++ b/library/traceback.po @@ -39,8 +39,8 @@ msgstr "" #: library/traceback.rst:23 msgid "" "The module uses :ref:`traceback objects ` --- these are " -"objects of type :class:`types.TracebackType`, which are assigned to the :" -"attr:`~BaseException.__traceback__` field of :class:`BaseException` " +"objects of type :class:`types.TracebackType`, which are assigned to " +"the :attr:`~BaseException.__traceback__` field of :class:`BaseException` " "instances." msgstr "" @@ -74,11 +74,11 @@ msgstr "" #: library/traceback.rst:41 msgid "" -":class:`TracebackException` class and its helper classes :class:" -"`StackSummary` and :class:`FrameSummary`. These offer both more flexibility " -"in the output generated and the ability to store the information necessary " -"for later formatting without holding references to actual exception and " -"traceback objects." +":class:`TracebackException` class and its helper " +"classes :class:`StackSummary` and :class:`FrameSummary`. These offer both " +"more flexibility in the output generated and the ability to store the " +"information necessary for later formatting without holding references to " +"actual exception and traceback objects." msgstr "" #: library/traceback.rst:49 @@ -98,10 +98,10 @@ msgstr "" #: library/traceback.rst:64 msgid "" -"The meaning of the *limit* parameter is different than the meaning of :const:" -"`sys.tracebacklimit`. A negative *limit* value corresponds to a positive " -"value of :const:`!sys.tracebacklimit`, whereas the behaviour of a positive " -"*limit* value cannot be achieved with :const:`!sys.tracebacklimit`." +"The meaning of the *limit* parameter is different than the meaning " +"of :const:`sys.tracebacklimit`. A negative *limit* value corresponds to a " +"positive value of :const:`!sys.tracebacklimit`, whereas the behaviour of a " +"positive *limit* value cannot be achieved with :const:`!sys.tracebacklimit`." msgstr "" #: library/traceback.rst:135 @@ -111,8 +111,8 @@ msgstr "" #: library/traceback.rst:77 msgid "" "Print exception information and stack trace entries from :ref:`traceback " -"object ` *tb* to *file*. This differs from :func:" -"`print_tb` in the following ways:" +"object ` *tb* to *file*. This differs " +"from :func:`print_tb` in the following ways:" msgstr "" #: library/traceback.rst:82 @@ -142,10 +142,10 @@ msgstr "" #: library/traceback.rst:97 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:" -"`~BaseException.__cause__` or :attr:`~BaseException.__context__` attributes " -"of the exception) will be printed as well, like the interpreter itself does " -"when printing an unhandled exception." +"If *chain* is true (the default), then chained exceptions " +"(the :attr:`~BaseException.__cause__` or :attr:`~BaseException.__context__` " +"attributes of the exception) will be printed as well, like the interpreter " +"itself does when printing an unhandled exception." msgstr "" #: library/traceback.rst:201 @@ -185,30 +185,30 @@ msgid "" "Return a :class:`StackSummary` object representing a list of \"pre-" "processed\" stack trace entries extracted from the :ref:`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 :class:" -"`FrameSummary` object containing attributes :attr:`~FrameSummary.filename`, :" -"attr:`~FrameSummary.lineno`, :attr:`~FrameSummary.name`, and :attr:" -"`~FrameSummary.line` representing the information that is usually printed " -"for a stack trace." +"traces. The optional *limit* argument has the same meaning as " +"for :func:`print_tb`. A \"pre-processed\" stack trace entry is " +"a :class:`FrameSummary` object containing " +"attributes :attr:`~FrameSummary.filename`, :attr:`~FrameSummary.lineno`, :attr:`~FrameSummary.name`, " +"and :attr:`~FrameSummary.line` representing the information that is usually " +"printed for a stack trace." msgstr "" #: library/traceback.rst:154 msgid "" "Extract the raw traceback from the current :ref:`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`." +"The optional *f* and *limit* arguments have the same meaning as " +"for :func:`print_stack`." msgstr "" #: library/traceback.rst:162 msgid "" -"Given a list of tuples or :class:`FrameSummary` objects 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``." +"Given a list of tuples or :class:`FrameSummary` objects 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 "" #: library/traceback.rst:172 @@ -246,8 +246,8 @@ msgstr "" #: library/traceback.rst:204 msgid "" -"This function's behavior and signature were modified to match :func:" -"`print_exception`." +"This function's behavior and signature were modified to " +"match :func:`print_exception`." msgstr "" #: library/traceback.rst:211 @@ -281,8 +281,8 @@ msgstr "" #: library/traceback.rst:244 msgid "" "Walk a traceback following :attr:`~traceback.tb_next` yielding the frame and " -"line number for each frame. This helper is used with :meth:`StackSummary." -"extract`." +"line number for each frame. This helper is used " +"with :meth:`StackSummary.extract`." msgstr "" #: library/traceback.rst:252 @@ -293,10 +293,10 @@ msgstr "" msgid "" ":class:`!TracebackException` objects are created from actual exceptions to " "capture data for later printing. They offer a more lightweight method of " -"storing this information by avoiding holding references to :ref:" -"`traceback` and :ref:`frame` objects In " -"addition, they expose more options to configure the output compared to the " -"module-level functions described above." +"storing this information by avoiding holding references " +"to :ref:`traceback` and :ref:`frame` " +"objects In addition, they expose more options to configure the output " +"compared to the module-level functions described above." msgstr "" #: library/traceback.rst:265 @@ -338,21 +338,21 @@ msgstr "" #: library/traceback.rst:291 msgid "" -"A :class:`!TracebackException` of the original :attr:`~BaseException." -"__cause__`." +"A :class:`!TracebackException` of the " +"original :attr:`~BaseException.__cause__`." msgstr "" #: library/traceback.rst:296 msgid "" -"A :class:`!TracebackException` of the original :attr:`~BaseException." -"__context__`." +"A :class:`!TracebackException` of the " +"original :attr:`~BaseException.__context__`." msgstr "" #: library/traceback.rst:301 msgid "" -"If ``self`` represents an :exc:`ExceptionGroup`, this field holds a list of :" -"class:`!TracebackException` instances representing the nested exceptions. " -"Otherwise it is ``None``." +"If ``self`` represents an :exc:`ExceptionGroup`, this field holds a list " +"of :class:`!TracebackException` instances representing the nested " +"exceptions. Otherwise it is ``None``." msgstr "" #: library/traceback.rst:309 @@ -448,9 +448,9 @@ msgstr "" #: library/traceback.rst:394 msgid "" "The generator emits the exception's message followed by its notes (if it has " -"any). The exception message is normally a single string; however, for :exc:" -"`SyntaxError` exceptions, it consists of several lines that (when printed) " -"display detailed information about where the syntax error occurred." +"any). The exception message is normally a single string; however, " +"for :exc:`SyntaxError` exceptions, it consists of several lines that (when " +"printed) display detailed information about where the syntax error occurred." msgstr "" #: library/traceback.rst:400 @@ -480,8 +480,8 @@ msgid "" "*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." +"formatted). If *capture_locals* is ``True`` the local variables in " +"each :class:`!FrameSummary` are captured as object representations." msgstr "" #: library/traceback.rst:429 @@ -492,9 +492,10 @@ msgstr "" #: library/traceback.rst:435 msgid "" -"Construct a :class:`!StackSummary` object from a supplied list of :class:" -"`FrameSummary` objects or old-style list of tuples. Each tuple should be a " -"4-tuple with *filename*, *lineno*, *name*, *line* as the elements." +"Construct a :class:`!StackSummary` object from a supplied list " +"of :class:`FrameSummary` objects or old-style list of tuples. Each tuple " +"should be a 4-tuple with *filename*, *lineno*, *name*, *line* as the " +"elements." msgstr "" #: library/traceback.rst:442 @@ -539,13 +540,13 @@ msgid "" "Represents a single :ref:`frame ` in the :ref:`traceback " "` or stack that is being formatted or printed. It may " "optionally have a stringified version of the frame's 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 :class:`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." +"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 :class:`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 "" #: library/traceback.rst:487 @@ -554,9 +555,9 @@ msgstr "" #: library/traceback.rst:491 msgid "" -"The filename of the source code for this frame. Equivalent to accessing :" -"attr:`f.f_code.co_filename ` on a :ref:`frame object " -"` *f*." +"The filename of the source code for this frame. Equivalent to " +"accessing :attr:`f.f_code.co_filename ` on " +"a :ref:`frame object ` *f*." msgstr "" #: library/traceback.rst:497 @@ -565,8 +566,8 @@ msgstr "" #: library/traceback.rst:501 msgid "" -"Equivalent to accessing :attr:`f.f_code.co_name ` on a :" -"ref:`frame object ` *f*." +"Equivalent to accessing :attr:`f.f_code.co_name ` on " +"a :ref:`frame object ` *f*." msgstr "" #: library/traceback.rst:506 @@ -583,8 +584,8 @@ msgstr "" 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. ::" +"more complete implementation of the interpreter loop, refer to " +"the :mod:`code` module. ::" msgstr "" #: library/traceback.rst:520 @@ -672,8 +673,8 @@ msgid "" "IndexError: tuple index out of range\n" "*** format_exception:\n" "['Traceback (most recent call last):\\n',\n" -" ' File \"\", line 10, in \\n " -"lumberjack()\\n',\n" +" ' File \"\", line 10, in \\n lumberjack()" +"\\n',\n" " ' File \"\", line 4, in lumberjack\\n " "bright_side_of_life()\\n',\n" " ' File \"\", line 7, in bright_side_of_life\\n " @@ -684,8 +685,8 @@ msgid "" " , line 4 in lumberjack>,\n" " , line 7 in bright_side_of_life>]\n" "*** format_tb:\n" -"[' File \"\", line 10, in \\n " -"lumberjack()\\n',\n" +"[' File \"\", line 10, in \\n lumberjack()" +"\\n',\n" " ' File \"\", line 4, in lumberjack\\n " "bright_side_of_life()\\n',\n" " ' File \"\", line 7, in bright_side_of_life\\n " @@ -721,10 +722,10 @@ msgid "" " ('', 3, 'another_function', 'lumberstack()'),\n" " ('', 7, 'lumberstack', 'print(repr(traceback.extract_stack()))')]\n" "[' File \"\", line 10, in \\n another_function()\\n',\n" -" ' File \"\", line 3, in another_function\\n " -"lumberstack()\\n',\n" -" ' File \"\", line 8, in lumberstack\\n print(repr(traceback." -"format_stack()))\\n']" +" ' File \"\", line 3, in another_function\\n lumberstack()" +"\\n',\n" +" ' File \"\", line 8, in lumberstack\\n " +"print(repr(traceback.format_stack()))\\n']" msgstr "" #: library/traceback.rst:639 @@ -788,8 +789,8 @@ msgid "" "IndexError: tuple index out of range\n" "\n" ">>> # capture_locals adds local variables in frames\n" -">>> TracebackException.from_exception(exc, limit=-2, capture_locals=True)." -"print()\n" +">>> TracebackException.from_exception(exc, limit=-2, " +"capture_locals=True).print()\n" "Traceback (most recent call last):\n" " File \"\", line 6, in lumberjack\n" " bright_side_of_life()\n" diff --git a/library/tracemalloc.po b/library/tracemalloc.po index 67bea5764..9c57290c1 100644 --- a/library/tracemalloc.po +++ b/library/tracemalloc.po @@ -56,9 +56,9 @@ msgstr "" #: 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." +"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 "" #: library/tracemalloc.rst:34 @@ -182,9 +182,9 @@ msgstr "" msgid "" "We can see that Python has loaded ``8173 KiB`` of module data (bytecode and " "constants), and that this is ``4428 KiB`` 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." +"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 "" #: library/tracemalloc.rst:115 @@ -421,9 +421,10 @@ msgstr "" #: library/tracemalloc.rst:309 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." +"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 "" #: library/tracemalloc.rst:314 @@ -446,8 +447,8 @@ msgstr "" #: library/tracemalloc.rst:329 msgid "" -"Get the current size and peak size of memory blocks traced by the :mod:" -"`tracemalloc` module as a tuple: ``(current: int, peak: int)``." +"Get the current size and peak size of memory blocks traced by " +"the :mod:`tracemalloc` module as a tuple: ``(current: int, peak: int)``." msgstr "" #: library/tracemalloc.rst:335 @@ -465,9 +466,9 @@ msgstr "" #: library/tracemalloc.rst:341 msgid "" "This function only modifies the recorded peak size, and does not modify or " -"clear any traces, unlike :func:`clear_traces`. Snapshots taken with :func:" -"`take_snapshot` before a call to :func:`reset_peak` can be meaningfully " -"compared to snapshots taken after the call." +"clear any traces, unlike :func:`clear_traces`. Snapshots taken " +"with :func:`take_snapshot` before a call to :func:`reset_peak` can be " +"meaningfully compared to snapshots taken after the call." msgstr "" #: library/tracemalloc.rst:346 @@ -507,15 +508,15 @@ msgstr "" #: library/tracemalloc.rst:376 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." +"by ``'traceback'`` or to compute cumulative statistics: see " +"the :meth:`Snapshot.compare_to` and :meth:`Snapshot.statistics` methods." msgstr "" #: library/tracemalloc.rst:380 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." +"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 "" #: library/tracemalloc.rst:384 @@ -558,8 +559,8 @@ msgstr "" #: library/tracemalloc.rst:410 msgid "" -"The snapshot does not include memory blocks allocated before the :mod:" -"`tracemalloc` module started to trace memory allocations." +"The snapshot does not include memory blocks allocated before " +"the :mod:`tracemalloc` module started to trace memory allocations." msgstr "" #: library/tracemalloc.rst:413 @@ -622,14 +623,14 @@ msgstr "" #: library/tracemalloc.rst:457 msgid "" -"``Filter(True, subprocess.__file__)`` only includes traces of the :mod:" -"`subprocess` module" +"``Filter(True, subprocess.__file__)`` only includes traces of " +"the :mod:`subprocess` module" msgstr "" #: library/tracemalloc.rst:459 msgid "" -"``Filter(False, tracemalloc.__file__)`` excludes traces of the :mod:" -"`tracemalloc` module" +"``Filter(False, tracemalloc.__file__)`` excludes traces of " +"the :mod:`tracemalloc` module" msgstr "" #: library/tracemalloc.rst:461 @@ -657,15 +658,15 @@ msgstr "" #: library/tracemalloc.rst:480 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`." +"a file with a name matching :attr:`filename_pattern` at line " +"number :attr:`lineno`." msgstr "" #: library/tracemalloc.rst:484 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`." +"file with a name matching :attr:`filename_pattern` at line " +"number :attr:`lineno`." msgstr "" #: library/tracemalloc.rst:490 @@ -686,9 +687,9 @@ msgstr "" #: library/tracemalloc.rst:502 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." +"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 "" #: library/tracemalloc.rst:508 @@ -737,10 +738,10 @@ msgstr "" #: library/tracemalloc.rst:542 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`." +"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 "" #: library/tracemalloc.rst:550 @@ -826,8 +827,9 @@ msgstr "" #: library/tracemalloc.rst:595 msgid "" -"The result is sorted from the biggest to the smallest by: :attr:`Statistic." -"size`, :attr:`Statistic.count` and then by :attr:`Statistic.traceback`." +"The result is sorted from the biggest to the smallest " +"by: :attr:`Statistic.size`, :attr:`Statistic.count` and then " +"by :attr:`Statistic.traceback`." msgstr "" #: library/tracemalloc.rst:602 @@ -884,8 +886,8 @@ msgstr "" #: library/tracemalloc.rst:644 msgid "" -"Statistic difference on memory allocations between an old and a new :class:" -"`Snapshot` instance." +"Statistic difference on memory allocations between an old and a " +"new :class:`Snapshot` instance." msgstr "" #: library/tracemalloc.rst:647 @@ -963,11 +965,11 @@ msgstr "" #: library/tracemalloc.rst:720 msgid "" -"When a snapshot is taken, tracebacks of traces are limited to :func:" -"`get_traceback_limit` frames. See the :func:`take_snapshot` function. The " -"original number of frames of the traceback is stored in the :attr:`Traceback." -"total_nframe` attribute. That allows to know if a traceback has been " -"truncated by the traceback limit." +"When a snapshot is taken, tracebacks of traces are limited " +"to :func:`get_traceback_limit` frames. See the :func:`take_snapshot` " +"function. The original number of frames of the traceback is stored in " +"the :attr:`Traceback.total_nframe` attribute. That allows to know if a " +"traceback has been truncated by the traceback limit." msgstr "" #: library/tracemalloc.rst:726 @@ -1004,8 +1006,8 @@ msgstr "" #: library/tracemalloc.rst:750 msgid "" -"Similar to the :func:`traceback.format_tb` function, except that :meth:`." -"format` does not include newlines." +"Similar to the :func:`traceback.format_tb` function, except " +"that :meth:`.format` does not include newlines." msgstr "" #: library/tracemalloc.rst:753 diff --git a/library/tty.po b/library/tty.po index 42a7962bc..0a80a3c31 100644 --- a/library/tty.po +++ b/library/tty.po @@ -70,9 +70,9 @@ msgstr "" #: library/tty.rst:50 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`. The return value of :func:`termios.tcgetattr` is saved before " -"setting *fd* to raw mode; this value is returned." +"defaults to :const:`termios.TCSAFLUSH`, and is passed " +"to :func:`termios.tcsetattr`. The return value of :func:`termios.tcgetattr` " +"is saved before setting *fd* to raw mode; this value is returned." msgstr "" #: library/tty.rst:69 @@ -83,9 +83,9 @@ msgstr "" #: library/tty.rst:61 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`. The return value of :func:`termios.tcgetattr` is saved before " -"setting *fd* to cbreak mode; this value is returned." +"defaults to :const:`termios.TCSAFLUSH`, and is passed " +"to :func:`termios.tcsetattr`. The return value of :func:`termios.tcgetattr` " +"is saved before setting *fd* to cbreak mode; this value is returned." msgstr "" #: library/tty.rst:66 diff --git a/library/turtle.po b/library/turtle.po index 47d623b67..96fb40004 100644 --- a/library/turtle.po +++ b/library/turtle.po @@ -288,8 +288,8 @@ msgstr "" #: library/turtle.rst:186 msgid "" "The turtle module makes this possible by exposing all its basic " -"functionality as functions, available with ``from turtle import *``. The :" -"ref:`turtle graphics tutorial ` covers this approach." +"functionality as functions, available with ``from turtle import *``. " +"The :ref:`turtle graphics tutorial ` covers this approach." msgstr "" #: library/turtle.rst:190 @@ -983,8 +983,8 @@ msgstr "" #: library/turtle.rst:537 msgid "" -"If *y* is ``None``, *x* must be a pair of coordinates or a :class:`Vec2D` (e." -"g. as returned by :func:`pos`)." +"If *y* is ``None``, *x* must be a pair of coordinates or a :class:`Vec2D` " +"(e.g. as returned by :func:`pos`)." msgstr "" #: library/turtle.rst:540 @@ -1403,8 +1403,8 @@ msgstr "" #: library/turtle.rst:930 msgid "" -"Return the turtle's current heading (value depends on the turtle mode, see :" -"func:`mode`)." +"Return the turtle's current heading (value depends on the turtle mode, " +"see :func:`mode`)." msgstr "" #: library/turtle.rst:933 @@ -1463,8 +1463,8 @@ msgstr "" #: library/turtle.rst:994 msgid "" -"Set the angle measurement units to radians. Equivalent to ``degrees(2*math." -"pi)``." +"Set the angle measurement units to radians. Equivalent to " +"``degrees(2*math.pi)``." msgstr "" #: library/turtle.rst:997 @@ -1757,8 +1757,8 @@ msgstr "" #: library/turtle.rst:1213 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`." +"specification strings or tuples as returned by :func:`pencolor` " +"and :func:`fillcolor`." msgstr "" #: library/turtle.rst:1217 @@ -1924,8 +1924,8 @@ msgid "" "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`." +"To learn about how to deal with shapes see Screen " +"method :func:`register_shape`." msgstr "" #: library/turtle.rst:1390 @@ -2312,8 +2312,8 @@ msgstr "" #: library/turtle.rst:1768 msgid "" -"Add as many components to this object as desired, using the :meth:`~Shape." -"addcomponent` method." +"Add as many components to this object as desired, using " +"the :meth:`~Shape.addcomponent` method." msgstr "" #: library/turtle.rst:1771 @@ -2884,16 +2884,16 @@ msgstr "" 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." +"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 "" #: library/turtle.rst:2288 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." +"are stored in the configuration dictionary and can be changed via " +"a :file:`turtle.cfg` file." msgstr "" #: library/turtle.rst:2292 @@ -2946,8 +2946,8 @@ msgstr "" #: library/turtle.rst:2332 msgid "" -"a :class:`!tkinter.Canvas`, a :class:`ScrolledCanvas` or a :class:" -"`TurtleScreen`" +"a :class:`!tkinter.Canvas`, a :class:`ScrolledCanvas` or " +"a :class:`TurtleScreen`" msgstr "" #: library/turtle.rst:2335 @@ -2958,8 +2958,9 @@ msgstr "" #: library/turtle.rst:2341 msgid "" -"Subclass of RawTurtle, has the same interface but draws on a default :class:" -"`Screen` object created automatically when needed for the first time." +"Subclass of RawTurtle, has the same interface but draws on a " +"default :class:`Screen` object created automatically when needed for the " +"first time." msgstr "" #: library/turtle.rst:2347 @@ -3029,8 +3030,8 @@ msgstr "" #: library/turtle.rst:2378 msgid "" -"``None`` (a compound shape has to be constructed using the :meth:" -"`addcomponent` method)" +"``None`` (a compound shape has to be constructed using " +"the :meth:`addcomponent` method)" msgstr "" #: library/turtle.rst:2384 @@ -3117,17 +3118,18 @@ msgstr "" msgid "" "``Turtle`` is a subclass of :class:`RawTurtle`, which *doesn't* " "automatically create a drawing surface - a *canvas* will need to be provided " -"or created for it. The *canvas* can be a :class:`!tkinter.Canvas`, :class:" -"`ScrolledCanvas` or :class:`TurtleScreen`." +"or created for it. The *canvas* can be a :class:`!" +"tkinter.Canvas`, :class:`ScrolledCanvas` or :class:`TurtleScreen`." msgstr "" #: library/turtle.rst:2435 msgid "" -":class:`TurtleScreen` is the basic drawing surface for a turtle. :class:" -"`Screen` is a subclass of ``TurtleScreen``, and includes :ref:`some " -"additional methods ` for managing its appearance (including " -"size and title) and behaviour. ``TurtleScreen``'s constructor needs a :class:" -"`!tkinter.Canvas` or a :class:`ScrolledCanvas` as an argument." +":class:`TurtleScreen` is the basic drawing surface for a " +"turtle. :class:`Screen` is a subclass of ``TurtleScreen``, and " +"includes :ref:`some additional methods ` for managing its " +"appearance (including size and title) and behaviour. ``TurtleScreen``'s " +"constructor needs a :class:`!tkinter.Canvas` or a :class:`ScrolledCanvas` as " +"an argument." msgstr "" #: library/turtle.rst:2442 @@ -3352,8 +3354,8 @@ msgstr "" #: library/turtle.rst:2603 msgid "" -"Line 5 and 6 correspond to the arguments of the method :func:`Screen." -"screensize `." +"Line 5 and 6 correspond to the arguments of the " +"method :func:`Screen.screensize `." msgstr "" #: library/turtle.rst:2605 @@ -3377,9 +3379,10 @@ msgstr "" #: library/turtle.rst:2612 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`)." +"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 "" #: library/turtle.rst:2615 @@ -3705,9 +3708,9 @@ msgstr "" #: library/turtle.rst:2740 msgid "" -"The method :func:`!Turtle.fill` has been eliminated. The behaviour of :func:" -"`begin_fill` and :func:`end_fill` have changed slightly: now every filling " -"process must be completed with an ``end_fill()`` call." +"The method :func:`!Turtle.fill` has been eliminated. The behaviour " +"of :func:`begin_fill` and :func:`end_fill` have changed slightly: now every " +"filling process must be completed with an ``end_fill()`` call." msgstr "" #: library/turtle.rst:2745 @@ -3724,11 +3727,11 @@ msgstr "" #: library/turtle.rst:2753 msgid "" -"The :class:`Turtle` methods :func:`shearfactor`, :func:`shapetransform` and :" -"func:`get_shapepoly` have been added. Thus the full range of regular linear " -"transforms is now available for transforming turtle shapes. :func:" -"`tiltangle` has been enhanced in functionality: it now can be used to get or " -"set the tilt angle. :func:`settiltangle` has been deprecated." +"The :class:`Turtle` methods :func:`shearfactor`, :func:`shapetransform` " +"and :func:`get_shapepoly` have been added. Thus the full range of regular " +"linear transforms is now available for transforming turtle " +"shapes. :func:`tiltangle` has been enhanced in functionality: it now can be " +"used to get or set the tilt angle. :func:`settiltangle` has been deprecated." msgstr "" #: library/turtle.rst:2760 @@ -3747,9 +3750,9 @@ msgstr "" #: library/turtle.rst:2768 msgid "" -"Two input methods have been added: :func:`Screen.textinput ` and :" -"func:`Screen.numinput `. These pop up input dialogs and return " -"strings and numbers respectively." +"Two input methods have been added: :func:`Screen.textinput ` " +"and :func:`Screen.numinput `. These pop up input dialogs and " +"return strings and numbers respectively." msgstr "" #: library/turtle.rst:2772 diff --git a/library/types.po b/library/types.po index e64e8a303..4bafdce11 100644 --- a/library/types.po +++ b/library/types.po @@ -33,8 +33,8 @@ msgstr "" #: 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." +"Python interpreter, but not exposed as builtins like :class:`int` " +"or :class:`str` are." msgstr "" #: library/types.rst:18 @@ -119,12 +119,12 @@ msgstr "" #: library/types.rst:76 msgid "" -"This function looks for items in *bases* that are not instances of :class:" -"`type`, and returns a tuple where each such object that has an :meth:" -"`~object.__mro_entries__` method is replaced with an unpacked result of " -"calling this method. If a *bases* item is an instance of :class:`type`, or " -"it doesn't have an :meth:`!__mro_entries__` method, then it is included in " -"the return tuple unchanged." +"This function looks for items in *bases* that are not instances " +"of :class:`type`, and returns a tuple where each such object that has " +"an :meth:`~object.__mro_entries__` method is replaced with an unpacked " +"result of calling this method. If a *bases* item is an instance " +"of :class:`type`, or it doesn't have an :meth:`!__mro_entries__` method, " +"then it is included in the return tuple unchanged." msgstr "" #: library/types.rst:87 @@ -212,8 +212,8 @@ msgstr "" #: library/types.rst:156 msgid "" -"The type of user-defined functions and functions created by :keyword:" -"`lambda` expressions." +"The type of user-defined functions and functions created " +"by :keyword:`lambda` expressions." msgstr "" #: library/types.rst:159 @@ -248,8 +248,8 @@ msgstr "" #: library/types.rst:191 msgid "" -"The type of :ref:`code objects ` such as returned by :func:" -"`compile`." +"The type of :ref:`code objects ` such as returned " +"by :func:`compile`." msgstr "" #: library/types.rst:193 @@ -285,8 +285,8 @@ msgstr "" #: library/types.rst:222 msgid "" -"The type of methods of some built-in data types and base classes such as :" -"meth:`object.__init__` or :meth:`object.__lt__`." +"The type of methods of some built-in data types and base classes such " +"as :meth:`object.__init__` or :meth:`object.__lt__`." msgstr "" #: library/types.rst:230 @@ -392,8 +392,8 @@ msgstr "" #: library/types.rst:319 msgid "" -"The type of traceback objects such as found in ``sys.exception()." -"__traceback__``." +"The type of traceback objects such as found in " +"``sys.exception().__traceback__``." msgstr "" #: library/types.rst:321 @@ -405,8 +405,8 @@ msgstr "" #: library/types.rst:328 msgid "" -"The type of :ref:`frame objects ` such as found in :attr:`tb." -"tb_frame ` if ``tb`` is a traceback object." +"The type of :ref:`frame objects ` such as found " +"in :attr:`tb.tb_frame ` if ``tb`` is a traceback object." msgstr "" #: library/types.rst:334 @@ -461,8 +461,8 @@ msgstr "" #: library/types.rst:377 msgid "" -"Return the item of the underlying mapping with key *key*. Raises a :exc:" -"`KeyError` if *key* is not in the underlying mapping." +"Return the item of the underlying mapping with key *key*. Raises " +"a :exc:`KeyError` if *key* is not in the underlying mapping." msgstr "" #: library/types.rst:382 @@ -583,8 +583,8 @@ msgstr "" #: library/types.rst:482 msgid "" -"This function transforms a :term:`generator` function into a :term:" -"`coroutine function` which returns a generator-based coroutine. The " +"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:`~object.__await__` " diff --git a/library/typing.po b/library/typing.po index 96237b95c..59ef29aa5 100644 --- a/library/typing.po +++ b/library/typing.po @@ -49,8 +49,8 @@ msgstr "" msgid "" "The function ``surface_area_of_cube`` takes an argument expected to be an " "instance of :class:`float`, as indicated by the :term:`type hint` " -"``edge_length: float``. The function is expected to return an instance of :" -"class:`str`, as indicated by the ``-> str`` hint." +"``edge_length: float``. The function is expected to return an instance " +"of :class:`str`, as indicated by the ``-> str`` hint." msgstr "" #: library/typing.rst:38 @@ -62,9 +62,9 @@ msgstr "" #: library/typing.rst:42 msgid "" -"New features are frequently added to the ``typing`` module. The :pypi:" -"`typing_extensions` package provides backports of these new features to " -"older versions of Python." +"New features are frequently added to the ``typing`` module. " +"The :pypi:`typing_extensions` package provides backports of these new " +"features to older versions of Python." msgstr "" #: library/typing.rst:48 @@ -79,8 +79,8 @@ msgstr "" #: library/typing.rst:51 msgid "" -"\"Type System Reference\" section of `the mypy docs `_" +"\"Type System Reference\" section of `the mypy docs `_" msgstr "" #: library/typing.rst:52 @@ -108,8 +108,8 @@ msgstr "" #: library/typing.rst:66 msgid "" "The canonical, up-to-date specification of the Python type system can be " -"found at `\"Specification for the Python type system\" `_." +"found at `\"Specification for the Python type system\" `_." msgstr "" #: library/typing.rst:72 @@ -320,10 +320,11 @@ msgstr "" #: library/typing.rst:210 msgid "" -"Functions -- or other :term:`callable` objects -- can be annotated using :" -"class:`collections.abc.Callable` or deprecated :data:`typing.Callable`. " -"``Callable[[int], str]`` signifies a function that takes a single parameter " -"of type :class:`int` and returns a :class:`str`." +"Functions -- or other :term:`callable` objects -- can be annotated " +"using :class:`collections.abc.Callable` or " +"deprecated :data:`typing.Callable`. ``Callable[[int], str]`` signifies a " +"function that takes a single parameter of type :class:`int` and returns " +"a :class:`str`." msgstr "" #: library/typing.rst:2916 library/typing.rst:3064 @@ -376,8 +377,8 @@ msgid "" "``Callable`` cannot express complex signatures such as functions that take a " "variadic number of arguments, :ref:`overloaded functions `, or " "functions that have keyword-only parameters. However, these signatures can " -"be expressed by defining a :class:`Protocol` class with a :meth:`~object." -"__call__` method:" +"be expressed by defining a :class:`Protocol` class with " +"a :meth:`~object.__call__` method:" msgstr "" #: library/typing.rst:256 @@ -417,8 +418,8 @@ msgstr "" #: library/typing.rst:3543 msgid "" -"``Callable`` now supports :class:`ParamSpec` and :data:`Concatenate`. See :" -"pep:`612` for more details." +"``Callable`` now supports :class:`ParamSpec` and :data:`Concatenate`. " +"See :pep:`612` for more details." msgstr "" #: library/typing.rst:290 @@ -515,17 +516,18 @@ msgstr "" #: library/typing.rst:356 msgid "" ":class:`list` only accepts one type argument, so a type checker would emit " -"an error on the ``y`` assignment above. Similarly, :class:`~collections.abc." -"Mapping` only accepts two type arguments: the first indicates the type of " -"the keys, and the second indicates the type of the values." +"an error on the ``y`` assignment above. " +"Similarly, :class:`~collections.abc.Mapping` only accepts two type " +"arguments: the first indicates the type of the keys, and the second " +"indicates the type of the values." msgstr "" #: library/typing.rst:362 msgid "" "Unlike most other Python containers, however, it is common in idiomatic " "Python code for tuples to have elements which are not all of the same type. " -"For this reason, tuples are special-cased in Python's typing system. :class:" -"`tuple` accepts *any number* of type arguments::" +"For this reason, tuples are special-cased in Python's typing " +"system. :class:`tuple` accepts *any number* of type arguments::" msgstr "" #: library/typing.rst:367 @@ -578,9 +580,10 @@ msgstr "" #: library/typing.rst:403 msgid "" "A variable annotated with ``C`` may accept a value of type ``C``. In " -"contrast, a variable annotated with ``type[C]`` (or deprecated :class:" -"`typing.Type[C] `) may accept values that are classes themselves -- " -"specifically, it will accept the *class object* of ``C``. For example::" +"contrast, a variable annotated with ``type[C]`` (or " +"deprecated :class:`typing.Type[C] `) may accept values that are " +"classes themselves -- specifically, it will accept the *class object* of " +"``C``. For example::" msgstr "" #: library/typing.rst:409 @@ -615,8 +618,9 @@ msgstr "" #: library/typing.rst:429 msgid "" -"The only legal parameters for :class:`type` are classes, :data:`Any`, :ref:" -"`type variables `, and unions of any of these types. For example::" +"The only legal parameters for :class:`type` are " +"classes, :data:`Any`, :ref:`type variables `, and unions of any of " +"these types. For example::" msgstr "" #: library/typing.rst:433 @@ -632,8 +636,8 @@ msgstr "" #: library/typing.rst:441 msgid "" -"``type[Any]`` is equivalent to :class:`type`, which is the root of Python's :" -"ref:`metaclass hierarchy `." +"``type[Any]`` is equivalent to :class:`type`, which is the root of " +"Python's :ref:`metaclass hierarchy `." msgstr "" #: library/typing.rst:448 @@ -642,9 +646,9 @@ msgstr "" #: library/typing.rst:450 msgid "" -"A generator can be annotated using the generic type :class:" -"`Generator[YieldType, SendType, ReturnType] `. " -"For example::" +"A generator can be annotated using the generic " +"type :class:`Generator[YieldType, SendType, ReturnType] " +"`. For example::" msgstr "" #: library/typing.rst:454 @@ -708,9 +712,9 @@ msgstr "" #: library/typing.rst:489 msgid "" -"As in the synchronous case, :class:`AsyncIterable[YieldType] ` and :class:`AsyncIterator[YieldType] ` are available as well::" +"As in the synchronous case, :class:`AsyncIterable[YieldType] " +"` and :class:`AsyncIterator[YieldType] " +"` are available as well::" msgstr "" #: library/typing.rst:494 @@ -777,8 +781,8 @@ msgstr "" #: library/typing.rst:542 msgid "" "Generic classes implicitly inherit from :class:`Generic`. For compatibility " -"with Python 3.11 and lower, it is also possible to inherit explicitly from :" -"class:`Generic` to indicate a generic class::" +"with Python 3.11 and lower, it is also possible to inherit explicitly " +"from :class:`Generic` to indicate a generic class::" msgstr "" #: library/typing.rst:546 @@ -808,8 +812,8 @@ msgstr "" #: library/typing.rst:562 msgid "" -"A generic type can have any number of type variables. All varieties of :" -"class:`TypeVar` are permissible as parameters for a generic type::" +"A generic type can have any number of type variables. All varieties " +"of :class:`TypeVar` are permissible as parameters for a generic type::" msgstr "" #: library/typing.rst:565 @@ -1000,16 +1004,16 @@ msgstr "" #: library/typing.rst:688 msgid "" -":class:`Generic` can now be parameterized over parameter expressions. See :" -"class:`ParamSpec` and :pep:`612` for more details." +":class:`Generic` can now be parameterized over parameter expressions. " +"See :class:`ParamSpec` and :pep:`612` for more details." msgstr "" #: library/typing.rst:692 msgid "" "A user-defined generic class can 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 :" -"term:`hashable` and comparable for equality." +"parameterizing generics is cached, and most types in the typing module " +"are :term:`hashable` and comparable for equality." msgstr "" #: library/typing.rst:699 @@ -1049,11 +1053,11 @@ msgstr "" #: library/typing.rst:723 msgid "" -"Notice that no type checking 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!" +"Notice that no type checking 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 "" #: library/typing.rst:729 @@ -1137,11 +1141,11 @@ msgstr "" #: library/typing.rst:783 msgid "" -"This requirement previously also applied to abstract base classes, such as :" -"class:`~collections.abc.Iterable`. The problem with this approach is that a " -"class had to be explicitly marked to support them, which is unpythonic and " -"unlike what one would normally do in idiomatic dynamically typed Python " -"code. For example, this conforms to :pep:`484`::" +"This requirement previously also applied to abstract base classes, such " +"as :class:`~collections.abc.Iterable`. The problem with this approach is " +"that a class had to be explicitly marked to support them, which is " +"unpythonic and unlike what one would normally do in idiomatic dynamically " +"typed Python code. For example, this conforms to :pep:`484`::" msgstr "" #: library/typing.rst:789 @@ -1261,9 +1265,10 @@ msgstr "" #: library/typing.rst:862 msgid "" -"Note that, despite its name, ``AnyStr`` has nothing to do with the :class:" -"`Any` type, nor does it mean \"any string\". In particular, ``AnyStr`` and " -"``str | bytes`` are different from each other and have different use cases::" +"Note that, despite its name, ``AnyStr`` has nothing to do with " +"the :class:`Any` type, nor does it mean \"any string\". In particular, " +"``AnyStr`` and ``str | bytes`` are different from each other and have " +"different use cases::" msgstr "" #: library/typing.rst:867 @@ -1324,14 +1329,14 @@ msgstr "" #: library/typing.rst:915 msgid "" -":data:`!Never` and :data:`!NoReturn` represent the `bottom type `_, a type that has no members." +":data:`!Never` and :data:`!NoReturn` represent the `bottom type `_, a type that has no members." msgstr "" #: library/typing.rst:919 msgid "" -"They can be used to indicate that a function never returns, such as :func:" -"`sys.exit`::" +"They can be used to indicate that a function never returns, such " +"as :func:`sys.exit`::" msgstr "" #: library/typing.rst:922 @@ -1507,11 +1512,11 @@ msgstr "" msgid "" ":data:`TypeAlias` is deprecated in favor of the :keyword:`type` statement, " "which creates instances of :class:`TypeAliasType` and which natively " -"supports forward references. Note that while :data:`TypeAlias` and :class:" -"`TypeAliasType` serve similar purposes and have similar names, they are " -"distinct and the latter is not the type of the former. Removal of :data:" -"`TypeAlias` is not currently planned, but users are encouraged to migrate " -"to :keyword:`type` statements." +"supports forward references. Note that while :data:`TypeAlias` " +"and :class:`TypeAliasType` serve similar purposes and have similar names, " +"they are distinct and the latter is not the type of the former. Removal " +"of :data:`TypeAlias` is not currently planned, but users are encouraged to " +"migrate to :keyword:`type` statements." msgstr "" #: library/typing.rst:1059 @@ -1644,13 +1649,13 @@ msgstr "" #: library/typing.rst:1135 msgid "" -"For example, to annotate a decorator ``with_lock`` which provides a :class:" -"`threading.Lock` to the decorated function, ``Concatenate`` can be used to " -"indicate that ``with_lock`` expects a callable which takes in a ``Lock`` as " -"the first argument, and returns a callable with a different type signature. " -"In this case, the :class:`ParamSpec` indicates that the returned callable's " -"parameter types are dependent on the parameter types of the callable being " -"passed in::" +"For example, to annotate a decorator ``with_lock`` which provides " +"a :class:`threading.Lock` to the decorated function, ``Concatenate`` can be " +"used to indicate that ``with_lock`` expects a callable which takes in a " +"``Lock`` as the first argument, and returns a callable with a different type " +"signature. In this case, the :class:`ParamSpec` indicates that the returned " +"callable's parameter types are dependent on the parameter types of the " +"callable being passed in::" msgstr "" #: library/typing.rst:1143 @@ -1757,10 +1762,11 @@ msgstr "" #: library/typing.rst:1222 msgid "" -":data:`ClassVar` is not a class itself, and should not be used with :func:" -"`isinstance` or :func:`issubclass`. :data:`ClassVar` does not change Python " -"runtime behavior, but it can be used by third-party type checkers. For " -"example, a type checker might flag the following code as an error::" +":data:`ClassVar` is not a class itself, and should not be used " +"with :func:`isinstance` or :func:`issubclass`. :data:`ClassVar` does not " +"change Python runtime behavior, but it can be used by third-party type " +"checkers. For example, a type checker might flag the following code as an " +"error::" msgstr "" #: library/typing.rst:1228 @@ -2742,15 +2748,15 @@ msgstr "" #: library/typing.rst:1918 msgid "" -"Since ``ParamSpec`` captures both positional and keyword parameters, ``P." -"args`` and ``P.kwargs`` can be used to split a ``ParamSpec`` into its " +"Since ``ParamSpec`` captures both positional and keyword parameters, " +"``P.args`` and ``P.kwargs`` can be used to split a ``ParamSpec`` into its " "components. ``P.args`` represents the tuple of positional parameters in a " "given call and should only be used to annotate ``*args``. ``P.kwargs`` " "represents the mapping of keyword parameters to their values in a given " "call, and should be only be used to annotate ``**kwargs``. Both attributes " "require the annotated parameter to be in scope. At runtime, ``P.args`` and " -"``P.kwargs`` are instances respectively of :class:`ParamSpecArgs` and :class:" -"`ParamSpecKwargs`." +"``P.kwargs`` are instances respectively of :class:`ParamSpecArgs` " +"and :class:`ParamSpecKwargs`." msgstr "" #: library/typing.rst:1930 @@ -2761,9 +2767,9 @@ msgstr "" msgid "" "Parameter specification variables created with ``covariant=True`` or " "``contravariant=True`` can be used to declare covariant or contravariant " -"generic types. The ``bound`` argument is also accepted, similar to :class:" -"`TypeVar`. However the actual semantics of these keywords are yet to be " -"decided." +"generic types. The ``bound`` argument is also accepted, similar " +"to :class:`TypeVar`. However the actual semantics of these keywords are yet " +"to be decided." msgstr "" #: library/typing.rst:1942 @@ -2784,10 +2790,11 @@ msgstr "" #: library/typing.rst:1958 msgid "" -"Arguments and keyword arguments attributes of a :class:`ParamSpec`. The ``P." -"args`` attribute of a ``ParamSpec`` is an instance of ``ParamSpecArgs``, and " -"``P.kwargs`` is an instance of ``ParamSpecKwargs``. They are intended for " -"runtime introspection and have no special meaning to static type checkers." +"Arguments and keyword arguments attributes of a :class:`ParamSpec`. The " +"``P.args`` attribute of a ``ParamSpec`` is an instance of ``ParamSpecArgs``, " +"and ``P.kwargs`` is an instance of ``ParamSpecKwargs``. They are intended " +"for runtime introspection and have no special meaning to static type " +"checkers." msgstr "" #: library/typing.rst:1963 @@ -3074,10 +3081,10 @@ msgstr "" #: library/typing.rst:2177 msgid "" -"See :pep:`544` for more details. Protocol classes decorated with :func:" -"`runtime_checkable` (described later) act as simple-minded runtime protocols " -"that check only the presence of given attributes, ignoring their type " -"signatures." +"See :pep:`544` for more details. Protocol classes decorated " +"with :func:`runtime_checkable` (described later) act as simple-minded " +"runtime protocols that check only the presence of given attributes, ignoring " +"their type signatures." msgstr "" #: library/typing.rst:2182 @@ -3115,8 +3122,8 @@ msgid "" "Such a protocol can be used with :func:`isinstance` and :func:`issubclass`. " "This raises :exc:`TypeError` when applied to a non-protocol class. This " "allows a simple-minded structural check, very similar to \"one trick " -"ponies\" in :mod:`collections.abc` such as :class:`~collections.abc." -"Iterable`. For example::" +"ponies\" in :mod:`collections.abc` such " +"as :class:`~collections.abc.Iterable`. For example::" msgstr "" #: library/typing.rst:2208 @@ -3138,12 +3145,12 @@ msgstr "" #: library/typing.rst:2223 msgid "" ":func:`!runtime_checkable` will check only the presence of the required " -"methods or attributes, not their type signatures or types. For example, :" -"class:`ssl.SSLObject` is a class, therefore it passes an :func:`issubclass` " -"check against :ref:`Callable `. However, the ``ssl." -"SSLObject.__init__`` method exists only to raise a :exc:`TypeError` with a " -"more informative message, therefore making it impossible to call " -"(instantiate) :class:`ssl.SSLObject`." +"methods or attributes, not their type signatures or types. For " +"example, :class:`ssl.SSLObject` is a class, therefore it passes " +"an :func:`issubclass` check against :ref:`Callable `. " +"However, the ``ssl.SSLObject.__init__`` method exists only to raise " +"a :exc:`TypeError` with a more informative message, therefore making it " +"impossible to call (instantiate) :class:`ssl.SSLObject`." msgstr "" #: library/typing.rst:2234 @@ -3169,8 +3176,9 @@ msgid "" "The members of a runtime-checkable protocol are now considered \"frozen\" at " "runtime as soon as the class has been created. Monkey-patching attributes " "onto a runtime-checkable protocol will still work, but will have no impact " -"on :func:`isinstance` checks comparing objects to the protocol. See :ref:" -"`\"What's new in Python 3.12\" ` for more details." +"on :func:`isinstance` checks comparing objects to the protocol. " +"See :ref:`\"What's new in Python 3.12\" ` for more " +"details." msgstr "" #: library/typing.rst:2262 @@ -3391,9 +3399,10 @@ msgstr "" #: library/typing.rst:2400 msgid "" -"A ``TypedDict`` can be introspected via annotations dicts (see :ref:" -"`annotations-howto` for more information on annotations best practices), :" -"attr:`__total__`, :attr:`__required_keys__`, and :attr:`__optional_keys__`." +"A ``TypedDict`` can be introspected via annotations dicts " +"(see :ref:`annotations-howto` for more information on annotations best " +"practices), :attr:`__total__`, :attr:`__required_keys__`, " +"and :attr:`__optional_keys__`." msgstr "" #: library/typing.rst:2406 @@ -3428,8 +3437,8 @@ msgstr "" #: library/typing.rst:2435 msgid "" -"``Point2D.__required_keys__`` and ``Point2D.__optional_keys__`` return :" -"class:`frozenset` objects containing required and non-required keys, " +"``Point2D.__required_keys__`` and ``Point2D.__optional_keys__`` " +"return :class:`frozenset` objects containing required and non-required keys, " "respectively." msgstr "" @@ -3480,8 +3489,8 @@ msgstr "" #: library/typing.rst:2476 msgid "" -"Added support for marking individual keys as :data:`Required` or :data:" -"`NotRequired`. See :pep:`655`." +"Added support for marking individual keys as :data:`Required` " +"or :data:`NotRequired`. See :pep:`655`." msgstr "" #: library/typing.rst:2480 @@ -3670,9 +3679,9 @@ msgstr "" #: library/typing.rst:2621 msgid "" -"At runtime, this function prints the runtime type of its argument to :data:" -"`sys.stderr` and returns the argument unchanged (allowing the call to be " -"used within an expression)::" +"At runtime, this function prints the runtime type of its argument " +"to :data:`sys.stderr` and returns the argument unchanged (allowing the call " +"to be used within an expression)::" msgstr "" #: library/typing.rst:2625 @@ -3697,8 +3706,8 @@ msgstr "" #: library/typing.rst:2642 msgid "" -"Decorator to mark an object as providing :func:`dataclass `-like behavior." +"Decorator to mark an object as providing :func:`dataclass " +"`-like behavior." msgstr "" #: library/typing.rst:2645 @@ -3760,9 +3769,9 @@ msgstr "" #: library/typing.rst:2686 msgid "" "The ``CustomerModel`` classes defined above will be treated by type checkers " -"similarly to classes created with :func:`@dataclasses.dataclass `. For example, type checkers will assume these classes have " -"``__init__`` methods that accept ``id`` and ``name``." +"similarly to classes created with :func:`@dataclasses.dataclass " +"`. For example, type checkers will assume these " +"classes have ``__init__`` methods that accept ``id`` and ``name``." msgstr "" #: library/typing.rst:2692 @@ -3938,8 +3947,8 @@ msgid "" "only, since they will be overwritten by the non-``@overload``-decorated " "definition. The non-``@overload``-decorated definition, meanwhile, will be " "used at runtime but should be ignored by a type checker. At runtime, " -"calling an ``@overload``-decorated function directly will raise :exc:" -"`NotImplementedError`." +"calling an ``@overload``-decorated function directly will " +"raise :exc:`NotImplementedError`." msgstr "" #: library/typing.rst:2797 @@ -3970,8 +3979,8 @@ msgstr "" #: library/typing.rst:2816 msgid "" -"Overloaded functions can now be introspected at runtime using :func:" -"`get_overloads`." +"Overloaded functions can now be introspected at runtime " +"using :func:`get_overloads`." msgstr "" #: library/typing.rst:2823 @@ -4190,8 +4199,8 @@ msgstr "" #: library/typing.rst:2991 msgid "" "The function recursively replaces all occurrences of ``Annotated[T, ...]`` " -"with ``T``, unless *include_extras* is set to ``True`` (see :class:" -"`Annotated` for more information)." +"with ``T``, unless *include_extras* is set to ``True`` " +"(see :class:`Annotated` for more information)." msgstr "" #: library/typing.rst:2995 @@ -4203,8 +4212,8 @@ msgstr "" #: library/typing.rst:3000 msgid "" "If any forward references in the annotations of *obj* are not resolvable or " -"are not valid Python code, this function will raise an exception such as :" -"exc:`NameError`. For example, this can happen with imported :ref:`type " +"are not valid Python code, this function will raise an exception such " +"as :exc:`NameError`. For example, this can happen with imported :ref:`type " "aliases ` that include forward references, or with names " "imported under :data:`if TYPE_CHECKING `." msgstr "" @@ -4231,9 +4240,9 @@ msgstr "" #: library/typing.rst:3020 msgid "" "If ``X`` is a typing-module alias for a builtin or :mod:`collections` class, " -"it will be normalized to the original class. If ``X`` is an instance of :" -"class:`ParamSpecArgs` or :class:`ParamSpecKwargs`, return the underlying :" -"class:`ParamSpec`. Return ``None`` for unsupported objects." +"it will be normalized to the original class. If ``X`` is an instance " +"of :class:`ParamSpecArgs` or :class:`ParamSpecKwargs`, return the " +"underlying :class:`ParamSpec`. Return ``None`` for unsupported objects." msgstr "" #: library/typing.rst:3050 @@ -4396,8 +4405,8 @@ msgstr "" #: library/typing.rst:3166 msgid "" -":class:`builtins.dict ` now supports subscripting (``[]``). See :pep:" -"`585` and :ref:`types-genericalias`." +":class:`builtins.dict ` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3172 @@ -4407,15 +4416,15 @@ msgstr "" #: library/typing.rst:3174 msgid "" "Note that to annotate arguments, it is preferred to use an abstract " -"collection type such as :class:`~collections.abc.Sequence` or :class:" -"`~collections.abc.Iterable` rather than to use :class:`list` or :class:`!" -"typing.List`." +"collection type such as :class:`~collections.abc.Sequence` " +"or :class:`~collections.abc.Iterable` rather than to use :class:`list` " +"or :class:`!typing.List`." msgstr "" #: library/typing.rst:3179 msgid "" -":class:`builtins.list ` now supports subscripting (``[]``). See :pep:" -"`585` and :ref:`types-genericalias`." +":class:`builtins.list ` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3185 @@ -4425,14 +4434,14 @@ msgstr "" #: library/typing.rst:3187 msgid "" "Note that to annotate arguments, it is preferred to use an abstract " -"collection type such as :class:`collections.abc.Set` rather than to use :" -"class:`set` or :class:`typing.Set`." +"collection type such as :class:`collections.abc.Set` rather than to " +"use :class:`set` or :class:`typing.Set`." msgstr "" #: library/typing.rst:3191 msgid "" -":class:`builtins.set ` now supports subscripting (``[]``). See :pep:" -"`585` and :ref:`types-genericalias`." +":class:`builtins.set ` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3197 @@ -4451,14 +4460,14 @@ msgstr "" #: library/typing.rst:3208 msgid "" -":class:`tuple` and ``Tuple`` are special-cased in the type system; see :ref:" -"`annotating-tuples` for more details." +":class:`tuple` and ``Tuple`` are special-cased in the type system; " +"see :ref:`annotating-tuples` for more details." msgstr "" #: library/typing.rst:3211 msgid "" -":class:`builtins.tuple ` now supports subscripting (``[]``). See :pep:" -"`585` and :ref:`types-genericalias`." +":class:`builtins.tuple ` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3217 @@ -4473,8 +4482,8 @@ msgstr "" #: library/typing.rst:3224 msgid "" -":class:`builtins.type ` now supports subscripting (``[]``). See :pep:" -"`585` and :ref:`types-genericalias`." +":class:`builtins.type ` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3231 @@ -4487,8 +4496,8 @@ msgstr "" #: library/typing.rst:3239 msgid "" -":class:`collections.defaultdict` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.defaultdict` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3245 @@ -4497,8 +4506,8 @@ msgstr "" #: library/typing.rst:3249 msgid "" -":class:`collections.OrderedDict` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.OrderedDict` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3255 @@ -4507,8 +4516,8 @@ msgstr "" #: library/typing.rst:3259 msgid "" -":class:`collections.ChainMap` now supports subscripting (``[]``). See :pep:" -"`585` and :ref:`types-genericalias`." +":class:`collections.ChainMap` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3265 @@ -4517,8 +4526,8 @@ msgstr "" #: library/typing.rst:3269 msgid "" -":class:`collections.Counter` now supports subscripting (``[]``). See :pep:" -"`585` and :ref:`types-genericalias`." +":class:`collections.Counter` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3275 @@ -4527,8 +4536,8 @@ msgstr "" #: library/typing.rst:3279 msgid "" -":class:`collections.deque` now supports subscripting (``[]``). See :pep:" -"`585` and :ref:`types-genericalias`." +":class:`collections.deque` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3286 @@ -4549,8 +4558,8 @@ msgstr "" #: library/typing.rst:3298 msgid "" -"These types (and the corresponding functions) are generic over :data:" -"`AnyStr`. ``Pattern`` can be specialised as ``Pattern[str]`` or " +"These types (and the corresponding functions) are generic " +"over :data:`AnyStr`. ``Pattern`` can be specialised as ``Pattern[str]`` or " "``Pattern[bytes]``; ``Match`` can be specialised as ``Match[str]`` or " "``Match[bytes]``." msgstr "" @@ -4563,8 +4572,8 @@ msgstr "" #: library/typing.rst:3307 msgid "" -"Classes ``Pattern`` and ``Match`` from :mod:`re` now support ``[]``. See :" -"pep:`585` and :ref:`types-genericalias`." +"Classes ``Pattern`` and ``Match`` from :mod:`re` now support ``[]``. " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3313 @@ -4606,14 +4615,14 @@ msgstr "" #: library/typing.rst:3343 msgid "" -":class:`collections.abc.Set` now supports subscripting (``[]``). See :pep:" -"`585` and :ref:`types-genericalias`." +":class:`collections.abc.Set` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3349 msgid "" -"This type represents the types :class:`bytes`, :class:`bytearray`, and :" -"class:`memoryview` of byte sequences." +"This type represents the types :class:`bytes`, :class:`bytearray`, " +"and :class:`memoryview` of byte sequences." msgstr "" #: library/typing.rst:3352 @@ -4628,8 +4637,8 @@ msgstr "" #: library/typing.rst:3361 msgid "" -":class:`collections.abc.Collection` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Collection` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3367 @@ -4638,8 +4647,8 @@ msgstr "" #: library/typing.rst:3369 msgid "" -":class:`collections.abc.Container` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Container` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3375 @@ -4648,8 +4657,8 @@ msgstr "" #: library/typing.rst:3377 msgid "" -":class:`collections.abc.ItemsView` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.ItemsView` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3383 @@ -4658,8 +4667,8 @@ msgstr "" #: library/typing.rst:3385 msgid "" -":class:`collections.abc.KeysView` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.KeysView` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3391 @@ -4668,8 +4677,8 @@ msgstr "" #: library/typing.rst:3393 msgid "" -":class:`collections.abc.Mapping` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Mapping` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3399 @@ -4708,8 +4717,8 @@ msgstr "" #: library/typing.rst:3427 msgid "" -":class:`collections.abc.MutableSet` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.MutableSet` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3433 @@ -4718,8 +4727,8 @@ msgstr "" #: library/typing.rst:3435 msgid "" -":class:`collections.abc.Sequence` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Sequence` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3441 @@ -4728,8 +4737,8 @@ msgstr "" #: library/typing.rst:3443 msgid "" -":class:`collections.abc.ValuesView` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.ValuesView` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3450 @@ -4742,14 +4751,15 @@ msgstr "" #: library/typing.rst:3456 msgid "" -"See :ref:`annotating-generators-and-coroutines` for details on using :class:" -"`collections.abc.Coroutine` and ``typing.Coroutine`` in type annotations." +"See :ref:`annotating-generators-and-coroutines` for details on " +"using :class:`collections.abc.Coroutine` and ``typing.Coroutine`` in type " +"annotations." msgstr "" #: library/typing.rst:3462 msgid "" -":class:`collections.abc.Coroutine` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Coroutine` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3468 @@ -4758,9 +4768,9 @@ msgstr "" #: library/typing.rst:3470 msgid "" -"See :ref:`annotating-generators-and-coroutines` for details on using :class:" -"`collections.abc.AsyncGenerator` and ``typing.AsyncGenerator`` in type " -"annotations." +"See :ref:`annotating-generators-and-coroutines` for details on " +"using :class:`collections.abc.AsyncGenerator` and ``typing.AsyncGenerator`` " +"in type annotations." msgstr "" #: library/typing.rst:3476 @@ -4795,8 +4805,8 @@ msgstr "" #: library/typing.rst:3507 msgid "" -":class:`collections.abc.Awaitable` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Awaitable` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3514 @@ -4809,8 +4819,8 @@ msgstr "" #: library/typing.rst:3520 msgid "" -":class:`collections.abc.Iterable` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Iterable` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3526 @@ -4819,8 +4829,8 @@ msgstr "" #: library/typing.rst:3528 msgid "" -":class:`collections.abc.Iterator` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Iterator` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3534 @@ -4829,14 +4839,15 @@ msgstr "" #: library/typing.rst:3536 msgid "" -"See :ref:`annotating-callables` for details on how to use :class:" -"`collections.abc.Callable` and ``typing.Callable`` in type annotations." +"See :ref:`annotating-callables` for details on how to " +"use :class:`collections.abc.Callable` and ``typing.Callable`` in type " +"annotations." msgstr "" #: library/typing.rst:3539 msgid "" -":class:`collections.abc.Callable` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Callable` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3549 @@ -4845,14 +4856,15 @@ msgstr "" #: library/typing.rst:3551 msgid "" -"See :ref:`annotating-generators-and-coroutines` for details on using :class:" -"`collections.abc.Generator` and ``typing.Generator`` in type annotations." +"See :ref:`annotating-generators-and-coroutines` for details on " +"using :class:`collections.abc.Generator` and ``typing.Generator`` in type " +"annotations." msgstr "" #: library/typing.rst:3555 msgid "" -":class:`collections.abc.Generator` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Generator` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3561 @@ -4869,8 +4881,8 @@ msgstr "" #: library/typing.rst:3570 msgid "" -":class:`collections.abc.Reversible` now supports subscripting (``[]``). See :" -"pep:`585` and :ref:`types-genericalias`." +":class:`collections.abc.Reversible` now supports subscripting (``[]``). " +"See :pep:`585` and :ref:`types-genericalias`." msgstr "" #: library/typing.rst:3576 diff --git a/library/unicodedata.po b/library/unicodedata.po index c446430b3..bf0cd52ff 100644 --- a/library/unicodedata.po +++ b/library/unicodedata.po @@ -24,8 +24,8 @@ msgstr "" 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 15.0.0 `_." +"in this database is compiled from the `UCD version 15.0.0 `_." msgstr "" #: library/unicodedata.rst:23 @@ -55,22 +55,22 @@ msgstr "" #: 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." +"such value is defined, *default* is returned, or, if not " +"given, :exc:`ValueError` is raised." msgstr "" #: 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." +"such value is defined, *default* is returned, or, if not " +"given, :exc:`ValueError` is raised." msgstr "" #: 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." +"such value is defined, *default* is returned, or, if not " +"given, :exc:`ValueError` is raised." msgstr "" #: library/unicodedata.rst:68 diff --git a/library/unittest.mock-examples.po b/library/unittest.mock-examples.po index b4f9aed0e..9ee1fe278 100644 --- a/library/unittest.mock-examples.po +++ b/library/unittest.mock-examples.po @@ -101,8 +101,8 @@ msgstr "" 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." +"accessing it in the test will create it, " +"but :meth:`~Mock.assert_called_with` will raise a failure exception." msgstr "" #: library/unittest.mock-examples.rst:106 @@ -122,8 +122,8 @@ 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`. ::" +"mock, so it is configured by modifying the " +"mock :attr:`~Mock.return_value`. ::" msgstr "" #: library/unittest.mock-examples.rst:118 @@ -156,9 +156,9 @@ msgstr "" #: library/unittest.mock-examples.rst:146 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." +"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 "" #: library/unittest.mock-examples.rst:158 @@ -259,10 +259,10 @@ msgstr "" #: library/unittest.mock-examples.rst:283 msgid "" -"Since Python 3.8, ``AsyncMock`` and ``MagicMock`` have support to mock :ref:" -"`async-iterators` through ``__aiter__``. The :attr:`~Mock.return_value` " -"attribute of ``__aiter__`` can be used to set the return values to be used " -"for iteration." +"Since Python 3.8, ``AsyncMock`` and ``MagicMock`` have support to " +"mock :ref:`async-iterators` through ``__aiter__``. " +"The :attr:`~Mock.return_value` attribute of ``__aiter__`` can be used to set " +"the return values to be used for iteration." msgstr "" #: library/unittest.mock-examples.rst:298 @@ -271,10 +271,10 @@ msgstr "" #: library/unittest.mock-examples.rst:300 msgid "" -"Since Python 3.8, ``AsyncMock`` and ``MagicMock`` have support to mock :ref:" -"`async-context-managers` through ``__aenter__`` and ``__aexit__``. By " -"default, ``__aenter__`` and ``__aexit__`` are ``AsyncMock`` instances that " -"return an async function." +"Since Python 3.8, ``AsyncMock`` and ``MagicMock`` have support to " +"mock :ref:`async-context-managers` through ``__aenter__`` and ``__aexit__``. " +"By default, ``__aenter__`` and ``__aexit__`` are ``AsyncMock`` instances " +"that return an async function." msgstr "" #: library/unittest.mock-examples.rst:322 @@ -337,9 +337,10 @@ msgstr "" #: library/unittest.mock-examples.rst:366 msgid "" -":func:`mock_open` is used to patch :func:`open` method. :attr:`~Mock." -"side_effect` can be used to return a new Mock object per call. This can be " -"used to return different contents per file stored in a dictionary::" +":func:`mock_open` is used to patch :func:`open` " +"method. :attr:`~Mock.side_effect` can be used to return a new Mock object " +"per call. This can be used to return different contents per file stored in a " +"dictionary::" msgstr "" #: library/unittest.mock-examples.rst:370 @@ -384,13 +385,13 @@ msgstr "" #: library/unittest.mock-examples.rst:404 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." +"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 "" #: library/unittest.mock-examples.rst:412 @@ -417,8 +418,8 @@ msgstr "" #: library/unittest.mock-examples.rst:429 msgid "" -"If you are patching a module (including :mod:`builtins`) then use :func:" -"`patch` instead of :func:`patch.object`:" +"If you are patching a module (including :mod:`builtins`) then " +"use :func:`patch` instead of :func:`patch.object`:" msgstr "" #: library/unittest.mock-examples.rst:439 @@ -560,14 +561,15 @@ msgstr "" #: library/unittest.mock-examples.rst:573 msgid "" -"mock_backend.get_endpoint.return_value.create_call.return_value.start_call." -"return_value = mock_response" +"mock_backend.get_endpoint.return_value.create_call.return_value.start_call.return_value " +"= mock_response" msgstr "" #: library/unittest.mock-examples.rst:575 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::" +"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 "" #: library/unittest.mock-examples.rst:578 @@ -575,8 +577,9 @@ msgid "" ">>> something = Something()\n" ">>> mock_response = Mock(spec=open)\n" ">>> mock_backend = Mock()\n" -">>> config = {'get_endpoint.return_value.create_call.return_value.start_call." -"return_value': mock_response}\n" +">>> config = " +"{'get_endpoint.return_value.create_call.return_value.start_call.return_value': " +"mock_response}\n" ">>> mock_backend.configure_mock(**config)" msgstr "" @@ -602,8 +605,8 @@ msgstr "" #: library/unittest.mock-examples.rst:595 msgid "" -">>> chained = call.get_endpoint('foobar').create_call('spam', 'eggs')." -"start_call()\n" +">>> chained = call.get_endpoint('foobar').create_call('spam', " +"'eggs').start_call()\n" ">>> call_list = chained.call_list()\n" ">>> assert mock_backend.mock_calls == call_list" msgstr "" @@ -617,8 +620,8 @@ 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:`datetime." -"date.today` method." +"in C, and so I couldn't just monkey-patch out the " +"static :meth:`datetime.date.today` method." msgstr "" #: library/unittest.mock-examples.rst:608 @@ -689,8 +692,8 @@ msgstr "" 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`." +"iteration is :meth:`~container.__iter__`, so we can mock this using " +"a :class:`MagicMock`." msgstr "" #: library/unittest.mock-examples.rst:653 @@ -711,11 +714,11 @@ msgstr "" #: library/unittest.mock-examples.rst:675 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 `_." +"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 "" #: library/unittest.mock-examples.rst:683 @@ -779,8 +782,8 @@ msgstr "" 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::" +"exception is raised in the setUp then tearDown is not " +"called. :meth:`unittest.TestCase.addCleanup` makes this easier::" msgstr "" #: library/unittest.mock-examples.rst:731 @@ -845,17 +848,17 @@ msgstr "" #: library/unittest.mock-examples.rst:792 msgid "" -"If your mock is only being called once you can use the :meth:`~Mock." -"assert_called_once_with` method that also asserts that the :attr:`~Mock." -"call_count` is one." +"If your mock is only being called once you can use " +"the :meth:`~Mock.assert_called_once_with` method that also asserts that " +"the :attr:`~Mock.call_count` is one." msgstr "" #: library/unittest.mock-examples.rst:803 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`:" +"times, and you want to make assertions about *all* those calls you can " +"use :attr:`~Mock.call_args_list`:" msgstr "" #: library/unittest.mock-examples.rst:815 @@ -975,9 +978,9 @@ msgstr "" #: library/unittest.mock-examples.rst:911 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:" +"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 "" #: library/unittest.mock-examples.rst:935 @@ -1075,8 +1078,9 @@ msgstr "" #: library/unittest.mock-examples.rst:1003 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:" +"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 "" #: library/unittest.mock-examples.rst:1019 @@ -1127,10 +1131,11 @@ msgstr "" #: library/unittest.mock-examples.rst:1099 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." +"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 "" #: library/unittest.mock-examples.rst:1105 @@ -1261,10 +1266,10 @@ msgstr "" #: library/unittest.mock-examples.rst:1242 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." +"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 "" #: library/unittest.mock-examples.rst:1256 @@ -1334,15 +1339,16 @@ msgstr "" #: library/unittest.mock-examples.rst:1339 msgid "" -"With a bit of tweaking you could have the comparison function raise the :exc:" -"`AssertionError` directly and provide a more useful failure message." +"With a bit of tweaking you could have the comparison function raise " +"the :exc:`AssertionError` directly and provide a more useful failure message." msgstr "" #: library/unittest.mock-examples.rst:1342 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 `_)." +"useful here, in the form of its equality matcher " +"(`hamcrest.library.integration.match_equality `_)." msgstr "" diff --git a/library/unittest.mock.po b/library/unittest.mock.po index 73e548262..173cfa6b1 100644 --- a/library/unittest.mock.po +++ b/library/unittest.mock.po @@ -43,10 +43,10 @@ msgstr "" #: library/unittest.mock.rst:26 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`." +"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 "" #: library/unittest.mock.rst:32 @@ -202,8 +202,8 @@ msgstr "" 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`" +"when you are mocking out objects that aren't " +"callable: :class:`NonCallableMock` and :class:`NonCallableMagicMock`" msgstr "" #: library/unittest.mock.rst:222 @@ -231,9 +231,9 @@ msgstr "" #: library/unittest.mock.rst:239 msgid "" -"If *spec* is an object (rather than a list of strings) then :attr:`~object." -"__class__` returns the class of the spec object. This allows mocks to pass :" -"func:`isinstance` tests." +"If *spec* is an object (rather than a list of strings) " +"then :attr:`~object.__class__` returns the class of the spec object. This " +"allows mocks to pass :func:`isinstance` tests." msgstr "" #: library/unittest.mock.rst:243 @@ -245,8 +245,8 @@ msgstr "" #: library/unittest.mock.rst:247 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 " +"*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." @@ -278,8 +278,8 @@ msgstr "" #: library/unittest.mock.rst:265 msgid "" "*unsafe*: By default, accessing any attribute whose name starts with " -"*assert*, *assret*, *asert*, *aseert* or *assrt* will raise an :exc:" -"`AttributeError`. Passing ``unsafe=True`` will allow access to these " +"*assert*, *assret*, *asert*, *aseert* or *assrt* will raise " +"an :exc:`AttributeError`. Passing ``unsafe=True`` will allow access to these " "attributes." msgstr "" @@ -289,8 +289,8 @@ msgid "" "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`)." +"to access an attribute that doesn't exist will raise " +"an :exc:`AttributeError`)." msgstr "" #: library/unittest.mock.rst:279 @@ -308,8 +308,8 @@ msgstr "" #: library/unittest.mock.rst:286 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." +"used to set attributes on the mock after it is created. See " +"the :meth:`configure_mock` method for details." msgstr "" #: library/unittest.mock.rst:292 @@ -338,16 +338,16 @@ msgstr "" #: library/unittest.mock.rst:348 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, and in the case of :meth:" -"`assert_called_once_with` it must also be the only call." +"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, and in the case " +"of :meth:`assert_called_once_with` it must also be the only call." msgstr "" #: library/unittest.mock.rst:361 msgid "" -"assert the mock has been called with the specified calls. The :attr:" -"`mock_calls` list is checked for the calls." +"assert the mock has been called with the specified calls. " +"The :attr:`mock_calls` list is checked for the calls." msgstr "" #: library/unittest.mock.rst:364 @@ -421,9 +421,9 @@ msgstr "" #: library/unittest.mock.rst:437 msgid "" -"Note that :meth:`reset_mock` *doesn't* clear the :attr:`return_value`, :attr:" -"`side_effect` or any child attributes you have set using normal assignment " -"by default." +"Note that :meth:`reset_mock` *doesn't* clear " +"the :attr:`return_value`, :attr:`side_effect` or any child attributes you " +"have set using normal assignment by default." msgstr "" #: library/unittest.mock.rst:441 @@ -447,8 +447,8 @@ msgstr "" #: library/unittest.mock.rst:457 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." +"Calls to the attached mock will be recorded in the :attr:`method_calls` " +"and :attr:`mock_calls` attributes of this one." msgstr "" #: library/unittest.mock.rst:464 @@ -538,8 +538,8 @@ msgstr "" 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)." +"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 "" #: library/unittest.mock.rst:584 @@ -578,10 +578,11 @@ msgstr "" #: library/unittest.mock.rst:668 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 `." +":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 "" #: library/unittest.mock.rst:674 @@ -593,8 +594,8 @@ 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`." +"used for conveniently constructing lists of calls to compare " +"with :attr:`call_args_list`." msgstr "" #: library/unittest.mock.rst:696 @@ -647,8 +648,8 @@ msgstr "" #: library/unittest.mock.rst:768 msgid "" -":attr:`!__class__` is assignable to, this allows a mock to pass an :func:" -"`isinstance` check without forcing you to use a spec:" +":attr:`!__class__` is assignable to, this allows a mock to pass " +"an :func:`isinstance` check without forcing you to use a spec:" msgstr "" #: library/unittest.mock.rst:778 @@ -666,8 +667,8 @@ msgstr "" #: library/unittest.mock.rst:792 msgid "" -"The :class:`Mock` classes have support for mocking magic methods. See :ref:" -"`magic methods ` for the full details." +"The :class:`Mock` classes have support for mocking magic methods. " +"See :ref:`magic methods ` for the full details." msgstr "" #: library/unittest.mock.rst:795 @@ -706,10 +707,10 @@ msgstr "" #: library/unittest.mock.rst:834 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." +"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 "" #: library/unittest.mock.rst:839 @@ -718,10 +719,10 @@ msgstr "" #: library/unittest.mock.rst:845 msgid "" -"A mock intended to be used as a :class:`property`, or other :term:" -"`descriptor`, on a class. :class:`PropertyMock` provides :meth:`~object." -"__get__` and :meth:`~object.__set__` methods so you can specify a return " -"value when it is fetched." +"A mock intended to be used as a :class:`property`, or " +"other :term:`descriptor`, on a class. :class:`PropertyMock` " +"provides :meth:`~object.__get__` and :meth:`~object.__set__` methods so you " +"can specify a return value when it is fetched." msgstr "" #: library/unittest.mock.rst:850 @@ -753,9 +754,9 @@ msgstr "" #: library/unittest.mock.rst:871 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::" +"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 "" #: library/unittest.mock.rst:875 @@ -835,12 +836,12 @@ msgstr "" #: library/unittest.mock.rst:936 msgid "" -"Setting the *spec* of a :class:`Mock`, :class:`MagicMock`, or :class:" -"`AsyncMock` to a class with asynchronous and synchronous functions will " -"automatically detect the synchronous functions and set them as :class:" -"`MagicMock` (if the parent mock is :class:`AsyncMock` or :class:`MagicMock`) " -"or :class:`Mock` (if the parent mock is :class:`Mock`). All asynchronous " -"functions will be :class:`AsyncMock`." +"Setting the *spec* of a :class:`Mock`, :class:`MagicMock`, " +"or :class:`AsyncMock` to a class with asynchronous and synchronous functions " +"will automatically detect the synchronous functions and set them " +"as :class:`MagicMock` (if the parent mock is :class:`AsyncMock` " +"or :class:`MagicMock`) or :class:`Mock` (if the parent mock " +"is :class:`Mock`). All asynchronous functions will be :class:`AsyncMock`." msgstr "" #: library/unittest.mock.rst:964 @@ -869,8 +870,8 @@ msgstr "" #: library/unittest.mock.rst:1049 msgid "" -"Assert the mock has been awaited with the specified calls. The :attr:" -"`await_args_list` list is checked for the awaits." +"Assert the mock has been awaited with the specified calls. " +"The :attr:`await_args_list` list is checked for the awaits." msgstr "" #: library/unittest.mock.rst:1052 @@ -891,8 +892,8 @@ msgstr "" #: library/unittest.mock.rst:1083 msgid "" -"See :func:`Mock.reset_mock`. Also sets :attr:`await_count` to 0, :attr:" -"`await_args` to None, and clears the :attr:`await_args_list`." +"See :func:`Mock.reset_mock`. Also sets :attr:`await_count` to " +"0, :attr:`await_args` to None, and clears the :attr:`await_args_list`." msgstr "" #: library/unittest.mock.rst:1088 @@ -903,8 +904,8 @@ msgstr "" #: library/unittest.mock.rst:1103 msgid "" "This is either ``None`` (if the mock hasn’t been awaited), or the arguments " -"that the mock was last awaited with. Functions the same as :attr:`Mock." -"call_args`." +"that the mock was last awaited with. Functions the same " +"as :attr:`Mock.call_args`." msgstr "" #: library/unittest.mock.rst:1121 @@ -920,17 +921,17 @@ msgstr "" #: library/unittest.mock.rst:1142 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." +"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 "" #: library/unittest.mock.rst:1148 msgid "" -"Calls made to the object will be recorded in the attributes like :attr:" -"`~Mock.call_args` and :attr:`~Mock.call_args_list`." +"Calls made to the object will be recorded in the attributes " +"like :attr:`~Mock.call_args` and :attr:`~Mock.call_args_list`." msgstr "" #: library/unittest.mock.rst:1151 @@ -942,8 +943,8 @@ msgstr "" #: library/unittest.mock.rst:1155 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:" +"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 "" #: library/unittest.mock.rst:1173 @@ -1027,8 +1028,8 @@ msgstr "" 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`::" +"creation time. There are two alternatives. One option is to " +"use :meth:`~Mock.configure_mock`::" msgstr "" #: library/unittest.mock.rst:1289 @@ -1075,8 +1076,8 @@ msgstr "" #: library/unittest.mock.rst:1332 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::" +"attach mocks that have names to a parent you use " +"the :meth:`~Mock.attach_mock` method::" msgstr "" #: library/unittest.mock.rst:1336 @@ -1156,8 +1157,8 @@ msgstr "" #: library/unittest.mock.rst:1395 msgid "" -"The *spec* and *spec_set* keyword arguments are passed to the :class:" -"`MagicMock` if patch is creating one for you." +"The *spec* and *spec_set* keyword arguments are passed to " +"the :class:`MagicMock` if patch is creating one for you." msgstr "" #: library/unittest.mock.rst:1398 @@ -1169,8 +1170,9 @@ msgstr "" #: library/unittest.mock.rst:1401 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:" -"`AsyncMock` is used for async functions and :class:`MagicMock` for the rest." +"that will be called to create the *new* object. By " +"default :class:`AsyncMock` is used for async functions " +"and :class:`MagicMock` for the rest." msgstr "" #: library/unittest.mock.rst:1405 @@ -1181,8 +1183,8 @@ msgid "" "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`." +"return value (the 'instance') will have the same spec as the class. See " +"the :func:`create_autospec` function and :ref:`auto-speccing`." msgstr "" #: library/unittest.mock.rst:1415 @@ -1213,10 +1215,10 @@ msgid "" "Patch can be used as a :class:`~unittest.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``." +"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 "" #: library/unittest.mock.rst:1439 @@ -1229,9 +1231,9 @@ msgstr "" #: library/unittest.mock.rst:1444 msgid "" -":func:`patch` takes arbitrary keyword arguments. These will be passed to :" -"class:`AsyncMock` if the patched object is asynchronous, to :class:" -"`MagicMock` otherwise or to *new_callable* if specified." +":func:`patch` takes arbitrary keyword arguments. These will be passed " +"to :class:`AsyncMock` if the patched object is asynchronous, " +"to :class:`MagicMock` otherwise or to *new_callable* if specified." msgstr "" #: library/unittest.mock.rst:1448 @@ -1259,15 +1261,15 @@ msgstr "" #: library/unittest.mock.rst:1461 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." +"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 "" #: library/unittest.mock.rst:1465 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." +"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 "" #: library/unittest.mock.rst:1469 @@ -1366,11 +1368,11 @@ msgstr "" #: library/unittest.mock.rst:1531 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 ``**``::" +"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 "" #: library/unittest.mock.rst:1537 @@ -1389,8 +1391,8 @@ msgstr "" #: library/unittest.mock.rst:1547 msgid "" "By default, attempting to patch a function in a module (or a method or an " -"attribute in a class) that does not exist will fail with :exc:" -"`AttributeError`::" +"attribute in a class) that does not exist will fail " +"with :exc:`AttributeError`::" msgstr "" #: library/unittest.mock.rst:1550 @@ -1441,15 +1443,15 @@ msgstr "" 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." +"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 "" #: library/unittest.mock.rst:1587 msgid "" -"When used as a class decorator :func:`patch.object` honours ``patch." -"TEST_PREFIX`` for choosing which methods to wrap." +"When used as a class decorator :func:`patch.object` honours " +"``patch.TEST_PREFIX`` for choosing which methods to wrap." msgstr "" #: library/unittest.mock.rst:1590 @@ -1527,8 +1529,9 @@ msgstr "" #: library/unittest.mock.rst:1649 msgid "" -"When used as a class decorator :func:`patch.dict` honours ``patch." -"TEST_PREFIX`` (default to ``'test'``) for choosing which methods to wrap:" +"When used as a class decorator :func:`patch.dict` honours " +"``patch.TEST_PREFIX`` (default to ``'test'``) for choosing which methods to " +"wrap:" msgstr "" #: library/unittest.mock.rst:1660 @@ -1556,9 +1559,9 @@ 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:`~object.__getitem__`, :meth:`~object." -"__setitem__`, :meth:`~object.__delitem__` and either :meth:`~container." -"__iter__` or :meth:`~object.__contains__`." +"to the magic " +"methods :meth:`~object.__getitem__`, :meth:`~object.__setitem__`, :meth:`~object.__delitem__` " +"and either :meth:`~container.__iter__` or :meth:`~object.__contains__`." msgstr "" #: library/unittest.mock.rst:1725 @@ -1582,8 +1585,8 @@ msgstr "" 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." +"decorated function by keyword, and a dictionary is returned " +"when :func:`patch.multiple` is used as a context manager." msgstr "" #: library/unittest.mock.rst:1741 @@ -1596,8 +1599,8 @@ msgstr "" #: library/unittest.mock.rst:1746 msgid "" -"When used as a class decorator :func:`patch.multiple` honours ``patch." -"TEST_PREFIX`` for choosing which methods to wrap." +"When used as a class decorator :func:`patch.multiple` honours " +"``patch.TEST_PREFIX`` for choosing which methods to wrap." msgstr "" #: library/unittest.mock.rst:1749 @@ -1726,8 +1729,8 @@ msgstr "" 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::" +"exception is raised in the ``setUp`` then ``tearDown`` is not " +"called. :meth:`unittest.TestCase.addCleanup` makes this easier::" msgstr "" #: library/unittest.mock.rst:1840 @@ -1751,8 +1754,8 @@ msgstr "" #: library/unittest.mock.rst:1853 msgid "" -"It is also possible to stop all patches which have been started by using :" -"func:`patch.stopall`." +"It is also possible to stop all patches which have been started by " +"using :func:`patch.stopall`." msgstr "" #: library/unittest.mock.rst:1858 @@ -1795,8 +1798,8 @@ msgstr "" #: library/unittest.mock.rst:1887 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``::" +"can inform the patchers of the different prefix by setting " +"``patch.TEST_PREFIX``::" msgstr "" #: library/unittest.mock.rst:1890 @@ -1879,10 +1882,10 @@ msgstr "" 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." +"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 "" #: library/unittest.mock.rst:1966 @@ -1900,10 +1903,10 @@ msgstr "" #: library/unittest.mock.rst:1972 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::" +"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 "" #: library/unittest.mock.rst:1977 @@ -1919,8 +1922,8 @@ 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 "" @@ -1934,9 +1937,9 @@ msgstr "" #: library/unittest.mock.rst:1998 msgid "" -":class:`Mock` supports mocking the Python protocol methods, also known as :" -"term:`\"magic methods\" `. This allows mock objects to replace " -"containers or other objects that implement Python protocols." +":class:`Mock` supports mocking the Python protocol methods, also known " +"as :term:`\"magic methods\" `. This allows mock objects to " +"replace containers or other objects that implement Python protocols." msgstr "" #: library/unittest.mock.rst:2002 @@ -1956,8 +1959,8 @@ msgstr "" #: library/unittest.mock.rst:2030 msgid "" -"One use case for this is for mocking objects used as context managers in a :" -"keyword:`with` statement:" +"One use case for this is for mocking objects used as context managers in " +"a :keyword:`with` statement:" msgstr "" #: library/unittest.mock.rst:2042 @@ -1969,8 +1972,8 @@ msgstr "" #: library/unittest.mock.rst:2047 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`." +"set a magic method that isn't in the spec will raise " +"an :exc:`AttributeError`." msgstr "" #: library/unittest.mock.rst:2050 @@ -2075,8 +2078,8 @@ msgstr "" #: library/unittest.mock.rst:2092 msgid "" -"There are two ``MagicMock`` variants: :class:`MagicMock` and :class:" -"`NonCallableMagicMock`." +"There are two ``MagicMock`` variants: :class:`MagicMock` " +"and :class:`NonCallableMagicMock`." msgstr "" #: library/unittest.mock.rst:2097 @@ -2201,9 +2204,9 @@ msgstr "" #: library/unittest.mock.rst:2163 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::" +"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 "" #: library/unittest.mock.rst:2168 @@ -2309,8 +2312,8 @@ msgstr "" #: library/unittest.mock.rst:2235 msgid "" -"The ``sentinel`` attributes now preserve their identity when they are :mod:" -"`copied ` or :mod:`pickled `." +"The ``sentinel`` attributes now preserve their identity when they " +"are :mod:`copied ` or :mod:`pickled `." msgstr "" #: library/unittest.mock.rst:2239 @@ -2323,8 +2326,8 @@ msgstr "" #: library/unittest.mock.rst:2244 msgid "" -"In this example we monkey patch ``method`` to return ``sentinel." -"some_object``:" +"In this example we monkey patch ``method`` to return " +"``sentinel.some_object``:" msgstr "" #: library/unittest.mock.rst:2256 @@ -2333,9 +2336,9 @@ msgstr "" #: library/unittest.mock.rst:2261 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." +"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 "" #: library/unittest.mock.rst:2267 @@ -2345,8 +2348,8 @@ msgstr "" #: library/unittest.mock.rst:2271 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 :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 "" @@ -2375,18 +2378,19 @@ 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." +"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 "" #: library/unittest.mock.rst:2317 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)." +"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 "" #: library/unittest.mock.rst:2322 @@ -2435,8 +2439,8 @@ msgstr "" #: library/unittest.mock.rst:2377 msgid "" -"See :ref:`auto-speccing` for examples of how to use auto-speccing with :func:" -"`create_autospec` and the *autospec* argument to :func:`patch`." +"See :ref:`auto-speccing` for examples of how to use auto-speccing " +"with :func:`create_autospec` and the *autospec* argument to :func:`patch`." msgstr "" #: library/unittest.mock.rst:2383 @@ -2460,14 +2464,15 @@ msgstr "" #: library/unittest.mock.rst:2397 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." +"*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 "" #: library/unittest.mock.rst:2406 msgid "" -":data:`ANY` can also be used in comparisons with call lists like :attr:" -"`~Mock.mock_calls`:" +":data:`ANY` can also be used in comparisons with call lists " +"like :attr:`~Mock.mock_calls`:" msgstr "" #: library/unittest.mock.rst:2416 @@ -2494,8 +2499,8 @@ msgid "" ":data:`FILTER_DIR` is a module level variable that controls the way mock " "objects respond to :func:`dir`. 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``." +"filtering, or need to switch it off for diagnostic purposes, then set " +"``mock.FILTER_DIR = False``." msgstr "" #: library/unittest.mock.rst:2437 @@ -2578,15 +2583,16 @@ msgstr "" #: library/unittest.mock.rst:2502 msgid "" -"*read_data* is a string for the :meth:`~io.RawIOBase.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." +"*read_data* is a string for " +"the :meth:`~io.RawIOBase.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 "" #: library/unittest.mock.rst:2512 @@ -2621,8 +2627,8 @@ msgstr "" #: library/unittest.mock.rst:2530 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:`~object." -"__enter__` and :meth:`~object.__exit__` called)." +"*returned object* that is used as a context manager (and " +"has :meth:`~object.__enter__` and :meth:`~object.__exit__` called)." msgstr "" #: library/unittest.mock.rst:2534 @@ -2672,8 +2678,8 @@ msgid "" "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." +"methods have the same call signature as the original so they raise " +"a :exc:`TypeError` if they are called incorrectly." msgstr "" #: library/unittest.mock.rst:2573 @@ -2726,8 +2732,8 @@ msgstr "" #: library/unittest.mock.rst:2611 msgid "" -"Auto-speccing solves this problem. You can either pass ``autospec=True`` to :" -"func:`patch` / :func:`patch.object` or use the :func:`create_autospec` " +"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 " @@ -2753,9 +2759,9 @@ msgstr "" #: library/unittest.mock.rst:2630 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::" +"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 "" #: library/unittest.mock.rst:2634 @@ -2807,8 +2813,8 @@ msgstr "" #: library/unittest.mock.rst:2662 msgid "" -"As well as using *autospec* through :func:`patch` there is a :func:" -"`create_autospec` for creating autospecced mocks directly:" +"As well as using *autospec* through :func:`patch` there is " +"a :func:`create_autospec` for creating autospecced mocks directly:" msgstr "" #: library/unittest.mock.rst:2670 @@ -2983,19 +2989,19 @@ msgstr "" #: library/unittest.mock.rst:2808 msgid "" -"If all three are set, mock will return the value from :attr:`~Mock." -"side_effect`, ignoring :attr:`~Mock.return_value` and the wrapped object " -"altogether. If any two are set, the one with the higher precedence will " -"return the value. Regardless of the order of which was set first, the order " -"of precedence remains unchanged." +"If all three are set, mock will return the value " +"from :attr:`~Mock.side_effect`, ignoring :attr:`~Mock.return_value` and the " +"wrapped object altogether. If any two are set, the one with the higher " +"precedence will return the value. Regardless of the order of which was set " +"first, the order of precedence remains unchanged." msgstr "" #: library/unittest.mock.rst:2826 msgid "" "As ``None`` is the default value of :attr:`~Mock.side_effect`, if you " "reassign its value back to ``None``, the order of precedence will be checked " -"between :attr:`~Mock.return_value` and the wrapped object, ignoring :attr:" -"`~Mock.side_effect`." +"between :attr:`~Mock.return_value` and the wrapped object, " +"ignoring :attr:`~Mock.side_effect`." msgstr "" #: library/unittest.mock.rst:2835 @@ -3007,8 +3013,8 @@ msgstr "" #: library/unittest.mock.rst:2844 msgid "" -"When :class:`Mock` wraps an object, the default value of :attr:`~Mock." -"return_value` will be :data:`DEFAULT`." +"When :class:`Mock` wraps an object, the default value " +"of :attr:`~Mock.return_value` will be :data:`DEFAULT`." msgstr "" #: library/unittest.mock.rst:2853 diff --git a/library/unittest.po b/library/unittest.po index 9e8fcbe8f..fdb345dd9 100644 --- a/library/unittest.po +++ b/library/unittest.po @@ -100,8 +100,8 @@ msgstr "" #: library/unittest.rst:55 msgid "" -"`Simple Smalltalk Testing: With Patterns `_" +"`Simple Smalltalk Testing: With Patterns `_" msgstr "" #: library/unittest.rst:56 @@ -205,11 +205,11 @@ msgstr "" #: library/unittest.rst:118 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." +"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 "" #: library/unittest.rst:125 @@ -238,9 +238,9 @@ msgstr "" #: library/unittest.rst:139 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::" +"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 "" #: library/unittest.rst:142 @@ -395,8 +395,8 @@ msgstr "" #: library/unittest.rst:240 msgid "" "For example, ``-k foo`` matches ``foo_tests.SomeTest.test_something``, " -"``bar_tests.SomeTest.test_foo``, but not ``bar_tests.FooTest." -"test_something``." +"``bar_tests.SomeTest.test_foo``, but not " +"``bar_tests.FooTest.test_something``." msgstr "" #: library/unittest.rst:245 @@ -436,9 +436,9 @@ msgstr "" #: library/unittest.rst:273 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 ` importable from the top-level directory of the " -"project (this means that their filenames must be valid :ref:`identifiers " +"discovery, all of the test files must be :ref:`modules ` " +"or :ref:`packages ` importable from the top-level directory of " +"the project (this means that their filenames must be valid :ref:`identifiers " "`)." msgstr "" @@ -570,10 +570,10 @@ msgstr "" #: library/unittest.rst:372 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`." +"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 "" #: library/unittest.rst:378 @@ -612,9 +612,9 @@ msgstr "" #: library/unittest.rst:399 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::" +"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 "" #: library/unittest.rst:404 @@ -676,19 +676,19 @@ msgstr "" msgid "" "Such a working environment for the testing code is called a :dfn:`test " "fixture`. A new TestCase instance is created as a unique test fixture used " -"to execute each individual test method. Thus :meth:`~TestCase.setUp`, :meth:" -"`~TestCase.tearDown`, and :meth:`~TestCase.__init__` will be called once per " -"test." +"to execute each individual test method. " +"Thus :meth:`~TestCase.setUp`, :meth:`~TestCase.tearDown`, " +"and :meth:`~TestCase.__init__` will be called once per test." msgstr "" #: library/unittest.rst:449 msgid "" "It is recommended that you use TestCase implementations to group tests " "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 " -"execute them." +"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 execute them." msgstr "" #: library/unittest.rst:456 @@ -805,10 +805,11 @@ msgstr "" #: library/unittest.rst:525 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." +"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 "" #: library/unittest.rst:534 @@ -825,10 +826,10 @@ msgstr "" #: library/unittest.rst:543 msgid "" -"Skipping a test is simply a matter of using the :func:`skip` :term:" -"`decorator` or one of its conditional variants, calling :meth:`TestCase." -"skipTest` within a :meth:`~TestCase.setUp` or test method, or raising :exc:" -"`SkipTest` directly." +"Skipping a test is simply a matter of using " +"the :func:`skip` :term:`decorator` or one of its conditional variants, " +"calling :meth:`TestCase.skipTest` within a :meth:`~TestCase.setUp` or test " +"method, or raising :exc:`SkipTest` directly." msgstr "" #: library/unittest.rst:547 @@ -968,10 +969,11 @@ msgstr "" #: library/unittest.rst:639 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." +"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 "" #: library/unittest.rst:647 @@ -1108,9 +1110,9 @@ msgstr "" #: library/unittest.rst:753 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." +"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 "" #: library/unittest.rst:761 @@ -1118,8 +1120,8 @@ 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 " +"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. " @@ -1337,9 +1339,9 @@ msgstr "" 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." +"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 "" #: library/unittest.rst:900 @@ -1422,8 +1424,8 @@ msgstr "" #: library/unittest.rst:979 msgid "" -":meth:`assertRaisesRegex(exc, r, fun, *args, **kwds) `" +":meth:`assertRaisesRegex(exc, r, fun, *args, **kwds) " +"`" msgstr "" #: library/unittest.rst:979 @@ -1440,8 +1442,8 @@ msgstr "" #: library/unittest.rst:985 msgid "" -":meth:`assertWarnsRegex(warn, r, fun, *args, **kwds) `" +":meth:`assertWarnsRegex(warn, r, fun, *args, **kwds) " +"`" msgstr "" #: library/unittest.rst:985 @@ -1479,11 +1481,11 @@ msgstr "" #: library/unittest.rst:998 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*." +"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 "" #: library/unittest.rst:1005 @@ -1507,9 +1509,9 @@ msgstr "" #: library/unittest.rst:1015 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::" +"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 "" #: library/unittest.rst:1019 @@ -1537,8 +1539,8 @@ msgstr "" 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::" +"object or a string containing a regular expression suitable for use " +"by :func:`re.search`. Examples::" msgstr "" #: library/unittest.rst:1043 @@ -1568,10 +1570,10 @@ msgstr "" #: library/unittest.rst:1064 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*." +"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 "" #: library/unittest.rst:1071 @@ -1595,10 +1597,11 @@ msgstr "" #: library/unittest.rst:1081 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::" +"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 "" #: library/unittest.rst:1087 @@ -1620,8 +1623,8 @@ msgstr "" 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::" +"string containing a regular expression suitable for use " +"by :func:`re.search`. Example::" msgstr "" #: library/unittest.rst:1110 @@ -1645,9 +1648,9 @@ msgstr "" #: library/unittest.rst:1130 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 that were not blocked by a non-propagating " +"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 that were not blocked by a non-propagating " "descendent logger." msgstr "" @@ -1702,9 +1705,9 @@ msgstr "" #: library/unittest.rst:1172 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." +"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 "" #: library/unittest.rst:1180 @@ -1796,8 +1799,8 @@ 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*." +"the values to the given number of *decimal places* (i.e. like " +"the :func:`round` function) and not *significant digits*." msgstr "" #: library/unittest.rst:1229 @@ -1844,8 +1847,8 @@ msgstr "" #: library/unittest.rst:1265 msgid "" -"The method ``assertRegexpMatches()`` has been renamed to :meth:`." -"assertRegex`." +"The method ``assertRegexpMatches()`` has been renamed " +"to :meth:`.assertRegex`." msgstr "" #: library/unittest.rst:1268 @@ -1880,17 +1883,17 @@ 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." +"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 "" #: library/unittest.rst:1307 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." +"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 "" #: library/unittest.rst:1312 @@ -1984,8 +1987,8 @@ msgstr "" #: library/unittest.rst:1377 msgid "" -"Fails if either of *first* or *second* does not have a :meth:`set." -"difference` method." +"Fails if either of *first* or *second* does not have " +"a :meth:`set.difference` method." msgstr "" #: library/unittest.rst:1385 @@ -2011,8 +2014,8 @@ 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`." +"fair\" with the framework. The initial value of this attribute " +"is :exc:`AssertionError`." msgstr "" #: library/unittest.rst:1416 @@ -2040,8 +2043,8 @@ 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`." +"the sequence comparison methods that delegate to " +"it), :meth:`assertDictEqual` and :meth:`assertMultiLineEqual`." msgstr "" #: library/unittest.rst:1440 @@ -2058,8 +2061,8 @@ msgstr "" #: library/unittest.rst:1452 msgid "" -"Return the number of tests represented by this test object. For :class:" -"`TestCase` instances, this will always be ``1``." +"Return the number of tests represented by this test object. " +"For :class:`TestCase` instances, this will always be ``1``." msgstr "" #: library/unittest.rst:1458 @@ -2071,9 +2074,9 @@ msgstr "" #: library/unittest.rst:1462 msgid "" -"For :class:`TestCase` instances, this will always be an instance of :class:" -"`TestResult`; subclasses of :class:`TestCase` should override this as " -"necessary." +"For :class:`TestCase` instances, this will always be an instance " +"of :class:`TestResult`; subclasses of :class:`TestCase` should override this " +"as necessary." msgstr "" #: library/unittest.rst:1469 @@ -2093,8 +2096,8 @@ msgstr "" 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." +"unittest extensions and adding the test name was moved to " +"the :class:`TextTestResult` in Python 3.2." msgstr "" #: library/unittest.rst:1489 @@ -2114,22 +2117,23 @@ msgstr "" #: library/unittest.rst:1503 msgid "" -"Enter the supplied :term:`context manager`. If successful, also add its :" -"meth:`~object.__exit__` method as a cleanup function by :meth:`addCleanup` " -"and return the result of the :meth:`~object.__enter__` method." +"Enter the supplied :term:`context manager`. If successful, also add " +"its :meth:`~object.__exit__` method as a cleanup function " +"by :meth:`addCleanup` and return the result of the :meth:`~object.__enter__` " +"method." msgstr "" #: library/unittest.rst:1513 msgid "" -"This method is called unconditionally after :meth:`tearDown`, or after :meth:" -"`setUp` if :meth:`setUp` raises an exception." +"This method is called unconditionally after :meth:`tearDown`, or " +"after :meth:`setUp` if :meth:`setUp` raises an exception." msgstr "" #: library/unittest.rst:1516 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." +"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 "" #: library/unittest.rst:1521 @@ -2155,23 +2159,24 @@ msgstr "" #: library/unittest.rst:1543 msgid "" -"Enter the supplied :term:`context manager`. If successful, also add its :" -"meth:`~object.__exit__` method as a cleanup function by :meth:" -"`addClassCleanup` and return the result of the :meth:`~object.__enter__` " -"method." +"Enter the supplied :term:`context manager`. If successful, also add " +"its :meth:`~object.__exit__` method as a cleanup function " +"by :meth:`addClassCleanup` and return the result of " +"the :meth:`~object.__enter__` method." msgstr "" #: library/unittest.rst:1553 msgid "" -"This method is called unconditionally after :meth:`tearDownClass`, or after :" -"meth:`setUpClass` if :meth:`setUpClass` raises an exception." +"This method is called unconditionally after :meth:`tearDownClass`, or " +"after :meth:`setUpClass` if :meth:`setUpClass` raises an exception." msgstr "" #: library/unittest.rst:1556 msgid "" -"It is responsible for calling all the cleanup functions added by :meth:" -"`addClassCleanup`. If you need cleanup functions to be called *prior* to :" -"meth:`tearDownClass` then you can call :meth:`doClassCleanups` yourself." +"It is responsible for calling all the cleanup functions added " +"by :meth:`addClassCleanup`. If you need cleanup functions to be called " +"*prior* to :meth:`tearDownClass` then you can call :meth:`doClassCleanups` " +"yourself." msgstr "" #: library/unittest.rst:1561 @@ -2188,11 +2193,11 @@ msgstr "" #: library/unittest.rst:1576 msgid "" -"Method called to prepare the test fixture. This is called after :meth:" -"`setUp`. 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." +"Method called to prepare the test fixture. This is called " +"after :meth:`setUp`. 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 "" #: library/unittest.rst:1584 @@ -2215,19 +2220,19 @@ msgstr "" #: library/unittest.rst:1600 msgid "" "Enter the supplied :term:`asynchronous context manager`. If successful, " -"also add its :meth:`~object.__aexit__` method as a cleanup function by :meth:" -"`addAsyncCleanup` and return the result of the :meth:`~object.__aenter__` " -"method." +"also add its :meth:`~object.__aexit__` method as a cleanup function " +"by :meth:`addAsyncCleanup` and return the result of " +"the :meth:`~object.__aenter__` method." msgstr "" #: library/unittest.rst:1610 msgid "" -"Sets up a new event loop to 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. At the end of the test all the tasks in the event loop are " -"cancelled." +"Sets up a new event loop to 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. At the end of the test all the tasks in " +"the event loop are cancelled." msgstr "" #: library/unittest.rst:1618 @@ -2253,8 +2258,8 @@ msgid "" "\n" " async def test_response(self):\n" " events.append(\"test_response\")\n" -" response = await self._async_connection.get(\"https://example." -"com\")\n" +" response = await self._async_connection.get(\"https://" +"example.com\")\n" " self.assertEqual(response.status_code, 200)\n" " self.addAsyncCleanup(self.on_cleanup)\n" "\n" @@ -2284,8 +2289,8 @@ 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." +"test cases using legacy test code, allowing it to be integrated into " +"a :mod:`unittest`-based test framework." msgstr "" #: library/unittest.rst:1669 @@ -2322,8 +2327,8 @@ msgstr "" #: library/unittest.rst:1695 msgid "" -"Add all the tests from an iterable of :class:`TestCase` and :class:" -"`TestSuite` instances to this test suite." +"Add all the tests from an iterable of :class:`TestCase` " +"and :class:`TestSuite` instances to this test suite." msgstr "" #: library/unittest.rst:1698 @@ -2339,8 +2344,9 @@ msgstr "" #: library/unittest.rst:1706 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." +"test result object passed as *result*. Note that " +"unlike :meth:`TestCase.run`, :meth:`TestSuite.run` requires the result " +"object to be passed in." msgstr "" #: library/unittest.rst:1714 @@ -2377,9 +2383,9 @@ msgstr "" #: library/unittest.rst:1742 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`." +"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 "" #: library/unittest.rst:1747 @@ -2396,9 +2402,9 @@ msgstr "" 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." +"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 "" #: library/unittest.rst:1762 @@ -2419,17 +2425,17 @@ msgstr "" #: library/unittest.rst:1781 msgid "" -"Return a suite of all test cases contained in the :class:`TestCase`\\ -" -"derived :class:`testCaseClass`." +"Return a suite of all test cases contained in the :class:`TestCase`\\ " +"-derived :class:`testCaseClass`." msgstr "" #: library/unittest.rst:1784 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." +"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 "" #: library/unittest.rst:1793 @@ -2476,25 +2482,25 @@ msgstr "" #: library/unittest.rst:1826 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\"." +"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 "" #: library/unittest.rst:1834 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." +"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 "" #: library/unittest.rst:1844 @@ -2630,15 +2636,15 @@ msgstr "" #: library/unittest.rst:1946 msgid "" -"Function to be used to compare method names when sorting them in :meth:" -"`getTestCaseNames` and all the ``loadTestsFrom*`` methods." +"Function to be used to compare method names when sorting them " +"in :meth:`getTestCaseNames` and all the ``loadTestsFrom*`` methods." msgstr "" #: library/unittest.rst:1952 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." +"methods on the resulting object are needed. The default value is " +"the :class:`TestSuite` class." msgstr "" #: library/unittest.rst:1969 @@ -2668,18 +2674,18 @@ msgstr "" #: library/unittest.rst:1979 msgid "" -"A :class:`TestResult` object stores the results of a set of tests. The :" -"class:`TestCase` and :class:`TestSuite` classes ensure that results are " +"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 "" #: library/unittest.rst:1984 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." +"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 "" #: library/unittest.rst:1989 @@ -2770,9 +2776,9 @@ msgstr "" #: library/unittest.rst:2071 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." +"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 "" #: library/unittest.rst:2076 @@ -2858,8 +2864,8 @@ msgstr "" #: library/unittest.rst:2149 msgid "" -"Called when the test case *test* fails or errors, but was marked with the :" -"func:`expectedFailure` decorator." +"Called when the test case *test* fails or errors, but was marked with " +"the :func:`expectedFailure` decorator." msgstr "" #: library/unittest.rst:2152 @@ -2877,8 +2883,8 @@ msgstr "" #: library/unittest.rst:2162 msgid "" -"The default implementation appends the test to the instance's :attr:" -"`unexpectedSuccesses` attribute." +"The default implementation appends the test to the " +"instance's :attr:`unexpectedSuccesses` attribute." msgstr "" #: library/unittest.rst:2168 @@ -2891,8 +2897,8 @@ msgstr "" #: library/unittest.rst:2172 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)``." +"with an exception where *outcome* is a tuple of the form returned " +"by :func:`sys.exc_info`: ``(type, value, traceback)``." msgstr "" #: library/unittest.rst:2176 @@ -2909,8 +2915,8 @@ msgstr "" #: library/unittest.rst:2190 msgid "" -"A concrete implementation of :class:`TestResult` used by the :class:" -"`TextTestRunner`. Subclasses should accept ``**kwargs`` to ensure " +"A concrete implementation of :class:`TestResult` used by " +"the :class:`TextTestRunner`. Subclasses should accept ``**kwargs`` to ensure " "compatibility as the interface changes." msgstr "" @@ -2938,12 +2944,12 @@ msgstr "" #: library/unittest.rst:2217 msgid "" -"By default this runner shows :exc:`DeprecationWarning`, :exc:" -"`PendingDeprecationWarning`, :exc:`ResourceWarning` and :exc:`ImportWarning` " -"even if they are :ref:`ignored by default `. This behavior " -"can be overridden using Python's :option:`!-Wd` or :option:`!-Wa` options " -"(see :ref:`Warning control `) and leaving *warnings* to " -"``None``." +"By default this runner " +"shows :exc:`DeprecationWarning`, :exc:`PendingDeprecationWarning`, :exc:`ResourceWarning` " +"and :exc:`ImportWarning` even if they are :ref:`ignored by default `. This behavior can be overridden using Python's :option:`!-Wd` " +"or :option:`!-Wa` options (see :ref:`Warning control `) " +"and leaving *warnings* to ``None``." msgstr "" #: library/unittest.rst:2225 @@ -2986,9 +2992,9 @@ msgstr "" #: library/unittest.rst:2253 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." +"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 "" #: library/unittest.rst:2264 @@ -3109,8 +3115,8 @@ msgstr "" #: library/unittest.rst:2336 msgid "" -"If a test module defines ``load_tests`` it will be called by :meth:" -"`TestLoader.loadTestsFromModule` with the following arguments::" +"If a test module defines ``load_tests`` it will be called " +"by :meth:`TestLoader.loadTestsFromModule` with the following arguments::" msgstr "" #: library/unittest.rst:2371 @@ -3138,8 +3144,8 @@ msgstr "" #: library/unittest.rst:2352 msgid "" -"A typical ``load_tests`` function that loads tests from a specific set of :" -"class:`TestCase` classes may look like::" +"A typical ``load_tests`` function that loads tests from a specific set " +"of :class:`TestCase` classes may look like::" msgstr "" #: library/unittest.rst:2355 @@ -3157,18 +3163,19 @@ msgstr "" #: library/unittest.rst:2364 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::" +"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 "" #: library/unittest.rst:2373 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`.)" +"package. (``standard_tests`` will only contain tests collected " +"from :file:`__init__.py`.)" msgstr "" #: library/unittest.rst:2377 @@ -3202,8 +3209,8 @@ msgstr "" 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." +"from the previous class (if there is one) is called, followed " +"by :meth:`setUpClass` from the new class." msgstr "" #: library/unittest.rst:2402 @@ -3278,17 +3285,17 @@ msgstr "" #: library/unittest.rst:2447 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." +"then you must call up to them yourself. The implementations " +"in :class:`TestCase` are empty." msgstr "" #: library/unittest.rst:2451 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." +"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 "" #: library/unittest.rst:2459 @@ -3327,8 +3334,8 @@ msgid "" "Add a function to be called after :func:`tearDownModule` to cleanup " "resources used during the test class. 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:" -"`addModuleCleanup` when they are added." +"are called with any arguments and keyword arguments passed " +"into :meth:`addModuleCleanup` when they are added." msgstr "" #: library/unittest.rst:2486 @@ -3339,10 +3346,10 @@ msgstr "" #: library/unittest.rst:2494 msgid "" -"Enter the supplied :term:`context manager`. If successful, also add its :" -"meth:`~object.__exit__` method as a cleanup function by :func:" -"`addModuleCleanup` and return the result of the :meth:`~object.__enter__` " -"method." +"Enter the supplied :term:`context manager`. If successful, also add " +"its :meth:`~object.__exit__` method as a cleanup function " +"by :func:`addModuleCleanup` and return the result of " +"the :meth:`~object.__enter__` method." msgstr "" #: library/unittest.rst:2504 @@ -3353,9 +3360,10 @@ msgstr "" #: library/unittest.rst:2507 msgid "" -"It is responsible for calling all the cleanup functions added by :func:" -"`addModuleCleanup`. If you need cleanup functions to be called *prior* to :" -"func:`tearDownModule` then you can call :func:`doModuleCleanups` yourself." +"It is responsible for calling all the cleanup functions added " +"by :func:`addModuleCleanup`. If you need cleanup functions to be called " +"*prior* to :func:`tearDownModule` then you can call :func:`doModuleCleanups` " +"yourself." msgstr "" #: library/unittest.rst:2512 @@ -3382,12 +3390,12 @@ msgstr "" 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." +"``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 "" #: library/unittest.rst:2539 @@ -3419,9 +3427,9 @@ msgstr "" #: library/unittest.rst:2562 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." +"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 "" #: library/unittest.rst:2569 diff --git a/library/urllib.error.po b/library/urllib.error.po index 416ad3472..605ecfc67 100644 --- a/library/urllib.error.po +++ b/library/urllib.error.po @@ -27,8 +27,8 @@ msgstr "" #: 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`." +"raised by :mod:`urllib.request`. The base exception class " +"is :exc:`URLError`." msgstr "" #: library/urllib.error.rst:17 @@ -56,10 +56,11 @@ msgstr "" #: 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." +"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 "" #: library/urllib.error.rst:44 @@ -69,8 +70,8 @@ msgstr "" #: library/urllib.error.rst:49 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`." +"corresponds to a value found in the dictionary of codes as found " +"in :attr:`http.server.BaseHTTPRequestHandler.responses`." msgstr "" #: library/urllib.error.rst:55 @@ -81,8 +82,8 @@ msgstr "" #: library/urllib.error.rst:60 msgid "" -"The HTTP response headers for the HTTP request that caused the :exc:" -"`HTTPError`. An alias for *hdrs* attribute." +"The HTTP response headers for the HTTP request that caused " +"the :exc:`HTTPError`. An alias for *hdrs* attribute." msgstr "" #: library/urllib.error.rst:68 diff --git a/library/urllib.parse.po b/library/urllib.parse.po index 3dd0601e1..fe5882baf 100644 --- a/library/urllib.parse.po +++ b/library/urllib.parse.po @@ -70,9 +70,9 @@ msgstr "" #: library/urllib.parse.rst:47 msgid "" "Parse a URL into six components, returning a 6-item :term:`named 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 into smaller parts (for example, the " +"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 into 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:" @@ -114,8 +114,8 @@ msgstr "" msgid "" ">>> from urllib.parse import urlparse\n" ">>> urlparse('//www.cwi.nl:80/%7Eguido/Python.html')\n" -"ParseResult(scheme='', netloc='www.cwi.nl:80', path='/%7Eguido/Python." -"html',\n" +"ParseResult(scheme='', netloc='www.cwi.nl:80', path='/%7Eguido/" +"Python.html',\n" " params='', query='', fragment='')\n" ">>> urlparse('www.cwi.nl/%7Eguido/Python.html')\n" "ParseResult(scheme='', netloc='', path='www.cwi.nl/%7Eguido/Python.html',\n" @@ -291,8 +291,8 @@ msgstr "" #: library/urllib.parse.rst:328 msgid "" -"Unmatched square brackets in the :attr:`netloc` attribute will raise a :exc:" -"`ValueError`." +"Unmatched square brackets in the :attr:`netloc` attribute will raise " +"a :exc:`ValueError`." msgstr "" #: library/urllib.parse.rst:331 @@ -306,9 +306,9 @@ msgstr "" #: library/urllib.parse.rst:150 msgid "" "As is the case with all named tuples, the subclass has a few additional " -"methods and attributes that are particularly useful. One such method is :" -"meth:`_replace`. The :meth:`_replace` method will return a new ParseResult " -"object replacing specified fields with new values." +"methods and attributes that are particularly useful. One such method " +"is :meth:`_replace`. The :meth:`_replace` method will return a new " +"ParseResult object replacing specified fields with new values." msgstr "" #: library/urllib.parse.rst:155 @@ -316,12 +316,12 @@ msgid "" ">>> from urllib.parse import urlparse\n" ">>> u = urlparse('//www.cwi.nl:80/%7Eguido/Python.html')\n" ">>> u\n" -"ParseResult(scheme='', netloc='www.cwi.nl:80', path='/%7Eguido/Python." -"html',\n" +"ParseResult(scheme='', netloc='www.cwi.nl:80', path='/%7Eguido/" +"Python.html',\n" " params='', query='', fragment='')\n" ">>> u._replace(scheme='http')\n" -"ParseResult(scheme='http', netloc='www.cwi.nl:80', path='/%7Eguido/Python." -"html',\n" +"ParseResult(scheme='http', netloc='www.cwi.nl:80', path='/%7Eguido/" +"Python.html',\n" " params='', query='', fragment='')" msgstr "" @@ -344,8 +344,8 @@ msgstr "" #: library/urllib.parse.rst:345 msgid "" -"Out-of-range port numbers now raise :exc:`ValueError`, instead of returning :" -"const:`None`." +"Out-of-range port numbers now raise :exc:`ValueError`, instead of " +"returning :const:`None`." msgstr "" #: library/urllib.parse.rst:349 @@ -356,10 +356,10 @@ msgstr "" #: library/urllib.parse.rst:191 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." +"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 "" #: library/urllib.parse.rst:241 @@ -381,8 +381,8 @@ msgstr "" #: library/urllib.parse.rst:251 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." +"percent-encoded sequences into Unicode characters, as accepted by " +"the :meth:`bytes.decode` method." msgstr "" #: library/urllib.parse.rst:255 @@ -422,9 +422,9 @@ msgstr "" #: library/urllib.parse.rst:237 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." +"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 "" #: library/urllib.parse.rst:262 @@ -504,8 +504,8 @@ msgstr "" #: library/urllib.parse.rst:381 msgid "" -"The *allow_fragments* argument has the same meaning and default as for :func:" -"`urlparse`." +"The *allow_fragments* argument has the same meaning and default as " +"for :func:`urlparse`." msgstr "" #: library/urllib.parse.rst:386 @@ -560,10 +560,10 @@ msgstr "" #: library/urllib.parse.rst:430 msgid "" -"Extract the url from a wrapped URL (that is, a string formatted as ````, ````, ``URL:scheme://host/path`` " -"or ``scheme://host/path``). If *url* is not a wrapped URL, it is returned " -"without changes." +"Extract the url from a wrapped URL (that is, a string formatted as " +"````, ````, ``URL:scheme://host/" +"path`` or ``scheme://host/path``). If *url* is not a wrapped URL, it is " +"returned without changes." msgstr "" #: library/urllib.parse.rst:438 @@ -616,36 +616,37 @@ 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." +"parsing functions in this module all operate on :class:`bytes` " +"and :class:`bytearray` objects in addition to :class:`str` objects." msgstr "" #: library/urllib.parse.rst:475 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." +"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 "" #: library/urllib.parse.rst:479 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`." +"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 "" #: library/urllib.parse.rst:484 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)." +"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 "" #: library/urllib.parse.rst:495 @@ -673,9 +674,9 @@ msgstr "" #: library/urllib.parse.rst:513 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 " +"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 "" @@ -787,8 +788,8 @@ msgid "" "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." +"*errors* must not be supplied if *string* is a :class:`bytes`, or " +"a :class:`TypeError` is raised." msgstr "" #: library/urllib.parse.rst:626 @@ -815,8 +816,8 @@ msgstr "" #: library/urllib.parse.rst:644 msgid "" -"Like :func:`quote`, but accepts a :class:`bytes` object rather than a :class:" -"`str`, and does not perform string-to-bytes encoding." +"Like :func:`quote`, but accepts a :class:`bytes` object rather than " +"a :class:`str`, and does not perform string-to-bytes encoding." msgstr "" #: library/urllib.parse.rst:647 @@ -827,8 +828,8 @@ msgstr "" msgid "" "Replace :samp:`%{xx}` escapes with 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." +"encoded sequences into Unicode characters, as accepted by " +"the :meth:`bytes.decode` method." msgstr "" #: library/urllib.parse.rst:660 @@ -924,9 +925,9 @@ msgstr "" #: library/urllib.parse.rst:730 msgid "" -"Refer to :ref:`urllib examples ` to find out how the :func:" -"`urllib.parse.urlencode` method can be used for generating the query string " -"of a URL or data for a POST request." +"Refer to :ref:`urllib examples ` to find out how " +"the :func:`urllib.parse.urlencode` method can be used for generating the " +"query string of a URL or data for a POST request." msgstr "" #: library/urllib.parse.rst:734 diff --git a/library/urllib.request.po b/library/urllib.request.po index 145b2e9d0..46d6c502e 100644 --- a/library/urllib.request.po +++ b/library/urllib.request.po @@ -90,8 +90,8 @@ msgstr "" #: library/urllib.request.rst:54 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." +"describing the various SSL options. " +"See :class:`~http.client.HTTPSConnection` for more details." msgstr "" #: library/urllib.request.rst:58 @@ -99,8 +99,8 @@ 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`." +"directory of hashed certificate files. More information can be found " +"in :meth:`ssl.SSLContext.load_verify_locations`." msgstr "" #: library/urllib.request.rst:64 @@ -110,25 +110,25 @@ msgstr "" #: library/urllib.request.rst:66 msgid "" "This function always returns an object which can work as a :term:`context " -"manager` and has the properties *url*, *headers*, and *status*. See :class:" -"`urllib.response.addinfourl` for more detail on these properties." +"manager` and has the properties *url*, *headers*, and *status*. " +"See :class:`urllib.response.addinfourl` for more detail on these properties." msgstr "" #: library/urllib.request.rst:70 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`." +"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 "" #: library/urllib.request.rst:78 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." +"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 "" #: library/urllib.request.rst:82 @@ -138,16 +138,16 @@ msgstr "" #: library/urllib.request.rst:84 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)." +"the default installed global :class:`OpenerDirector` " +"uses :class:`UnknownHandler` to ensure this never happens)." msgstr "" #: library/urllib.request.rst:88 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." +"environment variable like :envvar:`!http_proxy` is " +"set), :class:`ProxyHandler` is default installed and makes sure the requests " +"are handled through the proxy." msgstr "" #: library/urllib.request.rst:93 @@ -155,15 +155,15 @@ 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." +"parameter to ``urllib.urlopen``, can be obtained by " +"using :class:`ProxyHandler` objects." msgstr "" #: library/urllib.request.rst:101 msgid "" -"The default opener raises an :ref:`auditing event ` ``urllib." -"Request`` with arguments ``fullurl``, ``data``, ``headers``, ``method`` " -"taken from the request object." +"The default opener raises an :ref:`auditing event ` " +"``urllib.Request`` with arguments ``fullurl``, ``data``, ``headers``, " +"``method`` taken from the request object." msgstr "" #: library/urllib.request.rst:105 @@ -172,8 +172,8 @@ msgstr "" #: library/urllib.request.rst:108 msgid "" -"HTTPS virtual hosts are now supported if possible (that is, if :const:`ssl." -"HAS_SNI` is true)." +"HTTPS virtual hosts are now supported if possible (that is, " +"if :const:`ssl.HAS_SNI` is true)." msgstr "" #: library/urllib.request.rst:111 @@ -190,25 +190,27 @@ msgstr "" #: library/urllib.request.rst:119 msgid "" -"HTTPS connection now send an ALPN extension with protocol indicator " -"``http/1.1`` when no *context* is given. Custom *context* should set ALPN " -"protocols with :meth:`~ssl.SSLContext.set_alpn_protocols`." +"HTTPS connection now send an ALPN extension with protocol indicator ``http/" +"1.1`` when no *context* is given. Custom *context* should set ALPN protocols " +"with :meth:`~ssl.SSLContext.set_alpn_protocols`." msgstr "" #: library/urllib.request.rst:126 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." +"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 "" #: library/urllib.request.rst:134 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." +"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 "" #: library/urllib.request.rst:144 @@ -219,10 +221,8 @@ msgid "" "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`." +"(if proxy settings are " +"detected), :class:`UnknownHandler`, :class:`HTTPHandler`, :class:`HTTPDefaultErrorHandler`, :class:`HTTPRedirectHandler`, :class:`FTPHandler`, :class:`FileHandler`, :class:`HTTPErrorProcessor`." msgstr "" #: library/urllib.request.rst:154 @@ -241,8 +241,8 @@ msgstr "" 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." +"The return value will already be quoted using " +"the :func:`~urllib.parse.quote` function." msgstr "" #: library/urllib.request.rst:170 @@ -300,19 +300,19 @@ msgstr "" #: library/urllib.request.rst:213 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." +"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 "" #: library/urllib.request.rst:219 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 " +"*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 " @@ -337,11 +337,11 @@ msgstr "" #: library/urllib.request.rst:238 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." +"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 "" #: library/urllib.request.rst:246 @@ -356,11 +356,11 @@ msgstr "" #: library/urllib.request.rst:253 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." +"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 "" #: library/urllib.request.rst:261 @@ -467,9 +467,9 @@ msgstr "" 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 " +"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 " @@ -507,8 +507,9 @@ msgstr "" 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." +"that is compatible with :class:`HTTPPasswordMgr`; refer to " +"section :ref:`http-password-mgr` for information on the interface that must " +"be supported." msgstr "" #: library/urllib.request.rst:403 @@ -584,9 +585,9 @@ msgstr "" #: library/urllib.request.rst:486 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." +"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 "" #: library/urllib.request.rst:492 @@ -621,8 +622,8 @@ msgstr "" #: library/urllib.request.rst:518 msgid "" -"boolean, indicates whether the request is unverifiable as defined by :rfc:" -"`2965`." +"boolean, indicates whether the request is unverifiable as defined " +"by :rfc:`2965`." msgstr "" #: library/urllib.request.rst:523 @@ -644,10 +645,10 @@ msgstr "" #: library/urllib.request.rst:540 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." +"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 "" #: library/urllib.request.rst:545 @@ -728,10 +729,10 @@ 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). Note that, in the following, *protocol* should " -"be replaced with the actual protocol to handle, for example :meth:" -"`http_response` would be the HTTP protocol response handler. Also *type* " -"should be replaced with the actual HTTP code, for example :meth:" -"`http_error_404` would handle HTTP 404 errors." +"be replaced with the actual protocol to handle, for " +"example :meth:`http_response` would be the HTTP protocol response handler. " +"Also *type* should be replaced with the actual HTTP code, for " +"example :meth:`http_error_404` would handle HTTP 404 errors." msgstr "" #: library/urllib.request.rst:630 @@ -825,25 +826,27 @@ msgstr "" #: library/urllib.request.rst:688 msgid "" "Handlers with a method named like :meth:`!_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." +"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 "" #: library/urllib.request.rst:693 msgid "" -"In fact, the above algorithm is first tried for methods named :meth:" -"`~BaseHandler.default_open`. If all such methods return :const:`None`, the " -"algorithm is repeated for methods named like :meth:`!_open`. If " -"all such methods return :const:`None`, the algorithm is repeated for methods " +"In fact, the above algorithm is first tried for methods " +"named :meth:`~BaseHandler.default_open`. If all such methods " +"return :const:`None`, the algorithm is repeated for methods named " +"like :meth:`!_open`. If all such methods return :const:`None`, " +"the algorithm is repeated for methods " "named :meth:`~BaseHandler.unknown_open`." msgstr "" #: library/urllib.request.rst:699 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." +"parent :class:`OpenerDirector` instance's :meth:`~OpenerDirector.open` " +"and :meth:`~OpenerDirector.error` methods." msgstr "" #: library/urllib.request.rst:703 @@ -880,8 +883,8 @@ msgstr "" #: library/urllib.request.rst:731 msgid "" "The convention has been adopted that subclasses defining :meth:`!" -"_request` or :meth:`!_response` methods are named :class:" -"`!\\*Processor`; all others are named :class:`!\\*Handler`." +"_request` or :meth:`!_response` methods are " +"named :class:`!\\*Processor`; all others are named :class:`!\\*Handler`." msgstr "" #: library/urllib.request.rst:738 @@ -898,12 +901,13 @@ msgstr "" #: library/urllib.request.rst:747 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:`~OpenerDirector.open` method 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:`~urllib.error.URLError`)." +"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:`~OpenerDirector.open` method " +"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:`~urllib.error.URLError`)." msgstr "" #: library/urllib.request.rst:754 @@ -918,9 +922,9 @@ msgstr "" #: library/urllib.request.rst:764 msgid "" -"This method, if defined, will be called by the parent :class:" -"`OpenerDirector`. Return values should be the same as for :meth:" -"`~BaseHandler.default_open`." +"This method, if defined, will be called by the " +"parent :class:`OpenerDirector`. Return values should be the same as " +"for :meth:`~BaseHandler.default_open`." msgstr "" #: library/urllib.request.rst:770 @@ -932,18 +936,18 @@ msgstr "" #: library/urllib.request.rst:774 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`." +"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 "" #: library/urllib.request.rst:781 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." +"HTTP errors. It will be called automatically by " +"the :class:`OpenerDirector` getting the error, and should not normally be " +"called in other circumstances." msgstr "" #: library/urllib.request.rst:786 @@ -956,8 +960,8 @@ msgstr "" #: library/urllib.request.rst:791 msgid "" -"Return values and exceptions raised should be the same as those of :func:" -"`urlopen`." +"Return values and exceptions raised should be the same as those " +"of :func:`urlopen`." msgstr "" #: library/urllib.request.rst:798 @@ -973,8 +977,8 @@ msgstr "" #: library/urllib.request.rst:804 msgid "" -"Arguments, return values and exceptions raised should be the same as for :" -"meth:`~BaseHandler.http_error_default`." +"Arguments, return values and exceptions raised should be the same as " +"for :meth:`~BaseHandler.http_error_default`." msgstr "" #: library/urllib.request.rst:812 @@ -985,9 +989,9 @@ msgstr "" #: library/urllib.request.rst:815 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." +"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 "" #: library/urllib.request.rst:824 @@ -998,11 +1002,11 @@ msgstr "" #: library/urllib.request.rst:827 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`." +"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 "" #: library/urllib.request.rst:837 @@ -1029,18 +1033,19 @@ msgid "" "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." +"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 "" #: library/urllib.request.rst:862 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." +"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 "" #: library/urllib.request.rst:871 @@ -1105,8 +1110,8 @@ msgstr "" #: library/urllib.request.rst:934 msgid "" -"These methods are available on :class:`HTTPPasswordMgr` and :class:" -"`HTTPPasswordMgrWithDefaultRealm` objects." +"These methods are available on :class:`HTTPPasswordMgr` " +"and :class:`HTTPPasswordMgrWithDefaultRealm` objects." msgstr "" #: library/urllib.request.rst:940 @@ -1142,10 +1147,10 @@ msgstr "" #: library/urllib.request.rst:967 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." +"*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 "" #: library/urllib.request.rst:975 @@ -1171,8 +1176,8 @@ 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." +"URL and path to authenticate for, *req* should be the " +"(failed) :class:`Request` object, and *headers* should be the error headers." msgstr "" #: library/urllib.request.rst:1005 @@ -1222,8 +1227,8 @@ msgstr "" #: library/urllib.request.rst:1077 msgid "" -"Send an HTTP request, which can be either GET or POST, depending on ``req." -"has_data()``." +"Send an HTTP request, which can be either GET or POST, depending on " +"``req.has_data()``." msgstr "" #: library/urllib.request.rst:1084 @@ -1232,8 +1237,8 @@ msgstr "" #: library/urllib.request.rst:1089 msgid "" -"Send an HTTPS request, which can be either GET or POST, depending on ``req." -"has_data()``." +"Send an HTTPS request, which can be either GET or POST, depending on " +"``req.has_data()``." msgstr "" #: library/urllib.request.rst:1096 @@ -1314,8 +1319,8 @@ msgstr "" msgid "" "For non-200 error codes, this simply passes the job on to the :meth:`!" "http_error_\\` handler methods, via :meth:`OpenerDirector.error`. " -"Eventually, :class:`HTTPDefaultErrorHandler` will raise an :exc:`~urllib." -"error.HTTPError` if no other handler handles the error." +"Eventually, :class:`HTTPDefaultErrorHandler` will raise " +"an :exc:`~urllib.error.HTTPError` if no other handler handles the error." msgstr "" #: library/urllib.request.rst:1185 @@ -1390,8 +1395,8 @@ msgstr "" #: library/urllib.request.rst:1230 msgid "" -"It is also possible to achieve the same result without using the :term:" -"`context manager` approach. ::" +"It is also possible to achieve the same result without using " +"the :term:`context manager` approach. ::" msgstr "" #: library/urllib.request.rst:1233 @@ -1470,11 +1475,11 @@ msgstr "" #: library/urllib.request.rst:1282 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." +":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 "" #: library/urllib.request.rst:1288 @@ -1486,8 +1491,8 @@ msgstr "" #: library/urllib.request.rst:1292 msgid "" -"proxy_handler = urllib.request.ProxyHandler({'http': 'http://www.example." -"com:3128/'})\n" +"proxy_handler = urllib.request.ProxyHandler({'http': 'http://" +"www.example.com:3128/'})\n" "proxy_auth_handler = urllib.request.ProxyBasicAuthHandler()\n" "proxy_auth_handler.add_password('realm', 'host', 'username', 'password')\n" "\n" @@ -1530,9 +1535,10 @@ msgstr "" #: library/urllib.request.rst:1319 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`)." +"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 "" #: library/urllib.request.rst:1326 @@ -1618,9 +1624,9 @@ 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`." +"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 "" #: library/urllib.request.rst:1383 @@ -1642,8 +1648,8 @@ msgstr "" #: library/urllib.request.rst:1394 msgid "" ">>> import urllib.request\n" -">>> local_filename, headers = urllib.request.urlretrieve('http://python." -"org/')\n" +">>> local_filename, headers = urllib.request.urlretrieve('http://" +"python.org/')\n" ">>> html = open(local_filename)\n" ">>> html.close()" msgstr "" @@ -1652,9 +1658,9 @@ msgstr "" 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." +"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 "" #: library/urllib.request.rst:1405 @@ -1694,8 +1700,8 @@ msgstr "" #: library/urllib.request.rst:1430 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`." +"objects using schemes other than :file:`http:`, :file:`ftp:`, " +"or :file:`file:`, you probably want to use :class:`FancyURLopener`." msgstr "" #: library/urllib.request.rst:1434 @@ -1735,8 +1741,8 @@ 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`." +"The *data* argument has the same meaning as the *data* argument " +"of :func:`urlopen`." msgstr "" #: library/urllib.request.rst:1461 @@ -1750,35 +1756,35 @@ msgstr "" #: library/urllib.request.rst:1470 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." +"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 "" #: library/urllib.request.rst:1483 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." +"type is ``GET``). The *data* argument must in " +"standard :mimetype:`application/x-www-form-urlencoded` format; see " +"the :func:`urllib.parse.urlencode` function." msgstr "" #: library/urllib.request.rst:1492 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." +"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 "" #: library/urllib.request.rst:1502 @@ -1794,9 +1800,9 @@ msgstr "" #: library/urllib.request.rst:1509 msgid "" -"For all other response codes, the method :meth:`~BaseHandler." -"http_error_default` is called which you can override in subclasses to handle " -"the error appropriately." +"For all other response codes, the " +"method :meth:`~BaseHandler.http_error_default` is called which you can " +"override in subclasses to handle the error appropriately." msgstr "" #: library/urllib.request.rst:1514 @@ -1810,8 +1816,8 @@ msgstr "" #: library/urllib.request.rst:1519 msgid "" -"The parameters to the constructor are the same as those for :class:" -"`URLopener`." +"The parameters to the constructor are the same as those " +"for :class:`URLopener`." msgstr "" #: library/urllib.request.rst:1523 @@ -1888,9 +1894,9 @@ 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." +"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 "" #: library/urllib.request.rst:1581 @@ -1919,9 +1925,9 @@ msgstr "" msgid "" "The :mod:`urllib.response` module defines functions and classes which define " "a minimal file-like interface, including ``read()`` and ``readline()``. " -"Functions defined by this module are used internally by the :mod:`urllib." -"request` module. The typical response object is a :class:`urllib.response." -"addinfourl` instance:" +"Functions defined by this module are used internally by " +"the :mod:`urllib.request` module. The typical response object is " +"a :class:`urllib.response.addinfourl` instance:" msgstr "" #: library/urllib.request.rst:1612 @@ -1932,8 +1938,8 @@ msgstr "" #: library/urllib.request.rst:1616 msgid "" -"Returns the headers of the response in the form of an :class:`~email.message." -"EmailMessage` instance." +"Returns the headers of the response in the form of " +"an :class:`~email.message.EmailMessage` instance." msgstr "" #: library/urllib.request.rst:1622 diff --git a/library/urllib.robotparser.po b/library/urllib.robotparser.po index b3a021cba..d5ec8283a 100644 --- a/library/urllib.robotparser.po +++ b/library/urllib.robotparser.po @@ -35,8 +35,8 @@ msgstr "" #: library/urllib.robotparser.rst:28 msgid "" -"This class provides methods to read, parse and answer questions about the :" -"file:`robots.txt` file at *url*." +"This class provides methods to read, parse and answer questions about " +"the :file:`robots.txt` file at *url*." msgstr "" #: library/urllib.robotparser.rst:33 diff --git a/library/uuid.po b/library/uuid.po index 9561b9be8..5445f1769 100644 --- a/library/uuid.po +++ b/library/uuid.po @@ -27,15 +27,15 @@ msgstr "" #: 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`." +"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 "" #: 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 " +"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 "" @@ -98,9 +98,9 @@ msgstr "" #: library/uuid.rst:71 msgid "" -"Comparison of UUID objects are made by way of comparing their :attr:`UUID." -"int` attributes. Comparison with a non-UUID object raises a :exc:" -"`TypeError`." +"Comparison of UUID objects are made by way of comparing " +"their :attr:`UUID.int` attributes. Comparison with a non-UUID object raises " +"a :exc:`TypeError`." msgstr "" #: library/uuid.rst:75 @@ -179,14 +179,15 @@ msgstr "" #: library/uuid.rst:145 msgid "" "The UUID variant, which determines the internal layout of the UUID. This " -"will be one of the constants :const:`RESERVED_NCS`, :const:`RFC_4122`, :" -"const:`RESERVED_MICROSOFT`, or :const:`RESERVED_FUTURE`." +"will be one of the " +"constants :const:`RESERVED_NCS`, :const:`RFC_4122`, :const:`RESERVED_MICROSOFT`, " +"or :const:`RESERVED_FUTURE`." msgstr "" #: library/uuid.rst:152 msgid "" -"The UUID version number (1 through 5, meaningful only when the variant is :" -"const:`RFC_4122`)." +"The UUID version number (1 through 5, meaningful only when the variant " +"is :const:`RFC_4122`)." msgstr "" #: library/uuid.rst:157 @@ -327,8 +328,8 @@ msgstr "" #: library/uuid.rst:299 msgid "" -"Specify the function name to use to generate the uuid. By default :func:" -"`uuid4` is used." +"Specify the function name to use to generate the uuid. By " +"default :func:`uuid4` is used." msgstr "" #: library/uuid.rst:305 @@ -341,8 +342,8 @@ msgstr "" #: library/uuid.rst:312 msgid "" -"The name used as part of generating the uuid. Only required for :func:" -"`uuid3` / :func:`uuid5` functions." +"The name used as part of generating the uuid. Only required " +"for :func:`uuid3` / :func:`uuid5` functions." msgstr "" #: library/uuid.rst:319 diff --git a/library/venv.po b/library/venv.po index 9ef41b82d..cf6591593 100644 --- a/library/venv.po +++ b/library/venv.po @@ -117,9 +117,9 @@ msgstr "" msgid "" "This creates the target directory (including parent directories as needed) " "and places a :file:`pyvenv.cfg` file in it with a ``home`` key pointing to " -"the Python installation from which the command was run. It also creates a :" -"file:`bin` (or :file:`Scripts` on Windows) subdirectory containing a copy or " -"symlink of the Python executable (as appropriate for the platform or " +"the Python installation from which the command was run. It also creates " +"a :file:`bin` (or :file:`Scripts` on Windows) subdirectory containing a copy " +"or symlink of the Python executable (as appropriate for the platform or " "arguments used at environment creation time). It also creates a :file:`lib/" "pythonX.Y/site-packages` subdirectory (on Windows, this is :file:`Lib\\site-" "packages`). If an existing directory is specified, it will be re-used." @@ -257,12 +257,13 @@ msgstr "" #: library/venv.rst:181 msgid "" -"When a Python interpreter is running from a virtual environment, :data:`sys." -"prefix` and :data:`sys.exec_prefix` point to the directories of the virtual " -"environment, whereas :data:`sys.base_prefix` and :data:`sys." -"base_exec_prefix` point to those of the base Python used to create the " -"environment. It is sufficient to check ``sys.prefix != sys.base_prefix`` to " -"determine if the current interpreter is running from a virtual environment." +"When a Python interpreter is running from a virtual " +"environment, :data:`sys.prefix` and :data:`sys.exec_prefix` point to the " +"directories of the virtual environment, whereas :data:`sys.base_prefix` " +"and :data:`sys.base_exec_prefix` point to those of the base Python used to " +"create the environment. It is sufficient to check ``sys.prefix != " +"sys.base_prefix`` to determine if the current interpreter is running from a " +"virtual environment." msgstr "" #: library/venv.rst:190 @@ -365,13 +366,14 @@ msgstr "" #: library/venv.rst:228 msgid "" "In order to achieve this, scripts installed into virtual environments have a " -"\"shebang\" line which points to the environment's Python interpreter, :samp:" -"`#!/{}/bin/python`. This means that the script will run with " -"that interpreter regardless of the value of :envvar:`PATH`. On Windows, " -"\"shebang\" line processing is supported if you have the :ref:`launcher` " -"installed. Thus, double-clicking an installed script in a Windows Explorer " -"window should run it with the correct interpreter without the environment " -"needing to be activated or on the :envvar:`PATH`." +"\"shebang\" line which points to the environment's Python " +"interpreter, :samp:`#!/{}/bin/python`. This means that the " +"script will run with that interpreter regardless of the value " +"of :envvar:`PATH`. On Windows, \"shebang\" line processing is supported if " +"you have the :ref:`launcher` installed. Thus, double-clicking an installed " +"script in a Windows Explorer window should run it with the correct " +"interpreter without the environment needing to be activated or on " +"the :envvar:`PATH`." msgstr "" #: library/venv.rst:237 @@ -414,8 +416,8 @@ msgstr "" 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." +"customize environment creation according to their needs, " +"the :class:`EnvBuilder` class." msgstr "" #: library/venv.rst:277 @@ -515,9 +517,9 @@ msgstr "" #: library/venv.rst:338 msgid "" -"Each of the methods :meth:`ensure_directories`, :meth:" -"`create_configuration`, :meth:`setup_python`, :meth:`setup_scripts` and :" -"meth:`post_setup` can be overridden." +"Each of the " +"methods :meth:`ensure_directories`, :meth:`create_configuration`, :meth:`setup_python`, :meth:`setup_scripts` " +"and :meth:`post_setup` can be overridden." msgstr "" #: library/venv.rst:344 @@ -583,8 +585,8 @@ msgstr "" #: library/venv.rst:377 msgid "" "``env_exe`` - The name of the Python interpreter in the virtual environment. " -"Used for ``__VENV_PYTHON__`` in activation scripts (see :meth:" -"`install_scripts`)." +"Used for ``__VENV_PYTHON__`` in activation scripts " +"(see :meth:`install_scripts`)." msgstr "" #: library/venv.rst:381 @@ -804,8 +806,8 @@ msgid "" " \"\"\"\n" " Read lines from a subprocess' output stream and either pass to a " "progress\n" -" callable (if specified) or write progress information to sys." -"stderr.\n" +" callable (if specified) or write progress information to " +"sys.stderr.\n" " \"\"\"\n" " progress = self.progress\n" " while True:\n" @@ -866,8 +868,8 @@ msgid "" " url = \"https://bootstrap.pypa.io/ez_setup.py\"\n" " self.install_script(context, 'setuptools', url)\n" " # clear up the setuptools archive which gets downloaded\n" -" pred = lambda o: o.startswith('setuptools-') and o.endswith('.tar." -"gz')\n" +" pred = lambda o: o.startswith('setuptools-') and " +"o.endswith('.tar.gz')\n" " files = filter(pred, os.listdir(context.bin_path))\n" " for f in files:\n" " f = os.path.join(context.bin_path, f)\n" diff --git a/library/warnings.po b/library/warnings.po index 2932d88ea..59f3a9678 100644 --- a/library/warnings.po +++ b/library/warnings.po @@ -36,16 +36,16 @@ msgstr "" #: 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)." +"defined in this module. (C programmers use :c:func:`PyErr_WarnEx`; " +"see :ref:`exceptionhandling` for details)." msgstr "" #: library/warnings.rst:22 msgid "" "Warning messages are normally written to :data:`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 :" -"ref:`warning category `, the text of the warning " +"them into exceptions. The disposition of warnings can vary based on " +"the :ref:`warning category `, 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 "" @@ -60,11 +60,11 @@ msgstr "" #: library/warnings.rst:33 msgid "" -"The determination whether to issue a warning message is controlled by the :" -"ref:`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`." +"The determination whether to issue a warning message is controlled by " +"the :ref:`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 "" #: library/warnings.rst:38 @@ -313,10 +313,10 @@ msgstr "" #: library/warnings.rst:156 msgid "" "*message* is a string containing a regular expression that the start of the " -"warning message must match, case-insensitively. In :option:`-W` and :envvar:" -"`PYTHONWARNINGS`, *message* is a literal string that the start of the " -"warning message must contain (case-insensitively), ignoring any whitespace " -"at the start or end of *message*." +"warning message must match, case-insensitively. In :option:`-W` " +"and :envvar:`PYTHONWARNINGS`, *message* is a literal string that the start " +"of the warning message must contain (case-insensitively), ignoring any " +"whitespace at the start or end of *message*." msgstr "" #: library/warnings.rst:162 @@ -379,11 +379,11 @@ msgstr "" #: library/warnings.rst:198 msgid "" "The meaning of each of these fields is as described in :ref:`warning-" -"filter`. When listing multiple filters on a single line (as for :envvar:" -"`PYTHONWARNINGS`), the individual filters are separated by commas and the " -"filters listed later take precedence over those listed before them (as " -"they're applied left-to-right, and the most recently applied filters take " -"precedence over earlier ones)." +"filter`. When listing multiple filters on a single line (as " +"for :envvar:`PYTHONWARNINGS`), the individual filters are separated by " +"commas and the filters listed later take precedence over those listed before " +"them (as they're applied left-to-right, and the most recently applied " +"filters take precedence over earlier ones)." msgstr "" #: library/warnings.rst:205 @@ -440,8 +440,8 @@ msgstr "" #: library/warnings.rst:238 msgid "" -":exc:`DeprecationWarning` is now ignored by default in addition to :exc:" -"`PendingDeprecationWarning`." +":exc:`DeprecationWarning` is now ignored by default in addition " +"to :exc:`PendingDeprecationWarning`." msgstr "" #: library/warnings.rst:242 @@ -465,10 +465,10 @@ msgstr "" msgid "" "Developers of applications written in Python may wish to hide *all* Python " "level warnings from their users by default, and only display them when " -"running tests or otherwise working on the application. The :data:`sys." -"warnoptions` attribute used to pass filter configurations to the interpreter " -"can be used as a marker to indicate whether or not warnings should be " -"disabled::" +"running tests or otherwise working on the application. " +"The :data:`sys.warnoptions` attribute used to pass filter configurations to " +"the interpreter can be used as a marker to indicate whether or not warnings " +"should be disabled::" msgstr "" #: library/warnings.rst:263 @@ -713,8 +713,8 @@ msgstr "" #: library/warnings.rst:470 msgid "" -"*source*, if supplied, is the destroyed object which emitted a :exc:" -"`ResourceWarning`." +"*source*, if supplied, is the destroyed object which emitted " +"a :exc:`ResourceWarning`." msgstr "" #: library/warnings.rst:447 @@ -754,19 +754,19 @@ 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 :data:`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*." +"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 "" #: library/warnings.rst:490 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*." +"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 "" #: library/warnings.rst:499 @@ -784,10 +784,10 @@ msgstr "" #: library/warnings.rst:511 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." +"`. 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 "" #: library/warnings.rst:520 @@ -804,12 +804,13 @@ msgstr "" #: library/warnings.rst:530 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`." +"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 "" #: library/warnings.rst:539 diff --git a/library/wave.po b/library/wave.po index 187d76b46..14d99bb24 100644 --- a/library/wave.po +++ b/library/wave.po @@ -85,8 +85,8 @@ msgstr "" #: library/wave.rst:48 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." +"the :keyword:`!with` block completes, the :meth:`Wave_read.close` " +"or :meth:`Wave_write.close` method is called." msgstr "" #: library/wave.rst:176 @@ -205,13 +205,13 @@ 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:`setnframes` or :meth:`setparams` with the number of frames that will " -"be written before :meth:`close` is called and then using :meth:" -"`writeframesraw` to write the frame data, or by calling :meth:`writeframes` " -"with all of the frame data to be written. In the latter case :meth:" -"`writeframes` will calculate the number of frames in the data and set " -"*nframes* accordingly before writing the frame data." +"written. An accurate *nframes* value can be achieved either by " +"calling :meth:`setnframes` or :meth:`setparams` with the number of frames " +"that will be written before :meth:`close` is called and then " +"using :meth:`writeframesraw` to write the frame data, or by " +"calling :meth:`writeframes` with all of the frame data to be written. In " +"the latter case :meth:`writeframes` will calculate the number of frames in " +"the data and set *nframes* accordingly before writing the frame data." msgstr "" #: library/wave.rst:179 @@ -220,10 +220,10 @@ msgstr "" #: library/wave.rst:183 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." +"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 "" #: library/wave.rst:191 @@ -264,8 +264,8 @@ msgstr "" #: library/wave.rst:230 msgid "" -"Return current position in the file, with the same disclaimer for the :meth:" -"`Wave_read.tell` and :meth:`Wave_read.setpos` methods." +"Return current position in the file, with the same disclaimer for " +"the :meth:`Wave_read.tell` and :meth:`Wave_read.setpos` methods." msgstr "" #: library/wave.rst:236 @@ -286,7 +286,7 @@ msgstr "" #: library/wave.rst:252 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`." +"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 "" diff --git a/library/weakref.po b/library/weakref.po index cf665c498..d35b69613 100644 --- a/library/weakref.po +++ b/library/weakref.po @@ -39,11 +39,11 @@ msgstr "" #: library/weakref.rst:27 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." +"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 "" #: library/weakref.rst:33 @@ -58,15 +58,15 @@ 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." +"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 "" #: library/weakref.rst:50 @@ -74,9 +74,9 @@ 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." +"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 "" #: library/weakref.rst:57 @@ -90,10 +90,10 @@ msgstr "" #: library/weakref.rst:63 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." +"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 "" #: library/weakref.rst:68 @@ -131,8 +131,8 @@ msgstr "" #: library/weakref.rst:90 msgid "" -"Extension types can easily be made to support weak references; see :ref:" -"`weakref-support`." +"Extension types can easily be made to support weak references; " +"see :ref:`weakref-support`." msgstr "" #: library/weakref.rst:93 @@ -147,12 +147,12 @@ msgstr "" 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." +"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 "" #: library/weakref.rst:108 @@ -172,9 +172,9 @@ msgstr "" #: library/weakref.rst:116 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`." +"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 "" #: library/weakref.rst:121 @@ -210,8 +210,8 @@ msgid "" "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 prevents their use as dictionary " -"keys. *callback* is the same as the parameter of the same name to the :func:" -"`ref` function." +"keys. *callback* is the same as the parameter of the same name to " +"the :func:`ref` function." msgstr "" #: library/weakref.rst:149 @@ -378,21 +378,21 @@ msgstr "" 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:`~object." -"__del__` method or a weak reference's callback." +"handled in the same way as exceptions raised from an " +"object's :meth:`~object.__del__` method or a weak reference's callback." msgstr "" #: library/weakref.rst:286 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." +"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 "" #: library/weakref.rst:290 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 " +"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 "" @@ -468,15 +468,15 @@ msgstr "" #: library/weakref.rst:366 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:" +"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 "" #: library/weakref.rst:380 msgid "" -"If the referent no longer exists, calling the reference object returns :" -"const:`None`:" +"If the referent no longer exists, calling the reference object " +"returns :const:`None`:" msgstr "" #: library/weakref.rst:387 @@ -509,11 +509,11 @@ msgstr "" #: library/weakref.rst:405 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." +"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 "" #: library/weakref.rst:411 diff --git a/library/webbrowser.po b/library/webbrowser.po index a292fe9cd..88d4363a2 100644 --- a/library/webbrowser.po +++ b/library/webbrowser.po @@ -143,8 +143,8 @@ msgstr "" #: library/webbrowser.rst:99 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 " +"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``." @@ -152,10 +152,10 @@ msgstr "" #: library/webbrowser.rst:105 msgid "" -"Setting *preferred* to ``True`` makes this browser a preferred result for a :" -"func:`get` call with no argument. Otherwise, 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 " +"Setting *preferred* to ``True`` makes this browser a preferred result for " +"a :func:`get` call with no argument. Otherwise, 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 "" @@ -335,9 +335,9 @@ 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." +"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 "" #: library/webbrowser.rst:168 @@ -402,8 +402,8 @@ msgstr "" #: library/webbrowser.rst:218 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`." +"possible, otherwise, open *url* in the only browser window. " +"Alias :func:`open_new`." msgstr "" #: library/webbrowser.rst:225 diff --git a/library/winreg.po b/library/winreg.po index 6356548a2..86814b991 100644 --- a/library/winreg.po +++ b/library/winreg.po @@ -72,8 +72,8 @@ msgstr "" #: library/winreg.rst:77 library/winreg.rst:109 msgid "" -"The return value is the handle of the opened key. If the function fails, an :" -"exc:`OSError` exception is raised." +"The return value is the handle of the opened key. If the function fails, " +"an :exc:`OSError` exception is raised." msgstr "" #: library/winreg.rst:56 @@ -135,8 +135,8 @@ msgstr "" #: library/winreg.rst:100 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." +"desired security access for the key. Default is :const:`KEY_WRITE`. " +"See :ref:`Access Rights ` for other allowed values." msgstr "" #: library/winreg.rst:145 @@ -284,8 +284,8 @@ msgstr "" #: library/winreg.rst:247 msgid "" -"Expands environment variable placeholders ``%NAME%`` in strings like :const:" -"`REG_EXPAND_SZ`::" +"Expands environment variable placeholders ``%NAME%`` in strings " +"like :const:`REG_EXPAND_SZ`::" msgstr "" #: library/winreg.rst:250 @@ -296,8 +296,8 @@ msgstr "" #: library/winreg.rst:253 msgid "" -"Raises an :ref:`auditing event ` ``winreg." -"ExpandEnvironmentStrings`` with argument ``str``." +"Raises an :ref:`auditing event ` " +"``winreg.ExpandEnvironmentStrings`` with argument ``str``." msgstr "" #: library/winreg.rst:258 @@ -308,11 +308,11 @@ msgstr "" 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." +"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 "" #: library/winreg.rst:272 @@ -346,10 +346,11 @@ msgstr "" #: library/winreg.rst:290 msgid "" -"A call to :func:`LoadKey` fails if the calling process does not have the :c:" -"data:`!SE_RESTORE_PRIVILEGE` privilege. Note that privileges are different " -"from permissions -- see the `RegLoadKey documentation `__ for more details." +"A call to :func:`LoadKey` fails if the calling process does not have " +"the :c:data:`!SE_RESTORE_PRIVILEGE` privilege. Note that privileges are " +"different from permissions -- see the `RegLoadKey documentation `__ for more " +"details." msgstr "" #: library/winreg.rst:296 @@ -381,8 +382,8 @@ msgstr "" #: library/winreg.rst:314 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." +"desired security access for the key. Default is :const:`KEY_READ`. " +"See :ref:`Access Rights ` for other allowed values." msgstr "" #: library/winreg.rst:318 @@ -443,8 +444,8 @@ msgstr "" 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." +"underlying API call doesn't return the type, so always " +"use :func:`QueryValueEx` if possible." msgstr "" #: library/winreg.rst:400 @@ -473,8 +474,8 @@ msgstr "" #: library/winreg.rst:395 msgid "" -"An integer giving the registry type for this value (see table in docs for :" -"meth:`SetValueEx`)" +"An integer giving the registry type for this value (see table in docs " +"for :meth:`SetValueEx`)" msgstr "" #: library/winreg.rst:405 @@ -522,8 +523,8 @@ msgstr "" #: library/winreg.rst:437 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." +"must be :const:`REG_SZ`, meaning only strings are supported. Use " +"the :func:`SetValueEx` function for support for other data types." msgstr "" #: library/winreg.rst:471 @@ -545,8 +546,8 @@ msgstr "" #: library/winreg.rst:450 msgid "" -"The key identified by the *key* parameter must have been opened with :const:" -"`KEY_SET_VALUE` access." +"The key identified by the *key* parameter must have been opened " +"with :const:`KEY_SET_VALUE` access." msgstr "" #: library/winreg.rst:483 @@ -705,28 +706,28 @@ msgstr "" #: library/winreg.rst:595 msgid "" -"For more information, see `Registry Key Security and Access `__." +"For more information, see `Registry Key Security and Access `__." msgstr "" #: library/winreg.rst:600 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." +"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 "" #: library/winreg.rst:607 msgid "" -"Combines the STANDARD_RIGHTS_WRITE, :const:`KEY_SET_VALUE`, and :const:" -"`KEY_CREATE_SUB_KEY` access rights." +"Combines the STANDARD_RIGHTS_WRITE, :const:`KEY_SET_VALUE`, " +"and :const:`KEY_CREATE_SUB_KEY` access rights." msgstr "" #: library/winreg.rst:612 msgid "" -"Combines the STANDARD_RIGHTS_READ, :const:`KEY_QUERY_VALUE`, :const:" -"`KEY_ENUMERATE_SUB_KEYS`, and :const:`KEY_NOTIFY` values." +"Combines the " +"STANDARD_RIGHTS_READ, :const:`KEY_QUERY_VALUE`, :const:`KEY_ENUMERATE_SUB_KEYS`, " +"and :const:`KEY_NOTIFY` values." msgstr "" #: library/winreg.rst:617 @@ -860,8 +861,9 @@ msgstr "" #: library/winreg.rst:739 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." +"object is destroyed. To guarantee cleanup, you can call either " +"the :meth:`~PyHKEY.Close` method on the object, or the :func:`CloseKey` " +"function." msgstr "" #: library/winreg.rst:743 @@ -899,10 +901,10 @@ msgstr "" #: library/winreg.rst:759 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 " +"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 "" @@ -940,9 +942,9 @@ msgstr "" #: library/winreg.rst:790 msgid "" -"The HKEY object implements :meth:`~object.__enter__` and :meth:`~object." -"__exit__` and thus supports the context protocol for the :keyword:`with` " -"statement::" +"The HKEY object implements :meth:`~object.__enter__` " +"and :meth:`~object.__exit__` and thus supports the context protocol for " +"the :keyword:`with` statement::" msgstr "" #: library/winreg.rst:794 diff --git a/library/winsound.po b/library/winsound.po index a87cee3f0..543007100 100644 --- a/library/winsound.po +++ b/library/winsound.po @@ -43,8 +43,8 @@ msgid "" "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." +"waveform sound is stopped. If the system indicates an " +"error, :exc:`RuntimeError` is raised." msgstr "" #: library/winsound.rst:38 @@ -61,16 +61,16 @@ msgstr "" #: library/winsound.rst:49 msgid "" -"The *sound* parameter is the name of a WAV file. Do not use with :const:" -"`SND_ALIAS`." +"The *sound* parameter is the name of a WAV file. Do not use " +"with :const:`SND_ALIAS`." msgstr "" #: 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`." +"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 "" #: library/winsound.rst:60 @@ -157,8 +157,8 @@ msgstr "" #: 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`." +"a combination of this flag and :const:`SND_ASYNC` will " +"raise :exc:`RuntimeError`." msgstr "" #: library/winsound.rst:107 diff --git a/library/wsgiref.po b/library/wsgiref.po index 1a981146b..fb45b905f 100644 --- a/library/wsgiref.po +++ b/library/wsgiref.po @@ -67,8 +67,9 @@ msgid "" "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 and :data:`~wsgiref." -"types.WSGIEnvironment` for a type alias that can be used in type annotations." +"please see :pep:`3333` for a detailed specification " +"and :data:`~wsgiref.types.WSGIEnvironment` for a type alias that can be used " +"in type annotations." msgstr "" #: library/wsgiref.rst:56 @@ -122,11 +123,11 @@ msgid "" "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``." +"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 "" #: library/wsgiref.rst:100 @@ -147,9 +148,9 @@ msgstr "" 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." +"``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 "" #: library/wsgiref.rst:118 @@ -205,15 +206,16 @@ msgid "" "used to convert a file-like object to an :term:`iterator`. The resulting " "objects are :term:`iterable`\\ s. 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." +"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 "" #: library/wsgiref.rst:166 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." +"a :meth:`close` method, and it will invoke the *filelike* " +"object's :meth:`close` method when called." msgstr "" #: library/wsgiref.rst:172 @@ -252,15 +254,14 @@ msgstr "" #: library/wsgiref.rst:203 msgid "" -":class:`Headers` objects support typical mapping operations including :meth:" -"`~object.__getitem__`, :meth:`~dict.get`, :meth:`~object.__setitem__`, :meth:" -"`~dict.setdefault`, :meth:`~object.__delitem__` and :meth:`~object." -"__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." +":class:`Headers` objects support typical mapping operations " +"including :meth:`~object.__getitem__`, :meth:`~dict.get`, :meth:`~object.__setitem__`, :meth:`~dict.setdefault`, :meth:`~object.__delitem__` " +"and :meth:`~object.__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 "" #: library/wsgiref.rst:213 @@ -273,13 +274,13 @@ msgstr "" #: library/wsgiref.rst:218 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." +":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 "" #: library/wsgiref.rst:225 @@ -293,9 +294,10 @@ msgstr "" #: library/wsgiref.rst:231 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:" +"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 "" #: library/wsgiref.rst:238 @@ -355,8 +357,8 @@ msgid "" "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`.)" +"request. (E.g., using the :func:`shift_path_info` function " +"from :mod:`wsgiref.util`.)" msgstr "" #: library/wsgiref.rst:288 @@ -364,8 +366,8 @@ 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`." +"*handler_class*. *app* must be a WSGI application object, as defined " +"by :pep:`3333`." msgstr "" #: library/wsgiref.rst:295 @@ -393,15 +395,16 @@ msgstr "" #: library/wsgiref.rst:318 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." +"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 "" #: library/wsgiref.rst:323 msgid "" -"You do not normally need to call this constructor, as the :func:" -"`make_server` function can handle all the details for you." +"You do not normally need to call this constructor, as " +"the :func:`make_server` function can handle all the details for you." msgstr "" #: library/wsgiref.rst:326 @@ -423,25 +426,26 @@ msgstr "" #: library/wsgiref.rst:341 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." +"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 "" #: library/wsgiref.rst:348 msgid "" "Create an HTTP handler for the given *request* (i.e. a socket), " -"*client_address* (a ``(host,port)`` tuple), and *server* (:class:" -"`WSGIServer` instance)." +"*client_address* (a ``(host,port)`` tuple), and *server* " +"(:class:`WSGIServer` instance)." msgstr "" #: library/wsgiref.rst:351 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:" +"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 "" #: library/wsgiref.rst:360 @@ -474,10 +478,10 @@ msgstr "" #: library/wsgiref.rst:389 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 " +"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 "" @@ -571,10 +575,10 @@ msgstr "" #: library/wsgiref.rst:470 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." +"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 "" #: library/wsgiref.rst:478 @@ -605,18 +609,18 @@ msgstr "" #: library/wsgiref.rst:494 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." +"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 "" #: library/wsgiref.rst:504 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." +"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 "" #: library/wsgiref.rst:510 @@ -638,12 +642,11 @@ msgstr "" #: library/wsgiref.rst:523 msgid "" "This class is a subclass of :class:`BaseHandler`. It overrides the :meth:`!" -"__init__`, :meth:`~BaseHandler.get_stdin`, :meth:`~BaseHandler.get_stderr`, :" -"meth:`~BaseHandler.add_cgi_vars`, :meth:`~BaseHandler._write`, and :meth:" -"`~BaseHandler._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." +"__init__`, :meth:`~BaseHandler.get_stdin`, :meth:`~BaseHandler.get_stderr`, :meth:`~BaseHandler.add_cgi_vars`, :meth:`~BaseHandler._write`, " +"and :meth:`~BaseHandler._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 "" #: library/wsgiref.rst:532 @@ -719,8 +722,8 @@ 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." +"additional information before attempting to create a " +"customized :class:`BaseHandler` subclass." msgstr "" #: library/wsgiref.rst:594 @@ -751,10 +754,10 @@ msgstr "" #: library/wsgiref.rst:620 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 " +"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 "" @@ -776,9 +779,9 @@ msgstr "" #: library/wsgiref.rst:642 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." +"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 "" #: library/wsgiref.rst:650 @@ -807,8 +810,8 @@ msgstr "" #: library/wsgiref.rst:671 msgid "" -"The maximum number of frames to include in tracebacks output by the default :" -"meth:`log_exception` method. If ``None``, all frames are included." +"The maximum number of frames to include in tracebacks output by the " +"default :meth:`log_exception` method. If ``None``, all frames are included." msgstr "" #: library/wsgiref.rst:677 @@ -826,9 +829,10 @@ msgstr "" #: library/wsgiref.rst:684 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." +"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 "" #: library/wsgiref.rst:688 @@ -867,9 +871,9 @@ msgstr "" #: library/wsgiref.rst:719 msgid "" -"A ``wsgi.file_wrapper`` factory, compatible with :class:`wsgiref.types." -"FileWrapper`, or ``None``. The default value of this attribute is the :" -"class:`wsgiref.util.FileWrapper` class." +"A ``wsgi.file_wrapper`` factory, compatible " +"with :class:`wsgiref.types.FileWrapper`, or ``None``. The default value of " +"this attribute is the :class:`wsgiref.util.FileWrapper` class." msgstr "" #: library/wsgiref.rst:726 @@ -909,8 +913,8 @@ msgstr "" #: library/wsgiref.rst:755 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 " +"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 " @@ -931,8 +935,8 @@ msgstr "" #: library/wsgiref.rst:778 msgid "" -"This module provides various types for static type checking as described in :" -"pep:`3333`." +"This module provides various types for static type checking as described " +"in :pep:`3333`." msgstr "" #: library/wsgiref.rst:786 diff --git a/library/xdrlib.po b/library/xdrlib.po index 003ed6abd..827c15be6 100644 --- a/library/xdrlib.po +++ b/library/xdrlib.po @@ -46,8 +46,8 @@ msgstr "" #: library/xdrlib.rst:31 msgid "" -":class:`Packer` is the class for packing data into XDR representation. The :" -"class:`Packer` class is instantiated with no arguments." +":class:`Packer` is the class for packing data into XDR representation. " +"The :class:`Packer` class is instantiated with no arguments." msgstr "" #: library/xdrlib.rst:37 @@ -95,8 +95,9 @@ 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`." +"are " +"supported: :meth:`pack_uint`, :meth:`pack_int`, :meth:`pack_enum`, :meth:`pack_bool`, :meth:`pack_uhyper`, " +"and :meth:`pack_hyper`." msgstr "" #: library/xdrlib.rst:77 @@ -126,8 +127,8 @@ msgstr "" #: library/xdrlib.rst:101 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`." +"packed as an unsigned integer, then the string data is packed " +"with :meth:`pack_fstring`." msgstr "" #: library/xdrlib.rst:108 @@ -225,8 +226,8 @@ msgstr "" #: library/xdrlib.rst:195 msgid "" -"Unpacks a double-precision floating point number, similarly to :meth:" -"`unpack_float`." +"Unpacks a double-precision floating point number, similarly " +"to :meth:`unpack_float`." msgstr "" #: library/xdrlib.rst:198 @@ -242,8 +243,8 @@ msgstr "" #: library/xdrlib.rst:209 msgid "" -"Unpacks and returns a fixed length opaque data stream, similarly to :meth:" -"`unpack_fstring`." +"Unpacks and returns a fixed length opaque data stream, similarly " +"to :meth:`unpack_fstring`." msgstr "" #: library/xdrlib.rst:215 @@ -255,14 +256,14 @@ msgstr "" #: library/xdrlib.rst:222 msgid "" -"Unpacks and returns a variable length opaque data string, similarly to :meth:" -"`unpack_string`." +"Unpacks and returns a variable length opaque data string, similarly " +"to :meth:`unpack_string`." msgstr "" #: library/xdrlib.rst:228 msgid "" -"Unpacks and returns a variable length byte stream, similarly to :meth:" -"`unpack_string`." +"Unpacks and returns a variable length byte stream, similarly " +"to :meth:`unpack_string`." msgstr "" #: library/xdrlib.rst:231 @@ -302,8 +303,8 @@ msgstr "" #: library/xdrlib.rst:267 msgid "" -"The base exception class. :exc:`Error` has a single public attribute :attr:" -"`msg` containing the description of the error." +"The base exception class. :exc:`Error` has a single public " +"attribute :attr:`msg` containing the description of the error." msgstr "" #: library/xdrlib.rst:273 diff --git a/library/xml.dom.minidom.po b/library/xml.dom.minidom.po index cd3c29579..51b653d44 100644 --- a/library/xml.dom.minidom.po +++ b/library/xml.dom.minidom.po @@ -29,8 +29,8 @@ 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." +"Users who are not already proficient with the DOM should consider using " +"the :mod:`xml.etree.ElementTree` module for their XML processing instead." msgstr "" #: library/xml.dom.minidom.rst:24 @@ -42,8 +42,8 @@ msgstr "" #: 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::" +"DOM applications typically start by parsing some XML into a DOM. " +"With :mod:`xml.dom.minidom`, this is done through the parse functions::" msgstr "" #: library/xml.dom.minidom.rst:32 @@ -81,8 +81,8 @@ msgstr "" #: 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`." +"an :class:`io.StringIO` object for the string and passes that on " +"to :func:`parse`." msgstr "" #: library/xml.dom.minidom.rst:61 @@ -105,10 +105,10 @@ msgstr "" #: 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::" +"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 "" #: library/xml.dom.minidom.rst:77 @@ -127,9 +127,9 @@ msgstr "" 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::" +"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 "" #: library/xml.dom.minidom.rst:92 @@ -140,12 +140,12 @@ msgstr "" #: 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 essentially useless. " -"Otherwise, Python's garbage collector will eventually take care of the " -"objects in the tree." +"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 essentially " +"useless. Otherwise, Python's garbage collector will eventually take care of " +"the objects in the tree." msgstr "" #: library/xml.dom.minidom.rst:104 @@ -164,9 +164,9 @@ msgstr "" #: 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`." +"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 "" #: library/xml.dom.minidom.rst:120 @@ -182,8 +182,8 @@ msgstr "" #: 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::" +"statement. The following code will automatically unlink *dom* when " +"the :keyword:`!with` block is exited::" msgstr "" #: library/xml.dom.minidom.rst:131 @@ -262,8 +262,8 @@ msgstr "" #: library/xml.dom.minidom.rst:190 msgid "" -"The *encoding* argument behaves like the corresponding argument of :meth:" -"`toxml`." +"The *encoding* argument behaves like the corresponding argument " +"of :meth:`toxml`." msgstr "" #: library/xml.dom.minidom.rst:195 @@ -415,8 +415,8 @@ msgstr "" #: library/xml.dom.minidom.rst:249 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`." +"Instead, :mod:`xml.dom.minidom` uses standard Python exceptions such " +"as :exc:`TypeError` and :exc:`AttributeError`." msgstr "" #: library/xml.dom.minidom.rst:253 diff --git a/library/xml.dom.po b/library/xml.dom.po index fb69b0951..1b52e522f 100644 --- a/library/xml.dom.po +++ b/library/xml.dom.po @@ -93,8 +93,8 @@ msgstr "" #: library/xml.dom.rst:70 msgid "" -"`Document Object Model (DOM) Level 2 Specification `_" +"`Document Object Model (DOM) Level 2 Specification `_" msgstr "" #: library/xml.dom.rst:71 @@ -193,8 +193,8 @@ msgid "" "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 " +"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 "" @@ -362,8 +362,9 @@ msgstr "" 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." +"DOM Level 2 added the ability to create new :class:`Document` " +"and :class:`DocumentType` objects using the :class:`DOMImplementation` as " +"well." msgstr "" #: library/xml.dom.rst:213 @@ -374,12 +375,12 @@ msgstr "" #: 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." +"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 "" #: library/xml.dom.rst:229 @@ -401,10 +402,8 @@ msgstr "" #: 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`. " +"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 "" @@ -436,8 +435,8 @@ msgstr "" #: 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 " +"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 "" @@ -480,9 +479,9 @@ msgstr "" 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 " +"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 "" @@ -533,9 +532,10 @@ msgstr "" #: 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." +"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 "" #: library/xml.dom.rst:384 @@ -546,9 +546,9 @@ msgstr "" #: 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." +"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 "" #: library/xml.dom.rst:397 @@ -565,9 +565,10 @@ msgstr "" 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." +"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 "" #: library/xml.dom.rst:412 @@ -591,17 +592,17 @@ msgstr "" 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 " +"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 "" #: 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." +"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 "" #: library/xml.dom.rst:443 @@ -612,11 +613,11 @@ msgstr "" 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." +"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 "" #: library/xml.dom.rst:453 @@ -694,8 +695,8 @@ msgstr "" 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`." +"You need to explicitly insert it with one of the other methods such " +"as :meth:`insertBefore` or :meth:`appendChild`." msgstr "" #: library/xml.dom.rst:532 @@ -722,9 +723,9 @@ msgstr "" #: 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." +"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 "" #: library/xml.dom.rst:561 @@ -804,8 +805,8 @@ msgstr "" #: library/xml.dom.rst:641 msgid "" -"Remove an attribute by name. If there is no matching attribute, a :exc:" -"`NotFoundErr` is raised." +"Remove an attribute by name. If there is no matching attribute, " +"a :exc:`NotFoundErr` is raised." msgstr "" #: library/xml.dom.rst:647 @@ -828,8 +829,8 @@ msgstr "" 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." +"the old attribute node will be returned. If *newAttr* is already in " +"use, :exc:`InuseAttributeErr` will be raised." msgstr "" #: library/xml.dom.rst:672 @@ -874,8 +875,8 @@ msgstr "" #: library/xml.dom.rst:713 msgid "" -"The text value of the attribute. This is a synonym for the :attr:" -"`nodeValue` attribute." +"The text value of the attribute. This is a synonym for " +"the :attr:`nodeValue` attribute." msgstr "" #: library/xml.dom.rst:720 @@ -930,9 +931,9 @@ msgstr "" 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." +"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 "" #: library/xml.dom.rst:768 @@ -983,11 +984,11 @@ msgstr "" #: 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." +"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 "" #: library/xml.dom.rst:816 @@ -995,8 +996,8 @@ 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." +"specific exception, each of which carries the appropriate value for " +"the :attr:`code` attribute." msgstr "" #: library/xml.dom.rst:825 @@ -1314,12 +1315,13 @@ msgstr "" #: 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`." +"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 "" #: library/xml.dom.rst:1015 @@ -1346,7 +1348,7 @@ msgstr "" #: 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." +"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 "" diff --git a/library/xml.dom.pulldom.po b/library/xml.dom.pulldom.po index ffcc000cc..6b4ec2088 100644 --- a/library/xml.dom.pulldom.po +++ b/library/xml.dom.pulldom.po @@ -115,8 +115,9 @@ msgstr "" #: library/xml.dom.pulldom.rst:65 msgid "" -"``node`` is an object of type :class:`xml.dom.minidom.Document`, :class:`xml." -"dom.minidom.Element` or :class:`xml.dom.minidom.Text`." +"``node`` is an object of " +"type :class:`xml.dom.minidom.Document`, :class:`xml.dom.minidom.Element` " +"or :class:`xml.dom.minidom.Text`." msgstr "" #: library/xml.dom.pulldom.rst:68 @@ -127,8 +128,9 @@ msgid "" "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." +"in the document at any given point) or to make use of " +"the :func:`DOMEventStream.expandNode` method and switch to DOM-related " +"processing." msgstr "" #: library/xml.dom.pulldom.rst:85 @@ -176,12 +178,13 @@ msgstr "" #: library/xml.dom.pulldom.rst:122 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 information about its " -"children, unless :func:`expandNode` is called." +"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 information about its children, " +"unless :func:`expandNode` is called." msgstr "" #: library/xml.dom.pulldom.rst:132 diff --git a/library/xml.etree.elementtree.po b/library/xml.etree.elementtree.po index 8ae371ce2..6b216d450 100644 --- a/library/xml.etree.elementtree.po +++ b/library/xml.etree.elementtree.po @@ -63,12 +63,12 @@ msgstr "" #: library/xml.etree.elementtree.rst:39 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." +"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 "" #: library/xml.etree.elementtree.rst:50 @@ -129,10 +129,10 @@ msgstr "" #: library/xml.etree.elementtree.rst:90 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." +":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 "" #: library/xml.etree.elementtree.rst:94 @@ -191,9 +191,9 @@ msgstr "" #: library/xml.etree.elementtree.rst:134 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 " +"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." @@ -241,9 +241,9 @@ msgstr "" #: library/xml.etree.elementtree.rst:169 msgid "" -"Where *immediate* feedback through events is wanted, calling method :meth:" -"`XMLPullParser.flush` can help reduce delay; please make sure to study the " -"related security notes." +"Where *immediate* feedback through events is wanted, calling " +"method :meth:`XMLPullParser.flush` can help reduce delay; please make sure " +"to study the related security notes." msgstr "" #: library/xml.etree.elementtree.rst:175 @@ -432,11 +432,11 @@ msgstr "" #: library/xml.etree.elementtree.rst:309 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." +"XML_namespace>`__, 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 "" #: library/xml.etree.elementtree.rst:317 @@ -467,8 +467,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:338 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`::" +"every tag or attribute in the xpath of a :meth:`~Element.find` " +"or :meth:`~Element.findall`::" msgstr "" #: library/xml.etree.elementtree.rst:342 @@ -520,10 +520,10 @@ msgstr "" #: library/xml.etree.elementtree.rst:377 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." +"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 "" #: library/xml.etree.elementtree.rst:383 library/xml.etree.elementtree.rst:777 @@ -533,8 +533,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:385 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::" +"module. We'll be using the ``countrydata`` XML document from " +"the :ref:`Parsing XML ` section::" msgstr "" #: library/xml.etree.elementtree.rst:389 @@ -804,8 +804,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:539 msgid "" -"*rewrite_prefixes*: set to true to replace namespace prefixes by " -"\"n{number}\"" +"*rewrite_prefixes*: set to true to replace namespace prefixes by \"n{number}" +"\"" msgstr "" #: library/xml.etree.elementtree.rst:541 @@ -848,8 +848,8 @@ msgstr "" 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." +"comment nodes if they have been inserted into to the tree using one of " +"the :class:`Element` methods." msgstr "" #: library/xml.etree.elementtree.rst:569 @@ -878,8 +878,8 @@ msgstr "" msgid "" "Parses an XML section from a string constant. Same as :func:`XML`. *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." +"If not given, the standard :class:`XMLParser` parser is used. Returns " +"an :class:`Element` instance." msgstr "" #: library/xml.etree.elementtree.rst:592 @@ -956,8 +956,8 @@ msgstr "" 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." +"not given, the standard :class:`XMLParser` parser is used. Returns " +"an :class:`ElementTree` instance." msgstr "" #: library/xml.etree.elementtree.rst:666 @@ -1037,8 +1037,8 @@ msgid "" "``\"xml\"``). *xml_declaration*, *default_namespace* and " "*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)``." +"does not guarantee any specific sequence, except that " +"``b\"\".join(tostringlist(element)) == tostring(element)``." msgstr "" #: library/xml.etree.elementtree.rst:746 @@ -1051,17 +1051,18 @@ msgstr "" 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." +"data. *parser* is an optional parser instance. If not given, the " +"standard :class:`XMLParser` parser is used. Returns an :class:`Element` " +"instance." msgstr "" #: library/xml.etree.elementtree.rst:761 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." +"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 "" #: library/xml.etree.elementtree.rst:771 @@ -1070,8 +1071,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:773 msgid "" -"This module provides limited support for `XInclude directives `_, via the :mod:`xml.etree.ElementInclude` helper " +"This module provides limited support for `XInclude directives `_, via the :mod:`xml.etree.ElementInclude` helper " "module. This module can be used to insert subtrees and text strings into " "element trees, based on information in the tree." msgstr "" @@ -1101,8 +1102,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:790 msgid "" -"To process this file, load it as usual, and pass the root element to the :" -"mod:`xml.etree.ElementTree` module:" +"To process this file, load it as usual, and pass the root element to " +"the :mod:`xml.etree.ElementTree` module:" msgstr "" #: library/xml.etree.elementtree.rst:792 @@ -1296,8 +1297,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:962 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`." +"subelements. Raises :exc:`TypeError` if *subelement* is not " +"an :class:`Element`." msgstr "" #: library/xml.etree.elementtree.rst:969 @@ -1337,8 +1338,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:1006 msgid "" -"Inserts *subelement* at the given position in this element. Raises :exc:" -"`TypeError` if *subelement* is not an :class:`Element`." +"Inserts *subelement* at the given position in this element. " +"Raises :exc:`TypeError` if *subelement* is not an :class:`Element`." msgstr "" #: library/xml.etree.elementtree.rst:1012 @@ -1380,8 +1381,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:1052 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__`." +"for working with " +"subelements: :meth:`~object.__delitem__`, :meth:`~object.__getitem__`, :meth:`~object.__setitem__`, :meth:`~object.__len__`." msgstr "" #: library/xml.etree.elementtree.rst:1057 @@ -1423,8 +1424,8 @@ msgid "" "infoset/>`_ explicitly excludes the attribute order from conveying " "information. Code should be prepared to deal with any ordering on input. In " "cases where deterministic XML output is required, e.g. for cryptographic " -"signing or test data sets, canonical serialisation is available with the :" -"func:`canonicalize` function." +"signing or test data sets, canonical serialisation is available with " +"the :func:`canonicalize` function." msgstr "" #: library/xml.etree.elementtree.rst:1087 @@ -1510,8 +1511,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:1173 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 " +"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 " @@ -1590,8 +1591,8 @@ msgid "" "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." +"interpreted as a URI, and this argument is interpreted as a local " +"name. :class:`QName` instances are opaque." msgstr "" #: library/xml.etree.elementtree.rst:1251 @@ -1701,13 +1702,13 @@ msgstr "" #: library/xml.etree.elementtree.rst:1363 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. If " -"*encoding* [1]_ is given, the value overrides the encoding specified in the " -"XML file." +"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. " +"If *encoding* [1]_ is given, the value overrides the encoding specified in " +"the XML file." msgstr "" #: library/xml.etree.elementtree.rst:1371 @@ -1734,16 +1735,18 @@ msgid "" "ensure more immediate feedback, in particular with Expat >=2.6.0. The " "implementation of :meth:`flush` temporarily disables reparse deferral with " "Expat (if currently enabled) and triggers a reparse. Disabling reparse " -"deferral has security consequences; please see :meth:`xml.parsers.expat." -"xmlparser.SetReparseDeferralEnabled` for details." +"deferral has security consequences; please " +"see :meth:`xml.parsers.expat.xmlparser.SetReparseDeferralEnabled` for " +"details." msgstr "" #: library/xml.etree.elementtree.rst:1397 #: library/xml.etree.elementtree.rst:1475 msgid "" "Note that :meth:`flush` has been backported to some prior releases of " -"CPython as a security fix. Check for availability of :meth:`flush` using :" -"func:`hasattr` if used in code running across a variety of Python versions." +"CPython as a security fix. Check for availability of :meth:`flush` " +"using :func:`hasattr` if used in code running across a variety of Python " +"versions." msgstr "" #: library/xml.etree.elementtree.rst:1405 @@ -1814,10 +1817,10 @@ msgstr "" #: library/xml.etree.elementtree.rst:1484 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`." +"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 "" #: library/xml.etree.elementtree.rst:1491 @@ -1879,8 +1882,8 @@ msgstr "" #: library/xml.etree.elementtree.rst:1537 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." +"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 "" #: library/xml.etree.elementtree.rst:1542 diff --git a/library/xml.po b/library/xml.po index 38f6f8f70..3664ac0d5 100644 --- a/library/xml.po +++ b/library/xml.po @@ -32,8 +32,8 @@ msgstr "" #: 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:`defusedxml-package` sections." +"data. If you need to parse untrusted or unauthenticated data see " +"the :ref:`xml-vulnerabilities` and :ref:`defusedxml-package` sections." msgstr "" #: library/xml.rst:25 @@ -182,14 +182,14 @@ msgstr "" msgid "" "Expat 2.4.1 and newer is not vulnerable to the \"billion laughs\" and " "\"quadratic blowup\" vulnerabilities. Items still listed as vulnerable due " -"to potential reliance on system-provided libraries. Check :const:`!pyexpat." -"EXPAT_VERSION`." +"to potential reliance on system-provided libraries. Check :const:`!" +"pyexpat.EXPAT_VERSION`." msgstr "" #: library/xml.rst:78 msgid "" -":mod:`xml.etree.ElementTree` doesn't expand external entities and raises a :" -"exc:`~xml.etree.ElementTree.ParseError` when an entity occurs." +":mod:`xml.etree.ElementTree` doesn't expand external entities and raises " +"a :exc:`~xml.etree.ElementTree.ParseError` when an entity occurs." msgstr "" #: library/xml.rst:80 @@ -212,8 +212,8 @@ msgstr "" msgid "" "Expat 2.6.0 and newer is not vulnerable to denial of service through " "quadratic runtime caused by parsing large tokens. Items still listed as " -"vulnerable due to potential reliance on system-provided libraries. Check :" -"const:`!pyexpat.EXPAT_VERSION`." +"vulnerable due to potential reliance on system-provided libraries. " +"Check :const:`!pyexpat.EXPAT_VERSION`." msgstr "" #: library/xml.rst:92 @@ -268,8 +268,8 @@ msgstr "" msgid "" "Expat needs to re-parse unfinished tokens; without the protection introduced " "in Expat 2.6.0, this can lead to quadratic runtime that can be used to cause " -"denial of service in the application parsing XML. The issue is known as :cve:" -"`2023-52425`." +"denial of service in the application parsing XML. The issue is known " +"as :cve:`2023-52425`." msgstr "" #: library/xml.rst:129 diff --git a/library/xml.sax.handler.po b/library/xml.sax.handler.po index d85bac104..dd783ee07 100644 --- a/library/xml.sax.handler.po +++ b/library/xml.sax.handler.po @@ -330,11 +330,11 @@ msgstr "" #: library/xml.sax.handler.rst:228 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." +"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 "" #: library/xml.sax.handler.rst:238 @@ -344,8 +344,8 @@ msgstr "" #: library/xml.sax.handler.rst:240 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." +"after the corresponding :meth:`endElement` event, but the order " +"of :meth:`endPrefixMapping` events is not otherwise guaranteed." msgstr "" #: library/xml.sax.handler.rst:247 @@ -355,12 +355,12 @@ msgstr "" #: library/xml.sax.handler.rst:249 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." +"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 "" #: library/xml.sax.handler.rst:261 @@ -381,9 +381,9 @@ msgstr "" 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 " +"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 " diff --git a/library/xml.sax.po b/library/xml.sax.po index dc2c94ca4..37bd1a984 100644 --- a/library/xml.sax.po +++ b/library/xml.sax.po @@ -44,9 +44,9 @@ msgid "" "The SAX parser no longer processes general external entities by default to " "increase security. Before, the parser created network connections to fetch " "remote files or loaded local files from the file system for DTD and " -"entities. The feature can be enabled again with method :meth:`~xml.sax." -"xmlreader.XMLReader.setFeature` on the parser object and argument :data:" -"`~xml.sax.handler.feature_external_ges`." +"entities. The feature can be enabled again with " +"method :meth:`~xml.sax.xmlreader.XMLReader.setFeature` on the parser object " +"and argument :data:`~xml.sax.handler.feature_external_ges`." msgstr "" #: library/xml.sax.rst:36 @@ -57,9 +57,9 @@ msgstr "" 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 " -"an iterable 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." +"an iterable 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 "" #: library/xml.sax.rst:47 @@ -108,14 +108,14 @@ msgid "" "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." +"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 "" #: library/xml.sax.rst:95 @@ -129,10 +129,10 @@ 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." +"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 "" #: library/xml.sax.rst:109 @@ -150,25 +150,28 @@ msgstr "" #: library/xml.sax.rst:118 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." +"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 "" #: library/xml.sax.rst:128 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." +"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 "" #: library/xml.sax.rst:136 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." +"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 "" #: library/xml.sax.rst:145 diff --git a/library/xml.sax.reader.po b/library/xml.sax.reader.po index 94d74aa77..994aa420c 100644 --- a/library/xml.sax.reader.po +++ b/library/xml.sax.reader.po @@ -40,10 +40,10 @@ msgstr "" 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." +"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 "" #: library/xml.sax.reader.rst:33 @@ -90,8 +90,9 @@ msgstr "" #: 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." +"Applications will create objects of this class for use in " +"the :meth:`XMLReader.parse` method and for returning from " +"EntityResolver.resolveEntity." msgstr "" #: library/xml.sax.reader.rst:67 @@ -103,8 +104,8 @@ msgstr "" #: 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 " +"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 " @@ -114,12 +115,13 @@ msgstr "" #: 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 " +"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`)." +"they appear in the original document. This class implements " +"the :class:`AttributesNS` interface (see section :ref:`attributes-ns-" +"objects`)." msgstr "" #: library/xml.sax.reader.rst:96 @@ -154,8 +156,9 @@ msgstr "" #: library/xml.sax.reader.rst:124 msgid "" -"Set the current :class:`~xml.sax.handler.ContentHandler`. If no :class:" -"`~xml.sax.handler.ContentHandler` is set, content events will be discarded." +"Set the current :class:`~xml.sax.handler.ContentHandler`. If " +"no :class:`~xml.sax.handler.ContentHandler` is set, content events will be " +"discarded." msgstr "" #: library/xml.sax.reader.rst:131 @@ -164,8 +167,8 @@ msgstr "" #: library/xml.sax.reader.rst:136 msgid "" -"Set the current :class:`~xml.sax.handler.DTDHandler`. If no :class:`~xml." -"sax.handler.DTDHandler` is set, DTD events will be discarded." +"Set the current :class:`~xml.sax.handler.DTDHandler`. If " +"no :class:`~xml.sax.handler.DTDHandler` is set, DTD events will be discarded." msgstr "" #: library/xml.sax.reader.rst:143 @@ -174,10 +177,10 @@ msgstr "" #: library/xml.sax.reader.rst:148 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." +"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 "" #: library/xml.sax.reader.rst:156 @@ -211,9 +214,10 @@ msgstr "" #: library/xml.sax.reader.rst:183 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." +"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 "" #: library/xml.sax.reader.rst:190 @@ -225,9 +229,10 @@ msgstr "" #: library/xml.sax.reader.rst:197 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." +"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 "" #: library/xml.sax.reader.rst:205 @@ -314,8 +319,8 @@ msgstr "" #: library/xml.sax.reader.rst:290 msgid "" -"The encoding attribute of the :class:`InputSource` is ignored if the :class:" -"`InputSource` also contains a character stream." +"The encoding attribute of the :class:`InputSource` is ignored if " +"the :class:`InputSource` also contains a character stream." msgstr "" #: library/xml.sax.reader.rst:296 @@ -371,11 +376,10 @@ msgstr "" #: library/xml.sax.reader.rst:336 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:" +"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 "" #: library/xml.sax.reader.rst:346 diff --git a/library/xml.sax.utils.po b/library/xml.sax.utils.po index f37dd7657..c92a4a3c9 100644 --- a/library/xml.sax.utils.po +++ b/library/xml.sax.utils.po @@ -90,8 +90,8 @@ msgstr "" #: library/xml.sax.utils.rst:64 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 " +"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 " @@ -106,11 +106,12 @@ msgstr "" #: library/xml.sax.utils.rst:80 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." +"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 "" #: library/xml.sax.utils.rst:90 @@ -119,6 +120,6 @@ msgid "" "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:`~xml." -"sax.xmlreader.XMLReader.parse` method." +"function to implement the polymorphic *source* argument to " +"their :meth:`~xml.sax.xmlreader.XMLReader.parse` method." msgstr "" diff --git a/library/xmlrpc.client.po b/library/xmlrpc.client.po index c18b32be9..2e3974380 100644 --- a/library/xmlrpc.client.po +++ b/library/xmlrpc.client.po @@ -76,17 +76,17 @@ msgid "" "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 " -"*headers* parameter is an optional sequence of HTTP headers to send with " -"each request, expressed as a sequence of 2-tuples representing the header " -"name and value. (e.g. ``[('Header-Name', 'value')]``). The obsolete " -"*use_datetime* flag is similar to *use_builtin_types* but it applies only to " -"date/time values." +"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 *headers* parameter is an optional " +"sequence of HTTP headers to send with each request, expressed as a sequence " +"of 2-tuples representing the header name and value. (e.g. ``[('Header-Name', " +"'value')]``). The obsolete *use_datetime* flag is similar to " +"*use_builtin_types* but it applies only to date/time values." msgstr "" #: library/xmlrpc.client.rst:549 @@ -100,13 +100,13 @@ msgstr "" #: library/xmlrpc.client.rst:73 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." +"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 "" #: library/xmlrpc.client.rst:82 @@ -184,8 +184,8 @@ msgstr "" #: library/xmlrpc.client.rst:113 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." +"Objects of user-defined classes can be passed in; only " +"their :attr:`~object.__dict__` attribute is transmitted." msgstr "" #: library/xmlrpc.client.rst:118 @@ -243,8 +243,9 @@ msgid "" "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." +"have to pass arbitrary bytes via XML-RPC, use :class:`bytes` " +"or :class:`bytearray` classes or the :class:`Binary` wrapper class described " +"below." msgstr "" #: library/xmlrpc.client.rst:148 @@ -495,8 +496,8 @@ msgstr "" #: library/xmlrpc.client.rst:338 msgid "" -"It also supports certain of Python's built-in operators through :meth:" -"`~object.__eq__` and :meth:`~object.__ne__` methods." +"It also supports certain of Python's built-in operators " +"through :meth:`~object.__eq__` and :meth:`~object.__ne__` methods." msgstr "" #: library/xmlrpc.client.rst:341 @@ -618,8 +619,8 @@ msgstr "" #: library/xmlrpc.client.rst:447 msgid "" -"In the following example we're going to intentionally cause a :exc:" -"`ProtocolError` by providing an invalid URI::" +"In the following example we're going to intentionally cause " +"a :exc:`ProtocolError` by providing an invalid URI::" msgstr "" #: library/xmlrpc.client.rst:450 diff --git a/library/xmlrpc.server.po b/library/xmlrpc.server.po index f847a8903..229e43e81 100644 --- a/library/xmlrpc.server.po +++ b/library/xmlrpc.server.po @@ -27,9 +27,9 @@ msgstr "" #: 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`." +"RPC servers written in Python. Servers can either be free standing, " +"using :class:`SimpleXMLRPCServer`, or embedded in a CGI environment, " +"using :class:`CGIXMLRPCRequestHandler`." msgstr "" #: library/xmlrpc.server.rst:22 @@ -56,18 +56,19 @@ msgid "" "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." +"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 "" #: library/xmlrpc.server.rst:62 library/xmlrpc.server.rst:374 @@ -97,17 +98,18 @@ msgstr "" #: library/xmlrpc.server.rst:78 msgid "" -"The :class:`SimpleXMLRPCServer` class is based on :class:`socketserver." -"TCPServer` and provides a means of creating simple, stand alone XML-RPC " -"servers." +"The :class:`SimpleXMLRPCServer` class is based " +"on :class:`socketserver.TCPServer` and provides a means of creating simple, " +"stand alone XML-RPC servers." msgstr "" #: library/xmlrpc.server.rst:299 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 :" -"attr:`function.__name__` will be used. *name* is a string, and may contain " -"characters not legal in Python identifiers, including the period character." +"given, it will be the method name associated with *function*, " +"otherwise :attr:`function.__name__` will be used. *name* is a string, and " +"may contain characters not legal in Python identifiers, including the period " +"character." msgstr "" #: library/xmlrpc.server.rst:304 @@ -124,9 +126,9 @@ msgstr "" #: library/xmlrpc.server.rst:100 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, " +"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 " @@ -365,10 +367,10 @@ msgstr "" #: library/xmlrpc.server.rst:314 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 " +"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 " @@ -420,16 +422,16 @@ msgstr "" #: library/xmlrpc.server.rst:360 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`." +"response to HTTP GET requests. Servers can either be free standing, " +"using :class:`DocXMLRPCServer`, or embedded in a CGI environment, " +"using :class:`DocCGIXMLRPCRequestHandler`." msgstr "" #: library/xmlrpc.server.rst:370 msgid "" -"Create a new server instance. All parameters have the same meaning as for :" -"class:`SimpleXMLRPCServer`; *requestHandler* defaults to :class:" -"`DocXMLRPCRequestHandler`." +"Create a new server instance. All parameters have the same meaning as " +"for :class:`SimpleXMLRPCServer`; *requestHandler* defaults " +"to :class:`DocXMLRPCRequestHandler`." msgstr "" #: library/xmlrpc.server.rst:380 @@ -450,11 +452,11 @@ msgstr "" #: library/xmlrpc.server.rst:396 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 " +"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 "" @@ -483,9 +485,10 @@ msgstr "" #: library/xmlrpc.server.rst:424 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." +"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 "" diff --git a/library/zipapp.po b/library/zipapp.po index 23d511e88..5046b3057 100644 --- a/library/zipapp.po +++ b/library/zipapp.po @@ -238,8 +238,8 @@ msgstr "" 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." +"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 "" #: library/zipapp.rst:174 @@ -307,12 +307,12 @@ msgstr "" #: library/zipapp.rst:218 msgid "" -"To update the file in place, do the replacement in memory using a :class:" -"`~io.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::" +"To update the file in place, do the replacement in memory using " +"a :class:`~io.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 "" #: library/zipapp.rst:225 diff --git a/library/zipfile.po b/library/zipfile.po index 087613921..9c6e04775 100644 --- a/library/zipfile.po +++ b/library/zipfile.po @@ -68,9 +68,9 @@ msgstr "" #: library/zipfile.rst:58 msgid "" -"Class that implements a subset of the interface provided by :class:`pathlib." -"Path`, including the full :class:`importlib.resources.abc.Traversable` " -"interface." +"Class that implements a subset of the interface provided " +"by :class:`pathlib.Path`, including the " +"full :class:`importlib.resources.abc.Traversable` interface." msgstr "" #: library/zipfile.rst:68 @@ -85,8 +85,8 @@ msgid "" "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`." +"of the last modification to the file; the fields are described in " +"section :ref:`zipinfo-objects`." msgstr "" #: library/zipfile.rst:84 @@ -112,14 +112,14 @@ msgstr "" #: library/zipfile.rst:104 msgid "" -"The numeric constant for the BZIP2 compression method. This requires the :" -"mod:`bz2` module." +"The numeric constant for the BZIP2 compression method. This requires " +"the :mod:`bz2` module." msgstr "" #: library/zipfile.rst:111 msgid "" -"The numeric constant for the LZMA compression method. This requires the :" -"mod:`lzma` module." +"The numeric constant for the LZMA compression method. This requires " +"the :mod:`lzma` module." msgstr "" #: library/zipfile.rst:118 @@ -179,11 +179,12 @@ msgstr "" msgid "" "*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`." +"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`." msgstr "" #: library/zipfile.rst:169 @@ -197,11 +198,12 @@ msgstr "" #: library/zipfile.rst:174 msgid "" "The *compresslevel* parameter controls the compression level to use when " -"writing files to the archive. When using :const:`ZIP_STORED` or :const:" -"`ZIP_LZMA` it has no effect. When using :const:`ZIP_DEFLATED` integers ``0`` " -"through ``9`` are accepted (see :class:`zlib ` for more " -"information). When using :const:`ZIP_BZIP2` integers ``1`` through ``9`` are " -"accepted (see :class:`bz2 ` for more information)." +"writing files to the archive. When using :const:`ZIP_STORED` " +"or :const:`ZIP_LZMA` it has no effect. When using :const:`ZIP_DEFLATED` " +"integers ``0`` through ``9`` are accepted (see :class:`zlib " +"` for more information). When using :const:`ZIP_BZIP2` " +"integers ``1`` through ``9`` are accepted (see :class:`bz2 ` " +"for more information)." msgstr "" #: library/zipfile.rst:735 @@ -221,9 +223,9 @@ msgstr "" #: library/zipfile.rst:192 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." +"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 "" #: library/zipfile.rst:196 @@ -326,14 +328,14 @@ 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 as a :" -"class:`bytes` object." +"``'w'``. *pwd* is the password used to decrypt encrypted ZIP files as " +"a :class:`bytes` object." msgstr "" #: library/zipfile.rst:280 msgid "" -":meth:`~ZipFile.open` is also a context manager and therefore supports the :" -"keyword:`with` statement::" +":meth:`~ZipFile.open` is also a context manager and therefore supports " +"the :keyword:`with` statement::" msgstr "" #: library/zipfile.rst:283 @@ -346,18 +348,17 @@ msgstr "" #: library/zipfile.rst:287 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:`~io.IOBase.seek`, :" -"meth:`~io.IOBase.tell`, :meth:`~container.__iter__`, :meth:`~iterator." -"__next__`. These objects can operate independently of the ZipFile." +"provides the following " +"methods: :meth:`~io.BufferedIOBase.read`, :meth:`~io.IOBase.readline`, :meth:`~io.IOBase.readlines`, :meth:`~io.IOBase.seek`, :meth:`~io.IOBase.tell`, :meth:`~container.__iter__`, :meth:`~iterator.__next__`. " +"These objects can operate independently of the ZipFile." msgstr "" #: library/zipfile.rst:294 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`." +"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 "" #: library/zipfile.rst:299 @@ -446,8 +447,8 @@ msgstr "" #: library/zipfile.rst:367 msgid "" -"Calling :meth:`extractall` on a closed ZipFile will raise a :exc:" -"`ValueError`. Previously, a :exc:`RuntimeError` was raised." +"Calling :meth:`extractall` on a closed ZipFile will raise " +"a :exc:`ValueError`. Previously, a :exc:`RuntimeError` was raised." msgstr "" #: library/zipfile.rst:377 @@ -467,10 +468,10 @@ msgid "" "open for read or append. *pwd* is the password used for encrypted files as " "a :class:`bytes` object and, if specified, overrides 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." +"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 "" #: library/zipfile.rst:396 @@ -617,9 +618,9 @@ msgstr "" #: library/zipfile.rst:523 msgid "" -"Construct a Path object from a ``root`` zipfile (which may be a :class:" -"`ZipFile` instance or ``file`` suitable for passing to the :class:`ZipFile` " -"constructor)." +"Construct a Path object from a ``root`` zipfile (which may be " +"a :class:`ZipFile` instance or ``file`` suitable for passing to " +"the :class:`ZipFile` constructor)." msgstr "" #: library/zipfile.rst:527 @@ -645,9 +646,9 @@ msgstr "" msgid "" "Invoke :meth:`ZipFile.open` on the current path. Allows opening for read or " "write, text or binary through supported modes: 'r', 'w', 'rb', 'wb'. " -"Positional and keyword arguments are passed through to :class:`io." -"TextIOWrapper` when opened as text and ignored otherwise. ``pwd`` is the " -"``pwd`` parameter to :meth:`ZipFile.open`." +"Positional and keyword arguments are passed through " +"to :class:`io.TextIOWrapper` when opened as text and ignored otherwise. " +"``pwd`` is the ``pwd`` parameter to :meth:`ZipFile.open`." msgstr "" #: library/zipfile.rst:551 @@ -659,8 +660,8 @@ msgstr "" msgid "" "The ``encoding`` parameter can be supplied as a positional argument without " "causing a :exc:`TypeError`. As it could in 3.9. Code needing to be " -"compatible with unpatched 3.10 and 3.11 versions must pass all :class:`io." -"TextIOWrapper` arguments, ``encoding`` included, as keywords." +"compatible with unpatched 3.10 and 3.11 versions must pass " +"all :class:`io.TextIOWrapper` arguments, ``encoding`` included, as keywords." msgstr "" #: library/zipfile.rst:563 @@ -738,8 +739,8 @@ msgstr "" #: library/zipfile.rst:629 msgid "" "The :pypi:`zipp` project provides backports of the latest path object " -"functionality to older Pythons. Use ``zipp.Path`` in place of ``zipfile." -"Path`` for early access to changes." +"functionality to older Pythons. Use ``zipp.Path`` in place of " +"``zipfile.Path`` for early access to changes." msgstr "" #: library/zipfile.rst:637 @@ -748,8 +749,8 @@ msgstr "" #: library/zipfile.rst:639 msgid "" -"The :class:`PyZipFile` constructor takes the same parameters as the :class:" -"`ZipFile` constructor, and one additional parameter, *optimize*." +"The :class:`PyZipFile` constructor takes the same parameters as " +"the :class:`ZipFile` constructor, and one additional parameter, *optimize*." msgstr "" #: library/zipfile.rst:645 @@ -787,10 +788,10 @@ msgid "" "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:`\\*.pyc` are " -"added at the top level. If the directory is a package directory, then all :" -"file:`\\*.pyc` are added under the package name as a file path, and if any " -"subdirectories are package directories, all of these are added recursively " -"in sorted order." +"added at the top level. If the directory is a package directory, then " +"all :file:`\\*.pyc` are added under the package name as a file path, and if " +"any subdirectories are package directories, all of these are added " +"recursively in sorted order." msgstr "" #: library/zipfile.rst:675 @@ -1042,8 +1043,9 @@ msgstr "" #: library/zipfile.rst:878 msgid "" -"If you want to create a new ZIP archive, specify its name after the :option:" -"`-c` option and then list the filename(s) that should be included:" +"If you want to create a new ZIP archive, specify its name after " +"the :option:`-c` option and then list the filename(s) that should be " +"included:" msgstr "" #: library/zipfile.rst:881 @@ -1060,8 +1062,8 @@ msgstr "" #: library/zipfile.rst:891 msgid "" -"If you want to extract a ZIP archive into the specified directory, use the :" -"option:`-e` option:" +"If you want to extract a ZIP archive into the specified directory, use " +"the :option:`-e` option:" msgstr "" #: library/zipfile.rst:894 @@ -1098,8 +1100,8 @@ msgstr "" #: library/zipfile.rst:930 msgid "" -"Specify encoding of member names for :option:`-l`, :option:`-e` and :option:" -"`-t`." +"Specify encoding of member names for :option:`-l`, :option:`-e` " +"and :option:`-t`." msgstr "" #: library/zipfile.rst:937 diff --git a/library/zipimport.po b/library/zipimport.po index 4306df5bc..7070fd6eb 100644 --- a/library/zipimport.po +++ b/library/zipimport.po @@ -26,11 +26,11 @@ msgstr "" #: library/zipimport.rst:13 msgid "" -"This module adds the ability to import Python modules (:file:`\\*.py`, :file:" -"`\\*.pyc`) 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." +"This module adds the ability to import Python modules " +"(:file:`\\*.py`, :file:`\\*.pyc`) 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 "" #: library/zipimport.rst:19 @@ -47,8 +47,8 @@ msgstr "" #: library/zipimport.rst:26 msgid "" "Any files may be present in the ZIP archive, but importers are only invoked " -"for :file:`.py` and :file:`.pyc` files. ZIP import of dynamic modules (:" -"file:`.pyd`, :file:`.so`) is disallowed. Note that if an archive only " +"for :file:`.py` and :file:`.pyc` files. 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." @@ -78,8 +78,8 @@ msgstr "" 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`." +"written by Just van Rossum that uses the import hooks described " +"in :pep:`302`." msgstr "" #: library/zipimport.rst:47 @@ -97,8 +97,8 @@ msgstr "" #: library/zipimport.rst:56 msgid "" -"Exception raised by zipimporter objects. It's a subclass of :exc:" -"`ImportError`, so it can be caught as :exc:`ImportError`, too." +"Exception raised by zipimporter objects. It's a subclass " +"of :exc:`ImportError`, so it can be caught as :exc:`ImportError`, too." msgstr "" #: library/zipimport.rst:63 @@ -113,9 +113,9 @@ msgstr "" 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)." +"*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 "" #: library/zipimport.rst:74 @@ -132,8 +132,8 @@ msgstr "" #: library/zipimport.rst:84 msgid "" -"Implementation of :meth:`importlib.abc.Loader.create_module` that returns :" -"const:`None` to explicitly request the default semantics." +"Implementation of :meth:`importlib.abc.Loader.create_module` that " +"returns :const:`None` to explicitly request the default semantics." msgstr "" #: library/zipimport.rst:92 @@ -175,8 +175,8 @@ msgstr "" #: library/zipimport.rst:138 msgid "" -"Return ``True`` if the module specified by *fullname* is a package. Raise :" -"exc:`ZipImportError` if the module couldn't be found." +"Return ``True`` if the module specified by *fullname* is a package. " +"Raise :exc:`ZipImportError` if the module couldn't be found." msgstr "" #: library/zipimport.rst:144 @@ -211,8 +211,8 @@ msgstr "" #: library/zipimport.rst:173 msgid "" "The :attr:`archive` and :attr:`prefix` attributes, when combined with a " -"slash, equal the original *archivepath* argument given to the :class:" -"`zipimporter` constructor." +"slash, equal the original *archivepath* argument given to " +"the :class:`zipimporter` constructor." msgstr "" #: library/zipimport.rst:181 @@ -221,8 +221,8 @@ msgstr "" #: library/zipimport.rst:183 msgid "" -"Here is an example that imports a module from a ZIP archive - note that the :" -"mod:`zipimport` module is not explicitly used." +"Here is an example that imports a module from a ZIP archive - note that " +"the :mod:`zipimport` module is not explicitly used." msgstr "" #: library/zipimport.rst:186 diff --git a/library/zlib.po b/library/zlib.po index 22ec678e1..b71a72565 100644 --- a/library/zlib.po +++ b/library/zlib.po @@ -161,9 +161,9 @@ msgstr "" #: library/zlib.rst:108 msgid "" -"*strategy* is used to tune the compression algorithm. Possible values are :" -"const:`Z_DEFAULT_STRATEGY`, :const:`Z_FILTERED`, :const:`Z_HUFFMAN_ONLY`, :" -"const:`Z_RLE` (zlib 1.2.0.1) and :const:`Z_FIXED` (zlib 1.2.2.2)." +"*strategy* is used to tune the compression algorithm. Possible values " +"are :const:`Z_DEFAULT_STRATEGY`, :const:`Z_FILTERED`, :const:`Z_HUFFMAN_ONLY`, :const:`Z_RLE` " +"(zlib 1.2.0.1) and :const:`Z_FIXED` (zlib 1.2.2.2)." msgstr "" #: library/zlib.rst:112 @@ -303,15 +303,14 @@ msgstr "" #: library/zlib.rst:221 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_NO_FLUSH`, :const:`Z_PARTIAL_FLUSH`, :const:`Z_SYNC_FLUSH`, :const:" -"`Z_FULL_FLUSH`, :const:`Z_BLOCK` (zlib 1.2.3.4), or :const:`Z_FINISH`, " -"defaulting to :const:`Z_FINISH`. Except :const:`Z_FINISH`, all constants " -"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." +"compressed output is returned. *mode* can be selected from the " +"constants :const:`Z_NO_FLUSH`, :const:`Z_PARTIAL_FLUSH`, :const:`Z_SYNC_FLUSH`, :const:`Z_FULL_FLUSH`, :const:`Z_BLOCK` " +"(zlib 1.2.3.4), or :const:`Z_FINISH`, defaulting to :const:`Z_FINISH`. " +"Except :const:`Z_FINISH`, all constants 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 "" #: library/zlib.rst:234 @@ -340,11 +339,12 @@ msgstr "" #: library/zlib.rst:256 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." +"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 "" #: library/zlib.rst:265 @@ -363,9 +363,9 @@ msgstr "" 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." +"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 "" #: library/zlib.rst:282 @@ -375,8 +375,8 @@ msgid "" "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." +"*max_length* is zero then the whole input is decompressed, " +"and :attr:`unconsumed_tail` is empty." msgstr "" #: library/zlib.rst:289 @@ -386,9 +386,9 @@ msgstr "" #: library/zlib.rst:295 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." +"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 "" #: library/zlib.rst:300 diff --git a/library/zoneinfo.po b/library/zoneinfo.po index 44e938d7b..83c85b3ad 100644 --- a/library/zoneinfo.po +++ b/library/zoneinfo.po @@ -70,11 +70,11 @@ msgstr "" #: library/zoneinfo.rst:37 msgid "" -":class:`ZoneInfo` is a concrete implementation of the :class:`datetime." -"tzinfo` abstract base class, and is intended to be attached to ``tzinfo``, " -"either via the constructor, the :meth:`datetime.replace ` method or :meth:`datetime.astimezone `::" +":class:`ZoneInfo` is a concrete implementation of " +"the :class:`datetime.tzinfo` abstract base class, and is intended to be " +"attached to ``tzinfo``, either via the constructor, " +"the :meth:`datetime.replace ` method " +"or :meth:`datetime.astimezone `::" msgstr "" #: library/zoneinfo.rst:42 @@ -206,8 +206,8 @@ msgid "" "those building Python from source who know where their system time zone data " "is deployed may change the default time zone path by specifying the compile-" "time option ``TZPATH`` (or, more likely, the :option:`configure flag --with-" -"tzpath <--with-tzpath>`), which should be a string delimited by :data:`os." -"pathsep`." +"tzpath <--with-tzpath>`), which should be a string delimited " +"by :data:`os.pathsep`." msgstr "" #: library/zoneinfo.rst:134 @@ -222,10 +222,10 @@ msgstr "" #: library/zoneinfo.rst:142 msgid "" -"When initializing :data:`TZPATH` (either at import time or whenever :func:" -"`reset_tzpath` is called with no arguments), the ``zoneinfo`` module will " -"use the environment variable ``PYTHONTZPATH``, if it exists, to set the " -"search path." +"When initializing :data:`TZPATH` (either at import time or " +"whenever :func:`reset_tzpath` is called with no arguments), the ``zoneinfo`` " +"module will use the environment variable ``PYTHONTZPATH``, if it exists, to " +"set the search path." msgstr "" #: library/zoneinfo.rst:149 @@ -251,11 +251,11 @@ msgstr "" #: library/zoneinfo.rst:165 msgid "" -"The TZ search path can also be configured at runtime using the :func:" -"`reset_tzpath` function. This is generally not an advisable operation, " -"though it is reasonable to use it in test functions that require the use of " -"a specific time zone path (or require disabling access to the system time " -"zones)." +"The TZ search path can also be configured at runtime using " +"the :func:`reset_tzpath` function. This is generally not an advisable " +"operation, though it is reasonable to use it in test functions that require " +"the use of a specific time zone path (or require disabling access to the " +"system time zones)." msgstr "" #: library/zoneinfo.rst:172 @@ -287,8 +287,8 @@ msgstr "" #: library/zoneinfo.rst:192 msgid "" -"If no file matching ``key`` is found, the constructor will raise :exc:" -"`ZoneInfoNotFoundError`." +"If no file matching ``key`` is found, the constructor will " +"raise :exc:`ZoneInfoNotFoundError`." msgstr "" #: library/zoneinfo.rst:196 @@ -297,15 +297,15 @@ msgstr "" #: library/zoneinfo.rst:200 msgid "" -"Constructs a ``ZoneInfo`` object from a file-like object returning bytes (e." -"g. a file opened in binary mode or an :class:`io.BytesIO` object). Unlike " +"Constructs a ``ZoneInfo`` object from a file-like object returning bytes " +"(e.g. a file opened in binary mode or an :class:`io.BytesIO` object). Unlike " "the primary constructor, this always constructs a new object." msgstr "" #: library/zoneinfo.rst:204 msgid "" -"The ``key`` parameter sets the name of the zone for the purposes of :py:meth:" -"`~object.__str__` and :py:meth:`~object.__repr__`." +"The ``key`` parameter sets the name of the zone for the purposes " +"of :py:meth:`~object.__str__` and :py:meth:`~object.__repr__`." msgstr "" #: library/zoneinfo.rst:207 @@ -392,9 +392,9 @@ msgstr "" #: library/zoneinfo.rst:271 msgid "" -"The string representation returned when calling :py:class:`str` on a :class:" -"`ZoneInfo` object defaults to using the :attr:`ZoneInfo.key` attribute (see " -"the note on usage in the attribute documentation)::" +"The string representation returned when calling :py:class:`str` on " +"a :class:`ZoneInfo` object defaults to using the :attr:`ZoneInfo.key` " +"attribute (see the note on usage in the attribute documentation)::" msgstr "" #: library/zoneinfo.rst:275 @@ -536,10 +536,10 @@ msgstr "" #: library/zoneinfo.rst:376 msgid "" -"The ``to`` parameter must be a :term:`sequence` of strings or :class:`os." -"PathLike` and not a string, all of which must be absolute paths. :exc:" -"`ValueError` will be raised if something other than an absolute path is " -"passed." +"The ``to`` parameter must be a :term:`sequence` of strings " +"or :class:`os.PathLike` and not a string, all of which must be absolute " +"paths. :exc:`ValueError` will be raised if something other than an absolute " +"path is passed." msgstr "" #: library/zoneinfo.rst:382 @@ -562,15 +562,15 @@ msgstr "" #: library/zoneinfo.rst:393 msgid "" "The object that ``zoneinfo.TZPATH`` points to may change in response to a " -"call to :func:`reset_tzpath`, so it is recommended to use ``zoneinfo." -"TZPATH`` rather than importing ``TZPATH`` from ``zoneinfo`` or assigning a " -"long-lived variable to ``zoneinfo.TZPATH``." +"call to :func:`reset_tzpath`, so it is recommended to use " +"``zoneinfo.TZPATH`` rather than importing ``TZPATH`` from ``zoneinfo`` or " +"assigning a long-lived variable to ``zoneinfo.TZPATH``." msgstr "" #: library/zoneinfo.rst:398 msgid "" -"For more information on configuring the time zone search path, see :ref:" -"`zoneinfo_data_configuration`." +"For more information on configuring the time zone search path, " +"see :ref:`zoneinfo_data_configuration`." msgstr "" #: library/zoneinfo.rst:402 @@ -580,8 +580,8 @@ msgstr "" #: library/zoneinfo.rst:406 msgid "" "Raised when construction of a :class:`ZoneInfo` object fails because the " -"specified key could not be found on the system. This is a subclass of :exc:" -"`KeyError`." +"specified key could not be found on the system. This is a subclass " +"of :exc:`KeyError`." msgstr "" #: library/zoneinfo.rst:412 diff --git a/license.po b/license.po index 2c9ccfa4e..8670cc7c0 100644 --- a/license.po +++ b/license.po @@ -44,8 +44,8 @@ msgid "" "Virginia where he released several versions of the software." msgstr "" "1995'te Guido, yazılımın çeşitli sürümlerini yayınladığı Virginia, " -"Reston'daki Ulusal Araştırma Girişimleri Kurumu'nda (CNRI, bkz. https://www." -"cnri.reston.va.us/) Python üzerindeki çalışmalarına devam etti." +"Reston'daki Ulusal Araştırma Girişimleri Kurumu'nda (CNRI, bkz. https://" +"www.cnri.reston.va.us/) Python üzerindeki çalışmalarına devam etti." #: license.rst:22 msgid "" @@ -246,8 +246,8 @@ msgstr "" #: license.rst:78 msgid "" "Starting with Python 3.8.6, examples, recipes, and other code in the " -"documentation are dual licensed under the PSF License Agreement and the :ref:" -"`Zero-Clause BSD license `." +"documentation are dual licensed under the PSF License Agreement and " +"the :ref:`Zero-Clause BSD license `." msgstr "" "Python 3.8.6'dan başlayarak, belgelerdeki örnekler, tarifler ve diğer " "kodlar, PSF Lisans Sözleşmesi ve :ref:`Zero-Clause BSD license ` " @@ -256,8 +256,8 @@ msgstr "" #: license.rst:82 msgid "" "Some software incorporated into Python is under different licenses. The " -"licenses are listed with code falling under that license. See :ref:" -"`OtherLicenses` for an incomplete list of these licenses." +"licenses are listed with code falling under that license. " +"See :ref:`OtherLicenses` for an incomplete list of these licenses." msgstr "" "Python'a dahil edilen bazı yazılımlar farklı lisanslar altındadır. " "Lisanslar, bu lisansa giren kodla listelenir. Bu lisansların eksik listesi " @@ -651,9 +651,9 @@ msgstr "Soketler" #: license.rst:355 msgid "" -"The :mod:`socket` module uses the functions, :c:func:`!getaddrinfo`, and :c:" -"func:`!getnameinfo`, which are coded in separate source files from the WIDE " -"Project, https://www.wide.ad.jp/. ::" +"The :mod:`socket` module uses the functions, :c:func:`!getaddrinfo`, " +"and :c:func:`!getnameinfo`, which are coded in separate source files from " +"the WIDE Project, https://www.wide.ad.jp/. ::" msgstr "" ":mod:`socket` modülü, https://www.wide.ad.jp/ adresindeki WIDE Projesi'nden " "ayrı kaynak dosyalarında kodlanan :c:func:`!getaddrinfo` ve :c:func:`!" @@ -986,14 +986,14 @@ msgstr "strtod ve dtoa" 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 https://web.archive." -"org/web/20220517033456/http://www.netlib.org/fp/dtoa.c. The original file, " -"as retrieved on March 16, 2009, contains the following copyright and " -"licensing notice::" +"the same name by David M. Gay, currently available from https://" +"web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c. The " +"original file, as retrieved on March 16, 2009, contains the following " +"copyright and licensing notice::" msgstr "" "C double'larının dizelere ve dizelerden dönüştürülmesi için dtoa ve strtod C " -"fonksiyonlarını sağlayan :file:`Python/dtoa.c` dosyası, şu anda https://web." -"archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c 'den " +"fonksiyonlarını sağlayan :file:`Python/dtoa.c` dosyası, şu anda https://" +"web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c 'den " "erişilebilen David M. Gay tarafından aynı adlı dosyadan türetilmiştir. 16 " "Mart 2009'da alınan orijinal dosya aşağıdaki telif hakkı ve lisans " "bildirimini içerir::" diff --git a/reference/compound_stmts.po b/reference/compound_stmts.po index 1d36c7894..c752ba6f9 100644 --- a/reference/compound_stmts.po +++ b/reference/compound_stmts.po @@ -32,10 +32,10 @@ msgstr "" 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." +"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 "" #: reference/compound_stmts.rst:26 @@ -77,8 +77,8 @@ 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)." +"'dangling :keyword:`else`' problem is solved in Python by requiring " +"nested :keyword:`if` statements to be indented)." msgstr "" #: reference/compound_stmts.rst:75 @@ -126,9 +126,9 @@ msgstr "" #: reference/compound_stmts.rst:133 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." +"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 "" #: reference/compound_stmts.rst:142 @@ -143,22 +143,23 @@ msgstr "" #: reference/compound_stmts.rst:160 msgid "" -"The ``starred_list`` expression is evaluated once; it should yield an :term:" -"`iterable` object. An :term:`iterator` is created for that iterable. The " -"first item provided by the iterator is then assigned to the target list " -"using the standard rules for assignments (see :ref:`assignment`), and the " -"suite is executed. This repeats for each item provided by the iterator. " -"When the iterator is exhausted, the suite in the :keyword:`!else` clause, if " -"present, is executed, and the loop terminates." +"The ``starred_list`` expression is evaluated once; it should yield " +"an :term:`iterable` object. An :term:`iterator` is created for that " +"iterable. The first item provided by the iterator is then assigned to the " +"target list using the standard rules for assignments " +"(see :ref:`assignment`), and the suite is executed. This repeats for each " +"item provided by the iterator. When the iterator is exhausted, the suite in " +"the :keyword:`!else` clause, if present, is executed, and the loop " +"terminates." msgstr "" #: 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." +"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 "" #: reference/compound_stmts.rst:179 @@ -202,9 +203,9 @@ msgstr "" #: reference/compound_stmts.rst:231 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`." +"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 "" #: reference/compound_stmts.rst:239 @@ -250,13 +251,13 @@ msgstr "" #: reference/compound_stmts.rst:267 msgid "" "When a matching :keyword:`!except` clause is found, the exception is " -"assigned to the target specified after the :keyword:`!as` keyword in that :" -"keyword:`!except` clause, if present, and the :keyword:`!except` clause's " -"suite is executed. All :keyword:`!except` clauses must have an executable " -"block. When the end of this block is reached, execution continues normally " -"after the entire :keyword:`try` statement. (This means that if two nested " -"handlers exist for the same exception, and the exception occurs in the :" -"keyword:`!try` clause of the inner handler, the outer handler will not " +"assigned to the target specified after the :keyword:`!as` keyword in " +"that :keyword:`!except` clause, if present, and the :keyword:`!except` " +"clause's suite is executed. All :keyword:`!except` clauses must have an " +"executable block. When the end of this block is reached, execution continues " +"normally after the entire :keyword:`try` statement. (This means that if two " +"nested handlers exist for the same exception, and the exception occurs in " +"the :keyword:`!try` clause of the inner handler, the outer handler will not " "handle the exception.)" msgstr "" @@ -330,15 +331,15 @@ msgstr "" #: reference/compound_stmts.rst:335 msgid "" -"The :keyword:`!except*` clause(s) are used for handling :exc:" -"`ExceptionGroup`\\s. The exception type for matching is interpreted as in " -"the case of :keyword:`except`, but in the case of exception groups we can " -"have partial matches when the type matches some of the exceptions in the " -"group. This means that multiple :keyword:`!except*` clauses can execute, " -"each handling part of the exception group. Each clause executes at most once " -"and handles an exception group of all matching exceptions. Each exception " -"in the group is handled by at most one :keyword:`!except*` clause, the first " -"that matches it. ::" +"The :keyword:`!except*` clause(s) are used for " +"handling :exc:`ExceptionGroup`\\s. The exception type for matching is " +"interpreted as in the case of :keyword:`except`, but in the case of " +"exception groups we can have partial matches when the type matches some of " +"the exceptions in the group. This means that multiple :keyword:`!except*` " +"clauses can execute, each handling part of the exception group. Each clause " +"executes at most once and handles an exception group of all matching " +"exceptions. Each exception in the group is handled by at most " +"one :keyword:`!except*` clause, the first that matches it. ::" msgstr "" #: reference/compound_stmts.rst:345 @@ -396,8 +397,8 @@ msgstr "" #: reference/compound_stmts.rst:384 msgid "" "It is not possible to mix :keyword:`except` and :keyword:`!except*` in the " -"same :keyword:`try`. :keyword:`break`, :keyword:`continue` and :keyword:" -"`return` cannot appear in an :keyword:`!except*` clause." +"same :keyword:`try`. :keyword:`break`, :keyword:`continue` " +"and :keyword:`return` cannot appear in an :keyword:`!except*` clause." msgstr "" #: reference/compound_stmts.rst:399 @@ -407,10 +408,10 @@ msgstr "" #: reference/compound_stmts.rst:401 msgid "" "The optional :keyword:`!else` clause is executed if the control flow leaves " -"the :keyword:`try` suite, no exception was raised, and no :keyword:" -"`return`, :keyword:`continue`, or :keyword:`break` statement was executed. " -"Exceptions in the :keyword:`!else` clause are not handled by the preceding :" -"keyword:`except` clauses." +"the :keyword:`try` suite, no exception was raised, and " +"no :keyword:`return`, :keyword:`continue`, or :keyword:`break` statement was " +"executed. Exceptions in the :keyword:`!else` clause are not handled by the " +"preceding :keyword:`except` clauses." msgstr "" #: reference/compound_stmts.rst:413 @@ -419,16 +420,16 @@ msgstr "" #: reference/compound_stmts.rst:415 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`, :keyword:`break` or :keyword:`continue` statement, the saved " -"exception is discarded::" +"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`, :keyword:`break` or :keyword:`continue` statement, the " +"saved exception is discarded::" msgstr "" #: reference/compound_stmts.rst:425 @@ -479,8 +480,8 @@ msgstr "" #: reference/compound_stmts.rst:460 msgid "" -"Prior to Python 3.8, a :keyword:`continue` statement was illegal in the :" -"keyword:`!finally` clause due to a problem with the implementation." +"Prior to Python 3.8, a :keyword:`continue` statement was illegal in " +"the :keyword:`!finally` clause due to a problem with the implementation." msgstr "" #: reference/compound_stmts.rst:469 @@ -491,8 +492,8 @@ msgstr "" 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." +"This allows common :keyword:`try`...\\ :keyword:`except`..." +"\\ :keyword:`finally` usage patterns to be encapsulated for convenient reuse." msgstr "" #: reference/compound_stmts.rst:488 @@ -503,8 +504,8 @@ msgstr "" #: reference/compound_stmts.rst:490 msgid "" -"The context expression (the expression given in the :token:`~python-grammar:" -"with_item`) is evaluated to obtain a context manager." +"The context expression (the expression given in the :token:`~python-" +"grammar:with_item`) is evaluated to obtain a context manager." msgstr "" #: reference/compound_stmts.rst:493 @@ -528,11 +529,11 @@ msgstr "" #: reference/compound_stmts.rst:504 msgid "" -"The :keyword:`with` statement guarantees that if the :meth:`~object." -"__enter__` method returns without an error, then :meth:`~object.__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 7 below." +"The :keyword:`with` statement guarantees that if " +"the :meth:`~object.__enter__` method returns without an error, " +"then :meth:`~object.__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 7 below." msgstr "" #: reference/compound_stmts.rst:510 @@ -543,16 +544,16 @@ msgstr "" msgid "" "The context manager's :meth:`~object.__exit__` method is invoked. If an " "exception caused the suite to be exited, its type, value, and traceback are " -"passed as arguments to :meth:`~object.__exit__`. Otherwise, three :const:" -"`None` arguments are supplied." +"passed as arguments to :meth:`~object.__exit__`. Otherwise, " +"three :const:`None` arguments are supplied." msgstr "" #: reference/compound_stmts.rst:517 msgid "" -"If the suite was exited due to an exception, and the return value from the :" -"meth:`~object.__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." +"If the suite was exited due to an exception, and the return value from " +"the :meth:`~object.__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 "" #: reference/compound_stmts.rst:522 @@ -600,8 +601,8 @@ msgstr "" #: reference/compound_stmts.rst:550 msgid "" -"With more than one item, the context managers are processed as if multiple :" -"keyword:`with` statements were nested::" +"With more than one item, the context managers are processed as if " +"multiple :keyword:`with` statements were nested::" msgstr "" #: reference/compound_stmts.rst:553 @@ -968,8 +969,8 @@ msgstr "" #: reference/compound_stmts.rst:846 msgid "" -"The rule ``strings`` and the token ``NUMBER`` are defined in the :doc:" -"`standard Python grammar <./grammar>`. Triple-quoted strings are " +"The rule ``strings`` and the token ``NUMBER`` are defined in " +"the :doc:`standard Python grammar <./grammar>`. Triple-quoted strings are " "supported. Raw strings and byte strings are supported. :ref:`f-strings` " "are not supported." msgstr "" @@ -999,8 +1000,8 @@ msgstr "" #: reference/compound_stmts.rst:869 msgid "" "A single underscore ``_`` is not a capture pattern (this is what ``!'_'`` " -"expresses). It is instead treated as a :token:`~python-grammar:" -"wildcard_pattern`." +"expresses). It is instead treated as a :token:`~python-" +"grammar:wildcard_pattern`." msgstr "" #: reference/compound_stmts.rst:873 @@ -1061,8 +1062,8 @@ msgstr "" #: reference/compound_stmts.rst:918 msgid "" -"In simple terms ``NAME1.NAME2`` will succeed only if `` == NAME1." -"NAME2``" +"In simple terms ``NAME1.NAME2`` will succeed only if `` == " +"NAME1.NAME2``" msgstr "" #: reference/compound_stmts.rst:922 @@ -1274,8 +1275,8 @@ msgstr "" msgid "" "Key-value pairs are matched using the two-argument form of the mapping " "subject's ``get()`` method. Matched key-value pairs must already be present " -"in the mapping, and not created on-the-fly via :meth:`__missing__` or :meth:" -"`~object.__getitem__`." +"in the mapping, and not created on-the-fly via :meth:`__missing__` " +"or :meth:`~object.__getitem__`." msgstr "" #: reference/compound_stmts.rst:1064 @@ -1322,14 +1323,14 @@ msgstr "" #: reference/compound_stmts.rst:1094 msgid "" -"If ``name_or_attr`` is not an instance of the builtin :class:`type` , raise :" -"exc:`TypeError`." +"If ``name_or_attr`` is not an instance of the builtin :class:`type` , " +"raise :exc:`TypeError`." msgstr "" #: reference/compound_stmts.rst:1097 msgid "" -"If the subject value is not an instance of ``name_or_attr`` (tested via :" -"func:`isinstance`), the class pattern fails." +"If the subject value is not an instance of ``name_or_attr`` (tested " +"via :func:`isinstance`), the class pattern fails." msgstr "" #: reference/compound_stmts.rst:1100 @@ -1395,14 +1396,14 @@ msgstr "" #: reference/compound_stmts.rst:1133 msgid "" -"If the returned value is not a tuple, the conversion fails and :exc:" -"`TypeError` is raised." +"If the returned value is not a tuple, the conversion fails " +"and :exc:`TypeError` is raised." msgstr "" #: reference/compound_stmts.rst:1136 msgid "" -"If there are more positional patterns than ``len(cls.__match_args__)``, :exc:" -"`TypeError` is raised." +"If there are more positional patterns than " +"``len(cls.__match_args__)``, :exc:`TypeError` is raised." msgstr "" #: reference/compound_stmts.rst:1139 @@ -1521,8 +1522,8 @@ msgstr "" #: reference/compound_stmts.rst:1208 msgid "" -"A function definition defines a user-defined function object (see section :" -"ref:`types`):" +"A function definition defines a user-defined function object (see " +"section :ref:`types`):" msgstr "" #: reference/compound_stmts.rst:1228 @@ -1576,9 +1577,9 @@ msgstr "" #: reference/compound_stmts.rst:1258 msgid "" -"Functions may be decorated with any valid :token:`~python-grammar:" -"assignment_expression`. Previously, the grammar was much more restrictive; " -"see :pep:`614` for details." +"Functions may be decorated with any valid :token:`~python-" +"grammar:assignment_expression`. Previously, the grammar was much more " +"restrictive; see :pep:`614` for details." msgstr "" #: reference/compound_stmts.rst:1263 @@ -1630,18 +1631,18 @@ msgstr "" #: reference/compound_stmts.rst:1307 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 positional 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 by keyword arguments. Parameters before " -"\"``/``\" are positional-only parameters and may only be passed by " -"positional arguments." +"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 positional " +"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 by keyword arguments. " +"Parameters before \"``/``\" are positional-only parameters and may only be " +"passed by positional arguments." msgstr "" #: reference/compound_stmts.rst:1319 @@ -1660,8 +1661,8 @@ msgid "" "of the form \"``-> expression``\" after the parameter list. These " "annotations can be any valid Python expression. 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. If the " +"available as values of a dictionary keyed by the parameters' names in " +"the :attr:`__annotations__` attribute of the function object. If the " "``annotations`` import from :mod:`__future__` is used, annotations are " "preserved as strings at runtime which enables postponed evaluation. " "Otherwise, they are evaluated when the function definition is executed. In " @@ -1682,8 +1683,8 @@ msgid "" "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 " +"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 "" @@ -1777,14 +1778,14 @@ msgstr "" #: reference/compound_stmts.rst:1421 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." +"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 "" #: reference/compound_stmts.rst:1430 @@ -1826,9 +1827,9 @@ msgstr "" #: reference/compound_stmts.rst:1454 msgid "" -"Classes may be decorated with any valid :token:`~python-grammar:" -"assignment_expression`. Previously, the grammar was much more restrictive; " -"see :pep:`614` for details." +"Classes may be decorated with any valid :token:`~python-" +"grammar:assignment_expression`. Previously, the grammar was much more " +"restrictive; see :pep:`614` for details." msgstr "" #: reference/compound_stmts.rst:1459 @@ -1836,8 +1837,8 @@ msgid "" "A list of :ref:`type parameters ` may be given in square " "brackets immediately after the class's name. This indicates to static type " "checkers that the class is generic. At runtime, the type parameters can be " -"retrieved from the class's :attr:`~type.__type_params__` attribute. See :ref:" -"`generic-classes` for more." +"retrieved from the class's :attr:`~type.__type_params__` attribute. " +"See :ref:`generic-classes` for more." msgstr "" #: reference/compound_stmts.rst:1468 @@ -2039,9 +2040,9 @@ msgstr "" #: reference/compound_stmts.rst:1640 msgid "" -":ref:`Functions ` (including :ref:`coroutines `), :ref:" -"`classes ` and :ref:`type aliases ` may contain a type " -"parameter list::" +":ref:`Functions ` (including :ref:`coroutines `), :ref:`classes ` and :ref:`type aliases ` may contain a " +"type parameter list::" msgstr "" #: reference/compound_stmts.rst:1644 @@ -2084,8 +2085,9 @@ msgstr "" #: reference/compound_stmts.rst:1673 msgid "" -"Generic functions, classes, and type aliases have a :attr:`~definition." -"__type_params__` attribute listing their type parameters." +"Generic functions, classes, and type aliases have " +"a :attr:`~definition.__type_params__` attribute listing their type " +"parameters." msgstr "" #: reference/compound_stmts.rst:1676 @@ -2192,8 +2194,8 @@ msgid "" "Here ``annotation-def`` indicates an :ref:`annotation scope `, which is not actually bound to any name at runtime. (One other " "liberty is taken in the translation: the syntax does not go through " -"attribute access on the :mod:`typing` module, but creates an instance of :" -"data:`typing.TypeVar` directly.)" +"attribute access on the :mod:`typing` module, but creates an instance " +"of :data:`typing.TypeVar` directly.)" msgstr "" #: reference/compound_stmts.rst:1743 @@ -2218,8 +2220,8 @@ msgstr "" #: reference/compound_stmts.rst:1754 msgid "" -"Except for the :ref:`lazy evaluation ` of the :class:" -"`~typing.TypeVar` bound, this is equivalent to::" +"Except for the :ref:`lazy evaluation ` of " +"the :class:`~typing.TypeVar` bound, this is equivalent to::" msgstr "" #: reference/compound_stmts.rst:1757 @@ -2275,9 +2277,9 @@ msgstr "" #: reference/compound_stmts.rst:1798 msgid "" -"Here again ``annotation-def`` (not a real keyword) indicates an :ref:" -"`annotation scope `, and the name ``TYPE_PARAMS_OF_Bag`` " -"is not actually bound at runtime." +"Here again ``annotation-def`` (not a real keyword) indicates " +"an :ref:`annotation scope `, and the name " +"``TYPE_PARAMS_OF_Bag`` is not actually bound at runtime." msgstr "" #: reference/compound_stmts.rst:1802 @@ -2355,9 +2357,9 @@ msgstr "" #: reference/compound_stmts.rst:1848 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." +"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 "" #: reference/compound_stmts.rst:1852 @@ -2428,8 +2430,8 @@ msgstr "" #: reference/compound_stmts.rst:1878 msgid "" -"The standard library classes :class:`dict` and :class:`types." -"MappingProxyType` are mappings." +"The standard library classes :class:`dict` " +"and :class:`types.MappingProxyType` are mappings." msgstr "" #: reference/compound_stmts.rst:1881 diff --git a/reference/datamodel.po b/reference/datamodel.po index 35853b059..950bb58bf 100644 --- a/reference/datamodel.po +++ b/reference/datamodel.po @@ -104,9 +104,9 @@ msgid "" "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." +"to explicitly close such objects. The :keyword:`try`..." +"\\ :keyword:`finally` statement and the :keyword:`with` statement provide " +"convenient ways to do this." msgstr "" #: reference/datamodel.rst:97 @@ -223,8 +223,8 @@ msgstr "" #: reference/datamodel.rst:204 msgid "" -"The string representations of the numeric classes, computed by :meth:" -"`~object.__repr__` and :meth:`~object.__str__`, have the following " +"The string representations of the numeric classes, computed " +"by :meth:`~object.__repr__` and :meth:`~object.__str__`, have the following " "properties:" msgstr "" @@ -398,9 +398,9 @@ msgid "" "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." +"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 "" #: reference/datamodel.rst:362 @@ -426,8 +426,8 @@ 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 :func:`bytes` constructor can be used to create " -"bytes objects. Also, bytes objects can be decoded to strings via the :meth:" -"`~bytes.decode` method." +"bytes objects. Also, bytes objects can be decoded to strings via " +"the :meth:`~bytes.decode` method." msgstr "" #: reference/datamodel.rst:386 @@ -437,8 +437,8 @@ msgstr "" #: reference/datamodel.rst:395 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." +"and slicing notations can be used as the target of assignment " +"and :keyword:`del` (delete) statements." msgstr "" #: reference/datamodel.rst:403 @@ -468,8 +468,8 @@ msgstr "" #: reference/datamodel.rst:418 msgid "" -"A bytearray object is a mutable array. They are created by the built-in :" -"func:`bytearray` constructor. Aside from being mutable (and hence " +"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 :class:`bytes` objects." msgstr "" @@ -507,8 +507,8 @@ msgstr "" #: reference/datamodel.rst:449 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`." +"constructor and can be modified afterwards by several methods, such " +"as :meth:`~set.add`." msgstr "" #: reference/datamodel.rst:454 @@ -517,9 +517,10 @@ msgstr "" #: reference/datamodel.rst:457 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." +"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 "" #: reference/datamodel.rst:464 @@ -588,8 +589,8 @@ msgstr "" #: reference/datamodel.rst:525 msgid "" -"These are the types to which the function call operation (see section :ref:" -"`calls`) can be applied:" +"These are the types to which the function call operation (see " +"section :ref:`calls`) can be applied:" msgstr "" #: reference/datamodel.rst:532 @@ -617,9 +618,9 @@ msgstr "" #: reference/datamodel.rst:559 msgid "" -"A reference to the :class:`dictionary ` that holds the function's :ref:" -"`global variables ` -- the global namespace of the module in which " -"the function was defined." +"A reference to the :class:`dictionary ` that holds the " +"function's :ref:`global variables ` -- the global namespace of the " +"module in which the function was defined." msgstr "" #: reference/datamodel.rst:564 @@ -648,8 +649,8 @@ msgstr "" #: reference/datamodel.rst:596 msgid "" -"The function's name. See also: :attr:`__name__ attributes `." +"The function's name. See also: :attr:`__name__ attributes " +"`." msgstr "" #: reference/datamodel.rst:600 @@ -679,28 +680,28 @@ msgstr "" #: reference/datamodel.rst:619 msgid "" -"The namespace supporting arbitrary function attributes. See also: :attr:" -"`__dict__ attributes `." +"The namespace supporting arbitrary function attributes. See " +"also: :attr:`__dict__ attributes `." msgstr "" #: reference/datamodel.rst:623 msgid "" "A :class:`dictionary ` containing annotations of :term:`parameters " "`. The keys of the dictionary are the parameter names, and " -"``'return'`` for the return annotation, if provided. See also: :ref:" -"`annotations-howto`." +"``'return'`` for the return annotation, if provided. See " +"also: :ref:`annotations-howto`." msgstr "" #: reference/datamodel.rst:630 msgid "" -"A :class:`dictionary ` containing defaults for keyword-only :term:" -"`parameters `." +"A :class:`dictionary ` containing defaults for keyword-" +"only :term:`parameters `." msgstr "" #: reference/datamodel.rst:634 msgid "" -"A :class:`tuple` containing the :ref:`type parameters ` of a :" -"ref:`generic function `." +"A :class:`tuple` containing the :ref:`type parameters ` of " +"a :ref:`generic function `." msgstr "" #: reference/datamodel.rst:639 @@ -720,8 +721,8 @@ msgstr "" #: reference/datamodel.rst:650 msgid "" "Additional information about a function's definition can be retrieved from " -"its :ref:`code object ` (accessible via the :attr:`~function." -"__code__` attribute)." +"its :ref:`code object ` (accessible via " +"the :attr:`~function.__code__` attribute)." msgstr "" #: reference/datamodel.rst:658 @@ -750,15 +751,15 @@ msgstr "" #: reference/datamodel.rst:687 msgid "" -"The method's documentation (same as :attr:`method.__func__.__doc__ `). A :class:`string ` if the original function had a " +"The method's documentation (same as :attr:`method.__func__.__doc__ " +"`). A :class:`string ` if the original function had a " "docstring, else ``None``." msgstr "" #: reference/datamodel.rst:693 msgid "" -"The name of the method (same as :attr:`method.__func__.__name__ `)" +"The name of the method (same as :attr:`method.__func__.__name__ " +"`)" msgstr "" #: reference/datamodel.rst:697 @@ -776,43 +777,44 @@ msgstr "" 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 :ref:`function object ` or a :class:" -"`classmethod` object." +"defined :ref:`function object ` or " +"a :class:`classmethod` object." msgstr "" #: reference/datamodel.rst:710 msgid "" -"When an instance method object is created by retrieving a user-defined :ref:" -"`function object ` from a class via one of its " -"instances, its :attr:`~method.__self__` attribute is the instance, and the " -"method object is said to be *bound*. The new method's :attr:`~method." -"__func__` attribute is the original function object." +"When an instance method object is created by retrieving a user-" +"defined :ref:`function object ` from a class via one of " +"its instances, its :attr:`~method.__self__` attribute is the instance, and " +"the method object is said to be *bound*. The new " +"method's :attr:`~method.__func__` attribute is the original function object." msgstr "" #: reference/datamodel.rst:716 msgid "" -"When an instance method object is created by retrieving a :class:" -"`classmethod` object from a class or instance, its :attr:`~method.__self__` " -"attribute is the class itself, and its :attr:`~method.__func__` attribute is " -"the function object underlying the class method." +"When an instance method object is created by retrieving " +"a :class:`classmethod` object from a class or instance, " +"its :attr:`~method.__self__` attribute is the class itself, and " +"its :attr:`~method.__func__` attribute is the function object underlying the " +"class method." msgstr "" #: reference/datamodel.rst:721 msgid "" -"When an instance method object is called, the underlying function (:attr:" -"`~method.__func__`) is called, inserting the class instance (:attr:`~method." -"__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)``." +"When an instance method object is called, the underlying function " +"(:attr:`~method.__func__`) is called, inserting the class instance " +"(:attr:`~method.__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 "" #: reference/datamodel.rst:728 msgid "" "When an instance method object is derived from a :class:`classmethod` " "object, the \"class instance\" stored in :attr:`~method.__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 " +"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 "" @@ -829,15 +831,15 @@ msgstr "" #: reference/datamodel.rst:746 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 :term:`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." +"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 :term:`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 "" #: reference/datamodel.rst:758 @@ -847,10 +849,10 @@ msgstr "" #: reference/datamodel.rst:763 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." +"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 "" #: reference/datamodel.rst:771 @@ -868,13 +870,13 @@ msgstr "" #: reference/datamodel.rst:783 msgid "" -"Calling the asynchronous iterator's :meth:`aiterator.__anext__ ` method will return an :term:`awaitable` which when awaited will " -"execute until it provides a value using the :keyword:`yield` expression. " -"When the function executes an empty :keyword:`return` statement or falls off " -"the end, a :exc:`StopAsyncIteration` exception is raised and the " -"asynchronous iterator will have reached the end of the set of values to be " -"yielded." +"Calling the asynchronous iterator's :meth:`aiterator.__anext__ " +"` method will return an :term:`awaitable` which when " +"awaited will execute until it provides a value using the :keyword:`yield` " +"expression. When the function executes an empty :keyword:`return` statement " +"or falls off the end, a :exc:`StopAsyncIteration` exception is raised and " +"the asynchronous iterator will have reached the end of the set of values to " +"be yielded." msgstr "" #: reference/datamodel.rst:796 @@ -919,10 +921,10 @@ 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*. (The attribute has " -"the same semantics as it does with :attr:`other instance methods `.)" +"*alist* is a list object. In this case, the special read-only " +"attribute :attr:`!__self__` is set to the object denoted by *alist*. (The " +"attribute has the same semantics as it does with :attr:`other instance " +"methods `.)" msgstr "" #: reference/datamodel.rst:836 @@ -933,8 +935,8 @@ msgstr "" 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:`~object.__new__`. The arguments of the call are passed to :" -"meth:`!__new__` and, in the typical case, to :meth:`~object.__init__` to " +"override :meth:`~object.__new__`. The arguments of the call are passed " +"to :meth:`!__new__` and, in the typical case, to :meth:`~object.__init__` to " "initialize the new instance." msgstr "" @@ -944,8 +946,8 @@ msgstr "" #: reference/datamodel.rst:848 msgid "" -"Instances of arbitrary classes can be made callable by defining a :meth:" -"`~object.__call__` method in their class." +"Instances of arbitrary classes can be made callable by defining " +"a :meth:`~object.__call__` method in their class." msgstr "" #: reference/datamodel.rst:855 @@ -955,16 +957,16 @@ msgstr "" #: reference/datamodel.rst:861 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, or by calling functions such as :func:`importlib." -"import_module` and built-in :func:`__import__`. A module object has a " -"namespace implemented by a :class:`dictionary ` object (this is the " -"dictionary referenced by the :attr:`~function.__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)." +"the :ref:`import system ` as invoked either by " +"the :keyword:`import` statement, or by calling functions such " +"as :func:`importlib.import_module` and built-in :func:`__import__`. A " +"module object has a namespace implemented by a :class:`dictionary ` " +"object (this is the dictionary referenced by " +"the :attr:`~function.__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 "" #: reference/datamodel.rst:874 @@ -1028,8 +1030,8 @@ msgstr "" #: reference/datamodel.rst:933 msgid "" "This attribute must be set to the fully qualified name of the module. It is " -"expected to match the value of :attr:`module.__spec__.name `." +"expected to match the value of :attr:`module.__spec__.name " +"`." msgstr "" #: reference/datamodel.rst:939 @@ -1050,9 +1052,9 @@ msgstr "" msgid "" "If the module is top-level (that is, not a part of any specific package) " "then the attribute should be set to ``''`` (the empty string). Otherwise, it " -"should be set to the name of the module's package (which can be equal to :" -"attr:`module.__name__` if the module itself is a package). See :pep:`366` " -"for further details." +"should be set to the name of the module's package (which can be equal " +"to :attr:`module.__name__` if the module itself is a package). " +"See :pep:`366` for further details." msgstr "" #: reference/datamodel.rst:956 @@ -1067,9 +1069,9 @@ msgstr "" #: reference/datamodel.rst:962 msgid "" "It is **strongly** recommended that you use :attr:`module.__spec__.parent " -"` instead of :attr:`!module." -"__package__`. :attr:`__package__` is now only used as a fallback if :attr:`!" -"__spec__.parent` is not set, and this fallback path is deprecated." +"` instead of :attr:`!" +"module.__package__`. :attr:`__package__` is now only used as a fallback " +"if :attr:`!__spec__.parent` is not set, and this fallback path is deprecated." msgstr "" #: reference/datamodel.rst:1005 @@ -1081,17 +1083,18 @@ msgstr "" #: reference/datamodel.rst:973 msgid "" -"The value of :attr:`!__package__` is expected to be the same as :attr:" -"`__spec__.parent `. :attr:" -"`__package__` is now only used as a fallback during import resolution if :" -"attr:`!__spec__.parent` is not defined." +"The value of :attr:`!__package__` is expected to be the same " +"as :attr:`__spec__.parent " +"`. :attr:`__package__` is now only " +"used as a fallback during import resolution if :attr:`!__spec__.parent` is " +"not defined." msgstr "" #: reference/datamodel.rst:979 msgid "" ":exc:`ImportWarning` is raised if an import resolution falls back to :attr:`!" -"__package__` instead of :attr:`__spec__.parent `." +"__package__` instead of :attr:`__spec__.parent " +"`." msgstr "" #: reference/datamodel.rst:984 @@ -1115,16 +1118,16 @@ msgstr "" #: reference/datamodel.rst:996 msgid "" ":attr:`!__loader__` defaults to ``None`` for modules created dynamically " -"using the :class:`types.ModuleType` constructor; use :func:`importlib.util." -"module_from_spec` instead to ensure the attribute is set to a :term:`loader` " -"object." +"using the :class:`types.ModuleType` constructor; " +"use :func:`importlib.util.module_from_spec` instead to ensure the attribute " +"is set to a :term:`loader` object." msgstr "" #: reference/datamodel.rst:1001 msgid "" "It is **strongly** recommended that you use :attr:`module.__spec__.loader " -"` instead of :attr:`!module." -"__loader__`." +"` instead of :attr:`!" +"module.__loader__`." msgstr "" #: reference/datamodel.rst:1010 @@ -1145,9 +1148,10 @@ msgstr "" #: reference/datamodel.rst:1023 msgid "" -"It is **strongly** recommended that you use :attr:`module.__spec__." -"submodule_search_locations ` instead of :attr:`!module.__path__`." +"It is **strongly** recommended that you " +"use :attr:`module.__spec__.submodule_search_locations " +"` instead " +"of :attr:`!module.__path__`." msgstr "" #: reference/datamodel.rst:1030 @@ -1180,18 +1184,18 @@ msgstr "" #: reference/datamodel.rst:1048 msgid "" "Note that :attr:`!__cached__` may be set even if :attr:`!__file__` is not " -"set. However, that scenario is quite atypical. Ultimately, the :term:" -"`loader` is what makes use of the module spec provided by the :term:`finder` " -"(from which :attr:`!__file__` and :attr:`!__cached__` are derived). So if a " -"loader can load from a cached module but otherwise does not load from a " -"file, that atypical scenario may be appropriate." +"set. However, that scenario is quite atypical. Ultimately, " +"the :term:`loader` is what makes use of the module spec provided by " +"the :term:`finder` (from which :attr:`!__file__` and :attr:`!__cached__` are " +"derived). 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 "" #: reference/datamodel.rst:1055 msgid "" "It is **strongly** recommended that you use :attr:`module.__spec__.cached " -"` instead of :attr:`!module." -"__cached__`." +"` instead of :attr:`!" +"module.__cached__`." msgstr "" #: reference/datamodel.rst:1060 @@ -1206,15 +1210,15 @@ msgstr "" #: reference/datamodel.rst:1067 msgid "" -"The module's documentation string, or ``None`` if unavailable. See also: :" -"attr:`__doc__ attributes `." +"The module's documentation string, or ``None`` if unavailable. See " +"also: :attr:`__doc__ attributes `." msgstr "" #: reference/datamodel.rst:1072 msgid "" "A dictionary containing :term:`variable annotations ` " -"collected during module body execution. For best practices on working with :" -"attr:`__annotations__`, please see :ref:`annotations-howto`." +"collected during module body execution. For best practices on working " +"with :attr:`__annotations__`, please see :ref:`annotations-howto`." msgstr "" #: reference/datamodel.rst:1078 @@ -1246,25 +1250,25 @@ msgstr "" #: reference/datamodel.rst:1102 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 at :ref:`python_2.3_mro`." +"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 at :ref:`python_2.3_mro`." msgstr "" #: reference/datamodel.rst:1123 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:`~method.__self__` attribute is :class:`!C`. When it would yield a :" -"class:`staticmethod` object, it is transformed into the object wrapped by " +"class method object, it is transformed into an instance method object " +"whose :attr:`~method.__self__` attribute is :class:`!C`. When it would yield " +"a :class:`staticmethod` 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__`." @@ -1288,8 +1292,8 @@ msgstr "" #: reference/datamodel.rst:1160 msgid "" -"The class's name. See also: :attr:`__name__ attributes `." +"The class's name. See also: :attr:`__name__ attributes " +"`." msgstr "" #: reference/datamodel.rst:1164 @@ -1305,8 +1309,8 @@ msgstr "" #: reference/datamodel.rst:1171 msgid "" "A :class:`mapping proxy ` providing a read-only view " -"of the class's namespace. See also: :attr:`__dict__ attributes `." +"of the class's namespace. See also: :attr:`__dict__ attributes " +"`." msgstr "" #: reference/datamodel.rst:1176 @@ -1325,22 +1329,22 @@ msgstr "" #: reference/datamodel.rst:1185 msgid "" "A dictionary containing :term:`variable annotations ` " -"collected during class body execution. For best practices on working with :" -"attr:`!__annotations__`, please see :ref:`annotations-howto`." +"collected during class body execution. For best practices on working " +"with :attr:`!__annotations__`, please see :ref:`annotations-howto`." msgstr "" #: reference/datamodel.rst:1192 msgid "" "Accessing the :attr:`!__annotations__` attribute of a class object directly " "may yield incorrect results in the presence of metaclasses. In addition, the " -"attribute may not exist for some classes. Use :func:`inspect." -"get_annotations` to retrieve class annotations safely." +"attribute may not exist for some classes. " +"Use :func:`inspect.get_annotations` to retrieve class annotations safely." msgstr "" #: reference/datamodel.rst:1199 msgid "" -"A :class:`tuple` containing the :ref:`type parameters ` of a :" -"ref:`generic class `." +"A :class:`tuple` containing the :ref:`type parameters ` of " +"a :ref:`generic class `." msgstr "" #: reference/datamodel.rst:1205 @@ -1398,16 +1402,16 @@ msgid "" "\"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:`~object." -"__getattr__` method, that is called to satisfy the lookup." +"class attribute is found, and the object's class has " +"a :meth:`~object.__getattr__` method, that is called to satisfy the lookup." msgstr "" #: reference/datamodel.rst:1259 msgid "" "Attribute assignments and deletions update the instance's dictionary, never " -"a class's dictionary. If the class has a :meth:`~object.__setattr__` or :" -"meth:`~object.__delattr__` method, this is called instead of updating the " -"instance dictionary directly." +"a class's dictionary. If the class has a :meth:`~object.__setattr__` " +"or :meth:`~object.__delattr__` method, this is called instead of updating " +"the instance dictionary directly." msgstr "" #: reference/datamodel.rst:1269 @@ -1435,9 +1439,9 @@ msgstr "" 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)." +"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 "" #: reference/datamodel.rst:1312 @@ -1465,14 +1469,15 @@ msgstr "" #: reference/datamodel.rst:1338 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." +"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 "" #: reference/datamodel.rst:1372 @@ -1577,9 +1582,9 @@ msgid "" "``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. See :ref:" -"`inspect-module-co-flags` for details on the semantics of each flags that " -"might be present." +"arguments; bit ``0x20`` is set if the function is a generator. " +"See :ref:`inspect-module-co-flags` for details on the semantics of each " +"flags that might be present." msgstr "" #: reference/datamodel.rst:1450 @@ -1598,9 +1603,9 @@ msgstr "" #: reference/datamodel.rst:1460 msgid "" -"If a code object represents a function, the first item in :attr:`~codeobject." -"co_consts` is the documentation string of the function, or ``None`` if " -"undefined." +"If a code object represents a function, the first item " +"in :attr:`~codeobject.co_consts` is the documentation string of the " +"function, or ``None`` if undefined." msgstr "" #: reference/datamodel.rst:1465 @@ -1663,9 +1668,9 @@ msgstr "" #: reference/datamodel.rst:1502 msgid "" -"Returns an iterator that yields information about successive ranges of :term:" -"`bytecode`\\s. Each item yielded is a ``(start, end, lineno)`` :class:" -"`tuple`:" +"Returns an iterator that yields information about successive ranges " +"of :term:`bytecode`\\s. Each item yielded is a ``(start, end, " +"lineno)`` :class:`tuple`:" msgstr "" #: reference/datamodel.rst:1506 @@ -1682,9 +1687,9 @@ msgstr "" #: reference/datamodel.rst:1510 msgid "" -"``lineno`` is an :class:`int` representing the line number of the :term:" -"`bytecode` range, or ``None`` if the bytecodes in the given range have no " -"line number" +"``lineno`` is an :class:`int` representing the line number of " +"the :term:`bytecode` range, or ``None`` if the bytecodes in the given range " +"have no line number" msgstr "" #: reference/datamodel.rst:1514 @@ -1708,8 +1713,8 @@ msgstr "" #: reference/datamodel.rst:1521 msgid "" -"The last :class:`tuple` yielded will have ``end`` equal to the size of the :" -"term:`bytecode`." +"The last :class:`tuple` yielded will have ``end`` equal to the size of " +"the :term:`bytecode`." msgstr "" #: reference/datamodel.rst:1524 @@ -1752,8 +1757,8 @@ msgstr "" #: reference/datamodel.rst:1571 msgid "" "The :ref:`code object ` being executed in this frame. " -"Accessing this attribute raises an :ref:`auditing event ` ``object." -"__getattr__`` with arguments ``obj`` and ``\"f_code\"``." +"Accessing this attribute raises an :ref:`auditing event ` " +"``object.__getattr__`` with arguments ``obj`` and ``\"f_code\"``." msgstr "" #: reference/datamodel.rst:1576 @@ -1774,8 +1779,8 @@ msgstr "" #: reference/datamodel.rst:1588 msgid "" -"The \"precise instruction\" of the frame object (this is an index into the :" -"term:`bytecode` string of the :ref:`code object `)" +"The \"precise instruction\" of the frame object (this is an index into " +"the :term:`bytecode` string of the :ref:`code object `)" msgstr "" #: reference/datamodel.rst:1604 @@ -1847,18 +1852,18 @@ msgid "" "For implicitly created tracebacks, 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 :func:" -"`sys.exc_info`, and as the :attr:`~BaseException.__traceback__` attribute of " -"the caught exception." +"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 :func:`sys.exc_info`, and as " +"the :attr:`~BaseException.__traceback__` attribute of the caught exception." msgstr "" #: reference/datamodel.rst:1675 msgid "" "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 :data:`sys." -"last_traceback`." +"interactive, it is also made available to the user " +"as :data:`sys.last_traceback`." msgstr "" #: reference/datamodel.rst:1680 @@ -1875,8 +1880,8 @@ msgstr "" #: reference/datamodel.rst:1698 msgid "" -"Accessing this attribute raises an :ref:`auditing event ` ``object." -"__getattr__`` with arguments ``obj`` and ``\"tb_frame\"``." +"Accessing this attribute raises an :ref:`auditing event ` " +"``object.__getattr__`` with arguments ``obj`` and ``\"tb_frame\"``." msgstr "" #: reference/datamodel.rst:1703 @@ -1918,9 +1923,9 @@ msgstr "" #: reference/datamodel.rst:1741 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." +"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 "" #: reference/datamodel.rst:1745 @@ -1962,8 +1967,8 @@ msgid "" "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 :ref:`\"instance methods\" `. Class method objects are created by the built-in :func:" -"`classmethod` constructor." +"methods>`. Class method objects are created by the built-" +"in :func:`classmethod` constructor." msgstr "" #: reference/datamodel.rst:1782 @@ -1976,21 +1981,21 @@ msgid "" "(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:" -"`~object.__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`)." +"language operators. For instance, if a class defines a method " +"named :meth:`~object.__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 "" #: reference/datamodel.rst:1799 msgid "" "Setting a special method to ``None`` indicates that the corresponding " -"operation is not available. For example, if a class sets :meth:`~object." -"__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:" -"`~object.__getitem__`). [#]_" +"operation is not available. For example, if a class " +"sets :meth:`~object.__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:`~object.__getitem__`). [#]_" msgstr "" #: reference/datamodel.rst:1805 @@ -2069,10 +2074,10 @@ msgstr "" #: reference/datamodel.rst:1871 msgid "" "Called when the instance is about to be destroyed. This is also called a " -"finalizer or (improperly) 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." +"finalizer or (improperly) 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." msgstr "" #: reference/datamodel.rst:1877 @@ -2127,8 +2132,8 @@ msgid "" ":meth:`__del__` can be invoked when arbitrary code is being executed, " "including from any arbitrary thread. If :meth:`__del__` needs to take a " "lock or invoke any other blocking resource, it may deadlock as the resource " -"may already be taken by the code that gets interrupted to execute :meth:" -"`__del__`." +"may already be taken by the code that gets interrupted to " +"execute :meth:`__del__`." msgstr "" #: reference/datamodel.rst:1920 @@ -2149,9 +2154,10 @@ msgid "" "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." +"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 "" #: reference/datamodel.rst:1944 @@ -2185,8 +2191,8 @@ msgstr "" #: reference/datamodel.rst:1975 msgid "" "Called by :ref:`bytes ` to compute a byte-string representation " -"of an object. This should return a :class:`bytes` object. The :class:" -"`object` class itself does not provide this method." +"of an object. This should return a :class:`bytes` object. " +"The :class:`object` class itself does not provide this method." msgstr "" #: reference/datamodel.rst:1987 @@ -2231,10 +2237,10 @@ msgstr "" #: reference/datamodel.rst:2024 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)``." +"between operator symbols and method names is as follows: ``xy`` calls " +"``x.__gt__(y)``, and ``x>=y`` calls ``x.__ge__(y)``." msgstr "" #: reference/datamodel.rst:2030 @@ -2250,14 +2256,15 @@ msgstr "" #: reference/datamodel.rst:2037 msgid "" -"By default, ``object`` implements :meth:`__eq__` by using ``is``, returning :" -"data:`NotImplemented` in the case of a false comparison: ``True if x is y " -"else NotImplemented``. For :meth:`__ne__`, by default it delegates to :meth:" -"`__eq__` and inverts the result unless it is :data:`!NotImplemented`. There " -"are no other implied relationships among the comparison operators or default " -"implementations; for example, the truth of ``(x` such as :class:`int`, :class:`bytes`, and :class:" -"`tuple`." +"` such as :class:`int`, :class:`bytes`, " +"and :class:`tuple`." msgstr "" #: reference/datamodel.rst:2531 @@ -2860,8 +2868,8 @@ msgstr "" msgid "" "If a :class:`dictionary ` is used to assign *__slots__*, the " "dictionary keys will be used as the slot names. The values of the dictionary " -"can be used to provide per-attribute docstrings that will be recognised by :" -"func:`inspect.getdoc` and displayed in the output of :func:`help`." +"can be used to provide per-attribute docstrings that will be recognised " +"by :func:`inspect.getdoc` and displayed in the output of :func:`help`." msgstr "" #: reference/datamodel.rst:2538 @@ -2891,12 +2899,13 @@ msgstr "" #: reference/datamodel.rst:2557 msgid "" -"Whenever a class inherits from another class, :meth:`~object." -"__init_subclass__` is called on the parent 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." +"Whenever a class inherits from another " +"class, :meth:`~object.__init_subclass__` is called on the parent 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 "" #: reference/datamodel.rst:2566 @@ -2959,9 +2968,9 @@ msgstr "" #: reference/datamodel.rst:2608 msgid "" -"If the class variable is assigned after the class is created, :meth:" -"`__set_name__` will not be called automatically. If needed, :meth:" -"`__set_name__` can be called directly::" +"If the class variable is assigned after the class is " +"created, :meth:`__set_name__` will not be called automatically. If " +"needed, :meth:`__set_name__` can be called directly::" msgstr "" #: reference/datamodel.rst:2612 @@ -3045,14 +3054,14 @@ msgstr "" #: reference/datamodel.rst:2669 msgid "" -"If a base that appears in a class definition is not an instance of :class:" -"`type`, then an :meth:`!__mro_entries__` method is searched on the base. If " -"an :meth:`!__mro_entries__` method is found, the base is substituted with " -"the result of a call to :meth:`!__mro_entries__` when creating the class. " -"The method is called with the original bases tuple passed to the *bases* " -"parameter, and must return a tuple of classes that will be used instead of " -"the base. The returned tuple may be empty: in these cases, the original base " -"is ignored." +"If a base that appears in a class definition is not an instance " +"of :class:`type`, then an :meth:`!__mro_entries__` method is searched on the " +"base. If an :meth:`!__mro_entries__` method is found, the base is " +"substituted with the result of a call to :meth:`!__mro_entries__` when " +"creating the class. The method is called with the original bases tuple " +"passed to the *bases* parameter, and must return a tuple of classes that " +"will be used instead of the base. The returned tuple may be empty: in these " +"cases, the original base is ignored." msgstr "" #: reference/datamodel.rst:2680 @@ -3069,8 +3078,8 @@ msgstr "" #: reference/datamodel.rst:2684 msgid "" -"Retrieve a class's \"original bases\" prior to modifications by :meth:" -"`~object.__mro_entries__`." +"Retrieve a class's \"original bases\" prior to modifications " +"by :meth:`~object.__mro_entries__`." msgstr "" #: reference/datamodel.rst:2687 @@ -3097,8 +3106,8 @@ msgstr "" #: reference/datamodel.rst:2699 msgid "" -"if an explicit metaclass is given and it is *not* an instance of :func:" -"`type`, then it is used directly as the metaclass;" +"if an explicit metaclass is given and it is *not* an instance " +"of :func:`type`, then it is used directly as the metaclass;" msgstr "" #: reference/datamodel.rst:2701 @@ -3185,10 +3194,10 @@ 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." +"``__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 "" #: reference/datamodel.rst:2780 @@ -3266,8 +3275,8 @@ msgstr "" #: reference/datamodel.rst:2824 msgid "" -"The following methods are used to override the default behavior of the :func:" -"`isinstance` and :func:`issubclass` built-in functions." +"The following methods are used to override the default behavior of " +"the :func:`isinstance` and :func:`issubclass` built-in functions." msgstr "" #: reference/datamodel.rst:2827 @@ -3306,11 +3315,11 @@ msgstr "" #: reference/datamodel.rst:2854 msgid "" -"Includes the specification for customizing :func:`isinstance` and :func:" -"`issubclass` behavior through :meth:`~type.__instancecheck__` and :meth:" -"`~type.__subclasscheck__`, with motivation for this functionality in the " -"context of adding Abstract Base Classes (see the :mod:`abc` module) to the " -"language." +"Includes the specification for customizing :func:`isinstance` " +"and :func:`issubclass` behavior through :meth:`~type.__instancecheck__` " +"and :meth:`~type.__subclasscheck__`, with motivation for this functionality " +"in the context of adding Abstract Base Classes (see the :mod:`abc` module) " +"to the language." msgstr "" #: reference/datamodel.rst:2862 @@ -3343,8 +3352,8 @@ msgstr "" #: reference/datamodel.rst:2877 msgid "" -":ref:`Generics`, :ref:`user-defined generics` and :" -"class:`typing.Generic`" +":ref:`Generics`, :ref:`user-defined generics` " +"and :class:`typing.Generic`" msgstr "" #: reference/datamodel.rst:2878 @@ -3368,8 +3377,8 @@ msgstr "" #: reference/datamodel.rst:2889 msgid "" "When defined on a class, ``__class_getitem__()`` is automatically a class " -"method. As such, there is no need for it to be decorated with :func:" -"`@classmethod` when it is defined." +"method. As such, there is no need for it to be decorated " +"with :func:`@classmethod` when it is defined." msgstr "" #: reference/datamodel.rst:2895 @@ -3387,9 +3396,10 @@ msgstr "" msgid "" "To implement custom generic classes that can be parameterized at runtime and " "understood by static type-checkers, users should either inherit from a " -"standard library class that already implements :meth:`~object." -"__class_getitem__`, or inherit from :class:`typing.Generic`, which has its " -"own implementation of ``__class_getitem__()``." +"standard library class that already " +"implements :meth:`~object.__class_getitem__`, or inherit " +"from :class:`typing.Generic`, which has its own implementation of " +"``__class_getitem__()``." msgstr "" #: reference/datamodel.rst:2907 @@ -3417,8 +3427,9 @@ msgstr "" #: reference/datamodel.rst:2926 msgid "" "Presented with the :term:`expression` ``obj[x]``, the Python interpreter " -"follows something like the following process to decide whether :meth:" -"`~object.__getitem__` or :meth:`~object.__class_getitem__` should be called::" +"follows something like the following process to decide " +"whether :meth:`~object.__getitem__` or :meth:`~object.__class_getitem__` " +"should be called::" msgstr "" #: reference/datamodel.rst:2931 @@ -3451,10 +3462,10 @@ msgstr "" msgid "" "In Python, all classes are themselves instances of other classes. The class " "of a class is known as that class's :term:`metaclass`, and most classes have " -"the :class:`type` class as their metaclass. :class:`type` does not define :" -"meth:`~object.__getitem__`, meaning that expressions such as ``list[int]``, " -"``dict[str, float]`` and ``tuple[str, bytes]`` all result in :meth:`~object." -"__class_getitem__` being called::" +"the :class:`type` class as their metaclass. :class:`type` does not " +"define :meth:`~object.__getitem__`, meaning that expressions such as " +"``list[int]``, ``dict[str, float]`` and ``tuple[str, bytes]`` all result " +"in :meth:`~object.__class_getitem__` being called::" msgstr "" #: reference/datamodel.rst:2961 @@ -3474,9 +3485,10 @@ msgstr "" #: reference/datamodel.rst:2973 msgid "" -"However, if a class has a custom metaclass that defines :meth:`~object." -"__getitem__`, subscribing the class may result in different behaviour. An " -"example of this can be found in the :mod:`enum` module::" +"However, if a class has a custom metaclass that " +"defines :meth:`~object.__getitem__`, subscribing the class may result in " +"different behaviour. An example of this can be found in the :mod:`enum` " +"module::" msgstr "" #: reference/datamodel.rst:2977 @@ -3505,9 +3517,9 @@ msgstr "" #: reference/datamodel.rst:2997 msgid "" -"Introducing :meth:`~object.__class_getitem__`, and outlining when a :ref:" -"`subscription` results in ``__class_getitem__()`` being " -"called instead of :meth:`~object.__getitem__`" +"Introducing :meth:`~object.__class_getitem__`, and outlining when " +"a :ref:`subscription` results in ``__class_getitem__()`` " +"being called instead of :meth:`~object.__getitem__`" msgstr "" #: reference/datamodel.rst:3005 @@ -3529,37 +3541,37 @@ msgstr "" msgid "" "The following methods can be defined to implement container objects. None of " "them are provided by the :class:`object` class itself. Containers usually " -"are :term:`sequences ` (such as :class:`lists ` or :class:" -"`tuples `) or :term:`mappings ` (like :term:`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 :" -"class:`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 :class:`dictionary ` objects. " -"The :mod:`collections.abc` module provides a :class:`~collections.abc." -"MutableMapping` :term:`abstract base class` to help create those methods " -"from a base set of :meth:`~object.__getitem__`, :meth:`~object." -"__setitem__`, :meth:`~object.__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 :class:`list` " -"objects. Finally, sequence types should implement addition (meaning " -"concatenation) and multiplication (meaning repetition) by defining the " -"methods :meth:`~object.__add__`, :meth:`~object.__radd__`, :meth:`~object." -"__iadd__`, :meth:`~object.__mul__`, :meth:`~object.__rmul__` and :meth:" -"`~object.__imul__` described below; they should not define other numerical " -"operators. It is recommended that both mappings and sequences implement " -"the :meth:`~object.__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:`~object.__iter__` " -"method to allow efficient iteration through the container; for mappings, :" -"meth:`!__iter__` should iterate through the object's keys; for sequences, it " -"should iterate through the values." +"are :term:`sequences ` (such as :class:`lists ` " +"or :class:`tuples `) or :term:`mappings ` " +"(like :term:`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 :class:`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 :class:`dictionary ` objects. The :mod:`collections.abc` " +"module provides a :class:`~collections.abc.MutableMapping` :term:`abstract " +"base class` to help create those methods from a base set " +"of :meth:`~object.__getitem__`, :meth:`~object.__setitem__`, :meth:`~object.__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 :class:`list` objects. Finally, sequence types should " +"implement addition (meaning concatenation) and multiplication (meaning " +"repetition) by defining the " +"methods :meth:`~object.__add__`, :meth:`~object.__radd__`, :meth:`~object.__iadd__`, :meth:`~object.__mul__`, :meth:`~object.__rmul__` " +"and :meth:`~object.__imul__` described below; they should not define other " +"numerical operators. It is recommended that both mappings and sequences " +"implement the :meth:`~object.__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:`~object.__iter__` method to allow efficient iteration through the " +"container; for mappings, :meth:`!__iter__` should iterate through the " +"object's keys; for sequences, it should iterate through the values." msgstr "" #: reference/datamodel.rst:3064 @@ -3573,20 +3585,20 @@ msgstr "" #: reference/datamodel.rst:3071 msgid "" "In CPython, the length is required to be at most :data:`sys.maxsize`. If the " -"length is larger than :data:`!sys.maxsize` some features (such as :func:" -"`len`) may raise :exc:`OverflowError`. To prevent raising :exc:`!" -"OverflowError` by truth value testing, an object must define a :meth:" -"`~object.__bool__` method." +"length is larger than :data:`!sys.maxsize` some features (such " +"as :func:`len`) may raise :exc:`OverflowError`. To prevent raising :exc:`!" +"OverflowError` by truth value testing, an object must define " +"a :meth:`~object.__bool__` method." msgstr "" #: reference/datamodel.rst:3080 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. The return value may also be :data:" -"`NotImplemented`, which is treated the same as if the ``__length_hint__`` " -"method didn't exist at all. This method is purely an optimization and is " -"never required for correctness." +"The length must be an integer ``>=`` 0. The return value may also " +"be :data:`NotImplemented`, which is treated the same as if the " +"``__length_hint__`` method didn't exist at all. This method is purely an " +"optimization and is never required for correctness." msgstr "" #: reference/datamodel.rst:3094 @@ -3613,13 +3625,13 @@ msgstr "" #: reference/datamodel.rst:3107 msgid "" "Called to implement evaluation of ``self[key]``. For :term:`sequence` types, " -"the accepted keys should be integers. Optionally, they may support :class:" -"`slice` objects as well. Negative index support is also optional. If *key* " -"is of an inappropriate type, :exc:`TypeError` may be raised; if *key* is a " -"value outside the set of indexes for the sequence (after any special " -"interpretation of negative values), :exc:`IndexError` should be raised. For :" -"term:`mapping` types, if *key* is missing (not in the container), :exc:" -"`KeyError` should be raised." +"the accepted keys should be integers. Optionally, they may " +"support :class:`slice` objects as well. Negative index support is also " +"optional. If *key* is of an inappropriate type, :exc:`TypeError` may be " +"raised; if *key* is a value outside the set of indexes for the sequence " +"(after any special interpretation of negative values), :exc:`IndexError` " +"should be raised. For :term:`mapping` types, if *key* is missing (not in the " +"container), :exc:`KeyError` should be raised." msgstr "" #: reference/datamodel.rst:3119 @@ -3630,27 +3642,28 @@ msgstr "" #: reference/datamodel.rst:3124 msgid "" -"When :ref:`subscripting` a *class*, the special class method :" -"meth:`~object.__class_getitem__` may be called instead of ``__getitem__()``. " -"See :ref:`classgetitem-versus-getitem` for more details." +"When :ref:`subscripting` a *class*, the special class " +"method :meth:`~object.__class_getitem__` may be called instead of " +"``__getitem__()``. See :ref:`classgetitem-versus-getitem` for more details." msgstr "" #: reference/datamodel.rst:3132 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." +"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 "" #: reference/datamodel.rst:3141 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." +"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 "" #: reference/datamodel.rst:3150 @@ -3677,10 +3690,10 @@ msgstr "" #: reference/datamodel.rst:3168 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`." +"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 "" #: reference/datamodel.rst:3175 @@ -3721,15 +3734,15 @@ msgstr "" #: reference/datamodel.rst:3223 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, ``type(x).__add__(x, 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." +"(``+``, ``-``, ``*``, ``@``, ``/``, ``//``, " +"``%``, :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, ``type(x).__add__(x, " +"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 "" #: reference/datamodel.rst:3234 @@ -3741,14 +3754,14 @@ msgstr "" #: reference/datamodel.rst:3257 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, ``type(y)." -"__rsub__(y, x)`` is called if ``type(x).__sub__(x, y)`` returns :data:" -"`NotImplemented`." +"(``+``, ``-``, ``*``, ``@``, ``/``, ``//``, " +"``%``, :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, ``type(y).__rsub__(y, x)`` is called if " +"``type(x).__sub__(x, y)`` returns :data:`NotImplemented`." msgstr "" #: reference/datamodel.rst:3269 @@ -3775,25 +3788,25 @@ msgid "" "but does not have to be, *self*). If a specific method is not defined, or " "if that method returns :data:`NotImplemented`, 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)`` . If :meth:`__iadd__` does not exist, or if ``x.__iadd__(y)`` " -"returns :data:`!NotImplemented`, ``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." +"class with an :meth:`__iadd__` method, ``x += y`` is equivalent to ``x = " +"x.__iadd__(y)`` . If :meth:`__iadd__` does not exist, or if " +"``x.__iadd__(y)`` returns :data:`!NotImplemented`, ``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 "" #: reference/datamodel.rst:3318 msgid "" -"Called to implement the unary arithmetic operations (``-``, ``+``, :func:" -"`abs` and ``~``)." +"Called to implement the unary arithmetic operations (``-``, " +"``+``, :func:`abs` and ``~``)." msgstr "" #: reference/datamodel.rst:3331 msgid "" -"Called to implement the built-in functions :func:`complex`, :func:`int` and :" -"func:`float`. Should return a value of the appropriate type." +"Called to implement the built-in functions :func:`complex`, :func:`int` " +"and :func:`float`. Should return a value of the appropriate type." msgstr "" #: reference/datamodel.rst:3338 @@ -3923,8 +3936,8 @@ msgid "" "\"right\")`` that means that ``case MyClass(x, y)`` is equivalent to ``case " "MyClass(left=x, center=y)``. Note that the number of arguments in the " "pattern must be smaller than or equal to the number of elements in " -"*__match_args__*; if it is larger, the pattern match attempt will raise a :" -"exc:`TypeError`." +"*__match_args__*; if it is larger, the pattern match attempt will raise " +"a :exc:`TypeError`." msgstr "" #: reference/datamodel.rst:3448 @@ -3955,21 +3968,22 @@ msgstr "" #: reference/datamodel.rst:3467 msgid "" -"Called when a buffer is requested from *self* (for example, by the :class:" -"`memoryview` constructor). The *flags* argument is an integer representing " -"the kind of buffer requested, affecting for example whether the returned " -"buffer is read-only or writable. :class:`inspect.BufferFlags` provides a " -"convenient way to interpret the flags. The method must return a :class:" -"`memoryview` object." +"Called when a buffer is requested from *self* (for example, by " +"the :class:`memoryview` constructor). The *flags* argument is an integer " +"representing the kind of buffer requested, affecting for example whether the " +"returned buffer is read-only or writable. :class:`inspect.BufferFlags` " +"provides a convenient way to interpret the flags. The method must return " +"a :class:`memoryview` object." msgstr "" #: reference/datamodel.rst:3476 msgid "" -"Called when a buffer is no longer needed. The *buffer* argument is a :class:" -"`memoryview` object that was previously returned by :meth:`~object." -"__buffer__`. The method must release any resources associated with the " -"buffer. This method should return ``None``. Buffer objects that do not need " -"to perform any cleanup are not required to implement this method." +"Called when a buffer is no longer needed. The *buffer* argument is " +"a :class:`memoryview` object that was previously returned " +"by :meth:`~object.__buffer__`. The method must release any resources " +"associated with the buffer. This method should return ``None``. Buffer " +"objects that do not need to perform any cleanup are not required to " +"implement this method." msgstr "" #: reference/datamodel.rst:3487 @@ -4051,8 +4065,8 @@ msgstr "" #: reference/datamodel.rst:3536 msgid "" "In addition to bypassing any instance attributes in the interest of " -"correctness, implicit special method lookup generally also bypasses the :" -"meth:`~object.__getattribute__` method even of the object's metaclass::" +"correctness, implicit special method lookup generally also bypasses " +"the :meth:`~object.__getattribute__` method even of the object's metaclass::" msgstr "" #: reference/datamodel.rst:3540 @@ -4099,32 +4113,33 @@ msgstr "" #: reference/datamodel.rst:3579 msgid "" -"An :term:`awaitable` object generally implements an :meth:`~object." -"__await__` method. :term:`Coroutine objects ` returned from :" -"keyword:`async def` functions are awaitable." +"An :term:`awaitable` object generally implements " +"an :meth:`~object.__await__` method. :term:`Coroutine objects ` " +"returned from :keyword:`async def` functions are awaitable." msgstr "" #: reference/datamodel.rst:3585 msgid "" "The :term:`generator iterator` objects returned from generators decorated " -"with :func:`types.coroutine` are also awaitable, but they do not implement :" -"meth:`~object.__await__`." +"with :func:`types.coroutine` are also awaitable, but they do not " +"implement :meth:`~object.__await__`." msgstr "" #: reference/datamodel.rst:3591 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. The :class:" -"`object` class itself is not awaitable and does not provide this method." +"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. The :class:`object` class itself is not awaitable and does not " +"provide this method." msgstr "" #: reference/datamodel.rst:3599 msgid "" "The language doesn't place any restriction on the type or value of the " "objects yielded by the iterator returned by ``__await__``, as this is " -"specific to the implementation of the asynchronous execution framework (e." -"g. :mod:`asyncio`) that will be managing the :term:`awaitable` object." +"specific to the implementation of the asynchronous execution framework " +"(e.g. :mod:`asyncio`) that will be managing the :term:`awaitable` object." msgstr "" #: reference/datamodel.rst:3607 @@ -4140,10 +4155,11 @@ msgid "" ":term:`Coroutine objects ` are :term:`awaitable` objects. A " "coroutine's execution can be controlled by calling :meth:`~object.__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." +"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 "" #: reference/datamodel.rst:3623 @@ -4160,12 +4176,12 @@ msgstr "" #: reference/datamodel.rst:3633 msgid "" "Starts or resumes execution of the coroutine. If *value* is ``None``, this " -"is equivalent to advancing the iterator returned by :meth:`~object." -"__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." +"is equivalent to advancing the iterator returned " +"by :meth:`~object.__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 "" #: reference/datamodel.rst:3644 @@ -4173,10 +4189,11 @@ 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:`~object.__await__` return value, described above. If the exception is " -"not caught in the coroutine, it propagates back to the caller." +"raised at the suspension point. The result (return " +"value, :exc:`StopIteration`, or other exception) is the same as when " +"iterating over the :meth:`~object.__await__` return value, described above. " +"If the exception is not caught in the coroutine, it propagates back to the " +"caller." msgstr "" #: reference/datamodel.rst:3655 @@ -4260,8 +4277,8 @@ msgstr "" #: reference/datamodel.rst:3715 msgid "" "Starting with Python 3.7, :meth:`~object.__aiter__` must return an " -"asynchronous iterator object. Returning anything else will result in a :exc:" -"`TypeError` error." +"asynchronous iterator object. Returning anything else will result in " +"a :exc:`TypeError` error." msgstr "" #: reference/datamodel.rst:3723 @@ -4319,10 +4336,10 @@ msgstr "" #: reference/datamodel.rst:3760 msgid "" -"The :meth:`~object.__hash__`, :meth:`~object.__iter__`, :meth:`~object." -"__reversed__`, and :meth:`~object.__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." +"The :meth:`~object.__hash__`, :meth:`~object.__iter__`, :meth:`~object.__reversed__`, " +"and :meth:`~object.__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 "" #: reference/datamodel.rst:3766 diff --git a/reference/executionmodel.po b/reference/executionmodel.po index 3e40e0110..4d62af09e 100644 --- a/reference/executionmodel.po +++ b/reference/executionmodel.po @@ -33,9 +33,9 @@ msgid "" "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 :option:`-c` option) is a code block. A module run as " -"a top level script (as module ``__main__``) from the command line using a :" -"option:`-m` argument is also a code block. The string argument passed to the " -"built-in functions :func:`eval` and :func:`exec` is a code block." +"a top level script (as module ``__main__``) from the command line using " +"a :option:`-m` argument is also a code block. The string argument passed to " +"the built-in functions :func:`eval` and :func:`exec` is a code block." msgstr "" #: reference/executionmodel.rst:33 @@ -171,8 +171,8 @@ 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`." +"is used, an :exc:`UnboundLocalError` exception is " +"raised. :exc:`UnboundLocalError` is a subclass of :exc:`NameError`." msgstr "" #: reference/executionmodel.rst:127 @@ -193,11 +193,12 @@ msgid "" "names specified in the statement refer to the bindings of those names 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 names are not " -"found there, the builtins namespace is searched next. If the names are also " -"not found in the builtins namespace, new variables are created in the global " -"namespace. The global statement must precede all uses of the listed names." +"the code block, and the builtins namespace, the namespace of the " +"module :mod:`builtins`. The global namespace is searched first. If the " +"names are not found there, the builtins namespace is searched next. If the " +"names are also not found in the builtins namespace, new variables are " +"created in the global namespace. The global statement must precede all uses " +"of the listed names." msgstr "" #: reference/executionmodel.rst:146 @@ -211,10 +212,10 @@ msgstr "" #: reference/executionmodel.rst:152 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. :ref:`Type parameters ` cannot be " -"rebound with the :keyword:`!nonlocal` statement." +"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. :ref:`Type parameters ` cannot be rebound with the :keyword:`!nonlocal` statement." msgstr "" #: reference/executionmodel.rst:160 @@ -322,17 +323,17 @@ msgstr "" #: reference/executionmodel.rst:220 msgid "" "Expressions in annotation scopes cannot contain :keyword:`yield`, ``yield " -"from``, :keyword:`await`, or :token:`:= ` expressions. (These expressions are allowed in other " -"scopes contained within the annotation scope.)" +"from``, :keyword:`await`, or :token:`:= ` expressions. (These expressions are allowed " +"in other scopes contained within the annotation scope.)" msgstr "" #: reference/executionmodel.rst:224 msgid "" -"Names defined in annotation scopes cannot be rebound with :keyword:" -"`nonlocal` statements in inner scopes. This includes only type parameters, " -"as no other syntactic elements that can appear within annotation scopes can " -"introduce new names." +"Names defined in annotation scopes cannot be rebound " +"with :keyword:`nonlocal` statements in inner scopes. This includes only type " +"parameters, as no other syntactic elements that can appear within annotation " +"scopes can introduce new names." msgstr "" #: reference/executionmodel.rst:227 @@ -416,9 +417,9 @@ msgstr "" #: reference/executionmodel.rst:292 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." +"detail. Users wanting to override values in the builtins namespace " +"should :keyword:`import` the :mod:`builtins` module and modify its " +"attributes appropriately." msgstr "" #: reference/executionmodel.rst:297 @@ -428,8 +429,8 @@ msgid "" "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." +"other module, ``__builtins__`` is an alias for the dictionary of " +"the :mod:`builtins` module itself." msgstr "" #: reference/executionmodel.rst:309 @@ -456,10 +457,10 @@ 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." +"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 "" #: reference/executionmodel.rst:333 @@ -480,9 +481,9 @@ 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 " +"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 "" @@ -498,8 +499,8 @@ msgstr "" 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 traceback, except when the exception is :exc:" -"`SystemExit`." +"either case, it prints a stack traceback, except when the exception " +"is :exc:`SystemExit`." msgstr "" #: reference/executionmodel.rst:371 @@ -521,8 +522,8 @@ msgstr "" #: reference/executionmodel.rst:383 msgid "" -"See also the description of the :keyword:`try` statement in section :ref:" -"`try` and :keyword:`raise` statement in section :ref:`raise`." +"See also the description of the :keyword:`try` statement in " +"section :ref:`try` and :keyword:`raise` statement in section :ref:`raise`." msgstr "" #: reference/executionmodel.rst:388 diff --git a/reference/expressions.po b/reference/expressions.po index cc147946a..74905d6de 100644 --- a/reference/expressions.po +++ b/reference/expressions.po @@ -88,16 +88,16 @@ msgstr "" #: 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." +"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 "" #: 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." +"object. When a name is not bound, an attempt to evaluate it raises " +"a :exc:`NameError` exception." msgstr "" #: reference/expressions.rst:87 @@ -243,8 +243,8 @@ msgstr "" #: reference/expressions.rst:203 msgid "" -"they are computed via a set of looping and filtering instructions, called a :" -"dfn:`comprehension`." +"they are computed via a set of looping and filtering instructions, called " +"a :dfn:`comprehension`." msgstr "" #: reference/expressions.rst:211 @@ -253,9 +253,9 @@ msgstr "" #: reference/expressions.rst:219 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 " +"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." @@ -290,8 +290,8 @@ msgstr "" msgid "" "Since Python 3.6, in an :keyword:`async def` function, an :keyword:`!async " "for` clause may be used to iterate over a :term:`asynchronous iterator`. A " -"comprehension in an :keyword:`!async def` function may consist of either a :" -"keyword:`!for` or :keyword:`!async for` clause following the leading " +"comprehension in an :keyword:`!async def` function may consist of either " +"a :keyword:`!for` or :keyword:`!async for` clause following the leading " "expression, may contain additional :keyword:`!for` or :keyword:`!async for` " "clauses, and may also use :keyword:`await` expressions." msgstr "" @@ -412,11 +412,11 @@ msgstr "" #: reference/expressions.rst:375 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 value (textually rightmost in the display) stored for a " -"given key value prevails." +"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 value (textually rightmost in the " +"display) stored for a given key value prevails." msgstr "" #: reference/expressions.rst:381 @@ -444,16 +444,16 @@ msgstr "" #: reference/expressions.rst:407 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 iterable expression in the " -"leftmost :keyword:`!for` clause is immediately evaluated, so that an error " -"produced by it will be emitted at the point where the generator expression " -"is defined, rather than at the point where the first value is retrieved. " -"Subsequent :keyword:`!for` clauses and any filter condition in the leftmost :" -"keyword:`!for` clause cannot be evaluated in the enclosing scope as they may " -"depend on the values obtained from the leftmost iterable. For example: " -"``(x*y for x in range(10) for y in range(x, x+10))``." +"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 iterable " +"expression in the leftmost :keyword:`!for` clause is immediately evaluated, " +"so that an error produced by it will be emitted at the point where the " +"generator expression is defined, rather than at the point where the first " +"value is retrieved. Subsequent :keyword:`!for` clauses and any filter " +"condition in the leftmost :keyword:`!for` clause cannot be evaluated in the " +"enclosing scope as they may depend on the values obtained from the leftmost " +"iterable. For example: ``(x*y for x in range(10) for y in range(x, x+10))``." msgstr "" #: reference/expressions.rst:418 @@ -471,11 +471,11 @@ msgstr "" #: reference/expressions.rst:425 msgid "" -"If a generator expression contains either :keyword:`!async for` clauses or :" -"keyword:`await` expressions it is called an :dfn:`asynchronous generator " +"If a generator expression contains either :keyword:`!async for` clauses " +"or :keyword:`await` expressions it is called an :dfn:`asynchronous generator " "expression`. An asynchronous generator expression returns a new " -"asynchronous generator object, which is an asynchronous iterator (see :ref:" -"`async-iterators`)." +"asynchronous generator object, which is an asynchronous iterator " +"(see :ref:`async-iterators`)." msgstr "" #: reference/expressions.rst:431 @@ -498,9 +498,9 @@ msgid "" "The yield expression is used when defining a :term:`generator` function or " "an :term:`asynchronous 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 function, and using it in an :" -"keyword:`async def` function's body causes that coroutine function to be an " -"asynchronous generator function. For example::" +"body causes that function to be a generator function, and using it in " +"an :keyword:`async def` function's body causes that coroutine function to be " +"an asynchronous generator function. For example::" msgstr "" #: reference/expressions.rst:466 @@ -538,19 +538,19 @@ msgid "" "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:`~python-grammar:" -"yield_list` to the generator's caller, or ``None`` if :token:`~python-" -"grammar:yield_list` is omitted. 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 " +"where it is suspended again, returning the value of :token:`~python-" +"grammar:yield_list` to the generator's caller, or ``None`` " +"if :token:`~python-grammar:yield_list` is omitted. 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." +"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 "" #: reference/expressions.rst:504 @@ -566,30 +566,31 @@ msgstr "" 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." +"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 "" #: reference/expressions.rst:519 msgid "" "When ``yield from `` is used, the supplied expression must be an " "iterable. The values produced by iterating that iterable 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." +"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 "" #: reference/expressions.rst:528 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 subiterator is a generator (by " -"returning a value from the subgenerator)." +"the yield expression. It can be either set explicitly when " +"raising :exc:`StopIteration`, or automatically when the subiterator is a " +"generator (by returning a value from the subgenerator)." msgstr "" #: reference/expressions.rst:534 @@ -661,13 +662,13 @@ msgstr "" #: reference/expressions.rst:574 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 " +"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:`~python-grammar:yield_list` is returned to :meth:`__next__`'s " -"caller. If the generator exits without yielding another value, a :exc:" -"`StopIteration` exception is raised." +"expression, where the generator is suspended again, and the value of " +"the :token:`~python-grammar:yield_list` is returned to :meth:`__next__`'s " +"caller. If the generator exits without yielding another value, " +"a :exc:`StopIteration` exception is raised." msgstr "" #: reference/expressions.rst:583 @@ -724,10 +725,10 @@ 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." +"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 "" #: reference/expressions.rst:640 @@ -780,9 +781,9 @@ msgstr "" #: reference/expressions.rst:677 msgid "" -"The presence of a yield expression in a function or method defined using :" -"keyword:`async def` further defines the function as an :term:`asynchronous " -"generator` function." +"The presence of a yield expression in a function or method defined " +"using :keyword:`async def` further defines the function as " +"an :term:`asynchronous generator` function." msgstr "" #: reference/expressions.rst:681 @@ -791,26 +792,27 @@ msgid "" "asynchronous iterator known as an asynchronous generator object. That object " "then controls the execution of the generator function. An asynchronous " "generator object is typically used in an :keyword:`async for` statement in a " -"coroutine function analogously to how a generator object would be used in a :" -"keyword:`for` statement." +"coroutine function analogously to how a generator object would be used in " +"a :keyword:`for` statement." msgstr "" #: reference/expressions.rst:688 msgid "" -"Calling one of the asynchronous generator's methods returns an :term:" -"`awaitable` object, and the execution starts when this object is awaited on. " -"At that time, the execution proceeds to the first yield expression, where it " -"is suspended again, returning the value of :token:`~python-grammar:" -"yield_list` to the awaiting coroutine. As with a generator, suspension means " -"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 awaiting " -"on the next object returned by the asynchronous 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:`~agen.__anext__` is used " -"then the result is :const:`None`. Otherwise, if :meth:`~agen.asend` is used, " -"then the result will be the value passed in to that method." +"Calling one of the asynchronous generator's methods returns " +"an :term:`awaitable` object, and the execution starts when this object is " +"awaited on. At that time, the execution proceeds to the first yield " +"expression, where it is suspended again, returning the value " +"of :token:`~python-grammar:yield_list` to the awaiting coroutine. As with a " +"generator, suspension means 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 awaiting on the next object returned by the " +"asynchronous 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:`~agen.__anext__` is used then the result " +"is :const:`None`. Otherwise, if :meth:`~agen.asend` is used, then the result " +"will be the value passed in to that method." msgstr "" #: reference/expressions.rst:703 @@ -844,12 +846,12 @@ msgid "" "To take care of finalization upon event loop termination, an event loop " "should define a *finalizer* function which takes an asynchronous generator-" "iterator and presumably calls :meth:`~agen.aclose` and executes the " -"coroutine. This *finalizer* may be registered by calling :func:`sys." -"set_asyncgen_hooks`. When first iterated over, an asynchronous generator-" -"iterator will store the registered *finalizer* to be called upon " -"finalization. For a reference example of a *finalizer* method see the " -"implementation of ``asyncio.Loop.shutdown_asyncgens`` in :source:`Lib/" -"asyncio/base_events.py`." +"coroutine. This *finalizer* may be registered by " +"calling :func:`sys.set_asyncgen_hooks`. When first iterated over, an " +"asynchronous generator-iterator will store the registered *finalizer* to be " +"called upon finalization. For a reference example of a *finalizer* method " +"see the implementation of ``asyncio.Loop.shutdown_asyncgens`` " +"in :source:`Lib/asyncio/base_events.py`." msgstr "" #: reference/expressions.rst:733 @@ -878,9 +880,9 @@ msgid "" "expression. The value of the :token:`~python-grammar:yield_list` of the " "yield expression is the value of the :exc:`StopIteration` exception raised " "by the completing coroutine. If the asynchronous generator exits without " -"yielding another value, the awaitable instead raises a :exc:" -"`StopAsyncIteration` exception, signalling that the asynchronous iteration " -"has completed." +"yielding another value, the awaitable instead raises " +"a :exc:`StopAsyncIteration` exception, signalling that the asynchronous " +"iteration has completed." msgstr "" #: reference/expressions.rst:762 @@ -895,24 +897,24 @@ msgid "" "generator, this \"sends\" a value into the asynchronous generator function, " "and the *value* argument becomes the result of the current yield expression. " "The awaitable returned by the :meth:`asend` method will return the next " -"value yielded by the generator as the value of the raised :exc:" -"`StopIteration`, or raises :exc:`StopAsyncIteration` if the asynchronous " -"generator exits without yielding another value. When :meth:`asend` is " -"called to start the asynchronous generator, it must be called with :const:" -"`None` as the argument, because there is no yield expression that could " -"receive the value." +"value yielded by the generator as the value of the " +"raised :exc:`StopIteration`, or raises :exc:`StopAsyncIteration` if the " +"asynchronous generator exits without yielding another value. " +"When :meth:`asend` is called to start the asynchronous generator, it must be " +"called with :const:`None` as the argument, because there is no yield " +"expression that could receive the value." msgstr "" #: reference/expressions.rst:783 msgid "" "Returns an awaitable that raises an exception of type ``type`` at the point " "where the asynchronous generator was paused, and returns the next value " -"yielded by the generator function as the value of the raised :exc:" -"`StopIteration` exception. If the asynchronous generator exits without " -"yielding another value, a :exc:`StopAsyncIteration` exception is raised by " -"the awaitable. If the generator function does not catch the passed-in " -"exception, or raises a different exception, then when the awaitable is run " -"that exception propagates to the caller of the awaitable." +"yielded by the generator function as the value of the " +"raised :exc:`StopIteration` exception. If the asynchronous generator exits " +"without yielding another value, a :exc:`StopAsyncIteration` exception is " +"raised by the awaitable. If the generator function does not catch the passed-" +"in exception, or raises a different exception, then when the awaitable is " +"run that exception propagates to the caller of the awaitable." msgstr "" #: reference/expressions.rst:803 @@ -960,10 +962,11 @@ msgstr "" #: reference/expressions.rst:855 msgid "" -"This production can be customized by overriding the :meth:`~object." -"__getattribute__` method or the :meth:`~object.__getattr__` method. The :" -"meth:`!__getattribute__` method is called first and either returns a value " -"or raises :exc:`AttributeError` if the attribute is not available." +"This production can be customized by overriding " +"the :meth:`~object.__getattribute__` method or " +"the :meth:`~object.__getattr__` method. The :meth:`!__getattribute__` " +"method is called first and either returns a value or " +"raises :exc:`AttributeError` if the attribute is not available." msgstr "" #: reference/expressions.rst:861 @@ -979,9 +982,9 @@ msgstr "" #: reference/expressions.rst:882 msgid "" "The subscription of an instance of a :ref:`container class ` " -"will generally select an element from the container. The subscription of a :" -"term:`generic class ` will generally return a :ref:" -"`GenericAlias ` object." +"will generally select an element from the container. The subscription of " +"a :term:`generic class ` will generally return " +"a :ref:`GenericAlias ` object." msgstr "" #: reference/expressions.rst:890 @@ -993,18 +996,19 @@ msgstr "" #: reference/expressions.rst:893 msgid "" "The primary must evaluate to an object that supports subscription. An object " -"may support subscription through defining one or both of :meth:`~object." -"__getitem__` and :meth:`~object.__class_getitem__`. When the primary is " -"subscripted, the evaluated result of the expression list will be passed to " -"one of these methods. For more details on when ``__class_getitem__`` is " -"called instead of ``__getitem__``, see :ref:`classgetitem-versus-getitem`." +"may support subscription through defining one or both " +"of :meth:`~object.__getitem__` and :meth:`~object.__class_getitem__`. When " +"the primary is subscripted, the evaluated result of the expression list will " +"be passed to one of these methods. For more details on when " +"``__class_getitem__`` is called instead of ``__getitem__``, " +"see :ref:`classgetitem-versus-getitem`." msgstr "" #: reference/expressions.rst:900 msgid "" "If the expression list contains at least one comma, or if any of the " -"expressions are starred, the expression list will evaluate to a :class:" -"`tuple` containing the items of the expression list. Otherwise, the " +"expressions are starred, the expression list will evaluate to " +"a :class:`tuple` containing the items of the expression list. Otherwise, the " "expression list will evaluate to the value of the list's sole member." msgstr "" @@ -1030,22 +1034,22 @@ msgstr "" msgid "" "Sequences. If the primary is a :term:`sequence`, the expression list must " "evaluate to an :class:`int` or a :class:`slice` (as discussed in the " -"following section). Examples of builtin sequence classes include the :class:" -"`str`, :class:`list` and :class:`tuple` classes." +"following section). Examples of builtin sequence classes include " +"the :class:`str`, :class:`list` and :class:`tuple` classes." msgstr "" #: reference/expressions.rst:920 msgid "" -"The formal syntax makes no special provision for negative indices in :term:" -"`sequences `. However, built-in sequences all provide a :meth:" -"`~object.__getitem__` method that interprets negative indices by adding the " -"length of the sequence to the index so that, for example, ``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:`~object." -"__getitem__` method, subclasses overriding this method will need to " -"explicitly add that support." +"The formal syntax makes no special provision for negative indices " +"in :term:`sequences `. However, built-in sequences all provide " +"a :meth:`~object.__getitem__` method that interprets negative indices by " +"adding the length of the sequence to the index so that, for example, " +"``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:`~object.__getitem__` method, subclasses overriding this " +"method will need to explicitly add that support." msgstr "" #: reference/expressions.rst:934 @@ -1085,10 +1089,10 @@ msgid "" "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." +"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 "" #: reference/expressions.rst:1005 @@ -1143,8 +1147,8 @@ 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." +"CPython, this is the case for functions implemented in C that " +"use :c:func:`PyArg_ParseTuple` to parse their arguments." msgstr "" #: reference/expressions.rst:1064 @@ -1158,8 +1162,8 @@ msgstr "" #: reference/expressions.rst:1070 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 " +"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 " @@ -1347,8 +1351,9 @@ msgstr "" #: reference/expressions.rst:1238 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`.)" +"Raising a negative number to a fractional power results in " +"a :class:`complex` number. (In earlier versions it raised " +"a :exc:`ValueError`.)" msgstr "" #: reference/expressions.rst:1242 @@ -1382,14 +1387,14 @@ msgstr "" 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 or to custom objects that override the :" -"meth:`~object.__invert__` special method." +"It only applies to integral numbers or to custom objects that override " +"the :meth:`~object.__invert__` special method." msgstr "" #: reference/expressions.rst:1289 msgid "" -"In all three cases, if the argument does not have the proper type, a :exc:" -"`TypeError` exception is raised." +"In all three cases, if the argument does not have the proper type, " +"a :exc:`TypeError` exception is raised." msgstr "" #: reference/expressions.rst:1296 @@ -1428,8 +1433,8 @@ msgstr "" #: reference/expressions.rst:1331 msgid "" -"This operation can be customized using the special :meth:`~object." -"__matmul__` and :meth:`~object.__rmatmul__` methods." +"This operation can be customized using the " +"special :meth:`~object.__matmul__` and :meth:`~object.__rmatmul__` methods." msgstr "" #: reference/expressions.rst:1342 @@ -1444,10 +1449,11 @@ msgstr "" #: reference/expressions.rst:1349 msgid "" -"The division operation can be customized using the special :meth:`~object." -"__truediv__` and :meth:`~object.__rtruediv__` methods. The floor division " -"operation can be customized using the special :meth:`~object.__floordiv__` " -"and :meth:`~object.__rfloordiv__` methods." +"The division operation can be customized using the " +"special :meth:`~object.__truediv__` and :meth:`~object.__rtruediv__` " +"methods. The floor division operation can be customized using the " +"special :meth:`~object.__floordiv__` and :meth:`~object.__rfloordiv__` " +"methods." msgstr "" #: reference/expressions.rst:1358 @@ -1481,8 +1487,8 @@ msgstr "" #: reference/expressions.rst:1377 msgid "" -"The *modulo* operation can be customized using the special :meth:`~object." -"__mod__` and :meth:`~object.__rmod__` methods." +"The *modulo* operation can be customized using the " +"special :meth:`~object.__mod__` and :meth:`~object.__rmod__` methods." msgstr "" #: reference/expressions.rst:1380 @@ -1535,10 +1541,10 @@ msgstr "" #: reference/expressions.rst:1427 msgid "" -"The left shift operation can be customized using the special :meth:`~object." -"__lshift__` and :meth:`~object.__rlshift__` methods. The right shift " -"operation can be customized using the special :meth:`~object.__rshift__` " -"and :meth:`~object.__rrshift__` methods." +"The left shift operation can be customized using the " +"special :meth:`~object.__lshift__` and :meth:`~object.__rlshift__` methods. " +"The right shift operation can be customized using the " +"special :meth:`~object.__rshift__` and :meth:`~object.__rrshift__` methods." msgstr "" #: reference/expressions.rst:1434 @@ -1558,22 +1564,24 @@ msgstr "" #: reference/expressions.rst:1456 msgid "" "The ``&`` operator yields the bitwise AND of its arguments, which must be " -"integers or one of them must be a custom object overriding :meth:`~object." -"__and__` or :meth:`~object.__rand__` special methods." +"integers or one of them must be a custom object " +"overriding :meth:`~object.__and__` or :meth:`~object.__rand__` special " +"methods." msgstr "" #: reference/expressions.rst:1465 msgid "" "The ``^`` operator yields the bitwise XOR (exclusive OR) of its arguments, " -"which must be integers or one of them must be a custom object overriding :" -"meth:`~object.__xor__` or :meth:`~object.__rxor__` special methods." +"which must be integers or one of them must be a custom object " +"overriding :meth:`~object.__xor__` or :meth:`~object.__rxor__` special " +"methods." msgstr "" #: reference/expressions.rst:1474 msgid "" "The ``|`` operator yields the bitwise (inclusive) OR of its arguments, which " -"must be integers or one of them must be a custom object overriding :meth:" -"`~object.__or__` or :meth:`~object.__ror__` special methods." +"must be integers or one of them must be a custom object " +"overriding :meth:`~object.__or__` or :meth:`~object.__ror__` special methods." msgstr "" #: reference/expressions.rst:1482 @@ -1717,8 +1725,8 @@ msgstr "" #: reference/expressions.rst:1588 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. [#]_" +"numerical Unicode code points (the result of the built-in " +"function :func:`ord`) of their characters. [#]_" msgstr "" #: reference/expressions.rst:1592 @@ -1787,9 +1795,9 @@ msgid "" "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)." +"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 "" #: reference/expressions.rst:1635 @@ -1875,8 +1883,8 @@ msgstr "" #: reference/expressions.rst:1675 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." +"sequences, but not to sets or mappings). See also " +"the :func:`~functools.total_ordering` decorator." msgstr "" #: reference/expressions.rst:1679 @@ -1900,10 +1908,11 @@ 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)``." +"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 "" #: reference/expressions.rst:1702 @@ -1932,11 +1941,12 @@ msgstr "" #: reference/expressions.rst:1717 msgid "" -"Lastly, the old-style iteration protocol is tried: if a class defines :meth:" -"`~object.__getitem__`, ``x in y`` is ``True`` if and only if there is a non-" -"negative integer index *i* such that ``x is y[i] or x == y[i]``, and no " -"lower integer index raises the :exc:`IndexError` exception. (If any other " -"exception is raised, it is as if :keyword:`in` raised that exception)." +"Lastly, the old-style iteration protocol is tried: if a class " +"defines :meth:`~object.__getitem__`, ``x in y`` is ``True`` if and only if " +"there is a non-negative integer index *i* such that ``x is y[i] or x == " +"y[i]``, and no lower integer index raises the :exc:`IndexError` exception. " +"(If any other exception is raised, it is as if :keyword:`in` raised that " +"exception)." msgstr "" #: reference/expressions.rst:1729 @@ -1968,8 +1978,8 @@ msgid "" "``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:`~object." -"__bool__` method." +"objects can customize their truth value by providing " +"a :meth:`~object.__bool__` method." msgstr "" #: reference/expressions.rst:1776 @@ -2008,9 +2018,9 @@ msgstr "" #: reference/expressions.rst:1810 msgid "" "An assignment expression (sometimes also called a \"named expression\" or " -"\"walrus\") assigns an :token:`~python-grammar:expression` to an :token:" -"`~python-grammar:identifier`, while also returning the value of the :token:" -"`~python-grammar:expression`." +"\"walrus\") assigns an :token:`~python-grammar:expression` to " +"an :token:`~python-grammar:identifier`, while also returning the value of " +"the :token:`~python-grammar:expression`." msgstr "" #: reference/expressions.rst:1815 @@ -2123,8 +2133,8 @@ msgstr "" #: reference/expressions.rst:1936 msgid "" -"A trailing comma is required only to create a one-item tuple, such as ``1," -"``; it is optional in all other cases. A single expression without a " +"A trailing comma is required only to create a one-item tuple, such as " +"``1,``; 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: " "``()``.)" diff --git a/reference/grammar.po b/reference/grammar.po index 7289b9105..954e1c2cc 100644 --- a/reference/grammar.po +++ b/reference/grammar.po @@ -293,15 +293,15 @@ msgid "" " | a[asdl_alias_seq*]=','.import_from_as_name+ { a }\n" "import_from_as_name[alias_ty]:\n" " | a=NAME b=['as' z=NAME { z }] { _PyAST_alias(a->v.Name.id,\n" -" (b) ? ((expr_ty) b)->v.Name." -"id : NULL,\n" +" (b) ? ((expr_ty) b)-" +">v.Name.id : NULL,\n" " EXTRA) }\n" "dotted_as_names[asdl_alias_seq*]:\n" " | a[asdl_alias_seq*]=','.dotted_as_name+ { a }\n" "dotted_as_name[alias_ty]:\n" " | a=dotted_name b=['as' z=NAME { z }] { _PyAST_alias(a->v.Name.id,\n" -" (b) ? ((expr_ty) b)->v." -"Name.id : NULL,\n" +" (b) ? ((expr_ty) b)-" +">v.Name.id : NULL,\n" " EXTRA) }\n" "dotted_name[expr_ty]:\n" " | a=dotted_name '.' b=NAME { _PyPegen_join_names_with_dot(p, a, b) }\n" @@ -395,10 +395,10 @@ msgid "" " | a[asdl_arg_seq*]=param_no_default+ '/' ',' { a }\n" " | a[asdl_arg_seq*]=param_no_default+ '/' &')' { a }\n" "slash_with_default[SlashWithDefault*]:\n" -" | a=param_no_default* b=param_with_default+ '/' " -"',' { _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }\n" -" | a=param_no_default* b=param_with_default+ '/' " -"&')' { _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }\n" +" | a=param_no_default* b=param_with_default+ '/' ',' " +"{ _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }\n" +" | a=param_no_default* b=param_with_default+ '/' &')' " +"{ _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }\n" "\n" "star_etc[StarEtc*]:\n" " | invalid_star_etc\n" @@ -436,22 +436,22 @@ msgid "" "param_no_default_star_annotation[arg_ty]:\n" " | a=param_star_annotation ',' tc=TYPE_COMMENT? " "{ _PyPegen_add_type_comment_to_arg(p, a, tc) }\n" -" | a=param_star_annotation tc=TYPE_COMMENT? " -"&')' { _PyPegen_add_type_comment_to_arg(p, a, tc) }\n" +" | a=param_star_annotation tc=TYPE_COMMENT? &')' " +"{ _PyPegen_add_type_comment_to_arg(p, a, tc) }\n" "param_with_default[NameDefaultPair*]:\n" " | a=param c=default ',' tc=TYPE_COMMENT? { _PyPegen_name_default_pair(p, " "a, c, tc) }\n" -" | a=param c=default tc=TYPE_COMMENT? " -"&')' { _PyPegen_name_default_pair(p, a, c, tc) }\n" +" | a=param c=default tc=TYPE_COMMENT? &')' " +"{ _PyPegen_name_default_pair(p, a, c, tc) }\n" "param_maybe_default[NameDefaultPair*]:\n" " | a=param c=default? ',' tc=TYPE_COMMENT? " "{ _PyPegen_name_default_pair(p, a, c, tc) }\n" -" | a=param c=default? tc=TYPE_COMMENT? " -"&')' { _PyPegen_name_default_pair(p, a, c, tc) }\n" +" | a=param c=default? tc=TYPE_COMMENT? &')' " +"{ _PyPegen_name_default_pair(p, a, c, tc) }\n" "param[arg_ty]: a=NAME b=annotation? { _PyAST_arg(a->v.Name.id, b, NULL, " "EXTRA) }\n" -"param_star_annotation[arg_ty]: a=NAME b=star_annotation { _PyAST_arg(a->v." -"Name.id, b, NULL, EXTRA) }\n" +"param_star_annotation[arg_ty]: a=NAME b=star_annotation { _PyAST_arg(a-" +">v.Name.id, b, NULL, EXTRA) }\n" "annotation[expr_ty]: ':' a=expression { a }\n" "star_annotation[expr_ty]: ':' a=star_expression { a }\n" "default[expr_ty]: '=' a=expression { a } | invalid_default\n" @@ -652,8 +652,8 @@ msgid "" " | imag=NUMBER { _PyPegen_ensure_imaginary(p, imag) }\n" "\n" "capture_pattern[pattern_ty]:\n" -" | target=pattern_capture_target { _PyAST_MatchAs(NULL, target->v.Name." -"id, EXTRA) }\n" +" | target=pattern_capture_target { _PyAST_MatchAs(NULL, target-" +">v.Name.id, EXTRA) }\n" "\n" "pattern_capture_target[expr_ty]:\n" " | !\"_\" name=NAME !('.' | '(' | '=') {\n" @@ -677,10 +677,10 @@ msgid "" " | '(' pattern=pattern ')' { pattern }\n" "\n" "sequence_pattern[pattern_ty]:\n" -" | '[' patterns=maybe_sequence_pattern? " -"']' { _PyAST_MatchSequence(patterns, EXTRA) }\n" -" | '(' patterns=open_sequence_pattern? " -"')' { _PyAST_MatchSequence(patterns, EXTRA) }\n" +" | '[' patterns=maybe_sequence_pattern? ']' " +"{ _PyAST_MatchSequence(patterns, EXTRA) }\n" +" | '(' patterns=open_sequence_pattern? ')' " +"{ _PyAST_MatchSequence(patterns, EXTRA) }\n" "\n" "open_sequence_pattern[asdl_seq*]:\n" " | pattern=maybe_star_pattern ',' patterns=maybe_sequence_pattern? {\n" @@ -778,8 +778,8 @@ msgid "" " CHECK_VERSION(asdl_type_param_seq *, 12, \"Type parameter lists " "are\", t) }\n" "\n" -"type_param_seq[asdl_type_param_seq*]: a[asdl_type_param_seq*]=','." -"type_param+ [','] { a }\n" +"type_param_seq[asdl_type_param_seq*]: " +"a[asdl_type_param_seq*]=','.type_param+ [','] { a }\n" "\n" "type_param[type_param_ty] (memo):\n" " | a=NAME b=[type_param_bound] { _PyAST_TypeVar(a->v.Name.id, b, " @@ -834,8 +834,8 @@ msgid "" " | '*' a=bitwise_or { _PyAST_Starred(a, Load, EXTRA) }\n" " | expression\n" "\n" -"star_named_expressions[asdl_expr_seq*]: a[asdl_expr_seq*]=','." -"star_named_expression+ [','] { a }\n" +"star_named_expressions[asdl_expr_seq*]: " +"a[asdl_expr_seq*]=','.star_named_expression+ [','] { a }\n" "\n" "star_named_expression[expr_ty]:\n" " | '*' a=bitwise_or { _PyAST_Starred(a, Load, EXTRA) }\n" @@ -1051,10 +1051,10 @@ msgid "" " | a[asdl_arg_seq*]=lambda_param_no_default+ '/' &':' { a }\n" "\n" "lambda_slash_with_default[SlashWithDefault*]:\n" -" | a=lambda_param_no_default* b=lambda_param_with_default+ '/' " -"',' { _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }\n" -" | a=lambda_param_no_default* b=lambda_param_with_default+ '/' " -"&':' { _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }\n" +" | a=lambda_param_no_default* b=lambda_param_with_default+ '/' ',' " +"{ _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }\n" +" | a=lambda_param_no_default* b=lambda_param_with_default+ '/' &':' " +"{ _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }\n" "\n" "lambda_star_etc[StarEtc*]:\n" " | invalid_lambda_star_etc\n" @@ -1093,8 +1093,8 @@ msgid "" " | t=FSTRING_MIDDLE { _PyPegen_constant_from_token(p, t) }\n" "fstring_replacement_field[expr_ty]:\n" " | '{' a=(yield_expr | star_expressions) debug_expr='='? " -"conversion=[fstring_conversion] format=[fstring_full_format_spec] " -"rbrace='}' {\n" +"conversion=[fstring_conversion] format=[fstring_full_format_spec] rbrace='}' " +"{\n" " _PyPegen_formatted_value(p, a, debug_expr, conversion, format, " "rbrace, EXTRA) }\n" " | invalid_replacement_field\n" @@ -1173,8 +1173,8 @@ msgid "" " | invalid_comprehension\n" "\n" "genexp[expr_ty]:\n" -" | '(' a=( assignment_expression | expression !':=') b=for_if_clauses " -"')' { _PyAST_GeneratorExp(a, b, EXTRA) }\n" +" | '(' a=( assignment_expression | expression !':=') b=for_if_clauses ')' " +"{ _PyAST_GeneratorExp(a, b, EXTRA) }\n" " | invalid_comprehension\n" "\n" "dictcomp[expr_ty]:\n" @@ -1214,15 +1214,15 @@ msgid "" "kwarg_or_starred[KeywordOrStarred*]:\n" " | invalid_kwarg\n" " | a=NAME '=' b=expression {\n" -" _PyPegen_keyword_or_starred(p, CHECK(keyword_ty, _PyAST_keyword(a->v." -"Name.id, b, EXTRA)), 1) }\n" +" _PyPegen_keyword_or_starred(p, CHECK(keyword_ty, _PyAST_keyword(a-" +">v.Name.id, b, EXTRA)), 1) }\n" " | a=starred_expression { _PyPegen_keyword_or_starred(p, a, 0) }\n" "\n" "kwarg_or_double_starred[KeywordOrStarred*]:\n" " | invalid_kwarg\n" " | a=NAME '=' b=expression {\n" -" _PyPegen_keyword_or_starred(p, CHECK(keyword_ty, _PyAST_keyword(a->v." -"Name.id, b, EXTRA)), 1) }\n" +" _PyPegen_keyword_or_starred(p, CHECK(keyword_ty, _PyAST_keyword(a-" +">v.Name.id, b, EXTRA)), 1) }\n" " | '**' a=expression { _PyPegen_keyword_or_starred(p, CHECK(keyword_ty, " "_PyAST_keyword(NULL, a, EXTRA)), 1) }\n" "\n" @@ -1254,8 +1254,8 @@ msgid "" " | target_with_star_atom\n" "\n" "target_with_star_atom[expr_ty] (memo):\n" -" | a=t_primary '.' b=NAME !t_lookahead { _PyAST_Attribute(a, b->v.Name." -"id, Store, EXTRA) }\n" +" | a=t_primary '.' b=NAME !t_lookahead { _PyAST_Attribute(a, b-" +">v.Name.id, Store, EXTRA) }\n" " | a=t_primary '[' b=slices ']' !t_lookahead { _PyAST_Subscript(a, b, " "Store, EXTRA) }\n" " | star_atom\n" @@ -1273,14 +1273,14 @@ msgid "" " | '(' a=single_target ')' { a }\n" "\n" "single_subscript_attribute_target[expr_ty]:\n" -" | a=t_primary '.' b=NAME !t_lookahead { _PyAST_Attribute(a, b->v.Name." -"id, Store, EXTRA) }\n" +" | a=t_primary '.' b=NAME !t_lookahead { _PyAST_Attribute(a, b-" +">v.Name.id, Store, EXTRA) }\n" " | a=t_primary '[' b=slices ']' !t_lookahead { _PyAST_Subscript(a, b, " "Store, EXTRA) }\n" "\n" "t_primary[expr_ty]:\n" -" | a=t_primary '.' b=NAME &t_lookahead { _PyAST_Attribute(a, b->v.Name." -"id, Load, EXTRA) }\n" +" | a=t_primary '.' b=NAME &t_lookahead { _PyAST_Attribute(a, b-" +">v.Name.id, Load, EXTRA) }\n" " | a=t_primary '[' b=slices ']' &t_lookahead { _PyAST_Subscript(a, b, " "Load, EXTRA) }\n" " | a=t_primary b=genexp &t_lookahead {\n" @@ -1301,8 +1301,8 @@ msgid "" "del_targets[asdl_expr_seq*]: a[asdl_expr_seq*]=','.del_target+ [','] { a }\n" "\n" "del_target[expr_ty] (memo):\n" -" | a=t_primary '.' b=NAME !t_lookahead { _PyAST_Attribute(a, b->v.Name." -"id, Del, EXTRA) }\n" +" | a=t_primary '.' b=NAME !t_lookahead { _PyAST_Attribute(a, b-" +">v.Name.id, Del, EXTRA) }\n" " | a=t_primary '[' b=slices ']' !t_lookahead { _PyAST_Subscript(a, b, " "Del, EXTRA) }\n" " | del_t_atom\n" @@ -1351,8 +1351,9 @@ msgid "" "# From here on, there are rules for invalid syntax with specialised error " "messages\n" "invalid_arguments:\n" -" | ((','.(starred_expression | ( assignment_expression | expression !':" -"=') !'=')+ ',' kwargs) | kwargs) a=',' ','.(starred_expression !'=')+ {\n" +" | ((','.(starred_expression | ( assignment_expression | " +"expression !':=') !'=')+ ',' kwargs) | kwargs) a=',' ','." +"(starred_expression !'=')+ {\n" " RAISE_SYNTAX_ERROR_STARTING_FROM(a, \"iterable argument unpacking " "follows keyword argument unpacking\") }\n" " | a=expression b=for_if_clauses ',' [args | expression for_if_clauses] " @@ -1448,9 +1449,9 @@ msgid "" "annotation\") }\n" " | (star_targets '=')* a=star_expressions '=' {\n" " RAISE_SYNTAX_ERROR_INVALID_TARGET(STAR_TARGETS, a) }\n" -" | (star_targets '=')* a=yield_expr " -"'=' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, \"assignment to yield expression " -"not possible\") }\n" +" | (star_targets '=')* a=yield_expr '=' " +"{ RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, \"assignment to yield expression not " +"possible\") }\n" " | a=star_expressions augassign (yield_expr | star_expressions) {\n" " RAISE_SYNTAX_ERROR_KNOWN_LOCATION(\n" " a,\n" @@ -1511,8 +1512,8 @@ msgid "" "comment\") }\n" " | '*' param a='=' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, \"var-" "positional argument cannot have default value\") }\n" -" | '*' (param_no_default | ',') param_maybe_default* " -"a='*' (param_no_default | ',') {\n" +" | '*' (param_no_default | ',') param_maybe_default* a='*' " +"(param_no_default | ',') {\n" " RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, \"* argument may appear only " "once\") }\n" "invalid_kwds:\n" @@ -1555,8 +1556,8 @@ msgid "" "must follow bare *\") }\n" " | '*' lambda_param a='=' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, \"var-" "positional argument cannot have default value\") }\n" -" | '*' (lambda_param_no_default | ',') lambda_param_maybe_default* " -"a='*' (lambda_param_no_default | ',') {\n" +" | '*' (lambda_param_no_default | ',') lambda_param_maybe_default* a='*' " +"(lambda_param_no_default | ',') {\n" " RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, \"* argument may appear only " "once\") }\n" "invalid_lambda_kwds:\n" diff --git a/reference/import.po b/reference/import.po index ed9c9f434..8dc12bd0d 100644 --- a/reference/import.po +++ b/reference/import.po @@ -25,8 +25,8 @@ 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." +"way. Functions such as :func:`importlib.import_module` and built-" +"in :func:`__import__` can also be used to invoke the import machinery." msgstr "" #: reference/import.rst:16 @@ -36,8 +36,8 @@ msgid "" "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 " +"name binding operation of the :keyword:`!import` statement. See " +"the :keyword:`!import` statement for the exact details of that name binding " "operation." msgstr "" @@ -52,10 +52,11 @@ msgstr "" #: reference/import.rst:31 msgid "" -"When an :keyword:`import` statement is executed, the standard builtin :func:" -"`__import__` function is called. Other mechanisms for invoking the import " -"system (such as :func:`importlib.import_module`) may choose to bypass :func:" -"`__import__` and use their own solutions to implement import semantics." +"When an :keyword:`import` statement is executed, the standard " +"builtin :func:`__import__` function is called. Other mechanisms for invoking " +"the import system (such as :func:`importlib.import_module`) may choose to " +"bypass :func:`__import__` and use their own solutions to implement import " +"semantics." msgstr "" #: reference/import.rst:36 @@ -70,8 +71,8 @@ msgstr "" #: reference/import.rst:43 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 " +"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 "" @@ -139,11 +140,11 @@ msgid "" "package>` 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." +"``__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 "" #: reference/import.rst:108 @@ -228,9 +229,9 @@ msgstr "" 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, a :exc:`ModuleNotFoundError` " -"is raised." +"first tries to import ``foo``, then ``foo.bar``, and finally " +"``foo.bar.baz``. If any of the intermediate imports fail, " +"a :exc:`ModuleNotFoundError` is raised." msgstr "" #: reference/import.rst:173 @@ -251,9 +252,9 @@ msgstr "" 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 a :exc:" -"`ModuleNotFoundError` is raised. If the module name is missing, Python will " -"continue searching for the module." +"process completes. However, if the value is ``None``, then " +"a :exc:`ModuleNotFoundError` is raised. If the module name is missing, " +"Python will continue searching for the module." msgstr "" #: reference/import.rst:191 @@ -262,17 +263,17 @@ msgid "" "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 a :exc:" -"`ModuleNotFoundError`." +"to ``None``, forcing the next import of the module to result in " +"a :exc:`ModuleNotFoundError`." msgstr "" #: reference/import.rst:198 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." +"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 "" #: reference/import.rst:208 @@ -283,12 +284,12 @@ msgstr "" 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." +"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 "" #: reference/import.rst:223 @@ -351,10 +352,10 @@ msgstr "" #: reference/import.rst:267 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." +"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 "" #: reference/import.rst:274 @@ -366,11 +367,11 @@ 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." +"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 "" #: reference/import.rst:289 @@ -403,9 +404,10 @@ msgid "" "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)``." +"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 "" #: reference/import.rst:316 @@ -428,20 +430,20 @@ msgid "" "The :meth:`~importlib.abc.MetaPathFinder.find_spec` method of meta path " "finders replaced :meth:`!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 :meth:`~importlib.abc.MetaPathFinder." -"find_spec`." +"if the finder does not " +"implement :meth:`~importlib.abc.MetaPathFinder.find_spec`." msgstr "" #: reference/import.rst:332 msgid "" -"Use of :meth:`!find_module` by the import system now raises :exc:" -"`ImportWarning`." +"Use of :meth:`!find_module` by the import system now " +"raises :exc:`ImportWarning`." msgstr "" #: reference/import.rst:336 msgid "" -":meth:`!find_module` has been removed. Use :meth:`~importlib.abc." -"MetaPathFinder.find_spec` instead." +":meth:`!find_module` has been removed. " +"Use :meth:`~importlib.abc.MetaPathFinder.find_spec` instead." msgstr "" #: reference/import.rst:342 @@ -493,8 +495,8 @@ msgstr "" #: reference/import.rst:379 msgid "" -"If there is an existing module object with the given name in :data:`sys." -"modules`, import will have already returned it." +"If there is an existing module object with the given name " +"in :data:`sys.modules`, import will have already returned it." msgstr "" #: reference/import.rst:382 @@ -509,10 +511,10 @@ msgstr "" #: reference/import.rst:388 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`." +"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 "" #: reference/import.rst:394 @@ -539,8 +541,8 @@ msgstr "" #: reference/import.rst:406 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." +"loaders. These were previously performed by " +"the :meth:`importlib.abc.Loader.load_module` method." msgstr "" #: reference/import.rst:412 @@ -568,9 +570,9 @@ msgstr "" #: reference/import.rst:425 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." +"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 "" #: reference/import.rst:429 @@ -596,9 +598,9 @@ msgstr "" #: reference/import.rst:443 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." +"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 "" #: reference/import.rst:448 @@ -618,11 +620,11 @@ msgstr "" #: reference/import.rst:457 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`." +"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 "" #: reference/import.rst:463 @@ -633,9 +635,9 @@ msgstr "" #: reference/import.rst:467 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." +"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 "" #: reference/import.rst:472 @@ -702,9 +704,9 @@ msgstr "" 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." +"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 "" #: reference/import.rst:519 @@ -732,8 +734,8 @@ msgstr "" msgid "" "The module's spec is exposed as :attr:`module.__spec__`. Setting :attr:`!" "__spec__` appropriately applies equally to :ref:`modules initialized during " -"interpreter startup `. The one exception is ``__main__``, where :" -"attr:`!__spec__` is :ref:`set to None in some cases `." +"interpreter startup `. The one exception is ``__main__``, " +"where :attr:`!__spec__` is :ref:`set to None in some cases `." msgstr "" #: reference/import.rst:538 @@ -748,19 +750,19 @@ msgstr "" #: reference/import.rst:548 msgid "" -"The :attr:`~module.__path__` attribute should be a (possibly empty) :term:" -"`sequence` of strings enumerating the locations where the package's " -"submodules will be found. By definition, if a module has a :attr:`!__path__` " -"attribute, it is a :term:`package`." +"The :attr:`~module.__path__` attribute should be a (possibly " +"empty) :term:`sequence` of strings enumerating the locations where the " +"package's submodules will be found. By definition, if a module has a :attr:`!" +"__path__` attribute, it is a :term:`package`." msgstr "" #: reference/import.rst:553 msgid "" "A package's :attr:`~module.__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, :attr:`!__path__` is typically much more constrained " -"than :data:`!sys.path`." +"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, :attr:`!__path__` is typically much more " +"constrained than :data:`!sys.path`." msgstr "" #: reference/import.rst:560 @@ -772,12 +774,13 @@ msgstr "" #: reference/import.rst:564 msgid "" -"A package's ``__init__.py`` file may set or alter the package's :attr:" -"`~module.__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 :attr:`!__path__` manipulation code; the import machinery " -"automatically sets :attr:`!__path__` correctly for the namespace package." +"A package's ``__init__.py`` file may set or alter the " +"package's :attr:`~module.__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 :attr:`!__path__` manipulation code; the import " +"machinery automatically sets :attr:`!__path__` correctly for the namespace " +"package." msgstr "" #: reference/import.rst:573 @@ -796,9 +799,9 @@ 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." +"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 "" #: reference/import.rst:586 @@ -853,14 +856,14 @@ msgstr "" msgid "" "Python also supports \"hash-based\" cache files, which store a hash of the " "source file's contents rather than its metadata. There are two variants of " -"hash-based ``.pyc`` files: checked and unchecked. For checked hash-based ``." -"pyc`` files, Python validates the cache file by hashing the source file and " -"comparing the resulting hash with the hash in the cache file. If a checked " -"hash-based cache file is found to be invalid, Python regenerates it and " -"writes a new checked hash-based cache file. For unchecked hash-based ``." -"pyc`` files, Python simply assumes the cache file is valid if it exists. " -"Hash-based ``.pyc`` files validation behavior may be overridden with the :" -"option:`--check-hash-based-pycs` flag." +"hash-based ``.pyc`` files: checked and unchecked. For checked hash-based " +"``.pyc`` files, Python validates the cache file by hashing the source file " +"and comparing the resulting hash with the hash in the cache file. If a " +"checked hash-based cache file is found to be invalid, Python regenerates it " +"and writes a new checked hash-based cache file. For unchecked hash-based " +"``.pyc`` files, Python simply assumes the cache file is valid if it exists. " +"Hash-based ``.pyc`` files validation behavior may be overridden with " +"the :option:`--check-hash-based-pycs` flag." msgstr "" #: reference/import.rst:628 @@ -876,10 +879,10 @@ msgstr "" #: reference/import.rst:639 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." +"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 "" #: reference/import.rst:645 @@ -894,10 +897,10 @@ 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." +"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 "" #: reference/import.rst:656 @@ -921,8 +924,8 @@ msgstr "" #: reference/import.rst:668 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, " +"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 " @@ -951,18 +954,19 @@ msgstr "" #: reference/import.rst:696 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`." +"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 "" #: reference/import.rst:701 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." +"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 "" #: reference/import.rst:706 @@ -971,10 +975,10 @@ msgid "" "modules and packages. It is initialized from the :envvar:`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 should be present on :data:`sys.path`; all " -"other data types are ignored." +"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 should be present on :data:`sys.path`; " +"all other data types are ignored." msgstr "" #: reference/import.rst:715 @@ -982,39 +986,39 @@ 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." +"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 "" #: reference/import.rst:724 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." +"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." msgstr "" #: reference/import.rst:737 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` " +"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 " @@ -1024,11 +1028,11 @@ msgstr "" #: reference/import.rst:751 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." +"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 "" #: reference/import.rst:758 @@ -1043,12 +1047,12 @@ msgstr "" 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." +"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 "" #: reference/import.rst:773 @@ -1072,9 +1076,9 @@ msgstr "" #: reference/import.rst:784 msgid "" -"To indicate to the import machinery that the spec represents a namespace :" -"term:`portion`, the path entry finder sets ``submodule_search_locations`` to " -"a list containing the portion." +"To indicate to the import machinery that the spec represents a " +"namespace :term:`portion`, the path entry finder sets " +"``submodule_search_locations`` to a list containing the portion." msgstr "" #: reference/import.rst:788 @@ -1152,10 +1156,10 @@ msgstr "" msgid "" "To selectively prevent the 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:`ModuleNotFoundError` 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." +"sufficient to raise :exc:`ModuleNotFoundError` 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 "" #: reference/import.rst:849 @@ -1225,9 +1229,9 @@ msgstr "" 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 " +"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 "" @@ -1252,9 +1256,9 @@ msgstr "" #: reference/import.rst:913 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:" +"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 "" #: reference/import.rst:917 @@ -1277,8 +1281,8 @@ msgstr "" 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__`." +"the :option:`-m` switch if valid module metadata is desired " +"in :mod:`__main__`." msgstr "" #: reference/import.rst:927 @@ -1352,10 +1356,11 @@ msgstr "" #: reference/import.rst:968 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." +"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 "" #: reference/import.rst:8 diff --git a/reference/index.po b/reference/index.po index 971b6627c..55f5e4f47 100644 --- a/reference/index.po +++ b/reference/index.po @@ -33,11 +33,11 @@ msgid "" "index` describes the interfaces available to C/C++ programmers in detail." msgstr "" "Bu başvuru kılavuzu, dilin söz dizimini ve \"çekirdek semantiğini\" " -"tanımlar. Kısa ve özdür ancak tam ve eksiksiz olmayı hedefler. Temel " -"olmayan gömülü nesne türlerinin ve gömülü işlevler ile modüllerin " +"tanımlar. Kısa ve özdür ancak tam ve eksiksiz olmayı hedefler. Temel olmayan " +"gömülü nesne türlerinin ve gömülü işlevler ile modüllerin " "semantiği :ref:`library-index` içerisinde açıklanmaktadır. Dile resmi " "olmayan bir giriş için :ref:`tutorial-index` bölümüne bakınız. C veya C++ " "programcıları için, iki ek kılavuz mevcuttur: :ref:`extending-index` bir " -"Python genişletme modülünün nasıl yazılacağına dair üst düzey genel " -"görünümü açıklar ve :ref:`c-api-index` C/C++ programcıları için mevcut olan " +"Python genişletme modülünün nasıl yazılacağına dair üst düzey genel görünümü " +"açıklar ve :ref:`c-api-index` C/C++ programcıları için mevcut olan " "arayüzleri ayrıntılı olarak tanımlar." diff --git a/reference/introduction.po b/reference/introduction.po index 228906c4c..744b4343d 100644 --- a/reference/introduction.po +++ b/reference/introduction.po @@ -95,8 +95,8 @@ 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 `_." +"libraries. More information can be found at `the Jython website `_." msgstr "" #: reference/introduction.rst:59 @@ -170,8 +170,8 @@ msgstr "" #: reference/introduction.rst:106 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 " +"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 " diff --git a/reference/lexical_analysis.po b/reference/lexical_analysis.po index c3be894f0..e0b96177c 100644 --- a/reference/lexical_analysis.po +++ b/reference/lexical_analysis.po @@ -30,9 +30,9 @@ msgstr "" #: 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." +"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 "" #: reference/lexical_analysis.rst:23 @@ -365,8 +365,8 @@ msgid "" "the underscore ``_`` and, except for the first character, the digits ``0`` " "through ``9``. Python 3.0 introduced 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." +"uses the version of the Unicode Character Database as included in " +"the :mod:`unicodedata` module." msgstr "" #: reference/lexical_analysis.rst:294 @@ -419,8 +419,8 @@ msgstr "" #: reference/lexical_analysis.rst:315 msgid "" -"*Other_ID_Start* - explicit list of characters in `PropList.txt `_ to support backwards " +"*Other_ID_Start* - explicit list of characters in `PropList.txt `_ to support backwards " "compatibility" msgstr "" @@ -517,16 +517,16 @@ msgstr "" #: reference/lexical_analysis.rst:392 msgid "" -"In a ``case`` pattern within a :keyword:`match` statement, ``_`` is a :ref:" -"`soft keyword ` that denotes a :ref:`wildcard `." +"In a ``case`` pattern within a :keyword:`match` statement, ``_`` is " +"a :ref:`soft keyword ` that denotes a :ref:`wildcard " +"`." msgstr "" #: reference/lexical_analysis.rst:396 msgid "" "Separately, the interactive interpreter makes the result of the last " -"evaluation available in the variable ``_``. (It is stored in the :mod:" -"`builtins` module, alongside built-in functions like ``print``.)" +"evaluation available in the variable ``_``. (It is stored in " +"the :mod:`builtins` module, alongside built-in functions like ``print``.)" msgstr "" #: reference/lexical_analysis.rst:401 @@ -594,8 +594,8 @@ msgid "" "whitespace is not allowed between the :token:`~python-grammar:stringprefix` " "or :token:`~python-grammar: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`." +"no encoding declaration is given in the source file; see " +"section :ref:`encodings`." msgstr "" #: reference/lexical_analysis.rst:482 @@ -637,8 +637,8 @@ msgstr "" #: reference/lexical_analysis.rst:514 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." +"simplify the maintenance of dual Python 2.x and 3.x codebases. " +"See :pep:`414` for more information." msgstr "" #: reference/lexical_analysis.rst:522 @@ -864,15 +864,15 @@ msgstr "" #: reference/lexical_analysis.rst:618 msgid "" -"Octal escapes with value larger than ``0o377`` produce a :exc:" -"`DeprecationWarning`." +"Octal escapes with value larger than ``0o377`` produce " +"a :exc:`DeprecationWarning`." msgstr "" #: reference/lexical_analysis.rst:622 msgid "" -"Octal escapes with value larger than ``0o377`` produce a :exc:" -"`SyntaxWarning`. In a future Python version they will be eventually a :exc:" -"`SyntaxError`." +"Octal escapes with value larger than ``0o377`` produce " +"a :exc:`SyntaxWarning`. In a future Python version they will be eventually " +"a :exc:`SyntaxError`." msgstr "" #: reference/lexical_analysis.rst:628 diff --git a/reference/simple_stmts.po b/reference/simple_stmts.po index 70127a27b..b0bf09b87 100644 --- a/reference/simple_stmts.po +++ b/reference/simple_stmts.po @@ -202,9 +202,9 @@ msgid "" "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)." +"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 "" #: reference/simple_stmts.rst:211 @@ -374,8 +374,8 @@ 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:`~object." -"__setitem__` or :meth:`~object.__setattr__` call." +"interpreter evaluates the target except for the " +"last :meth:`~object.__setitem__` or :meth:`~object.__setattr__` call." msgstr "" #: reference/simple_stmts.rst:361 @@ -494,8 +494,8 @@ msgstr "" 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." +"statement in the same code block. If the name is unbound, " +"a :exc:`NameError` exception will be raised." msgstr "" #: reference/simple_stmts.rst:471 @@ -545,16 +545,17 @@ msgstr "" 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." +"returned value (if any) is used as an argument to " +"construct :exc:`StopIteration` and becomes the :attr:`StopIteration.value` " +"attribute." msgstr "" #: reference/simple_stmts.rst:513 msgid "" "In an asynchronous generator function, an empty :keyword:`return` statement " -"indicates that the asynchronous generator is done and will cause :exc:" -"`StopAsyncIteration` to be raised. A non-empty :keyword:`!return` statement " -"is a syntax error in an asynchronous generator function." +"indicates that the asynchronous generator is done and will " +"cause :exc:`StopAsyncIteration` to be raised. A non-empty :keyword:`!" +"return` statement is a syntax error in an asynchronous generator function." msgstr "" #: reference/simple_stmts.rst:521 @@ -587,16 +588,16 @@ msgstr "" #: reference/simple_stmts.rst:546 msgid "" -"Yield expressions and statements are only used when defining a :term:" -"`generator` function, and are only used in the body of the generator " +"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 "" #: reference/simple_stmts.rst:551 msgid "" -"For full details of :keyword:`yield` semantics, refer to the :ref:" -"`yieldexpr` section." +"For full details of :keyword:`yield` semantics, refer to " +"the :ref:`yieldexpr` section." msgstr "" #: reference/simple_stmts.rst:557 @@ -614,15 +615,15 @@ msgstr "" #: reference/simple_stmts.rst:573 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." +"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 "" #: reference/simple_stmts.rst:578 msgid "" -"The :dfn:`type` of the exception is the exception instance's class, the :dfn:" -"`value` is the instance itself." +"The :dfn:`type` of the exception is the exception instance's class, " +"the :dfn:`value` is the instance itself." msgstr "" #: reference/simple_stmts.rst:583 @@ -675,8 +676,8 @@ msgstr "" #: reference/simple_stmts.rst:624 msgid "" "A similar mechanism works implicitly if a new exception is raised when an " -"exception is already being handled. An exception may be handled when an :" -"keyword:`except` or :keyword:`finally` clause, or a :keyword:`with` " +"exception is already being handled. An exception may be handled when " +"an :keyword:`except` or :keyword:`finally` clause, or a :keyword:`with` " "statement, is used. The previous exception is then attached as the new " "exception's :attr:`~BaseException.__context__` attribute:" msgstr "" @@ -722,9 +723,9 @@ msgstr "" #: reference/simple_stmts.rst:664 msgid "" -"Additional information on exceptions can be found in section :ref:" -"`exceptions`, and information about handling exceptions is in section :ref:" -"`try`." +"Additional information on exceptions can be found in " +"section :ref:`exceptions`, and information about handling exceptions is in " +"section :ref:`try`." msgstr "" #: reference/simple_stmts.rst:667 @@ -751,8 +752,8 @@ msgstr "" #: reference/simple_stmts.rst:693 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 " +":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 "" @@ -810,8 +811,8 @@ msgstr "" #: reference/simple_stmts.rst:766 msgid "" -"define a name or names in the local namespace for the scope where the :" -"keyword:`import` statement occurs." +"define a name or names in the local namespace for the scope where " +"the :keyword:`import` statement occurs." msgstr "" #: reference/simple_stmts.rst:769 @@ -840,8 +841,8 @@ msgstr "" #: reference/simple_stmts.rst:787 msgid "" -"If the module name is followed by :keyword:`!as`, then the name following :" -"keyword:`!as` is bound directly to the imported module." +"If the module name is followed by :keyword:`!as`, then the name " +"following :keyword:`!as` is bound directly to the imported module." msgstr "" #: reference/simple_stmts.rst:789 @@ -903,10 +904,10 @@ msgid "" "import foo # foo imported and bound locally\n" "import foo.bar.baz # foo, foo.bar, and foo.bar.baz imported, foo " "bound locally\n" -"import foo.bar.baz as fbb # foo, foo.bar, and foo.bar.baz imported, foo.bar." -"baz bound as fbb\n" -"from foo.bar import baz # foo, foo.bar, and foo.bar.baz imported, foo.bar." -"baz bound as baz\n" +"import foo.bar.baz as fbb # foo, foo.bar, and foo.bar.baz imported, " +"foo.bar.baz bound as fbb\n" +"from foo.bar import baz # foo, foo.bar, and foo.bar.baz imported, " +"foo.bar.baz bound as baz\n" "from foo import attr # foo imported and foo.attr bound as attr" msgstr "" @@ -963,8 +964,8 @@ msgstr "" #: reference/simple_stmts.rst:866 msgid "" "Raises an :ref:`auditing event ` ``import`` with arguments " -"``module``, ``filename``, ``sys.path``, ``sys.meta_path``, ``sys." -"path_hooks``." +"``module``, ``filename``, ``sys.path``, ``sys.meta_path``, " +"``sys.path_hooks``." msgstr "" #: reference/simple_stmts.rst:871 @@ -1070,11 +1071,11 @@ msgstr "" #: reference/simple_stmts.rst:936 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." +"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 "" #: reference/simple_stmts.rst:942 @@ -1136,8 +1137,8 @@ msgid "" "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." +"containing the function call. The same applies to the :func:`eval` " +"and :func:`compile` functions." msgstr "" #: reference/simple_stmts.rst:1004 @@ -1152,8 +1153,8 @@ msgid "" "identifiers to refer to names previously bound in nonlocal scopes. It allows " "encapsulated code to rebind such nonlocal identifiers. If a name is bound " "in more than one nonlocal scope, the nearest binding is used. If a name is " -"not bound in any nonlocal scope, or if there is no nonlocal scope, a :exc:" -"`SyntaxError` is raised." +"not bound in any nonlocal scope, or if there is no nonlocal scope, " +"a :exc:`SyntaxError` is raised." msgstr "" #: reference/simple_stmts.rst:1021 @@ -1174,8 +1175,8 @@ msgstr "" #: reference/simple_stmts.rst:1030 msgid "" "**Programmer's note:** :keyword:`nonlocal` is a directive to the parser and " -"applies only to code parsed along with it. See the note for the :keyword:" -"`global` statement." +"applies only to code parsed along with it. See the note for " +"the :keyword:`global` statement." msgstr "" #: reference/simple_stmts.rst:1038 @@ -1217,9 +1218,9 @@ msgstr "" msgid "" "The value of the type alias is evaluated in the annotation scope. It is not " "evaluated when the type alias is created, but only when the value is " -"accessed through the type alias's :attr:`!__value__` attribute (see :ref:" -"`lazy-evaluation`). This allows the type alias to refer to names that are " -"not yet defined." +"accessed through the type alias's :attr:`!__value__` attribute " +"(see :ref:`lazy-evaluation`). This allows the type alias to refer to names " +"that are not yet defined." msgstr "" #: reference/simple_stmts.rst:1067 diff --git a/reference/toplevel_components.po b/reference/toplevel_components.po index 4e9d22ece..4d38f4d8f 100644 --- a/reference/toplevel_components.po +++ b/reference/toplevel_components.po @@ -38,10 +38,10 @@ msgid "" "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." +"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 "" #: reference/toplevel_components.rst:36 diff --git a/sphinx.po b/sphinx.po index ee6a66418..a9ace3273 100644 --- a/sphinx.po +++ b/sphinx.po @@ -130,8 +130,8 @@ msgstr "" #: tools/templates/download.html:51 msgid "" -"Download (ca. " -"%(download_size)s MiB)" +"Download (ca. %" +"(download_size)s MiB)" msgstr "" #: tools/templates/download.html:56 @@ -518,8 +518,8 @@ msgstr "mevcut kararlı sürüm için olan Python dokümantasyonunu okumalısın #: tools/templates/layout.html:14 msgid "" -"This is a deploy preview created from a pull request.\n" +"This is a deploy preview created from a pull request.\n" " For authoritative documentation, see" msgstr "" "Bu, pull request'ten " diff --git a/tutorial/appendix.po b/tutorial/appendix.po index 15be55683..6f3a07285 100644 --- a/tutorial/appendix.po +++ b/tutorial/appendix.po @@ -35,8 +35,8 @@ 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 " +"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 status; this " "applies to internal inconsistencies and some cases of running out of " "memory. All error messages are written to the standard error stream; normal " @@ -45,27 +45,27 @@ msgstr "" "Bir hata oluştuğunda, yorumlayıcı bir hata iletisi ve yığın izlemesi " "yazdırır. Etkileşimli modda, daha sonra birincil istemi döndürür; bir " "dosyadan veri giriş gercekleştiğinde, yığın izlemeyi yazdırdıktan sonra " -"sıfır olmayan bir çıkış koduyla çıkar. (:keyword:`try` deyimindeki :keyword:" -"`except` yan tümcesi tarafından işlenen özel durumlar bu bağlamda hata " -"değildir.) Bazı hatalar koşulsuz olarak ölümcüldür ve sıfır olmayan bir " -"çıkış koduyla çıkışa neden olur; bu, iç tutarsızlıklar ve belleğin " -"tükendiğine ilişkin bazı durumlar için geçerlidir. Tüm hata iletileri " -"standart hata akışına yazılır; yürütülen komutlardan normal çıktı standart " -"çıktıya yazılır." +"sıfır olmayan bir çıkış koduyla çıkar. (:keyword:`try` " +"deyimindeki :keyword:`except` yan tümcesi tarafından işlenen özel durumlar " +"bu bağlamda hata değildir.) Bazı hatalar koşulsuz olarak ölümcüldür ve " +"sıfır olmayan bir çıkış koduyla çıkışa neden olur; bu, iç tutarsızlıklar ve " +"belleğin tükendiğine ilişkin bazı durumlar için geçerlidir. Tüm hata " +"iletileri standart hata akışına yazılır; yürütülen komutlardan normal çıktı " +"standart çıktıya yazılır." #: 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." +"the :exc:`KeyboardInterrupt` exception, which may be handled by " +"a :keyword:`try` statement." msgstr "" "Yarıda kesme karakterinin (genellikle :kbd:`Control-C` veya :kbd:`Delete`) " "birincil veya ikincil istemine yazılması girişi iptal eder ve birincil " "istemi döndürür. [#]_ Bir komut yürütülürken bir yarıda kesme karakteri " -"yazmak :exc:`KeyboardInterrupt` özel durumuna neden olur ve bu özel durum :" -"keyword:`try` deyimi tarafından işlenebilir." +"yazmak :exc:`KeyboardInterrupt` özel durumuna neden olur ve bu özel " +"durum :keyword:`try` deyimi tarafından işlenebilir." #: tutorial/appendix.rst:38 msgid "Executable Python Scripts" @@ -101,8 +101,8 @@ msgstr "" #: tutorial/appendix.rst:52 msgid "" -"The script can be given an executable mode, or permission, using the :" -"program:`chmod` command." +"The script can be given an executable mode, or permission, using " +"the :program:`chmod` command." msgstr "" "Komut dosyasına :program:`chmod` komutu kullanılarak yürütülebilir mod veya " "izin verilebilir." @@ -140,8 +140,8 @@ msgstr "" "Python'u etkileşimli olarak kullandığınızda, yorumlayıcı her başlatıldığında " "bazı standart komutların yürütülmesi genellikle kullanışlıdır. Bunu, " "başlatma komutlarınızı içeren bir dosyanın adına :envvar:`PYTHONSTARTUP` " -"adlı bir ortam değişkeni ayarlayarak yapabilirsiniz. Bu, Unix kabuklarının :" -"file:`.profile` özelliğine benzer." +"adlı bir ortam değişkeni ayarlayarak yapabilirsiniz. Bu, Unix " +"kabuklarının :file:`.profile` özelliğine benzer." #: tutorial/appendix.rst:77 msgid "" @@ -164,16 +164,16 @@ msgstr "" #: 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 " +"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 "" "Geçerli dizinden ek bir başlangıç dosyası okumak istiyorsanız, bunu genel " -"başlangıç dosyasında ``if os.path.isfile('.pythonrc.py'): exec(open('." -"pythonrc.py').read()`` gibi bir kod kullanarak programlayabilirsiniz. " -"Başlangıç dosyasını bir komut dosyasında kullanmak istiyorsanız, bunu komut " -"dosyasında açıkça yapmalısınız::" +"başlangıç dosyasında ``if os.path.isfile('.pythonrc.py'): " +"exec(open('.pythonrc.py').read()`` gibi bir kod kullanarak " +"programlayabilirsiniz. Başlangıç dosyasını bir komut dosyasında kullanmak " +"istiyorsanız, bunu komut dosyasında açıkça yapmalısınız::" #: tutorial/appendix.rst:91 msgid "" @@ -197,10 +197,10 @@ msgid "" "location of your user site-packages directory. Start Python and run this " "code::" msgstr "" -"Python özelleştirmenize izin vermek için iki kanca sağlar: :mod:" -"`sitecustomize` ve :mod:`usercustomize`. Nasıl çalıştığını görmek için önce " -"kullanıcı sitesi paketleri dizininizin konumunu bulmanız gerekir. Python'ı " -"başlatın ve şu kodu çalıştırın::" +"Python özelleştirmenize izin vermek için iki kanca " +"sağlar: :mod:`sitecustomize` ve :mod:`usercustomize`. Nasıl çalıştığını " +"görmek için önce kullanıcı sitesi paketleri dizininizin konumunu bulmanız " +"gerekir. Python'ı başlatın ve şu kodu çalıştırın::" #: tutorial/appendix.rst:108 msgid "" @@ -226,13 +226,13 @@ msgstr "" msgid "" ":index:`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 :index:`usercustomize`. See the documentation of the :mod:" -"`site` module for more details." +"imported before :index:`usercustomize`. See the documentation of " +"the :mod:`site` module for more details." msgstr "" ":mod:`sitecustomize` aynı şekilde çalışır, ancak genellikle genel site " -"paketleri dizinindeki bilgisayarın yöneticisi tarafından oluşturulur ve :mod:" -"`usercustomize` 'dan önce alınır. Daha fazla ayrıntı için :mod:`site` " -"modülünün belgelerine bakın." +"paketleri dizinindeki bilgisayarın yöneticisi tarafından oluşturulur " +"ve :mod:`usercustomize` 'dan önce alınır. Daha fazla ayrıntı " +"için :mod:`site` modülünün belgelerine bakın." #: tutorial/appendix.rst:123 msgid "Footnotes" diff --git a/tutorial/classes.po b/tutorial/classes.po index 378a3d755..5d5091565 100644 --- a/tutorial/classes.po +++ b/tutorial/classes.po @@ -208,10 +208,10 @@ msgid "" msgstr "" "Nitelikler salt okunur veya düzenlenebilir olabilir. İkinci durumda, " "niteliklere atama yapmak mümkündür. Modül nitelikleri düzenlenebilir: " -"``modname.the_answer = 42`` yazabilirsiniz. Düzenlenebilir nitelikler :" -"keyword:`del` ifadesiyle de silinebilir. Örneğin, ``del modname." -"the_answer`` ifadesi :attr:`the_answer` niteliğini ``modname`` tarafından " -"adlandırılan nesneden kaldırır." +"``modname.the_answer = 42`` yazabilirsiniz. Düzenlenebilir " +"nitelikler :keyword:`del` ifadesiyle de silinebilir. Örneğin, ``del " +"modname.the_answer`` ifadesi :attr:`the_answer` niteliğini ``modname`` " +"tarafından adlandırılan nesneden kaldırır." #: tutorial/classes.rst:96 msgid "" @@ -221,19 +221,19 @@ msgid "" "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`.)" +"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 "" "Ad alanları farklı anlarda oluşturulur ve farklı yaşam sürelerine sahiptir. " "Yerleşik adları içeren ad alanı, Python yorumlayıcısı başlatıldığında " "oluşturulur ve hiçbir zaman silinmez. Modül tanımı okunduğunda modül için " "genel ad alanı oluşturulur; normalde, modül ad alanları da yorumlayıcı çıkıp " "bitene kadar sürer. Bir komut dosyasından veya etkileşimli olarak okunan " -"yorumlayıcının en üst düzey çağrısı tarafından yürütülen ifadeler :mod:" -"`__main__` adlı bir modülün parçası olarak kabul edilir, bu nedenle kendi " -"genel ad alanlarına sahiptirler. (Yerleşik isimler aslında bir modülde de " -"yaşar; buna :mod:`builtins`.)" +"yorumlayıcının en üst düzey çağrısı tarafından yürütülen " +"ifadeler :mod:`__main__` adlı bir modülün parçası olarak kabul edilir, bu " +"nedenle kendi genel ad alanlarına sahiptirler. (Yerleşik isimler aslında " +"bir modülde de yaşar; buna :mod:`builtins`.)" #: tutorial/classes.rst:106 msgid "" @@ -295,11 +295,11 @@ msgstr "en dıştaki kapsam (en son aranan), yerleşik adlar içeren ad alanıd msgid "" "If a name is declared global, then all references and assignments go " "directly to the next-to-last 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)." +"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 "" "Bir ad global olarak bildirilirse, tüm başvurular ve atamalar doğrudan " "modülün genel adlarını içeren orta kapsama gider. En iç kapsamın dışında " @@ -340,35 +340,35 @@ msgstr "" #: tutorial/classes.rst:146 msgid "" -"A special quirk of Python is that -- if no :keyword:`global` or :keyword:" -"`nonlocal` 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." +"A special quirk of Python is that -- if no :keyword:`global` " +"or :keyword:`nonlocal` 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 "" "Python'un özel bir cilvesi, eğer :keyword:`global` veya :keyword:`nonlocal` " "deyimi geçerli değilse -- isimlere yapılan atamaların her zaman en içteki " "kapsama girmesidir. Atamalar verileri kopyalamaz --- adları nesnelere " "bağlarlar. Aynı şey silme için de geçerlidir: ``del x`` deyimi, ``x`` " "bağlamasını yerel kapsam tarafından başvurulan ad alanından kaldırır. " -"Aslında, yeni adlar tanıtan tüm işlemler yerel kapsamı kullanır: özellikle, :" -"keyword:`import` ifadeleri ve işlev tanımları modül veya işlev adını yerel " -"kapsamda bağlar." +"Aslında, yeni adlar tanıtan tüm işlemler yerel kapsamı kullanır: " +"özellikle, :keyword:`import` ifadeleri ve işlev tanımları modül veya işlev " +"adını yerel kapsamda bağlar." #: tutorial/classes.rst:154 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." +"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 "" ":keyword:`global` deyimi, belirli değişkenlerin genel kapsamda yaşadığını ve " -"orada geri alınması gerektiğini belirtmek için kullanılabilir; :keyword:" -"`nonlocal` deyimi, belirli değişkenlerin bir çevreleme kapsamında yaşadığını " -"ve orada geri alınması gerektiğini gösterir." +"orada geri alınması gerektiğini belirtmek için " +"kullanılabilir; :keyword:`nonlocal` deyimi, belirli değişkenlerin bir " +"çevreleme kapsamında yaşadığını ve orada geri alınması gerektiğini gösterir." #: tutorial/classes.rst:162 msgid "Scopes and Namespaces Example" @@ -380,9 +380,9 @@ msgid "" "namespaces, and how :keyword:`global` and :keyword:`nonlocal` affect " "variable binding::" msgstr "" -"Bu, farklı kapsamlara ve ad alanlarına başvurmayı ve :keyword:`global` ve :" -"keyword:`nonlocal` değişken bağlamasını nasıl etkileyeceğini gösteren bir " -"örnektir::" +"Bu, farklı kapsamlara ve ad alanlarına başvurmayı ve :keyword:`global` " +"ve :keyword:`nonlocal` değişken bağlamasını nasıl etkileyeceğini gösteren " +"bir örnektir::" #: tutorial/classes.rst:168 msgid "" @@ -436,8 +436,8 @@ msgstr "" #: tutorial/classes.rst:205 msgid "" -"You can also see that there was no previous binding for *spam* before the :" -"keyword:`global` assignment." +"You can also see that there was no previous binding for *spam* before " +"the :keyword:`global` assignment." msgstr "" "Ayrıca :keyword:`global` atamasından önce *spam* için herhangi bir bağlama " "olmadığını görebilirsiniz." @@ -605,8 +605,8 @@ msgstr "" 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:`~object.__init__`, like this::" +"specific initial state. Therefore a class may define a special method " +"named :meth:`~object.__init__`, like this::" msgstr "" "Örnekleme işlemi (\"sınıf nesnesi çağırma\") boş bir nesne oluşturur. Birçok " "sınıf, belirli bir başlangıç durumuna göre özelleştirilmiş örneklerle " @@ -754,8 +754,8 @@ msgstr "daima ``hello world`` yazdırmaya devam edecek." #: tutorial/classes.rst:372 #, fuzzy 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 " +"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 " @@ -1170,10 +1170,10 @@ msgstr "" 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.)" +"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 "" "Türetilmiş bir sınıfta geçersiz kılma yöntemi aslında yalnızca aynı adlı " "temel sınıf yöntemini değiştirmek yerine genişletmek isteyebilir. Temel " @@ -1193,8 +1193,8 @@ msgid "" "derived from :class:`int`." msgstr "" "Bir örneğin türünü denetlemek için :func:`isinstance` kullanın: " -"``isinstance(obj, int)`` yalnızca ``obj.__class__`` :class:`int` veya :class:" -"`int` sınıfından türetilmiş bir sınıfsa ``True`` olacaktır." +"``isinstance(obj, int)`` yalnızca ``obj.__class__`` :class:`int` " +"veya :class:`int` sınıfından türetilmiş bir sınıfsa ``True`` olacaktır." #: tutorial/classes.rst:618 msgid "" @@ -1243,10 +1243,10 @@ msgid "" msgstr "" "Basitçe, bir üst sınıftan devralınan nitelikleri aramayı, hiyerarşide " "çakışmanın olduğu aynı sınıfta iki kez arama yapmadan, derinlik öncelikli, " -"soldan sağa olarak düşünebilirsiniz. Bu nedenle, bir nitelik :class:" -"`DerivedClassName` içinde bulunamazsa, :class:`Base1` 'de, sonra " -"(özyinelemeli olarak) :class:`Base1` temel sınıflarında aranır ve orada " -"bulunamazsa :class:`Base2` vb." +"soldan sağa olarak düşünebilirsiniz. Bu nedenle, bir " +"nitelik :class:`DerivedClassName` içinde bulunamazsa, :class:`Base1` 'de, " +"sonra (özyinelemeli olarak) :class:`Base1` temel sınıflarında aranır ve " +"orada bulunamazsa :class:`Base2` vb." #: tutorial/classes.rst:647 msgid "" @@ -1256,11 +1256,11 @@ msgid "" "method and is more powerful than the super call found in single-inheritance " "languages." msgstr "" -"Aslında, durum bundan biraz daha karmaşıktır: yöntem çözümleme sırası, :func:" -"`super` için işbirliği çağrılarını desteklemek için dinamik olarak değişir. " -"Bu yaklaşım, diğer bazı çoklu kalıtım dillerinde sonraki çağrı yöntemi " -"olarak bilinir ve tekli kalıtım dillerinde bulunan süper çağrıdan daha " -"güçlüdür." +"Aslında, durum bundan biraz daha karmaşıktır: yöntem çözümleme " +"sırası, :func:`super` için işbirliği çağrılarını desteklemek için dinamik " +"olarak değişir. Bu yaklaşım, diğer bazı çoklu kalıtım dillerinde sonraki " +"çağrı yöntemi olarak bilinir ve tekli kalıtım dillerinde bulunan süper " +"çağrıdan daha güçlüdür." #: tutorial/classes.rst:653 #, fuzzy @@ -1459,10 +1459,10 @@ msgstr "" #: tutorial/classes.rst:772 #, fuzzy msgid "" -":ref:`Instance method objects ` have attributes, too: :" -"attr:`m.__self__ ` is the instance object with the method :" -"meth:`!m`, and :attr:`m.__func__ ` is the :ref:`function " -"object ` corresponding to the method." +":ref:`Instance method objects ` have attributes, " +"too: :attr:`m.__self__ ` is the instance object with the " +"method :meth:`!m`, and :attr:`m.__func__ ` is " +"the :ref:`function object ` corresponding to the method." msgstr "" "Örnek yöntem nesnelerinin de nitelikleri vardır: ``m.__self__`` yöntemi olan " "örnek nesnedir :meth:`m`, ve ``m.__func__`` yönteme karşılık gelen fonksiyon " @@ -1497,24 +1497,25 @@ msgstr "" #: tutorial/classes.rst:798 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::" +"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 "" "Bu erişim tarzı açık, özlü ve kullanışlıdır. Yineleyicilerin kullanımı " "Python'u istila eder ve birleştirir. Perde arkasında :keyword:`for` deyimi " "kapsayıcı nesne üzerinde :func:`iter` öğesini çağırır. Fonksiyon, " "kapsayıcıdaki öğelere teker teker erişen :meth:`~iterator.__next__` metodunu " -"tanımlayan bir yineleyici nesnesi döndürür. Başka öğe olmadığında, :meth:" -"`~iterator.__next__`, :keyword:`!for` döngüsünün sonlandırılacağını bildiren " -"bir :exc:`StopIteration` hatası oluşturur. :func:`next` yerleşik " -"fonksiyonunu kullanarak :meth:`~iterator.__next__` yöntemini " -"çağırabilirsiniz; Bu örnek, her şeyin nasıl çalıştığını gösterir::" +"tanımlayan bir yineleyici nesnesi döndürür. Başka öğe " +"olmadığında, :meth:`~iterator.__next__`, :keyword:`!for` döngüsünün " +"sonlandırılacağını bildiren bir :exc:`StopIteration` hatası " +"oluşturur. :func:`next` yerleşik fonksiyonunu " +"kullanarak :meth:`~iterator.__next__` yöntemini çağırabilirsiniz; Bu örnek, " +"her şeyin nasıl çalıştığını gösterir::" #: tutorial/classes.rst:807 msgid "" @@ -1546,8 +1547,9 @@ msgid "" msgstr "" "Yineleme protokolünün arkasındaki mekaniği gördükten sonra, sınıflarınıza " "yineleme davranışı eklemek kolaydır. :meth:`~iterator.__next__` metodu ile " -"bir nesne döndüren :meth:`__iter__` metodunu tanımlayın. Sınıf :meth:" -"`__next__` tanımlarsa, :meth:`__iter__` sadece ``self`` döndürebilir::" +"bir nesne döndüren :meth:`__iter__` metodunu tanımlayın. " +"Sınıf :meth:`__next__` tanımlarsa, :meth:`__iter__` sadece ``self`` " +"döndürebilir::" #: tutorial/classes.rst:828 msgid "" @@ -1588,17 +1590,17 @@ msgstr "Üreteçler" #: tutorial/classes.rst:862 msgid "" ":term:`Generators ` 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::" +"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 "" ":term:`Üreteçler ` yineleyiciler oluşturmak için basit ve güçlü " "bir araçtır. Normal fonksiyonlar gibi yazılırlar, ancak veri döndürmek " -"istediklerinde :keyword:`yield` deyimini kullanırlar. Üzerinde her :func:" -"`next` çağrıldığı zaman, üreteç kaldığı yerden devam eder (tüm veri " -"değerlerini ve hangi deyimin en son yürütüldüğını hatırlar). Bu örnek, " +"istediklerinde :keyword:`yield` deyimini kullanırlar. Üzerinde " +"her :func:`next` çağrıldığı zaman, üreteç kaldığı yerden devam eder (tüm " +"veri değerlerini ve hangi deyimin en son yürütüldüğını hatırlar). Bu örnek, " "üreteçlerin oluşturulmasının ne kadar da kolay olabileceğini gösterir::" #: tutorial/classes.rst:869 @@ -1624,8 +1626,8 @@ msgstr "" 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:`~iterator.__iter__` and :meth:`~generator." -"__next__` methods are created automatically." +"compact is that the :meth:`~iterator.__iter__` " +"and :meth:`~generator.__next__` methods are created automatically." msgstr "" "Üreteçlerle yapılabilecek her şey, önceki bölümde açıklandığı gibi sınıf " "tabanlı yineleyicilerle de yapılabilir. Üreteçleri bu kadar kompakt yapan " @@ -1636,8 +1638,8 @@ msgstr "" 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``." +"and much more clear than an approach using instance variables like " +"``self.index`` and ``self.data``." msgstr "" "Başka bir önemli özellik, yerel değişkenlerin ve yürütme durumunun çağrılar " "arasında otomatik olarak kaydedilmesidir. Bu, fonksiyonun yazılmasını " diff --git a/tutorial/controlflow.po b/tutorial/controlflow.po index 24eff6ffa..48a6bd637 100644 --- a/tutorial/controlflow.po +++ b/tutorial/controlflow.po @@ -62,9 +62,9 @@ msgstr "" 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." +"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 "" "Sıfır veya daha fazla :keyword:`elif` bölümü olabilir ve :keyword:`else` " "bölümü isteğe bağlıdır. ':keyword:`!elif`' anahtar sözcüğü 'else if' " @@ -91,10 +91,10 @@ 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):" +"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 "" "Python'daki :keyword:`for` deyimi, C veya Pascal'da alışkın olduğunuzdan " "biraz farklıdır. Her zaman sayıların aritmetik ilerlemesi üzerinde yineleme " @@ -150,11 +150,13 @@ msgstr ":func:`range` Fonksiyonu" #: tutorial/controlflow.rst:96 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::" +"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 "" -"Bir sayı dizisi üzerinde yineleme yapmanız gerekiyorsa, yerleşik :func:" -"`range` fonksiyonu kullanışlı olur. Aritmetik ilerlemeler üretir::" +"Bir sayı dizisi üzerinde yineleme yapmanız gerekiyorsa, " +"yerleşik :func:`range` fonksiyonu kullanışlı olur. Aritmetik ilerlemeler " +"üretir::" #: tutorial/controlflow.rst:99 msgid "" @@ -198,8 +200,8 @@ msgid "" "To iterate over the indices of a sequence, you can combine :func:`range` " "and :func:`len` as follows::" msgstr "" -"Bir dizinin indisleri üzerinde yineleme yapmak için :func:`range` ve :func:" -"`len` öğelerini aşağıdaki gibi birleştirebilirsiniz::" +"Bir dizinin indisleri üzerinde yineleme yapmak için :func:`range` " +"ve :func:`len` öğelerini aşağıdaki gibi birleştirebilirsiniz::" #: tutorial/controlflow.rst:125 msgid "" @@ -248,9 +250,9 @@ msgstr "" msgid "" "We say such an object is :term:`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 a construct, while an example of a function " -"that takes an iterable is :func:`sum`::" +"successive items until the supply is exhausted. We have seen that " +"the :keyword:`for` statement is such a construct, while an example of a " +"function that takes an iterable is :func:`sum`::" msgstr "" "Böyle bir nesnenin :term:`iterable` olduğunu, yani arz tükenene kadar " "ardışık öğeler elde edebilecekleri bir şey bekleyen fonksiyonlar ve yapılar " @@ -271,8 +273,8 @@ msgid "" "about :func:`list`." msgstr "" "Daha sonra yinelenebilirleri döndüren ve argüman olarak yinelenebilirleri " -"alan daha fazla fonksiyon göreceğiz. :ref:`tut-structures` bölümünde, :func:" -"`list` hakkında daha ayrıntılı olarak tartışacağız." +"alan daha fazla fonksiyon göreceğiz. :ref:`tut-structures` " +"bölümünde, :func:`list` hakkında daha ayrıntılı olarak tartışacağız." #: tutorial/controlflow.rst:164 #, fuzzy @@ -284,11 +286,11 @@ msgstr "" #: tutorial/controlflow.rst:166 #, fuzzy msgid "" -"The :keyword:`break` statement breaks out of the innermost enclosing :" -"keyword:`for` or :keyword:`while` loop::" +"The :keyword:`break` statement breaks out of the innermost " +"enclosing :keyword:`for` or :keyword:`while` loop::" msgstr "" -"C'de olduğu gibi :keyword:`break` deyimi, en içteki :keyword:`for` veya :" -"keyword:`while` döngüsünü keser." +"C'de olduğu gibi :keyword:`break` deyimi, en içteki :keyword:`for` " +"veya :keyword:`while` döngüsünü keser." #: tutorial/controlflow.rst:169 msgid "" @@ -638,8 +640,8 @@ msgid "" "A recommended way to read patterns is to look at them as an extended form of " "what you would put on the left of an assignment, to understand which " "variables would be set to what. Only the standalone names (like ``var`` " -"above) are assigned to by a match statement. Dotted names (like ``foo." -"bar``), attribute names (the ``x=`` and ``y=`` above) or class names " +"above) are assigned to by a match statement. Dotted names (like " +"``foo.bar``), attribute names (the ``x=`` and ``y=`` above) or class names " "(recognized by the \"(...)\" next to them like ``Point`` above) are never " "assigned to." msgstr "" @@ -648,8 +650,8 @@ msgstr "" "genişletilmiş bir biçimi olarak bakmaktır. Yalnızca bağımsız isimler " "(yukarıdaki ``var`` gibi) bir eşleştirme deyimi tarafından atanır. Noktalı " "isimlere (``foo.bar`` gibi), nitelik isimlerine (yukarıdaki ``x=`` ve ``y=`` " -"gibi) veya sınıf isimlerine (yukarıdaki ``Point`` gibi yanlarındaki " -"\"(...)\" ile tanınan) asla atama yapılmaz." +"gibi) veya sınıf isimlerine (yukarıdaki ``Point`` gibi yanlarındaki \"(...)" +"\" ile tanınan) asla atama yapılmaz." #: tutorial/controlflow.rst:378 #, fuzzy @@ -792,8 +794,8 @@ msgstr "" #: tutorial/controlflow.rst:454 msgid "" -"For a more detailed explanation and additional examples, you can look into :" -"pep:`636` which is written in a tutorial format." +"For a more detailed explanation and additional examples, you can look " +"into :pep:`636` which is written in a tutorial format." msgstr "" "Daha ayrıntılı bir açıklama ve ek örnekler için, öğretici bir formatta " "yazılmış olan :pep:`636` sayfasına bakabilirsiniz." @@ -840,21 +842,21 @@ msgstr "" #: tutorial/controlflow.rst:487 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." +"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 "" "Fonksiyon gövdesinin ilk ifadesi isteğe bağlı olarak bir string literal " -"olabilir; bu string literal fonksiyonun dokümantasyon stringi veya :dfn:" -"`docstring` 'dir. (Docstringler hakkında daha fazla bilgi :ref:`tut-" -"docstrings` bölümünde bulunabilir.) Otomatik olarak çevrimiçi veya basılı " -"dokümantasyon üretmek veya kullanıcının etkileşimli olarak kodda gezinmesini " -"sağlamak için docstringleri kullanan araçlar vardır; yazdığınız koda " -"docstringler eklemek iyi bir uygulamadır, bu yüzden bunu alışkanlık haline " -"getirin." +"olabilir; bu string literal fonksiyonun dokümantasyon stringi " +"veya :dfn:`docstring` 'dir. (Docstringler hakkında daha fazla " +"bilgi :ref:`tut-docstrings` bölümünde bulunabilir.) Otomatik olarak " +"çevrimiçi veya basılı dokümantasyon üretmek veya kullanıcının etkileşimli " +"olarak kodda gezinmesini sağlamak için docstringleri kullanan araçlar " +"vardır; yazdığınız koda docstringler eklemek iyi bir uygulamadır, bu yüzden " +"bunu alışkanlık haline getirin." #: tutorial/controlflow.rst:494 msgid "" @@ -876,9 +878,9 @@ msgstr "" "çevreleyen fonksiyonların yerel sembol tablolarına, daha sonra global sembol " "tablosuna ve son olarak da yerleşik isimler tablosuna bakar. Bu nedenle, " "global değişkenlere ve çevreleyen fonksiyonların değişkenlerine bir " -"fonksiyon içinde doğrudan değer atanamaz (global değişkenler için bir :" -"keyword:`global` deyiminde veya çevreleyen fonksiyonların değişkenleri için " -"bir :keyword:`nonlocal` deyiminde isimlendirilmedikçe), ancak bunlara " +"fonksiyon içinde doğrudan değer atanamaz (global değişkenler için " +"bir :keyword:`global` deyiminde veya çevreleyen fonksiyonların değişkenleri " +"için bir :keyword:`nonlocal` deyiminde isimlendirilmedikçe), ancak bunlara " "referans verilebilir." #: tutorial/controlflow.rst:505 @@ -926,16 +928,16 @@ msgid "" "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`::" +"the only value written. You can see it if you really want to " +"using :func:`print`::" msgstr "" "Diğer dillerden geliyorsanız, ``fib`` 'in bir fonksiyon değil, değer " -"döndürmediği için bir prosedür olduğuna itiraz edebilirsiniz. Aslında, :" -"keyword:`return` ifadesi olmayan fonksiyonlar bile, oldukça sıkıcı olsa da, " -"bir değer döndürürler. Bu değer ``None`` olarak adlandırılır (yerleşik bir " -"isimdir). Normalde ``None`` değerinin yazılması, yazılan tek değer olacaksa " -"yorumlayıcı tarafından bastırılır. Eğer gerçekten istiyorsanız :func:`print` " -"kullanarak görebilirsiniz::" +"döndürmediği için bir prosedür olduğuna itiraz edebilirsiniz. " +"Aslında, :keyword:`return` ifadesi olmayan fonksiyonlar bile, oldukça sıkıcı " +"olsa da, bir değer döndürürler. Bu değer ``None`` olarak adlandırılır " +"(yerleşik bir isimdir). Normalde ``None`` değerinin yazılması, yazılan tek " +"değer olacaksa yorumlayıcı tarafından bastırılır. Eğer gerçekten " +"istiyorsanız :func:`print` kullanarak görebilirsiniz::" #: tutorial/controlflow.rst:530 msgid "" @@ -975,9 +977,9 @@ msgstr "" #: tutorial/controlflow.rst:552 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``." +"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 "" "Bir :keyword:`return` deyimi bir fonksiyondan bir değerle döner. :keyword:`!" "return` deyimi bir ifade argümanı olmadan ``None`` döndürür. Bir fonksiyonun " @@ -992,8 +994,8 @@ msgid "" "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 " +"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." @@ -1260,11 +1262,12 @@ msgid "" msgstr "" "``**name`` biçiminde bir son biçimsel parametre mevcut olduğunda, biçimsel " "parametreye karşılık gelenler dışındaki tüm anahtar kelime argümanlarını " -"içeren bir sözlük alır (bkz. :ref:`typesmapping`). Bu, biçimsel parametre :" -"ref:`tuple ` listesinin ötesindeki konumsal argümanları içeren " -"bir ``*name`` biçimindeki bir biçimsel parametre ile birleştirilebilir (bir " -"sonraki alt bölümde açıklanmıştır). (``*name``, ``**name`` 'den önce " -"gelmelidir.) Örneğin, aşağıdaki gibi bir fonksiyon tanımlarsak::" +"içeren bir sözlük alır (bkz. :ref:`typesmapping`). Bu, biçimsel " +"parametre :ref:`tuple ` listesinin ötesindeki konumsal " +"argümanları içeren bir ``*name`` biçimindeki bir biçimsel parametre ile " +"birleştirilebilir (bir sonraki alt bölümde açıklanmıştır). (``*name``, " +"``**name`` 'den önce gelmelidir.) Örneğin, aşağıdaki gibi bir fonksiyon " +"tanımlarsak::" #: tutorial/controlflow.rst:708 msgid "" @@ -1902,15 +1905,15 @@ msgid "" "denoting the end of the :keyword:`def` statement. The following example has " "a required argument, an optional argument, and the return value annotated::" msgstr "" -":term:`İşaretlemeler `, fonksiyonun :attr:" -"`__annotations__` özelliğinde bir sözlük olarak saklanır ve fonksiyonun " -"diğer bölümleri üzerinde hiçbir etkisi yoktur. Parametre ek açıklamaları, " -"parametre adından sonra iki nokta üst üste işareti ve ardından ek " -"açıklamanın değerine göre değerlendirilen bir ifade ile tanımlanır. Dönüş " -"ek açıklamaları, parametre listesi ile :keyword:`def` ifadesinin sonunu " -"belirten iki nokta arasında bir ``->`` ifadesi ve ardından bir ifade ile " -"tanımlanır. Aşağıdaki örnekte bir gerekli argüman, bir isteğe bağlı argüman " -"ve dönüş değeri ek açıklamalıdır::" +":term:`İşaretlemeler `, " +"fonksiyonun :attr:`__annotations__` özelliğinde bir sözlük olarak saklanır " +"ve fonksiyonun diğer bölümleri üzerinde hiçbir etkisi yoktur. Parametre ek " +"açıklamaları, parametre adından sonra iki nokta üst üste işareti ve ardından " +"ek açıklamanın değerine göre değerlendirilen bir ifade ile tanımlanır. " +"Dönüş ek açıklamaları, parametre listesi ile :keyword:`def` ifadesinin " +"sonunu belirten iki nokta arasında bir ``->`` ifadesi ve ardından bir ifade " +"ile tanımlanır. Aşağıdaki örnekte bir gerekli argüman, bir isteğe bağlı " +"argüman ve dönüş değeri ek açıklamalıdır::" #: tutorial/controlflow.rst:1084 msgid "" @@ -2130,10 +2133,11 @@ msgstr "" #~ msgid "" #~ "Loop statements may have an :keyword:`!else` clause; it is executed when " -#~ "the loop terminates through exhaustion of the iterable (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::" +#~ "the loop terminates through exhaustion of the iterable " +#~ "(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 "" #~ "Döngü deyimleri bir :keyword:`!else` cümlesine sahip olabilir; bu cümle " #~ "döngü yinelenebilirin tükenmesiyle sonlandığında (:keyword:`for` ile) " diff --git a/tutorial/datastructures.po b/tutorial/datastructures.po index dfe5d3722..d43cf6649 100644 --- a/tutorial/datastructures.po +++ b/tutorial/datastructures.po @@ -62,16 +62,16 @@ msgid "" "of the list, and ``a.insert(len(a), x)`` is equivalent to ``a.append(x)``." msgstr "" "Verilen pozisyona bir öğe ekleyin. İlk argüman, daha önce ekleyeceğiniz " -"öğenin indeksidir, bu nedenle ``a.insert(0, x)`` listenin önüne ekler ve ``a." -"insert(len(a), x)`` komutu ``a.append(x)`` komutu ile eş değerdir." +"öğenin indeksidir, bu nedenle ``a.insert(0, x)`` listenin önüne ekler ve " +"``a.insert(len(a), x)`` komutu ``a.append(x)`` komutu ile eş değerdir." #: tutorial/datastructures.rst:43 msgid "" "Remove the first item from the list whose value is equal to *x*. It raises " "a :exc:`ValueError` if there is no such item." msgstr "" -"Değeri *x*'e eşit olan ilk öğeyi listeden kaldırır. Böyle bir öğe yoksa :" -"exc:`ValueError` hatası ortaya çıkar." +"Değeri *x*'e eşit olan ilk öğeyi listeden kaldırır. Böyle bir öğe " +"yoksa :exc:`ValueError` hatası ortaya çıkar." #: tutorial/datastructures.rst:50 #, fuzzy @@ -336,10 +336,10 @@ msgid "" "which follow it. For example, this listcomp combines the elements of two " "lists if they are not equal::" msgstr "" -"Bir liste kavrayışı, bir ifade içeren parantezlerden ve ardından bir :" -"keyword:`!for` cümlesinden, ardından sıfır veya daha fazla :keyword:`!for` " -"veya :keyword:`!if` cümlesinden oluşur. Sonuç, ifadenin kendisini takip " -"eden :keyword:`!for` ve :keyword:`!if` cümleleri bağlamında " +"Bir liste kavrayışı, bir ifade içeren parantezlerden ve ardından " +"bir :keyword:`!for` cümlesinden, ardından sıfır veya daha fazla :keyword:`!" +"for` veya :keyword:`!if` cümlesinden oluşur. Sonuç, ifadenin kendisini " +"takip eden :keyword:`!for` ve :keyword:`!if` cümleleri bağlamında " "değerlendirilmesiyle elde edilen yeni bir liste olacaktır. Örneğin, " "listcomp, eşit değillerse iki listenin öğelerini birleştirir::" @@ -471,8 +471,9 @@ msgid "" "in the context of the :keyword:`for` that follows it, so this example is " "equivalent to::" msgstr "" -"Önceki bölümde gördüğümüz gibi, iç liste kavrayışı, onu takip eden :keyword:" -"`for` bağlamında değerlendirilir, bu nedenle bu örnek şuna eş değerdir::" +"Önceki bölümde gördüğümüz gibi, iç liste kavrayışı, onu takip " +"eden :keyword:`for` bağlamında değerlendirilir, bu nedenle bu örnek şuna eş " +"değerdir::" #: tutorial/datastructures.rst:309 msgid "" @@ -532,10 +533,11 @@ msgstr ":keyword:`!del` ifadesi" #, fuzzy 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:`~list." -"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::" +"value: the :keyword:`del` statement. This differs from " +"the :meth:`~list.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 "" "Değer yerine indeksi verilen bir öğeyi listeden kaldırmanın bir yolu " "vardır: :keyword:`del` ifadesi. Bu, bir değer döndüren :meth:`pop` " @@ -641,17 +643,17 @@ msgid "" "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." +"the case of :func:`namedtuples `). Lists " +"are :term:`mutable`, and their elements are usually homogeneous and are " +"accessed by iterating over the list." msgstr "" "Veri grupları listelere benzer görünse de, genellikle farklı durumlarda ve " "farklı amaçlar için kullanılırlar. Veri grupları :term:`immutable` 'dır ve " "genellikle paket açma (bu bölümün ilerleyen kısımlarına bakınız) veya " "indeksleme (hatta :func:`namedtuples ` durumunda " -"öznitelik ile) yoluyla erişilen heterojen bir dizi eleman içerir. Listeler :" -"term:`mutable` 'dır ve elemanları genellikle homojendir ve listenin üzerinde " -"yinelenerek erişilir." +"öznitelik ile) yoluyla erişilen heterojen bir dizi eleman içerir. " +"Listeler :term:`mutable` 'dır ve elemanları genellikle homojendir ve " +"listenin üzerinde yinelenerek erişilir." #: tutorial/datastructures.rst:415 msgid "" @@ -790,16 +792,16 @@ msgstr "Sözlükler" #: tutorial/datastructures.rst:495 #, fuzzy 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:" -"`~list.append` and :meth:`~list.extend`." +"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:`~list.append` and :meth:`~list.extend`." msgstr "" "Python'da yerleşik olarak bulunan bir başka kullanışlı veri türü de " "*sözlüktür* (bkz :ref:`typesmapping`). Sözlükler bazen diğer dillerde " @@ -831,16 +833,16 @@ msgstr "" #: tutorial/datastructures.rst:512 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 " +"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 "" "Bir sözlük üzerindeki ana işlemler, bir değeri bir anahtarla depolamak ve " -"anahtarı verilen değeri geri çıkarmaktır. Ayrıca ``del`` ile bir anahtar:" -"değer çiftini silmek de mümkündür. Zaten bir değeri kullanımda olan bir " -"anahtar kullanarak saklarsanız, bu anahtarla ilişkili eski değer unutulur. " -"Var olmayan bir anahtar kullanarak değer çıkarmak bir hatadır." +"anahtarı verilen değeri geri çıkarmaktır. Ayrıca ``del`` ile bir " +"anahtar:değer çiftini silmek de mümkündür. Zaten bir değeri kullanımda olan " +"bir anahtar kullanarak saklarsanız, bu anahtarla ilişkili eski değer " +"unutulur. Var olmayan bir anahtar kullanarak değer çıkarmak bir hatadır." #: tutorial/datastructures.rst:518 msgid "" @@ -852,8 +854,8 @@ msgstr "" "Bir sözlük üzerinde ``list(d)`` işlemini gerçekleştirmek, sözlükte " "kullanılan tüm anahtarların bir listesini eklenme sırasına göre döndürür " "(başka bir düzenle sıralanmasını istiyorsanız, bunun yerine ``sorted(d)`` " -"kullanın). Tek bir anahtarın sözlükte olup olmadığını kontrol etmek için :" -"keyword:`in` anahtar sözcüğünü kullanın." +"kullanın). Tek bir anahtarın sözlükte olup olmadığını kontrol etmek " +"için :keyword:`in` anahtar sözcüğünü kullanın." #: tutorial/datastructures.rst:523 msgid "Here is a small example using a dictionary::" @@ -969,8 +971,8 @@ msgid "" "To loop over two or more sequences at the same time, the entries can be " "paired with the :func:`zip` function. ::" msgstr "" -"Aynı anda iki veya daha fazla dizi üzerinde döngü yapmak için, girdiler :" -"func:`zip` fonksiyonu ile eşleştirilebilir. ::" +"Aynı anda iki veya daha fazla dizi üzerinde döngü yapmak için, " +"girdiler :func:`zip` fonksiyonu ile eşleştirilebilir. ::" #: tutorial/datastructures.rst:591 msgid "" @@ -1029,8 +1031,8 @@ msgstr "" #: tutorial/datastructures.rst:626 msgid "" -"Using :func:`set` on a sequence eliminates duplicate elements. The use of :" -"func:`sorted` in combination with :func:`set` over a sequence is an " +"Using :func:`set` on a sequence eliminates duplicate elements. The use " +"of :func:`sorted` in combination with :func:`set` over a sequence is an " "idiomatic way to loop over unique elements of the sequence in sorted " "order. ::" msgstr "" @@ -1223,8 +1225,8 @@ msgstr "" "türlerdeki nesnelerin ``<`` veya ``>`` ile karşılaştırılabileceğini " "unutmayın. Örneğin, karışık sayısal türler sayısal değerlerine göre " "karşılaştırılır, bu nedenle 0 eşittir 0.0, vb. Bu türler uygun yöntemlere " -"sahip değillerse, yorumlayıcı rastgele bir sıralama döndürmek yerine :exc:" -"`TypeError` hatası verir." +"sahip değillerse, yorumlayıcı rastgele bir sıralama döndürmek " +"yerine :exc:`TypeError` hatası verir." #: tutorial/datastructures.rst:732 msgid "Footnotes" diff --git a/tutorial/errors.po b/tutorial/errors.po index 85e7eb440..5199c4356 100644 --- a/tutorial/errors.po +++ b/tutorial/errors.po @@ -110,18 +110,18 @@ msgstr "" 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)." +"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 "" "Hata iletisinin son satırı hataya neyin sebep olduğu gösterir. Özel durumlar " "farklı türlerde gelir ve tür iletinin bir parçası olarak yazdırılır: " -"örnekteki türler şunlardır :exc:`ZeroDivisionError`, :exc:`NameError` ve :" -"exc:`TypeError`. Özel durum türü olarak yazdırılan dize, oluşan gömülü özel " -"durumun adıdır. Bu, tüm gömülü özel durumlar için geçerlidir, ancak " +"örnekteki türler şunlardır :exc:`ZeroDivisionError`, :exc:`NameError` " +"ve :exc:`TypeError`. Özel durum türü olarak yazdırılan dize, oluşan gömülü " +"özel durumun adıdır. Bu, tüm gömülü özel durumlar için geçerlidir, ancak " "kullanıcı tanımlı özel durumlar için doğru olması gerekmez (yararlı bir " "kural olmasına rağmen). Standart özel durum adları gömülü tanımlayıcılardır " "(ayrılmış anahtar sözcükler değildir)." @@ -160,16 +160,17 @@ msgstr "Özel Durumları İşleme" 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. ::" +"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 "" "Seçili özel durumları işleyen programlar yazmak mümkündür. Geçerli bir tam " "sayı girilene kadar kullanıcıdan giriş isteyen, ancak kullanıcının programı " "kesmesine izin veren aşağıdaki örneğe bakın (:kbd:`Control-C` veya işletim " -"sistemi ne destekliyorsa onu kullanarak); kullanıcı kaynaklı kesintilerin :" -"exc:`KeyboardInterrupt` özel durumu ile gösterildiğini unutmayın. ::" +"sistemi ne destekliyorsa onu kullanarak); kullanıcı kaynaklı " +"kesintilerin :exc:`KeyboardInterrupt` özel durumu ile gösterildiğini " +"unutmayın. ::" #: tutorial/errors.rst:88 msgid "" @@ -188,16 +189,16 @@ msgstr ":keyword:`try` ifadesi aşağıdaki gibi çalışır." #: tutorial/errors.rst:98 msgid "" -"First, the *try clause* (the statement(s) between the :keyword:`try` and :" -"keyword:`except` keywords) is executed." +"First, the *try clause* (the statement(s) between the :keyword:`try` " +"and :keyword:`except` keywords) is executed." msgstr "" "İlk olarak, *try yan tümcesi* (:keyword:`try` ve :keyword:`except` anahtar " "kelimeleri arasındaki ifadeler) yürütülür." #: tutorial/errors.rst:101 msgid "" -"If no exception occurs, the *except clause* is skipped and execution of the :" -"keyword:`try` statement is finished." +"If no exception occurs, the *except clause* is skipped and execution of " +"the :keyword:`try` statement is finished." msgstr "" "Özel durum oluşmazsa, *except yan tümcesi* atlanır ve :keyword:`try` " "ifadesinin yürütülmesi tamamlanır." @@ -355,17 +356,17 @@ msgid "" "subclasses, :exc:`Exception`, is the base class of all the non-fatal " "exceptions. Exceptions which are not subclasses of :exc:`Exception` are not " "typically handled, because they are used to indicate that the program should " -"terminate. They include :exc:`SystemExit` which is raised by :meth:`sys." -"exit` and :exc:`KeyboardInterrupt` which is raised when a user wishes to " -"interrupt the program." +"terminate. They include :exc:`SystemExit` which is raised " +"by :meth:`sys.exit` and :exc:`KeyboardInterrupt` which is raised when a user " +"wishes to interrupt the program." msgstr "" ":exc:`BaseException`, tüm istisnaların ortak temel sınıfıdır. Alt " "sınıflarından biri olan :exc:`Exception`, tüm önemli olmayan istisnaların " "temel sınıfıdır. :exc:`Exception` öğesinin alt sınıfları olmayan istisnalar " "genellikle işlenmez, çünkü bunlar programın sona ermesi gerektiğini " -"belirtmek için kullanılır. Bunlar :meth:`sys.exit` tarafından oluşturulan :" -"exc:`SystemExit` ve bir kullanıcı programı kesmek istediğinde ortaya çıkan :" -"exc:`KeyboardInterrupt` içerir." +"belirtmek için kullanılır. Bunlar :meth:`sys.exit` tarafından " +"oluşturulan :exc:`SystemExit` ve bir kullanıcı programı kesmek istediğinde " +"ortaya çıkan :exc:`KeyboardInterrupt` içerir." #: tutorial/errors.rst:187 msgid "" @@ -439,8 +440,8 @@ msgid "" msgstr "" ":keyword:`!else` yan tümcesinin kullanılması, :keyword:`try` yan tümcesine " "ek kod eklemekten daha iyidir çünkü yanlışlıkla :keyword:`!try` tarafından " -"korunan kod tarafından oluşturulmamış bir istisnayı yakalamayı önler. ... :" -"keyword:`!except` ifadesi." +"korunan kod tarafından oluşturulmamış bir istisnayı yakalamayı " +"önler. ... :keyword:`!except` ifadesi." #: tutorial/errors.rst:229 msgid "" @@ -561,8 +562,9 @@ msgstr "" #: tutorial/errors.rst:305 msgid "" -"To indicate that an exception is a direct consequence of another, the :" -"keyword:`raise` statement allows an optional :keyword:`from` clause::" +"To indicate that an exception is a direct consequence of another, " +"the :keyword:`raise` statement allows an optional :keyword:`from` " +"clause::" msgstr "" ":keyword:`raise` ifadesi, bir istisnanın başka bir istisnanın doğrudan " "sonucu olduğunu belirtmek için isteğe bağlı :keyword:`from` yan " @@ -639,9 +641,9 @@ msgid "" "indirectly." msgstr "" "Programlar yeni bir istisna sınıfı oluşturarak kendi özel durumlarını " -"adlandırabilir (Python sınıfları hakkında daha fazla bilgi için bkz: :ref:" -"`tut-classes` ). Özel durumlar genellikle doğrudan veya dolaylı olarak :exc:" -"`Exception` sınıfından türetilmelidir." +"adlandırabilir (Python sınıfları hakkında daha fazla bilgi için " +"bkz: :ref:`tut-classes` ). Özel durumlar genellikle doğrudan veya dolaylı " +"olarak :exc:`Exception` sınıfından türetilmelidir." #: tutorial/errors.rst:356 msgid "" @@ -705,11 +707,11 @@ msgid "" "statement produces an exception. The following points discuss more complex " "cases when an exception occurs:" msgstr "" -"Bir :keyword:`finally` yan tümcesi varsa, :keyword:`!finally` yan tümcesi :" -"keyword:`try` deyimi tamamlanmadan önceki son görev olarak yürütülür. :" -"keyword:`!finally` yan tümcesi :keyword:`!try` deyiminin bir istisna " -"oluşturup oluşturmadığından bağımsız çalışır. Aşağıdaki noktalarda, bir " -"istisna oluştuğunda daha karmaşık durumlar anlatılmaktadır:" +"Bir :keyword:`finally` yan tümcesi varsa, :keyword:`!finally` yan " +"tümcesi :keyword:`try` deyimi tamamlanmadan önceki son görev olarak " +"yürütülür. :keyword:`!finally` yan tümcesi :keyword:`!try` deyiminin bir " +"istisna oluşturup oluşturmadığından bağımsız çalışır. Aşağıdaki noktalarda, " +"bir istisna oluştuğunda daha karmaşık durumlar anlatılmaktadır:" #: tutorial/errors.rst:392 msgid "" @@ -720,14 +722,15 @@ msgid "" msgstr "" ":keyword:`!try` yan tümcesinin yürütülmesi sırasında bir istisna oluşursa, " "istisna bir :keyword:`except` yan tümcesi tarafından işlenebilir. İstisna " -"bir :keyword:`!except` yan tümcesi tarafından ele alınmıyorsa, istisna :" -"keyword:`!finally` yan tümcesi yürütüldükten sonra yeniden oluşturulur." +"bir :keyword:`!except` yan tümcesi tarafından ele alınmıyorsa, " +"istisna :keyword:`!finally` yan tümcesi yürütüldükten sonra yeniden " +"oluşturulur." #: tutorial/errors.rst:398 msgid "" -"An exception could occur during execution of an :keyword:`!except` or :" -"keyword:`!else` clause. Again, the exception is re-raised after the :keyword:" -"`!finally` clause has been executed." +"An exception could occur during execution of an :keyword:`!except` " +"or :keyword:`!else` clause. Again, the exception is re-raised after " +"the :keyword:`!finally` clause has been executed." msgstr "" "Bir :keyword:`!except` veya :keyword:`!else` yan tümcesinin yürütülmesi " "sırasında bir istisna oluşabilir. Yine, istisna, :keyword:`!finally` yan " @@ -735,35 +738,36 @@ msgstr "" #: tutorial/errors.rst:402 msgid "" -"If the :keyword:`!finally` clause executes a :keyword:`break`, :keyword:" -"`continue` or :keyword:`return` statement, exceptions are not re-raised." +"If the :keyword:`!finally` clause executes " +"a :keyword:`break`, :keyword:`continue` or :keyword:`return` statement, " +"exceptions are not re-raised." msgstr "" ":keyword:`!finally` yan tümcesi bir :keyword:`break`, :keyword:`continue` " "veya :keyword:`return` deyimini yürütürse, istisnalar yeniden oluşturulmaz." #: tutorial/errors.rst:406 msgid "" -"If the :keyword:`!try` statement reaches a :keyword:`break`, :keyword:" -"`continue` or :keyword:`return` statement, the :keyword:`!finally` clause " -"will execute just prior to the :keyword:`!break`, :keyword:`!continue` or :" -"keyword:`!return` statement's execution." +"If the :keyword:`!try` statement reaches " +"a :keyword:`break`, :keyword:`continue` or :keyword:`return` statement, " +"the :keyword:`!finally` clause will execute just prior to the :keyword:`!" +"break`, :keyword:`!continue` or :keyword:`!return` statement's execution." msgstr "" -":keyword:`!try` ifadesi bir :keyword:`break`, :keyword:`continue` veya :" -"keyword:`return` ifadesine ulaşırsa, :keyword:`!finally` yan tümcesi :" -"keyword:`!break`, :keyword:`!continue` veya :keyword:`!return` ifadesinin " -"yürütülmesinin hemen öncesinde yürütülür." +":keyword:`!try` ifadesi bir :keyword:`break`, :keyword:`continue` " +"veya :keyword:`return` ifadesine ulaşırsa, :keyword:`!finally` yan " +"tümcesi :keyword:`!break`, :keyword:`!continue` veya :keyword:`!return` " +"ifadesinin yürütülmesinin hemen öncesinde yürütülür." #: tutorial/errors.rst:412 msgid "" "If a :keyword:`!finally` clause includes a :keyword:`!return` statement, the " -"returned value will be the one from the :keyword:`!finally` clause's :" -"keyword:`!return` statement, not the value from the :keyword:`!try` " -"clause's :keyword:`!return` statement." +"returned value will be the one from the :keyword:`!finally` " +"clause's :keyword:`!return` statement, not the value from the :keyword:`!" +"try` clause's :keyword:`!return` statement." msgstr "" "Bir :keyword:`!finally` yan tümcesi bir :keyword:`!return` ifadesini " "içeriyorsa, döndürülen değer, :keyword:`!finally` yan tümcesinin :keyword:`!" -"return` ifadesindeki değer olacaktır, :keyword:`!try` yan tümcesinin :" -"keyword:`!return` ifadesindeki değer değil." +"return` ifadesindeki değer olacaktır, :keyword:`!try` yan " +"tümcesinin :keyword:`!return` ifadesindeki değer değil." #: tutorial/errors.rst:418 msgid "For example::" @@ -814,8 +818,8 @@ msgstr "" #: tutorial/errors.rst:454 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:`!" +"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 "" "Gördüğünüz gibi, :keyword:`finally` yan tümcesi her durumda yürütülür. İki " @@ -866,9 +870,9 @@ msgid "" msgstr "" "Bu kodla ilgili sorun, kodun bu bölümünün yürütülmesi tamamlandıktan sonra " "dosyayı belirsiz bir süre açık bırakmasıdır. Bu basit komut dosyalarında bir " -"sorun değildir, ancak daha büyük uygulamalar için bir sorun olabilir. :" -"keyword:`with` ifadesi, dosyalar gibi nesnelerin her zaman hızlı ve doğru " -"temizlenmesini sağlayacak şekilde kullanılmasına izin verir. ::" +"sorun değildir, ancak daha büyük uygulamalar için bir sorun " +"olabilir. :keyword:`with` ifadesi, dosyalar gibi nesnelerin her zaman hızlı " +"ve doğru temizlenmesini sağlayacak şekilde kullanılmasına izin verir. ::" #: tutorial/errors.rst:483 msgid "" @@ -1133,8 +1137,8 @@ msgstr "" #~ "The :keyword:`raise` statement allows an optional :keyword:`from` " #~ "which enables chaining exceptions. For example::" #~ msgstr "" -#~ ":keyword:`raise` ifadesi, zincirleme istisnalar sağlayan opsiyonel bir :" -#~ "keyword:`raise` 'e izin verir. Örneğin::" +#~ ":keyword:`raise` ifadesi, zincirleme istisnalar sağlayan opsiyonel " +#~ "bir :keyword:`raise` 'e izin verir. Örneğin::" #~ msgid "" #~ "Exception chaining happens automatically when an exception is raised " diff --git a/tutorial/floatingpoint.po b/tutorial/floatingpoint.po index 3b72ea7a9..5098772ae 100644 --- a/tutorial/floatingpoint.po +++ b/tutorial/floatingpoint.po @@ -252,8 +252,8 @@ msgstr "" #, fuzzy 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:" +"cannot get any closer to the exact value of 3/10, then pre-rounding " +"with :func:`round` function cannot help:" msgstr "" "Ayrıca, 0,1 tam 1/10 değerine ve 0,3 tam 3/10 değerine daha fazla " "yaklaşamayacağından, :func:`round` fonksiyonu ile ön yuvarlama yapmak " @@ -335,25 +335,25 @@ 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`." +"expect. :func:`str` usually suffices, and for finer control see " +"the :meth:`str.format` method's format specifiers in :ref:`formatstrings`." msgstr "" "Patolojik durumlar mevcut olsa da, kayan noktalı aritmetiğin sıradan " "kullanımı için, nihai sonuçlarınızın görüntüsünü beklediğiniz ondalık " -"basamak sayısına yuvarlarsanız, sonunda beklediğiniz sonucu görürsünüz. :" -"func:`str` genellikle yeterlidir ve daha ince kontrol için :ref:" -"`formatstrings` içindeki :meth:`str.format` yönteminin biçim " +"basamak sayısına yuvarlarsanız, sonunda beklediğiniz sonucu " +"görürsünüz. :func:`str` genellikle yeterlidir ve daha ince kontrol " +"için :ref:`formatstrings` içindeki :meth:`str.format` yönteminin biçim " "belirleyicilerine bakın." #: tutorial/floatingpoint.rst:169 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." +"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 "" "Tam ondalık gösterim gerektiren durumlar için, muhasebe uygulamaları ve " -"yüksek hassasiyetli uygulamalar için uygun ondalık aritmetiği uygulayan :mod:" -"`decimal` modülünü kullanmayı deneyin." +"yüksek hassasiyetli uygulamalar için uygun ondalık aritmetiği " +"uygulayan :mod:`decimal` modülünü kullanmayı deneyin." #: tutorial/floatingpoint.rst:173 msgid "" @@ -370,8 +370,8 @@ msgstr "" msgid "" "If you are a heavy user of floating-point operations you should take a look " "at the NumPy package and many other packages for mathematical and " -"statistical operations supplied by the SciPy project. See ." +"statistical operations supplied by the SciPy project. See ." msgstr "" "Kayan nokta işlemlerinin yoğun bir kullanıcısıysanız, NumPy paketine ve " "SciPy projesi tarafından sağlanan matematiksel ve istatistiksel işlemler " @@ -381,13 +381,14 @@ msgstr "" #, fuzzy 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:" +"*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 "" "Python, bir kayan noktanın tam değerini *gerçekten* bilmek istediğiniz nadir " -"durumlarda yardımcı olabilecek araçlar sağlar. :meth:`float." -"as_integer_ratio` metodu bir kayan noktanın değerini kesir olarak ifade " -"eder::" +"durumlarda yardımcı olabilecek araçlar " +"sağlar. :meth:`float.as_integer_ratio` metodu bir kayan noktanın değerini " +"kesir olarak ifade eder::" #: tutorial/floatingpoint.rst:186 msgid "" diff --git a/tutorial/index.po b/tutorial/index.po index 727d509dc..fa794f272 100644 --- a/tutorial/index.po +++ b/tutorial/index.po @@ -76,8 +76,9 @@ msgstr "" 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." +"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 "" "Standart nesnelerin ve modüllerin açıklaması için :ref:`library-index` 'e " "bakınız. :ref:`reference-index` dilin daha resmi bir tanımını verir. " diff --git a/tutorial/inputoutput.po b/tutorial/inputoutput.po index 6c7524ace..91ee9aee3 100644 --- a/tutorial/inputoutput.po +++ b/tutorial/inputoutput.po @@ -39,16 +39,16 @@ msgstr "Güzel Çıktı Biçimlendirmesi" #, fuzzy 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:`~io." -"TextIOBase.write` method of file objects; the standard output file can be " -"referenced as ``sys.stdout``. See the Library Reference for more information " -"on this.)" +"and the :func:`print` function. (A third way is using " +"the :meth:`~io.TextIOBase.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 "" "Şimdiye kadar iki değer yazma yolu ile karşılaştık: *expression statements* " -"ve :func:`print` fonksiyonu. (Üçüncü bir yol, dosya nesnelerinin :meth:" -"`write` yöntemini kullanmaktır; standart çıktı dosyasına ``sys.stdout`` " -"olarak başvurulabilir. Bu konuda daha fazla bilgi için Kütüphane " -"Referansı'na bakın.)" +"ve :func:`print` fonksiyonu. (Üçüncü bir yol, dosya " +"nesnelerinin :meth:`write` yöntemini kullanmaktır; standart çıktı dosyasına " +"``sys.stdout`` olarak başvurulabilir. Bu konuda daha fazla bilgi için " +"Kütüphane Referansı'na bakın.)" #: tutorial/inputoutput.rst:22 msgid "" @@ -108,8 +108,8 @@ msgstr "" msgid "" "Notice how the ``yes_votes`` are padded with spaces and a negative sign only " "for negative numbers. The example also prints ``percentage`` multiplied by " -"100, with 2 decimal places and followed by a percent sign (see :ref:" -"`formatspec` for details)." +"100, with 2 decimal places and followed by a percent sign " +"(see :ref:`formatspec` for details)." msgstr "" #: tutorial/inputoutput.rst:57 @@ -139,20 +139,21 @@ msgstr "" 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 " +"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 "" ":func:`str` işlevi açıkça okunabilir değerlerin gösterimlerini döndürmek " "için, :func:`repr` ise yorumlayıcı tarafından okunabilecek gösterimler " "oluşturmak içindir (veya eş değer bir sözdizimi yoksa :exc:`SyntaxError` 'ı " -"zorlar). İnsan tüketimi için belirli bir temsili olmayan nesneler için :" -"func:`str`, :func:`repr` ile aynı değeri döndürür. Sayılar veya listeler ve " -"sözlükler benzeri yapılar gibi birçok değer, her iki işlevi de kullanarak " -"aynı gösterime sahiptir. Özellikle dizelerin iki farklı gösterimi vardır." +"zorlar). İnsan tüketimi için belirli bir temsili olmayan nesneler " +"için :func:`str`, :func:`repr` ile aynı değeri döndürür. Sayılar veya " +"listeler ve sözlükler benzeri yapılar gibi birçok değer, her iki işlevi de " +"kullanarak aynı gösterime sahiptir. Özellikle dizelerin iki farklı " +"gösterimi vardır." #: tutorial/inputoutput.rst:75 msgid "Some examples::" @@ -254,8 +255,8 @@ msgid "" "applies :func:`repr`::" msgstr "" "Diğer değiştiriciler, değeri biçimlendirilmeden önce dönüştürmek için " -"kullanılabilir. ``'!a'`` :func:`ascii`, ``'!s'`` :func:`str`, ve ``'!r'`` :" -"func:`repr` uygular::" +"kullanılabilir. ``'!a'`` :func:`ascii`, ``'!s'`` :func:`str`, ve ``'!" +"r'`` :func:`repr` uygular::" #: tutorial/inputoutput.rst:144 msgid "" @@ -304,8 +305,8 @@ msgstr "" 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. ::" +"brackets can be used to refer to the position of the object passed into " +"the :meth:`str.format` method. ::" msgstr "" "İçlerindeki köşeli ayraçlar ve karakterler (format fields olarak " "adlandırılır) :meth:`str.format` yöntemine geçirilen nesnelerle " @@ -379,16 +380,17 @@ msgstr "" #: tutorial/inputoutput.rst:209 msgid "" ">>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 8637678}\n" -">>> print('Jack: {Jack:d}; Sjoerd: {Sjoerd:d}; Dcab: {Dcab:d}'." -"format(**table))\n" +">>> print('Jack: {Jack:d}; Sjoerd: {Sjoerd:d}; Dcab: " +"{Dcab:d}'.format(**table))\n" "Jack: 4098; Sjoerd: 4127; Dcab: 8637678" msgstr "" #: tutorial/inputoutput.rst:213 #, fuzzy msgid "" -"This is particularly useful in combination with the built-in function :func:" -"`vars`, which returns a dictionary containing all local variables::" +"This is particularly useful in combination with the built-in " +"function :func:`vars`, which returns a dictionary containing all local " +"variables::" msgstr "" "Bu, özellikle tüm yerel değişkenleri içeren bir sözlük döndüren yerleşik " "işlev :func:`vars` ile birlikte yararlıdır." @@ -428,11 +430,11 @@ msgstr "" #: tutorial/inputoutput.rst:238 msgid "" -"For a complete overview of string formatting with :meth:`str.format`, see :" -"ref:`formatstrings`." +"For a complete overview of string formatting with :meth:`str.format`, " +"see :ref:`formatstrings`." msgstr "" -":meth:`str.format` ile dize biçimlendirmeye tam bir genel bakış için bkz. :" -"ref:`formatstrings`." +":meth:`str.format` ile dize biçimlendirmeye tam bir genel bakış için " +"bkz. :ref:`formatstrings`." #: tutorial/inputoutput.rst:243 msgid "Manual String Formatting" @@ -463,8 +465,8 @@ msgstr "" #: tutorial/inputoutput.rst:263 msgid "" -"(Note that the one space between each column was added by the way :func:" -"`print` works: it always adds spaces between its arguments.)" +"(Note that the one space between each column was added by the " +"way :func:`print` works: it always adds spaces between its arguments.)" msgstr "" "(Her sütun arasındaki tek boşluğun :func:`print` çalışma şekliyle ekli " "olduğunu unutmayın: her zaman argümanları arasına boşluk ekler.)" @@ -494,8 +496,8 @@ 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 "" -"Soldaki sayısal bir dizeyi sıfırlarla dolduran başka bir metot vardır: :meth:" -"`str.zfill`. Bu metot artı ve eksi işaretlerini anlar::" +"Soldaki sayısal bir dizeyi sıfırlarla dolduran başka bir metot " +"vardır: :meth:`str.zfill`. Bu metot artı ve eksi işaretlerini anlar::" #: tutorial/inputoutput.rst:278 msgid "" @@ -582,18 +584,19 @@ msgid "" "*encoding*. If *encoding* is not specified, the default is platform " "dependent (see :func:`open`). Because UTF-8 is the modern de-facto standard, " "``encoding=\"utf-8\"`` is recommended unless you know that you need to use a " -"different encoding. Appending a ``'b'`` to the mode opens the file in :dfn:" -"`binary mode`. Binary mode data is read and written as :class:`bytes` " -"objects. You can not specify *encoding* when opening file in binary mode." +"different encoding. Appending a ``'b'`` to the mode opens the file " +"in :dfn:`binary mode`. Binary mode data is read and written " +"as :class:`bytes` objects. You can not specify *encoding* when opening file " +"in binary mode." msgstr "" "Normalde dosyalar :dfn:`text mode` 'unda açılır, yani belirli bir *kodlamada " "(encoding)* kodlanmış dizeleri dosyadan okur ve dosyaya yazarsınız. " -"*kodlama* belirtilmezse, varsayılan değer platforma bağlıdır (bakınız :func:" -"`open`). UTF-8 modern de-fakto standart olduğundan, farklı bir kodlama " -"kullanmanız gerekmiyorsa ``encoding=\"utf-8\"`` kullanmanız önerilir. Moda " -"``'b'`` eklemek, dosyayı :dfn:`binary` modunda açar. İkili mod verileri, :" -"class:`bytes` nesneleri olarak okunur ve yazılır. Dosyayı ikili modda " -"açarken *kodlama* belirtemezsiniz." +"*kodlama* belirtilmezse, varsayılan değer platforma bağlıdır " +"(bakınız :func:`open`). UTF-8 modern de-fakto standart olduğundan, farklı " +"bir kodlama kullanmanız gerekmiyorsa ``encoding=\"utf-8\"`` kullanmanız " +"önerilir. Moda ``'b'`` eklemek, dosyayı :dfn:`binary` modunda açar. İkili " +"mod verileri, :class:`bytes` nesneleri olarak okunur ve yazılır. Dosyayı " +"ikili modda açarken *kodlama* belirtemezsiniz." #: tutorial/inputoutput.rst:344 msgid "" @@ -601,9 +604,9 @@ msgid "" "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." +"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 "" "Metin modunda, okurken varsayılan değer platforma özgü satır sonlarını " "(``\\n`` on Unix, ``\\r\\n`` on Windows) yalnızca ``\\n`` olarak " @@ -618,15 +621,15 @@ msgstr "" msgid "" "It is good practice to use the :keyword:`with` keyword when dealing with " "file objects. The advantage is that the file is properly closed after its " -"suite finishes, even if an exception is raised at some point. Using :" -"keyword:`!with` is also much shorter than writing equivalent :keyword:" -"`try`\\ -\\ :keyword:`finally` blocks::" +"suite finishes, even if an exception is raised at some point. " +"Using :keyword:`!with` is also much shorter than writing " +"equivalent :keyword:`try`\\ -\\ :keyword:`finally` blocks::" msgstr "" "Dosya nesneleriyle uğraşırken :keyword:`with` anahtar sözcüğünü kullanmak " "iyi bir uygulamadır. Avantajı, herhangi bir noktada bir hata oluşsa bile, " -"paketi bittikten sonra dosyanın düzgün bir şekilde kapatılmasıdır. :keyword:" -"`!with` kullanmak da eş değer :keyword:`try` \\ -\\ :keyword:`finally` " -"blokları yazmaktançok daha kısadır::" +"paketi bittikten sonra dosyanın düzgün bir şekilde " +"kapatılmasıdır. :keyword:`!with` kullanmak da eş değer :keyword:`try` \\ -" +"\\ :keyword:`finally` blokları yazmaktançok daha kısadır::" #: tutorial/inputoutput.rst:358 msgid "" @@ -640,8 +643,8 @@ msgstr "" #: tutorial/inputoutput.rst:365 msgid "" -"If you're not using the :keyword:`with` keyword, then you should call ``f." -"close()`` to close the file and immediately free up any system resources " +"If you're not using the :keyword:`with` keyword, then you should call " +"``f.close()`` to close the file and immediately free up any system resources " "used by it." msgstr "" ":keyword:`with` anahtar sözcüğünü kullanmıyorsanız, dosyayı kapatmak ve " @@ -728,10 +731,10 @@ msgid "" msgstr "" "``f.readline()`` dosyadan tek bir satır okur; dizenin sonunda bir newline " "karakteri (``\\n``) bırakılır ve dosya yalnızca dosya yeni satırda bitmezse " -"dosyanın son satırında atlanır. Bu, dönüş değerini netleştirir; ``f." -"readline()`` boş bir dize döndürürse, dosyanın sonuna ulaşılmış demektir, " -"boş bir satır ise yalnızca tek bir yeni satır içeren bir dize olan ``'\\n'`` " -"ile temsil edilir. ::" +"dosyanın son satırında atlanır. Bu, dönüş değerini netleştirir; " +"``f.readline()`` boş bir dize döndürürse, dosyanın sonuna ulaşılmış " +"demektir, boş bir satır ise yalnızca tek bir yeni satır içeren bir dize olan " +"``'\\n'`` ile temsil edilir. ::" #: tutorial/inputoutput.rst:418 msgid "" @@ -863,9 +866,9 @@ msgid "" "and :meth:`~io.IOBase.truncate` which are less frequently used; consult the " "Library Reference for a complete guide to file objects." msgstr "" -"Dosya nesnelerinin daha az kullanılan :meth:`~file.isatty` ve :meth:`~file." -"truncate` gibi bazı ek metotları vardır; dosya nesneleri için eksiksiz bir " -"kılavuz için Kütüphane Referansı'na bakın." +"Dosya nesnelerinin daha az kullanılan :meth:`~file.isatty` " +"ve :meth:`~file.truncate` gibi bazı ek metotları vardır; dosya nesneleri " +"için eksiksiz bir kılavuz için Kütüphane Referansı'na bakın." #: tutorial/inputoutput.rst:488 msgid "Saving structured data with :mod:`json`" @@ -892,8 +895,8 @@ msgstr "" 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 " +"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 " @@ -939,9 +942,10 @@ msgstr "" #: tutorial/inputoutput.rst:522 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::" +"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 "" ":func:`~json.dumps` işlevinin başka bir çeşidi, :func:`~json.dump` adı " "verilen nesneyi bir :term:`text file` (metin dosyası) olarak seri hale " @@ -957,8 +961,8 @@ msgid "" "To decode the object again, if ``f`` is a :term:`binary file` or :term:`text " "file` object which has been opened for reading::" msgstr "" -"Nesnenin kodunu tekrar çözmek için, ``f`` okuma için açılmış bir :term:" -"`binary file` veya :term:`text file` nesnesiyse::" +"Nesnenin kodunu tekrar çözmek için, ``f`` okuma için açılmış " +"bir :term:`binary file` veya :term:`text file` nesnesiyse::" #: tutorial/inputoutput.rst:531 msgid "x = json.load(f)" diff --git a/tutorial/interactive.po b/tutorial/interactive.po index ee4f05cee..b444c6807 100644 --- a/tutorial/interactive.po +++ b/tutorial/interactive.po @@ -50,21 +50,22 @@ msgid "" "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:`~object.__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." +"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 "" -"Değişken ve modül adlarının tamamlanması, yorumlayıcı başlangıcında :ref:" -"`otomatik olarak etkinleştirilir `, böylece :kbd:`Tab` " -"tuşu tamamlama işlevini çağırır; Python deyim adlarına, mevcut yerel " -"değişkenlere ve kullanılabilir modül adlarına bakar. ``string.a`` gibi " -"noktalı ifadeler için, ifadeyi ``'.'`` sonuna kadar değerlendirecek ve " -"ardından ortaya çıkan nesnenin niteliklerinden tamamlamalar önerecektir. :" -"meth:`__getattr__` yöntemine sahip bir nesne ifadenin bir parçasıysa bunun " -"uygulama tanımlı kodu çalıştırabileceğini unutmayın. Varsayılan yapılandırma " -"aynı zamanda geçmişinizi kullanıcı dizininizdeki :file:`.python_history` " -"adlı bir dosyaya da kaydeder. Geçmiş, bir sonraki interaktif tercüman " -"oturumu sırasında tekrar kullanılabilir olacaktır." +"Değişken ve modül adlarının tamamlanması, yorumlayıcı " +"başlangıcında :ref:`otomatik olarak etkinleştirilir `, " +"böylece :kbd:`Tab` tuşu tamamlama işlevini çağırır; Python deyim adlarına, " +"mevcut yerel değişkenlere ve kullanılabilir modül adlarına bakar. " +"``string.a`` gibi noktalı ifadeler için, ifadeyi ``'.'`` sonuna kadar " +"değerlendirecek ve ardından ortaya çıkan nesnenin niteliklerinden " +"tamamlamalar önerecektir. :meth:`__getattr__` yöntemine sahip bir nesne " +"ifadenin bir parçasıysa bunun uygulama tanımlı kodu çalıştırabileceğini " +"unutmayın. Varsayılan yapılandırma aynı zamanda geçmişinizi kullanıcı " +"dizininizdeki :file:`.python_history` adlı bir dosyaya da kaydeder. Geçmiş, " +"bir sonraki interaktif tercüman oturumu sırasında tekrar kullanılabilir " +"olacaktır." #: tutorial/interactive.rst:36 msgid "Alternatives to the Interactive Interpreter" diff --git a/tutorial/interpreter.po b/tutorial/interpreter.po index 2eac2568c..5527f2321 100644 --- a/tutorial/interpreter.po +++ b/tutorial/interpreter.po @@ -58,8 +58,8 @@ msgstr "" msgid "" "On Windows machines where you have installed Python from the :ref:`Microsoft " "Store `, the :file:`python3.12` command will be available. If " -"you have the :ref:`py.exe launcher ` installed, you can use the :" -"file:`py` command. See :ref:`setting-envvars` for other ways to launch " +"you have the :ref:`py.exe launcher ` installed, you can use " +"the :file:`py` command. See :ref:`setting-envvars` for other ways to launch " "Python." msgstr "" "Python'ı :ref:`Microsoft Store ` yüklediğiniz Windows " @@ -118,10 +118,10 @@ msgstr "" #: tutorial/interpreter.rst:51 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." +"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." msgstr "" "Yorumlayıcıyı başlatmanın ikinci bir yolu, kabuğun :option:`-c` seçeneğine " "benzer şekilde *command* içindeki deyimleri çalıştıran ``python -c command " @@ -142,8 +142,8 @@ msgstr "" #: tutorial/interpreter.rst:61 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." +"script and enter interactive mode afterwards. This can be done by " +"passing :option:`-i` before the script." msgstr "" "Bir komut dosyası kullanıldığında, bazen komut dosyasını çalıştırabilmek ve " "daha sonra etkileşimli moda girebilmek yararlıdır. Bu komut dosyasından " @@ -183,8 +183,8 @@ msgstr "" "c`` olarak ayarlanır. :option:`-m` *modül* kullanıldığında, ``sys.argv[0]`` " "bulunan modülün tam adına ayarlanır. :option:`-c` *komut* veya :option:`-m` " "*modül* 'den sonra bulunan seçenekler, Python yorumlayıcısının seçenek " -"işlemesi tarafından tüketilmez, ancak komut veya modülün işlemesi için ``sys." -"argv`` içinde bırakılır." +"işlemesi tarafından tüketilmez, ancak komut veya modülün işlemesi için " +"``sys.argv`` içinde bırakılır." #: tutorial/interpreter.rst:89 msgid "Interactive Mode" diff --git a/tutorial/introduction.po b/tutorial/introduction.po index b313108fe..f8869c3d4 100644 --- a/tutorial/introduction.po +++ b/tutorial/introduction.po @@ -124,8 +124,9 @@ msgstr "" #: tutorial/introduction.rst:68 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." +"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 "" "Tam sayıların (örneğin ``2``, ``4``, ``20``) türü :class:`int` olup, kesirli " "kısmı olanlar (örneğin ``5.0``, ``1.6``) :class:`float` türüne sahiptir. " @@ -253,16 +254,16 @@ msgstr "" #: tutorial/introduction.rst:132 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``)." +"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 "" -":class:`int` ve :class:`float` 'a ek olarak Python, :class:`~decimal." -"Decimal` ve :class:`~fractions.Fraction` gibi diğer sayı türlerini de " -"destekler. Python ayrıca :ref:`karmaşık sayılar ` için gömülü " -"desteğe sahiptir ve hayali kısmı belirtmek için ``j`` veya ``J`` son ekini " -"kullanır (ör. ``3+5j``)." +":class:`int` ve :class:`float` 'a ek olarak " +"Python, :class:`~decimal.Decimal` ve :class:`~fractions.Fraction` gibi diğer " +"sayı türlerini de destekler. Python ayrıca :ref:`karmaşık sayılar " +"` için gömülü desteğe sahiptir ve hayali kısmı belirtmek için " +"``j`` veya ``J`` son ekini kullanır (ör. ``3+5j``)." #: tutorial/introduction.rst:142 msgid "Text" @@ -276,11 +277,12 @@ msgid "" "\"``Yay! :)``\". They can be enclosed in single quotes (``'...'``) or double " "quotes (``\"...\"``) with the same result [#]_." msgstr "" -"Python sayıların yanı sıra metinleri de (\"string\" olarak adlandırılan :" -"class:`str` türü ile temsil edilir) işleyebilir. Bu karakterleri \"``!``\", " -"kelimeleri \"``tavşan``\", isimleri \"``Paris``\", cümleleri \"``Arkanı " -"kolluyorum.``\", vb. içerir. \"``Yay! :)``\". Tek tırnak (``'...'``) veya " -"çift tırnak (``\"...\"``) içine alınabilirler ve aynı sonucu verirler [#]_." +"Python sayıların yanı sıra metinleri de (\"string\" olarak " +"adlandırılan :class:`str` türü ile temsil edilir) işleyebilir. Bu " +"karakterleri \"``!``\", kelimeleri \"``tavşan``\", isimleri \"``Paris``\", " +"cümleleri \"``Arkanı kolluyorum.``\", vb. içerir. \"``Yay! :)``\". Tek " +"tırnak (``'...'``) veya çift tırnak (``\"...\"``) içine alınabilirler ve " +"aynı sonucu verirler [#]_." #: tutorial/introduction.rst:157 msgid "" @@ -797,8 +799,8 @@ msgstr "" #: tutorial/introduction.rst:423 #, fuzzy 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)::" +"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 "" "Ayrıca, :meth:`~list.append` *method*'u kullanarak listenin sonuna yeni " "öğeler ekleyebilirsiniz (yöntemler hakkında daha fazla bilgiyi daha sonra " @@ -1105,7 +1107,7 @@ msgstr "yorum" #~ "özel karakterler ters eğik çizgiyle çıkarılır. Bu bazen girdiden farklı " #~ "görünse de (ilgili tırnak işaretleri değişebilir), iki dize eş değerdir. " #~ "Dize tek bir tırnak işareti içeriyorsa ve çift tırnak içermiyorsa dize " -#~ "çift tırnak içine alınır, aksi takdirde tek tırnak içine alınır. :func:" -#~ "`print` fonksiyonu, ekteki tırnak işaretlerini atlayarak ve çıkış " -#~ "karakterlerini ve özel karakterleri yazdırarak daha okunaklı bir çıktı " -#~ "üretir::" +#~ "çift tırnak içine alınır, aksi takdirde tek tırnak içine " +#~ "alınır. :func:`print` fonksiyonu, ekteki tırnak işaretlerini atlayarak ve " +#~ "çıkış karakterlerini ve özel karakterleri yazdırarak daha okunaklı bir " +#~ "çıktı üretir::" diff --git a/tutorial/modules.po b/tutorial/modules.po index 21632b7e4..2c3e38497 100644 --- a/tutorial/modules.po +++ b/tutorial/modules.po @@ -65,11 +65,12 @@ msgid "" "to create a file called :file:`fibo.py` in the current directory with the " "following contents::" msgstr "" -"Modül, Python tanımlarını ve ifadelerini içeren bir dosyadır. Dosya adı, :" -"file:`.py` son ekini içeren modül adıdır. Bir modül içinde, modülün adı " -"(dize olarak) ``__name__`` genel değişkeninin değeri olarak kullanılabilir. " -"Örneğin, geçerli dizinde aşağıdaki içeriklerle :file:`fibo.py` adlı bir " -"dosya oluşturmak için en sevdiğiniz metin düzenleyicisini kullanın::" +"Modül, Python tanımlarını ve ifadelerini içeren bir dosyadır. Dosya " +"adı, :file:`.py` son ekini içeren modül adıdır. Bir modül içinde, modülün " +"adı (dize olarak) ``__name__`` genel değişkeninin değeri olarak " +"kullanılabilir. Örneğin, geçerli dizinde aşağıdaki " +"içeriklerle :file:`fibo.py` adlı bir dosya oluşturmak için en sevdiğiniz " +"metin düzenleyicisini kullanın::" #: tutorial/modules.rst:28 msgid "" @@ -110,10 +111,10 @@ msgid "" "it only adds the module name ``fibo`` there. Using the module name you can " "access the functions::" msgstr "" -"Bu, ``fibo`` 'da tanımlanan işlevlerin adlarını doğrudan geçerli :term:" -"`namespace` 'e eklemez (daha fazla ayrıntı için bkz. :ref:`tut-scopes`); " -"oraya sadece ``fibo`` modül adını ekler. Modül adını kullanarak şu işlevlere " -"erişebilirsiniz:" +"Bu, ``fibo`` 'da tanımlanan işlevlerin adlarını doğrudan " +"geçerli :term:`namespace` 'e eklemez (daha fazla ayrıntı için " +"bkz. :ref:`tut-scopes`); oraya sadece ``fibo`` modül adını ekler. Modül " +"adını kullanarak şu işlevlere erişebilirsiniz:" #: tutorial/modules.rst:55 msgid "" @@ -247,8 +248,8 @@ msgstr "" #: tutorial/modules.rst:116 msgid "" -"If the module name is followed by :keyword:`!as`, then the name following :" -"keyword:`!as` is bound directly to the imported module." +"If the module name is followed by :keyword:`!as`, then the name " +"following :keyword:`!as` is bound directly to the imported module." msgstr "" "Modül adının ardından :keyword:`!as` geliyorsa, :keyword:`!as` 'den sonraki " "ad doğrudan içe aktarılan modüle bağlanır." @@ -286,14 +287,14 @@ 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)``." +"use :func:`importlib.reload`, e.g. ``import importlib; " +"importlib.reload(modulename)``." msgstr "" "Verimlilik nedeniyle, her modül yorumlayıcı oturumu başına yalnızca bir kez " "içe aktarılır. Bu nedenle, modüllerinizi değiştirirseniz, yorumlayıcıyı " "yeniden başlatmanız gerekir - veya etkileşimli olarak test etmek istediğiniz " -"tek bir modülse, :func:`importlib.reload`, örneğin ``importlib; importlib." -"reload(modulename)``." +"tek bir modülse, :func:`importlib.reload`, örneğin ``importlib; " +"importlib.reload(modulename)``." #: tutorial/modules.rst:147 msgid "Executing modules as scripts" @@ -366,16 +367,18 @@ msgstr "Modül Arama Yolu" #: tutorial/modules.rst:186 msgid "" "When a module named :mod:`!spam` is imported, the interpreter first searches " -"for a built-in module with that name. These module names are listed in :data:" -"`sys.builtin_module_names`. 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:" +"for a built-in module with that name. These module names are listed " +"in :data:`sys.builtin_module_names`. 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 "" ":mod:`!spam` adında bir modül içe aktarıldığında, yorumlayıcı ilk olarak bu " -"ada sahip gömülü bir modül arar. Bu modül adları :data:`sys." -"builtin_module_names` içinde listelenir. Bulamazsa, :data:`sys.path` " -"değişkeni tarafından verilen dizin listesinde :file:`spam.py` adlı bir dosya " -"arar. :data:`sys.path` bu konumlardan başlatılır:" +"ada sahip gömülü bir modül arar. Bu modül " +"adları :data:`sys.builtin_module_names` içinde listelenir. " +"Bulamazsa, :data:`sys.path` değişkeni tarafından verilen dizin " +"listesinde :file:`spam.py` adlı bir dosya arar. :data:`sys.path` bu " +"konumlardan başlatılır:" #: tutorial/modules.rst:192 msgid "" @@ -508,8 +511,8 @@ msgstr "" #: tutorial/modules.rst:251 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." +"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 "" "Bir program ``.pyc`` dosyasından okunduğunda, ``.py`` dosyasından " "okunduğundan daha hızlı çalışmaz; ``.pyc`` dosyaları hakkında daha hızlı " @@ -590,9 +593,9 @@ msgid "" "standard list operations::" msgstr "" "``sys.path`` değişkeni, yorumlayıcının modüller için arama yolunu belirleyen " -"bir dizeler listesidir. :envvar:`PYTHONPATH` ortam değişkeninden veya :" -"envvar:`PYTHONPATH` ayarlanmamışsa yerleşik bir varsayılan değerden alınan " -"varsayılan bir yola başlatılır. Standart liste işlemlerini kullanarak " +"bir dizeler listesidir. :envvar:`PYTHONPATH` ortam değişkeninden " +"veya :envvar:`PYTHONPATH` ayarlanmamışsa yerleşik bir varsayılan değerden " +"alınan varsayılan bir yola başlatılır. Standart liste işlemlerini kullanarak " "değiştirebilirsiniz::" #: tutorial/modules.rst:300 @@ -674,8 +677,8 @@ msgstr "" #: tutorial/modules.rst:350 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`::" +"you want a list of those, they are defined in the standard " +"module :mod:`builtins`::" msgstr "" ":func:`dir` yerleşik fonksiyonlarun ve değişkenlerin adlarını listelemez. " "Bunların bir listesini istiyorsanız, standart modül :mod:`builtins` 'de " @@ -743,22 +746,22 @@ msgstr "" 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):" +"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 "" "Ses dosyalarının ve ses verilerinin tek tip işlenmesi için bir modül " "koleksiyonu (\"paket\") tasarlamak istediğinizi varsayalım. Birçok farklı " -"ses dosyası biçimi vardır (genellikle uzantılarıyla tanınır, örneğin: :file:" -"`.wav`, :file:`.aiff`, :file:`.au`) bu nedenle, çeşitli dosya biçimleri " -"arasında dönüşüm için büyüyen bir modül koleksiyonu oluşturmanız ve " -"sürdürmeniz gerekebilir. Ses verileri üzerinde gerçekleştirmek " +"ses dosyası biçimi vardır (genellikle uzantılarıyla tanınır, " +"örneğin: :file:`.wav`, :file:`.aiff`, :file:`.au`) bu nedenle, çeşitli dosya " +"biçimleri arasında dönüşüm için büyüyen bir modül koleksiyonu oluşturmanız " +"ve sürdürmeniz gerekebilir. Ses verileri üzerinde gerçekleştirmek " "isteyebileceğiniz birçok farklı işlem de vardır (karıştırma, eko ekleme, " "ekolayzır işlevi uygulama, yapay bir stereo efekti oluşturma gibi) bu " "nedenle ek olarak, bu işlemleri gerçekleştirmek için hiç bitmeyen bir modül " @@ -794,8 +797,8 @@ msgstr "" #: tutorial/modules.rst:436 msgid "" -"When importing the package, Python searches through the directories on ``sys." -"path`` looking for the package subdirectory." +"When importing the package, Python searches through the directories on " +"``sys.path`` looking for the package subdirectory." msgstr "" "Paketi içe aktarırken Python, paket alt dizinini arayan ``sys.path`` " "üzerindeki dizinleri arar." @@ -814,10 +817,10 @@ msgstr "" "olarak ele almasını sağlamak için gereklidir (nispeten gelişmiş bir özellik " "olan :term:`namespace package` kullanılmadığı sürece). Bu, ``string`` gibi " "ortak bir ada sahip dizinlerin, modül arama yolunda daha sonra ortaya çıkan " -"geçerli modülleri istemeden gizlemesini önler. En basit durumda, :file:" -"`__init__.py` sadece boş bir dosya olabilir, ancak aynı zamanda paket için " -"başlatma kodunu çalıştırabilir veya daha sonra açıklanacak olan ``__all__`` " -"değişkenini ayarlayabilir." +"geçerli modülleri istemeden gizlemesini önler. En basit " +"durumda, :file:`__init__.py` sadece boş bir dosya olabilir, ancak aynı " +"zamanda paket için başlatma kodunu çalıştırabilir veya daha sonra " +"açıklanacak olan ``__all__`` değişkenini ayarlayabilir." #: tutorial/modules.rst:447 msgid "" @@ -877,8 +880,8 @@ msgstr "" #: tutorial/modules.rst:470 msgid "" -"Again, this loads the submodule :mod:`!echo`, but this makes its function :" -"func:`!echofilter` directly available::" +"Again, this loads the submodule :mod:`!echo`, but this makes its " +"function :func:`!echofilter` directly available::" msgstr "" "Yine, bu, :mod:`!echo` alt modülünü yükler, ancak bu, :func:`!echofilter` " "fonksiyonunu doğrudan kullanılabilir hale getirir::" @@ -893,8 +896,8 @@ msgid "" "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." +"module and attempts to load it. If it fails to find it, " +"an :exc:`ImportError` exception is raised." msgstr "" "``from package import item`` kullanırken, öğenin paketin bir alt modülü " "(veya alt paketi) veya pakette tanımlanmış bir fonksiyon, sınıf veya " @@ -946,15 +949,15 @@ msgid "" "importing \\* from their package. For example, the file :file:`sound/" "effects/__init__.py` could contain the following code::" msgstr "" -"Tek çözüm, paket yazarının paketin açık bir dizinini sağlamasıdır. :keyword:" -"`import` ifadesi aşağıdaki kuralı kullanır: eğer bir paketin :file:`__init__." -"py` kodu ``__all__`` adlı bir liste tanımlarsa, ``from package import *`` " -"ile karşılaşıldığında alınması gereken modül adlarının listesi olarak " -"alınır. Paketin yeni bir sürümü yayınlandığında bu listeyi güncel tutmak " -"paket yazarının sorumluluğundadır. Paket yazarları, paketlerinden \\* içe " -"aktarmak için bir kullanım görmezlerse, onu desteklememeye de karar " -"verebilirler. Örneğin, :file:`sound/effects/__init__.py` dosyası şu kodu " -"içerebilir::" +"Tek çözüm, paket yazarının paketin açık bir dizinini " +"sağlamasıdır. :keyword:`import` ifadesi aşağıdaki kuralı kullanır: eğer bir " +"paketin :file:`__init__.py` kodu ``__all__`` adlı bir liste tanımlarsa, " +"``from package import *`` ile karşılaşıldığında alınması gereken modül " +"adlarının listesi olarak alınır. Paketin yeni bir sürümü yayınlandığında bu " +"listeyi güncel tutmak paket yazarının sorumluluğundadır. Paket yazarları, " +"paketlerinden \\* içe aktarmak için bir kullanım görmezlerse, onu " +"desteklememeye de karar verebilirler. Örneğin, :file:`sound/effects/" +"__init__.py` dosyası şu kodu içerebilir::" #: tutorial/modules.rst:511 msgid "__all__ = [\"echo\", \"surround\", \"reverse\"]" @@ -1000,23 +1003,23 @@ msgstr "" 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 " +"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 "" -"Eğer ``__all__`` tanımlanmamışsa, ``from sound.effects import *`` ifadesi :" -"mod:`!sound.effects` paketindeki tüm alt modülleri geçerli isim alanına " -"import etmez; sadece :mod:`!sound.effects` paketinin import edildiğinden " -"emin olur (muhtemelen :file:`__init__.py` içindeki herhangi bir başlatma " -"kodunu çalıştırır) ve sonra pakette tanımlanan isimleri import eder. Bu, :" -"file:`__init__.py` tarafından tanımlanan (ve alt modülleri açıkça yüklenen) " -"tüm isimleri içerir. Ayrıca, önceki :keyword:`import` deyimleri tarafından " -"açıkça yüklenmiş olan paketin tüm alt modüllerini de içerir. Bu kodu göz " -"önünde bulundurun::" +"Eğer ``__all__`` tanımlanmamışsa, ``from sound.effects import *`` " +"ifadesi :mod:`!sound.effects` paketindeki tüm alt modülleri geçerli isim " +"alanına import etmez; sadece :mod:`!sound.effects` paketinin import " +"edildiğinden emin olur (muhtemelen :file:`__init__.py` içindeki herhangi bir " +"başlatma kodunu çalıştırır) ve sonra pakette tanımlanan isimleri import " +"eder. Bu, :file:`__init__.py` tarafından tanımlanan (ve alt modülleri " +"açıkça yüklenen) tüm isimleri içerir. Ayrıca, önceki :keyword:`import` " +"deyimleri tarafından açıkça yüklenmiş olan paketin tüm alt modüllerini de " +"içerir. Bu kodu göz önünde bulundurun::" #: tutorial/modules.rst:541 msgid "" @@ -1028,9 +1031,9 @@ msgstr "" #: tutorial/modules.rst:545 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.)" +"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 "" "Bu örnekte, :mod:`!echo` ve :mod:`!surround` modülleri, ``from...import`` " "deyimi çalıştırıldığında :mod:`!sound.effects` paketinde tanımlandıkları " @@ -1066,22 +1069,23 @@ msgstr "Paket İçi Referanslar" 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``." +"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 "" "Paketler alt paketler halinde yapılandırıldığında (örnekteki :mod:`!sound` " "paketinde olduğu gibi), kardeş paketlerin alt modüllerine başvurmak için " -"mutlak içe aktarımları kullanabilirsiniz. Örneğin, :mod:`!sound.filters." -"vocoder` modülünün :mod:`!sound.effects` paketindeki :mod:`!echo` modülünü " -"kullanması gerekiyorsa, ``from sound.effects import echo`` kullanabilir." +"mutlak içe aktarımları kullanabilirsiniz. Örneğin, :mod:`!" +"sound.filters.vocoder` modülünün :mod:`!sound.effects` paketindeki :mod:`!" +"echo` modülünü kullanması gerekiyorsa, ``from sound.effects import echo`` " +"kullanabilir." #: tutorial/modules.rst:571 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::" +"current and parent packages involved in the relative import. From " +"the :mod:`!surround` module for example, you might use::" msgstr "" "Ayrıca, içe aktarma ifadesinin ``from module import name`` formuyla göreli " "içe aktarmaları(relative import) da yazabilirsiniz. Bu içe aktarmalar, " diff --git a/tutorial/stdlib.po b/tutorial/stdlib.po index 3afebb6c2..2bd580185 100644 --- a/tutorial/stdlib.po +++ b/tutorial/stdlib.po @@ -165,13 +165,13 @@ msgstr "" #: tutorial/stdlib.rst:93 msgid "" -"When run at the command line with ``python top.py --lines=5 alpha.txt beta." -"txt``, the script sets ``args.lines`` to ``5`` and ``args.filenames`` to " -"``['alpha.txt', 'beta.txt']``." +"When run at the command line with ``python top.py --lines=5 alpha.txt " +"beta.txt``, the script sets ``args.lines`` to ``5`` and ``args.filenames`` " +"to ``['alpha.txt', 'beta.txt']``." msgstr "" "Komut satırında ``python top.py --lines=5 alpha.txt beta.txt`` " -"çalıştırıldığı zaman program, ``args.lines`` ögesini ``5`` ve ``args." -"filenames`` ögesini ``['alpha.txt', 'beta.txt']`` olarak ayarlar." +"çalıştırıldığı zaman program, ``args.lines`` ögesini ``5`` ve " +"``args.filenames`` ögesini ``['alpha.txt', 'beta.txt']`` olarak ayarlar." #: tutorial/stdlib.rst:101 msgid "Error Output Redirection and Program Termination" @@ -389,12 +389,13 @@ msgstr "Veri Sıkıştırma" #: tutorial/stdlib.rst:238 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`. ::" +"modules " +"including: :mod:`zlib`, :mod:`gzip`, :mod:`bz2`, :mod:`lzma`, :mod:`zipfile` " +"and :mod:`tarfile`. ::" msgstr "" "Genel veri arşivleme ve sıkıştırma formatları şu modüller tarafından " -"desteklenir: :mod:`zlib`, :mod:`gzip`, :mod:`bz2`, :mod:`lzma`, :mod:" -"`zipfile` ve :mod:`tarfile`. ::" +"desteklenir: :mod:`zlib`, :mod:`gzip`, :mod:`bz2`, :mod:`lzma`, :mod:`zipfile` " +"ve :mod:`tarfile`. ::" #: tutorial/stdlib.rst:242 msgid "" @@ -428,8 +429,9 @@ msgstr "" #: tutorial/stdlib.rst:264 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::" +"feature instead of the traditional approach to swapping arguments. " +"The :mod:`timeit` module quickly demonstrates a modest performance " +"advantage::" msgstr "" "Örneğin, argümanları değiştirmek için geleneksel yaklaşım yerine dizi " "paketleme ve açma özelliğini kullanmak cazip olabilir. :mod:`timeit` modülü " @@ -450,9 +452,9 @@ msgid "" "and :mod:`pstats` modules provide tools for identifying time critical " "sections in larger blocks of code." msgstr "" -":mod:`timeit` 'in ince ayrıntı düzeyinin aksine, :mod:`profile` ve :mod:" -"`pstats` modülleri, daha büyük kod bloklarında zaman açısından kritik " -"bölümleri tanımlamak için araçlar sağlar." +":mod:`timeit` 'in ince ayrıntı düzeyinin aksine, :mod:`profile` " +"ve :mod:`pstats` modülleri, daha büyük kod bloklarında zaman açısından " +"kritik bölümleri tanımlamak için araçlar sağlar." #: tutorial/stdlib.rst:282 msgid "Quality Control" @@ -567,17 +569,17 @@ 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." +"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 "" ":mod:`json` paketi, bu popüler veri değişim biçimini ayrıştırmak için sağlam " "destek sağlar. :mod:`csv` modülü, genellikle veritabanları ve elektronik " "tablolar tarafından desteklenen Virgülle-Ayrılmış Değer biçimindeki " -"dosyaların doğrudan okunmasını ve yazılmasını destekler. XML işleme :mod:" -"`xml.etree.ElementTree`, :mod:`xml.dom` ve :mod:`xml.sax` paketleri " -"tarafından desteklenir. Birlikte, bu modüller ve paketler Python " +"dosyaların doğrudan okunmasını ve yazılmasını destekler. XML " +"işleme :mod:`xml.etree.ElementTree`, :mod:`xml.dom` ve :mod:`xml.sax` " +"paketleri tarafından desteklenir. Birlikte, bu modüller ve paketler Python " "uygulamaları ve diğer araçlar arasındaki veri değişimini büyük ölçüde " "basitleştirir." @@ -593,8 +595,8 @@ msgstr "" #: tutorial/stdlib.rst:357 msgid "" -"Internationalization is supported by a number of modules including :mod:" -"`gettext`, :mod:`locale`, and the :mod:`codecs` package." +"Internationalization is supported by a number of modules " +"including :mod:`gettext`, :mod:`locale`, and the :mod:`codecs` package." msgstr "" "Uluslararasılaştırma :mod:`gettext`, :mod:`locale` ve :mod:`codecs` paketi " "dahil olmak üzere bir dizi modül tarafından desteklenir." diff --git a/tutorial/stdlib2.po b/tutorial/stdlib2.po index e83be328f..1efa1b220 100644 --- a/tutorial/stdlib2.po +++ b/tutorial/stdlib2.po @@ -165,16 +165,16 @@ msgstr "" 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::" +"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 "" ":meth:`~string.Template.substitute` yöntemi, bir sözlükte veya anahtar " "sözcük bağımsız değişkeninde yer tutucu sağlandığında :exc:`KeyError` " "öğesini yükseltir. Adres mektup birleştirme stili uygulamalar için, " -"kullanıcı tarafından sağlanan veriler eksik olabilir ve :meth:`~string." -"Template.safe_substitute` yöntemi daha uygun olabilir --- veriler eksikse " -"yer tutucuları değiştirmez::" +"kullanıcı tarafından sağlanan veriler eksik olabilir " +"ve :meth:`~string.Template.safe_substitute` yöntemi daha uygun olabilir --- " +"veriler eksikse yer tutucuları değiştirmez::" #: tutorial/stdlib2.rst:94 msgid "" @@ -239,13 +239,13 @@ msgstr "İkili Veri Kaydı Düzenleriyle Çalışma" #: tutorial/stdlib2.rst:136 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::" +"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 "" ":mod:`struct` modülü, değişken uzunluklu ikili kayıt formatlarıyla çalışmak " "için :func:`~struct.pack` ve :func:`~struct.unpack` işlevlerini sağlar. " @@ -300,9 +300,9 @@ 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 "" -"Aşağıdaki kod, ana program çalışmaya devam ederken üst düzey :mod:" -"`threading` modülünün görevleri arka planda nasıl çalıştırabileceğini " -"gösterir::" +"Aşağıdaki kod, ana program çalışmaya devam ederken üst " +"düzey :mod:`threading` modülünün görevleri arka planda nasıl " +"çalıştırabileceğini gösterir::" #: tutorial/stdlib2.rst:177 msgid "" @@ -366,8 +366,8 @@ msgstr "Günlükleme" #: tutorial/stdlib2.rst:216 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``::" +"system. At its simplest, log messages are sent to a file or to " +"``sys.stderr``::" msgstr "" ":mod:`logging` modülü, tam özellikli ve esnek bir kayıt sistemi sunar. En " "basit haliyle, günlük mesajları bir dosyaya veya ``sys.stderr`` adresine " @@ -399,16 +399,16 @@ 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`." +"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 "" "Varsayılan olarak, bilgi ve hata ayıklama mesajları bastırılır ve çıktı " "standart hataya gönderilir. Diğer çıktı seçenekleri, mesajları e-posta, " "datagramlar, yuvalar veya bir HTTP Sunucusuna yönlendirmeyi içerir. Yeni " -"filtreler mesaj önceliğine göre farklı yönlendirme seçebilir: :const:" -"`~logging.DEBUG`, :const:`~logging.INFO`, :const:`~logging.WARNING`, :const:" -"`~logging.ERROR` , ve :const:`~logging.CRITICAL`." +"filtreler mesaj önceliğine göre farklı yönlendirme " +"seçebilir: :const:`~logging.DEBUG`, :const:`~logging.INFO`, :const:`~logging.WARNING`, :const:`~logging.ERROR` , " +"ve :const:`~logging.CRITICAL`." #: tutorial/stdlib2.rst:241 msgid "" @@ -529,9 +529,9 @@ msgid "" "queues and breadth first tree searches::" msgstr "" ":mod:`collections` modülü, eklemelerin daha hızlı olduğu ve sol taraftan " -"açılan ancak ortada daha yavaş aramaların olduğu bir liste gibi bir :class:" -"`~collections.deque()` nesnesi sağlar. Bu nesneler, kuyruklar uygulamak ve " -"ilk ağaç aramalarını genişletmek için çok uygundur::" +"açılan ancak ortada daha yavaş aramaların olduğu bir liste gibi " +"bir :class:`~collections.deque()` nesnesi sağlar. Bu nesneler, kuyruklar " +"uygulamak ve ilk ağaç aramalarını genişletmek için çok uygundur::" #: tutorial/stdlib2.rst:314 msgid "" @@ -606,9 +606,10 @@ msgid "" "decimal floating-point arithmetic. Compared to the built-in :class:`float` " "implementation of binary floating point, the class is especially helpful for" msgstr "" -":mod:`decimal` modülü, ondalık kayan nokta aritmetiği için bir :class:" -"`~decimal.Decimal` veri tipi sunar. İkili kayan noktanın yerleşik :class:" -"`float` uygulamasıyla karşılaştırıldığında, sınıf özellikle için yararlıdır" +":mod:`decimal` modülü, ondalık kayan nokta aritmetiği için " +"bir :class:`~decimal.Decimal` veri tipi sunar. İkili kayan noktanın " +"yerleşik :class:`float` uygulamasıyla karşılaştırıldığında, sınıf özellikle " +"için yararlıdır" #: tutorial/stdlib2.rst:362 msgid "" diff --git a/tutorial/venv.po b/tutorial/venv.po index 5fa0b3714..b6111eeab 100644 --- a/tutorial/venv.po +++ b/tutorial/venv.po @@ -85,10 +85,11 @@ msgstr "Sanal Ortamlar Oluşturma" #: tutorial/venv.rst:38 #, fuzzy msgid "" -"The module used to create and manage virtual environments is called :mod:" -"`venv`. :mod:`venv` will install the Python version from which the command " -"was run (as reported by the :option:`--version` option). For instance, " -"executing the command with ``python3.12`` will install version 3.12." +"The module used to create and manage virtual environments is " +"called :mod:`venv`. :mod:`venv` will install the Python version from which " +"the command was run (as reported by the :option:`--version` option). For " +"instance, executing the command with ``python3.12`` will install version " +"3.12." msgstr "" "Sanal ortamlar oluşturmak ve yönetmek için kullanılan modüle :mod:`venv` " "denir. :mod:`venv` genellikle mevcut olan en son Python sürümünü yükler. " @@ -101,8 +102,8 @@ msgid "" "place it, and run the :mod:`venv` module as a script with the directory " "path::" msgstr "" -"Sanal ortam oluşturmak için, yerleştirmek istediğiniz dizine karar verin ve :" -"mod:`venv` modülünü dizin yolu ile bir komut dosyası olarak çalıştırın::" +"Sanal ortam oluşturmak için, yerleştirmek istediğiniz dizine karar verin " +"ve :mod:`venv` modülünü dizin yolu ile bir komut dosyası olarak çalıştırın::" #: tutorial/venv.rst:47 msgid "python -m venv tutorial-env" @@ -157,9 +158,10 @@ msgid "" "or :program:`fish` shells, there are alternate ``activate.csh`` and " "``activate.fish`` scripts you should use instead.)" msgstr "" -"(Bu komut dosyası bash kabuğu için yazılmıştır. Eğer :program:`csh` veya :" -"program:`fish` kabuklarını kullanıyorsanız, bunun yerine ``activate.csh`` " -"veya ``activate.fish`` komut dosyalarını kullanmanız gerekmektedir.)" +"(Bu komut dosyası bash kabuğu için yazılmıştır. Eğer :program:`csh` " +"veya :program:`fish` kabuklarını kullanıyorsanız, bunun yerine " +"``activate.csh`` veya ``activate.fish`` komut dosyalarını kullanmanız " +"gerekmektedir.)" #: tutorial/venv.rst:74 msgid "" @@ -204,10 +206,10 @@ msgstr "Paketleri pip ile Yönetme" #: tutorial/venv.rst:100 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." +"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." msgstr "" ":program:`pip` adlı bir program kullanarak paketleri yükleyebilir, " "yükseltebilir ve kaldırabilirsiniz. Varsayılan olarak ``pip``, `Python " @@ -220,9 +222,9 @@ msgid "" "etc. (Consult the :ref:`installing-index` guide for complete documentation " "for ``pip``.)" msgstr "" -"``pip`` bir dizi alt komut içerir: \"install\" (yükle), " -"\"uninstall\" (kaldır), \"freeze\" (dondur), vb. (``pip`` için eksiksiz " -"dokümantasyon için :ref:`installing-index` rehberine bakın.)" +"``pip`` bir dizi alt komut içerir: \"install\" (yükle), \"uninstall\" " +"(kaldır), \"freeze\" (dondur), vb. (``pip`` için eksiksiz dokümantasyon " +"için :ref:`installing-index` rehberine bakın.)" #: tutorial/venv.rst:109 msgid "" diff --git a/tutorial/whatnow.po b/tutorial/whatnow.po index 4e4f73293..05330e877 100644 --- a/tutorial/whatnow.po +++ b/tutorial/whatnow.po @@ -149,12 +149,12 @@ msgid "" "new features, and announcing new modules. Mailing list archives are " "available at https://mail.python.org/pipermail/." msgstr "" -"Python ile ilgili sorular ve sorun raporları için haber grubu :newsgroup:" -"`comp.lang.python` adresine gönderebilir veya bunları python-list@python.org " -"posta listesine gönderebilirsiniz. Haber grubu ve posta listesi aynı ağ " -"içinde olduğundan, birine gönderilen iletiler otomatik olarak diğerine " -"iletilir. Günde yüzlerce gönderi geliyor, sorular soruluyor (ve " -"yanıtlanıyor), yeni özellikler öneriliyor ve yeni modüller duyuruluyor. " +"Python ile ilgili sorular ve sorun raporları için haber " +"grubu :newsgroup:`comp.lang.python` adresine gönderebilir veya bunları " +"python-list@python.org posta listesine gönderebilirsiniz. Haber grubu ve " +"posta listesi aynı ağ içinde olduğundan, birine gönderilen iletiler otomatik " +"olarak diğerine iletilir. Günde yüzlerce gönderi geliyor, sorular soruluyor " +"(ve yanıtlanıyor), yeni özellikler öneriliyor ve yeni modüller duyuruluyor. " "Posta listesi arşivleri için https://mail.python.org/pipermail/." #: tutorial/whatnow.rst:64 diff --git a/using/cmdline.po b/using/cmdline.po index 92a6f0c9b..b4fe6d4ca 100644 --- a/using/cmdline.po +++ b/using/cmdline.po @@ -28,8 +28,8 @@ msgstr "" #: using/cmdline.rst:16 msgid "" -"Other implementations' command line schemes may differ. See :ref:" -"`implementations` for further resources." +"Other implementations' command line schemes may differ. " +"See :ref:`implementations` for further resources." msgstr "" #: using/cmdline.rst:23 @@ -121,9 +121,9 @@ msgstr "" #: 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)." +"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 "" #: using/cmdline.rst:73 @@ -173,9 +173,10 @@ msgstr "" #: using/cmdline.rst:104 msgid "" -":option:`-I` option can be used to run the script in isolated mode where :" -"data:`sys.path` contains neither the current directory nor the user's site-" -"packages directory. All ``PYTHON*`` environment variables are ignored, too." +":option:`-I` option can be used to run the script in isolated mode " +"where :data:`sys.path` contains neither the current directory nor the user's " +"site-packages directory. All ``PYTHON*`` environment variables are ignored, " +"too." msgstr "" #: using/cmdline.rst:109 @@ -225,8 +226,8 @@ msgstr "" #: using/cmdline.rst:136 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`." +"\"`` and the current directory will be added to the start " +"of :data:`sys.path`." msgstr "" #: using/cmdline.rst:723 @@ -265,9 +266,10 @@ msgstr "" #: using/cmdline.rst:162 msgid "" -":option:`-I` option can be used to run the script in isolated mode where :" -"data:`sys.path` contains neither the script's directory nor the user's site-" -"packages directory. All ``PYTHON*`` environment variables are ignored, too." +":option:`-I` option can be used to run the script in isolated mode " +"where :data:`sys.path` contains neither the script's directory nor the " +"user's site-packages directory. All ``PYTHON*`` environment variables are " +"ignored, too." msgstr "" #: using/cmdline.rst:167 @@ -349,10 +351,11 @@ msgstr "" #: using/cmdline.rst:245 msgid "" -"Issue a warning when converting :class:`bytes` or :class:`bytearray` to :" -"class:`str` without specifying encoding or 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`)." +"Issue a warning when converting :class:`bytes` or :class:`bytearray` " +"to :class:`str` without specifying encoding or 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 "" #: using/cmdline.rst:250 @@ -384,8 +387,8 @@ msgstr "" #: using/cmdline.rst:275 msgid "" -"Turn on parser debugging output (for expert only). See also the :envvar:" -"`PYTHONDEBUG` environment variable." +"Turn on parser debugging output (for expert only). See also " +"the :envvar:`PYTHONDEBUG` environment variable." msgstr "" #: using/cmdline.rst:278 @@ -396,8 +399,8 @@ msgstr "" #: using/cmdline.rst:284 msgid "" -"Ignore all ``PYTHON*`` environment variables, e.g. :envvar:`PYTHONPATH` and :" -"envvar:`PYTHONHOME`, that might be set." +"Ignore all ``PYTHON*`` environment variables, e.g. :envvar:`PYTHONPATH` " +"and :envvar:`PYTHONHOME`, that might be set." msgstr "" #: using/cmdline.rst:287 @@ -408,8 +411,8 @@ msgstr "" 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." +"when :data:`sys.stdin` does not appear to be a terminal. " +"The :envvar:`PYTHONSTARTUP` file is not read." msgstr "" #: using/cmdline.rst:297 @@ -434,10 +437,10 @@ msgstr "" #: using/cmdline.rst:316 msgid "" -"Remove assert statements and any code conditional on the value of :const:" -"`__debug__`. Augment the filename for compiled (:term:`bytecode`) files by " -"adding ``.opt-1`` before the ``.pyc`` extension (see :pep:`488`). See also :" -"envvar:`PYTHONOPTIMIZE`." +"Remove assert statements and any code conditional on the value " +"of :const:`__debug__`. Augment the filename for compiled (:term:`bytecode`) " +"files by adding ``.opt-1`` before the ``.pyc`` extension (see :pep:`488`). " +"See also :envvar:`PYTHONOPTIMIZE`." msgstr "" #: using/cmdline.rst:331 @@ -486,9 +489,9 @@ msgstr "" #: using/cmdline.rst:361 msgid "" -"Turn on hash randomization. This option only has an effect if the :envvar:" -"`PYTHONHASHSEED` environment variable is set to ``0``, since hash " -"randomization is enabled by default." +"Turn on hash randomization. This option only has an effect if " +"the :envvar:`PYTHONHASHSEED` environment variable is set to ``0``, since " +"hash randomization is enabled by default." msgstr "" #: using/cmdline.rst:365 @@ -520,8 +523,8 @@ msgstr "" #: using/cmdline.rst:387 msgid "" -"Don't add the :data:`user site-packages directory ` to :data:" -"`sys.path`." +"Don't add the :data:`user site-packages directory ` " +"to :data:`sys.path`." msgstr "" #: using/cmdline.rst:390 @@ -536,8 +539,8 @@ msgstr "" 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)." +"manipulations if :mod:`site` is explicitly imported later " +"(call :func:`site.main` if you want them to be triggered)." msgstr "" #: using/cmdline.rst:407 @@ -557,8 +560,8 @@ msgstr "" #: using/cmdline.rst:418 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 " +"(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." msgstr "" @@ -653,17 +656,17 @@ msgstr "" #: using/cmdline.rst:477 msgid "" "Multiple :option:`-W` options can 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)." +"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 "" #: using/cmdline.rst:482 msgid "" "Warnings can also be controlled using the :envvar:`PYTHONWARNINGS` " -"environment variable and from within a Python program using the :mod:" -"`warnings` module. For example, the :func:`warnings.filterwarnings` function " -"can be used to use a regular expression on the warning message." +"environment variable and from within a Python program using " +"the :mod:`warnings` module. For example, the :func:`warnings.filterwarnings` " +"function can be used to use a regular expression on the warning message." msgstr "" #: using/cmdline.rst:856 @@ -686,8 +689,8 @@ msgstr "" #: using/cmdline.rst:502 msgid "" -"``-X faulthandler`` to enable :mod:`faulthandler`. See also :envvar:" -"`PYTHONFAULTHANDLER`." +"``-X faulthandler`` to enable :mod:`faulthandler`. See " +"also :envvar:`PYTHONFAULTHANDLER`." msgstr "" #: using/cmdline.rst:507 @@ -700,18 +703,19 @@ msgstr "" #: using/cmdline.rst:514 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 :func:`tracemalloc.start` and :" -"envvar:`PYTHONTRACEMALLOC` for more information." +"``-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 :func:`tracemalloc.start` and :envvar:`PYTHONTRACEMALLOC` for more " +"information." msgstr "" #: using/cmdline.rst:523 msgid "" "``-X int_max_str_digits`` configures the :ref:`integer string conversion " -"length limitation `. See also :envvar:" -"`PYTHONINTMAXSTRDIGITS`." +"length limitation `. See " +"also :envvar:`PYTHONINTMAXSTRDIGITS`." msgstr "" #: using/cmdline.rst:529 @@ -740,15 +744,15 @@ msgstr "" #: using/cmdline.rst:550 msgid "" "``-X pycache_prefix=PATH`` enables writing ``.pyc`` files to a parallel tree " -"rooted at the given directory instead of to the code tree. See also :envvar:" -"`PYTHONPYCACHEPREFIX`." +"rooted at the given directory instead of to the code tree. See " +"also :envvar:`PYTHONPYCACHEPREFIX`." msgstr "" #: using/cmdline.rst:556 msgid "" "``-X warn_default_encoding`` issues a :class:`EncodingWarning` when the " -"locale-specific default encoding is used for opening files. See also :envvar:" -"`PYTHONWARNDEFAULTENCODING`." +"locale-specific default encoding is used for opening files. See " +"also :envvar:`PYTHONWARNDEFAULTENCODING`." msgstr "" #: using/cmdline.rst:562 @@ -757,8 +761,8 @@ msgid "" "location information (end line, start column offset and end column offset) " "to every instruction in code objects. This is useful when smaller code " "objects and pyc files are desired as well as suppressing the extra visual " -"location indicators when the interpreter displays tracebacks. See also :" -"envvar:`PYTHONNODEBUGRANGES`." +"location indicators when the interpreter displays tracebacks. See " +"also :envvar:`PYTHONNODEBUGRANGES`." msgstr "" #: using/cmdline.rst:571 @@ -783,8 +787,8 @@ msgstr "" #: using/cmdline.rst:589 msgid "" -"It also allows passing arbitrary values and retrieving them through the :" -"data:`sys._xoptions` dictionary." +"It also allows passing arbitrary values and retrieving them through " +"the :data:`sys._xoptions` dictionary." msgstr "" #: using/cmdline.rst:594 @@ -818,10 +822,10 @@ msgstr "" #: using/cmdline.rst:623 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`." +"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 "" #: using/cmdline.rst:629 @@ -834,8 +838,8 @@ msgstr "" #: using/cmdline.rst:636 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-" +"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 "" @@ -855,8 +859,8 @@ msgstr "" #: using/cmdline.rst:649 msgid "" -"An additional directory will be inserted in the search path in front of :" -"envvar:`PYTHONPATH` as described above under :ref:`using-on-interface-" +"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 "" @@ -869,8 +873,8 @@ msgstr "" #: using/cmdline.rst:665 msgid "" -"If this is set to a non-empty string, it overrides the :data:`sys." -"platlibdir` value." +"If this is set to a non-empty string, it overrides " +"the :data:`sys.platlibdir` value." msgstr "" #: using/cmdline.rst:673 @@ -892,9 +896,9 @@ msgstr "" #: using/cmdline.rst:688 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." +"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 "" #: using/cmdline.rst:695 @@ -904,15 +908,15 @@ msgid "" "by the default implementation of :func:`sys.breakpointhook` which itself is " "called by built-in :func:`breakpoint`. If not set, or set to the empty " "string, it is equivalent to the value \"pdb.set_trace\". Setting this to " -"the string \"0\" causes the default implementation of :func:`sys." -"breakpointhook` to do nothing but return immediately." +"the string \"0\" causes the default implementation " +"of :func:`sys.breakpointhook` to do nothing but return immediately." msgstr "" #: using/cmdline.rst:707 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." +"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 "" #: using/cmdline.rst:711 @@ -923,8 +927,8 @@ msgstr "" #: using/cmdline.rst:717 msgid "" -"If this is set to a non-empty string it is equivalent to specifying the :" -"option:`-i` option." +"If this is set to a non-empty string it is equivalent to specifying " +"the :option:`-i` option." msgstr "" #: using/cmdline.rst:720 @@ -939,15 +943,15 @@ msgstr "" #: using/cmdline.rst:731 msgid "" -"If this is set to a non-empty string it is equivalent to specifying the :" -"option:`-u` option." +"If this is set to a non-empty string it is equivalent to specifying " +"the :option:`-u` option." msgstr "" #: using/cmdline.rst:737 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." +"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 "" #: using/cmdline.rst:744 @@ -1039,8 +1043,8 @@ msgstr "" #: using/cmdline.rst:821 msgid "" "Defines the :data:`user base directory `, which is used to " -"compute the path of the :data:`user site-packages directory ` and :ref:`installation paths ` for " +"compute the path of the :data:`user site-packages directory " +"` and :ref:`installation paths ` for " "``python -m pip install --user``." msgstr "" @@ -1070,11 +1074,11 @@ msgstr "" #: using/cmdline.rst:862 msgid "" -"If this environment variable is set to a non-empty string, :func:" -"`faulthandler.enable` is called at startup: install a handler for :const:" -"`~signal.SIGSEGV`, :const:`~signal.SIGFPE`, :const:`~signal.SIGABRT`, :const:" -"`~signal.SIGBUS` and :const:`~signal.SIGILL` signals to dump the Python " -"traceback. This is equivalent to :option:`-X` ``faulthandler`` option." +"If this environment variable is set to a non-empty " +"string, :func:`faulthandler.enable` is called at startup: install a handler " +"for :const:`~signal.SIGSEGV`, :const:`~signal.SIGFPE`, :const:`~signal.SIGABRT`, :const:`~signal.SIGBUS` " +"and :const:`~signal.SIGILL` signals to dump the Python traceback. This is " +"equivalent to :option:`-X` ``faulthandler`` option." msgstr "" #: using/cmdline.rst:874 @@ -1096,8 +1100,8 @@ msgstr "" #: using/cmdline.rst:896 msgid "" -"If this environment variable is set to a non-empty string, enable the :ref:" -"`debug mode ` of the :mod:`asyncio` module." +"If this environment variable is set to a non-empty string, enable " +"the :ref:`debug mode ` of the :mod:`asyncio` module." msgstr "" #: using/cmdline.rst:904 @@ -1117,15 +1121,15 @@ msgstr "" #: using/cmdline.rst:910 msgid "" "``malloc``: use the :c:func:`malloc` function of the C library for all " -"domains (:c:macro:`PYMEM_DOMAIN_RAW`, :c:macro:`PYMEM_DOMAIN_MEM`, :c:macro:" -"`PYMEM_DOMAIN_OBJ`)." +"domains " +"(:c:macro:`PYMEM_DOMAIN_RAW`, :c:macro:`PYMEM_DOMAIN_MEM`, :c:macro:`PYMEM_DOMAIN_OBJ`)." msgstr "" #: using/cmdline.rst:913 msgid "" -"``pymalloc``: use the :ref:`pymalloc allocator ` for :c:macro:" -"`PYMEM_DOMAIN_MEM` and :c:macro:`PYMEM_DOMAIN_OBJ` domains and use the :c:" -"func:`malloc` function for the :c:macro:`PYMEM_DOMAIN_RAW` domain." +"``pymalloc``: use the :ref:`pymalloc allocator ` " +"for :c:macro:`PYMEM_DOMAIN_MEM` and :c:macro:`PYMEM_DOMAIN_OBJ` domains and " +"use the :c:func:`malloc` function for the :c:macro:`PYMEM_DOMAIN_RAW` domain." msgstr "" #: using/cmdline.rst:917 @@ -1152,9 +1156,9 @@ msgstr "" #: using/cmdline.rst:932 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." +"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 "" #: using/cmdline.rst:936 @@ -1180,8 +1184,8 @@ msgstr "" #: using/cmdline.rst:952 msgid "" -"This may also be enabled at runtime with :func:`sys." -"_enablelegacywindowsfsencoding`." +"This may also be enabled at runtime " +"with :func:`sys._enablelegacywindowsfsencoding`." msgstr "" #: using/cmdline.rst:969 using/cmdline.rst:1020 @@ -1251,11 +1255,12 @@ msgstr "" #: using/cmdline.rst:1002 msgid "" "Configuring one of these locales (either explicitly or via the above " -"implicit locale coercion) automatically enables the ``surrogateescape`` :ref:" -"`error handler ` for :data:`sys.stdin` and :data:`sys." -"stdout` (:data:`sys.stderr` continues to use ``backslashreplace`` as it does " -"in any other locale). This stream handling behavior can be overridden using :" -"envvar:`PYTHONIOENCODING` as usual." +"implicit locale coercion) automatically enables the " +"``surrogateescape`` :ref:`error handler ` " +"for :data:`sys.stdin` and :data:`sys.stdout` (:data:`sys.stderr` continues " +"to use ``backslashreplace`` as it does in any other locale). This stream " +"handling behavior can be overridden using :envvar:`PYTHONIOENCODING` as " +"usual." msgstr "" #: using/cmdline.rst:1009 @@ -1281,10 +1286,10 @@ msgstr "" #: using/cmdline.rst:1028 msgid "" -"If this environment variable is set to a non-empty string, enable :ref:" -"`Python Development Mode `, introducing additional runtime checks " -"that are too expensive to be enabled by default. This is equivalent to " -"setting the :option:`-X` ``dev`` option." +"If this environment variable is set to a non-empty string, " +"enable :ref:`Python Development Mode `, introducing additional " +"runtime checks that are too expensive to be enabled by default. This is " +"equivalent to setting the :option:`-X` ``dev`` option." msgstr "" #: using/cmdline.rst:1037 @@ -1303,8 +1308,8 @@ msgstr "" #: using/cmdline.rst:1048 msgid "" -"If this environment variable is set to a non-empty string, issue a :class:" -"`EncodingWarning` when the locale-specific default encoding is used." +"If this environment variable is set to a non-empty string, issue " +"a :class:`EncodingWarning` when the locale-specific default encoding is used." msgstr "" #: using/cmdline.rst:1051 @@ -1332,8 +1337,8 @@ msgstr "" #: using/cmdline.rst:1072 msgid "" -"See also the :option:`-X perf <-X>` command-line option and :ref:" -"`perf_profiling`." +"See also the :option:`-X perf <-X>` command-line option " +"and :ref:`perf_profiling`." msgstr "" #: using/cmdline.rst:1079 diff --git a/using/configure.po b/using/configure.po index b1c0bfa8b..70689083a 100644 --- a/using/configure.po +++ b/using/configure.po @@ -38,8 +38,8 @@ msgstr "" #: using/configure.rst:17 msgid "" "Support for `IEEE 754 `_ floating-" -"point numbers and `floating-point Not-a-Number (NaN) `_." +"point numbers and `floating-point Not-a-Number (NaN) `_." msgstr "" #: using/configure.rst:21 @@ -164,14 +164,14 @@ msgstr "" #: using/configure.rst:97 msgid "" -"See the :meth:`sqlite3.Connection.enable_load_extension` method of the :mod:" -"`sqlite3` module." +"See the :meth:`sqlite3.Connection.enable_load_extension` method of " +"the :mod:`sqlite3` module." msgstr "" #: using/configure.rst:104 msgid "" -"Disable IPv6 support (enabled by default if supported), see the :mod:" -"`socket` module." +"Disable IPv6 support (enabled by default if supported), see " +"the :mod:`socket` module." msgstr "" #: using/configure.rst:109 @@ -197,15 +197,15 @@ msgstr "" #: using/configure.rst:121 msgid "" "The default suffix is ``.exe`` on Windows and macOS (``python.exe`` " -"executable), ``.js`` on Emscripten node, ``.html`` on Emscripten browser, ``." -"wasm`` on WASI, and an empty string on other platforms (``python`` " +"executable), ``.js`` on Emscripten node, ``.html`` on Emscripten browser, " +"``.wasm`` on WASI, and an empty string on other platforms (``python`` " "executable)." msgstr "" #: using/configure.rst:126 msgid "" -"The default suffix on WASM platform is one of ``.js``, ``.html`` or ``." -"wasm``." +"The default suffix on WASM platform is one of ``.js``, ``.html`` or " +"``.wasm``." msgstr "" #: using/configure.rst:132 @@ -294,8 +294,8 @@ msgstr "" msgid "" "Some Linux distribution packaging policies recommend against bundling " "dependencies. For example, Fedora installs wheel packages in the ``/usr/" -"share/python-wheels/`` directory and don't install the :mod:`!ensurepip." -"_bundled` package." +"share/python-wheels/`` directory and don't install the :mod:`!" +"ensurepip._bundled` package." msgstr "" #: using/configure.rst:199 @@ -367,8 +367,8 @@ msgstr "" #: using/configure.rst:253 msgid "" -"Install architecture-independent files in PREFIX. On Unix, it defaults to :" -"file:`/usr/local`." +"Install architecture-independent files in PREFIX. On Unix, it defaults " +"to :file:`/usr/local`." msgstr "" #: using/configure.rst:256 @@ -393,8 +393,8 @@ msgstr "" #: using/configure.rst:269 msgid "" -"Don't build nor install test modules, like the :mod:`test` package or the :" -"mod:`!_testcapi` extension module (built and installed by default)." +"Don't build nor install test modules, like the :mod:`test` package or " +"the :mod:`!_testcapi` extension module (built and installed by default)." msgstr "" #: using/configure.rst:276 @@ -514,10 +514,10 @@ msgstr "" #: using/configure.rst:361 msgid "" -"The :envvar:`!BOLT_INSTRUMENT_FLAGS` and :envvar:`!BOLT_APPLY_FLAGS` :" -"program:`configure` variables can be defined to override the default set of " -"arguments for :program:`llvm-bolt` to instrument and apply BOLT data to " -"binaries, respectively." +"The :envvar:`!BOLT_INSTRUMENT_FLAGS` and :envvar:`!" +"BOLT_APPLY_FLAGS` :program:`configure` variables can be defined to override " +"the default set of arguments for :program:`llvm-bolt` to instrument and " +"apply BOLT data to binaries, respectively." msgstr "" #: using/configure.rst:370 @@ -663,8 +663,8 @@ msgstr "" #: using/configure.rst:440 msgid "" "Release builds and debug builds are now ABI compatible: defining the " -"``Py_DEBUG`` macro no longer implies the ``Py_TRACE_REFS`` macro (see the :" -"option:`--with-trace-refs` option), which introduces the only ABI " +"``Py_DEBUG`` macro no longer implies the ``Py_TRACE_REFS`` macro (see " +"the :option:`--with-trace-refs` option), which introduces the only ABI " "incompatibility." msgstr "" @@ -973,8 +973,8 @@ msgstr "" #: using/configure.rst:673 msgid "" -"Specify the name for the python framework on macOS only valid when :option:" -"`--enable-framework` is set (default: ``Python``)." +"Specify the name for the python framework on macOS only valid " +"when :option:`--enable-framework` is set (default: ``Python``)." msgstr "" #: using/configure.rst:678 @@ -1053,8 +1053,8 @@ msgstr "" #: using/configure.rst:730 msgid "" -":file:`Modules/Setup`: C extensions built by the Makefile using :file:" -"`Module/makesetup` shell script;" +":file:`Modules/Setup`: C extensions built by the Makefile " +"using :file:`Module/makesetup` shell script;" msgstr "" #: using/configure.rst:734 @@ -1162,8 +1162,8 @@ msgstr "" msgid "" ">>> import _asyncio\n" ">>> _asyncio\n" -"\n" +"\n" ">>> _asyncio.__file__\n" "'/usr/lib64/python3.9/lib-dynload/_asyncio.cpython-39-x86_64-linux-gnu.so'" msgstr "" @@ -1178,9 +1178,10 @@ msgstr "" #: using/configure.rst:796 msgid "" -"The :c:macro:`!PyAPI_FUNC()`, :c:macro:`!PyAPI_DATA()` and :c:macro:" -"`PyMODINIT_FUNC` macros of :file:`Include/exports.h` are defined differently " -"depending if the ``Py_BUILD_CORE_MODULE`` macro is defined:" +"The :c:macro:`!PyAPI_FUNC()`, :c:macro:`!PyAPI_DATA()` " +"and :c:macro:`PyMODINIT_FUNC` macros of :file:`Include/exports.h` are " +"defined differently depending if the ``Py_BUILD_CORE_MODULE`` macro is " +"defined:" msgstr "" #: using/configure.rst:800 @@ -1237,8 +1238,8 @@ msgstr "" #: using/configure.rst:840 msgid "" -"Default: ``$(BASECPPFLAGS) -I. -I$(srcdir)/Include $(CONFIGURE_CPPFLAGS) " -"$(CPPFLAGS)``." +"Default: ``$(BASECPPFLAGS) -I. -I$(srcdir)/Include $(CONFIGURE_CPPFLAGS) $" +"(CPPFLAGS)``." msgstr "" #: using/configure.rst:845 @@ -1268,8 +1269,8 @@ msgstr "" #: using/configure.rst:865 msgid "" ":envvar:`CFLAGS_NODIST` is used for building the interpreter and stdlib C " -"extensions. Use it when a compiler flag should *not* be part of :envvar:" -"`CFLAGS` once Python is installed (:gh:`65320`)." +"extensions. Use it when a compiler flag should *not* be part " +"of :envvar:`CFLAGS` once Python is installed (:gh:`65320`)." msgstr "" #: using/configure.rst:869 @@ -1279,8 +1280,9 @@ msgstr "" #: using/configure.rst:871 msgid "" "the compiler flag ``-I`` (for setting the search path for include files). " -"The ``-I`` flags are processed from left to right, and any flags in :envvar:" -"`CFLAGS` would take precedence over user- and package-supplied ``-I`` flags." +"The ``-I`` flags are processed from left to right, and any flags " +"in :envvar:`CFLAGS` would take precedence over user- and package-supplied ``-" +"I`` flags." msgstr "" #: using/configure.rst:876 @@ -1342,8 +1344,8 @@ msgstr "" #: using/configure.rst:936 msgid "" -"Default: ``$(BASECFLAGS) $(OPT) $(CONFIGURE_CFLAGS) $(CFLAGS) " -"$(EXTRA_CFLAGS)``." +"Default: ``$(BASECFLAGS) $(OPT) $(CONFIGURE_CFLAGS) $(CFLAGS) $" +"(EXTRA_CFLAGS)``." msgstr "" #: using/configure.rst:940 @@ -1358,8 +1360,8 @@ msgstr "" #: using/configure.rst:948 msgid "" -"Default: ``$(PY_CFLAGS) $(PY_CFLAGS_NODIST) $(PY_CPPFLAGS) " -"$(CFLAGSFORSHARED)``." +"Default: ``$(PY_CFLAGS) $(PY_CFLAGS_NODIST) $(PY_CPPFLAGS) $" +"(CFLAGSFORSHARED)``." msgstr "" #: using/configure.rst:954 @@ -1411,9 +1413,9 @@ msgstr "" #: using/configure.rst:995 msgid "" -":envvar:`LDFLAGS_NODIST` is used in the same manner as :envvar:" -"`CFLAGS_NODIST`. Use it when a linker flag should *not* be part of :envvar:" -"`LDFLAGS` once Python is installed (:gh:`65320`)." +":envvar:`LDFLAGS_NODIST` is used in the same manner " +"as :envvar:`CFLAGS_NODIST`. Use it when a linker flag should *not* be part " +"of :envvar:`LDFLAGS` once Python is installed (:gh:`65320`)." msgstr "" #: using/configure.rst:999 @@ -1423,8 +1425,9 @@ msgstr "" #: using/configure.rst:1001 msgid "" "the compiler flag ``-L`` (for setting the search path for libraries). The ``-" -"L`` flags are processed from left to right, and any flags in :envvar:" -"`LDFLAGS` would take precedence over user- and package-supplied ``-L`` flags." +"L`` flags are processed from left to right, and any flags " +"in :envvar:`LDFLAGS` would take precedence over user- and package-supplied " +"``-L`` flags." msgstr "" #: using/configure.rst:1008 diff --git a/using/mac.po b/using/mac.po index 57cb965d1..5b51894ed 100644 --- a/using/mac.po +++ b/using/mac.po @@ -73,14 +73,14 @@ msgstr "" #: using/mac.rst:44 msgid "" -"On macOS 10.8-12.3, 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." +"On macOS 10.8-12.3, 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 "" #: using/mac.rst:52 @@ -111,12 +111,13 @@ msgstr "" 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. macOS comes " -"with a number of standard Unix command line editors, :program:`vim` :program:" -"`nano` among them. If you want a more Mac-like editor, :program:`BBEdit` " -"from Bare Bones Software (see https://www.barebones.com/products/bbedit/" -"index.html) are good choices, as is :program:`TextMate` (see https://" -"macromates.com). Other editors include :program:`MacVim` (https://macvim." -"org) and :program:`Aquamacs` (https://aquamacs.org)." +"with a number of standard Unix command line " +"editors, :program:`vim` :program:`nano` among them. If you want a more Mac-" +"like editor, :program:`BBEdit` from Bare Bones Software (see https://" +"www.barebones.com/products/bbedit/index.html) are good choices, as " +"is :program:`TextMate` (see https://macromates.com). Other editors " +"include :program:`MacVim` (https://macvim.org) and :program:`Aquamacs` " +"(https://aquamacs.org)." msgstr "" #: using/mac.rst:77 @@ -150,8 +151,8 @@ msgstr "" msgid "" "With older versions of Python, there is one macOS 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." +"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 "" #: using/mac.rst:101 @@ -165,12 +166,13 @@ msgstr "" #: using/mac.rst:107 msgid "" -"Python on macOS 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 Q&A QA1067 `__ for details." +"Python on macOS 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 Q&A QA1067 " +"`__ for " +"details." msgstr "" #: using/mac.rst:115 diff --git a/using/unix.po b/using/unix.po index bd9203969..a77240027 100644 --- a/using/unix.po +++ b/using/unix.po @@ -107,8 +107,8 @@ msgstr "" #: using/unix.rst:54 msgid "" -"pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/i386/python-2.5.1p2." -"tgz" +"pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/i386/" +"python-2.5.1p2.tgz" msgstr "" #: using/unix.rst:60 diff --git a/using/windows.po b/using/windows.po index ed72df740..afd55f8e0 100644 --- a/using/windows.po +++ b/using/windows.po @@ -345,9 +345,9 @@ msgstr "" #: using/windows.rst:165 msgid "" -":file:`%LocalAppData%\\\\\\ Programs\\\\Python\\\\\\ PythonXY` or :file:" -"`%LocalAppData%\\\\\\ Programs\\\\Python\\\\\\ PythonXY-32` or :file:" -"`%LocalAppData%\\\\\\ Programs\\\\Python\\\\\\ PythonXY-64`" +":file:`%LocalAppData%\\\\\\ Programs\\\\Python\\\\\\ PythonXY` " +"or :file:`%LocalAppData%\\\\\\ Programs\\\\Python\\\\\\ PythonXY-32` " +"or :file:`%LocalAppData%\\\\\\ Programs\\\\Python\\\\\\ PythonXY-64`" msgstr "" #: using/windows.rst:175 @@ -572,11 +572,12 @@ msgstr "" #: using/windows.rst:252 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 as the previous example:" +"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 as the " +"previous example:" msgstr "" #: using/windows.rst:258 @@ -650,8 +651,8 @@ msgstr "" #: using/windows.rst:307 msgid "" -"\"Uninstall\" will remove Python entirely, with the exception of the :ref:" -"`launcher`, which has its own entry in Programs and Features." +"\"Uninstall\" will remove Python entirely, with the exception of " +"the :ref:`launcher`, which has its own entry in Programs and Features." msgstr "" #: using/windows.rst:314 @@ -706,8 +707,8 @@ msgstr "" msgid "" "If you have installed another version of Python and added it to your " "``PATH`` variable, it will be available as ``python.exe`` rather than the " -"one from the Microsoft Store. To access the new installation, use ``python3." -"exe`` or ``python3.x.exe``." +"one from the Microsoft Store. To access the new installation, use " +"``python3.exe`` or ``python3.x.exe``." msgstr "" #: using/windows.rst:350 @@ -744,9 +745,9 @@ msgstr "" msgid "" "At runtime, Python will use a private copy of well-known Windows folders and " "the registry. For example, if the environment variable :envvar:`%APPDATA%` " -"is :file:`c:\\\\Users\\\\\\\\AppData\\\\`, then when writing to :file:" -"`C:\\\\Users\\\\\\\\AppData\\\\Local` will write to :file:`C:\\" -"\\Users\\\\\\\\AppData\\\\Local\\\\Packages\\" +"is :file:`c:\\\\Users\\\\\\\\AppData\\\\`, then when writing " +"to :file:`C:\\\\Users\\\\\\\\AppData\\\\Local` will write to :file:`C:" +"\\\\Users\\\\\\\\AppData\\\\Local\\\\Packages\\" "\\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\\\\LocalCache\\\\Local\\" "\\`." msgstr "" @@ -754,16 +755,16 @@ msgstr "" #: using/windows.rst:374 msgid "" "When reading files, Windows will return the file from the private folder, or " -"if that does not exist, the real Windows directory. For example reading :" -"file:`C:\\\\Windows\\\\System32` returns the contents of :file:`C:\\" +"if that does not exist, the real Windows directory. For example " +"reading :file:`C:\\\\Windows\\\\System32` returns the contents of :file:`C:\\" "\\Windows\\\\System32` plus the contents of :file:`C:\\\\Program Files\\" "\\WindowsApps\\\\package_name\\\\VFS\\\\SystemX86`." msgstr "" #: using/windows.rst:378 msgid "" -"You can find the real path of any existing file using :func:`os.path." -"realpath`:" +"You can find the real path of any existing file " +"using :func:`os.path.realpath`:" msgstr "" #: using/windows.rst:380 @@ -1086,8 +1087,8 @@ msgstr "" #: using/windows.rst:584 msgid "" -"To temporarily set environment variables, open Command Prompt and use the :" -"command:`set` command:" +"To temporarily set environment variables, open Command Prompt and use " +"the :command:`set` command:" msgstr "" #: using/windows.rst:587 @@ -1107,19 +1108,19 @@ msgstr "" 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." +"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 "" #: using/windows.rst:602 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)." +"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 "" #: using/windows.rst:611 @@ -1209,8 +1210,8 @@ msgstr "" #: using/windows.rst:666 msgid "" "Windows still uses legacy encodings for the system encoding (the ANSI Code " -"Page). Python uses it for the default encoding of text files (e.g. :func:" -"`locale.getencoding`)." +"Page). Python uses it for the default encoding of text files " +"(e.g. :func:`locale.getencoding`)." msgstr "" #: using/windows.rst:670 @@ -1470,8 +1471,8 @@ msgstr "" #: using/windows.rst:836 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 " +"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." @@ -1556,8 +1557,8 @@ msgstr "" #: using/windows.rst:890 msgid "" "The \"-64\" suffix is deprecated, and now implies \"any architecture that is " -"not provably i386/32-bit\". To request a specific environment, use the new :" -"samp:`-V:{TAG}` argument with the complete tag." +"not provably i386/32-bit\". To request a specific environment, use the " +"new :samp:`-V:{TAG}` argument with the complete tag." msgstr "" #: using/windows.rst:894 @@ -1569,9 +1570,9 @@ msgid "" "program, which performs a :envvar:`PATH` search. If an executable matching " "the first argument after the ``env`` command cannot be found, but the " "argument starts with ``python``, it will be handled as described for the " -"other virtual commands. The environment variable :envvar:" -"`PYLAUNCHER_NO_SEARCH_PATH` may be set (to any value) to skip this search " -"of :envvar:`PATH`." +"other virtual commands. The environment " +"variable :envvar:`PYLAUNCHER_NO_SEARCH_PATH` may be set (to any value) to " +"skip this search of :envvar:`PATH`." msgstr "" #: using/windows.rst:905 @@ -1631,10 +1632,10 @@ msgstr "" #: using/windows.rst:946 msgid "" "Two .ini files will be searched by the launcher - ``py.ini`` in the current " -"user's application data directory (``%LOCALAPPDATA%`` or ``$env:" -"LocalAppData``) 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)." +"user's application data directory (``%LOCALAPPDATA%`` or " +"``$env:LocalAppData``) 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 "" #: using/windows.rst:952 @@ -1667,12 +1668,12 @@ msgstr "" #: using/windows.rst:968 msgid "" -"If no version qualifiers are found in a command, the environment variable :" -"envvar:`PY_PYTHON` can be set to specify the default version qualifier. If " -"it is not set, the default is \"3\". The variable can specify any value that " -"may be passed on the command line, such as \"3\", \"3.7\", \"3.7-32\" or " -"\"3.7-64\". (Note that the \"-64\" option is only available with the " -"launcher included with Python 3.7 or newer.)" +"If no version qualifiers are found in a command, the environment " +"variable :envvar:`PY_PYTHON` can be set to specify the default version " +"qualifier. If it is not set, the default is \"3\". The variable can specify " +"any value that may be passed on the command line, such as \"3\", \"3.7\", " +"\"3.7-32\" or \"3.7-64\". (Note that the \"-64\" option is only available " +"with the launcher included with Python 3.7 or newer.)" msgstr "" #: using/windows.rst:975 @@ -1819,8 +1820,8 @@ msgstr "" msgid "" "An additional :envvar:`PYLAUNCHER_ALWAYS_INSTALL` variable causes the " "launcher to always try to install Python, even if it is detected. This is " -"mainly intended for testing (and should be used with :envvar:" -"`PYLAUNCHER_DRYRUN`)." +"mainly intended for testing (and should be used " +"with :envvar:`PYLAUNCHER_DRYRUN`)." msgstr "" #: using/windows.rst:1072 @@ -1955,19 +1956,19 @@ msgstr "" #: using/windows.rst:1117 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.)." +"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 "" #: using/windows.rst:1122 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 " +"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 "" @@ -2046,8 +2047,8 @@ msgstr "" #: using/windows.rst:1171 msgid "" "If you are loading :file:`python3.dll` or :file:`python37.dll` in your own " -"executable, explicitly call :c:func:`Py_SetPath` or (at least) :c:func:" -"`Py_SetProgramName` before :c:func:`Py_Initialize`." +"executable, explicitly call :c:func:`Py_SetPath` or (at " +"least) :c:func:`Py_SetProgramName` before :c:func:`Py_Initialize`." msgstr "" #: using/windows.rst:1175 @@ -2077,8 +2078,8 @@ msgstr "" #: using/windows.rst:1192 msgid "" -"Add ``._pth`` file support and removes ``applocal`` option from ``pyvenv." -"cfg``." +"Add ``._pth`` file support and removes ``applocal`` option from " +"``pyvenv.cfg``." msgstr "" #: using/windows.rst:1197 @@ -2148,9 +2149,9 @@ msgstr "" #: using/windows.rst:1234 msgid "" -"`PythonWin `_ is a sample MFC application shipped with PyWin32. " -"It is an embeddable IDE with a built-in debugger." +"`PythonWin `_ is a sample MFC application shipped " +"with PyWin32. It is an embeddable IDE with a built-in debugger." msgstr "" #: using/windows.rst:1240 diff --git a/whatsnew/2.0.po b/whatsnew/2.0.po index f6e5a351f..6751f840a 100644 --- a/whatsnew/2.0.po +++ b/whatsnew/2.0.po @@ -155,8 +155,8 @@ msgid "" "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\":" +"accepting or rejecting the proposal. Quoting from the introduction " +"to :pep:`1`, \"PEP Purpose and Guidelines\":" msgstr "" #: whatsnew/2.0.rst:120 @@ -210,10 +210,10 @@ msgstr "" #: 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, :" -"samp:`\\\\u{HHHH}`, where *HHHH* is a 4-digit hexadecimal number from 0000 " -"to FFFF. The existing :samp:`\\\\x{HH}` escape sequence can also be used, " -"and octal escapes can be used for characters up to U+01FF, which is " +"Arbitrary Unicode characters can be written using a new escape " +"sequence, :samp:`\\\\u{HHHH}`, where *HHHH* is a 4-digit hexadecimal number " +"from 0000 to FFFF. The existing :samp:`\\\\x{HH}` escape sequence can also " +"be used, and octal escapes can be used for characters up to U+01FF, which is " "represented by ``\\777``." msgstr "" @@ -320,9 +320,9 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.0.rst:229 @@ -436,9 +436,9 @@ msgid "" "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." +"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 "" #: whatsnew/2.0.rst:307 @@ -562,8 +562,8 @@ msgid "" "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 " +"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 "" @@ -608,11 +608,11 @@ msgstr "" #: 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)``." +"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 "" #: whatsnew/2.0.rst:433 @@ -816,11 +816,11 @@ msgstr "" #: 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 https://pythonce.sourceforge." -"net/ for more information." +"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 https://" +"pythonce.sourceforge.net/ for more information." msgstr "" #: whatsnew/2.0.rst:577 @@ -837,10 +837,10 @@ msgid "" "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. ::" +"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 "" #: whatsnew/2.0.rst:590 @@ -876,27 +876,27 @@ msgstr "" 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\"." +"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 "" #: 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." +"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 "" #: 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::" +"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 "" #: whatsnew/2.0.rst:628 @@ -917,10 +917,10 @@ 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`." +"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 "" #: whatsnew/2.0.rst:647 @@ -966,9 +966,9 @@ msgstr "" msgid "" "Some of the functions in the :mod:`socket` module are still forgiving in " "this way. For example, ``socket.connect( ('hostname', 25) )`` is the " -"correct form, passing a tuple representing an IP address, but ``socket." -"connect('hostname', 25)`` also works. :meth:`socket.connect_ex ` and :meth:`socket.bind ` are " +"correct form, passing a tuple representing an IP address, but " +"``socket.connect('hostname', 25)`` also works. :meth:`socket.connect_ex " +"` and :meth:`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 " @@ -1027,11 +1027,11 @@ msgstr "" 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'``." +"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 "" #: whatsnew/2.0.rst:724 @@ -1067,10 +1067,10 @@ msgstr "" #: 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)``." +"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 "" #: whatsnew/2.0.rst:759 @@ -1088,8 +1088,8 @@ msgstr "" 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 :c:func:`malloc`. For documentation, read the comments in :" -"file:`Include/pymem.h` and :file:`Include/objimpl.h`. For the lengthy " +"of C's standard :c: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 "" @@ -1131,19 +1131,19 @@ msgstr "" #: 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: :c:func:" -"`PyModule_AddObject`, :c:func:`PyModule_AddIntConstant`, and :c: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 " +"dictionary at module initialization time were " +"added: :c:func:`PyModule_AddObject`, :c:func:`PyModule_AddIntConstant`, " +"and :c: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 "" #: whatsnew/2.0.rst:804 msgid "" -"A wrapper API was added for Unix-style signal handlers. :c:func:" -"`PyOS_getsig` gets a signal handler and :c:func:`PyOS_setsig` will set a new " -"handler." +"A wrapper API was added for Unix-style signal " +"handlers. :c:func:`PyOS_getsig` gets a signal handler " +"and :c:func:`PyOS_setsig` will set a new handler." msgstr "" #: whatsnew/2.0.rst:811 @@ -1181,8 +1181,8 @@ msgstr "" #: 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::" +"For the simple case, when the software contains only .py files, a " +"minimal :file:`setup.py` can be just a few lines long::" msgstr "" #: whatsnew/2.0.rst:837 @@ -1273,11 +1273,12 @@ 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:`~xml.sax.handler.ContentHandler." -"startElement` and :meth:`~xml.sax.handler.ContentHandler.endElement` methods " -"are called for every starting and end tag encountered by the parser, the :" -"meth:`~xml.sax.handler.ContentHandler.characters` method is called for every " -"chunk of character data, and so forth." +"the XML parser. For example, " +"the :meth:`~xml.sax.handler.ContentHandler.startElement` " +"and :meth:`~xml.sax.handler.ContentHandler.endElement` methods are called " +"for every starting and end tag encountered by the parser, " +"the :meth:`~xml.sax.handler.ContentHandler.characters` method is called for " +"every chunk of character data, and so forth." msgstr "" #: whatsnew/2.0.rst:906 @@ -1292,8 +1293,8 @@ msgstr "" #: 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::" +"message for every starting and ending tag, and then parses the " +"file :file:`hamlet.xml` using it::" msgstr "" #: whatsnew/2.0.rst:916 @@ -1352,10 +1353,11 @@ msgstr "" #: 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::" +"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 "" #: whatsnew/2.0.rst:961 @@ -1466,23 +1468,25 @@ msgstr "" #: 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` :mod:`wave`, :mod:" -"`random`, :mod:`shelve`, and :mod:`nntplib`. Consult the CVS logs for the " -"exact patch-by-patch details." +"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` :mod:`wave`, :mod:`random`, :mod:`shelve`, " +"and :mod:`nntplib`. Consult the CVS logs for the exact patch-by-patch " +"details." msgstr "" #: 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." +"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 "" #: whatsnew/2.0.rst:1046 @@ -1520,10 +1524,10 @@ msgstr "" #: whatsnew/2.0.rst:1065 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." +"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 "" #: whatsnew/2.0.rst:1075 @@ -1581,8 +1585,8 @@ msgid "" "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.)" +"the :mod:`re` module. (Contributed by Sam Rushing, with some extensions by " +"A.M. Kuchling.)" msgstr "" #: whatsnew/2.0.rst:1109 @@ -1619,9 +1623,9 @@ msgid "" "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.)" +"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 "" #: whatsnew/2.0.rst:1133 @@ -1704,8 +1708,8 @@ msgstr "" #: whatsnew/2.0.rst:1178 msgid "" -"Three new keystroke commands: Check module (:kbd:`Alt-F5`), Import module (:" -"kbd:`F5`) and Run script (:kbd:`Ctrl-F5`)." +"Three new keystroke commands: Check module (:kbd:`Alt-F5`), Import module " +"(:kbd:`F5`) and Run script (:kbd:`Ctrl-F5`)." msgstr "" #: whatsnew/2.0.rst:1185 @@ -1722,13 +1726,13 @@ msgstr "" #: whatsnew/2.0.rst:1191 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." +"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 "" #: whatsnew/2.0.rst:1200 diff --git a/whatsnew/2.1.po b/whatsnew/2.1.po index d565621b0..7212e0d86 100644 --- a/whatsnew/2.1.po +++ b/whatsnew/2.1.po @@ -114,10 +114,11 @@ msgid "" "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." +"(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 "" #: whatsnew/2.1.rst:77 @@ -220,10 +221,11 @@ msgstr "" 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." +"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 "" #: whatsnew/2.1.rst:153 @@ -320,9 +322,9 @@ msgstr "" #: 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.)" +"(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 "" #: whatsnew/2.1.rst:198 @@ -356,8 +358,8 @@ msgstr "" 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 " +"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 "" @@ -390,8 +392,8 @@ msgstr "" #: 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 " +"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." @@ -429,9 +431,9 @@ msgstr "" 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 ::" +"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 "" #: whatsnew/2.1.rst:269 @@ -445,13 +447,13 @@ msgstr "" #: 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)." +"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 "" #: whatsnew/2.1.rst:283 @@ -519,8 +521,8 @@ msgstr "" 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/` " +"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 "" @@ -683,12 +685,13 @@ msgstr "" #: whatsnew/2.1.rst:445 msgid "" -"The dictionary containing attributes can be accessed as the function's :attr:" -"`~function.__dict__`. Unlike the :attr:`~type.__dict__` attribute of class " -"instances, in functions you can actually assign a new dictionary to :attr:" -"`~function.__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." +"The dictionary containing attributes can be accessed as the " +"function's :attr:`~function.__dict__`. Unlike the :attr:`~type.__dict__` " +"attribute of class instances, in functions you can actually assign a new " +"dictionary to :attr:`~function.__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 "" #: whatsnew/2.1.rst:455 @@ -716,9 +719,10 @@ 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." +"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 "" #: whatsnew/2.1.rst:480 @@ -815,17 +819,18 @@ msgstr "" #: whatsnew/2.1.rst:552 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." +"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 "" #: whatsnew/2.1.rst:565 @@ -834,8 +839,8 @@ msgid "" "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/." +"enhancements. It will be available from the Distutils SIG at https://" +"www.python.org/community/sigs/current/distutils-sig/." msgstr "" #: whatsnew/2.1.rst:574 @@ -860,10 +865,11 @@ msgstr "" 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::" +"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 "" #: whatsnew/2.1.rst:594 @@ -886,8 +892,8 @@ msgstr "" #: whatsnew/2.1.rst:609 msgid "" -":file:`pydoc` also includes a Tk-based interactive help browser. :file:" -"`pydoc` quickly becomes addictive; try it out!" +":file:`pydoc` also includes a Tk-based interactive help " +"browser. :file:`pydoc` quickly becomes addictive; try it out!" msgstr "" #: whatsnew/2.1.rst:612 @@ -897,18 +903,18 @@ msgid "" "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 https://pyunit." -"sourceforge.net/ for more information about PyUnit." +"adaptation of Kent Beck's Smalltalk testing framework. See https://" +"pyunit.sourceforge.net/ for more information about PyUnit." msgstr "" #: whatsnew/2.1.rst:620 msgid "" -"The :mod:`difflib` module contains a class, :class:`~difflib." -"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." +"The :mod:`difflib` module contains a " +"class, :class:`~difflib.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 "" #: whatsnew/2.1.rst:626 @@ -931,14 +937,14 @@ msgstr "" #: whatsnew/2.1.rst:638 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." +"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 "" #: whatsnew/2.1.rst:646 @@ -986,11 +992,11 @@ msgstr "" #: whatsnew/2.1.rst:673 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." +"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 "" #: whatsnew/2.1.rst:680 @@ -1018,9 +1024,9 @@ msgid "" "faster than the system :c:func:`malloc` and have less memory overhead. The " "allocator uses C's :c: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." +"enabled by providing the :option:`!--with-pymalloc` option to " +"the :program:`configure` script; see :file:`Objects/obmalloc.c` for the " +"implementation details." msgstr "" #: whatsnew/2.1.rst:702 @@ -1028,16 +1034,16 @@ 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 :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 " -"will get you a core dump. For example, if memory was allocated using :c:" -"macro:`PyMem_New`, it has to be freed using :c:func:`PyMem_Del`, 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." +"API that have previously been just 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 will get you a core dump. For example, if memory " +"was allocated using :c:macro:`PyMem_New`, it has to be freed " +"using :c:func:`PyMem_Del`, 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 "" #: whatsnew/2.1.rst:715 @@ -1059,11 +1065,11 @@ msgstr "" #: whatsnew/2.1.rst:726 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::" +"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 "" #: whatsnew/2.1.rst:733 @@ -1133,10 +1139,10 @@ msgstr "" #: whatsnew/2.1.rst:773 msgid "" -"C extensions which import other modules have been changed to use :c: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." +"C extensions which import other modules have been changed to " +"use :c: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 "" #: whatsnew/2.1.rst:778 diff --git a/whatsnew/2.2.po b/whatsnew/2.2.po index 4f3e91a8e..3594249c3 100644 --- a/whatsnew/2.2.po +++ b/whatsnew/2.2.po @@ -185,16 +185,16 @@ 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 :class:" -"`object`.)" +"see :pep:`253` for the details --- but it's easier to just " +"subclass :class:`object`.)" msgstr "" #: 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. ::" +"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 "" #: whatsnew/2.2.rst:131 @@ -397,12 +397,12 @@ msgstr "" #: whatsnew/2.2.rst:265 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." +"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 "" #: whatsnew/2.2.rst:273 @@ -432,9 +432,9 @@ msgstr "" #: whatsnew/2.2.rst:288 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`, " +"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 " @@ -469,8 +469,9 @@ msgid "" "A fair number of sophisticated Python classes define hooks for attribute " "access using :meth:`~object.__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." +"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 "" #: whatsnew/2.2.rst:318 @@ -495,12 +496,12 @@ 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:`~object.__getattr__` methods also end up " -"being called by Python when it checks for other methods such as :meth:" -"`~object.__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." +"accesses inside them, and instead have to mess around with the contents " +"of :attr:`~object.__dict__`. :meth:`~object.__getattr__` methods also end up " +"being called by Python when it checks for other methods such " +"as :meth:`~object.__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 "" #: whatsnew/2.2.rst:338 @@ -544,10 +545,10 @@ 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::" +"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 "" #: whatsnew/2.2.rst:372 @@ -598,11 +599,11 @@ 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." +"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 "" #: whatsnew/2.2.rst:413 @@ -653,13 +654,14 @@ msgstr "" #: whatsnew/2.2.rst:443 msgid "" -"In Python 2.2, iteration can be implemented separately, and :meth:`~object." -"__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." +"In Python 2.2, iteration can be implemented separately, " +"and :meth:`~object.__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 "" #: whatsnew/2.2.rst:451 @@ -667,10 +669,10 @@ 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." +"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 "" #: whatsnew/2.2.rst:458 @@ -705,8 +707,8 @@ 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 " +"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::" @@ -723,9 +725,9 @@ msgstr "" #: whatsnew/2.2.rst:493 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::" +"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 "" #: whatsnew/2.2.rst:496 @@ -751,10 +753,11 @@ msgstr "" #: whatsnew/2.2.rst:513 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)``." +"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 "" #: whatsnew/2.2.rst:519 @@ -843,11 +846,12 @@ msgid "" "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.)" +"``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 "" #: whatsnew/2.2.rst:584 @@ -1098,20 +1102,21 @@ msgstr "" #: whatsnew/2.2.rst:756 msgid "" -"Classes can define methods called :meth:`~object.__truediv__` and :meth:" -"`~object.__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." +"Classes can define methods called :meth:`~object.__truediv__` " +"and :meth:`~object.__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 "" #: whatsnew/2.2.rst:761 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." +"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 "" #: whatsnew/2.2.rst:771 @@ -1276,10 +1281,11 @@ msgid "" "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." +"(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 "" #: whatsnew/2.2.rst:889 @@ -1386,8 +1392,8 @@ msgstr "" #: whatsnew/2.2.rst:963 msgid "" -"The new :mod:`hmac` module implements the HMAC algorithm described by :rfc:" -"`2104`. (Contributed by Gerhard Häring.)" +"The new :mod:`hmac` module implements the HMAC algorithm described " +"by :rfc:`2104`. (Contributed by Gerhard Häring.)" msgstr "" #: whatsnew/2.2.rst:966 @@ -1395,18 +1401,19 @@ msgid "" "Several functions that originally returned lengthy tuples now return pseudo-" "sequences that still behave like tuples but also have mnemonic attributes " "such as :attr:`!memberst_mtime` or :attr:`~time.struct_time.tm_year`. The " -"enhanced functions include :func:`~os.stat`, :func:`~os.fstat`, :func:`~os." -"statvfs`, and :func:`~os.fstatvfs` in the :mod:`os` module, and :func:`~time." -"localtime`, :func:`~time.gmtime`, and :func:`~time.strptime` in the :mod:" -"`time` module." +"enhanced functions " +"include :func:`~os.stat`, :func:`~os.fstat`, :func:`~os.statvfs`, " +"and :func:`~os.fstatvfs` in the :mod:`os` module, " +"and :func:`~time.localtime`, :func:`~time.gmtime`, " +"and :func:`~time.strptime` in the :mod:`time` module." msgstr "" #: whatsnew/2.2.rst:973 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``." +"now this can be written more clearly as ``file_size = " +"os.stat(filename).st_size``." msgstr "" #: whatsnew/2.2.rst:977 @@ -1422,9 +1429,9 @@ msgstr "" #: whatsnew/2.2.rst:982 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.)" +"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 "" #: whatsnew/2.2.rst:986 @@ -1437,13 +1444,13 @@ msgstr "" #: whatsnew/2.2.rst:991 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.)" +"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 "" #: whatsnew/2.2.rst:999 @@ -1495,14 +1502,14 @@ msgstr "" #: whatsnew/2.2.rst:1029 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.)" +"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 "" #: whatsnew/2.2.rst:1038 @@ -1547,12 +1554,12 @@ msgstr "" #: whatsnew/2.2.rst:1066 msgid "" "Another low-level API, primarily of interest to implementers 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.)" +"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 "" #: whatsnew/2.2.rst:1073 @@ -1586,8 +1593,8 @@ msgstr "" #: whatsnew/2.2.rst:1087 msgid "" -"Rename :c:func:`!PyObject_GC_Init` to :c:func:`PyObject_GC_Track` and :c:" -"func:`!PyObject_GC_Fini` to :c:func:`PyObject_GC_UnTrack`." +"Rename :c:func:`!PyObject_GC_Init` to :c:func:`PyObject_GC_Track` " +"and :c:func:`!PyObject_GC_Fini` to :c:func:`PyObject_GC_UnTrack`." msgstr "" #: whatsnew/2.2.rst:1090 @@ -1625,19 +1632,20 @@ msgid "" "Two new flags :c:macro:`METH_NOARGS` and :c:macro:`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 :c:macro:" -"`METH_VARARGS`. Also, the old :c:macro:`!METH_OLDARGS` style of writing C " -"methods is now officially deprecated." +"efficient than calling a corresponding method that " +"uses :c:macro:`METH_VARARGS`. Also, the old :c:macro:`!METH_OLDARGS` style " +"of writing C methods is now officially deprecated." msgstr "" #: whatsnew/2.2.rst:1115 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.)" +"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 "" #: whatsnew/2.2.rst:1122 @@ -1705,8 +1713,8 @@ msgstr "" 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." +"The :exc:`ReferenceError` exception has therefore moved from " +"the :mod:`weakref` module to become a built-in exception." msgstr "" #: whatsnew/2.2.rst:1186 @@ -1718,10 +1726,10 @@ msgstr "" #: whatsnew/2.2.rst:1190 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`. " +"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 "" @@ -1762,12 +1770,12 @@ 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." +"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 "" #: whatsnew/2.2.rst:1225 @@ -1808,9 +1816,9 @@ msgstr "" #: whatsnew/2.2.rst:1246 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.)" +"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 "" #: whatsnew/2.2.rst:1251 diff --git a/whatsnew/2.3.po b/whatsnew/2.3.po index 9a4e10b9c..42f404d06 100644 --- a/whatsnew/2.3.po +++ b/whatsnew/2.3.po @@ -103,8 +103,8 @@ msgstr "" #: whatsnew/2.3.rst:66 msgid "" -"The union and intersection of sets can be computed with the :meth:" -"`~frozenset.union` and :meth:`~frozenset.intersection` methods; an " +"The union and intersection of sets can be computed with " +"the :meth:`~frozenset.union` and :meth:`~frozenset.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:`~frozenset.intersection_update`. ::" @@ -134,8 +134,8 @@ msgid "" "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:" -"`~frozenset.symmetric_difference_update`. ::" +"notation (``^``), and an in-place version with the ungainly " +"name :meth:`~frozenset.symmetric_difference_update`. ::" msgstr "" #: whatsnew/2.3.rst:92 @@ -233,12 +233,13 @@ msgid "" "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.)" +"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 "" #: whatsnew/2.3.rst:169 @@ -384,9 +385,9 @@ msgstr "" 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." +"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 "" #: whatsnew/2.3.rst:273 @@ -415,8 +416,8 @@ msgstr "" 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:" +"be automatically imported if a ZIP archive's filename is added to " +"``sys.path``. For example:" msgstr "" #: whatsnew/2.3.rst:296 @@ -442,11 +443,12 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.3.rst:321 @@ -464,9 +466,9 @@ msgstr "" 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." +"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 "" #: whatsnew/2.3.rst:338 @@ -483,10 +485,11 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.3.rst:350 @@ -498,10 +501,10 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.3.rst:359 @@ -536,9 +539,9 @@ msgstr "" 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 " +"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 "" @@ -552,9 +555,9 @@ msgstr "" #: 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." +"This feature can be disabled when compiling Python by specifying " +"the :option:`!--without-universal-newlines` switch when running " +"Python's :program:`configure` script." msgstr "" #: whatsnew/2.3.rst:403 @@ -628,15 +631,16 @@ msgstr "" msgid "" "The :class:`~logging.Logger` class is the primary class. Most application " "code will deal with one or more :class:`~logging.Logger` objects, each one " -"used by a particular subsystem of the application. Each :class:`~logging." -"Logger` is identified by a name, and names are organized into a hierarchy " -"using ``.`` as the component separator. For example, you might have :class:" -"`~logging.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:`~logging.Logger` that's the parent of all other loggers." +"used by a particular subsystem of the application. " +"Each :class:`~logging.Logger` is identified by a name, and names are " +"organized into a hierarchy using ``.`` as the component separator. For " +"example, you might have :class:`~logging.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:`~logging.Logger` that's the " +"parent of all other loggers." msgstr "" #: whatsnew/2.3.rst:464 @@ -671,8 +675,8 @@ msgstr "" 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:" -"`~logging.Logger.setLevel` method on the root logger." +"display of informational and debugging messages by calling " +"the :meth:`~logging.Logger.setLevel` method on the root logger." msgstr "" #: whatsnew/2.3.rst:486 @@ -729,9 +733,9 @@ msgstr "" #: 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:" -"`~logging.Logger` can prevent this by setting its :attr:`~logging.Logger." -"propagate` attribute to :const:`False`." +"``server.auth`` is also seen by ``server`` and ``root``, but " +"a :class:`~logging.Logger` can prevent this by setting " +"its :attr:`~logging.Logger.propagate` attribute to :const:`False`." msgstr "" #: whatsnew/2.3.rst:523 @@ -742,10 +746,10 @@ msgid "" "any number of different :class:`~logging.Handler` instances. Loggers and " "handlers can also have an attached list of filters, and each filter can " "cause the :class:`~logging.LogRecord` to be ignored or can modify the record " -"before passing it along. When they're finally output, :class:`~logging." -"LogRecord` instances are converted to text by a :class:`~logging.Formatter` " -"class. All of these classes can be replaced by your own specially written " -"classes." +"before passing it along. When they're finally " +"output, :class:`~logging.LogRecord` instances are converted to text by " +"a :class:`~logging.Formatter` class. All of these classes can be replaced " +"by your own specially written classes." msgstr "" #: whatsnew/2.3.rst:533 @@ -772,17 +776,17 @@ msgstr "" #: 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.)" +"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 "" #: 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`. ::" +"for it takes any Python value and converts it to :const:`True` " +"or :const:`False`. ::" msgstr "" #: whatsnew/2.3.rst:561 @@ -828,13 +832,13 @@ msgstr "" 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. ::" +"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 "" #: whatsnew/2.3.rst:596 @@ -873,9 +877,9 @@ msgstr "" 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 " +"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." @@ -999,14 +1003,14 @@ msgstr "" 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." +"an importer object that will handle imports from this path or raises " +"an :exc:`ImportError` exception if it can't handle this path." msgstr "" #: 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." +"``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 "" #: whatsnew/2.3.rst:724 @@ -1118,9 +1122,9 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.3.rst:805 @@ -1168,10 +1172,10 @@ msgstr "" #: 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:`~object." -"__getstate__`, :meth:`~object.__setstate__`, and :meth:`~object." -"__getnewargs__`. Consult :pep:`307` for the full semantics of these " -"methods." +"customizing pickling was added using three special " +"methods: :meth:`~object.__getstate__`, :meth:`~object.__setstate__`, " +"and :meth:`~object.__getnewargs__`. Consult :pep:`307` for the full " +"semantics of these methods." msgstr "" #: whatsnew/2.3.rst:841 @@ -1487,10 +1491,10 @@ msgstr "" #: 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:" +"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 "" #: whatsnew/2.3.rst:1052 @@ -1508,16 +1512,16 @@ 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`." +"deprecated in the future, supply :option:`-" +"Walways::PendingDeprecationWarning:: <-W>` on the command line or " +"use :func:`warnings.filterwarnings`." msgstr "" #: 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`." +"occurred\"``, has begun. Raising a string will now " +"trigger :exc:`PendingDeprecationWarning`." msgstr "" #: whatsnew/2.3.rst:1069 @@ -1592,8 +1596,8 @@ msgstr "" #: 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:`~type.__name__` and :attr:" -"`~type.__bases__` attributes of new-style classes. There are some " +"been removed: you can now assign to the :attr:`~type.__name__` " +"and :attr:`~type.__bases__` attributes of new-style classes. There are some " "restrictions on what can be assigned to :attr:`!__bases__` along the lines " "of those relating to assigning to an instance's :attr:`~object.__class__` " "attribute." @@ -1723,8 +1727,9 @@ msgstr "" #: 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.)" +"increase, depending on your compiler's idiosyncrasies. See " +"section :ref:`23section-other` for a longer explanation. (Removed by Michael " +"Hudson.)" msgstr "" #: whatsnew/2.3.rst:1206 @@ -1785,18 +1790,19 @@ msgid "" "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`." +"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 "" #: 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.)" +"library. bz2-compressed data is usually smaller than " +"corresponding :mod:`zlib`\\ -compressed data. (Contributed by Gustavo " +"Niemeyer.)" msgstr "" #: whatsnew/2.3.rst:1253 @@ -1830,18 +1836,18 @@ msgstr "" #: 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)." +"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 "" #: 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:`~doctest.DocTestSuite` function creates a :" -"class:`unittest.TestSuite` object from a set of :mod:`doctest` tests." +"private ones as well. The :func:`~doctest.DocTestSuite` function creates " +"a :class:`unittest.TestSuite` object from a set of :mod:`doctest` tests." msgstr "" #: whatsnew/2.3.rst:1280 @@ -1854,10 +1860,10 @@ msgstr "" msgid "" "The :mod:`getopt` module gained a new function, :func:`~getopt.gnu_getopt`, " "that supports the same arguments as the existing :func:`~getopt.getopt` " -"function but uses GNU-style scanning mode. The existing :func:`~getopt." -"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::" +"function but uses GNU-style scanning mode. The " +"existing :func:`~getopt.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 "" #: whatsnew/2.3.rst:1289 @@ -1904,10 +1910,10 @@ msgstr "" #: whatsnew/2.3.rst:1314 msgid "" -"The :mod:`heapq` module provides :func:`~heapq.heappush` and :func:`~heapq." -"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::" +"The :mod:`heapq` module provides :func:`~heapq.heappush` " +"and :func:`~heapq.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 "" #: whatsnew/2.3.rst:1318 @@ -1992,8 +1998,8 @@ msgid "" "stamps are floats. For compatibility, when using the tuple interface of " "the :class:`~os.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::" +"stamps are still represented as integers, unless :func:`!" +"os.stat_float_times` is invoked to enable float return values::" msgstr "" #: whatsnew/2.3.rst:1376 @@ -2047,8 +2053,8 @@ 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:`~xml.parsers.expat.xmlparser.buffer_text` attribute to :" -"const:`True` will enable buffering." +"object's :attr:`~xml.parsers.expat.xmlparser.buffer_text` attribute " +"to :const:`True` will enable buffering." msgstr "" #: whatsnew/2.3.rst:1410 @@ -2093,8 +2099,8 @@ msgstr "" #: whatsnew/2.3.rst:1438 msgid "" -"The :mod:`readline` module also gained a number of new functions: :func:" -"`~readline.get_history_item`, :func:`~readline.get_current_history_length`, " +"The :mod:`readline` module also gained a number of new " +"functions: :func:`~readline.get_history_item`, :func:`~readline.get_current_history_length`, " "and :func:`~readline.redisplay`." msgstr "" @@ -2130,9 +2136,9 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.3.rst:1463 @@ -2167,8 +2173,8 @@ msgstr "" #: 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.)" +"The new :mod:`tarfile` module allows reading from and writing " +"to :program:`tar`\\ -format archive files. (Contributed by Lars Gustäbel.)" msgstr "" #: whatsnew/2.3.rst:1484 @@ -2178,8 +2184,8 @@ msgid "" "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:`~textwrap.fill` is built on top of :func:`~textwrap." -"wrap`. For example::" +"you can guess, :func:`~textwrap.fill` is built on top " +"of :func:`~textwrap.wrap`. For example::" msgstr "" #: whatsnew/2.3.rst:1491 @@ -2203,21 +2209,21 @@ msgstr "" #: whatsnew/2.3.rst:1506 msgid "" "The module also contains a :class:`~textwrap.TextWrapper` class that " -"actually implements the text wrapping strategy. Both the :class:`~textwrap." -"TextWrapper` class and the :func:`~textwrap.wrap` and :func:`~textwrap.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.)" +"actually implements the text wrapping strategy. Both " +"the :class:`~textwrap.TextWrapper` class and the :func:`~textwrap.wrap` " +"and :func:`~textwrap.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 "" #: 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::" +"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 "" #: whatsnew/2.3.rst:1519 @@ -2231,12 +2237,13 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.3.rst:1532 @@ -2290,9 +2297,9 @@ msgid "" "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.)" +"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 "" #: whatsnew/2.3.rst:1572 @@ -2342,8 +2349,9 @@ msgstr "" #: whatsnew/2.3.rst:1598 msgid "" "Adding the mix-in as a superclass provides the full dictionary interface " -"whenever the class defines :meth:`~object.__getitem__`, :meth:`~object." -"__setitem__`, :meth:`~object.__delitem__`, and :meth:`!keys`. For example::" +"whenever the class " +"defines :meth:`~object.__getitem__`, :meth:`~object.__setitem__`, :meth:`~object.__delitem__`, " +"and :meth:`!keys`. For example::" msgstr "" #: whatsnew/2.3.rst:1602 @@ -2393,9 +2401,9 @@ msgstr "" #: 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:`~xml.dom.minidom.Node.toxml` and :meth:`~xml.dom.minidom.Node." -"toprettyxml` methods of DOM nodes." +"in a particular encoding by providing an optional encoding argument to " +"the :meth:`~xml.dom.minidom.Node.toxml` " +"and :meth:`~xml.dom.minidom.Node.toprettyxml` methods of DOM nodes." msgstr "" #: whatsnew/2.3.rst:1645 @@ -2452,9 +2460,9 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.3.rst:1685 @@ -2462,19 +2470,19 @@ msgid "" "The three primary types are: :class:`~datetime.date`, representing a day, " "month, and year; :class:`~datetime.time`, consisting of hour, minute, and " "second; and :class:`~datetime.datetime`, which contains all the attributes " -"of both :class:`~datetime.date` and :class:`~datetime.time`. There's also a :" -"class:`~datetime.timedelta` class representing differences between two " +"of both :class:`~datetime.date` and :class:`~datetime.time`. There's also " +"a :class:`~datetime.timedelta` class representing differences between two " "points in time, and time zone logic is implemented by classes inheriting " "from the abstract :class:`~datetime.tzinfo` class." msgstr "" #: whatsnew/2.3.rst:1692 msgid "" -"You can create instances of :class:`~datetime.date` and :class:`~datetime." -"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:`~datetime.date.today` " -"class method returns the current local date." +"You can create instances of :class:`~datetime.date` " +"and :class:`~datetime.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:`~datetime.date.today` class method returns the current local date." msgstr "" #: whatsnew/2.3.rst:1698 @@ -2515,12 +2523,12 @@ msgstr "" #: whatsnew/2.3.rst:1720 msgid "" "Instances can be compared, hashed, and converted to strings (the result is " -"the same as that of :meth:`~datetime.datetime.isoformat`). :class:" -"`~datetime.date` and :class:`~datetime.datetime` instances can be subtracted " -"from each other, and added to :class:`~datetime.timedelta` instances. The " -"largest missing feature is that there's no standard library support for " -"parsing strings and getting back a :class:`~datetime.date` or :class:" -"`~datetime.datetime`." +"the same as that " +"of :meth:`~datetime.datetime.isoformat`). :class:`~datetime.date` " +"and :class:`~datetime.datetime` instances can be subtracted from each other, " +"and added to :class:`~datetime.timedelta` instances. The largest missing " +"feature is that there's no standard library support for parsing strings and " +"getting back a :class:`~datetime.date` or :class:`~datetime.datetime`." msgstr "" #: whatsnew/2.3.rst:1727 @@ -2564,8 +2572,8 @@ msgstr "" #: whatsnew/2.3.rst:1756 msgid "" -"Parsing a command line is then done by calling the :meth:`~optparse." -"OptionParser.parse_args` method. ::" +"Parsing a command line is then done by calling " +"the :meth:`~optparse.OptionParser.parse_args` method. ::" msgstr "" #: whatsnew/2.3.rst:1758 @@ -2684,22 +2692,23 @@ msgstr "" #: 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`." +"memory\" family: :c:func:`PyMem_Malloc`, :c:func:`PyMem_Realloc`, " +"and :c:func:`PyMem_Free`." msgstr "" #: 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`." +"allocations: :c:func:`PyObject_Malloc`, :c:func:`PyObject_Realloc`, " +"and :c:func:`PyObject_Free`." msgstr "" #: whatsnew/2.3.rst:1849 msgid "" -"To allocate and free Python objects, use the \"object\" family :c:macro:" -"`PyObject_New`, :c:macro:`PyObject_NewVar`, and :c:func:`PyObject_Del`." +"To allocate and free Python objects, use the \"object\" " +"family :c:macro:`PyObject_New`, :c:macro:`PyObject_NewVar`, " +"and :c:func:`PyObject_Del`." msgstr "" #: whatsnew/2.3.rst:1852 @@ -2707,8 +2716,8 @@ 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`." +"compile a debugging version of the Python interpreter by " +"running :program:`configure` with :option:`!--with-pydebug`." msgstr "" #: whatsnew/2.3.rst:1858 @@ -2743,15 +2752,16 @@ msgstr "" 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." +"Python without it, and the :option:`!--with-cycle-gc` switch " +"to :program:`configure` has been removed." msgstr "" #: 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.)" +"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 "" #: whatsnew/2.3.rst:1889 @@ -2766,8 +2776,8 @@ msgstr "" #: 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% " +"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 "" @@ -2786,9 +2796,9 @@ msgstr "" #: whatsnew/2.3.rst:1907 msgid "" ":c:func:`PyArg_ParseTuple` accepts new format characters for various sizes " -"of unsigned integers: ``B`` for :c:expr:`unsigned char`, ``H`` for :c:expr:" -"`unsigned short int`, ``I`` for :c:expr:`unsigned int`, and ``K`` for :c:" -"expr:`unsigned long long`." +"of unsigned integers: ``B`` for :c:expr:`unsigned char`, ``H`` " +"for :c:expr:`unsigned short int`, ``I`` for :c:expr:`unsigned int`, and " +"``K`` for :c:expr:`unsigned long long`." msgstr "" #: whatsnew/2.3.rst:1912 @@ -2800,9 +2810,9 @@ msgstr "" #: 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)." +"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 "" #: whatsnew/2.3.rst:1920 @@ -2821,12 +2831,12 @@ msgstr "" #: 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:`~type.__module__` and :" -"attr:`~type.__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." +"aware of a change in the rules relating to the :attr:`~type.__module__` " +"and :attr:`~type.__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 "" #: whatsnew/2.3.rst:1938 @@ -2838,11 +2848,11 @@ 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 " +"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 "" @@ -2863,8 +2873,8 @@ msgstr "" #: whatsnew/2.3.rst:1957 msgid "" -"Other new platforms now supported by Python include AtheOS (http://www." -"atheos.cx/), GNU/Hurd, and OpenVMS." +"Other new platforms now supported by Python include AtheOS (http://" +"www.atheos.cx/), GNU/Hurd, and OpenVMS." msgstr "" #: whatsnew/2.3.rst:1966 @@ -2934,10 +2944,11 @@ msgstr "" #: whatsnew/2.3.rst:2006 msgid "" -"A nifty new feature is that trace functions can now assign to the :attr:" -"`~frame.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.)" +"A nifty new feature is that trace functions can now assign to " +"the :attr:`~frame.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 "" #: whatsnew/2.3.rst:2015 @@ -2986,9 +2997,10 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.3.rst:2043 diff --git a/whatsnew/2.4.po b/whatsnew/2.4.po index f361198f5..b54be88b3 100644 --- a/whatsnew/2.4.po +++ b/whatsnew/2.4.po @@ -135,10 +135,11 @@ msgstr "" 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." +"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 "" #: whatsnew/2.4.rst:99 @@ -325,10 +326,10 @@ msgstr "" 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::" +"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 "" #: whatsnew/2.4.rst:227 @@ -342,8 +343,8 @@ msgstr "" #: 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." +"If the method was very long, it would be easy to miss or forget " +"the :func:`classmethod` invocation after the function body." msgstr "" #: whatsnew/2.4.rst:236 @@ -545,8 +546,8 @@ msgstr "" #: whatsnew/2.4.rst:363 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`. ::" +"If you want to reverse an iterator, first convert it to a list " +"with :func:`list`. ::" msgstr "" #: whatsnew/2.4.rst:367 @@ -574,13 +575,14 @@ msgstr "" #: whatsnew/2.4.rst:386 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." +"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 "" #: whatsnew/2.4.rst:395 @@ -642,26 +644,27 @@ msgstr "" #: whatsnew/2.4.rst:430 msgid "" -"*universal_newlines* opens the child's input and output using Python's :term:" -"`universal newlines` feature." +"*universal_newlines* opens the child's input and output using " +"Python's :term:`universal newlines` feature." msgstr "" #: whatsnew/2.4.rst:433 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)``." +"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 "" #: whatsnew/2.4.rst:440 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`::" +":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 "" #: whatsnew/2.4.rst:444 @@ -809,10 +812,10 @@ msgstr "" #: whatsnew/2.4.rst:540 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." +"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 "" #: whatsnew/2.4.rst:545 @@ -935,9 +938,9 @@ msgstr "" #: whatsnew/2.4.rst:623 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. ::" +":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 "" #: whatsnew/2.4.rst:627 @@ -963,8 +966,9 @@ msgstr "" #: whatsnew/2.4.rst:639 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." +"constants for the various " +"possibilities: :const:`ROUND_DOWN`, :const:`ROUND_CEILING`, :const:`ROUND_HALF_EVEN`, " +"and various others." msgstr "" #: whatsnew/2.4.rst:643 @@ -977,10 +981,10 @@ msgstr "" #: whatsnew/2.4.rst:648 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::" +"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 "" #: whatsnew/2.4.rst:653 @@ -1147,8 +1151,8 @@ msgstr "" #: whatsnew/2.4.rst:756 msgid "" -"``PyOS_ascii_formatd(buffer, buf_len, format, d)`` converts a :c:expr:" -"`double` to an ASCII string." +"``PyOS_ascii_formatd(buffer, buf_len, format, d)`` converts " +"a :c:expr:`double` to an ASCII string." msgstr "" #: whatsnew/2.4.rst:759 @@ -1156,9 +1160,9 @@ msgid "" "The code for these functions came from the GLib library (`https://developer-" "old.gnome.org/glib/2.26/ `__), 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." +"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 "" #: whatsnew/2.4.rst:768 @@ -1207,9 +1211,9 @@ msgstr "" #: whatsnew/2.4.rst:792 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.)" +"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 "" #: whatsnew/2.4.rst:796 @@ -1221,9 +1225,9 @@ msgstr "" #: whatsnew/2.4.rst:800 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.) ::" +"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 "" #: whatsnew/2.4.rst:804 @@ -1236,9 +1240,9 @@ msgstr "" #: whatsnew/2.4.rst:809 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." +"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 "" #: whatsnew/2.4.rst:813 @@ -1246,8 +1250,8 @@ 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`." +"Previously this was the only parameter that could be provided " +"to :meth:`sort`." msgstr "" #: whatsnew/2.4.rst:818 @@ -1299,8 +1303,8 @@ msgstr "" #: whatsnew/2.4.rst:849 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)``." +"true, the list will be sorted into reverse order. Instead of ``L.sort(); " +"L.reverse()``, you can now write ``L.sort(reverse=True)``." msgstr "" #: whatsnew/2.4.rst:853 @@ -1363,8 +1367,8 @@ msgstr "" #: whatsnew/2.4.rst:1520 msgid "" -"Integer operations will no longer trigger an :exc:`OverflowWarning`. The :" -"exc:`OverflowWarning` warning will disappear in Python 2.5." +"Integer operations will no longer trigger an :exc:`OverflowWarning`. " +"The :exc:`OverflowWarning` warning will disappear in Python 2.5." msgstr "" #: whatsnew/2.4.rst:897 @@ -1386,9 +1390,9 @@ msgstr "" #: whatsnew/2.4.rst:907 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::" +"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 "" #: whatsnew/2.4.rst:912 @@ -1424,36 +1428,38 @@ msgstr "" 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.)" +"resulting in performance boosts " +"for :meth:`keys`, :meth:`values`, :meth:`items`, :meth:`iterkeys`, :meth:`itervalues`, " +"and :meth:`iteritems`. (Contributed by Raymond Hettinger.)" msgstr "" #: whatsnew/2.4.rst:942 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.)" +"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 "" #: whatsnew/2.4.rst:949 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.)" +"now run several times faster with non-sequence arguments that supply " +"a :meth:`__len__` method. (Contributed by Raymond Hettinger.)" msgstr "" #: whatsnew/2.4.rst:953 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.)" +"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 "" #: whatsnew/2.4.rst:960 @@ -1602,18 +1608,18 @@ msgstr "" msgid "" "The :mod:`ConfigParser ` classes have been enhanced slightly. " "The :meth:`~configparser.ConfigParser.read` method now returns a list of the " -"files that were successfully parsed, and the :meth:`~configparser." -"ConfigParser.set` method raises :exc:`TypeError` if passed a *value* " -"argument that isn't a string. (Contributed by John Belmonte and David " -"Goodger.)" +"files that were successfully parsed, and " +"the :meth:`~configparser.ConfigParser.set` method raises :exc:`TypeError` if " +"passed a *value* argument that isn't a string. (Contributed by John " +"Belmonte and David Goodger.)" msgstr "" #: whatsnew/2.4.rst:1060 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.)" +"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 "" #: whatsnew/2.4.rst:1065 @@ -1639,19 +1645,19 @@ msgstr "" 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.)" +"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 "" #: whatsnew/2.4.rst:1084 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.)" +"such as :const:`OK`, :const:`CREATED`, :const:`CONTINUE`, " +"and :const:`MOVED_PERMANENTLY`; use pydoc to get a full list. (Contributed " +"by Andrew Eland.)" msgstr "" #: whatsnew/2.4.rst:1090 @@ -1696,9 +1702,9 @@ msgstr "" #: whatsnew/2.4.rst:1118 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::" +":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 "" #: whatsnew/2.4.rst:1122 @@ -1761,19 +1767,19 @@ msgstr "" #: whatsnew/2.4.rst:1165 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.)" +"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 "" #: whatsnew/2.4.rst:1170 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::" +"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 "" #: whatsnew/2.4.rst:1176 @@ -1788,9 +1794,9 @@ msgstr "" 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` " +"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 "" @@ -1818,8 +1824,8 @@ 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::" +"or item; these callables make excellent data extractors when used " +"with :func:`map` or :func:`sorted`. For example::" msgstr "" #: whatsnew/2.4.rst:1205 @@ -1845,11 +1851,11 @@ msgstr "" #: whatsnew/2.4.rst:1221 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.)" +"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 "" #: whatsnew/2.4.rst:1227 @@ -1970,9 +1976,10 @@ msgstr "" #: whatsnew/2.4.rst:1298 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.)" +"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 "" #: whatsnew/2.4.rst:1302 @@ -2027,9 +2034,9 @@ msgstr "" #: whatsnew/2.4.rst:1338 msgid "" -":mod:`urllib2 ` has been changed to interact with :mod:" -"`cookielib `: :class:`HTTPCookieProcessor` manages a cookie " -"jar that is used when accessing URLs." +":mod:`urllib2 ` has been changed to interact " +"with :mod:`cookielib `: :class:`HTTPCookieProcessor` manages " +"a cookie jar that is used when accessing URLs." msgstr "" #: whatsnew/2.4.rst:1342 @@ -2043,9 +2050,9 @@ msgstr "" #: whatsnew/2.4.rst:1350 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" +"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 "" #: whatsnew/2.4.rst:1355 @@ -2139,9 +2146,9 @@ msgstr "" #: whatsnew/2.4.rst:1412 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::" +"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 "" #: whatsnew/2.4.rst:1417 @@ -2230,9 +2237,9 @@ msgstr "" #: whatsnew/2.4.rst:1476 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.)" +"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 "" #: whatsnew/2.4.rst:1480 @@ -2246,20 +2253,20 @@ msgstr "" #: whatsnew/2.4.rst:1485 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.)" +"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 "" #: whatsnew/2.4.rst:1495 msgid "" -"The :c:type:`!tracebackobject` type has been renamed to :c:type:" -"`PyTracebackObject`." +"The :c:type:`!tracebackobject` type has been renamed " +"to :c:type:`PyTracebackObject`." msgstr "" #: whatsnew/2.4.rst:1502 @@ -2344,8 +2351,8 @@ msgstr "" 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." +"silently. For example, you can no longer set a handler on " +"the :const:`SIGKILL` signal." msgstr "" #: whatsnew/2.4.rst:1560 diff --git a/whatsnew/2.5.po b/whatsnew/2.5.po index 923d797e5..466929549 100644 --- a/whatsnew/2.5.po +++ b/whatsnew/2.5.po @@ -54,10 +54,10 @@ msgid "" "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." +"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 "" #: whatsnew/2.5.rst:34 @@ -247,8 +247,8 @@ msgstr "" 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. ::" +"provided for the menu option is a partially applied version of " +"the :meth:`open_item` method, where the first argument has been provided. ::" msgstr "" #: whatsnew/2.5.rst:165 @@ -406,8 +406,8 @@ msgstr "" #: whatsnew/2.5.rst:274 msgid "" -"This defines a package named :mod:`pkg` containing the :mod:`pkg.main` and :" -"mod:`pkg.string` submodules." +"This defines a package named :mod:`pkg` containing the :mod:`pkg.main` " +"and :mod:`pkg.string` submodules." msgstr "" #: whatsnew/2.5.rst:277 @@ -415,9 +415,9 @@ 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." +"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 "" #: whatsnew/2.5.rst:284 @@ -434,11 +434,11 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.5.rst:299 @@ -469,10 +469,10 @@ msgstr "" #: 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::" +"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 "" #: whatsnew/2.5.rst:320 @@ -520,11 +520,11 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.5.rst:359 @@ -575,10 +575,10 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.5.rst:399 @@ -657,8 +657,8 @@ msgstr "" #: 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-" +"(: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``.)" @@ -668,8 +668,8 @@ msgstr "" 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`." +"the specified *value*. If the regular :meth:`next` method is called, " +"the :keyword:`!yield` returns :const:`None`." msgstr "" #: whatsnew/2.5.rst:463 @@ -737,19 +737,19 @@ msgstr "" 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." +"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 "" #: whatsnew/2.5.rst:512 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`." +"suggest using a ``try: ... finally:`` suite instead of " +"catching :exc:`GeneratorExit`." msgstr "" #: whatsnew/2.5.rst:515 @@ -774,21 +774,22 @@ msgid "" "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." +"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 "" #: whatsnew/2.5.rst:536 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." +"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 "" #: whatsnew/2.5.rst:544 @@ -855,8 +856,8 @@ msgstr "" #: whatsnew/2.5.rst:577 msgid "" "The expression is evaluated, and it should result in an object that supports " -"the context management protocol (that is, has :meth:`~object.__enter__` and :" -"meth:`~object.__exit__` methods." +"the context management protocol (that is, has :meth:`~object.__enter__` " +"and :meth:`~object.__exit__` methods." msgstr "" #: whatsnew/2.5.rst:581 @@ -869,9 +870,9 @@ msgstr "" #: whatsnew/2.5.rst:586 msgid "" -"After execution of the *with-block* is finished, the object's :meth:`~object." -"__exit__` method is called, even if the block raised an exception, and can " -"therefore run clean-up code." +"After execution of the *with-block* is finished, the " +"object's :meth:`~object.__exit__` method is called, even if the block raised " +"an exception, and can therefore run clean-up code." msgstr "" #: whatsnew/2.5.rst:590 @@ -912,8 +913,8 @@ msgstr "" #: whatsnew/2.5.rst:611 msgid "" -"In this case, *f* is the same object created by :func:`open`, because :meth:" -"`~object.__enter__` returns *self*." +"In this case, *f* is the same object created by :func:`open`, " +"because :meth:`~object.__enter__` returns *self*." msgstr "" #: whatsnew/2.5.rst:614 @@ -977,8 +978,8 @@ msgstr "" #: whatsnew/2.5.rst:654 msgid "" "The expression is evaluated and should result in an object called a " -"\"context manager\". The context manager must have :meth:`~object." -"__enter__` and :meth:`~object.__exit__` methods." +"\"context manager\". The context manager must " +"have :meth:`~object.__enter__` and :meth:`~object.__exit__` methods." msgstr "" #: whatsnew/2.5.rst:658 @@ -995,12 +996,12 @@ msgstr "" #: whatsnew/2.5.rst:664 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." +"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 "" #: whatsnew/2.5.rst:672 @@ -1042,8 +1043,8 @@ msgstr "" #: whatsnew/2.5.rst:693 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::" +"or rolled back if there's an exception. Here's the basic interface " +"for :class:`DatabaseConnection` that I'll assume::" msgstr "" #: whatsnew/2.5.rst:697 @@ -1124,8 +1125,8 @@ msgid "" "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:`~object.__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 " +"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:`~object.__exit__` " "method. Any exception raised in the block will be raised by the :keyword:`!" "yield` statement." @@ -1235,12 +1236,12 @@ msgstr "" #: whatsnew/2.5.rst:828 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::" +"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 "" #: whatsnew/2.5.rst:835 @@ -1318,9 +1319,9 @@ msgstr "" 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." +"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 "" #: whatsnew/2.5.rst:894 @@ -1339,19 +1340,21 @@ msgstr "" #: whatsnew/2.5.rst:904 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`." +"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 "" #: whatsnew/2.5.rst:910 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:expr:`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`." +"new conversion code, ``n``, " +"for :c:type:`Py_ssize_t`. :c:func:`PyArg_ParseTuple`'s ``s#`` and ``t#`` " +"still output :c:expr:`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 "" #: whatsnew/2.5.rst:916 @@ -1386,9 +1389,9 @@ msgstr "" #: whatsnew/2.5.rst:941 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." +"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 "" #: whatsnew/2.5.rst:946 @@ -1408,8 +1411,8 @@ msgstr "" #: whatsnew/2.5.rst:953 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." +"interpreter will check that the type returned is correct, and raises " +"a :exc:`TypeError` if this requirement isn't met." msgstr "" #: whatsnew/2.5.rst:957 @@ -1443,9 +1446,9 @@ 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::" +"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 "" #: whatsnew/2.5.rst:985 @@ -1543,11 +1546,11 @@ msgstr "" #: whatsnew/2.5.rst:1045 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.)" +"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 "" #: whatsnew/2.5.rst:1052 @@ -1556,8 +1559,8 @@ msgid "" "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)." +"return non-negative numbers, and users often seem to use ``id(self)`` " +"in :meth:`__hash__` methods (though this is discouraged)." msgstr "" #: whatsnew/2.5.rst:1061 @@ -1618,12 +1621,12 @@ 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.)" +"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 "" #: whatsnew/2.5.rst:1102 @@ -1689,11 +1692,11 @@ msgstr "" #: whatsnew/2.5.rst:1147 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.)" +"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 "" #: whatsnew/2.5.rst:1153 @@ -1720,8 +1723,8 @@ msgid "" "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.)" +"iteration and these methods will now trigger a :exc:`ValueError` from " +"the :meth:`!read\\*` method. (Implemented by Thomas Wouters.)" msgstr "" #: whatsnew/2.5.rst:1178 @@ -1734,8 +1737,9 @@ msgstr "" #: whatsnew/2.5.rst:1182 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.)" +"allocator functions instead of the system's :c:func:`malloc` " +"and :c:func:`free`. (Contributed by Jack Diederich at the NeedForSpeed " +"sprint.)" msgstr "" #: whatsnew/2.5.rst:1186 @@ -1793,16 +1797,15 @@ msgstr "" #: whatsnew/2.5.rst:1228 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.)" +"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 "" #: whatsnew/2.5.rst:1240 @@ -1854,10 +1857,11 @@ msgstr "" #: whatsnew/2.5.rst:1271 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.)" +"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 "" #: whatsnew/2.5.rst:1276 @@ -1890,12 +1894,12 @@ msgstr "" 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." +"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 "" #: whatsnew/2.5.rst:1301 @@ -1947,10 +1951,10 @@ msgstr "" #: whatsnew/2.5.rst:1330 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.)" +"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 "" #: whatsnew/2.5.rst:1337 @@ -1963,12 +1967,12 @@ msgstr "" 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:" -"`~fileinput.fileno` returns the file descriptor for the currently opened " -"file. (Contributed by Georg Brandl.)" +"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:`~fileinput.fileno` returns the file descriptor for the currently " +"opened file. (Contributed by Georg Brandl.)" msgstr "" #: whatsnew/2.5.rst:1354 @@ -2035,9 +2039,9 @@ msgstr "" #: whatsnew/2.5.rst:1393 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." +"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 "" #: whatsnew/2.5.rst:1397 @@ -2082,9 +2086,10 @@ msgstr "" #: whatsnew/2.5.rst:1425 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.)" +"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 "" #: whatsnew/2.5.rst:1429 @@ -2097,11 +2102,11 @@ msgstr "" #: whatsnew/2.5.rst:1433 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.)" +"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 "" #: whatsnew/2.5.rst:1440 @@ -2115,19 +2120,19 @@ msgstr "" #: whatsnew/2.5.rst:1445 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.)" +"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 "" #: whatsnew/2.5.rst:1451 msgid "" -"Constants named :const:`os.SEEK_SET`, :const:`os.SEEK_CUR`, and :const:`os." -"SEEK_END` have been added; these are the parameters to the :func:`os.lseek` " -"function. Two new constants for locking are :const:`os.O_SHLOCK` and :const:" -"`os.O_EXLOCK`." +"Constants named :const:`os.SEEK_SET`, :const:`os.SEEK_CUR`, " +"and :const:`os.SEEK_END` have been added; these are the parameters to " +"the :func:`os.lseek` function. Two new constants for locking " +"are :const:`os.O_SHLOCK` and :const:`os.O_EXLOCK`." msgstr "" #: whatsnew/2.5.rst:1456 @@ -2145,9 +2150,9 @@ msgstr "" #: whatsnew/2.5.rst:1465 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ò.)" +"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 "" #: whatsnew/2.5.rst:1472 @@ -2178,9 +2183,9 @@ msgstr "" #: whatsnew/2.5.rst:1490 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 " +"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 " @@ -2206,8 +2211,8 @@ msgstr "" #: whatsnew/2.5.rst:1507 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`." +"ever since Python 2.0, have finally been deleted. Other deleted " +"modules: :mod:`statcache`, :mod:`tzparse`, :mod:`whrandom`." msgstr "" #: whatsnew/2.5.rst:1511 @@ -2220,9 +2225,9 @@ msgstr "" #: whatsnew/2.5.rst:1516 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.)" +"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 "" #: whatsnew/2.5.rst:1522 @@ -2239,8 +2244,8 @@ 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 " +"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 "" @@ -2255,9 +2260,9 @@ msgstr "" #: whatsnew/2.5.rst:1541 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." +"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 "" #: whatsnew/2.5.rst:1545 @@ -2268,12 +2273,12 @@ msgstr "" #: whatsnew/2.5.rst:1548 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::" +"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 "" #: whatsnew/2.5.rst:1555 @@ -2310,10 +2315,10 @@ msgstr "" #: whatsnew/2.5.rst:1575 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.)" +"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 "" #: whatsnew/2.5.rst:1580 @@ -2326,11 +2331,11 @@ msgstr "" #: whatsnew/2.5.rst:1585 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." +"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 "" #: whatsnew/2.5.rst:1590 @@ -2393,35 +2398,35 @@ msgstr "" #: whatsnew/2.5.rst:1634 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.)" +"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 "" #: whatsnew/2.5.rst:1641 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.)" +"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 "" #: whatsnew/2.5.rst:1653 msgid "" -"The :mod:`xmlrpclib ` module now supports returning :class:" -"`~datetime.datetime` objects for the XML-RPC date type. Supply " -"``use_datetime=True`` to the :func:`~xmlrpc.client.loads` function or the :" -"class:`!Unmarshaller` class to enable this feature. (Contributed by Skip " -"Montanaro.)" +"The :mod:`xmlrpclib ` module now supports " +"returning :class:`~datetime.datetime` objects for the XML-RPC date type. " +"Supply ``use_datetime=True`` to the :func:`~xmlrpc.client.loads` function " +"or the :class:`!Unmarshaller` class to enable this feature. (Contributed by " +"Skip Montanaro.)" msgstr "" #: whatsnew/2.5.rst:1660 @@ -2454,10 +2459,10 @@ msgstr "" #: whatsnew/2.5.rst:1687 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. ::" +"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 "" #: whatsnew/2.5.rst:1692 @@ -2470,14 +2475,15 @@ msgstr "" #: whatsnew/2.5.rst:1697 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:expr:`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.)" +"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:expr:`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 "" #: whatsnew/2.5.rst:1706 @@ -2497,8 +2503,8 @@ msgstr "" #: whatsnew/2.5.rst:1715 msgid "" -"C functions are assumed to return integers, but you can set the :attr:" -"`restype` attribute of the function object to change this::" +"C functions are assumed to return integers, but you can set " +"the :attr:`restype` attribute of the function object to change this::" msgstr "" #: whatsnew/2.5.rst:1718 @@ -2512,12 +2518,12 @@ msgstr "" #: whatsnew/2.5.rst:1724 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:`~ctypes.py_object` type " -"constructor that will create a :c:expr:`PyObject *` pointer. A simple " -"usage::" +":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:`~ctypes.py_object` type constructor that will create " +"a :c:expr:`PyObject *` pointer. A simple usage::" msgstr "" #: whatsnew/2.5.rst:1730 @@ -2539,10 +2545,10 @@ msgstr "" #: whatsnew/2.5.rst:1740 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." +"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 "" #: whatsnew/2.5.rst:1749 @@ -2608,8 +2614,8 @@ msgstr "" #: whatsnew/2.5.rst:1790 msgid "" -"Once you have an :class:`ElementTree` instance, you can call its :meth:" -"`getroot` method to get the root :class:`Element` node." +"Once you have an :class:`ElementTree` instance, you can call " +"its :meth:`getroot` method to get the root :class:`Element` node." msgstr "" #: whatsnew/2.5.rst:1793 @@ -2741,8 +2747,8 @@ msgstr "" #: whatsnew/2.5.rst:1837 msgid "" -"Comments and processing instructions are also represented as :class:" -"`Element` nodes. To check if a node is a comment or processing " +"Comments and processing instructions are also represented " +"as :class:`Element` nodes. To check if a node is a comment or processing " "instructions::" msgstr "" @@ -3035,9 +3041,9 @@ msgstr "" #: whatsnew/2.5.rst:2042 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." +"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 "" #: whatsnew/2.5.rst:2049 @@ -3104,9 +3110,9 @@ msgstr "" #: whatsnew/2.5.rst:2094 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:expr:" -"`int`. See the earlier section :ref:`pep-353` for a discussion of this " -"change." +"interpreter to use a :c:type:`Py_ssize_t` type definition instead " +"of :c:expr:`int`. See the earlier section :ref:`pep-353` for a discussion " +"of this change." msgstr "" #: whatsnew/2.5.rst:2099 @@ -3119,9 +3125,9 @@ msgstr "" #: whatsnew/2.5.rst:2104 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::" +"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 "" #: whatsnew/2.5.rst:2108 @@ -3138,13 +3144,13 @@ msgstr "" #: whatsnew/2.5.rst:2117 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 " +"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." @@ -3174,31 +3180,32 @@ msgstr "" 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." +"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 "" #: whatsnew/2.5.rst:2152 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 ``PyMem`` function but freed " -"it with the ``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." +"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 " +"``PyMem`` function but freed it with the ``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 "" #: whatsnew/2.5.rst:2159 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.)" +"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 "" #: whatsnew/2.5.rst:2165 @@ -3216,9 +3223,9 @@ msgid "" "``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 macro :c:macro:`!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 " +"be inlined. If macro :c:macro:`!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 "" @@ -3265,14 +3272,14 @@ msgstr "" #: whatsnew/2.5.rst:2210 msgid "" -"MacOS X (10.3 and higher): dynamic loading of modules now uses the :c:func:" -"`dlopen` function instead of MacOS-specific functions." +"MacOS X (10.3 and higher): dynamic loading of modules now uses " +"the :c:func:`dlopen` function instead of MacOS-specific functions." msgstr "" #: whatsnew/2.5.rst:2213 msgid "" -"MacOS X: an :option:`!--enable-universalsdk` switch was added to the :" -"program:`configure` script that compiles the interpreter as a universal " +"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 "" @@ -3305,8 +3312,9 @@ msgstr "" #: whatsnew/2.5.rst:2238 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``." +"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 "" #: whatsnew/2.5.rst:2242 @@ -3343,11 +3351,12 @@ msgstr "" #: whatsnew/2.5.rst:2261 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." +"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 "" #: whatsnew/2.5.rst:2267 diff --git a/whatsnew/2.6.po b/whatsnew/2.6.po index 2a13d334b..544139084 100644 --- a/whatsnew/2.6.po +++ b/whatsnew/2.6.po @@ -41,8 +41,9 @@ msgid "" "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." +"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 "" #: whatsnew/2.6.rst:62 @@ -103,8 +104,8 @@ msgstr "" #: whatsnew/2.6.rst:106 msgid "" -"The addition of :func:`functools.reduce` as a synonym for the built-in :func:" -"`reduce` function." +"The addition of :func:`functools.reduce` as a synonym for the built-" +"in :func:`reduce` function." msgstr "" #: whatsnew/2.6.rst:109 @@ -122,16 +123,17 @@ 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`." +"switch is available to Python code as the boolean " +"variable :data:`sys.py3kwarning`, and to C extension code " +"as :c:data:`Py_Py3kWarningFlag`." msgstr "" #: whatsnew/2.6.rst:126 msgid "" -"The 3\\ *xxx* 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." +"The 3\\ *xxx* 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 "" #: whatsnew/2.6.rst:134 @@ -164,8 +166,8 @@ msgid "" "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 " +"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 " @@ -187,8 +189,8 @@ 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 ``https://svn." -"python.org/view/tracker/importer/`` and may be useful to other projects " +"SourceForge; his scripts for this import operation are at ``https://" +"svn.python.org/view/tracker/importer/`` and may be useful to other projects " "wishing to move from SourceForge to Roundup." msgstr "" @@ -268,9 +270,9 @@ msgstr "" #: whatsnew/2.6.rst:226 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." +"dozen other projects (`listed on the Sphinx web site `__) have adopted Sphinx as their " +"documentation tool." msgstr "" #: whatsnew/2.6.rst:233 @@ -336,8 +338,8 @@ msgstr "" #: whatsnew/2.6.rst:269 msgid "" "The expression is evaluated, and it should result in an object that supports " -"the context management protocol (that is, has :meth:`~object.__enter__` and :" -"meth:`~object.__exit__` methods)." +"the context management protocol (that is, has :meth:`~object.__enter__` " +"and :meth:`~object.__exit__` methods)." msgstr "" #: whatsnew/2.6.rst:273 @@ -350,9 +352,9 @@ msgstr "" #: whatsnew/2.6.rst:278 msgid "" -"After execution of the *with-block* is finished, the object's :meth:`~object." -"__exit__` method is called, even if the block raised an exception, and can " -"therefore run clean-up code." +"After execution of the *with-block* is finished, the " +"object's :meth:`~object.__exit__` method is called, even if the block raised " +"an exception, and can therefore run clean-up code." msgstr "" #: whatsnew/2.6.rst:282 @@ -379,8 +381,8 @@ msgstr "" #: whatsnew/2.6.rst:296 msgid "" -"In this case, *f* is the same object created by :func:`open`, because :meth:" -"`~object.__enter__` returns *self*." +"In this case, *f* is the same object created by :func:`open`, " +"because :meth:`~object.__enter__` returns *self*." msgstr "" #: whatsnew/2.6.rst:299 @@ -444,8 +446,8 @@ msgstr "" #: whatsnew/2.6.rst:339 msgid "" "The expression is evaluated and should result in an object called a " -"\"context manager\". The context manager must have :meth:`~object." -"__enter__` and :meth:`~object.__exit__` methods." +"\"context manager\". The context manager must " +"have :meth:`~object.__enter__` and :meth:`~object.__exit__` methods." msgstr "" #: whatsnew/2.6.rst:343 @@ -461,15 +463,15 @@ msgstr "" #: whatsnew/2.6.rst:349 msgid "" -"If *BLOCK* raises an exception, the context manager's :meth:`~object." -"__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." +"If *BLOCK* raises an exception, the context " +"manager's :meth:`~object.__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 "" #: whatsnew/2.6.rst:358 @@ -511,8 +513,8 @@ msgstr "" #: whatsnew/2.6.rst:379 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::" +"or rolled back if there's an exception. Here's the basic interface " +"for :class:`DatabaseConnection` that I'll assume::" msgstr "" #: whatsnew/2.6.rst:383 @@ -592,8 +594,8 @@ msgid "" "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:`~object.__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 " +"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:`~object.__exit__` " "method. Any exception raised in the block will be raised by the :keyword:`!" "yield` statement." @@ -738,9 +740,9 @@ 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." +"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 "" #: whatsnew/2.6.rst:544 @@ -772,14 +774,15 @@ msgstr "" #: whatsnew/2.6.rst:567 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 " +"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." +"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 "" #: whatsnew/2.6.rst:577 @@ -837,10 +840,10 @@ 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::" +"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 "" #: whatsnew/2.6.rst:630 @@ -997,8 +1000,8 @@ msgstr "" #: whatsnew/2.6.rst:744 msgid "" ">>> import sys\n" -">>> print 'Platform: {0.platform}\\nPython version: {0.version}'." -"format(sys)\n" +">>> print 'Platform: {0.platform}\\nPython version: " +"{0.version}'.format(sys)\n" "Platform: darwin\n" "Python version: 2.6a1+ (trunk:61261M, Mar 5 2008, 20:29:41)\n" "[GCC 4.0.1 (Apple Computer, Inc. build 5367)]'\n" @@ -1326,11 +1329,12 @@ msgstr "" #: whatsnew/2.6.rst:902 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::" +"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 "" #: whatsnew/2.6.rst:909 @@ -1387,10 +1391,10 @@ msgstr "" #: whatsnew/2.6.rst:945 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." +"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 "" #: whatsnew/2.6.rst:952 @@ -1398,8 +1402,8 @@ 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." +"2.6, ``bytes([65, 66, 67])`` returns the 12-byte string representing " +"the :func:`str` of the list." msgstr "" #: whatsnew/2.6.rst:958 @@ -1407,9 +1411,9 @@ 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." +"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 "" #: whatsnew/2.6.rst:965 @@ -1433,10 +1437,9 @@ msgstr "" 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." +"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 "" #: whatsnew/2.6.rst:984 @@ -1461,9 +1464,10 @@ msgstr "" #: whatsnew/2.6.rst:999 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`." +"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 "" #: whatsnew/2.6.rst:1006 @@ -1477,8 +1481,9 @@ msgstr "" #: whatsnew/2.6.rst:1012 msgid "" -"There's also a corresponding C API, with :c:func:`PyByteArray_FromObject`, :" -"c:func:`PyByteArray_FromStringAndSize`, and various other functions." +"There's also a corresponding C API, " +"with :c:func:`PyByteArray_FromObject`, :c:func:`PyByteArray_FromStringAndSize`, " +"and various other functions." msgstr "" #: whatsnew/2.6.rst:1019 @@ -1497,10 +1502,10 @@ msgstr "" 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." +"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 "" #: whatsnew/2.6.rst:1037 @@ -1511,12 +1516,12 @@ msgstr "" #: whatsnew/2.6.rst:1040 msgid "" -":class:`RawIOBase` defines raw I/O operations: :meth:`read`, :meth:" -"`readinto`, :meth:`write`, :meth:`seek`, :meth:`tell`, :meth:`truncate`, " +":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." +"single system call. There are also :meth:`readable`, :meth:`writable`, " +"and :meth:`seekable` methods for determining what operations a given object " +"will allow." msgstr "" #: whatsnew/2.6.rst:1048 @@ -1529,37 +1534,37 @@ msgstr "" 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." +"efficient. It supports all of the methods of :class:`RawIOBase`, and adds " +"a :attr:`raw` attribute holding the underlying raw object." msgstr "" #: whatsnew/2.6.rst:1058 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." +"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 "" #: whatsnew/2.6.rst:1071 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." +"(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 "" #: whatsnew/2.6.rst:1077 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." +"a :attr:`buffer` attribute for access to the underlying " +"object. :class:`StringIO` simply buffers everything in memory without ever " +"writing anything to disk." msgstr "" #: whatsnew/2.6.rst:1083 @@ -1686,19 +1691,19 @@ msgid "" "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`?" +"the iterative variants such as :meth:`iterkeys`? :meth:`copy` " +"and :meth:`update`? Iterating over the object with :func:`iter`?" msgstr "" #: whatsnew/2.6.rst:1178 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." +"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 "" #: whatsnew/2.6.rst:1187 @@ -1734,11 +1739,11 @@ msgstr "" #: whatsnew/2.6.rst:1207 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::" +"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 "" #: whatsnew/2.6.rst:1214 @@ -1810,18 +1815,19 @@ 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." +"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 "" #: whatsnew/2.6.rst:1266 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::" +"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 "" #: whatsnew/2.6.rst:1272 @@ -1982,8 +1988,8 @@ msgstr "" #: whatsnew/2.6.rst:1386 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." +"Scheme's numeric tower. These classes were backported to 2.6 as " +"the :mod:`numbers` module." msgstr "" #: whatsnew/2.6.rst:1390 @@ -2013,9 +2019,9 @@ msgstr "" 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`.)" +"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 "" #: whatsnew/2.6.rst:1412 @@ -2028,11 +2034,11 @@ msgstr "" #: whatsnew/2.6.rst:1417 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." +"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 "" #: whatsnew/2.6.rst:1425 @@ -2140,10 +2146,10 @@ 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`.)" +"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 "" #: whatsnew/2.6.rst:1498 @@ -2194,8 +2200,9 @@ msgstr "" 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`.)" +"returned if *iterator* has been exhausted; otherwise, " +"the :exc:`StopIteration` exception will be raised. (Backported " +"in :issue:`2719`.)" msgstr "" #: whatsnew/2.6.rst:1531 @@ -2227,10 +2234,10 @@ msgstr "" #: whatsnew/2.6.rst:1549 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::" +"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 "" #: whatsnew/2.6.rst:1554 @@ -2260,9 +2267,9 @@ msgstr "" #: whatsnew/2.6.rst:1576 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`." +"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 "" #: whatsnew/2.6.rst:1584 @@ -2283,15 +2290,15 @@ 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`.)" +"platform with IEEE 754 semantics. (Contributed by Christian " +"Heimes; :issue:`1635`.)" msgstr "" #: whatsnew/2.6.rst:1598 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`)" +"return true if their floating-point argument is infinite or Not A Number. " +"(:issue:`1640`)" msgstr "" #: whatsnew/2.6.rst:1602 @@ -2339,9 +2346,9 @@ msgid "" "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`.)" +"C level, extensions can set ``tp_hash`` " +"to :c:func:`PyObject_HashNotImplemented`. (Fixed by Nick Coghlan and Amaury " +"Forgeot d'Arc; :issue:`2235`.)" msgstr "" #: whatsnew/2.6.rst:1640 @@ -2355,8 +2362,8 @@ msgstr "" #: whatsnew/2.6.rst:1646 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`.)" +"original code object backing the generator. (Contributed by Collin " +"Winter; :issue:`1473257`.)" msgstr "" #: whatsnew/2.6.rst:1650 @@ -2369,8 +2376,8 @@ msgstr "" 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`)" +"values. For example, ``complex('(3+4j)')`` now returns the value (3+4j). " +"(:issue:`1491866`)" msgstr "" #: whatsnew/2.6.rst:1659 @@ -2378,8 +2385,8 @@ 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`.)" +"(Contributed by Bengt Richter and implemented by Raymond " +"Hettinger; :issue:`1193128`.)" msgstr "" #: whatsnew/2.6.rst:1665 @@ -2387,26 +2394,26 @@ 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`)" +"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 "" #: whatsnew/2.6.rst:1673 msgid "" "Instance method objects have new attributes for the object and function " -"comprising the method; the new synonym for :attr:`!im_self` is :attr:" -"`~method.__self__`, and :attr:`!im_func` is also available as :attr:`~method." -"__func__`. The old names are still supported in Python 2.6, but are gone in " -"3.0." +"comprising the method; the new synonym for :attr:`!im_self` " +"is :attr:`~method.__self__`, and :attr:`!im_func` is also available " +"as :attr:`~method.__func__`. The old names are still supported in Python " +"2.6, but are gone in 3.0." msgstr "" #: whatsnew/2.6.rst:1679 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.)" +"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 "" #: whatsnew/2.6.rst:1688 @@ -2417,8 +2424,8 @@ msgstr "" 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`.)" +"startup faster. (Contributed by Neal Norwitz and Brett " +"Cannon; :issue:`1631171`.)" msgstr "" #: whatsnew/2.6.rst:1695 @@ -2469,9 +2476,9 @@ msgstr "" #: whatsnew/2.6.rst:1729 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." +"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 "" #: whatsnew/2.6.rst:1735 @@ -2574,8 +2581,8 @@ msgstr "" 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`)." +"versions still available in the :mod:`!cgi` module will " +"trigger :exc:`PendingDeprecationWarning` messages in 2.6 (:issue:`600362`)." msgstr "" #: whatsnew/2.6.rst:1815 @@ -2619,8 +2626,8 @@ 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." +"See :issue:`1381` for the details. The branch cuts " +"for :func:`asinh`, :func:`atanh`: and :func:`atan` have also been corrected." msgstr "" #: whatsnew/2.6.rst:1841 @@ -2667,9 +2674,9 @@ msgstr "" #: whatsnew/2.6.rst:1870 msgid "" "Several places in the standard library that returned tuples have been " -"modified to return :func:`namedtuple` instances. For example, the :meth:" -"`Decimal.as_tuple` method now returns a named tuple with :attr:`sign`, :attr:" -"`digits`, and :attr:`exponent` fields." +"modified to return :func:`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 "" #: whatsnew/2.6.rst:1877 @@ -2699,8 +2706,8 @@ msgid "" "The :mod:`Cookie ` module's :class:`~http.cookies.Morsel` " "objects now support an :attr:`~http.cookies.Morsel.httponly` attribute. In " "some browsers. cookies with this attribute set cannot be accessed or " -"manipulated by JavaScript code. (Contributed by Arvin Schnell; :issue:" -"`1638033`.)" +"manipulated by JavaScript code. (Contributed by Arvin " +"Schnell; :issue:`1638033`.)" msgstr "" #: whatsnew/2.6.rst:1903 @@ -2721,16 +2728,16 @@ msgstr "" 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." +"supplying a true value for the *insert_mode* parameter when creating " +"the :class:`Textbox` instance." msgstr "" #: whatsnew/2.6.rst:1918 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`.)" +"padded on the left to six places. (Contributed by Skip " +"Montanaro; :issue:`1158`.)" msgstr "" #: whatsnew/2.6.rst:1923 @@ -2773,20 +2780,21 @@ msgstr "" #: whatsnew/2.6.rst:1946 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`.)" +"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 "" #: whatsnew/2.6.rst:1954 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`.)" +"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 "" #: whatsnew/2.6.rst:1960 @@ -2801,8 +2809,8 @@ msgstr "" #: whatsnew/2.6.rst:1966 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`)" +"path was used and Unicode filenames are matched within the directory. " +"(:issue:`1001604`)" msgstr "" #: whatsnew/2.6.rst:1970 @@ -2829,17 +2837,18 @@ msgstr "" #: whatsnew/2.6.rst:1983 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.)" +"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 "" #: whatsnew/2.6.rst:1989 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.)" +"was added to the :class:`httplib.HTTPConnection " +"` and :class:`HTTPSConnection " +"` class constructors. (Added by Facundo " +"Batista.)" msgstr "" #: whatsnew/2.6.rst:1994 @@ -2852,8 +2861,9 @@ msgstr "" #: whatsnew/2.6.rst:2000 msgid "" -"Some new functions in the module include :func:`isgenerator`, :func:" -"`isgeneratorfunction`, and :func:`isabstract`." +"Some new functions in the module " +"include :func:`isgenerator`, :func:`isgeneratorfunction`, " +"and :func:`isabstract`." msgstr "" #: whatsnew/2.6.rst:2004 @@ -2951,10 +2961,11 @@ msgstr "" #: whatsnew/2.6.rst:2060 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. ::" +"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 "" #: whatsnew/2.6.rst:2067 @@ -2969,11 +2980,12 @@ msgstr "" #: whatsnew/2.6.rst:2072 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.)" +"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 "" #: whatsnew/2.6.rst:2079 @@ -3025,9 +3037,10 @@ msgstr "" #: whatsnew/2.6.rst:2108 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>`__." +":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 "" #: whatsnew/2.6.rst:2113 @@ -3045,8 +3058,8 @@ msgid "" "``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`.)" +"standard recommends signaling 'overflow', Python will " +"raise :exc:`OverflowError`. (See :issue:`711019` and :issue:`1640`.)" msgstr "" #: whatsnew/2.6.rst:2127 @@ -3147,16 +3160,16 @@ 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`)" +"now returns ``('.ipython', '')`` instead of ``('', '.ipython')``. " +"(:issue:`1115886`)" msgstr "" #: whatsnew/2.6.rst:2196 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`.)" +"directory to the destination ``path``. (Contributed by Richard " +"Barran; :issue:`1339796`.)" msgstr "" #: whatsnew/2.6.rst:2201 @@ -3216,9 +3229,9 @@ msgstr "" #: whatsnew/2.6.rst:2238 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`.)" +"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 "" #: whatsnew/2.6.rst:2243 @@ -3273,10 +3286,11 @@ msgstr "" #: whatsnew/2.6.rst:2280 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`.)" +"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 "" #: whatsnew/2.6.rst:2286 @@ -3332,11 +3346,11 @@ msgstr "" #: whatsnew/2.6.rst:2322 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." +"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 "" #: whatsnew/2.6.rst:2330 @@ -3373,8 +3387,8 @@ msgstr "" 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`.)" +"agents that don't manage a mail queue. (LMTP implemented by Leif " +"Hedstrom; :issue:`957003`.)" msgstr "" #: whatsnew/2.6.rst:2356 @@ -3406,12 +3420,12 @@ msgstr "" msgid "" "The base classes in the :mod:`SocketServer ` module now " "support calling a :meth:`~socketserver.BaseServer.handle_timeout` method " -"after a span of inactivity specified by the server's :attr:`~socketserver." -"BaseServer.timeout` attribute. (Contributed by Michael Pomraning.) The :" -"meth:`~socketserver.BaseServer.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`.)" +"after a span of inactivity specified by the " +"server's :attr:`~socketserver.BaseServer.timeout` attribute. (Contributed " +"by Michael Pomraning.) The :meth:`~socketserver.BaseServer.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 "" #: whatsnew/2.6.rst:2383 @@ -3429,10 +3443,11 @@ msgstr "" #: whatsnew/2.6.rst:2391 msgid "" "The :class:`~subprocess.Popen` objects provided by the :mod:`subprocess` " -"module now have :meth:`~subprocess.Popen.terminate`, :meth:`~subprocess." -"Popen.kill`, and :meth:`~subprocess.Popen.send_signal` methods. On Windows, :" -"meth:`!send_signal` only supports the :py:const:`~signal.SIGTERM` signal, " -"and all these methods are aliases for the Win32 API function :c:func:`!" +"module now " +"have :meth:`~subprocess.Popen.terminate`, :meth:`~subprocess.Popen.kill`, " +"and :meth:`~subprocess.Popen.send_signal` methods. On Windows, :meth:`!" +"send_signal` only supports the :py:const:`~signal.SIGTERM` signal, and all " +"these methods are aliases for the Win32 API function :c:func:`!" "TerminateProcess`. (Contributed by Christian Heimes.)" msgstr "" @@ -3440,10 +3455,10 @@ msgstr "" 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`.)" +"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 "" #: whatsnew/2.6.rst:2406 @@ -3471,9 +3486,9 @@ msgstr "" 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`.)" +"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 "" #: whatsnew/2.6.rst:2432 @@ -3547,17 +3562,18 @@ msgstr "" #: whatsnew/2.6.rst:2476 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`.)" +"both work as context managers, so you can write ``with " +"tempfile.NamedTemporaryFile() as tmp: ...``. (Contributed by Alexander " +"Belopolsky; :issue:`2021`.)" msgstr "" #: whatsnew/2.6.rst:2481 msgid "" "The :mod:`test.test_support ` module gained a number of " -"context managers useful for writing tests. :func:`~test.support.os_helper." -"EnvironmentVarGuard` is a context manager that temporarily changes " -"environment variables and automatically restores them to their old values." +"context managers useful for writing " +"tests. :func:`~test.support.os_helper.EnvironmentVarGuard` is a context " +"manager that temporarily changes environment variables and automatically " +"restores them to their old values." msgstr "" #: whatsnew/2.6.rst:2487 @@ -3626,22 +3642,22 @@ msgstr "" #: whatsnew/2.6.rst:2531 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.)" +"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 "" #: whatsnew/2.6.rst:2542 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`.)" +"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 "" #: whatsnew/2.6.rst:2547 @@ -3650,8 +3666,8 @@ msgid "" "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`.)" +"instance and call the corresponding method. (Contributed by Erik " +"Demaine; :issue:`1533909`.)" msgstr "" #: whatsnew/2.6.rst:2556 @@ -3755,14 +3771,14 @@ msgstr "" #: whatsnew/2.6.rst:2607 msgid "" -"The XML-RPC :class:`SimpleXMLRPCServer ` and :class:" -"`DocXMLRPCServer ` classes can now be prevented from " -"immediately opening and binding to their socket by passing ``False`` 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`.)" +"The XML-RPC :class:`SimpleXMLRPCServer ` " +"and :class:`DocXMLRPCServer ` classes can now be prevented " +"from immediately opening and binding to their socket by passing ``False`` 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 "" #: whatsnew/2.6.rst:2616 @@ -3779,14 +3795,14 @@ msgstr "" #: whatsnew/2.6.rst:2624 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:`~datetime.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`)." +"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:`~datetime.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 "" #: whatsnew/2.6.rst:2634 @@ -3840,8 +3856,9 @@ msgstr "" #: whatsnew/2.6.rst:2671 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::" +"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 "" #: whatsnew/2.6.rst:2675 @@ -3955,8 +3972,8 @@ msgstr "" #: whatsnew/2.6.rst:2761 msgid "" -"``hex(value)``, ``oct(value)``: instead of calling the :meth:`__hex__` or :" -"meth:`__oct__` methods, these versions will call the :meth:`__index__` " +"``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 "" @@ -4072,10 +4089,10 @@ msgstr "" #: whatsnew/2.6.rst:2853 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." +"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 "" #: whatsnew/2.6.rst:2860 @@ -4096,8 +4113,8 @@ msgstr "" #: whatsnew/2.6.rst:2870 msgid "" -"The Win32 LastError variable is similarly supported by the :func:`DLL`, :" -"func:`OleDLL`, and :func:`WinDLL` functions. You supply " +"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 "" @@ -4142,8 +4159,8 @@ msgstr "" #: whatsnew/2.6.rst:3262 msgid "" -"String exceptions have been removed. Attempting to use them raises a :exc:" -"`TypeError`." +"String exceptions have been removed. Attempting to use them raises " +"a :exc:`TypeError`." msgstr "" #: whatsnew/2.6.rst:2911 @@ -4162,13 +4179,13 @@ msgstr "" #: whatsnew/2.6.rst:2921 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`." +"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 "" #: whatsnew/2.6.rst:2946 @@ -4226,8 +4243,8 @@ msgstr "" #: whatsnew/2.6.rst:2978 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 " +"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 "" @@ -4240,11 +4257,11 @@ msgstr "" #: whatsnew/2.6.rst:2988 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.)" +"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 "" #: whatsnew/2.6.rst:2995 @@ -4286,9 +4303,10 @@ msgstr "" #: whatsnew/2.6.rst:3021 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.)" +"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 "" #: whatsnew/2.6.rst:3026 @@ -4316,11 +4334,11 @@ msgstr "" #: whatsnew/2.6.rst:3044 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.)" +"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 "" #: whatsnew/2.6.rst:3052 @@ -4355,25 +4373,26 @@ msgstr "" 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.)" +"finally defines standard macros for adding values to a " +"module, :c:macro:`PyModule_AddStringMacro` " +"and :c:macro:`PyModule_AddIntMacro()`. (Contributed by Christian Heimes.)" msgstr "" #: whatsnew/2.6.rst:3082 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`)" +"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 "" #: whatsnew/2.6.rst:3091 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`.)" +"running on a debug version of Python. (Contributed by Collin " +"Winter; :issue:`1530959`.)" msgstr "" #: whatsnew/2.6.rst:3095 @@ -4442,35 +4461,35 @@ msgstr "" #: whatsnew/2.6.rst:3142 msgid "" -"The :mod:`socket` module's socket objects now have an :meth:`~socket.socket." -"ioctl` method that provides a limited interface to the :c:func:`WSAIoctl` " -"system interface." +"The :mod:`socket` module's socket objects now have " +"an :meth:`~socket.socket.ioctl` method that provides a limited interface to " +"the :c:func:`WSAIoctl` system interface." msgstr "" #: whatsnew/2.6.rst:3146 msgid "" -"The :mod:`_winreg ` module now has a function, :func:`~winreg." -"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.)" +"The :mod:`_winreg ` module now has a " +"function, :func:`~winreg.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 "" #: whatsnew/2.6.rst:3153 msgid "" ":mod:`_winreg ` also has better support for x64 systems, exposing " -"the :func:`~winreg.DisableReflectionKey`, :func:`~winreg." -"EnableReflectionKey`, and :func:`~winreg.QueryReflectionKey` functions, " -"which enable and disable registry reflection for 32-bit processes running on " -"64-bit systems. (:issue:`1753245`)" +"the :func:`~winreg.DisableReflectionKey`, :func:`~winreg.EnableReflectionKey`, " +"and :func:`~winreg.QueryReflectionKey` functions, which enable and disable " +"registry reflection for 32-bit processes running on 64-bit systems. " +"(:issue:`1753245`)" msgstr "" #: whatsnew/2.6.rst:3159 msgid "" -"The :mod:`msilib` module's :class:`!Record` object gained :meth:`~msilib." -"Record.GetInteger` and :meth:`~msilib.Record.GetString` methods that return " -"field values as an integer or a string. (Contributed by Floris Bruynooghe; :" -"issue:`2125`.)" +"The :mod:`msilib` module's :class:`!Record` object " +"gained :meth:`~msilib.Record.GetInteger` " +"and :meth:`~msilib.Record.GetString` methods that return field values as an " +"integer or a string. (Contributed by Floris Bruynooghe; :issue:`2125`.)" msgstr "" #: whatsnew/2.6.rst:3167 @@ -4486,24 +4505,25 @@ msgstr "" #: whatsnew/2.6.rst:3174 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`)" +"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 "" #: whatsnew/2.6.rst:3178 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`." +"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 "" #: whatsnew/2.6.rst:3221 @@ -4515,10 +4535,10 @@ 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`." +"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 "" #: whatsnew/2.6.rst:3253 @@ -4557,9 +4577,9 @@ msgstr "" 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." +"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 "" #: whatsnew/2.6.rst:3284 @@ -4585,20 +4605,20 @@ msgstr "" #: whatsnew/2.6.rst:3298 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`.)" +"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 "" #: whatsnew/2.6.rst:3303 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:`~datetime.time` " -"instances. (:issue:`1330538`)" +"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:`~datetime.time` instances. (:issue:`1330538`)" msgstr "" #: whatsnew/2.6.rst:3310 diff --git a/whatsnew/2.7.po b/whatsnew/2.7.po index 993adb5be..816deb69c 100644 --- a/whatsnew/2.7.po +++ b/whatsnew/2.7.po @@ -38,11 +38,11 @@ msgstr "" 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." +"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 "" #: whatsnew/2.7.rst:63 @@ -58,9 +58,9 @@ msgid "" "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." +"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 "" #: whatsnew/2.7.rst:80 @@ -167,10 +167,11 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.7.rst:158 @@ -247,8 +248,8 @@ msgstr "" #: 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." +"Float-to-string and string-to-float conversions are correctly rounded. " +"The :func:`round` function is also now correctly rounded." msgstr "" #: whatsnew/2.7.rst:194 @@ -286,8 +287,8 @@ 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." +"the experiences from those implementations, 2.7 introduces a " +"new :class:`~collections.OrderedDict` class in the :mod:`collections` module." msgstr "" #: whatsnew/2.7.rst:222 @@ -405,9 +406,9 @@ msgstr "" #: 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." +"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 "" #: whatsnew/2.7.rst:298 @@ -494,14 +495,14 @@ msgstr "" #: 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` " +"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.)" +"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 "" #: whatsnew/2.7.rst:366 @@ -591,9 +592,9 @@ msgid "" "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." +"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 "" #: whatsnew/2.7.rst:437 @@ -610,8 +611,8 @@ msgstr "" #: whatsnew/2.7.rst:441 msgid "" -"Part of the Python documentation, describing how to convert code that uses :" -"mod:`optparse`." +"Part of the Python documentation, describing how to convert code that " +"uses :mod:`optparse`." msgstr "" #: whatsnew/2.7.rst:444 @@ -638,10 +639,10 @@ msgstr "" 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.config.fileConfig` function that parses a file, but the file " -"format doesn't support configuring filters, and it's messier to generate " -"programmatically." +"set-up requires verbose but boring code. :mod:`logging` also supports " +"a :func:`~logging.config.fileConfig` function that parses a file, but the " +"file format doesn't support configuring filters, and it's messier to " +"generate programmatically." msgstr "" #: whatsnew/2.7.rst:462 @@ -717,8 +718,8 @@ msgstr "" 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." +"socket to use, either :const:`socket.SOCK_DGRAM` for UDP " +"or :const:`socket.SOCK_STREAM` for TCP. The default protocol remains UDP." msgstr "" #: whatsnew/2.7.rst:529 @@ -726,15 +727,16 @@ 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')``." +"calling ``log.getChild('network.listen')`` is equivalent to " +"``getLogger('app.network.listen')``." msgstr "" #: whatsnew/2.7.rst:535 msgid "" -"The :class:`~logging.LoggerAdapter` class gained an :meth:`~logging.Logger." -"isEnabledFor` method that takes a *level* and returns whether the underlying " -"logger would process a message of that level of importance." +"The :class:`~logging.LoggerAdapter` class gained " +"an :meth:`~logging.Logger.isEnabledFor` method that takes a *level* and " +"returns whether the underlying logger would process a message of that level " +"of importance." msgstr "" #: whatsnew/2.7.rst:544 @@ -751,17 +753,18 @@ msgstr "" #: 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." +"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 "" #: 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:" -"`!viewkeys`, :meth:`!viewvalues`, and :meth:`!viewitems`." +"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:`!viewkeys`, :meth:`!viewvalues`, " +"and :meth:`!viewitems`." msgstr "" #: whatsnew/2.7.rst:562 @@ -824,8 +827,8 @@ msgstr "" #: 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." +"change them to the standard :meth:`~dict.keys`, :meth:`~dict.values`, " +"and :meth:`~dict.items` methods." msgstr "" #: whatsnew/2.7.rst:605 @@ -834,8 +837,8 @@ msgstr "" #: whatsnew/2.7.rst:606 msgid "" -"PEP written by Guido van Rossum. Backported to 2.7 by Alexandre Vassalotti; :" -"issue:`1967`." +"PEP written by Guido van Rossum. Backported to 2.7 by Alexandre " +"Vassalotti; :issue:`1967`." msgstr "" #: whatsnew/2.7.rst:611 @@ -1000,11 +1003,12 @@ msgstr "" 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." +"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 "" #: whatsnew/2.7.rst:741 @@ -1027,8 +1031,8 @@ msgstr "" #: whatsnew/2.7.rst:757 msgid "" -"Implemented by Eric Smith and Mark Dickinson, using David Gay's :file:`dtoa." -"c` library; :issue:`7117`." +"Implemented by Eric Smith and Mark Dickinson, using David " +"Gay's :file:`dtoa.c` library; :issue:`7117`." msgstr "" #: whatsnew/2.7.rst:760 @@ -1125,9 +1129,9 @@ msgstr "" #: 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 " +"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 " @@ -1170,15 +1174,15 @@ msgstr "" #: 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`.)" +"override the :meth:`!__unicode__` method. (Implemented by Victor " +"Stinner; :issue:`1583863`.)" msgstr "" #: 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`.)" +"accepts ``None`` as its first argument. (Fixed by Georg " +"Brandl; :issue:`4759`.)" msgstr "" #: whatsnew/2.7.rst:861 @@ -1201,8 +1205,8 @@ msgstr "" 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`.)" +"contributed by Alexander Belchenko and Amaury Forgeot d'Arc " +"in :issue:`1616979`; CP858 contributed by Tim Hatch in :issue:`8016`.)" msgstr "" #: whatsnew/2.7.rst:879 @@ -1211,14 +1215,14 @@ msgid "" "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`)." +"the C library to catch and report the error (fixed by Stefan " +"Krah; :issue:`5677`)." msgstr "" #: whatsnew/2.7.rst:886 msgid "" -"The Python tokenizer now translates line endings itself, so the :func:" -"`compile` built-in function now accepts code using any line-ending " +"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 "" @@ -1234,15 +1238,15 @@ msgstr "" #: whatsnew/2.7.rst:896 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`.)" +"style classes were always weak-referenceable. (Fixed by Antoine " +"Pitrou; :issue:`8268`.)" msgstr "" #: whatsnew/2.7.rst:900 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`)." +"only cleared if no one else is holding a reference to the dictionary " +"(:issue:`7140`)." msgstr "" #: whatsnew/2.7.rst:909 @@ -1280,8 +1284,8 @@ msgstr "" #: whatsnew/2.7.rst:934 msgid "" "A new opcode was added to perform the initial setup for :keyword:`with` " -"statements, looking up the :meth:`~object.__enter__` and :meth:`~object." -"__exit__` methods. (Contributed by Benjamin Peterson.)" +"statements, looking up the :meth:`~object.__enter__` " +"and :meth:`~object.__exit__` methods. (Contributed by Benjamin Peterson.)" msgstr "" #: whatsnew/2.7.rst:938 @@ -1368,8 +1372,8 @@ msgstr "" #: whatsnew/2.7.rst:999 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`.)" +"bytecode. (Patch by Antoine Pitrou, back-ported to 2.7 by Jeffrey " +"Yasskin; :issue:`4715`.)" msgstr "" #: whatsnew/2.7.rst:1003 @@ -1398,8 +1402,8 @@ msgstr "" #: whatsnew/2.7.rst:1020 msgid "" "The :mod:`!cPickle` module now special-cases dictionaries, nearly halving " -"the time required to pickle them. (Contributed by Collin Winter; :issue:" -"`5670`.)" +"the time required to pickle them. (Contributed by Collin " +"Winter; :issue:`5670`.)" msgstr "" #: whatsnew/2.7.rst:1027 @@ -1421,8 +1425,8 @@ msgid "" "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`.)" +"(Contributed by Maru Newby after a suggestion by Senthil " +"Kumaran; :issue:`5142`.)" msgstr "" #: whatsnew/2.7.rst:1043 @@ -1476,13 +1480,13 @@ msgstr "" #: whatsnew/2.7.rst:1081 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. ::" +"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 "" #: whatsnew/2.7.rst:1091 @@ -1513,13 +1517,13 @@ msgstr "" #: whatsnew/2.7.rst:1111 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.)" +"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 "" #: whatsnew/2.7.rst:1119 @@ -1597,28 +1601,30 @@ msgstr "" #: whatsnew/2.7.rst:1174 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`.)" +"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 "" #: whatsnew/2.7.rst:1181 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`.)" +"number of seconds in the duration. (Contributed by Brian " +"Quinlan; :issue:`5788`.)" msgstr "" #: whatsnew/2.7.rst:1185 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`. 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 " +"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`. 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 "" @@ -1639,32 +1645,33 @@ msgstr "" 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`)." +"characters such as Arabic-Indic digits (contributed by Mark " +"Dickinson; :issue:`6595`)." msgstr "" #: whatsnew/2.7.rst:1210 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`.)" +"are the :meth:`~decimal.Context.canonical` " +"and :meth:`~decimal.Context.is_canonical` methods. (Patch by Juan José " +"Conti; :issue:`7633`.)" msgstr "" #: whatsnew/2.7.rst:1215 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`.)" +"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 "" #: whatsnew/2.7.rst:2484 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`.)" +"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 "" #: whatsnew/2.7.rst:1226 @@ -1694,16 +1701,16 @@ msgstr "" 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`.)" +"encoding specified by :attr:`!output_charset`. (Added by R. David " +"Murray; :issue:`1368247`.)" msgstr "" #: whatsnew/2.7.rst:1247 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`.)" +"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 "" #: whatsnew/2.7.rst:1253 @@ -1717,36 +1724,37 @@ msgstr "" 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`.)" +"subsequent control and data transfers. (Contributed by Giampaolo " +"Rodola; :issue:`2054`.)" msgstr "" #: whatsnew/2.7.rst:1266 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`.)" +"uploads thanks to an added *rest* parameter (patch by Pablo " +"Mouzo; :issue:`6845`.)" msgstr "" #: whatsnew/2.7.rst:1270 msgid "" -"New class decorator: :func:`~functools.total_ordering` in the :mod:" -"`functools` module takes a class that defines an :meth:`~object.__eq__` " -"method and one of :meth:`~object.__lt__`, :meth:`~object.__le__`, :meth:" -"`~object.__gt__`, or :meth:`~object.__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`.)" +"New class decorator: :func:`~functools.total_ordering` in " +"the :mod:`functools` module takes a class that defines " +"an :meth:`~object.__eq__` method and one " +"of :meth:`~object.__lt__`, :meth:`~object.__le__`, :meth:`~object.__gt__`, " +"or :meth:`~object.__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 "" #: whatsnew/2.7.rst:1278 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.)" +"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 "" #: whatsnew/2.7.rst:1285 @@ -1760,12 +1768,12 @@ msgstr "" 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`.)" +"(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 "" #: whatsnew/2.7.rst:1299 @@ -1785,18 +1793,19 @@ msgstr "" #: whatsnew/2.7.rst:1309 msgid "" -"The default :class:`~http.client.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`.)" +"The default :class:`~http.client.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 "" #: whatsnew/2.7.rst:1313 msgid "" -"The :class:`~http.client.HTTPConnection` and :class:`~http.client." -"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`.)" +"The :class:`~http.client.HTTPConnection` " +"and :class:`~http.client.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 "" #: whatsnew/2.7.rst:1318 @@ -1851,8 +1860,8 @@ msgstr "" #: whatsnew/2.7.rst:1353 msgid "" -"One minor resulting change: the :class:`io.TextIOBase` class now has an :" -"attr:`~io.TextIOBase.errors` attribute giving the error setting used for " +"One minor resulting change: the :class:`io.TextIOBase` class now has " +"an :attr:`~io.TextIOBase.errors` attribute giving the error setting used for " "encoding and decoding errors (one of ``'strict'``, ``'replace'``, " "``'ignore'``)." msgstr "" @@ -1860,10 +1869,10 @@ msgstr "" #: whatsnew/2.7.rst:1358 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`.)" +"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 "" #: whatsnew/2.7.rst:1364 @@ -1904,9 +1913,9 @@ msgstr "" 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`.)" +"allows keyword arguments, and using non-integer values such as floats " +"or :class:`~decimal.Decimal` instances. (Implemented by Raymond " +"Hettinger; :issue:`5032`.)" msgstr "" #: whatsnew/2.7.rst:1391 @@ -1943,13 +1952,13 @@ msgstr "" #: whatsnew/2.7.rst:1412 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`.)" +"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 "" #: whatsnew/2.7.rst:1420 @@ -1978,13 +1987,14 @@ msgstr "" #: whatsnew/2.7.rst:1437 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`.)" +"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 "" #: whatsnew/2.7.rst:1447 @@ -1996,11 +2006,12 @@ msgstr "" #: whatsnew/2.7.rst:1451 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`.)" +"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 "" #: whatsnew/2.7.rst:1457 @@ -2012,24 +2023,26 @@ msgstr "" #: whatsnew/2.7.rst:1461 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.)" +"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 "" #: whatsnew/2.7.rst:1465 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`.)" +"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 "" #: whatsnew/2.7.rst:1479 @@ -2053,27 +2066,28 @@ msgstr "" 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`.)" +"catch the EINTR signal robustly. (Fixed by Charles-Francois " +"Natali; :issue:`8354`.)" msgstr "" #: whatsnew/2.7.rst:1495 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 :data:`~site." -"USER_BASE` environment variable, giving the path to a directory that can be " -"used to store data. (Contributed by Tarek Ziadé; :issue:`6693`.)" +"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 :data:`~site.USER_BASE` environment variable, giving the path " +"to a directory that can be used to store data. (Contributed by Tarek " +"Ziadé; :issue:`6693`.)" msgstr "" #: whatsnew/2.7.rst:1506 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`.)" +"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 "" #: whatsnew/2.7.rst:1511 @@ -2085,25 +2099,27 @@ msgstr "" #: whatsnew/2.7.rst:1516 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`.)" +"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 "" #: whatsnew/2.7.rst:1521 msgid "" -"The :mod:`SocketServer ` module's :class:`~socketserver." -"TCPServer` class now supports socket timeouts and disabling the Nagle " -"algorithm. The :attr:`!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`.)" +"The :mod:`SocketServer ` " +"module's :class:`~socketserver.TCPServer` class now supports socket timeouts " +"and disabling the Nagle algorithm. The :attr:`!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 "" #: whatsnew/2.7.rst:1533 @@ -2112,18 +2128,19 @@ msgid "" "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.)" +"method to enable extensions, and then " +"call :meth:`~sqlite3.Connection.load_extension` to load a particular shared " +"library. (Updated by Gerhard Häring.)" msgstr "" #: whatsnew/2.7.rst:1540 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`)." +"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 "" #: whatsnew/2.7.rst:1547 @@ -2145,10 +2162,11 @@ msgstr "" #: whatsnew/2.7.rst:1560 msgid "" -"The version of OpenSSL being used is now available as the module attributes :" -"const:`ssl.OPENSSL_VERSION` (a string), :const:`ssl.OPENSSL_VERSION_INFO` (a " -"5-tuple), and :const:`ssl.OPENSSL_VERSION_NUMBER` (an integer). (Added by " -"Antoine Pitrou; :issue:`8321`.)" +"The version of OpenSSL being used is now available as the module " +"attributes :const:`ssl.OPENSSL_VERSION` (a " +"string), :const:`ssl.OPENSSL_VERSION_INFO` (a 5-tuple), " +"and :const:`ssl.OPENSSL_VERSION_NUMBER` (an integer). (Added by Antoine " +"Pitrou; :issue:`8321`.)" msgstr "" #: whatsnew/2.7.rst:1566 @@ -2164,10 +2182,11 @@ msgstr "" #: whatsnew/2.7.rst:1575 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." +"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 "" #: whatsnew/2.7.rst:1582 @@ -2195,10 +2214,10 @@ msgstr "" #: whatsnew/2.7.rst:1596 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.)" +"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 "" #: whatsnew/2.7.rst:2500 @@ -2218,8 +2237,8 @@ msgstr "" #: whatsnew/2.7.rst:1610 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:`!" +"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 "" @@ -2244,8 +2263,8 @@ msgid "" "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`.)" +"also now supports the context management protocol. (Added by Lars " +"Gustäbel; :issue:`7232`.)" msgstr "" #: whatsnew/2.7.rst:1636 @@ -2262,10 +2281,10 @@ msgstr "" 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`)." +"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 "" #: whatsnew/2.7.rst:2512 @@ -2305,8 +2324,8 @@ msgstr "" #: whatsnew/2.7.rst:1678 msgid "" "The :mod:`urlparse ` module also supports IPv6 literal " -"addresses as defined by :rfc:`2732` (contributed by Senthil Kumaran; :issue:" -"`2987`)." +"addresses as defined by :rfc:`2732` (contributed by Senthil " +"Kumaran; :issue:`2987`)." msgstr "" #: whatsnew/2.7.rst:1681 @@ -2335,13 +2354,13 @@ msgstr "" #: whatsnew/2.7.rst:1700 msgid "" -"The XML-RPC client and server, provided by the :mod:`xmlrpclib ` and :mod:`SimpleXMLRPCServer ` modules, have " +"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:`~xmlrpc.server.SimpleXMLRPCRequestHandler`, which contains a size in " -"bytes; responses larger than this will be compressed. (Contributed by " +"compression is controlled by the :attr:`!encode_threshold` attribute " +"of :class:`~xmlrpc.server.SimpleXMLRPCRequestHandler`, which contains a size " +"in bytes; responses larger than this will be compressed. (Contributed by " "Kristján Valur Jónsson; :issue:`6267`.)" msgstr "" @@ -2356,9 +2375,9 @@ msgstr "" 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:`read() ` and :meth:`readline() ` now works correctly. " -"(Contributed by Nir Aides; :issue:`7610`.)" +"of an archive is faster, and interleaving :meth:`read() " +"` and :meth:`readline() ` now " +"works correctly. (Contributed by Nir Aides; :issue:`7610`.)" msgstr "" #: whatsnew/2.7.rst:1720 @@ -2387,8 +2406,8 @@ msgid "" "useful for implementers 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`." +"tiny subset that contains a single " +"function, :func:`~importlib.import_module`." msgstr "" #: whatsnew/2.7.rst:1747 @@ -2504,10 +2523,10 @@ msgstr "" #: whatsnew/2.7.rst:1818 msgid "" -"The :mod:`tkinter.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 " +"The :mod:`tkinter.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 "" @@ -2579,8 +2598,8 @@ msgstr "" 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`.)" +"tests. (Suggested by Cliff Dyer and implemented by Michael " +"Foord; :issue:`8074`.)" msgstr "" #: whatsnew/2.7.rst:1874 @@ -2598,13 +2617,13 @@ msgstr "" #: whatsnew/2.7.rst:1881 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`.)" +"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 "" #: whatsnew/2.7.rst:1888 @@ -2627,22 +2646,24 @@ msgstr "" #: whatsnew/2.7.rst:1899 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." +"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 "" #: whatsnew/2.7.rst:1907 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`)." +"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 "" #: whatsnew/2.7.rst:1915 @@ -2655,31 +2676,31 @@ msgstr "" #: whatsnew/2.7.rst:1920 msgid "" -":meth:`~unittest.TestCase.assertIsNone` and :meth:`~unittest.TestCase." -"assertIsNotNone` take one expression and verify that the result is or is not " -"``None``." +":meth:`~unittest.TestCase.assertIsNone` " +"and :meth:`~unittest.TestCase.assertIsNotNone` take one expression and " +"verify that the result is or is not ``None``." msgstr "" #: whatsnew/2.7.rst:1923 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`.)" +":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 "" #: whatsnew/2.7.rst:1927 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`.)" +":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 "" #: whatsnew/2.7.rst:1932 msgid "" -":meth:`~unittest.TestCase.assertGreater`, :meth:`~unittest.TestCase." -"assertGreaterEqual`, :meth:`~unittest.TestCase.assertLess`, and :meth:" -"`~unittest.TestCase.assertLessEqual` compare two quantities." +":meth:`~unittest.TestCase.assertGreater`, :meth:`~unittest.TestCase.assertGreaterEqual`, :meth:`~unittest.TestCase.assertLess`, " +"and :meth:`~unittest.TestCase.assertLessEqual` compare two quantities." msgstr "" #: whatsnew/2.7.rst:1936 @@ -2692,10 +2713,10 @@ msgstr "" #: whatsnew/2.7.rst:1941 msgid "" -":meth:`assertRegexpMatches() ` and :meth:" -"`assertNotRegexpMatches() ` checks whether " -"the first argument is a string matching or not matching the regular " -"expression provided as the second argument (:issue:`8038`)." +":meth:`assertRegexpMatches() ` " +"and :meth:`assertNotRegexpMatches() ` " +"checks whether the first argument is a string matching or not matching the " +"regular expression provided as the second argument (:issue:`8038`)." msgstr "" #: whatsnew/2.7.rst:1946 @@ -2708,8 +2729,9 @@ msgstr "" #: whatsnew/2.7.rst:1951 msgid "" -":meth:`~unittest.TestCase.assertIn` and :meth:`~unittest.TestCase." -"assertNotIn` tests whether *first* is or is not in *second*." +":meth:`~unittest.TestCase.assertIn` " +"and :meth:`~unittest.TestCase.assertNotIn` tests whether *first* is or is " +"not in *second*." msgstr "" #: whatsnew/2.7.rst:1954 @@ -2726,13 +2748,14 @@ msgstr "" #: whatsnew/2.7.rst:1960 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." +"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 "" #: whatsnew/2.7.rst:1968 @@ -2746,45 +2769,47 @@ msgstr "" #: whatsnew/2.7.rst:1973 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." +":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 "" #: whatsnew/2.7.rst:1979 msgid "" -":meth:`~unittest.TestLoader.loadTestsFromName` properly honors the :attr:" -"`~unittest.TestLoader.suiteClass` attribute of the :class:`~unittest." -"TestLoader`. (Fixed by Mark Roddy; :issue:`6866`.)" +":meth:`~unittest.TestLoader.loadTestsFromName` properly honors " +"the :attr:`~unittest.TestLoader.suiteClass` attribute of " +"the :class:`~unittest.TestLoader`. (Fixed by Mark Roddy; :issue:`6866`.)" msgstr "" #: whatsnew/2.7.rst:1983 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." +"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 "" #: whatsnew/2.7.rst:1992 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`.)" +":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 "" #: whatsnew/2.7.rst:1997 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 " +":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 "" @@ -2841,16 +2866,16 @@ msgstr "" #: whatsnew/2.7.rst:2031 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 " +"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:" -"`~xml.etree.ElementTree.Element.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." +"skip over elements and only output the text chunks. If you set " +"the :attr:`~xml.etree.ElementTree.Element.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 "" #: whatsnew/2.7.rst:2044 @@ -2858,17 +2883,18 @@ 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." +"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 "" #: whatsnew/2.7.rst:2052 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::" +"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 "" #: whatsnew/2.7.rst:2058 @@ -2887,19 +2913,19 @@ msgstr "" #: whatsnew/2.7.rst:2069 msgid "" -"New :class:`~xml.etree.ElementTree.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." +"New :class:`~xml.etree.ElementTree.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 "" #: whatsnew/2.7.rst:2076 msgid "" -"New :class:`~xml.etree.ElementTree.Element` method: :meth:`~xml.etree." -"ElementTree.Element.itertext` yields all chunks of text that are descendants " -"of the element. For example::" +"New :class:`~xml.etree.ElementTree.Element` " +"method: :meth:`~xml.etree.ElementTree.Element.itertext` yields all chunks of " +"text that are descendants of the element. For example::" msgstr "" #: whatsnew/2.7.rst:2080 @@ -2925,8 +2951,8 @@ msgstr "" #: whatsnew/2.7.rst:2095 msgid "" "Fredrik Lundh develops ElementTree and produced the 1.3 version; you can " -"read his article describing 1.3 at https://web.archive.org/" -"web/20200703234532/http://effbot.org/zone/elementtree-13-intro.htm. Florent " +"read his article describing 1.3 at https://web.archive.org/web/" +"20200703234532/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 "" @@ -2965,8 +2991,8 @@ msgstr "" 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`.)" +"for asynchronous IO operations. (Contributed by Kristján Valur " +"Jónsson; :issue:`4293`.)" msgstr "" #: whatsnew/2.7.rst:2131 @@ -2997,11 +3023,12 @@ msgstr "" #: whatsnew/2.7.rst:2150 msgid "" -"New functions: :c:func:`PyLong_AsLongAndOverflow` and :c:func:" -"`PyLong_AsLongLongAndOverflow` approximates a Python long integer as a C :c:" -"expr:`long` or :c:expr:`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`.)" +"New functions: :c:func:`PyLong_AsLongAndOverflow` " +"and :c:func:`PyLong_AsLongLongAndOverflow` approximates a Python long " +"integer as a C :c:expr:`long` or :c:expr:`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 "" #: whatsnew/2.7.rst:2157 @@ -3047,14 +3074,12 @@ msgstr "" #: whatsnew/2.7.rst:2183 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`.)" +"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 "" #: whatsnew/2.7.rst:2201 @@ -3099,16 +3124,17 @@ msgstr "" #: whatsnew/2.7.rst:2230 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`.)" +"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 "" #: whatsnew/2.7.rst:2235 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 :c:macro:" -"`T_STRING_INPLACE` attribute." +"type, Python will no longer let you try to delete or set " +"a :c:macro:`T_STRING_INPLACE` attribute." msgstr "" #: whatsnew/2.7.rst:2241 @@ -3121,8 +3147,8 @@ msgstr "" 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`.)" +"Expat library. (Contributed by Arfrever Frehtes Taifersar " +"Arahesis; :issue:`7609`.)" msgstr "" #: whatsnew/2.7.rst:2249 @@ -3130,8 +3156,8 @@ 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`.)" +"detecting memory leaks and overruns. (Contributed by James " +"Henstridge; :issue:`2422`.)" msgstr "" #: whatsnew/2.7.rst:2256 @@ -3146,8 +3172,8 @@ 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`.)" +"available if anyone wishes to use it. (Added by Mark " +"Dickinson; :issue:`2937`.)" msgstr "" #: whatsnew/2.7.rst:2267 @@ -3177,12 +3203,12 @@ msgstr "" 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." +"*`` 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 "" #: whatsnew/2.7.rst:2292 @@ -3220,8 +3246,8 @@ 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:`!" -"PyCObject` interface. Use of :c:func:`!PyCObject_AsVoidPtr` will signal a :" -"exc:`PendingDeprecationWarning`, which is silent by default." +"PyCObject` interface. Use of :c:func:`!PyCObject_AsVoidPtr` will signal " +"a :exc:`PendingDeprecationWarning`, which is silent by default." msgstr "" #: whatsnew/2.7.rst:2322 @@ -3236,11 +3262,11 @@ msgstr "" #: whatsnew/2.7.rst:2331 msgid "" -"The :mod:`msvcrt` module now contains some constants from the :file:" -"`crtassem.h` header file: :data:`~msvcrt.CRT_ASSEMBLY_VERSION`, :data:" -"`~msvcrt.VC_ASSEMBLY_PUBLICKEYTOKEN`, and :data:`~msvcrt." -"LIBRARIES_ASSEMBLY_NAME_PREFIX`. (Contributed by David Cournapeau; :issue:" -"`4365`.)" +"The :mod:`msvcrt` module now contains some constants from " +"the :file:`crtassem.h` header " +"file: :data:`~msvcrt.CRT_ASSEMBLY_VERSION`, :data:`~msvcrt.VC_ASSEMBLY_PUBLICKEYTOKEN`, " +"and :data:`~msvcrt.LIBRARIES_ASSEMBLY_NAME_PREFIX`. (Contributed by David " +"Cournapeau; :issue:`4365`.)" msgstr "" #: whatsnew/2.7.rst:2338 @@ -3248,9 +3274,10 @@ 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`.)" +"arguments. " +"The :func:`~winreg.DisableReflectionKey`, :func:`~winreg.EnableReflectionKey`, " +"and :func:`~winreg.QueryReflectionKey` were also tested and documented. " +"(Implemented by Brian Curtin: :issue:`7347`.)" msgstr "" #: whatsnew/2.7.rst:2346 @@ -3263,11 +3290,12 @@ msgstr "" #: whatsnew/2.7.rst:2350 msgid "" "The :func:`os.kill` function now works on Windows. The signal value can be " -"the constants :const:`~signal.CTRL_C_EVENT`, :const:`~signal." -"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`.)" +"the " +"constants :const:`~signal.CTRL_C_EVENT`, :const:`~signal.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 "" #: whatsnew/2.7.rst:2357 @@ -3288,10 +3316,10 @@ msgstr "" #: whatsnew/2.7.rst:2369 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`.)" +"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 "" #: whatsnew/2.7.rst:2376 @@ -3312,10 +3340,11 @@ msgstr "" #: whatsnew/2.7.rst:2389 msgid "" -"FreeBSD 7.1's :const:`!SO_SETFIB` constant, used with the :func:`~socket." -"socket` methods :func:`~socket.socket.getsockopt`/:func:`~socket.socket." -"setsockopt` to select an alternate routing table, is now available in the :" -"mod:`socket` module. (Added by Kyle VanderBeek; :issue:`8235`.)" +"FreeBSD 7.1's :const:`!SO_SETFIB` constant, used with " +"the :func:`~socket.socket` " +"methods :func:`~socket.socket.getsockopt`/:func:`~socket.socket.setsockopt` " +"to select an alternate routing table, is now available in the :mod:`socket` " +"module. (Added by Kyle VanderBeek; :issue:`8235`.)" msgstr "" #: whatsnew/2.7.rst:2395 @@ -3334,8 +3363,8 @@ msgstr "" #: whatsnew/2.7.rst:2405 msgid "" -"The :file:`Tools/i18n/msgfmt.py` script now understands plural forms in :" -"file:`.po` files. (Fixed by Martin von Löwis; :issue:`5464`.)" +"The :file:`Tools/i18n/msgfmt.py` script now understands plural forms " +"in :file:`.po` files. (Fixed by Martin von Löwis; :issue:`5464`.)" msgstr "" #: whatsnew/2.7.rst:2409 @@ -3351,9 +3380,9 @@ msgstr "" #: whatsnew/2.7.rst:2416 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.)" +"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 "" #: whatsnew/2.7.rst:2422 @@ -3395,8 +3424,8 @@ msgstr "" 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`.)" +"matches the precision used by :func:`str`. (Changed by Eric " +"Smith; :issue:`5920`.)" msgstr "" #: whatsnew/2.7.rst:2454 @@ -3410,10 +3439,10 @@ msgstr "" #: whatsnew/2.7.rst:2460 msgid "" -"Due to a bug in Python 2.6, the *exc_value* parameter to :meth:`~object." -"__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`.)" +"Due to a bug in Python 2.6, the *exc_value* parameter " +"to :meth:`~object.__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 "" #: whatsnew/2.7.rst:2470 @@ -3423,18 +3452,18 @@ msgstr "" #: whatsnew/2.7.rst:2472 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`.)" +"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 "" #: whatsnew/2.7.rst:2478 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`.)" +"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 "" #: whatsnew/2.7.rst:2490 @@ -3465,9 +3494,9 @@ msgstr "" #: whatsnew/2.7.rst:2545 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." +"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 "" #: whatsnew/2.7.rst:2549 @@ -3509,8 +3538,8 @@ msgstr "" #: whatsnew/2.7.rst:2580 msgid "" -"In debug mode, the ``[xxx refs]`` statistic is not written by default, the :" -"envvar:`!PYTHONSHOWREFCOUNT` environment variable now must also be set. " +"In debug mode, the ``[xxx refs]`` statistic is not written by default, " +"the :envvar:`!PYTHONSHOWREFCOUNT` environment variable now must also be set. " "(Contributed by Victor Stinner; :issue:`31733`.)" msgstr "" @@ -3519,8 +3548,8 @@ msgid "" "When Python is compiled with ``COUNT_ALLOC`` defined, allocation counts are " "no longer dumped by default anymore: the :envvar:`!PYTHONSHOWALLOCCOUNT` " "environment variable must now also be set. Moreover, allocation counts are " -"now dumped into stderr, rather than stdout. (Contributed by Victor Stinner; :" -"issue:`31692`.)" +"now dumped into stderr, rather than stdout. (Contributed by Victor " +"Stinner; :issue:`31692`.)" msgstr "" #: whatsnew/2.7.rst:2593 @@ -3583,8 +3612,8 @@ msgstr "" #: whatsnew/2.7.rst:2626 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`.)" +"python.org. (Contributed by Zachary Ware in :issue:`21671` " +"for :cve:`2014-0224`.)" msgstr "" #: whatsnew/2.7.rst:2629 @@ -3614,10 +3643,10 @@ msgstr "" #: whatsnew/2.7.rst:2643 msgid "" -":data:`hashlib.algorithms_guaranteed` and :data:`hashlib." -"algorithms_available` were backported from Python 3 to make it easier for " -"Python 2 applications to select the strongest available hash algorithm. " -"(Contributed by Alex Gaynor in :issue:`21307`)" +":data:`hashlib.algorithms_guaranteed` " +"and :data:`hashlib.algorithms_available` were backported from Python 3 to " +"make it easier for Python 2 applications to select the strongest available " +"hash algorithm. (Contributed by Alex Gaynor in :issue:`21307`)" msgstr "" #: whatsnew/2.7.rst:2650 @@ -3696,8 +3725,8 @@ msgstr "" #: whatsnew/2.7.rst:2700 msgid "" "However, as this migration is currently still incomplete, the legacy " -"versions of those guides remaining available as :ref:`install-index` and :" -"ref:`setuptools-index`." +"versions of those guides remaining available as :ref:`install-index` " +"and :ref:`setuptools-index`." msgstr "" #: whatsnew/2.7.rst:2706 @@ -3717,9 +3746,9 @@ msgstr "" #: whatsnew/2.7.rst:2713 msgid "" -":pep:`476` updated :mod:`httplib ` and modules which use it, such as :" -"mod:`urllib2 ` and :mod:`xmlrpclib `, to now " -"verify that the server presents a certificate which is signed by a " +":pep:`476` updated :mod:`httplib ` and modules which use it, such " +"as :mod:`urllib2 ` and :mod:`xmlrpclib `, to " +"now verify that the server presents a certificate which is signed by a " "Certificate Authority in the platform trust store and whose hostname matches " "the hostname being requested by default, significantly improving security " "for many applications. This change was made in the Python 2.7.9 release." @@ -3802,8 +3831,8 @@ msgstr "" #: whatsnew/2.7.rst:2772 msgid "" -"More selective regeneration targets are also defined - see :source:`Makefile." -"pre.in` for details." +"More selective regeneration targets are also defined - " +"see :source:`Makefile.pre.in` for details." msgstr "" #: whatsnew/2.7.rst:2788 diff --git a/whatsnew/3.0.po b/whatsnew/3.0.po index 87b29d22c..e249796e1 100644 --- a/whatsnew/3.0.po +++ b/whatsnew/3.0.po @@ -149,26 +149,26 @@ msgstr "" #: 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)." +":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 "" #: whatsnew/3.0.rst:153 msgid "" -"Also, the :meth:`dict.iterkeys`, :meth:`dict.iteritems` and :meth:`dict." -"itervalues` methods are no longer supported." +"Also, the :meth:`dict.iterkeys`, :meth:`dict.iteritems` " +"and :meth:`dict.itervalues` methods are no longer supported." msgstr "" #: 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 " +"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 "" @@ -176,10 +176,10 @@ msgstr "" #: 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)))``." +"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 "" #: whatsnew/3.0.rst:173 @@ -215,16 +215,16 @@ msgstr "" #: 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\"." +"argument providing a comparison function. Use the *key* argument instead. " +"N.B. the *key* and *reverse* arguments are now \"keyword-only\"." msgstr "" #: 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 " +"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 "" @@ -251,9 +251,9 @@ 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)." +"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 "" #: whatsnew/3.0.rst:224 @@ -281,14 +281,14 @@ msgstr "" 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." +"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 "" #: whatsnew/3.0.rst:250 @@ -297,9 +297,9 @@ msgid "" "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." +"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 "" #: whatsnew/3.0.rst:258 @@ -311,10 +311,10 @@ msgstr "" #: 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." +"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 "" #: whatsnew/3.0.rst:268 @@ -337,11 +337,11 @@ msgstr "" #: 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`." +"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 "" #: whatsnew/3.0.rst:287 @@ -364,10 +364,10 @@ msgstr "" #: 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." +"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 "" #: whatsnew/3.0.rst:310 @@ -376,14 +376,14 @@ msgid "" "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`." +"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 "" #: whatsnew/3.0.rst:325 @@ -415,8 +415,8 @@ msgstr "" #: 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." +"import the :mod:`io` module and use :class:`io.StringIO` " +"or :class:`io.BytesIO` for text and data respectively." msgstr "" #: whatsnew/3.0.rst:344 @@ -467,8 +467,8 @@ msgstr "" #: 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." +"now assign directly to a variable in an outer (but non-global) " +"scope. :keyword:`!nonlocal` is a new reserved word." msgstr "" #: whatsnew/3.0.rst:378 @@ -525,8 +525,8 @@ msgstr "" #: whatsnew/3.0.rst:408 msgid "" -":pep:`3109` and :pep:`3134`: new :keyword:`raise` statement syntax: :samp:" -"`raise [{expr} [from {expr}]]`. See below." +":pep:`3109` and :pep:`3134`: new :keyword:`raise` statement " +"syntax: :samp:`raise [{expr} [from {expr}]]`. See below." msgstr "" #: whatsnew/3.0.rst:411 @@ -543,8 +543,8 @@ msgstr "" #: whatsnew/3.0.rst:417 msgid "" -"Change from :keyword:`except` *exc*, *var* to :keyword:`!except` *exc* :" -"keyword:`!as` *var*. See :pep:`3110`." +"Change from :keyword:`except` *exc*, *var* to :keyword:`!except` " +"*exc* :keyword:`!as` *var*. See :pep:`3110`." msgstr "" #: whatsnew/3.0.rst:420 @@ -682,9 +682,10 @@ msgstr "" 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." +"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 "" #: whatsnew/3.0.rst:507 @@ -712,11 +713,11 @@ 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)." +"*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 "" #: whatsnew/3.0.rst:529 @@ -727,11 +728,11 @@ msgstr "" #: 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." +":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 "" #: whatsnew/3.0.rst:539 @@ -777,8 +778,8 @@ 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." +"However, the package is alive and well, externally maintained at https://" +"www.jcea.es/programacion/pybsddb.htm." msgstr "" #: whatsnew/3.0.rst:572 @@ -882,8 +883,8 @@ msgstr "" #: whatsnew/3.0.rst:606 msgid "" -":mod:`dbm` (:mod:`!anydbm`, :mod:`!dbhash`, :mod:`!dbm`, :mod:`!dumbdbm`, :" -"mod:`!gdbm`, :mod:`!whichdb`)." +":mod:`dbm` (:mod:`!anydbm`, :mod:`!dbhash`, :mod:`!dbm`, :mod:`!" +"dumbdbm`, :mod:`!gdbm`, :mod:`!whichdb`)." msgstr "" #: whatsnew/3.0.rst:609 @@ -899,9 +900,9 @@ msgstr "" #: 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." +"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 "" #: whatsnew/3.0.rst:620 @@ -927,9 +928,9 @@ msgstr "" #: 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.)" +"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 "" #: whatsnew/3.0.rst:636 @@ -942,15 +943,15 @@ msgstr "" #: whatsnew/3.0.rst:642 msgid "" -"Cleanup of the :mod:`operator` module: removed :func:`sequenceIncludes` and :" -"func:`isCallable`." +"Cleanup of the :mod:`operator` module: removed :func:`sequenceIncludes` " +"and :func:`isCallable`." msgstr "" #: whatsnew/3.0.rst:645 msgid "" "Cleanup of the :mod:`!thread` module: :func:`!acquire_lock` and :func:`!" -"release_lock` are gone; use :meth:`~threading.Lock.acquire` and :meth:" -"`~threading.Lock.release` instead." +"release_lock` are gone; use :meth:`~threading.Lock.acquire` " +"and :meth:`~threading.Lock.release` instead." msgstr "" #: whatsnew/3.0.rst:649 @@ -975,10 +976,10 @@ msgstr "" #: 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 " +":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 "" @@ -986,8 +987,8 @@ msgstr "" 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__`!" +"most global namespaces is unchanged. To modify a builtin, you should " +"use :mod:`builtins`, not :data:`__builtins__`!" msgstr "" #: whatsnew/3.0.rst:675 @@ -1014,21 +1015,22 @@ msgstr "" #: 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." +":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 "" #: 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`." +"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 "" #: whatsnew/3.0.rst:705 @@ -1054,8 +1056,8 @@ msgstr "" 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." +"{variable}`. Moreover, the *variable* is explicitly deleted when " +"the :keyword:`except` block is left." msgstr "" #: whatsnew/3.0.rst:722 @@ -1079,19 +1081,19 @@ msgid "" "object, probably an exception that was previously caught). In this case, the " "primary exception is stored on the :attr:`~BaseException.__cause__` " "attribute of the secondary exception. The traceback printed when an " -"unhandled exception occurs walks the chain of :attr:`!__cause__` and :attr:" -"`~BaseException.__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.)" +"unhandled exception occurs walks the chain of :attr:`!__cause__` " +"and :attr:`~BaseException.__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 "" #: whatsnew/3.0.rst:743 msgid "" -":pep:`3134`: Exception objects now store their traceback as the :attr:" -"`~BaseException.__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)." +":pep:`3134`: Exception objects now store their traceback as " +"the :attr:`~BaseException.__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 "" #: whatsnew/3.0.rst:749 @@ -1111,8 +1113,8 @@ msgstr "" #: whatsnew/3.0.rst:761 msgid "" -"``!=`` now returns the opposite of ``==``, unless ``==`` returns :data:" -"`NotImplemented`." +"``!=`` now returns the opposite of ``==``, unless ``==`` " +"returns :data:`NotImplemented`." msgstr "" #: whatsnew/3.0.rst:764 @@ -1132,15 +1134,15 @@ msgstr "" #: whatsnew/3.0.rst:774 msgid "" -":pep:`3114`: the standard :meth:`next` method has been renamed to :meth:" -"`~iterator.__next__`." +":pep:`3114`: the standard :meth:`next` method has been renamed " +"to :meth:`~iterator.__next__`." msgstr "" #: whatsnew/3.0.rst:777 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." +"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 "" #: whatsnew/3.0.rst:781 @@ -1149,14 +1151,14 @@ msgstr "" #: whatsnew/3.0.rst:783 msgid "" -"The function attributes named :attr:`!func_X` have been renamed to use the :" -"attr:`!__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:" -"`~function.__closure__`, :attr:`~function.__code__`, :attr:`~function." -"__defaults__`, :attr:`~function.__dict__`, :attr:`~function.__doc__`, :attr:" -"`~function.__globals__`, :attr:`~function.__name__`, respectively." +"The function attributes named :attr:`!func_X` have been renamed to use " +"the :attr:`!__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:`~function.__closure__`, :attr:`~function.__code__`, :attr:`~function.__defaults__`, :attr:`~function.__dict__`, :attr:`~function.__doc__`, :attr:`~function.__globals__`, :attr:`~function.__name__`, " +"respectively." msgstr "" #: whatsnew/3.0.rst:794 @@ -1187,8 +1189,8 @@ msgstr "" #: whatsnew/3.0.rst:811 msgid "" -"A new built-in function :func:`next` was added to call the :meth:`~iterator." -"__next__` method on an object." +"A new built-in function :func:`next` was added to call " +"the :meth:`~iterator.__next__` method on an object." msgstr "" #: whatsnew/3.0.rst:814 @@ -1226,8 +1228,8 @@ msgstr "" #: whatsnew/3.0.rst:835 msgid "" -"Removed :func:`execfile`. Instead of ``execfile(fn)`` use ``exec(open(fn)." -"read())``." +"Removed :func:`execfile`. Instead of ``execfile(fn)`` use " +"``exec(open(fn).read())``." msgstr "" #: whatsnew/3.0.rst:838 @@ -1292,9 +1294,9 @@ msgstr "" #: whatsnew/3.0.rst:873 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)." +"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 "" #: whatsnew/3.0.rst:877 @@ -1360,8 +1362,8 @@ msgstr "" #: whatsnew/3.0.rst:920 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 " +"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 " diff --git a/whatsnew/3.1.po b/whatsnew/3.1.po index 4985bcb45..f4490479c 100644 --- a/whatsnew/3.1.po +++ b/whatsnew/3.1.po @@ -43,8 +43,8 @@ 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." +"the experiences from those implementations, a " +"new :class:`collections.OrderedDict` class has been introduced." msgstr "" #: whatsnew/3.1.rst:62 @@ -136,8 +136,8 @@ msgstr "" #: whatsnew/3.1.rst:123 msgid "" -"The supported types are :class:`int`, :class:`float`, :class:`complex` and :" -"class:`decimal.Decimal`." +"The supported types are :class:`int`, :class:`float`, :class:`complex` " +"and :class:`decimal.Decimal`." msgstr "" #: whatsnew/3.1.rst:126 @@ -226,10 +226,10 @@ msgstr "" 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." +"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 "" #: whatsnew/3.1.rst:184 @@ -409,13 +409,13 @@ msgstr "" #: whatsnew/3.1.rst:285 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`::" +"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 "" #: whatsnew/3.1.rst:294 @@ -474,10 +474,11 @@ msgstr "" #: whatsnew/3.1.rst:330 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\"::" +"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 "" #: whatsnew/3.1.rst:335 @@ -503,8 +504,8 @@ msgstr "" #: whatsnew/3.1.rst:346 msgid "" -"The :mod:`pdb` module can now access and display source code loaded via :mod:" -"`zipimport` (or any other conformant :pep:`302` loader)." +"The :mod:`pdb` module can now access and display source code loaded " +"via :mod:`zipimport` (or any other conformant :pep:`302` loader)." msgstr "" #: whatsnew/3.1.rst:349 @@ -568,13 +569,11 @@ msgstr "" #: whatsnew/3.1.rst:383 msgid "" -"In addition, several new assertion methods were added including :meth:" -"`~unittest.TestCase.assertSetEqual`, :meth:`~unittest.TestCase." -"assertDictEqual`, :meth:`!assertDictContainsSubset`, :meth:`~unittest." -"TestCase.assertListEqual`, :meth:`~unittest.TestCase.assertTupleEqual`, :" -"meth:`~unittest.TestCase.assertSequenceEqual`, :meth:`assertRaisesRegexp() " -"`, :meth:`~unittest.TestCase." -"assertIsNone`, and :meth:`~unittest.TestCase.assertIsNotNone`." +"In addition, several new assertion methods were added " +"including :meth:`~unittest.TestCase.assertSetEqual`, :meth:`~unittest.TestCase.assertDictEqual`, :meth:`!" +"assertDictContainsSubset`, :meth:`~unittest.TestCase.assertListEqual`, :meth:`~unittest.TestCase.assertTupleEqual`, :meth:`~unittest.TestCase.assertSequenceEqual`, :meth:`assertRaisesRegexp() " +"`, :meth:`~unittest.TestCase.assertIsNone`, " +"and :meth:`~unittest.TestCase.assertIsNotNone`." msgstr "" #: whatsnew/3.1.rst:394 @@ -701,8 +700,8 @@ msgstr "" #: whatsnew/3.1.rst:469 msgid "" -"(Contributed by Antoine Pitrou along with a number of other participants, :" -"issue:`4753`)." +"(Contributed by Antoine Pitrou along with a number of other " +"participants, :issue:`4753`)." msgstr "" #: whatsnew/3.1.rst:472 diff --git a/whatsnew/3.10.po b/whatsnew/3.10.po index 9d420955d..80f8e2808 100644 --- a/whatsnew/3.10.po +++ b/whatsnew/3.10.po @@ -31,8 +31,8 @@ msgstr "" #: whatsnew/3.10.rst:47 msgid "" "This article explains the new features in Python 3.10, compared to 3.9. " -"Python 3.10 was released on October 4, 2021. For full details, see the :ref:" -"`changelog `." +"Python 3.10 was released on October 4, 2021. For full details, see " +"the :ref:`changelog `." msgstr "" #: whatsnew/3.10.rst:52 @@ -182,14 +182,14 @@ msgstr "" #: whatsnew/3.10.rst:142 msgid "" -"This new syntax uses the non LL(1) capacities of the new parser. Check :pep:" -"`617` for more details." +"This new syntax uses the non LL(1) capacities of the new parser. " +"Check :pep:`617` for more details." msgstr "" #: whatsnew/3.10.rst:145 msgid "" -"(Contributed by Guido van Rossum, Pablo Galindo and Lysandros Nikolaou in :" -"issue:`12782` and :issue:`40334`.)" +"(Contributed by Guido van Rossum, Pablo Galindo and Lysandros Nikolaou " +"in :issue:`12782` and :issue:`40334`.)" msgstr "" #: whatsnew/3.10.rst:150 @@ -256,8 +256,8 @@ msgstr "" #: whatsnew/3.10.rst:191 msgid "" -"(Contributed by Pablo Galindo in :issue:`42864` and Batuhan Taskaya in :" -"issue:`40176`.)" +"(Contributed by Pablo Galindo in :issue:`42864` and Batuhan Taskaya " +"in :issue:`40176`.)" msgstr "" #: whatsnew/3.10.rst:194 @@ -558,8 +558,8 @@ msgstr "" msgid "" "The :attr:`~codeobject.co_lnotab` attribute of :ref:`code objects ` is deprecated and will be removed in 3.12. Code that needs to " -"convert from offset to line number should use the new :meth:`~codeobject." -"co_lines` method instead." +"convert from offset to line number should use the " +"new :meth:`~codeobject.co_lines` method instead." msgstr "" #: whatsnew/3.10.rst:412 @@ -980,8 +980,8 @@ msgstr "" #: whatsnew/3.10.rst:684 msgid "" -"For the full specification see :pep:`634`. Motivation and rationale are in :" -"pep:`635`, and a longer tutorial is in :pep:`636`." +"For the full specification see :pep:`634`. Motivation and rationale are " +"in :pep:`635`, and a longer tutorial is in :pep:`636`." msgstr "" #: whatsnew/3.10.rst:691 @@ -1026,8 +1026,8 @@ msgstr "" #: whatsnew/3.10.rst:716 msgid "" -"This section covers major changes affecting :pep:`484` type hints and the :" -"mod:`typing` module." +"This section covers major changes affecting :pep:`484` type hints and " +"the :mod:`typing` module." msgstr "" #: whatsnew/3.10.rst:721 @@ -1065,8 +1065,8 @@ msgstr "" #: whatsnew/3.10.rst:740 msgid "" -"This new syntax is also accepted as the second argument to :func:" -"`isinstance` and :func:`issubclass`::" +"This new syntax is also accepted as the second argument " +"to :func:`isinstance` and :func:`issubclass`::" msgstr "" #: whatsnew/3.10.rst:743 @@ -1114,9 +1114,8 @@ msgstr "" #: whatsnew/3.10.rst:769 msgid "" -"See :class:`typing.Callable`, :class:`typing.ParamSpec`, :class:`typing." -"Concatenate`, :class:`typing.ParamSpecArgs`, :class:`typing." -"ParamSpecKwargs`, and :pep:`612` for more details." +"See :class:`typing.Callable`, :class:`typing.ParamSpec`, :class:`typing.Concatenate`, :class:`typing.ParamSpecArgs`, :class:`typing.ParamSpecKwargs`, " +"and :pep:`612` for more details." msgstr "" #: whatsnew/3.10.rst:773 @@ -1172,8 +1171,8 @@ msgstr "" msgid "" ":data:`~typing.TypeGuard` has been added to the :mod:`typing` module to " "annotate type guard functions and improve information provided to static " -"type checkers during type narrowing. For more information, please see :data:" -"`~typing.TypeGuard`\\ 's documentation, and :pep:`647`." +"type checkers during type narrowing. For more information, please " +"see :data:`~typing.TypeGuard`\\ 's documentation, and :pep:`647`." msgstr "" #: whatsnew/3.10.rst:806 @@ -1195,10 +1194,10 @@ msgstr "" #: whatsnew/3.10.rst:816 msgid "" -"The views returned by :meth:`dict.keys`, :meth:`dict.values` and :meth:`dict." -"items` now all have a ``mapping`` attribute that gives a :class:`types." -"MappingProxyType` object wrapping the original dictionary. (Contributed by " -"Dennis Sweeney in :issue:`40890`.)" +"The views returned by :meth:`dict.keys`, :meth:`dict.values` " +"and :meth:`dict.items` now all have a ``mapping`` attribute that gives " +"a :class:`types.MappingProxyType` object wrapping the original dictionary. " +"(Contributed by Dennis Sweeney in :issue:`40890`.)" msgstr "" #: whatsnew/3.10.rst:821 @@ -1212,8 +1211,9 @@ msgid "" "Builtin and extension functions that take integer arguments no longer " "accept :class:`~decimal.Decimal`\\ s, :class:`~fractions.Fraction`\\ s and " "other objects that can be converted to integers only with a loss (e.g. that " -"have the :meth:`~object.__int__` method but do not have the :meth:`~object." -"__index__` method). (Contributed by Serhiy Storchaka in :issue:`37999`.)" +"have the :meth:`~object.__int__` method but do not have " +"the :meth:`~object.__index__` method). (Contributed by Serhiy Storchaka " +"in :issue:`37999`.)" msgstr "" #: whatsnew/3.10.rst:831 @@ -1248,8 +1248,8 @@ msgstr "" #: whatsnew/3.10.rst:849 msgid "" -"Static methods (:func:`@staticmethod `) and class methods (:" -"func:`@classmethod `) now inherit the method attributes " +"Static methods (:func:`@staticmethod `) and class methods " +"(:func:`@classmethod `) now inherit the method attributes " "(``__module__``, ``__name__``, ``__qualname__``, ``__doc__``, " "``__annotations__``) and have a new ``__wrapped__`` attribute. Moreover, " "static methods are now callable as regular functions. (Contributed by Victor " @@ -1260,8 +1260,8 @@ msgstr "" msgid "" "Annotations for complex targets (everything beside ``simple name`` targets " "defined by :pep:`526`) no longer cause any runtime effects with ``from " -"__future__ import annotations``. (Contributed by Batuhan Taskaya in :issue:" -"`42737`.)" +"__future__ import annotations``. (Contributed by Batuhan Taskaya " +"in :issue:`42737`.)" msgstr "" #: whatsnew/3.10.rst:860 @@ -1277,8 +1277,8 @@ msgstr "" msgid "" "Annotations consist of ``yield``, ``yield from``, ``await`` or named " "expressions are now forbidden under ``from __future__ import annotations`` " -"due to their side effects. (Contributed by Batuhan Taskaya in :issue:" -"`42725`.)" +"due to their side effects. (Contributed by Batuhan Taskaya " +"in :issue:`42725`.)" msgstr "" #: whatsnew/3.10.rst:872 @@ -1291,19 +1291,19 @@ msgstr "" #: whatsnew/3.10.rst:877 msgid "" -"Hashes of NaN values of both :class:`float` type and :class:`decimal." -"Decimal` type now depend on object identity. Formerly, they always hashed to " -"``0`` even though NaN values are not equal to one another. This caused " -"potentially quadratic runtime behavior due to excessive hash collisions when " -"creating dictionaries and sets containing multiple NaNs. (Contributed by " -"Raymond Hettinger in :issue:`43475`.)" +"Hashes of NaN values of both :class:`float` type " +"and :class:`decimal.Decimal` type now depend on object identity. Formerly, " +"they always hashed to ``0`` even though NaN values are not equal to one " +"another. This caused potentially quadratic runtime behavior due to excessive " +"hash collisions when creating dictionaries and sets containing multiple " +"NaNs. (Contributed by Raymond Hettinger in :issue:`43475`.)" msgstr "" #: whatsnew/3.10.rst:884 msgid "" "A :exc:`SyntaxError` (instead of a :exc:`NameError`) will be raised when " -"deleting the :const:`__debug__` constant. (Contributed by Donghee Na in :" -"issue:`45000`.)" +"deleting the :const:`__debug__` constant. (Contributed by Donghee Na " +"in :issue:`45000`.)" msgstr "" #: whatsnew/3.10.rst:887 @@ -1331,9 +1331,9 @@ msgstr "" #: whatsnew/3.10.rst:903 msgid "" -"Add missing :meth:`~asyncio.events.AbstractEventLoop." -"connect_accepted_socket` method. (Contributed by Alex Grönholm in :issue:" -"`41332`.)" +"Add " +"missing :meth:`~asyncio.events.AbstractEventLoop.connect_accepted_socket` " +"method. (Contributed by Alex Grönholm in :issue:`41332`.)" msgstr "" #: whatsnew/3.10.rst:908 @@ -1395,8 +1395,9 @@ msgstr "" #: whatsnew/3.10.rst:941 msgid "" -"Added the possibility of providing a *key* function to the APIs in the :mod:" -"`bisect` module. (Contributed by Raymond Hettinger in :issue:`4356`.)" +"Added the possibility of providing a *key* function to the APIs in " +"the :mod:`bisect` module. (Contributed by Raymond Hettinger " +"in :issue:`4356`.)" msgstr "" #: whatsnew/3.10.rst:945 @@ -1416,17 +1417,17 @@ msgstr "" #: whatsnew/3.10.rst:953 msgid "" "The ``__args__`` of the :ref:`parameterized generic ` " -"for :class:`collections.abc.Callable` are now consistent with :data:`typing." -"Callable`. :class:`collections.abc.Callable` generic now flattens type " -"parameters, similar to what :data:`typing.Callable` currently does. This " -"means that ``collections.abc.Callable[[int, str], str]`` will have " -"``__args__`` of ``(int, str, str)``; previously this was ``([int, str], " +"for :class:`collections.abc.Callable` are now consistent " +"with :data:`typing.Callable`. :class:`collections.abc.Callable` generic now " +"flattens type parameters, similar to what :data:`typing.Callable` currently " +"does. This means that ``collections.abc.Callable[[int, str], str]`` will " +"have ``__args__`` of ``(int, str, str)``; previously this was ``([int, str], " "str)``. To allow this change, :class:`types.GenericAlias` can now be " -"subclassed, and a subclass will be returned when subscripting the :class:" -"`collections.abc.Callable` type. Note that a :exc:`TypeError` may be raised " -"for invalid forms of parameterizing :class:`collections.abc.Callable` which " -"may have passed silently in Python 3.9. (Contributed by Ken Jin in :issue:" -"`42195`.)" +"subclassed, and a subclass will be returned when subscripting " +"the :class:`collections.abc.Callable` type. Note that a :exc:`TypeError` " +"may be raised for invalid forms of " +"parameterizing :class:`collections.abc.Callable` which may have passed " +"silently in Python 3.9. (Contributed by Ken Jin in :issue:`42195`.)" msgstr "" #: whatsnew/3.10.rst:966 @@ -1459,11 +1460,11 @@ msgstr "" #: whatsnew/3.10.rst:981 msgid "" "The extended color functions added in ncurses 6.1 will be used transparently " -"by :func:`curses.color_content`, :func:`curses.init_color`, :func:`curses." -"init_pair`, and :func:`curses.pair_content`. A new function, :func:`curses." -"has_extended_color_support`, indicates whether extended color support is " -"provided by the underlying ncurses library. (Contributed by Jeffrey " -"Kintscher and Hans Petter Jansson in :issue:`36982`.)" +"by :func:`curses.color_content`, :func:`curses.init_color`, :func:`curses.init_pair`, " +"and :func:`curses.pair_content`. A new " +"function, :func:`curses.has_extended_color_support`, indicates whether " +"extended color support is provided by the underlying ncurses library. " +"(Contributed by Jeffrey Kintscher and Hans Petter Jansson in :issue:`36982`.)" msgstr "" #: whatsnew/3.10.rst:988 @@ -1575,11 +1576,11 @@ msgid "" "3.12. Its functionality for specifying package builds has already been " "completely replaced by third-party packages ``setuptools`` and " "``packaging``, and most other commonly used APIs are available elsewhere in " -"the standard library (such as :mod:`platform`, :mod:`shutil`, :mod:" -"`subprocess` or :mod:`sysconfig`). There are no plans to migrate any other " -"functionality from ``distutils``, and applications that are using other " -"functions should plan to make private copies of the code. Refer to :pep:" -"`632` for discussion." +"the standard library (such " +"as :mod:`platform`, :mod:`shutil`, :mod:`subprocess` or :mod:`sysconfig`). " +"There are no plans to migrate any other functionality from ``distutils``, " +"and applications that are using other functions should plan to make private " +"copies of the code. Refer to :pep:`632` for discussion." msgstr "" #: whatsnew/3.10.rst:1072 @@ -1595,8 +1596,8 @@ msgstr "" #: whatsnew/3.10.rst:1215 whatsnew/3.10.rst:1341 msgid "" -"When a module does not define ``__loader__``, fall back to ``__spec__." -"loader``. (Contributed by Brett Cannon in :issue:`42133`.)" +"When a module does not define ``__loader__``, fall back to " +"``__spec__.loader``. (Contributed by Brett Cannon in :issue:`42133`.)" msgstr "" #: whatsnew/3.10.rst:1084 @@ -1615,10 +1616,11 @@ msgstr "" #: whatsnew/3.10.rst:1092 msgid "" -":class:`~enum.Enum` :func:`~object.__repr__` now returns ``enum_name." -"member_name`` and :func:`~object.__str__` now returns ``member_name``. " -"Stdlib enums available as module constants have a :func:`repr` of " -"``module_name.member_name``. (Contributed by Ethan Furman in :issue:`40066`.)" +":class:`~enum.Enum` :func:`~object.__repr__` now returns " +"``enum_name.member_name`` and :func:`~object.__str__` now returns " +"``member_name``. Stdlib enums available as module constants have " +"a :func:`repr` of ``module_name.member_name``. (Contributed by Ethan Furman " +"in :issue:`40066`.)" msgstr "" #: whatsnew/3.10.rst:1097 @@ -1633,8 +1635,9 @@ msgstr "" #: whatsnew/3.10.rst:1103 msgid "" -"Add *encoding* and *errors* parameters in :func:`fileinput.input` and :class:" -"`fileinput.FileInput`. (Contributed by Inada Naoki in :issue:`43712`.)" +"Add *encoding* and *errors* parameters in :func:`fileinput.input` " +"and :class:`fileinput.FileInput`. (Contributed by Inada Naoki " +"in :issue:`43712`.)" msgstr "" #: whatsnew/3.10.rst:1107 @@ -1651,8 +1654,8 @@ msgstr "" #: whatsnew/3.10.rst:1114 msgid "" "The :mod:`faulthandler` module now detects if a fatal error occurs during a " -"garbage collector collection. (Contributed by Victor Stinner in :issue:" -"`44466`.)" +"garbage collector collection. (Contributed by Victor Stinner " +"in :issue:`44466`.)" msgstr "" #: whatsnew/3.10.rst:1119 @@ -1661,8 +1664,9 @@ msgstr "" #: whatsnew/3.10.rst:1121 msgid "" -"Add audit hooks for :func:`gc.get_objects`, :func:`gc.get_referrers` and :" -"func:`gc.get_referents`. (Contributed by Pablo Galindo in :issue:`43439`.)" +"Add audit hooks for :func:`gc.get_objects`, :func:`gc.get_referrers` " +"and :func:`gc.get_referents`. (Contributed by Pablo Galindo " +"in :issue:`43439`.)" msgstr "" #: whatsnew/3.10.rst:1125 @@ -1671,9 +1675,9 @@ msgstr "" #: whatsnew/3.10.rst:1127 msgid "" -"Add the *root_dir* and *dir_fd* parameters in :func:`~glob.glob` and :func:" -"`~glob.iglob` which allow to specify the root directory for searching. " -"(Contributed by Serhiy Storchaka in :issue:`38144`.)" +"Add the *root_dir* and *dir_fd* parameters in :func:`~glob.glob` " +"and :func:`~glob.iglob` which allow to specify the root directory for " +"searching. (Contributed by Serhiy Storchaka in :issue:`38144`.)" msgstr "" #: whatsnew/3.10.rst:1132 @@ -1716,8 +1720,8 @@ msgstr "" #: whatsnew/3.10.rst:1154 msgid "" "Make IDLE invoke :func:`sys.excepthook` (when started without '-n'). User " -"hooks were previously ignored. (Contributed by Ken Hilton in :issue:" -"`43008`.)" +"hooks were previously ignored. (Contributed by Ken Hilton " +"in :issue:`43008`.)" msgstr "" #: whatsnew/3.10.rst:1158 @@ -1725,10 +1729,10 @@ msgid "" "Rearrange the settings dialog. Split the General tab into Windows and Shell/" "Ed tabs. Move help sources, which extend the Help menu, to the Extensions " "tab. Make space for new options and shorten the dialog. The latter makes " -"the dialog better fit small screens. (Contributed by Terry Jan Reedy in :" -"issue:`40468`.) Move the indent space setting from the Font tab to the new " -"Windows tab. (Contributed by Mark Roseman and Terry Jan Reedy in :issue:" -"`33962`.)" +"the dialog better fit small screens. (Contributed by Terry Jan Reedy " +"in :issue:`40468`.) Move the indent space setting from the Font tab to the " +"new Windows tab. (Contributed by Mark Roseman and Terry Jan Reedy " +"in :issue:`33962`.)" msgstr "" #: whatsnew/3.10.rst:1166 @@ -1756,11 +1760,12 @@ msgstr "" #: whatsnew/3.10.rst:1182 msgid "" -"Highlight the new :ref:`soft keywords ` :keyword:`match`, :" -"keyword:`case `, and :keyword:`_ ` in pattern-" -"matching statements. However, this highlighting is not perfect and will be " -"incorrect in some rare cases, including some ``_``-s in ``case`` patterns. " -"(Contributed by Tal Einat in :issue:`44010`.)" +"Highlight the new :ref:`soft keywords ` :keyword:`match`, :keyword:`case `, and :keyword:`_ " +"` in pattern-matching statements. However, this " +"highlighting is not perfect and will be incorrect in some rare cases, " +"including some ``_``-s in ``case`` patterns. (Contributed by Tal Einat " +"in :issue:`44010`.)" msgstr "" #: whatsnew/3.10.rst:1188 @@ -1792,9 +1797,9 @@ msgstr "" #: whatsnew/3.10.rst:1202 msgid "" ":ref:`importlib.metadata entry points ` now provide a nicer " -"experience for selecting entry points by group and name through a new :ref:" -"`importlib.metadata.EntryPoints ` class. See the Compatibility " -"Note in the docs for more info on the deprecation and usage." +"experience for selecting entry points by group and name through a " +"new :ref:`importlib.metadata.EntryPoints ` class. See the " +"Compatibility Note in the docs for more info on the deprecation and usage." msgstr "" #: whatsnew/3.10.rst:1208 @@ -1814,16 +1819,17 @@ msgid "" "defined on an object. It works around the quirks of accessing the " "annotations on various types of objects, and makes very few assumptions " "about the object it examines. :func:`inspect.get_annotations` can also " -"correctly un-stringize stringized annotations. :func:`inspect." -"get_annotations` is now considered best practice for accessing the " -"annotations dict defined on any Python object; for more information on best " -"practices for working with annotations, please see :ref:`annotations-howto`. " -"Relatedly, :func:`inspect.signature`, :func:`inspect.Signature." -"from_callable`, and :func:`!inspect.Signature.from_function` now call :func:" -"`inspect.get_annotations` to retrieve annotations. This means :func:`inspect." -"signature` and :func:`inspect.Signature.from_callable` can also now un-" -"stringize stringized annotations. (Contributed by Larry Hastings in :issue:" -"`43817`.)" +"correctly un-stringize stringized " +"annotations. :func:`inspect.get_annotations` is now considered best " +"practice for accessing the annotations dict defined on any Python object; " +"for more information on best practices for working with annotations, please " +"see :ref:`annotations-howto`. " +"Relatedly, :func:`inspect.signature`, :func:`inspect.Signature.from_callable`, " +"and :func:`!inspect.Signature.from_function` now " +"call :func:`inspect.get_annotations` to retrieve annotations. This " +"means :func:`inspect.signature` and :func:`inspect.Signature.from_callable` " +"can also now un-stringize stringized annotations. (Contributed by Larry " +"Hastings in :issue:`43817`.)" msgstr "" #: whatsnew/3.10.rst:1234 @@ -1832,8 +1838,8 @@ msgstr "" #: whatsnew/3.10.rst:1236 msgid "" -"Add :func:`itertools.pairwise`. (Contributed by Raymond Hettinger in :issue:" -"`38200`.)" +"Add :func:`itertools.pairwise`. (Contributed by Raymond Hettinger " +"in :issue:`38200`.)" msgstr "" #: whatsnew/3.10.rst:1240 @@ -1853,8 +1859,8 @@ msgstr "" #: whatsnew/3.10.rst:1251 msgid "" "Add a new function :func:`os.eventfd` and related helpers to wrap the " -"``eventfd2`` syscall on Linux. (Contributed by Christian Heimes in :issue:" -"`41001`.)" +"``eventfd2`` syscall on Linux. (Contributed by Christian Heimes " +"in :issue:`41001`.)" msgstr "" #: whatsnew/3.10.rst:1255 @@ -1868,8 +1874,8 @@ msgstr "" #: whatsnew/3.10.rst:1260 msgid "" "Add :const:`~os.O_EVTONLY`, :const:`~os.O_FSYNC`, :const:`~os.O_SYMLINK` " -"and :const:`~os.O_NOFOLLOW_ANY` for macOS. (Contributed by Donghee Na in :" -"issue:`43106`.)" +"and :const:`~os.O_NOFOLLOW_ANY` for macOS. (Contributed by Donghee Na " +"in :issue:`43106`.)" msgstr "" #: whatsnew/3.10.rst:1265 @@ -1895,24 +1901,25 @@ msgstr "" #: whatsnew/3.10.rst:1278 msgid "" -"Add negative indexing support to :attr:`PurePath.parents `. (Contributed by Yaroslav Pankovych in :issue:`21041`.)" +"Add negative indexing support to :attr:`PurePath.parents " +"`. (Contributed by Yaroslav Pankovych " +"in :issue:`21041`.)" msgstr "" #: whatsnew/3.10.rst:1282 msgid "" "Add :meth:`Path.hardlink_to ` method that " -"supersedes :meth:`!link_to`. The new method has the same argument order as :" -"meth:`~pathlib.Path.symlink_to`. (Contributed by Barney Gale in :issue:" -"`39950`.)" +"supersedes :meth:`!link_to`. The new method has the same argument order " +"as :meth:`~pathlib.Path.symlink_to`. (Contributed by Barney Gale " +"in :issue:`39950`.)" msgstr "" #: whatsnew/3.10.rst:1287 msgid "" ":meth:`pathlib.Path.stat` and :meth:`~pathlib.Path.chmod` now accept a " "*follow_symlinks* keyword-only argument for consistency with corresponding " -"functions in the :mod:`os` module. (Contributed by Barney Gale in :issue:" -"`39906`.)" +"functions in the :mod:`os` module. (Contributed by Barney Gale " +"in :issue:`39906`.)" msgstr "" #: whatsnew/3.10.rst:1293 @@ -1960,9 +1967,9 @@ msgstr "" #: whatsnew/3.10.rst:1318 msgid "" "Add an ``end_lineno`` attribute to the ``Function`` and ``Class`` objects in " -"the tree returned by :func:`pyclbr.readmodule` and :func:`pyclbr." -"readmodule_ex`. It matches the existing (start) ``lineno``. (Contributed by " -"Aviral Srivastava in :issue:`38307`.)" +"the tree returned by :func:`pyclbr.readmodule` " +"and :func:`pyclbr.readmodule_ex`. It matches the existing (start) " +"``lineno``. (Contributed by Aviral Srivastava in :issue:`38307`.)" msgstr "" #: whatsnew/3.10.rst:1324 @@ -1982,9 +1989,10 @@ msgstr "" #: whatsnew/3.10.rst:1333 msgid "" -"Add :func:`~statistics.covariance`, Pearson's :func:`~statistics." -"correlation`, and simple :func:`~statistics.linear_regression` functions. " -"(Contributed by Tymoteusz Wołodźko in :issue:`38490`.)" +"Add :func:`~statistics.covariance`, " +"Pearson's :func:`~statistics.correlation`, and " +"simple :func:`~statistics.linear_regression` functions. (Contributed by " +"Tymoteusz Wołodźko in :issue:`38490`.)" msgstr "" #: whatsnew/3.10.rst:1339 @@ -2025,30 +2033,31 @@ msgstr "" #: whatsnew/3.10.rst:1362 msgid "" -"The ssl module has preliminary support for OpenSSL 3.0.0 and new option :" -"const:`~ssl.OP_IGNORE_UNEXPECTED_EOF`. (Contributed by Christian Heimes in :" -"issue:`38820`, :issue:`43794`, :issue:`43788`, :issue:`43791`, :issue:" -"`43799`, :issue:`43920`, :issue:`43789`, and :issue:`43811`.)" +"The ssl module has preliminary support for OpenSSL 3.0.0 and new " +"option :const:`~ssl.OP_IGNORE_UNEXPECTED_EOF`. (Contributed by Christian " +"Heimes " +"in :issue:`38820`, :issue:`43794`, :issue:`43788`, :issue:`43791`, :issue:`43799`, :issue:`43920`, :issue:`43789`, " +"and :issue:`43811`.)" msgstr "" #: whatsnew/3.10.rst:1368 msgid "" -"Deprecated function and use of deprecated constants now result in a :exc:" -"`DeprecationWarning`. :attr:`ssl.SSLContext.options` has :data:`~ssl." -"OP_NO_SSLv2` and :data:`~ssl.OP_NO_SSLv3` set by default and therefore " -"cannot warn about setting the flag again. The :ref:`deprecation section " -"` has a list of deprecated features. (Contributed by " -"Christian Heimes in :issue:`43880`.)" +"Deprecated function and use of deprecated constants now result in " +"a :exc:`DeprecationWarning`. :attr:`ssl.SSLContext.options` " +"has :data:`~ssl.OP_NO_SSLv2` and :data:`~ssl.OP_NO_SSLv3` set by default and " +"therefore cannot warn about setting the flag again. The :ref:`deprecation " +"section ` has a list of deprecated features. " +"(Contributed by Christian Heimes in :issue:`43880`.)" msgstr "" #: whatsnew/3.10.rst:1376 msgid "" "The ssl module now has more secure default settings. Ciphers without forward " "secrecy or SHA-1 MAC are disabled by default. Security level 2 prohibits " -"weak RSA, DH, and ECC keys with less than 112 bits of security. :class:`~ssl." -"SSLContext` defaults to minimum protocol version TLS 1.2. Settings are based " -"on Hynek Schlawack's research. (Contributed by Christian Heimes in :issue:" -"`43998`.)" +"weak RSA, DH, and ECC keys with less than 112 bits of " +"security. :class:`~ssl.SSLContext` defaults to minimum protocol version TLS " +"1.2. Settings are based on Hynek Schlawack's research. (Contributed by " +"Christian Heimes in :issue:`43998`.)" msgstr "" #: whatsnew/3.10.rst:1383 @@ -2083,9 +2092,10 @@ msgstr "" #: whatsnew/3.10.rst:1400 msgid "" -"Add audit events for :func:`~sqlite3.connect/handle`, :meth:`~sqlite3." -"Connection.enable_load_extension`, and :meth:`~sqlite3.Connection." -"load_extension`. (Contributed by Erlend E. Aasland in :issue:`43762`.)" +"Add audit events for :func:`~sqlite3.connect/" +"handle`, :meth:`~sqlite3.Connection.enable_load_extension`, " +"and :meth:`~sqlite3.Connection.load_extension`. (Contributed by Erlend E. " +"Aasland in :issue:`43762`.)" msgstr "" #: whatsnew/3.10.rst:1406 @@ -2123,8 +2133,9 @@ msgstr "" #: whatsnew/3.10.rst:1426 msgid "" "Add :func:`threading.gettrace` and :func:`threading.getprofile` to retrieve " -"the functions set by :func:`threading.settrace` and :func:`threading." -"setprofile` respectively. (Contributed by Mario Corchero in :issue:`42251`.)" +"the functions set by :func:`threading.settrace` " +"and :func:`threading.setprofile` respectively. (Contributed by Mario " +"Corchero in :issue:`42251`.)" msgstr "" #: whatsnew/3.10.rst:1431 @@ -2140,10 +2151,10 @@ msgstr "" #: whatsnew/3.10.rst:1439 msgid "" -"The :func:`~traceback.format_exception`, :func:`~traceback." -"format_exception_only`, and :func:`~traceback.print_exception` functions can " -"now take an exception object as a positional-only argument. (Contributed by " -"Zackery Spytz and Matthias Bussonnier in :issue:`26389`.)" +"The :func:`~traceback.format_exception`, :func:`~traceback.format_exception_only`, " +"and :func:`~traceback.print_exception` functions can now take an exception " +"object as a positional-only argument. (Contributed by Zackery Spytz and " +"Matthias Bussonnier in :issue:`26389`.)" msgstr "" #: whatsnew/3.10.rst:1446 @@ -2152,10 +2163,10 @@ msgstr "" #: whatsnew/3.10.rst:1448 msgid "" -"Reintroduce the :data:`types.EllipsisType`, :data:`types.NoneType` and :data:" -"`types.NotImplementedType` classes, providing a new set of types readily " -"interpretable by type checkers. (Contributed by Bas van Beek in :issue:" -"`41810`.)" +"Reintroduce the :data:`types.EllipsisType`, :data:`types.NoneType` " +"and :data:`types.NotImplementedType` classes, providing a new set of types " +"readily interpretable by type checkers. (Contributed by Bas van Beek " +"in :issue:`41810`.)" msgstr "" #: whatsnew/3.10.rst:1454 @@ -2168,8 +2179,9 @@ msgstr "" #: whatsnew/3.10.rst:1458 msgid "" -"The behavior of :class:`typing.Literal` was changed to conform with :pep:" -"`586` and to match the behavior of static type checkers specified in the PEP." +"The behavior of :class:`typing.Literal` was changed to conform " +"with :pep:`586` and to match the behavior of static type checkers specified " +"in the PEP." msgstr "" #: whatsnew/3.10.rst:1461 @@ -2214,8 +2226,8 @@ msgstr "" #: whatsnew/3.10.rst:1481 msgid "" "Add new function :func:`typing.is_typeddict` to introspect if an annotation " -"is a :class:`typing.TypedDict`. (Contributed by Patrick Reader in :issue:" -"`41792`.)" +"is a :class:`typing.TypedDict`. (Contributed by Patrick Reader " +"in :issue:`41792`.)" msgstr "" #: whatsnew/3.10.rst:1485 @@ -2223,15 +2235,15 @@ msgid "" "Subclasses of ``typing.Protocol`` which only have data variables declared " "will now raise a ``TypeError`` when checked with ``isinstance`` unless they " "are decorated with :func:`~typing.runtime_checkable`. Previously, these " -"checks passed silently. Users should decorate their subclasses with the :" -"func:`!runtime_checkable` decorator if they want runtime protocols. " +"checks passed silently. Users should decorate their subclasses with " +"the :func:`!runtime_checkable` decorator if they want runtime protocols. " "(Contributed by Yurii Karabas in :issue:`38908`.)" msgstr "" #: whatsnew/3.10.rst:1493 msgid "" -"Importing from the ``typing.io`` and ``typing.re`` submodules will now emit :" -"exc:`DeprecationWarning`. These submodules have been deprecated since " +"Importing from the ``typing.io`` and ``typing.re`` submodules will now " +"emit :exc:`DeprecationWarning`. These submodules have been deprecated since " "Python 3.8 and will be removed in a future version of Python. Anything " "belonging to those submodules should be imported directly from :mod:`typing` " "instead. (Contributed by Sebastian Rittau in :issue:`38291`.)" @@ -2255,24 +2267,25 @@ msgstr "" #: whatsnew/3.10.rst:1510 msgid "" "Python versions earlier than Python 3.10 allowed using both ``;`` and ``&`` " -"as query parameter separators in :func:`urllib.parse.parse_qs` and :func:" -"`urllib.parse.parse_qsl`. Due to security concerns, and to conform with " -"newer W3C recommendations, this has been changed to allow only a single " -"separator key, with ``&`` as the default. This change also affects :func:" -"`cgi.parse` and :func:`cgi.parse_multipart` as they use the affected " -"functions internally. For more details, please see their respective " -"documentation. (Contributed by Adam Goldschmidt, Senthil Kumaran and Ken Jin " -"in :issue:`42967`.)" +"as query parameter separators in :func:`urllib.parse.parse_qs` " +"and :func:`urllib.parse.parse_qsl`. Due to security concerns, and to " +"conform with newer W3C recommendations, this has been changed to allow only " +"a single separator key, with ``&`` as the default. This change also " +"affects :func:`cgi.parse` and :func:`cgi.parse_multipart` as they use the " +"affected functions internally. For more details, please see their " +"respective documentation. (Contributed by Adam Goldschmidt, Senthil Kumaran " +"and Ken Jin in :issue:`42967`.)" msgstr "" #: whatsnew/3.10.rst:1520 msgid "" "The presence of newline or tab characters in parts of a URL allows for some " -"forms of attacks. Following the WHATWG specification that updates :rfc:" -"`3986`, ASCII newline ``\\n``, ``\\r`` and tab ``\\t`` characters are " -"stripped from the URL by the parser in :mod:`urllib.parse` preventing such " -"attacks. The removal characters are controlled by a new module level " -"variable ``urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE``. (See :gh:`88048`)" +"forms of attacks. Following the WHATWG specification that " +"updates :rfc:`3986`, ASCII newline ``\\n``, ``\\r`` and tab ``\\t`` " +"characters are stripped from the URL by the parser in :mod:`urllib.parse` " +"preventing such attacks. The removal characters are controlled by a new " +"module level variable ``urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE``. " +"(See :gh:`88048`)" msgstr "" #: whatsnew/3.10.rst:1528 @@ -2281,9 +2294,9 @@ msgstr "" #: whatsnew/3.10.rst:1530 msgid "" -"Add a :class:`~xml.sax.handler.LexicalHandler` class to the :mod:`xml.sax." -"handler` module. (Contributed by Jonathan Gossage and Zackery Spytz in :" -"issue:`35018`.)" +"Add a :class:`~xml.sax.handler.LexicalHandler` class to " +"the :mod:`xml.sax.handler` module. (Contributed by Jonathan Gossage and " +"Zackery Spytz in :issue:`35018`.)" msgstr "" #: whatsnew/3.10.rst:1535 @@ -2292,10 +2305,10 @@ msgstr "" #: whatsnew/3.10.rst:1536 msgid "" -"Add methods related to :pep:`451`: :meth:`~zipimport.zipimporter." -"find_spec`, :meth:`zipimport.zipimporter.create_module`, and :meth:" -"`zipimport.zipimporter.exec_module`. (Contributed by Brett Cannon in :issue:" -"`42131`.)" +"Add methods related " +"to :pep:`451`: :meth:`~zipimport.zipimporter.find_spec`, :meth:`zipimport.zipimporter.create_module`, " +"and :meth:`zipimport.zipimporter.exec_module`. (Contributed by Brett Cannon " +"in :issue:`42131`.)" msgstr "" #: whatsnew/3.10.rst:1541 @@ -2311,17 +2324,17 @@ msgstr "" #: whatsnew/3.10.rst:1548 msgid "" "Constructors :func:`str`, :func:`bytes` and :func:`bytearray` are now faster " -"(around 30--40% for small objects). (Contributed by Serhiy Storchaka in :" -"issue:`41334`.)" +"(around 30--40% for small objects). (Contributed by Serhiy Storchaka " +"in :issue:`41334`.)" msgstr "" #: whatsnew/3.10.rst:1552 msgid "" "The :mod:`runpy` module now imports fewer modules. The ``python3 -m module-" -"name`` command startup time is 1.4x faster in average. On Linux, ``python3 -" -"I -m module-name`` imports 69 modules on Python 3.9, whereas it only imports " -"51 modules (-18) on Python 3.10. (Contributed by Victor Stinner in :issue:" -"`41006` and :issue:`41718`.)" +"name`` command startup time is 1.4x faster in average. On Linux, ``python3 " +"-I -m module-name`` imports 69 modules on Python 3.9, whereas it only " +"imports 51 modules (-18) on Python 3.10. (Contributed by Victor Stinner " +"in :issue:`41006` and :issue:`41718`.)" msgstr "" #: whatsnew/3.10.rst:1558 @@ -2338,20 +2351,20 @@ msgid "" "When building Python with :option:`--enable-optimizations` now ``-fno-" "semantic-interposition`` is added to both the compile and link line. This " "speeds builds of the Python interpreter created with :option:`--enable-" -"shared` with ``gcc`` by up to 30%. See `this article `_ for more details. (Contributed by Victor Stinner " -"and Pablo Galindo in :issue:`38980`.)" +"shared` with ``gcc`` by up to 30%. See `this article `_ for more details. (Contributed by Victor " +"Stinner and Pablo Galindo in :issue:`38980`.)" msgstr "" #: whatsnew/3.10.rst:1572 msgid "" -"Use a new output buffer management code for :mod:`bz2` / :mod:`lzma` / :mod:" -"`zlib` modules, and add ``.readall()`` function to ``_compression." -"DecompressReader`` class. bz2 decompression is now 1.09x ~ 1.17x faster, " -"lzma decompression 1.20x ~ 1.32x faster, ``GzipFile.read(-1)`` 1.11x ~ 1.18x " -"faster. (Contributed by Ma Lin, reviewed by Gregory P. Smith, in :issue:" -"`41486`)" +"Use a new output buffer management code " +"for :mod:`bz2` / :mod:`lzma` / :mod:`zlib` modules, and add ``.readall()`` " +"function to ``_compression.DecompressReader`` class. bz2 decompression is " +"now 1.09x ~ 1.17x faster, lzma decompression 1.20x ~ 1.32x faster, " +"``GzipFile.read(-1)`` 1.11x ~ 1.18x faster. (Contributed by Ma Lin, reviewed " +"by Gregory P. Smith, in :issue:`41486`)" msgstr "" #: whatsnew/3.10.rst:1578 @@ -2376,17 +2389,18 @@ msgstr "" msgid "" "Add micro-optimizations to ``_PyType_Lookup()`` to improve type attribute " "cache lookup performance in the common case of cache hits. This makes the " -"interpreter 1.04 times faster on average. (Contributed by Dino Viehland in :" -"issue:`43452`.)" +"interpreter 1.04 times faster on average. (Contributed by Dino Viehland " +"in :issue:`43452`.)" msgstr "" #: whatsnew/3.10.rst:1594 msgid "" "The following built-in functions now support the faster :pep:`590` " -"vectorcall calling convention: :func:`map`, :func:`filter`, :func:" -"`reversed`, :func:`bool` and :func:`float`. (Contributed by Donghee Na and " -"Jeroen Demeyer in :issue:`43575`, :issue:`43287`, :issue:`41922`, :issue:" -"`41873` and :issue:`41870`.)" +"vectorcall calling " +"convention: :func:`map`, :func:`filter`, :func:`reversed`, :func:`bool` " +"and :func:`float`. (Contributed by Donghee Na and Jeroen Demeyer " +"in :issue:`43575`, :issue:`43287`, :issue:`41922`, :issue:`41873` " +"and :issue:`41870`.)" msgstr "" #: whatsnew/3.10.rst:1598 @@ -2409,27 +2423,28 @@ msgid "" "ambiguous expressions like ``[0x1for x in y]`` (which can be interpreted as " "``[0x1 for x in y]`` or ``[0x1f or x in y]``). Starting in this release, a " "deprecation warning is raised if the numeric literal is immediately followed " -"by one of keywords :keyword:`and`, :keyword:`else`, :keyword:`for`, :keyword:" -"`if`, :keyword:`in`, :keyword:`is` and :keyword:`or`. In future releases it " -"will be changed to syntax warning, and finally to syntax error. (Contributed " -"by Serhiy Storchaka in :issue:`43833`.)" +"by one of " +"keywords :keyword:`and`, :keyword:`else`, :keyword:`for`, :keyword:`if`, :keyword:`in`, :keyword:`is` " +"and :keyword:`or`. In future releases it will be changed to syntax warning, " +"and finally to syntax error. (Contributed by Serhiy Storchaka " +"in :issue:`43833`.)" msgstr "" #: whatsnew/3.10.rst:1619 msgid "" "Starting in this release, there will be a concerted effort to begin cleaning " "up old import semantics that were kept for Python 2.7 compatibility. " -"Specifically, :meth:`!find_loader`/:meth:`!find_module` (superseded by :meth:" -"`~importlib.abc.MetaPathFinder.find_spec`), :meth:`~importlib.abc.Loader." -"load_module` (superseded by :meth:`~importlib.abc.Loader.exec_module`), :" -"meth:`!module_repr` (which the import system takes care of for you), the " +"Specifically, :meth:`!find_loader`/:meth:`!find_module` (superseded " +"by :meth:`~importlib.abc.MetaPathFinder.find_spec`), :meth:`~importlib.abc.Loader.load_module` " +"(superseded by :meth:`~importlib.abc.Loader.exec_module`), :meth:`!" +"module_repr` (which the import system takes care of for you), the " "``__package__`` attribute (superseded by ``__spec__.parent``), the " "``__loader__`` attribute (superseded by ``__spec__.loader``), and the " "``__cached__`` attribute (superseded by ``__spec__.cached``) will slowly be " -"removed (as well as other classes and methods in :mod:`importlib`). :exc:" -"`ImportWarning` and/or :exc:`DeprecationWarning` will be raised as " -"appropriate to help identify code which needs updating during this " -"transition." +"removed (as well as other classes and methods " +"in :mod:`importlib`). :exc:`ImportWarning` and/or :exc:`DeprecationWarning` " +"will be raised as appropriate to help identify code which needs updating " +"during this transition." msgstr "" #: whatsnew/3.10.rst:1636 @@ -2441,17 +2456,17 @@ msgstr "" #: whatsnew/3.10.rst:1640 msgid "" -"Non-integer arguments to :func:`random.randrange` are deprecated. The :exc:" -"`ValueError` is deprecated in favor of a :exc:`TypeError`. (Contributed by " -"Serhiy Storchaka and Raymond Hettinger in :issue:`37319`.)" +"Non-integer arguments to :func:`random.randrange` are deprecated. " +"The :exc:`ValueError` is deprecated in favor of a :exc:`TypeError`. " +"(Contributed by Serhiy Storchaka and Raymond Hettinger in :issue:`37319`.)" msgstr "" #: whatsnew/3.10.rst:1644 msgid "" "The various ``load_module()`` methods of :mod:`importlib` have been " -"documented as deprecated since Python 3.6, but will now also trigger a :exc:" -"`DeprecationWarning`. Use :meth:`~importlib.abc.Loader.exec_module` instead. " -"(Contributed by Brett Cannon in :issue:`26131`.)" +"documented as deprecated since Python 3.6, but will now also trigger " +"a :exc:`DeprecationWarning`. Use :meth:`~importlib.abc.Loader.exec_module` " +"instead. (Contributed by Brett Cannon in :issue:`26131`.)" msgstr "" #: whatsnew/3.10.rst:1650 @@ -2464,8 +2479,9 @@ msgstr "" #: whatsnew/3.10.rst:1654 msgid "" "The use of :meth:`~importlib.abc.Loader.load_module` by the import system " -"now triggers an :exc:`ImportWarning` as :meth:`~importlib.abc.Loader." -"exec_module` is preferred. (Contributed by Brett Cannon in :issue:`26131`.)" +"now triggers an :exc:`ImportWarning` " +"as :meth:`~importlib.abc.Loader.exec_module` is preferred. (Contributed by " +"Brett Cannon in :issue:`26131`.)" msgstr "" #: whatsnew/3.10.rst:1659 @@ -2481,45 +2497,49 @@ msgstr "" #: whatsnew/3.10.rst:1668 msgid "" "The use of :meth:`!importlib.abc.PathEntryFinder.find_loader` by the import " -"system now triggers an :exc:`ImportWarning` as :meth:`importlib.abc." -"PathEntryFinder.find_spec` is preferred. You can use :func:`importlib.util." -"spec_from_loader` to help in porting. (Contributed by Brett Cannon in :issue:" -"`43672`.)" +"system now triggers an :exc:`ImportWarning` " +"as :meth:`importlib.abc.PathEntryFinder.find_spec` is preferred. You can " +"use :func:`importlib.util.spec_from_loader` to help in porting. (Contributed " +"by Brett Cannon in :issue:`43672`.)" msgstr "" #: whatsnew/3.10.rst:1674 msgid "" -"The various implementations of :meth:`!importlib.abc.MetaPathFinder." -"find_module` ( :meth:`!importlib.machinery.BuiltinImporter.find_module`, :" -"meth:`!importlib.machinery.FrozenImporter.find_module`, :meth:`!importlib." -"machinery.WindowsRegistryFinder.find_module`, :meth:`!importlib.machinery." -"PathFinder.find_module`, :meth:`!importlib.abc.MetaPathFinder." -"find_module` ), :meth:`!importlib.abc.PathEntryFinder.find_module` ( :meth:`!" -"importlib.machinery.FileFinder.find_module` ), and :meth:`!importlib.abc." -"PathEntryFinder.find_loader` ( :meth:`!importlib.machinery.FileFinder." -"find_loader` ) now raise :exc:`DeprecationWarning` and are slated for " -"removal in Python 3.12 (previously they were documented as deprecated in " -"Python 3.4). (Contributed by Brett Cannon in :issue:`42135`.)" +"The various implementations of :meth:`!" +"importlib.abc.MetaPathFinder.find_module` ( :meth:`!" +"importlib.machinery.BuiltinImporter.find_module`, :meth:`!" +"importlib.machinery.FrozenImporter.find_module`, :meth:`!" +"importlib.machinery.WindowsRegistryFinder.find_module`, :meth:`!" +"importlib.machinery.PathFinder.find_module`, :meth:`!" +"importlib.abc.MetaPathFinder.find_module` ), :meth:`!" +"importlib.abc.PathEntryFinder.find_module` ( :meth:`!" +"importlib.machinery.FileFinder.find_module` ), and :meth:`!" +"importlib.abc.PathEntryFinder.find_loader` ( :meth:`!" +"importlib.machinery.FileFinder.find_loader` ) now " +"raise :exc:`DeprecationWarning` and are slated for removal in Python 3.12 " +"(previously they were documented as deprecated in Python 3.4). (Contributed " +"by Brett Cannon in :issue:`42135`.)" msgstr "" #: whatsnew/3.10.rst:1689 msgid "" -":class:`!importlib.abc.Finder` is deprecated (including its sole method, :" -"meth:`!find_module`). Both :class:`importlib.abc.MetaPathFinder` and :class:" -"`importlib.abc.PathEntryFinder` no longer inherit from the class. Users " -"should inherit from one of these two classes as appropriate instead. " +":class:`!importlib.abc.Finder` is deprecated (including its sole " +"method, :meth:`!find_module`). Both :class:`importlib.abc.MetaPathFinder` " +"and :class:`importlib.abc.PathEntryFinder` no longer inherit from the class. " +"Users should inherit from one of these two classes as appropriate instead. " "(Contributed by Brett Cannon in :issue:`42135`.)" msgstr "" #: whatsnew/3.10.rst:1696 msgid "" "The deprecations of :mod:`!imp`, :func:`!importlib.find_loader`, :func:`!" -"importlib.util.set_package_wrapper`, :func:`!importlib.util." -"set_loader_wrapper`, :func:`!importlib.util.module_for_loader`, :class:`!" -"pkgutil.ImpImporter`, and :class:`!pkgutil.ImpLoader` have all been updated " -"to list Python 3.12 as the slated version of removal (they began raising :" -"exc:`DeprecationWarning` in previous versions of Python). (Contributed by " -"Brett Cannon in :issue:`43720`.)" +"importlib.util.set_package_wrapper`, :func:`!" +"importlib.util.set_loader_wrapper`, :func:`!" +"importlib.util.module_for_loader`, :class:`!pkgutil.ImpImporter`, " +"and :class:`!pkgutil.ImpLoader` have all been updated to list Python 3.12 as " +"the slated version of removal (they began raising :exc:`DeprecationWarning` " +"in previous versions of Python). (Contributed by Brett Cannon " +"in :issue:`43720`.)" msgstr "" #: whatsnew/3.10.rst:1706 @@ -2532,18 +2552,18 @@ msgstr "" #: whatsnew/3.10.rst:1712 msgid "" -":meth:`!importlib.abc.Loader.module_repr`, :meth:`!importlib.machinery." -"FrozenLoader.module_repr`, and :meth:`!importlib.machinery.BuiltinLoader." -"module_repr` are deprecated and slated for removal in Python 3.12. " -"(Contributed by Brett Cannon in :issue:`42136`.)" +":meth:`!importlib.abc.Loader.module_repr`, :meth:`!" +"importlib.machinery.FrozenLoader.module_repr`, and :meth:`!" +"importlib.machinery.BuiltinLoader.module_repr` are deprecated and slated for " +"removal in Python 3.12. (Contributed by Brett Cannon in :issue:`42136`.)" msgstr "" #: whatsnew/3.10.rst:1718 msgid "" "``sqlite3.OptimizedUnicode`` has been undocumented and obsolete since Python " "3.3, when it was made an alias to :class:`str`. It is now deprecated, " -"scheduled for removal in Python 3.12. (Contributed by Erlend E. Aasland in :" -"issue:`42264`.)" +"scheduled for removal in Python 3.12. (Contributed by Erlend E. Aasland " +"in :issue:`42264`.)" msgstr "" #: whatsnew/3.10.rst:1723 @@ -2620,16 +2640,17 @@ msgstr "" msgid "" ":data:`!OP_NO_SSLv2`, :data:`!OP_NO_SSLv3`, :data:`!OP_NO_TLSv1`, :data:`!" "OP_NO_TLSv1_1`, :data:`!OP_NO_TLSv1_2`, and :data:`!OP_NO_TLSv1_3` are " -"replaced by :attr:`~ssl.SSLContext.minimum_version` and :attr:`~ssl." -"SSLContext.maximum_version`." +"replaced by :attr:`~ssl.SSLContext.minimum_version` " +"and :attr:`~ssl.SSLContext.maximum_version`." msgstr "" #: whatsnew/3.10.rst:1768 msgid "" -":data:`!PROTOCOL_SSLv2`, :data:`!PROTOCOL_SSLv3`, :data:`!PROTOCOL_SSLv23`, :" -"data:`!PROTOCOL_TLSv1`, :data:`!PROTOCOL_TLSv1_1`, :data:`!" -"PROTOCOL_TLSv1_2`, and :const:`!PROTOCOL_TLS` are deprecated in favor of :" -"const:`~ssl.PROTOCOL_TLS_CLIENT` and :const:`~ssl.PROTOCOL_TLS_SERVER`" +":data:`!PROTOCOL_SSLv2`, :data:`!PROTOCOL_SSLv3`, :data:`!" +"PROTOCOL_SSLv23`, :data:`!PROTOCOL_TLSv1`, :data:`!" +"PROTOCOL_TLSv1_1`, :data:`!PROTOCOL_TLSv1_2`, and :const:`!PROTOCOL_TLS` are " +"deprecated in favor of :const:`~ssl.PROTOCOL_TLS_CLIENT` " +"and :const:`~ssl.PROTOCOL_TLS_SERVER`" msgstr "" #: whatsnew/3.10.rst:1774 @@ -2646,8 +2667,8 @@ msgstr "" #: whatsnew/3.10.rst:1780 msgid "" -"NPN features like :meth:`ssl.SSLSocket.selected_npn_protocol` and :meth:`ssl." -"SSLContext.set_npn_protocols` are replaced by ALPN." +"NPN features like :meth:`ssl.SSLSocket.selected_npn_protocol` " +"and :meth:`ssl.SSLContext.set_npn_protocols` are replaced by ALPN." msgstr "" #: whatsnew/3.10.rst:1783 @@ -2660,9 +2681,9 @@ msgstr "" #: whatsnew/3.10.rst:1788 msgid "" -"Importing from the ``typing.io`` and ``typing.re`` submodules will now emit :" -"exc:`DeprecationWarning`. These submodules will be removed in a future " -"version of Python. Anything belonging to these submodules should be " +"Importing from the ``typing.io`` and ``typing.re`` submodules will now " +"emit :exc:`DeprecationWarning`. These submodules will be removed in a " +"future version of Python. Anything belonging to these submodules should be " "imported directly from :mod:`typing` instead. (Contributed by Sebastian " "Rittau in :issue:`38291`.)" msgstr "" @@ -2675,8 +2696,8 @@ msgstr "" msgid "" "Removed special methods ``__int__``, ``__float__``, ``__floordiv__``, " "``__mod__``, ``__divmod__``, ``__rfloordiv__``, ``__rmod__`` and " -"``__rdivmod__`` of the :class:`complex` class. They always raised a :exc:" -"`TypeError`. (Contributed by Serhiy Storchaka in :issue:`41974`.)" +"``__rdivmod__`` of the :class:`complex` class. They always raised " +"a :exc:`TypeError`. (Contributed by Serhiy Storchaka in :issue:`41974`.)" msgstr "" #: whatsnew/3.10.rst:1805 @@ -2684,16 +2705,16 @@ msgid "" "The ``ParserBase.error()`` method from the private and undocumented " "``_markupbase`` module has been removed. :class:`html.parser.HTMLParser` is " "the only subclass of ``ParserBase`` and its ``error()`` implementation was " -"already removed in Python 3.5. (Contributed by Berker Peksag in :issue:" -"`31844`.)" +"already removed in Python 3.5. (Contributed by Berker Peksag " +"in :issue:`31844`.)" msgstr "" #: whatsnew/3.10.rst:1811 msgid "" "Removed the ``unicodedata.ucnhash_CAPI`` attribute which was an internal " "PyCapsule object. The related private ``_PyUnicode_Name_CAPI`` structure was " -"moved to the internal C API. (Contributed by Victor Stinner in :issue:" -"`42157`.)" +"moved to the internal C API. (Contributed by Victor Stinner " +"in :issue:`42157`.)" msgstr "" #: whatsnew/3.10.rst:1816 @@ -2731,15 +2752,15 @@ msgstr "" #: whatsnew/3.10.rst:1837 msgid "" "Remove deprecated aliases to :ref:`collections-abstract-base-classes` from " -"the :mod:`collections` module. (Contributed by Victor Stinner in :issue:" -"`37324`.)" +"the :mod:`collections` module. (Contributed by Victor Stinner " +"in :issue:`37324`.)" msgstr "" #: whatsnew/3.10.rst:1841 msgid "" -"The ``loop`` parameter has been removed from most of :mod:`asyncio`\\ 's :" -"doc:`high-level API <../library/asyncio-api-index>` following deprecation in " -"Python 3.8. The motivation behind this change is multifold:" +"The ``loop`` parameter has been removed from most of :mod:`asyncio`\\ " +"'s :doc:`high-level API <../library/asyncio-api-index>` following " +"deprecation in Python 3.8. The motivation behind this change is multifold:" msgstr "" #: whatsnew/3.10.rst:1845 @@ -2801,18 +2822,19 @@ msgstr "" #: whatsnew/3.10.rst:1882 msgid "" -"The *etype* parameters of the :func:`~traceback.format_exception`, :func:" -"`~traceback.format_exception_only`, and :func:`~traceback.print_exception` " -"functions in the :mod:`traceback` module have been renamed to *exc*. " -"(Contributed by Zackery Spytz and Matthias Bussonnier in :issue:`26389`.)" +"The *etype* parameters of " +"the :func:`~traceback.format_exception`, :func:`~traceback.format_exception_only`, " +"and :func:`~traceback.print_exception` functions in the :mod:`traceback` " +"module have been renamed to *exc*. (Contributed by Zackery Spytz and " +"Matthias Bussonnier in :issue:`26389`.)" msgstr "" #: whatsnew/3.10.rst:1888 msgid "" -":mod:`atexit`: At Python exit, if a callback registered with :func:`atexit." -"register` fails, its exception is now logged. Previously, only some " -"exceptions were logged, and the last exception was always silently ignored. " -"(Contributed by Victor Stinner in :issue:`42639`.)" +":mod:`atexit`: At Python exit, if a callback registered " +"with :func:`atexit.register` fails, its exception is now logged. Previously, " +"only some exceptions were logged, and the last exception was always silently " +"ignored. (Contributed by Victor Stinner in :issue:`42639`.)" msgstr "" #: whatsnew/3.10.rst:1894 @@ -2824,23 +2846,23 @@ msgid "" "accesses the arguments via :func:`typing.get_args` or ``__args__`` need to " "account for this change. Furthermore, :exc:`TypeError` may be raised for " "invalid forms of parameterizing :class:`collections.abc.Callable` which may " -"have passed silently in Python 3.9. (Contributed by Ken Jin in :issue:" -"`42195`.)" +"have passed silently in Python 3.9. (Contributed by Ken Jin " +"in :issue:`42195`.)" msgstr "" #: whatsnew/3.10.rst:1904 msgid "" ":meth:`socket.htons` and :meth:`socket.ntohs` now raise :exc:`OverflowError` " "instead of :exc:`DeprecationWarning` if the given parameter will not fit in " -"a 16-bit unsigned integer. (Contributed by Erlend E. Aasland in :issue:" -"`42393`.)" +"a 16-bit unsigned integer. (Contributed by Erlend E. Aasland " +"in :issue:`42393`.)" msgstr "" #: whatsnew/3.10.rst:1909 msgid "" -"The ``loop`` parameter has been removed from most of :mod:`asyncio`\\ 's :" -"doc:`high-level API <../library/asyncio-api-index>` following deprecation in " -"Python 3.8." +"The ``loop`` parameter has been removed from most of :mod:`asyncio`\\ " +"'s :doc:`high-level API <../library/asyncio-api-index>` following " +"deprecation in Python 3.8." msgstr "" #: whatsnew/3.10.rst:1913 @@ -2874,11 +2896,11 @@ msgstr "" msgid "" "The :data:`types.FunctionType` constructor now inherits the current builtins " "if the *globals* dictionary has no ``\"__builtins__\"`` key, rather than " -"using ``{\"None\": None}`` as builtins: same behavior as :func:`eval` and :" -"func:`exec` functions. Defining a function with ``def function(...): ...`` " -"in Python is not affected, globals cannot be overridden with this syntax: it " -"also inherits the current builtins. (Contributed by Victor Stinner in :issue:" -"`42990`.)" +"using ``{\"None\": None}`` as builtins: same behavior as :func:`eval` " +"and :func:`exec` functions. Defining a function with ``def " +"function(...): ...`` in Python is not affected, globals cannot be overridden " +"with this syntax: it also inherits the current builtins. (Contributed by " +"Victor Stinner in :issue:`42990`.)" msgstr "" #: whatsnew/3.10.rst:1939 @@ -2922,9 +2944,10 @@ msgstr "" msgid "" "To compile a file given a ``char *`` filename, explicitly open the file, " "read it and compile the result. One way to do this is using the :py:mod:`io` " -"module with :c:func:`PyImport_ImportModule`, :c:func:`PyObject_CallMethod`, :" -"c:func:`PyBytes_AsString` and :c:func:`Py_CompileString`, as sketched below. " -"(Declarations and error handling are omitted.) ::" +"module " +"with :c:func:`PyImport_ImportModule`, :c:func:`PyObject_CallMethod`, :c:func:`PyBytes_AsString` " +"and :c:func:`Py_CompileString`, as sketched below. (Declarations and error " +"handling are omitted.) ::" msgstr "" #: whatsnew/3.10.rst:1966 @@ -2945,8 +2968,8 @@ msgid "" "string. This means that this number needs to be multiplied by 2 to be used " "with APIs that expect a byte offset instead (like :c:func:`PyCode_Addr2Line` " "for example). Notice as well that the :attr:`!f_lasti` member of " -"``FrameObject`` objects is not considered stable: please use :c:func:" -"`PyFrame_GetLineNumber` instead." +"``FrameObject`` objects is not considered stable: please " +"use :c:func:`PyFrame_GetLineNumber` instead." msgstr "" #: whatsnew/3.10.rst:1981 @@ -3008,8 +3031,8 @@ msgstr "" msgid "" "Some Linux distribution packaging policies recommend against bundling " "dependencies. For example, Fedora installs wheel packages in the ``/usr/" -"share/python-wheels/`` directory and don't install the ``ensurepip." -"_bundled`` package." +"share/python-wheels/`` directory and don't install the " +"``ensurepip._bundled`` package." msgstr "" #: whatsnew/3.10.rst:2019 @@ -3066,9 +3089,9 @@ msgstr "" #: whatsnew/3.10.rst:2055 msgid "" -"The result of :c:func:`PyNumber_Index` now always has exact type :class:" -"`int`. Previously, the result could have been an instance of a subclass of " -"``int``. (Contributed by Serhiy Storchaka in :issue:`40792`.)" +"The result of :c:func:`PyNumber_Index` now always has exact " +"type :class:`int`. Previously, the result could have been an instance of a " +"subclass of ``int``. (Contributed by Serhiy Storchaka in :issue:`40792`.)" msgstr "" #: whatsnew/3.10.rst:2059 @@ -3080,10 +3103,11 @@ msgstr "" #: whatsnew/3.10.rst:2064 msgid "" -"The :c:func:`PyDateTime_DATE_GET_TZINFO` and :c:func:" -"`PyDateTime_TIME_GET_TZINFO` macros have been added for accessing the " -"``tzinfo`` attributes of :class:`datetime.datetime` and :class:`datetime." -"time` objects. (Contributed by Zackery Spytz in :issue:`30155`.)" +"The :c:func:`PyDateTime_DATE_GET_TZINFO` " +"and :c:func:`PyDateTime_TIME_GET_TZINFO` macros have been added for " +"accessing the ``tzinfo`` attributes of :class:`datetime.datetime` " +"and :class:`datetime.time` objects. (Contributed by Zackery Spytz " +"in :issue:`30155`.)" msgstr "" #: whatsnew/3.10.rst:2070 @@ -3107,9 +3131,9 @@ msgstr "" #: whatsnew/3.10.rst:2081 msgid "" -"Add :c:func:`PyModule_AddObjectRef` function: similar to :c:func:" -"`PyModule_AddObject` but don't steal a reference to the value on success. " -"(Contributed by Victor Stinner in :issue:`1635741`.)" +"Add :c:func:`PyModule_AddObjectRef` function: similar " +"to :c:func:`PyModule_AddObject` but don't steal a reference to the value on " +"success. (Contributed by Victor Stinner in :issue:`1635741`.)" msgstr "" #: whatsnew/3.10.rst:2086 @@ -3121,9 +3145,9 @@ msgstr "" #: whatsnew/3.10.rst:2090 msgid "" -"The :c:func:`PyType_FromSpecWithBases` and :c:func:" -"`PyType_FromModuleAndSpec` functions now accept a single class as the " -"*bases* argument. (Contributed by Serhiy Storchaka in :issue:`42423`.)" +"The :c:func:`PyType_FromSpecWithBases` " +"and :c:func:`PyType_FromModuleAndSpec` functions now accept a single class " +"as the *bases* argument. (Contributed by Serhiy Storchaka in :issue:`42423`.)" msgstr "" #: whatsnew/3.10.rst:2094 @@ -3156,37 +3180,37 @@ msgid "" "The limited C API is now supported if :ref:`Python is built in debug mode " "` (if the ``Py_DEBUG`` macro is defined). In the limited C API, " "the :c:func:`Py_INCREF` and :c:func:`Py_DECREF` functions are now " -"implemented as opaque function calls, rather than accessing directly the :c:" -"member:`PyObject.ob_refcnt` member, if Python is built in debug mode and the " -"``Py_LIMITED_API`` macro targets Python 3.10 or newer. It became possible to " -"support the limited C API in debug mode because the :c:type:`PyObject` " -"structure is the same in release and debug mode since Python 3.8 (see :issue:" -"`36465`)." +"implemented as opaque function calls, rather than accessing directly " +"the :c:member:`PyObject.ob_refcnt` member, if Python is built in debug mode " +"and the ``Py_LIMITED_API`` macro targets Python 3.10 or newer. It became " +"possible to support the limited C API in debug mode because " +"the :c:type:`PyObject` structure is the same in release and debug mode since " +"Python 3.8 (see :issue:`36465`)." msgstr "" #: whatsnew/3.10.rst:2120 msgid "" "The limited C API is still not supported in the :option:`--with-trace-refs` " -"special build (``Py_TRACE_REFS`` macro). (Contributed by Victor Stinner in :" -"issue:`43688`.)" +"special build (``Py_TRACE_REFS`` macro). (Contributed by Victor Stinner " +"in :issue:`43688`.)" msgstr "" #: whatsnew/3.10.rst:2124 msgid "" "Add the :c:func:`Py_Is(x, y) ` function to test if the *x* object is " -"the *y* object, the same as ``x is y`` in Python. Add also the :c:func:" -"`Py_IsNone`, :c:func:`Py_IsTrue`, :c:func:`Py_IsFalse` functions to test if " -"an object is, respectively, the ``None`` singleton, the ``True`` singleton " -"or the ``False`` singleton. (Contributed by Victor Stinner in :issue:" -"`43753`.)" +"the *y* object, the same as ``x is y`` in Python. Add also " +"the :c:func:`Py_IsNone`, :c:func:`Py_IsTrue`, :c:func:`Py_IsFalse` functions " +"to test if an object is, respectively, the ``None`` singleton, the ``True`` " +"singleton or the ``False`` singleton. (Contributed by Victor Stinner " +"in :issue:`43753`.)" msgstr "" #: whatsnew/3.10.rst:2131 msgid "" -"Add new functions to control the garbage collector from C code: :c:func:" -"`PyGC_Enable()`, :c:func:`PyGC_Disable()`, :c:func:`PyGC_IsEnabled()`. These " -"functions allow to activate, deactivate and query the state of the garbage " -"collector from C code without having to import the :mod:`gc` module." +"Add new functions to control the garbage collector from C " +"code: :c:func:`PyGC_Enable()`, :c:func:`PyGC_Disable()`, :c:func:`PyGC_IsEnabled()`. " +"These functions allow to activate, deactivate and query the state of the " +"garbage collector from C code without having to import the :mod:`gc` module." msgstr "" #: whatsnew/3.10.rst:2138 @@ -3204,11 +3228,11 @@ msgstr "" #: whatsnew/3.10.rst:2149 msgid "" -"The ``PY_SSIZE_T_CLEAN`` macro must now be defined to use :c:func:" -"`PyArg_ParseTuple` and :c:func:`Py_BuildValue` formats which use ``#``: " -"``es#``, ``et#``, ``s#``, ``u#``, ``y#``, ``z#``, ``U#`` and ``Z#``. See :" -"ref:`arg-parsing` and :pep:`353`. (Contributed by Victor Stinner in :issue:" -"`40943`.)" +"The ``PY_SSIZE_T_CLEAN`` macro must now be defined to " +"use :c:func:`PyArg_ParseTuple` and :c:func:`Py_BuildValue` formats which use " +"``#``: ``es#``, ``et#``, ``s#``, ``u#``, ``y#``, ``z#``, ``U#`` and ``Z#``. " +"See :ref:`arg-parsing` and :pep:`353`. (Contributed by Victor Stinner " +"in :issue:`40943`.)" msgstr "" #: whatsnew/3.10.rst:2155 @@ -3254,20 +3278,19 @@ msgstr "" #: whatsnew/3.10.rst:2179 msgid "" -":c:func:`Py_GetPath`, :c:func:`Py_GetPrefix`, :c:func:`Py_GetExecPrefix`, :c:" -"func:`Py_GetProgramFullPath`, :c:func:`Py_GetPythonHome` and :c:func:" -"`Py_GetProgramName` functions now return ``NULL`` if called before :c:func:" -"`Py_Initialize` (before Python is initialized). Use the new :ref:`init-" -"config` API to get the :ref:`init-path-config`. (Contributed by Victor " -"Stinner in :issue:`42260`.)" +":c:func:`Py_GetPath`, :c:func:`Py_GetPrefix`, :c:func:`Py_GetExecPrefix`, :c:func:`Py_GetProgramFullPath`, :c:func:`Py_GetPythonHome` " +"and :c:func:`Py_GetProgramName` functions now return ``NULL`` if called " +"before :c:func:`Py_Initialize` (before Python is initialized). Use the " +"new :ref:`init-config` API to get the :ref:`init-path-config`. (Contributed " +"by Victor Stinner in :issue:`42260`.)" msgstr "" #: whatsnew/3.10.rst:2186 msgid "" -":c:func:`PyList_SET_ITEM`, :c:func:`PyTuple_SET_ITEM` and :c:func:" -"`PyCell_SET` macros can no longer be used as l-value or r-value. For " -"example, ``x = PyList_SET_ITEM(a, b, c)`` and ``PyList_SET_ITEM(a, b, c) = " -"x`` now fail with a compiler error. It prevents bugs like ``if " +":c:func:`PyList_SET_ITEM`, :c:func:`PyTuple_SET_ITEM` " +"and :c:func:`PyCell_SET` macros can no longer be used as l-value or r-value. " +"For example, ``x = PyList_SET_ITEM(a, b, c)`` and ``PyList_SET_ITEM(a, b, c) " +"= x`` now fail with a compiler error. It prevents bugs like ``if " "(PyList_SET_ITEM (a, b, c) < 0) ...`` test. (Contributed by Zackery Spytz " "and Victor Stinner in :issue:`30459`.)" msgstr "" @@ -3275,12 +3298,12 @@ msgstr "" #: whatsnew/3.10.rst:2193 msgid "" "The non-limited API files ``odictobject.h``, ``parser_interface.h``, " -"``picklebufobject.h``, ``pyarena.h``, ``pyctype.h``, ``pydebug.h``, ``pyfpe." -"h``, and ``pytime.h`` have been moved to the ``Include/cpython`` directory. " -"These files must not be included directly, as they are already included in " -"``Python.h``; see :ref:`api-includes`. If they have been included directly, " -"consider including ``Python.h`` instead. (Contributed by Nicholas Sim in :" -"issue:`35134`.)" +"``picklebufobject.h``, ``pyarena.h``, ``pyctype.h``, ``pydebug.h``, " +"``pyfpe.h``, and ``pytime.h`` have been moved to the ``Include/cpython`` " +"directory. These files must not be included directly, as they are already " +"included in ``Python.h``; see :ref:`api-includes`. If they have been " +"included directly, consider including ``Python.h`` instead. (Contributed by " +"Nicholas Sim in :issue:`35134`.)" msgstr "" #: whatsnew/3.10.rst:2201 @@ -3288,8 +3311,8 @@ msgid "" "Use the :c:macro:`Py_TPFLAGS_IMMUTABLETYPE` type flag to create immutable " "type objects. Do not rely on :c:macro:`Py_TPFLAGS_HEAPTYPE` to decide if a " "type object is mutable or not; check if :c:macro:`Py_TPFLAGS_IMMUTABLETYPE` " -"is set instead. (Contributed by Victor Stinner and Erlend E. Aasland in :" -"issue:`43908`.)" +"is set instead. (Contributed by Victor Stinner and Erlend E. Aasland " +"in :issue:`43908`.)" msgstr "" #: whatsnew/3.10.rst:2207 @@ -3314,20 +3337,20 @@ msgstr "" #: whatsnew/3.10.rst:2225 msgid "" -"``Py_UNICODE_strlen``: use :c:func:`PyUnicode_GetLength` or :c:macro:" -"`PyUnicode_GET_LENGTH`" +"``Py_UNICODE_strlen``: use :c:func:`PyUnicode_GetLength` " +"or :c:macro:`PyUnicode_GET_LENGTH`" msgstr "" #: whatsnew/3.10.rst:2227 msgid "" -"``Py_UNICODE_strcat``: use :c:func:`PyUnicode_CopyCharacters` or :c:func:" -"`PyUnicode_FromFormat`" +"``Py_UNICODE_strcat``: use :c:func:`PyUnicode_CopyCharacters` " +"or :c:func:`PyUnicode_FromFormat`" msgstr "" #: whatsnew/3.10.rst:2229 msgid "" -"``Py_UNICODE_strcpy``, ``Py_UNICODE_strncpy``: use :c:func:" -"`PyUnicode_CopyCharacters` or :c:func:`PyUnicode_Substring`" +"``Py_UNICODE_strcpy``, ``Py_UNICODE_strncpy``: " +"use :c:func:`PyUnicode_CopyCharacters` or :c:func:`PyUnicode_Substring`" msgstr "" #: whatsnew/3.10.rst:2231 @@ -3340,8 +3363,8 @@ msgstr "" #: whatsnew/3.10.rst:2233 msgid "" -"``Py_UNICODE_strchr``, ``Py_UNICODE_strrchr``: use :c:func:" -"`PyUnicode_FindChar`" +"``Py_UNICODE_strchr``, ``Py_UNICODE_strrchr``: " +"use :c:func:`PyUnicode_FindChar`" msgstr "" #: whatsnew/3.10.rst:2236 @@ -3352,15 +3375,16 @@ msgstr "" #: whatsnew/3.10.rst:2239 msgid "" -"Removed ``PyLong_FromUnicode()``. Please migrate to :c:func:" -"`PyLong_FromUnicodeObject`. (Contributed by Inada Naoki in :issue:`41103`.)" +"Removed ``PyLong_FromUnicode()``. Please migrate " +"to :c:func:`PyLong_FromUnicodeObject`. (Contributed by Inada Naoki " +"in :issue:`41103`.)" msgstr "" #: whatsnew/3.10.rst:2242 msgid "" -"Removed ``PyUnicode_AsUnicodeCopy()``. Please use :c:func:" -"`PyUnicode_AsUCS4Copy` or :c:func:`PyUnicode_AsWideCharString` (Contributed " -"by Inada Naoki in :issue:`41103`.)" +"Removed ``PyUnicode_AsUnicodeCopy()``. Please " +"use :c:func:`PyUnicode_AsUCS4Copy` or :c:func:`PyUnicode_AsWideCharString` " +"(Contributed by Inada Naoki in :issue:`41103`.)" msgstr "" #: whatsnew/3.10.rst:2246 @@ -3373,16 +3397,17 @@ msgstr "" #: whatsnew/3.10.rst:2250 msgid "" "Removed undocumented macros ``Py_ALLOW_RECURSION`` and " -"``Py_END_ALLOW_RECURSION`` and the ``recursion_critical`` field of the :c:" -"type:`PyInterpreterState` structure. (Contributed by Serhiy Storchaka in :" -"issue:`41936`.)" +"``Py_END_ALLOW_RECURSION`` and the ``recursion_critical`` field of " +"the :c:type:`PyInterpreterState` structure. (Contributed by Serhiy Storchaka " +"in :issue:`41936`.)" msgstr "" #: whatsnew/3.10.rst:2255 msgid "" "Removed the undocumented ``PyOS_InitInterrupts()`` function. Initializing " -"Python already implicitly installs signal handlers: see :c:member:`PyConfig." -"install_signal_handlers`. (Contributed by Victor Stinner in :issue:`41713`.)" +"Python already implicitly installs signal handlers: " +"see :c:member:`PyConfig.install_signal_handlers`. (Contributed by Victor " +"Stinner in :issue:`41713`.)" msgstr "" #: whatsnew/3.10.rst:2260 @@ -3528,8 +3553,8 @@ msgstr "" #: whatsnew/3.10.rst:2319 msgid "" "These functions were undocumented, excluded from the limited C API, and were " -"only used internally by the compiler. (Contributed by Victor Stinner in :" -"issue:`43244`.)" +"only used internally by the compiler. (Contributed by Victor Stinner " +"in :issue:`43244`.)" msgstr "" #: whatsnew/3.10.rst:2323 @@ -3564,8 +3589,8 @@ msgid "" "The deprecated :mod:`!mailcap` module now refuses to inject unsafe text " "(filenames, MIME types, parameters) into shell commands. Instead of using " "such text, it will warn and act as if a match was not found (or for test " -"commands, as if the test failed). (Contributed by Petr Viktorin in :gh:" -"`98966`.)" +"commands, as if the test failed). (Contributed by Petr Viktorin " +"in :gh:`98966`.)" msgstr "" #: whatsnew/3.10.rst:2350 diff --git a/whatsnew/3.11.po b/whatsnew/3.11.po index 15b3c0953..f79bef099 100644 --- a/whatsnew/3.11.po +++ b/whatsnew/3.11.po @@ -31,8 +31,8 @@ msgstr "" #: whatsnew/3.11.rst:47 msgid "" "This article explains the new features in Python 3.11, compared to 3.10. " -"Python 3.11 was released on October 24, 2022. For full details, see the :ref:" -"`changelog `." +"Python 3.11 was released on October 24, 2022. For full details, see " +"the :ref:`changelog `." msgstr "" #: whatsnew/3.11.rst:55 @@ -42,8 +42,8 @@ msgstr "" #: whatsnew/3.11.rst:60 msgid "" "Python 3.11 is between 10-60% faster than Python 3.10. On average, we " -"measured a 1.25x speedup on the standard benchmark suite. See :ref:" -"`whatsnew311-faster-cpython` for details." +"measured a 1.25x speedup on the standard benchmark suite. " +"See :ref:`whatsnew311-faster-cpython` for details." msgstr "" #: whatsnew/3.11.rst:66 @@ -200,9 +200,9 @@ msgstr "" #: whatsnew/3.11.rst:159 msgid "" "Additionally, the information used by the enhanced traceback feature is made " -"available via a general API, that can be used to correlate :term:`bytecode` :" -"ref:`instructions ` with source code location. This information " -"can be retrieved using:" +"available via a general API, that can be used to " +"correlate :term:`bytecode` :ref:`instructions ` with source code " +"location. This information can be retrieved using:" msgstr "" #: whatsnew/3.11.rst:164 @@ -225,8 +225,8 @@ msgid "" "may result in a small increase in interpreter memory usage and disk usage " "for compiled Python files. To avoid storing the extra information and " "deactivate printing the extra traceback information, use the :option:`-X " -"no_debug_ranges <-X>` command line option or the :envvar:" -"`PYTHONNODEBUGRANGES` environment variable." +"no_debug_ranges <-X>` command line option or " +"the :envvar:`PYTHONNODEBUGRANGES` environment variable." msgstr "" #: whatsnew/3.11.rst:183 @@ -236,9 +236,9 @@ msgstr "" #: whatsnew/3.11.rst:185 msgid "" ":pep:`654` introduces language features that enable a program to raise and " -"handle multiple unrelated exceptions simultaneously. The builtin types :exc:" -"`ExceptionGroup` and :exc:`BaseExceptionGroup` make it possible to group " -"exceptions and raise them together, and the new :keyword:`except* " +"handle multiple unrelated exceptions simultaneously. The builtin " +"types :exc:`ExceptionGroup` and :exc:`BaseExceptionGroup` make it possible " +"to group exceptions and raise them together, and the new :keyword:`except* " "` syntax generalizes :keyword:`except` to match subgroups of " "exception groups." msgstr "" @@ -282,26 +282,26 @@ msgstr "" #: whatsnew/3.11.rst:219 msgid "" "The copy of the :ref:`launcher` included with Python 3.11 has been " -"significantly updated. It now supports company/tag syntax as defined in :pep:" -"`514` using the :samp:`-V:{}/{}` argument instead of the " -"limited :samp:`-{}.{}`. This allows launching distributions " -"other than ``PythonCore``, the one hosted on `python.org `_." +"significantly updated. It now supports company/tag syntax as defined " +"in :pep:`514` using the :samp:`-V:{}/{}` argument instead of " +"the limited :samp:`-{}.{}`. This allows launching " +"distributions other than ``PythonCore``, the one hosted on `python.org " +"`_." msgstr "" #: whatsnew/3.11.rst:225 msgid "" "When using ``-V:`` selectors, either company or tag can be omitted, but all " "installs will be searched. For example, ``-V:OtherPython/`` will select the " -"\"best\" tag registered for ``OtherPython``, while ``-V:3.11`` or ``-" -"V:/3.11`` will select the \"best\" distribution with tag ``3.11``." +"\"best\" tag registered for ``OtherPython``, while ``-V:3.11`` or ``-V:/" +"3.11`` will select the \"best\" distribution with tag ``3.11``." msgstr "" #: whatsnew/3.11.rst:230 msgid "" -"When using the legacy :samp:`-{}`, :samp:`-{}.{}`, :" -"samp:`-{}-{}` or :samp:`-{}.{}-{}` " -"arguments, all existing behaviour should be preserved from past versions, " +"When using the legacy :samp:`-{}`, :samp:`-{}.{}" +"`, :samp:`-{}-{}` or :samp:`-{}.{}-{}" +"` arguments, all existing behaviour should be preserved from past versions, " "and only releases from ``PythonCore`` will be selected. However, the ``-64`` " "suffix now implies \"not 32-bit\" (not necessarily x86-64), as there are " "multiple supported 64-bit platforms. 32-bit runtimes are detected by " @@ -315,8 +315,8 @@ msgstr "" #: whatsnew/3.11.rst:246 msgid "" -"This section covers major changes affecting :pep:`484` type hints and the :" -"mod:`typing` module." +"This section covers major changes affecting :pep:`484` type hints and " +"the :mod:`typing` module." msgstr "" #: whatsnew/3.11.rst:253 @@ -326,10 +326,10 @@ msgstr "" #: whatsnew/3.11.rst:255 msgid "" ":pep:`484` previously introduced :data:`~typing.TypeVar`, enabling creation " -"of generics parameterised with a single type. :pep:`646` adds :data:`~typing." -"TypeVarTuple`, enabling parameterisation with an *arbitrary* number of " -"types. In other words, a :data:`~typing.TypeVarTuple` is a *variadic* type " -"variable, enabling *variadic* generics." +"of generics parameterised with a single type. :pep:`646` " +"adds :data:`~typing.TypeVarTuple`, enabling parameterisation with an " +"*arbitrary* number of types. In other words, a :data:`~typing.TypeVarTuple` " +"is a *variadic* type variable, enabling *variadic* generics." msgstr "" #: whatsnew/3.11.rst:262 @@ -360,9 +360,9 @@ msgstr "" #: whatsnew/3.11.rst:280 msgid "" ":data:`~typing.Required` and :data:`~typing.NotRequired` provide a " -"straightforward way to mark whether individual items in a :class:`~typing." -"TypedDict` must be present. Previously, this was only possible using " -"inheritance." +"straightforward way to mark whether individual items in " +"a :class:`~typing.TypedDict` must be present. Previously, this was only " +"possible using inheritance." msgstr "" #: whatsnew/3.11.rst:285 @@ -420,9 +420,9 @@ msgstr "" #: whatsnew/3.11.rst:322 msgid "" -"Common use cases include alternative constructors provided as :func:" -"`classmethod `\\s, and :meth:`~object.__enter__` methods that " -"return ``self``::" +"Common use cases include alternative constructors provided " +"as :func:`classmethod `\\s, and :meth:`~object.__enter__` " +"methods that return ``self``::" msgstr "" #: whatsnew/3.11.rst:326 @@ -515,8 +515,8 @@ msgid "" ":data:`~typing.dataclass_transform` may be used to decorate a class, " "metaclass, or a function that is itself a decorator. The presence of " "``@dataclass_transform()`` tells a static type checker that the decorated " -"object performs runtime \"magic\" that transforms a class, giving it :func:" -"`dataclass `-like behaviors." +"object performs runtime \"magic\" that transforms a class, giving " +"it :func:`dataclass `-like behaviors." msgstr "" #: whatsnew/3.11.rst:397 @@ -586,39 +586,39 @@ msgstr "" #: whatsnew/3.11.rst:447 msgid "" -"A :exc:`TypeError` is now raised instead of an :exc:`AttributeError` in :" -"keyword:`with` statements and :meth:`contextlib.ExitStack.enter_context` for " -"objects that do not support the :term:`context manager` protocol, and in :" -"keyword:`async with` statements and :meth:`contextlib.AsyncExitStack." -"enter_async_context` for objects not supporting the :term:`asynchronous " -"context manager` protocol. (Contributed by Serhiy Storchaka in :issue:" -"`12022` and :issue:`44471`.)" +"A :exc:`TypeError` is now raised instead of an :exc:`AttributeError` " +"in :keyword:`with` statements and :meth:`contextlib.ExitStack.enter_context` " +"for objects that do not support the :term:`context manager` protocol, and " +"in :keyword:`async with` statements " +"and :meth:`contextlib.AsyncExitStack.enter_async_context` for objects not " +"supporting the :term:`asynchronous context manager` protocol. (Contributed " +"by Serhiy Storchaka in :issue:`12022` and :issue:`44471`.)" msgstr "" #: whatsnew/3.11.rst:455 msgid "" "Added :meth:`object.__getstate__`, which provides the default implementation " "of the :meth:`!__getstate__` method. :mod:`copy`\\ing and :mod:`pickle`\\ing " -"instances of subclasses of builtin types :class:`bytearray`, :class:`set`, :" -"class:`frozenset`, :class:`collections.OrderedDict`, :class:`collections." -"deque`, :class:`weakref.WeakSet`, and :class:`datetime.tzinfo` now copies " -"and pickles instance attributes implemented as :term:`slots <__slots__>`. " -"This change has an unintended side effect: It trips up a small minority of " -"existing Python projects not expecting :meth:`object.__getstate__` to exist. " -"See the later comments on :gh:`70766` for discussions of what workarounds " -"such code may need. (Contributed by Serhiy Storchaka in :issue:`26579`.)" +"instances of subclasses of builtin " +"types :class:`bytearray`, :class:`set`, :class:`frozenset`, :class:`collections.OrderedDict`, :class:`collections.deque`, :class:`weakref.WeakSet`, " +"and :class:`datetime.tzinfo` now copies and pickles instance attributes " +"implemented as :term:`slots <__slots__>`. This change has an unintended side " +"effect: It trips up a small minority of existing Python projects not " +"expecting :meth:`object.__getstate__` to exist. See the later comments " +"on :gh:`70766` for discussions of what workarounds such code may need. " +"(Contributed by Serhiy Storchaka in :issue:`26579`.)" msgstr "" #: whatsnew/3.11.rst:470 msgid "" "Added a :option:`-P` command line option and a :envvar:`PYTHONSAFEPATH` " -"environment variable, which disable the automatic prepending to :data:`sys." -"path` of the script's directory when running a script, or the current " -"directory when using :option:`-c` and :option:`-m`. This ensures only stdlib " -"and installed modules are picked up by :keyword:`import`, and avoids " -"unintentionally or maliciously shadowing modules with those in a local (and " -"typically user-writable) directory. (Contributed by Victor Stinner in :gh:" -"`57684`.)" +"environment variable, which disable the automatic prepending " +"to :data:`sys.path` of the script's directory when running a script, or the " +"current directory when using :option:`-c` and :option:`-m`. This ensures " +"only stdlib and installed modules are picked up by :keyword:`import`, and " +"avoids unintentionally or maliciously shadowing modules with those in a " +"local (and typically user-writable) directory. (Contributed by Victor " +"Stinner in :gh:`57684`.)" msgstr "" #: whatsnew/3.11.rst:481 @@ -644,10 +644,10 @@ msgstr "" #: whatsnew/3.11.rst:499 msgid "" -"The special methods :meth:`~object.__complex__` for :class:`complex` and :" -"meth:`~object.__bytes__` for :class:`bytes` are implemented to support the :" -"class:`typing.SupportsComplex` and :class:`typing.SupportsBytes` protocols. " -"(Contributed by Mark Dickinson and Donghee Na in :issue:`24234`.)" +"The special methods :meth:`~object.__complex__` for :class:`complex` " +"and :meth:`~object.__bytes__` for :class:`bytes` are implemented to support " +"the :class:`typing.SupportsComplex` and :class:`typing.SupportsBytes` " +"protocols. (Contributed by Mark Dickinson and Donghee Na in :issue:`24234`.)" msgstr "" #: whatsnew/3.11.rst:504 @@ -663,10 +663,10 @@ msgstr "" #: whatsnew/3.11.rst:513 msgid "" "When an active exception is re-raised by a :keyword:`raise` statement with " -"no parameters, the traceback attached to this exception is now always ``sys." -"exc_info()[1].__traceback__``. This means that changes made to the traceback " -"in the current :keyword:`except` clause are reflected in the re-raised " -"exception. (Contributed by Irit Katriel in :issue:`45711`.)" +"no parameters, the traceback attached to this exception is now always " +"``sys.exc_info()[1].__traceback__``. This means that changes made to the " +"traceback in the current :keyword:`except` clause are reflected in the re-" +"raised exception. (Contributed by Irit Katriel in :issue:`45711`.)" msgstr "" #: whatsnew/3.11.rst:519 @@ -743,17 +743,17 @@ msgstr "" msgid "" "Added the :class:`~asyncio.TaskGroup` class, an :ref:`asynchronous context " "manager ` holding a group of tasks that will wait " -"for all of them upon exit. For new code this is recommended over using :func:" -"`~asyncio.create_task` and :func:`~asyncio.gather` directly. (Contributed by " -"Yury Selivanov and others in :gh:`90908`.)" +"for all of them upon exit. For new code this is recommended over " +"using :func:`~asyncio.create_task` and :func:`~asyncio.gather` directly. " +"(Contributed by Yury Selivanov and others in :gh:`90908`.)" msgstr "" #: whatsnew/3.11.rst:585 msgid "" "Added :func:`~asyncio.timeout`, an asynchronous context manager for setting " "a timeout on asynchronous operations. For new code this is recommended over " -"using :func:`~asyncio.wait_for` directly. (Contributed by Andrew Svetlov in :" -"gh:`90927`.)" +"using :func:`~asyncio.wait_for` directly. (Contributed by Andrew Svetlov " +"in :gh:`90927`.)" msgstr "" #: whatsnew/3.11.rst:590 @@ -771,25 +771,26 @@ msgstr "" #: whatsnew/3.11.rst:599 msgid "" -"Added keyword argument *all_errors* to :meth:`asyncio.loop." -"create_connection` so that multiple connection errors can be raised as an :" -"exc:`ExceptionGroup`." +"Added keyword argument *all_errors* " +"to :meth:`asyncio.loop.create_connection` so that multiple connection errors " +"can be raised as an :exc:`ExceptionGroup`." msgstr "" #: whatsnew/3.11.rst:602 msgid "" "Added the :meth:`asyncio.StreamWriter.start_tls` method for upgrading " -"existing stream-based connections to TLS. (Contributed by Ian Good in :issue:" -"`34975`.)" +"existing stream-based connections to TLS. (Contributed by Ian Good " +"in :issue:`34975`.)" msgstr "" #: whatsnew/3.11.rst:606 msgid "" -"Added raw datagram socket functions to the event loop: :meth:`~asyncio.loop." -"sock_sendto`, :meth:`~asyncio.loop.sock_recvfrom` and :meth:`~asyncio.loop." -"sock_recvfrom_into`. These have implementations in :class:`~asyncio." -"SelectorEventLoop` and :class:`~asyncio.ProactorEventLoop`. (Contributed by " -"Alex Grönholm in :issue:`46805`.)" +"Added raw datagram socket functions to the event " +"loop: :meth:`~asyncio.loop.sock_sendto`, :meth:`~asyncio.loop.sock_recvfrom` " +"and :meth:`~asyncio.loop.sock_recvfrom_into`. These have implementations " +"in :class:`~asyncio.SelectorEventLoop` " +"and :class:`~asyncio.ProactorEventLoop`. (Contributed by Alex Grönholm " +"in :issue:`46805`.)" msgstr "" #: whatsnew/3.11.rst:614 @@ -816,10 +817,10 @@ msgstr "" #: whatsnew/3.11.rst:635 msgid "" -"Change field default mutability check, allowing only defaults which are :" -"term:`hashable` instead of any object which is not an instance of :class:" -"`dict`, :class:`list` or :class:`set`. (Contributed by Eric V. Smith in :" -"issue:`44674`.)" +"Change field default mutability check, allowing only defaults which " +"are :term:`hashable` instead of any object which is not an instance " +"of :class:`dict`, :class:`list` or :class:`set`. (Contributed by Eric V. " +"Smith in :issue:`44674`.)" msgstr "" #: whatsnew/3.11.rst:644 @@ -828,8 +829,9 @@ msgstr "" #: whatsnew/3.11.rst:646 msgid "" -"Add :const:`datetime.UTC`, a convenience alias for :attr:`datetime.timezone." -"utc`. (Contributed by Kabir Kwatra in :gh:`91973`.)" +"Add :const:`datetime.UTC`, a convenience alias " +"for :attr:`datetime.timezone.utc`. (Contributed by Kabir Kwatra " +"in :gh:`91973`.)" msgstr "" #: whatsnew/3.11.rst:649 @@ -858,33 +860,34 @@ msgstr "" #: whatsnew/3.11.rst:666 msgid "" -"Added :class:`~enum.ReprEnum`, which only modifies the :meth:`~object." -"__repr__` of members while returning their literal values (rather than " -"names) for :meth:`~object.__str__` and :meth:`~object.__format__` (used by :" -"func:`str`, :func:`format` and :term:`f-string`\\s)." +"Added :class:`~enum.ReprEnum`, which only modifies " +"the :meth:`~object.__repr__` of members while returning their literal values " +"(rather than names) for :meth:`~object.__str__` " +"and :meth:`~object.__format__` (used by :func:`str`, :func:`format` " +"and :term:`f-string`\\s)." msgstr "" #: whatsnew/3.11.rst:672 msgid "" -"Changed :meth:`Enum.__format__() ` (the default for :" -"func:`format`, :meth:`str.format` and :term:`f-string`\\s) to always produce " -"the same result as :meth:`Enum.__str__() `: for enums " -"inheriting from :class:`~enum.ReprEnum` it will be the member's value; for " -"all other enums it will be the enum and member name (e.g. ``Color.RED``)." +"Changed :meth:`Enum.__format__() ` (the default " +"for :func:`format`, :meth:`str.format` and :term:`f-string`\\s) to always " +"produce the same result as :meth:`Enum.__str__() `: for " +"enums inheriting from :class:`~enum.ReprEnum` it will be the member's value; " +"for all other enums it will be the enum and member name (e.g. ``Color.RED``)." msgstr "" #: whatsnew/3.11.rst:678 msgid "" -"Added a new *boundary* class parameter to :class:`~enum.Flag` enums and the :" -"class:`~enum.FlagBoundary` enum with its options, to control how to handle " -"out-of-range flag values." +"Added a new *boundary* class parameter to :class:`~enum.Flag` enums and " +"the :class:`~enum.FlagBoundary` enum with its options, to control how to " +"handle out-of-range flag values." msgstr "" #: whatsnew/3.11.rst:682 msgid "" -"Added the :func:`~enum.verify` enum decorator and the :class:`~enum." -"EnumCheck` enum with its options, to check enum classes against several " -"specific constraints." +"Added the :func:`~enum.verify` enum decorator and " +"the :class:`~enum.EnumCheck` enum with its options, to check enum classes " +"against several specific constraints." msgstr "" #: whatsnew/3.11.rst:686 @@ -895,25 +898,26 @@ msgstr "" #: whatsnew/3.11.rst:689 msgid "" -"Added the :func:`~enum.property` decorator, which works like :func:" -"`property` except for enums. Use this instead of :func:`types." -"DynamicClassAttribute`." +"Added the :func:`~enum.property` decorator, which works " +"like :func:`property` except for enums. Use this instead " +"of :func:`types.DynamicClassAttribute`." msgstr "" #: whatsnew/3.11.rst:693 msgid "" -"Added the :func:`~enum.global_enum` enum decorator, which adjusts :meth:" -"`~object.__repr__` and :meth:`~object.__str__` to show values as members of " -"their module rather than the enum class. For example, ``'re.ASCII'`` for " -"the :const:`~re.ASCII` member of :class:`re.RegexFlag` rather than " -"``'RegexFlag.ASCII'``." +"Added the :func:`~enum.global_enum` enum decorator, which " +"adjusts :meth:`~object.__repr__` and :meth:`~object.__str__` to show values " +"as members of their module rather than the enum class. For example, " +"``'re.ASCII'`` for the :const:`~re.ASCII` member of :class:`re.RegexFlag` " +"rather than ``'RegexFlag.ASCII'``." msgstr "" #: whatsnew/3.11.rst:699 msgid "" -"Enhanced :class:`~enum.Flag` to support :func:`len`, iteration and :keyword:" -"`in`/:keyword:`not in` on its members. For example, the following now works: " -"``len(AFlag(3)) == 2 and list(AFlag(3)) == (AFlag.ONE, AFlag.TWO)``" +"Enhanced :class:`~enum.Flag` to support :func:`len`, iteration " +"and :keyword:`in`/:keyword:`not in` on its members. For example, the " +"following now works: ``len(AFlag(3)) == 2 and list(AFlag(3)) == (AFlag.ONE, " +"AFlag.TWO)``" msgstr "" #: whatsnew/3.11.rst:704 @@ -964,8 +968,8 @@ msgstr "" #: whatsnew/3.11.rst:743 msgid "" -":func:`functools.singledispatch` now supports :data:`types.UnionType` and :" -"data:`typing.Union` as annotations to the dispatch argument.::" +":func:`functools.singledispatch` now supports :data:`types.UnionType` " +"and :data:`typing.Union` as annotations to the dispatch argument.::" msgstr "" #: whatsnew/3.11.rst:746 @@ -1004,13 +1008,14 @@ msgstr "" #: whatsnew/3.11.rst:776 msgid "" "The :func:`gzip.compress` function is now faster when used with the " -"**mtime=0** argument as it delegates the compression entirely to a single :" -"func:`zlib.compress` operation. There is one side effect of this change: The " -"gzip file header contains an \"OS\" byte in its header. That was " -"traditionally always set to a value of 255 representing \"unknown\" by the :" -"mod:`gzip` module. Now, when using :func:`~gzip.compress` with **mtime=0**, " -"it may be set to a different value by the underlying zlib C library Python " -"was linked against. (See :gh:`112346` for details on the side effect.)" +"**mtime=0** argument as it delegates the compression entirely to a " +"single :func:`zlib.compress` operation. There is one side effect of this " +"change: The gzip file header contains an \"OS\" byte in its header. That was " +"traditionally always set to a value of 255 representing \"unknown\" by " +"the :mod:`gzip` module. Now, when using :func:`~gzip.compress` with " +"**mtime=0**, it may be set to a different value by the underlying zlib C " +"library Python was linked against. (See :gh:`112346` for details on the side " +"effect.)" msgstr "" #: whatsnew/3.11.rst:789 @@ -1068,8 +1073,8 @@ msgstr "" #: whatsnew/3.11.rst:828 msgid "" "Add :func:`~inspect.ismethodwrapper` for checking if the type of an object " -"is a :class:`~types.MethodWrapperType`. (Contributed by Hakan Çelik in :" -"issue:`29418`.)" +"is a :class:`~types.MethodWrapperType`. (Contributed by Hakan Çelik " +"in :issue:`29418`.)" msgstr "" #: whatsnew/3.11.rst:832 @@ -1112,8 +1117,8 @@ msgstr "" #: whatsnew/3.11.rst:852 msgid "" "Add :func:`locale.getencoding` to get the current locale encoding. It is " -"similar to ``locale.getpreferredencoding(False)`` but ignores the :ref:" -"`Python UTF-8 Mode `." +"similar to ``locale.getpreferredencoding(False)`` but ignores " +"the :ref:`Python UTF-8 Mode `." msgstr "" #: whatsnew/3.11.rst:860 @@ -1123,18 +1128,19 @@ msgstr "" #: whatsnew/3.11.rst:862 msgid "" "Added :func:`~logging.getLevelNamesMapping` to return a mapping from logging " -"level names (e.g. ``'CRITICAL'``) to the values of their corresponding :ref:" -"`levels` (e.g. ``50``, by default). (Contributed by Andrei Kulakovin in :gh:" -"`88024`.)" +"level names (e.g. ``'CRITICAL'``) to the values of their " +"corresponding :ref:`levels` (e.g. ``50``, by default). (Contributed by " +"Andrei Kulakovin in :gh:`88024`.)" msgstr "" #: whatsnew/3.11.rst:867 msgid "" -"Added a :meth:`~logging.handlers.SysLogHandler.createSocket` method to :" -"class:`~logging.handlers.SysLogHandler`, to match :meth:`SocketHandler." -"createSocket() `. It is called " -"automatically during handler initialization and when emitting an event, if " -"there is no active socket. (Contributed by Kirill Pinchuk in :gh:`88457`.)" +"Added a :meth:`~logging.handlers.SysLogHandler.createSocket` method " +"to :class:`~logging.handlers.SysLogHandler`, to " +"match :meth:`SocketHandler.createSocket() " +"`. It is called automatically " +"during handler initialization and when emitting an event, if there is no " +"active socket. (Contributed by Kirill Pinchuk in :gh:`88457`.)" msgstr "" #: whatsnew/3.11.rst:879 @@ -1156,10 +1162,10 @@ msgstr "" #: whatsnew/3.11.rst:887 msgid "" "The behaviour of two :func:`math.pow` corner cases was changed, for " -"consistency with the IEEE 754 specification. The operations ``math.pow(0.0, -" -"math.inf)`` and ``math.pow(-0.0, -math.inf)`` now return ``inf``. Previously " -"they raised :exc:`ValueError`. (Contributed by Mark Dickinson in :issue:" -"`44339`.)" +"consistency with the IEEE 754 specification. The operations ``math.pow(0.0, " +"-math.inf)`` and ``math.pow(-0.0, -math.inf)`` now return ``inf``. " +"Previously they raised :exc:`ValueError`. (Contributed by Mark Dickinson " +"in :issue:`44339`.)" msgstr "" #: whatsnew/3.11.rst:893 @@ -1174,9 +1180,9 @@ msgstr "" #: whatsnew/3.11.rst:902 msgid "" -"A new function ``operator.call`` has been added, such that ``operator." -"call(obj, *args, **kwargs) == obj(*args, **kwargs)``. (Contributed by Antony " -"Lee in :issue:`44019`.)" +"A new function ``operator.call`` has been added, such that " +"``operator.call(obj, *args, **kwargs) == obj(*args, **kwargs)``. " +"(Contributed by Antony Lee in :issue:`44019`.)" msgstr "" #: whatsnew/3.11.rst:910 @@ -1186,8 +1192,8 @@ msgstr "" #: whatsnew/3.11.rst:912 msgid "" "On Windows, :func:`os.urandom` now uses ``BCryptGenRandom()``, instead of " -"``CryptGenRandom()`` which is deprecated. (Contributed by Donghee Na in :" -"issue:`44611`.)" +"``CryptGenRandom()`` which is deprecated. (Contributed by Donghee Na " +"in :issue:`44611`.)" msgstr "" #: whatsnew/3.11.rst:920 @@ -1197,9 +1203,9 @@ msgstr "" #: whatsnew/3.11.rst:922 msgid "" ":meth:`~pathlib.Path.glob` and :meth:`~pathlib.Path.rglob` return only " -"directories if *pattern* ends with a pathname components separator: :data:" -"`~os.sep` or :data:`~os.altsep`. (Contributed by Eisuke Kawasima in :issue:" -"`22276` and :issue:`33392`.)" +"directories if *pattern* ends with a pathname components " +"separator: :data:`~os.sep` or :data:`~os.altsep`. (Contributed by Eisuke " +"Kawasima in :issue:`22276` and :issue:`33392`.)" msgstr "" #: whatsnew/3.11.rst:931 @@ -1229,8 +1235,8 @@ msgstr "" #: whatsnew/3.11.rst:952 msgid "" -"Add CAN Socket support for NetBSD. (Contributed by Thomas Klausner in :issue:" -"`30512`.)" +"Add CAN Socket support for NetBSD. (Contributed by Thomas Klausner " +"in :issue:`30512`.)" msgstr "" #: whatsnew/3.11.rst:955 @@ -1246,33 +1252,33 @@ msgstr "" #: whatsnew/3.11.rst:966 msgid "" -"You can now disable the authorizer by passing :const:`None` to :meth:" -"`~sqlite3.Connection.set_authorizer`. (Contributed by Erlend E. Aasland in :" -"issue:`44491`.)" +"You can now disable the authorizer by passing :const:`None` " +"to :meth:`~sqlite3.Connection.set_authorizer`. (Contributed by Erlend E. " +"Aasland in :issue:`44491`.)" msgstr "" #: whatsnew/3.11.rst:970 msgid "" "Collation name :meth:`~sqlite3.Connection.create_collation` can now contain " -"any Unicode character. Collation names with invalid characters now raise :" -"exc:`UnicodeEncodeError` instead of :exc:`sqlite3.ProgrammingError`. " +"any Unicode character. Collation names with invalid characters now " +"raise :exc:`UnicodeEncodeError` instead of :exc:`sqlite3.ProgrammingError`. " "(Contributed by Erlend E. Aasland in :issue:`44688`.)" msgstr "" #: whatsnew/3.11.rst:975 msgid "" -":mod:`sqlite3` exceptions now include the SQLite extended error code as :" -"attr:`~sqlite3.Error.sqlite_errorcode` and the SQLite error name as :attr:" -"`~sqlite3.Error.sqlite_errorname`. (Contributed by Aviv Palivoda, Daniel " -"Shahaf, and Erlend E. Aasland in :issue:`16379` and :issue:`24139`.)" +":mod:`sqlite3` exceptions now include the SQLite extended error code " +"as :attr:`~sqlite3.Error.sqlite_errorcode` and the SQLite error name " +"as :attr:`~sqlite3.Error.sqlite_errorname`. (Contributed by Aviv Palivoda, " +"Daniel Shahaf, and Erlend E. Aasland in :issue:`16379` and :issue:`24139`.)" msgstr "" #: whatsnew/3.11.rst:981 msgid "" -"Add :meth:`~sqlite3.Connection.setlimit` and :meth:`~sqlite3.Connection." -"getlimit` to :class:`sqlite3.Connection` for setting and getting SQLite " -"limits by connection basis. (Contributed by Erlend E. Aasland in :issue:" -"`45243`.)" +"Add :meth:`~sqlite3.Connection.setlimit` " +"and :meth:`~sqlite3.Connection.getlimit` to :class:`sqlite3.Connection` for " +"setting and getting SQLite limits by connection basis. (Contributed by " +"Erlend E. Aasland in :issue:`45243`.)" msgstr "" #: whatsnew/3.11.rst:986 @@ -1299,24 +1305,25 @@ msgstr "" #: whatsnew/3.11.rst:1000 msgid "" -"Add :meth:`~sqlite3.Connection.serialize` and :meth:`~sqlite3.Connection." -"deserialize` to :class:`sqlite3.Connection` for serializing and " -"deserializing databases. (Contributed by Erlend E. Aasland in :issue:" -"`41930`.)" +"Add :meth:`~sqlite3.Connection.serialize` " +"and :meth:`~sqlite3.Connection.deserialize` to :class:`sqlite3.Connection` " +"for serializing and deserializing databases. (Contributed by Erlend E. " +"Aasland in :issue:`41930`.)" msgstr "" #: whatsnew/3.11.rst:1005 msgid "" -"Add :meth:`~sqlite3.Connection.create_window_function` to :class:`sqlite3." -"Connection` for creating aggregate window functions. (Contributed by Erlend " -"E. Aasland in :issue:`34916`.)" +"Add :meth:`~sqlite3.Connection.create_window_function` " +"to :class:`sqlite3.Connection` for creating aggregate window functions. " +"(Contributed by Erlend E. Aasland in :issue:`34916`.)" msgstr "" #: whatsnew/3.11.rst:1009 msgid "" -"Add :meth:`~sqlite3.Connection.blobopen` to :class:`sqlite3.Connection`. :" -"class:`sqlite3.Blob` allows incremental I/O operations on blobs. " -"(Contributed by Aviv Palivoda and Erlend E. Aasland in :issue:`24905`.)" +"Add :meth:`~sqlite3.Connection.blobopen` " +"to :class:`sqlite3.Connection`. :class:`sqlite3.Blob` allows incremental I/O " +"operations on blobs. (Contributed by Aviv Palivoda and Erlend E. Aasland " +"in :issue:`24905`.)" msgstr "" #: whatsnew/3.11.rst:1017 @@ -1325,10 +1332,10 @@ msgstr "" #: whatsnew/3.11.rst:1019 msgid "" -"Add :meth:`~string.Template.get_identifiers` and :meth:`~string.Template." -"is_valid` to :class:`string.Template`, which respectively return all valid " -"placeholders, and whether any invalid placeholders are present. (Contributed " -"by Ben Kehoe in :gh:`90465`.)" +"Add :meth:`~string.Template.get_identifiers` " +"and :meth:`~string.Template.is_valid` to :class:`string.Template`, which " +"respectively return all valid placeholders, and whether any invalid " +"placeholders are present. (Contributed by Ben Kehoe in :gh:`90465`.)" msgstr "" #: whatsnew/3.11.rst:1029 @@ -1340,15 +1347,15 @@ msgid "" ":func:`sys.exc_info` now derives the ``type`` and ``traceback`` fields from " "the ``value`` (the exception instance), so when an exception is modified " "while it is being handled, the changes are reflected in the results of " -"subsequent calls to :func:`!exc_info`. (Contributed by Irit Katriel in :" -"issue:`45711`.)" +"subsequent calls to :func:`!exc_info`. (Contributed by Irit Katriel " +"in :issue:`45711`.)" msgstr "" #: whatsnew/3.11.rst:1037 msgid "" "Add :func:`sys.exception` which returns the active exception instance " -"(equivalent to ``sys.exc_info()[1]``). (Contributed by Irit Katriel in :" -"issue:`46328`.)" +"(equivalent to ``sys.exc_info()[1]``). (Contributed by Irit Katriel " +"in :issue:`46328`.)" msgstr "" #: whatsnew/3.11.rst:1041 @@ -1384,8 +1391,8 @@ msgid "" ":class:`~tempfile.SpooledTemporaryFile` objects now fully implement the " "methods of :class:`io.BufferedIOBase` or :class:`io.TextIOBase` (depending " "on file mode). This lets them work correctly with APIs that expect file-like " -"objects, such as compression modules. (Contributed by Carey Metcalfe in :gh:" -"`70363`.)" +"objects, such as compression modules. (Contributed by Carey Metcalfe " +"in :gh:`70363`.)" msgstr "" #: whatsnew/3.11.rst:1080 @@ -1398,8 +1405,8 @@ msgid "" "(glibc 2.30 and newer), the :meth:`threading.Lock.acquire` method now uses " "the monotonic clock (:const:`time.CLOCK_MONOTONIC`) for the timeout, rather " "than using the system clock (:const:`time.CLOCK_REALTIME`), to not be " -"affected by system clock changes. (Contributed by Victor Stinner in :issue:" -"`41710`.)" +"affected by system clock changes. (Contributed by Victor Stinner " +"in :issue:`41710`.)" msgstr "" #: whatsnew/3.11.rst:1093 @@ -1422,8 +1429,8 @@ msgid "" "hardware/drivers/kernel/high-resolution-timers>`_ which has a resolution of " "100 nanoseconds (10\\ :sup:`-7` seconds). Previously, it had a resolution of " "1 millisecond (10\\ :sup:`-3` seconds). (Contributed by Benjamin Szőke, " -"Donghee Na, Eryk Sun and Victor Stinner in :issue:`21302` and :issue:" -"`45429`.)" +"Donghee Na, Eryk Sun and Victor Stinner in :issue:`21302` " +"and :issue:`45429`.)" msgstr "" #: whatsnew/3.11.rst:1112 @@ -1450,9 +1457,9 @@ msgstr "" #: whatsnew/3.11.rst:1129 msgid "" -"Add :func:`traceback.TracebackException.print`, which prints the formatted :" -"exc:`~traceback.TracebackException` instance to a file. (Contributed by Irit " -"Katriel in :issue:`33809`.)" +"Add :func:`traceback.TracebackException.print`, which prints the " +"formatted :exc:`~traceback.TracebackException` instance to a file. " +"(Contributed by Irit Katriel in :issue:`33809`.)" msgstr "" #: whatsnew/3.11.rst:1137 @@ -1465,10 +1472,11 @@ msgstr "" #: whatsnew/3.11.rst:1141 msgid "" -"Add :func:`typing.assert_never` and :class:`typing.Never`. :func:`typing." -"assert_never` is useful for asking a type checker to confirm that a line of " -"code is not reachable. At runtime, it raises an :exc:`AssertionError`. " -"(Contributed by Jelle Zijlstra in :gh:`90633`.)" +"Add :func:`typing.assert_never` " +"and :class:`typing.Never`. :func:`typing.assert_never` is useful for asking " +"a type checker to confirm that a line of code is not reachable. At runtime, " +"it raises an :exc:`AssertionError`. (Contributed by Jelle Zijlstra " +"in :gh:`90633`.)" msgstr "" #: whatsnew/3.11.rst:1147 @@ -1515,8 +1523,8 @@ msgstr "" msgid "" "The :func:`typing.get_overloads` function can be used for introspecting the " "overloads of a function. :func:`typing.clear_overloads` can be used to clear " -"all registered overloads of a function. (Contributed by Jelle Zijlstra in :" -"gh:`89263`.)" +"all registered overloads of a function. (Contributed by Jelle Zijlstra " +"in :gh:`89263`.)" msgstr "" #: whatsnew/3.11.rst:1176 @@ -1549,15 +1557,15 @@ msgstr "" #: whatsnew/3.11.rst:1192 msgid "" ":func:`typing.get_type_hints` no longer adds :data:`~typing.Optional` to " -"parameters with ``None`` as a default. (Contributed by Nikita Sobolev in :gh:" -"`90353`.)" +"parameters with ``None`` as a default. (Contributed by Nikita Sobolev " +"in :gh:`90353`.)" msgstr "" #: whatsnew/3.11.rst:1196 msgid "" -":func:`typing.get_type_hints` now supports evaluating bare stringified :data:" -"`~typing.ClassVar` annotations. (Contributed by Gregory Beauregard in :gh:" -"`90711`.)" +":func:`typing.get_type_hints` now supports evaluating bare " +"stringified :data:`~typing.ClassVar` annotations. (Contributed by Gregory " +"Beauregard in :gh:`90711`.)" msgstr "" #: whatsnew/3.11.rst:1200 @@ -1583,11 +1591,13 @@ msgstr "" #: whatsnew/3.11.rst:1219 msgid "" -"Added methods :meth:`~unittest.TestCase.enterContext` and :meth:`~unittest." -"TestCase.enterClassContext` of class :class:`~unittest.TestCase`, method :" -"meth:`~unittest.IsolatedAsyncioTestCase.enterAsyncContext` of class :class:" -"`~unittest.IsolatedAsyncioTestCase` and function :func:`unittest." -"enterModuleContext`. (Contributed by Serhiy Storchaka in :issue:`45046`.)" +"Added methods :meth:`~unittest.TestCase.enterContext` " +"and :meth:`~unittest.TestCase.enterClassContext` of " +"class :class:`~unittest.TestCase`, " +"method :meth:`~unittest.IsolatedAsyncioTestCase.enterAsyncContext` of " +"class :class:`~unittest.IsolatedAsyncioTestCase` and " +"function :func:`unittest.enterModuleContext`. (Contributed by Serhiy " +"Storchaka in :issue:`45046`.)" msgstr "" #: whatsnew/3.11.rst:1231 @@ -1602,8 +1612,8 @@ msgid "" "installation scheme is the default. That means that downstream distributors " "can change the default sysconfig install scheme without changing behavior of " "virtual environments. Third party code that also creates new virtual " -"environments should do the same. (Contributed by Miro Hrončok in :issue:" -"`45413`.)" +"environments should do the same. (Contributed by Miro Hrončok " +"in :issue:`45413`.)" msgstr "" #: whatsnew/3.11.rst:1247 @@ -1612,10 +1622,10 @@ msgstr "" #: whatsnew/3.11.rst:1249 msgid "" -":func:`warnings.catch_warnings` now accepts arguments for :func:`warnings." -"simplefilter`, providing a more concise way to locally ignore warnings or " -"convert them to errors. (Contributed by Zac Hatfield-Dodds in :issue:" -"`47074`.)" +":func:`warnings.catch_warnings` now accepts arguments " +"for :func:`warnings.simplefilter`, providing a more concise way to locally " +"ignore warnings or convert them to errors. (Contributed by Zac Hatfield-" +"Dodds in :issue:`47074`.)" msgstr "" #: whatsnew/3.11.rst:1257 @@ -1624,8 +1634,8 @@ msgstr "" #: whatsnew/3.11.rst:1259 msgid "" -"Added support for specifying member name encoding for reading metadata in a :" -"class:`~zipfile.ZipFile`'s directory and file headers. (Contributed by " +"Added support for specifying member name encoding for reading metadata in " +"a :class:`~zipfile.ZipFile`'s directory and file headers. (Contributed by " "Stephen J. Turnbull and Serhiy Storchaka in :issue:`28080`.)" msgstr "" @@ -1637,9 +1647,9 @@ msgstr "" #: whatsnew/3.11.rst:1267 msgid "" -"Added :attr:`~zipfile.Path.stem`, :attr:`~zipfile.Path.suffix` and :attr:" -"`~zipfile.Path.suffixes` to :class:`zipfile.Path`. (Contributed by Miguel " -"Brito in :gh:`88261`.)" +"Added :attr:`~zipfile.Path.stem`, :attr:`~zipfile.Path.suffix` " +"and :attr:`~zipfile.Path.suffixes` to :class:`zipfile.Path`. (Contributed by " +"Miguel Brito in :gh:`88261`.)" msgstr "" #: whatsnew/3.11.rst:1275 @@ -1648,8 +1658,9 @@ msgstr "" #: whatsnew/3.11.rst:1277 msgid "" -"This section covers specific optimizations independent of the :ref:" -"`whatsnew311-faster-cpython` project, which is covered in its own section." +"This section covers specific optimizations independent of " +"the :ref:`whatsnew311-faster-cpython` project, which is covered in its own " +"section." msgstr "" #: whatsnew/3.11.rst:1280 @@ -1664,8 +1675,8 @@ msgstr "" msgid "" "Integer division (``//``) is better tuned for optimization by compilers. It " "is now around 20% faster on x86-64 when dividing an :class:`int` by a value " -"smaller than ``2**30``. (Contributed by Gregory P. Smith and Tim Peters in :" -"gh:`90564`.)" +"smaller than ``2**30``. (Contributed by Gregory P. Smith and Tim Peters " +"in :gh:`90564`.)" msgstr "" #: whatsnew/3.11.rst:1291 @@ -1676,17 +1687,18 @@ msgstr "" #: whatsnew/3.11.rst:1294 msgid "" -"Resizing lists is streamlined for the common case, speeding up :meth:`list." -"append` by ≈15% and simple :term:`list comprehension`\\s by up to 20-30% " -"(Contributed by Dennis Sweeney in :gh:`91165`.)" +"Resizing lists is streamlined for the common case, speeding " +"up :meth:`list.append` by ≈15% and simple :term:`list comprehension`\\s by " +"up to 20-30% (Contributed by Dennis Sweeney in :gh:`91165`.)" msgstr "" #: whatsnew/3.11.rst:1299 msgid "" "Dictionaries don't store hash values when all keys are Unicode objects, " -"decreasing :class:`dict` size. For example, ``sys.getsizeof(dict." -"fromkeys(\"abcdefg\"))`` is reduced from 352 bytes to 272 bytes (23% " -"smaller) on 64-bit platforms. (Contributed by Inada Naoki in :issue:`46845`.)" +"decreasing :class:`dict` size. For example, " +"``sys.getsizeof(dict.fromkeys(\"abcdefg\"))`` is reduced from 352 bytes to " +"272 bytes (23% smaller) on 64-bit platforms. (Contributed by Inada Naoki " +"in :issue:`46845`.)" msgstr "" #: whatsnew/3.11.rst:1305 @@ -1705,11 +1717,11 @@ msgstr "" #: whatsnew/3.11.rst:1314 msgid "" -"The :mod:`statistics` functions :func:`~statistics.mean`, :func:`~statistics." -"variance` and :func:`~statistics.stdev` now consume iterators in one pass " -"rather than converting them to a :class:`list` first. This is twice as fast " -"and can save substantial memory. (Contributed by Raymond Hettinger in :gh:" -"`90415`.)" +"The :mod:`statistics` " +"functions :func:`~statistics.mean`, :func:`~statistics.variance` " +"and :func:`~statistics.stdev` now consume iterators in one pass rather than " +"converting them to a :class:`list` first. This is twice as fast and can save " +"substantial memory. (Contributed by Raymond Hettinger in :gh:`90415`.)" msgstr "" #: whatsnew/3.11.rst:1320 @@ -1815,10 +1827,10 @@ msgstr "" #: whatsnew/3.11.rst:1396 msgid "" "Old-style :ref:`frame objects ` are now created only when " -"requested by debuggers or by Python introspection functions such as :func:" -"`sys._getframe` and :func:`inspect.currentframe`. For most user code, no " -"frame objects are created at all. As a result, nearly all Python functions " -"calls have sped up significantly. We measured a 3-7% speedup in " +"requested by debuggers or by Python introspection functions such " +"as :func:`sys._getframe` and :func:`inspect.currentframe`. For most user " +"code, no frame objects are created at all. As a result, nearly all Python " +"functions calls have sped up significantly. We measured a 3-7% speedup in " "pyperformance." msgstr "" @@ -1849,8 +1861,9 @@ msgid "" "Most Python function calls now consume no C stack space, speeding them up. " "In simple recursive functions like fibonacci or factorial, we observed a " "1.7x speedup. This also means recursive functions can recurse significantly " -"deeper (if the user increases the recursion limit with :func:`sys." -"setrecursionlimit`). We measured a 1-3% improvement in pyperformance." +"deeper (if the user increases the recursion limit " +"with :func:`sys.setrecursionlimit`). We measured a 1-3% improvement in " +"pyperformance." msgstr "" #: whatsnew/3.11.rst:1427 @@ -1876,8 +1889,8 @@ msgid "" "more specialized one. This specialized operation uses fast paths available " "only to those use cases/types, which generally outperform their generic " "counterparts. This also brings in another concept called *inline caching*, " -"where Python caches the results of expensive operations directly in the :" -"term:`bytecode`." +"where Python caches the results of expensive operations directly in " +"the :term:`bytecode`." msgstr "" #: whatsnew/3.11.rst:1447 @@ -1898,9 +1911,9 @@ msgstr "" #: whatsnew/3.11.rst:1457 msgid "" -"(PEP written by Mark Shannon, with ideas inspired by Stefan Brunthaler. See :" -"pep:`659` for more information. Implementation by Mark Shannon and Brandt " -"Bucher, with additional help from Irit Katriel and Dennis Sweeney.)" +"(PEP written by Mark Shannon, with ideas inspired by Stefan Brunthaler. " +"See :pep:`659` for more information. Implementation by Mark Shannon and " +"Brandt Bucher, with additional help from Irit Katriel and Dennis Sweeney.)" msgstr "" #: whatsnew/3.11.rst:1465 @@ -1941,9 +1954,9 @@ msgstr "" #: whatsnew/3.11.rst:1468 msgid "" -"Binary add, multiply and subtract for common types such as :class:`int`, :" -"class:`float` and :class:`str` take custom fast paths for their underlying " -"types." +"Binary add, multiply and subtract for common types such " +"as :class:`int`, :class:`float` and :class:`str` take custom fast paths for " +"their underlying types." msgstr "" #: whatsnew/3.11.rst:1468 @@ -1964,14 +1977,14 @@ msgstr "" #: whatsnew/3.11.rst:1474 msgid "" -"Subscripting container types such as :class:`list`, :class:`tuple` and :" -"class:`dict` directly index the underlying data structures." +"Subscripting container types such as :class:`list`, :class:`tuple` " +"and :class:`dict` directly index the underlying data structures." msgstr "" #: whatsnew/3.11.rst:1478 msgid "" -"Subscripting custom :meth:`~object.__getitem__` is also inlined similar to :" -"ref:`inline-calls`." +"Subscripting custom :meth:`~object.__getitem__` is also inlined similar " +"to :ref:`inline-calls`." msgstr "" #: whatsnew/3.11.rst:1481 @@ -2012,8 +2025,8 @@ msgstr "" #: whatsnew/3.11.rst:1484 msgid "" -"Calls to common builtin (C) functions and types such as :func:`len` and :" -"class:`str` directly call their underlying C version. This avoids going " +"Calls to common builtin (C) functions and types such as :func:`len` " +"and :class:`str` directly call their underlying C version. This avoids going " "through the internal calling convention." msgstr "" @@ -2139,8 +2152,8 @@ msgstr "" #: whatsnew/3.11.rst:1513 msgid "" "A similar optimization already existed since Python 3.10. 3.11 specializes " -"for more forms. Furthermore, all attribute loads should be sped up by :issue:" -"`45947`." +"for more forms. Furthermore, all attribute loads should be sped up " +"by :issue:`45947`." msgstr "" #: whatsnew/3.11.rst:1521 @@ -2156,9 +2169,9 @@ msgstr "" #: whatsnew/3.11.rst:1527 msgid "" -"\"Zero-cost\" exceptions are implemented, eliminating the cost of :keyword:" -"`try` statements when no exception is raised. (Contributed by Mark Shannon " -"in :issue:`40222`.)" +"\"Zero-cost\" exceptions are implemented, eliminating the cost " +"of :keyword:`try` statements when no exception is raised. (Contributed by " +"Mark Shannon in :issue:`40222`.)" msgstr "" #: whatsnew/3.11.rst:1531 @@ -2173,9 +2186,9 @@ msgid "" ":mod:`re`'s regular expression matching engine has been partially " "refactored, and now uses computed gotos (or \"threaded code\") on supported " "platforms. As a result, Python 3.11 executes the `pyperformance regular " -"expression benchmarks `_ up to 10% faster than Python 3.10. (Contributed by Brandt " -"Bucher in :gh:`91404`.)" +"expression benchmarks `_ up to 10% faster than Python 3.10. (Contributed " +"by Brandt Bucher in :gh:`91404`.)" msgstr "" #: whatsnew/3.11.rst:1546 @@ -2285,9 +2298,9 @@ msgstr "" #: whatsnew/3.11.rst:1632 msgid "" -":opcode:`CHECK_EG_MATCH` and :opcode:`!PREP_RERAISE_STAR`, to handle the :" -"ref:`new exception groups and except* ` added in :pep:" -"`654`." +":opcode:`CHECK_EG_MATCH` and :opcode:`!PREP_RERAISE_STAR`, to handle " +"the :ref:`new exception groups and except* ` added " +"in :pep:`654`." msgstr "" #: whatsnew/3.11.rst:1636 @@ -2512,19 +2525,20 @@ msgstr "" #: whatsnew/3.11.rst:1720 msgid "" "Chaining :class:`classmethod` descriptors (introduced in :issue:`19072`) is " -"now deprecated. It can no longer be used to wrap other descriptors such as :" -"class:`property`. The core design of this feature was flawed and caused a " -"number of downstream problems. To \"pass-through\" a :class:`classmethod`, " -"consider using the :attr:`!__wrapped__` attribute that was added in Python " -"3.10. (Contributed by Raymond Hettinger in :gh:`89519`.)" +"now deprecated. It can no longer be used to wrap other descriptors such " +"as :class:`property`. The core design of this feature was flawed and caused " +"a number of downstream problems. To \"pass-through\" " +"a :class:`classmethod`, consider using the :attr:`!__wrapped__` attribute " +"that was added in Python 3.10. (Contributed by Raymond Hettinger " +"in :gh:`89519`.)" msgstr "" #: whatsnew/3.11.rst:1728 msgid "" "Octal escapes in string and bytes literals with values larger than ``0o377`` " "(255 in decimal) now produce a :exc:`DeprecationWarning`. In a future Python " -"version, they will raise a :exc:`SyntaxWarning` and eventually a :exc:" -"`SyntaxError`. (Contributed by Serhiy Storchaka in :gh:`81548`.)" +"version, they will raise a :exc:`SyntaxWarning` and eventually " +"a :exc:`SyntaxError`. (Contributed by Serhiy Storchaka in :gh:`81548`.)" msgstr "" #: whatsnew/3.11.rst:1734 @@ -2532,8 +2546,8 @@ msgid "" "The delegation of :func:`int` to :meth:`~object.__trunc__` is now " "deprecated. Calling ``int(a)`` when ``type(a)`` implements :meth:`!" "__trunc__` but not :meth:`~object.__int__` or :meth:`~object.__index__` now " -"raises a :exc:`DeprecationWarning`. (Contributed by Zackery Spytz in :issue:" -"`44977`.)" +"raises a :exc:`DeprecationWarning`. (Contributed by Zackery Spytz " +"in :issue:`44977`.)" msgstr "" #: whatsnew/3.11.rst:1744 @@ -2624,8 +2638,8 @@ msgstr "" #: whatsnew/3.11.rst:1761 msgid "" -"(Contributed by Brett Cannon in :issue:`47061` and Victor Stinner in :gh:" -"`68966`.)" +"(Contributed by Brett Cannon in :issue:`47061` and Victor Stinner " +"in :gh:`68966`.)" msgstr "" #: whatsnew/3.11.rst:1764 @@ -2639,16 +2653,16 @@ msgstr "" #: whatsnew/3.11.rst:1769 msgid "" "The :mod:`lib2to3` package and :ref:`2to3 <2to3-reference>` tool are now " -"deprecated and may not be able to parse Python 3.10 or newer. See :pep:" -"`617`, introducing the new PEG parser, for details. (Contributed by Victor " -"Stinner in :issue:`40360`.)" +"deprecated and may not be able to parse Python 3.10 or newer. " +"See :pep:`617`, introducing the new PEG parser, for details. (Contributed by " +"Victor Stinner in :issue:`40360`.)" msgstr "" #: whatsnew/3.11.rst:1774 msgid "" "Undocumented modules :mod:`!sre_compile`, :mod:`!sre_constants` and :mod:`!" -"sre_parse` are now deprecated. (Contributed by Serhiy Storchaka in :issue:" -"`47152`.)" +"sre_parse` are now deprecated. (Contributed by Serhiy Storchaka " +"in :issue:`47152`.)" msgstr "" #: whatsnew/3.11.rst:1782 @@ -2683,9 +2697,9 @@ msgid "" ":class:`!configparser.LegacyInterpolation` has been deprecated in the " "docstring since Python 3.2, and is not listed in the :mod:`configparser` " "documentation. It now emits a :exc:`DeprecationWarning` and will be removed " -"in Python 3.13. Use :class:`configparser.BasicInterpolation` or :class:" -"`configparser.ExtendedInterpolation` instead. (Contributed by Hugo van " -"Kemenade in :issue:`46607`.)" +"in Python 3.13. Use :class:`configparser.BasicInterpolation` " +"or :class:`configparser.ExtendedInterpolation` instead. (Contributed by Hugo " +"van Kemenade in :issue:`46607`.)" msgstr "" #: whatsnew/3.11.rst:1801 @@ -2727,9 +2741,10 @@ msgstr "" #: whatsnew/3.11.rst:1814 msgid "" "The :func:`locale.getdefaultlocale` function is deprecated and will be " -"removed in Python 3.15. Use :func:`locale.setlocale`, :func:`locale." -"getpreferredencoding(False) ` and :func:`locale." -"getlocale` functions instead. (Contributed by Victor Stinner in :gh:`90817`.)" +"removed in Python 3.15. " +"Use :func:`locale.setlocale`, :func:`locale.getpreferredencoding(False) " +"` and :func:`locale.getlocale` functions " +"instead. (Contributed by Victor Stinner in :gh:`90817`.)" msgstr "" #: whatsnew/3.11.rst:1820 @@ -2743,11 +2758,11 @@ msgstr "" msgid "" "Stricter rules will now be applied for numerical group references and group " "names in :ref:`regular expressions `. Only sequences of ASCII " -"digits will now be accepted as a numerical reference, and the group name in :" -"class:`bytes` patterns and replacement strings can only contain ASCII " +"digits will now be accepted as a numerical reference, and the group name " +"in :class:`bytes` patterns and replacement strings can only contain ASCII " "letters, digits and underscores. For now, a deprecation warning is raised " -"for syntax violating these rules. (Contributed by Serhiy Storchaka in :gh:" -"`91760`.)" +"for syntax violating these rules. (Contributed by Serhiy Storchaka " +"in :gh:`91760`.)" msgstr "" #: whatsnew/3.11.rst:1832 @@ -2762,10 +2777,10 @@ msgstr "" #: whatsnew/3.11.rst:1838 msgid "" ":func:`turtle.settiltangle` has been deprecated since Python 3.1; it now " -"emits a deprecation warning and will be removed in Python 3.13. Use :func:" -"`turtle.tiltangle` instead (it was earlier incorrectly marked as deprecated, " -"and its docstring is now corrected). (Contributed by Hugo van Kemenade in :" -"issue:`45837`.)" +"emits a deprecation warning and will be removed in Python 3.13. " +"Use :func:`turtle.tiltangle` instead (it was earlier incorrectly marked as " +"deprecated, and its docstring is now corrected). (Contributed by Hugo van " +"Kemenade in :issue:`45837`.)" msgstr "" #: whatsnew/3.11.rst:1844 @@ -2792,8 +2807,8 @@ msgstr "" #: whatsnew/3.11.rst:1858 msgid "" -"The behavior of returning a value from a :class:`~unittest.TestCase` and :" -"class:`~unittest.IsolatedAsyncioTestCase` test methods (other than the " +"The behavior of returning a value from a :class:`~unittest.TestCase` " +"and :class:`~unittest.IsolatedAsyncioTestCase` test methods (other than the " "default ``None`` value) is now deprecated." msgstr "" @@ -3119,10 +3134,11 @@ msgstr "" #: whatsnew/3.11.rst:1955 msgid "" "Removed the :func:`!@asyncio.coroutine` :term:`decorator` enabling legacy " -"generator-based coroutines to be compatible with :keyword:`async` / :keyword:" -"`await` code. The function has been deprecated since Python 3.8 and the " -"removal was initially scheduled for Python 3.10. Use :keyword:`async def` " -"instead. (Contributed by Illia Volochii in :issue:`43216`.)" +"generator-based coroutines to be compatible " +"with :keyword:`async` / :keyword:`await` code. The function has been " +"deprecated since Python 3.8 and the removal was initially scheduled for " +"Python 3.10. Use :keyword:`async def` instead. (Contributed by Illia " +"Volochii in :issue:`43216`.)" msgstr "" #: whatsnew/3.11.rst:1962 @@ -3134,11 +3150,11 @@ msgstr "" #: whatsnew/3.11.rst:1966 msgid "" -"Due to significant security concerns, the *reuse_address* parameter of :meth:" -"`asyncio.loop.create_datagram_endpoint`, disabled in Python 3.9, is now " -"entirely removed. This is because of the behavior of the socket option " -"``SO_REUSEADDR`` in UDP. (Contributed by Hugo van Kemenade in :issue:" -"`45129`.)" +"Due to significant security concerns, the *reuse_address* parameter " +"of :meth:`asyncio.loop.create_datagram_endpoint`, disabled in Python 3.9, is " +"now entirely removed. This is because of the behavior of the socket option " +"``SO_REUSEADDR`` in UDP. (Contributed by Hugo van Kemenade " +"in :issue:`45129`.)" msgstr "" #: whatsnew/3.11.rst:1972 @@ -3180,21 +3196,22 @@ msgstr "" #: whatsnew/3.11.rst:1988 msgid "" -"Removed the :meth:`~object.__getitem__` methods of :class:`xml.dom.pulldom." -"DOMEventStream`, :class:`wsgiref.util.FileWrapper` and :class:`fileinput." -"FileInput`, deprecated since Python 3.9. (Contributed by Hugo van Kemenade " -"in :issue:`45132`.)" +"Removed the :meth:`~object.__getitem__` methods " +"of :class:`xml.dom.pulldom.DOMEventStream`, :class:`wsgiref.util.FileWrapper` " +"and :class:`fileinput.FileInput`, deprecated since Python 3.9. (Contributed " +"by Hugo van Kemenade in :issue:`45132`.)" msgstr "" #: whatsnew/3.11.rst:1993 msgid "" "Removed the deprecated :mod:`gettext` functions :func:`!lgettext`, :func:`!" -"ldgettext`, :func:`!lngettext` and :func:`!ldngettext`. Also removed the :" -"func:`!bind_textdomain_codeset` function, the :meth:`!NullTranslations." -"output_charset` and :meth:`!NullTranslations.set_output_charset` methods, " -"and the *codeset* parameter of :func:`!translation` and :func:`!install`, " -"since they are only used for the :func:`!l*gettext` functions. (Contributed " -"by Donghee Na and Serhiy Storchaka in :issue:`44235`.)" +"ldgettext`, :func:`!lngettext` and :func:`!ldngettext`. Also removed " +"the :func:`!bind_textdomain_codeset` function, the :meth:`!" +"NullTranslations.output_charset` and :meth:`!" +"NullTranslations.set_output_charset` methods, and the *codeset* parameter " +"of :func:`!translation` and :func:`!install`, since they are only used for " +"the :func:`!l*gettext` functions. (Contributed by Donghee Na and Serhiy " +"Storchaka in :issue:`44235`.)" msgstr "" #: whatsnew/3.11.rst:2003 @@ -3203,22 +3220,23 @@ msgstr "" #: whatsnew/3.11.rst:2005 msgid "" -"The :func:`!getargspec` function, deprecated since Python 3.0; use :func:" -"`inspect.signature` or :func:`inspect.getfullargspec` instead." +"The :func:`!getargspec` function, deprecated since Python 3.0; " +"use :func:`inspect.signature` or :func:`inspect.getfullargspec` instead." msgstr "" #: whatsnew/3.11.rst:2008 msgid "" -"The :func:`!formatargspec` function, deprecated since Python 3.5; use the :" -"func:`inspect.signature` function or the :class:`inspect.Signature` object " -"directly." +"The :func:`!formatargspec` function, deprecated since Python 3.5; use " +"the :func:`inspect.signature` function or the :class:`inspect.Signature` " +"object directly." msgstr "" #: whatsnew/3.11.rst:2012 msgid "" -"The undocumented :meth:`!Signature.from_builtin` and :meth:`!Signature." -"from_function` methods, deprecated since Python 3.5; use the :meth:" -"`Signature.from_callable() ` method instead." +"The undocumented :meth:`!Signature.from_builtin` and :meth:`!" +"Signature.from_function` methods, deprecated since Python 3.5; use " +"the :meth:`Signature.from_callable() ` " +"method instead." msgstr "" #: whatsnew/3.11.rst:2017 @@ -3227,9 +3245,9 @@ msgstr "" #: whatsnew/3.11.rst:2019 msgid "" -"Removed the :meth:`~object.__class_getitem__` method from :class:`pathlib." -"PurePath`, because it was not used and added by mistake in previous " -"versions. (Contributed by Nikita Sobolev in :issue:`46483`.)" +"Removed the :meth:`~object.__class_getitem__` method " +"from :class:`pathlib.PurePath`, because it was not used and added by mistake " +"in previous versions. (Contributed by Nikita Sobolev in :issue:`46483`.)" msgstr "" #: whatsnew/3.11.rst:2024 @@ -3241,8 +3259,8 @@ msgstr "" #: whatsnew/3.11.rst:2028 msgid "" -"Removed the deprecated :meth:`!split` method of :class:`!_tkinter." -"TkappType`. (Contributed by Erlend E. Aasland in :issue:`38371`.)" +"Removed the deprecated :meth:`!split` method of :class:`!" +"_tkinter.TkappType`. (Contributed by Erlend E. Aasland in :issue:`38371`.)" msgstr "" #: whatsnew/3.11.rst:2031 @@ -3293,21 +3311,21 @@ msgstr "" #: whatsnew/3.11.rst:2063 msgid "" -":func:`open`, :func:`io.open`, :func:`codecs.open` and :class:`fileinput." -"FileInput` no longer accept ``'U'`` (\"universal newline\") in the file " -"mode. In Python 3, \"universal newline\" mode is used by default whenever a " -"file is opened in text mode, and the ``'U'`` flag has been deprecated since " -"Python 3.3. The :ref:`newline parameter ` to these " -"functions controls how universal newlines work. (Contributed by Victor " -"Stinner in :issue:`37330`.)" +":func:`open`, :func:`io.open`, :func:`codecs.open` " +"and :class:`fileinput.FileInput` no longer accept ``'U'`` (\"universal " +"newline\") in the file mode. In Python 3, \"universal newline\" mode is used " +"by default whenever a file is opened in text mode, and the ``'U'`` flag has " +"been deprecated since Python 3.3. The :ref:`newline parameter ` to these functions controls how universal newlines work. " +"(Contributed by Victor Stinner in :issue:`37330`.)" msgstr "" #: whatsnew/3.11.rst:2072 msgid "" -":class:`ast.AST` node positions are now validated when provided to :func:" -"`compile` and other related functions. If invalid positions are detected, a :" -"exc:`ValueError` will be raised. (Contributed by Pablo Galindo in :gh:" -"`93351`)" +":class:`ast.AST` node positions are now validated when provided " +"to :func:`compile` and other related functions. If invalid positions are " +"detected, a :exc:`ValueError` will be raised. (Contributed by Pablo Galindo " +"in :gh:`93351`)" msgstr "" #: whatsnew/3.11.rst:2076 @@ -3319,9 +3337,10 @@ msgstr "" #: whatsnew/3.11.rst:2081 msgid "" -":mod:`calendar`: The :class:`calendar.LocaleTextCalendar` and :class:" -"`calendar.LocaleHTMLCalendar` classes now use :func:`locale.getlocale`, " -"instead of using :func:`locale.getdefaultlocale`, if no locale is specified. " +":mod:`calendar`: The :class:`calendar.LocaleTextCalendar` " +"and :class:`calendar.LocaleHTMLCalendar` classes now " +"use :func:`locale.getlocale`, instead of " +"using :func:`locale.getdefaultlocale`, if no locale is specified. " "(Contributed by Victor Stinner in :issue:`46659`.)" msgstr "" @@ -3336,24 +3355,24 @@ msgstr "" msgid "" "The *population* parameter of :func:`random.sample` must be a sequence, and " "automatic conversion of :class:`set`\\s to :class:`list`\\s is no longer " -"supported. Also, if the sample size is larger than the population size, a :" -"exc:`ValueError` is raised. (Contributed by Raymond Hettinger in :issue:" -"`40465`.)" +"supported. Also, if the sample size is larger than the population size, " +"a :exc:`ValueError` is raised. (Contributed by Raymond Hettinger " +"in :issue:`40465`.)" msgstr "" #: whatsnew/3.11.rst:2097 msgid "" "The *random* optional parameter of :func:`random.shuffle` was removed. It " -"was previously an arbitrary random function to use for the shuffle; now, :" -"func:`random.random` (its previous default) will always be used." +"was previously an arbitrary random function to use for the shuffle; " +"now, :func:`random.random` (its previous default) will always be used." msgstr "" #: whatsnew/3.11.rst:2101 msgid "" "In :mod:`re` :ref:`re-syntax`, global inline flags (e.g. ``(?i)``) can now " "only be used at the start of regular expressions. Using them elsewhere has " -"been deprecated since Python 3.6. (Contributed by Serhiy Storchaka in :issue:" -"`47066`.)" +"been deprecated since Python 3.6. (Contributed by Serhiy Storchaka " +"in :issue:`47066`.)" msgstr "" #: whatsnew/3.11.rst:2106 @@ -3379,8 +3398,8 @@ msgid "" "limited subset of POSIX APIs; Python standard libraries features and modules " "related to networking, processes, threading, signals, mmap, and users/groups " "are not available or don't work. (Emscripten contributed by Christian Heimes " -"and Ethan Smith in :gh:`84461` and WASI contributed by Christian Heimes in :" -"gh:`90473`; platforms promoted in :gh:`95085`)" +"and Ethan Smith in :gh:`84461` and WASI contributed by Christian Heimes " +"in :gh:`90473`; platforms promoted in :gh:`95085`)" msgstr "" #: whatsnew/3.11.rst:2131 @@ -3392,8 +3411,8 @@ msgid "" "A `C11 `_ compiler and standard library. " "`Optional C11 features `_ are not required. " -"(Contributed by Victor Stinner in :issue:`46656`, :issue:`45440` and :issue:" -"`46640`.)" +"(Contributed by Victor Stinner in :issue:`46656`, :issue:`45440` " +"and :issue:`46640`.)" msgstr "" #: whatsnew/3.11.rst:2140 @@ -3423,8 +3442,8 @@ msgid "" "detected by `pkg-config `_ (when available). :mod:`tkinter` now requires a pkg-config " "command to detect development settings for `Tcl/Tk`_ headers and libraries. " -"(Contributed by Christian Heimes and Erlend Egeberg Aasland in :issue:" -"`45847`, :issue:`45747`, and :issue:`45763`.)" +"(Contributed by Christian Heimes and Erlend Egeberg Aasland " +"in :issue:`45847`, :issue:`45747`, and :issue:`45763`.)" msgstr "" #: whatsnew/3.11.rst:2162 @@ -3437,16 +3456,16 @@ msgstr "" msgid "" "CPython can now be built with the `ThinLTO `_ option via passing ``thin`` to :option:`--with-lto`, i.e. " -"``--with-lto=thin``. (Contributed by Donghee Na and Brett Holman in :issue:" -"`44340`.)" +"``--with-lto=thin``. (Contributed by Donghee Na and Brett Holman " +"in :issue:`44340`.)" msgstr "" #: whatsnew/3.11.rst:2170 msgid "" "Freelists for object structs can now be disabled. A new :program:`configure` " "option :option:`--without-freelists` can be used to disable all freelists " -"except empty tuple singleton. (Contributed by Christian Heimes in :issue:" -"`45522`.)" +"except empty tuple singleton. (Contributed by Christian Heimes " +"in :issue:`45522`.)" msgstr "" #: whatsnew/3.11.rst:2175 @@ -3454,8 +3473,8 @@ msgid "" "``Modules/Setup`` and ``Modules/makesetup`` have been improved and tied up. " "Extension modules can now be built through ``makesetup``. All except some " "test modules can be linked statically into a main binary or library. " -"(Contributed by Brett Cannon and Christian Heimes in :issue:`45548`, :issue:" -"`45570`, :issue:`45571`, and :issue:`43974`.)" +"(Contributed by Brett Cannon and Christian Heimes " +"in :issue:`45548`, :issue:`45570`, :issue:`45571`, and :issue:`43974`.)" msgstr "" #: whatsnew/3.11.rst:2182 @@ -3479,11 +3498,11 @@ msgid "" "CPython will now use 30-bit digits by default for the Python :class:`int` " "implementation. Previously, the default was to use 30-bit digits on " "platforms with ``SIZEOF_VOID_P >= 8``, and 15-bit digits otherwise. It's " -"still possible to explicitly request use of 15-bit digits via either the :" -"option:`--enable-big-digits` option to the configure script or (for Windows) " -"the ``PYLONG_BITS_IN_DIGIT`` variable in ``PC/pyconfig.h``, but this option " -"may be removed at some point in the future. (Contributed by Mark Dickinson " -"in :issue:`45569`.)" +"still possible to explicitly request use of 15-bit digits via either " +"the :option:`--enable-big-digits` option to the configure script or (for " +"Windows) the ``PYLONG_BITS_IN_DIGIT`` variable in ``PC/pyconfig.h``, but " +"this option may be removed at some point in the future. (Contributed by Mark " +"Dickinson in :issue:`45569`.)" msgstr "" #: whatsnew/3.11.rst:2206 @@ -3504,17 +3523,17 @@ msgstr "" #: whatsnew/3.11.rst:2219 msgid "" -"Add new :c:func:`PyThreadState_EnterTracing` and :c:func:" -"`PyThreadState_LeaveTracing` functions to the limited C API to suspend and " -"resume tracing and profiling. (Contributed by Victor Stinner in :issue:" -"`43760`.)" +"Add new :c:func:`PyThreadState_EnterTracing` " +"and :c:func:`PyThreadState_LeaveTracing` functions to the limited C API to " +"suspend and resume tracing and profiling. (Contributed by Victor Stinner " +"in :issue:`43760`.)" msgstr "" #: whatsnew/3.11.rst:2224 msgid "" -"Added the :c:data:`Py_Version` constant which bears the same value as :c:" -"macro:`PY_VERSION_HEX`. (Contributed by Gabriele N. Tornetta in :issue:" -"`43931`.)" +"Added the :c:data:`Py_Version` constant which bears the same value " +"as :c:macro:`PY_VERSION_HEX`. (Contributed by Gabriele N. Tornetta " +"in :issue:`43931`.)" msgstr "" #: whatsnew/3.11.rst:2228 @@ -3573,8 +3592,8 @@ msgstr "" #: whatsnew/3.11.rst:2243 msgid "" -":c:member:`~PyBufferProcs.bf_getbuffer` and :c:member:`~PyBufferProcs." -"bf_releasebuffer` type slots" +":c:member:`~PyBufferProcs.bf_getbuffer` " +"and :c:member:`~PyBufferProcs.bf_releasebuffer` type slots" msgstr "" #: whatsnew/3.11.rst:2246 @@ -3591,26 +3610,26 @@ msgstr "" #: whatsnew/3.11.rst:2253 msgid "" -"Add new functions to pack and unpack C double (serialize and deserialize): :" -"c:func:`PyFloat_Pack2`, :c:func:`PyFloat_Pack4`, :c:func:`PyFloat_Pack8`, :c:" -"func:`PyFloat_Unpack2`, :c:func:`PyFloat_Unpack4` and :c:func:" -"`PyFloat_Unpack8`. (Contributed by Victor Stinner in :issue:`46906`.)" +"Add new functions to pack and unpack C double (serialize and " +"deserialize): :c:func:`PyFloat_Pack2`, :c:func:`PyFloat_Pack4`, :c:func:`PyFloat_Pack8`, :c:func:`PyFloat_Unpack2`, :c:func:`PyFloat_Unpack4` " +"and :c:func:`PyFloat_Unpack8`. (Contributed by Victor Stinner " +"in :issue:`46906`.)" msgstr "" #: whatsnew/3.11.rst:2259 msgid "" -"Add new functions to get frame object attributes: :c:func:" -"`PyFrame_GetBuiltins`, :c:func:`PyFrame_GetGenerator`, :c:func:" -"`PyFrame_GetGlobals`, :c:func:`PyFrame_GetLasti`." +"Add new functions to get frame object " +"attributes: :c:func:`PyFrame_GetBuiltins`, :c:func:`PyFrame_GetGenerator`, :c:func:`PyFrame_GetGlobals`, :c:func:`PyFrame_GetLasti`." msgstr "" #: whatsnew/3.11.rst:2263 msgid "" -"Added two new functions to get and set the active exception instance: :c:" -"func:`PyErr_GetHandledException` and :c:func:`PyErr_SetHandledException`. " -"These are alternatives to :c:func:`PyErr_SetExcInfo()` and :c:func:" -"`PyErr_GetExcInfo()` which work with the legacy 3-tuple representation of " -"exceptions. (Contributed by Irit Katriel in :issue:`46343`.)" +"Added two new functions to get and set the active exception " +"instance: :c:func:`PyErr_GetHandledException` " +"and :c:func:`PyErr_SetHandledException`. These are alternatives " +"to :c:func:`PyErr_SetExcInfo()` and :c:func:`PyErr_GetExcInfo()` which work " +"with the legacy 3-tuple representation of exceptions. (Contributed by Irit " +"Katriel in :issue:`46343`.)" msgstr "" #: whatsnew/3.11.rst:2270 @@ -3673,8 +3692,8 @@ msgstr "" #: whatsnew/3.11.rst:2318 msgid "" ":c:type:`PyCodeObject` no longer has the ``co_code``, ``co_varnames``, " -"``co_cellvars`` and ``co_freevars`` fields. Instead, use :c:func:" -"`PyCode_GetCode`, :c:func:`PyCode_GetVarnames`, :c:func:`PyCode_GetCellvars` " +"``co_cellvars`` and ``co_freevars`` fields. Instead, " +"use :c:func:`PyCode_GetCode`, :c:func:`PyCode_GetVarnames`, :c:func:`PyCode_GetCellvars` " "and :c:func:`PyCode_GetFreevars` respectively to access them via the C API. " "(Contributed by Brandt Bucher in :issue:`46841` and Ken Jin in :gh:`92154` " "and :gh:`94936`.)" @@ -3747,16 +3766,16 @@ msgstr "" msgid "" "The :c:func:`PyType_Ready` function now raises an error if a type is defined " "with the :c:macro:`Py_TPFLAGS_HAVE_GC` flag set but has no traverse function " -"(:c:member:`PyTypeObject.tp_traverse`). (Contributed by Victor Stinner in :" -"issue:`44263`.)" +"(:c:member:`PyTypeObject.tp_traverse`). (Contributed by Victor Stinner " +"in :issue:`44263`.)" msgstr "" #: whatsnew/3.11.rst:2372 msgid "" "Heap types with the :c:macro:`Py_TPFLAGS_IMMUTABLETYPE` flag can now inherit " -"the :pep:`590` vectorcall protocol. Previously, this was only possible for :" -"ref:`static types `. (Contributed by Erlend E. Aasland in :" -"issue:`43908`)" +"the :pep:`590` vectorcall protocol. Previously, this was only possible " +"for :ref:`static types `. (Contributed by Erlend E. Aasland " +"in :issue:`43908`)" msgstr "" #: whatsnew/3.11.rst:2377 @@ -3799,9 +3818,9 @@ msgstr "" #: whatsnew/3.11.rst:2405 msgid "" -"```` no longer includes the header files ````, ````, ```` and ```` when the ``Py_LIMITED_API`` macro is " -"set to ``0x030b0000`` (Python 3.11) or higher. C extensions should " +"```` no longer includes the header files ````, " +"````, ```` and ```` when the ``Py_LIMITED_API`` " +"macro is set to ``0x030b0000`` (Python 3.11) or higher. C extensions should " "explicitly include the header files after ``#include ``. " "(Contributed by Victor Stinner in :issue:`45434`.)" msgstr "" @@ -3969,19 +3988,19 @@ msgstr "" #: whatsnew/3.11.rst:2474 msgid "" -"The Python frame object is now created lazily. A side effect is that the :" -"attr:`~frame.f_back` member must not be accessed directly, since its value " -"is now also computed lazily. The :c:func:`PyFrame_GetBack` function must be " -"called instead." +"The Python frame object is now created lazily. A side effect is that " +"the :attr:`~frame.f_back` member must not be accessed directly, since its " +"value is now also computed lazily. The :c:func:`PyFrame_GetBack` function " +"must be called instead." msgstr "" #: whatsnew/3.11.rst:2480 msgid "" -"Debuggers that accessed the :attr:`~frame.f_locals` directly *must* call :c:" -"func:`PyFrame_GetLocals` instead. They no longer need to call :c:func:`!" -"PyFrame_FastToLocalsWithError` or :c:func:`!PyFrame_LocalsToFast`, in fact " -"they should not call those functions. The necessary updating of the frame is " -"now managed by the virtual machine." +"Debuggers that accessed the :attr:`~frame.f_locals` directly *must* " +"call :c:func:`PyFrame_GetLocals` instead. They no longer need to " +"call :c:func:`!PyFrame_FastToLocalsWithError` or :c:func:`!" +"PyFrame_LocalsToFast`, in fact they should not call those functions. The " +"necessary updating of the frame is now managed by the virtual machine." msgstr "" #: whatsnew/3.11.rst:2486 @@ -4033,9 +4052,9 @@ msgstr "" #: whatsnew/3.11.rst:2516 msgid "" -"``tracing``: changed, use :c:func:`PyThreadState_EnterTracing` and :c:func:" -"`PyThreadState_LeaveTracing` (functions added to Python 3.11 by :issue:" -"`43760`)." +"``tracing``: changed, use :c:func:`PyThreadState_EnterTracing` " +"and :c:func:`PyThreadState_LeaveTracing` (functions added to Python 3.11 " +"by :issue:`43760`)." msgstr "" #: whatsnew/3.11.rst:2519 @@ -4120,8 +4139,8 @@ msgstr "" msgid "" ":c:func:`PyConfig_Read` no longer calculates the initial search path, and " "will not fill any values into :c:member:`PyConfig.module_search_paths`. To " -"calculate default paths and then modify them, finish initialization and use :" -"c:func:`PySys_GetObject` to retrieve :data:`sys.path` as a Python list " +"calculate default paths and then modify them, finish initialization and " +"use :c:func:`PySys_GetObject` to retrieve :data:`sys.path` as a Python list " "object and modify it directly." msgstr "" @@ -4187,8 +4206,9 @@ msgstr "" #: whatsnew/3.11.rst:2601 msgid "" -"Deprecate the ``ob_shash`` member of the :c:type:`PyBytesObject`. Use :c:" -"func:`PyObject_Hash` instead. (Contributed by Inada Naoki in :issue:`46864`.)" +"Deprecate the ``ob_shash`` member of the :c:type:`PyBytesObject`. " +"Use :c:func:`PyObject_Hash` instead. (Contributed by Inada Naoki " +"in :issue:`46864`.)" msgstr "" #: whatsnew/3.11.rst:2610 @@ -4313,8 +4333,8 @@ msgstr "" #: whatsnew/3.11.rst:2659 msgid "" "Remove the ``Py_FORCE_DOUBLE()`` macro. It was used by the " -"``Py_IS_INFINITY()`` macro. (Contributed by Victor Stinner in :issue:" -"`45440`.)" +"``Py_IS_INFINITY()`` macro. (Contributed by Victor Stinner " +"in :issue:`45440`.)" msgstr "" #: whatsnew/3.11.rst:2663 diff --git a/whatsnew/3.12.po b/whatsnew/3.12.po index 09a68fcd7..d79bfd1cb 100644 --- a/whatsnew/3.12.po +++ b/whatsnew/3.12.po @@ -31,8 +31,8 @@ msgstr "" #: whatsnew/3.12.rst:48 msgid "" "This article explains the new features in Python 3.12, compared to 3.11. " -"Python 3.12 was released on October 2, 2023. For full details, see the :ref:" -"`changelog `." +"Python 3.12 was released on October 2, 2023. For full details, see " +"the :ref:`changelog `." msgstr "" #: whatsnew/3.12.rst:54 @@ -58,9 +58,9 @@ msgid "" "The language changes focus on usability, as :term:`f-strings ` " "have had many limitations removed and 'Did you mean ...' suggestions " "continue to improve. The new :ref:`type parameter syntax ` and :keyword:`type` statement improve ergonomics for using :term:" -"`generic types ` and :term:`type aliases ` with " -"static type checkers." +"pep695>` and :keyword:`type` statement improve ergonomics for " +"using :term:`generic types ` and :term:`type aliases ` with static type checkers." msgstr "" #: whatsnew/3.12.rst:76 @@ -80,8 +80,8 @@ msgstr "" #: whatsnew/3.12.rst:92 msgid "" -":ref:`PEP 695 `, type parameter syntax and the :keyword:" -"`type` statement" +":ref:`PEP 695 `, type parameter syntax and " +"the :keyword:`type` statement" msgstr "" #: whatsnew/3.12.rst:94 @@ -110,8 +110,8 @@ msgstr "" #: whatsnew/3.12.rst:103 msgid "" -"`Improved 'Did you mean ...' suggestions `_ for :" -"exc:`NameError`, :exc:`ImportError`, and :exc:`SyntaxError` exceptions" +"`Improved 'Did you mean ...' suggestions `_ " +"for :exc:`NameError`, :exc:`ImportError`, and :exc:`SyntaxError` exceptions" msgstr "" #: whatsnew/3.12.rst:106 @@ -138,14 +138,14 @@ msgstr "" #: whatsnew/3.12.rst:115 msgid "" -"A :ref:`command-line interface ` has been added to the :mod:" -"`sqlite3` module" +"A :ref:`command-line interface ` has been added to " +"the :mod:`sqlite3` module" msgstr "" #: whatsnew/3.12.rst:117 msgid "" -":func:`isinstance` checks against :func:`runtime-checkable protocols ` enjoy a speed up of between two and 20 times" +":func:`isinstance` checks against :func:`runtime-checkable protocols " +"` enjoy a speed up of between two and 20 times" msgstr "" #: whatsnew/3.12.rst:119 @@ -272,8 +272,8 @@ msgstr "" #: whatsnew/3.12.rst:187 msgid "" -":pep:`695` introduces a new, more compact and explicit way to create :ref:" -"`generic classes ` and :ref:`functions ` and :ref:`functions `::" msgstr "" @@ -311,9 +311,9 @@ msgstr "" #: whatsnew/3.12.rst:210 msgid "" -"The new syntax allows declaring :class:`~typing.TypeVarTuple` and :class:" -"`~typing.ParamSpec` parameters, as well as :class:`~typing.TypeVar` " -"parameters with bounds or constraints::" +"The new syntax allows declaring :class:`~typing.TypeVarTuple` " +"and :class:`~typing.ParamSpec` parameters, as well " +"as :class:`~typing.TypeVar` parameters with bounds or constraints::" msgstr "" #: whatsnew/3.12.rst:214 @@ -409,10 +409,11 @@ msgstr "" #: whatsnew/3.12.rst:290 msgid "" "Backslashes and unicode characters: before Python 3.12 f-string expressions " -"couldn't contain any ``\\`` character. This also affected unicode :ref:" -"`escape sequences ` (such as ``\\N{snowman}``) as these " -"contain the ``\\N`` part that previously could not be part of expression " -"components of f-strings. Now, you can define expressions like this:" +"couldn't contain any ``\\`` character. This also affected " +"unicode :ref:`escape sequences ` (such as ``\\N{snowman}" +"``) as these contain the ``\\N`` part that previously could not be part of " +"expression components of f-strings. Now, you can define expressions like " +"this:" msgstr "" #: whatsnew/3.12.rst:303 @@ -528,16 +529,17 @@ msgstr "" #: whatsnew/3.12.rst:386 msgid "" ":pep:`688` introduces a way to use the :ref:`buffer protocol " -"` from Python code. Classes that implement the :meth:`~object." -"__buffer__` method are now usable as buffer types." +"` from Python code. Classes that implement " +"the :meth:`~object.__buffer__` method are now usable as buffer types." msgstr "" #: whatsnew/3.12.rst:390 msgid "" "The new :class:`collections.abc.Buffer` ABC provides a standard way to " -"represent buffer objects, for example in type annotations. The new :class:" -"`inspect.BufferFlags` enum represents the flags that can be used to " -"customize buffer creation. (Contributed by Jelle Zijlstra in :gh:`102500`.)" +"represent buffer objects, for example in type annotations. The " +"new :class:`inspect.BufferFlags` enum represents the flags that can be used " +"to customize buffer creation. (Contributed by Jelle Zijlstra " +"in :gh:`102500`.)" msgstr "" #: whatsnew/3.12.rst:399 @@ -616,8 +618,8 @@ msgstr "" #: whatsnew/3.12.rst:459 msgid "" "Improve the :exc:`SyntaxError` error message when the user types ``import x " -"from y`` instead of ``from y import x``. (Contributed by Pablo Galindo in :" -"gh:`98931`.)" +"from y`` instead of ``from y import x``. (Contributed by Pablo Galindo " +"in :gh:`98931`.)" msgstr "" #: whatsnew/3.12.rst:469 @@ -634,8 +636,8 @@ msgstr "" #: whatsnew/3.12.rst:482 msgid "" -"This section covers major changes affecting :pep:`type hints <484>` and the :" -"mod:`typing` module." +"This section covers major changes affecting :pep:`type hints <484>` and " +"the :mod:`typing` module." msgstr "" #: whatsnew/3.12.rst:488 @@ -734,17 +736,18 @@ msgid "" "a :exc:`SyntaxWarning`, instead of :exc:`DeprecationWarning`. For example, " "``re.compile(\"\\d+\\.\\d+\")`` now emits a :exc:`SyntaxWarning` " "(``\"\\d\"`` is an invalid escape sequence, use raw strings for regular " -"expression: ``re.compile(r\"\\d+\\.\\d+\")``). In a future Python version, :" -"exc:`SyntaxError` will eventually be raised, instead of :exc:" -"`SyntaxWarning`. (Contributed by Victor Stinner in :gh:`98401`.)" +"expression: ``re.compile(r\"\\d+\\.\\d+\")``). In a future Python " +"version, :exc:`SyntaxError` will eventually be raised, instead " +"of :exc:`SyntaxWarning`. (Contributed by Victor Stinner in :gh:`98401`.)" msgstr "" #: whatsnew/3.12.rst:557 msgid "" "Octal escapes with value larger than ``0o377`` (ex: ``\"\\477\"``), " -"deprecated in Python 3.11, now produce a :exc:`SyntaxWarning`, instead of :" -"exc:`DeprecationWarning`. In a future Python version they will be eventually " -"a :exc:`SyntaxError`. (Contributed by Victor Stinner in :gh:`98401`.)" +"deprecated in Python 3.11, now produce a :exc:`SyntaxWarning`, instead " +"of :exc:`DeprecationWarning`. In a future Python version they will be " +"eventually a :exc:`SyntaxError`. (Contributed by Victor Stinner " +"in :gh:`98401`.)" msgstr "" #: whatsnew/3.12.rst:563 @@ -767,9 +770,9 @@ msgstr "" #: whatsnew/3.12.rst:574 msgid "" "When a ``try-except*`` construct handles the entire :exc:`ExceptionGroup` " -"and raises one other exception, that exception is no longer wrapped in an :" -"exc:`ExceptionGroup`. Also changed in version 3.11.4. (Contributed by Irit " -"Katriel in :gh:`103590`.)" +"and raises one other exception, that exception is no longer wrapped in " +"an :exc:`ExceptionGroup`. Also changed in version 3.11.4. (Contributed by " +"Irit Katriel in :gh:`103590`.)" msgstr "" #: whatsnew/3.12.rst:579 @@ -778,8 +781,8 @@ msgid "" "Python bytecode evaluation loop instead of object allocations. The GC can " "also run when :c:func:`PyErr_CheckSignals` is called so C extensions that " "need to run for a long time without executing any Python code also have a " -"chance to execute the GC periodically. (Contributed by Pablo Galindo in :gh:" -"`97922`.)" +"chance to execute the GC periodically. (Contributed by Pablo Galindo " +"in :gh:`97922`.)" msgstr "" #: whatsnew/3.12.rst:586 @@ -835,12 +838,13 @@ msgstr "" #: whatsnew/3.12.rst:616 msgid "" "Add :ref:`support for the perf profiler ` through the new " -"environment variable :envvar:`PYTHONPERFSUPPORT` and command-line option :" -"option:`-X perf <-X>`, as well as the new :func:`sys." -"activate_stack_trampoline`, :func:`sys.deactivate_stack_trampoline`, and :" -"func:`sys.is_stack_trampoline_active` functions. (Design by Pablo Galindo. " -"Contributed by Pablo Galindo and Christian Heimes with contributions from " -"Gregory P. Smith [Google] and Mark Shannon in :gh:`96123`.)" +"environment variable :envvar:`PYTHONPERFSUPPORT` and command-line " +"option :option:`-X perf <-X>`, as well as the " +"new :func:`sys.activate_stack_trampoline`, :func:`sys.deactivate_stack_trampoline`, " +"and :func:`sys.is_stack_trampoline_active` functions. (Design by Pablo " +"Galindo. Contributed by Pablo Galindo and Christian Heimes with " +"contributions from Gregory P. Smith [Google] and Mark Shannon " +"in :gh:`96123`.)" msgstr "" #: whatsnew/3.12.rst:628 @@ -861,8 +865,8 @@ msgstr "" #: whatsnew/3.12.rst:639 msgid "" -"The :class:`array.array` class now supports subscripting, making it a :term:" -"`generic type`. (Contributed by Jelle Zijlstra in :gh:`98658`.)" +"The :class:`array.array` class now supports subscripting, making it " +"a :term:`generic type`. (Contributed by Jelle Zijlstra in :gh:`98658`.)" msgstr "" #: whatsnew/3.12.rst:643 @@ -879,25 +883,28 @@ msgstr "" #: whatsnew/3.12.rst:650 msgid "" -"Add :func:`asyncio.eager_task_factory` and :func:`asyncio." -"create_eager_task_factory` functions to allow opting an event loop in to " -"eager task execution, making some use-cases 2x to 5x faster. (Contributed by " -"Jacob Bower & Itamar Oren in :gh:`102853`, :gh:`104140`, and :gh:`104138`)" +"Add :func:`asyncio.eager_task_factory` " +"and :func:`asyncio.create_eager_task_factory` functions to allow opting an " +"event loop in to eager task execution, making some use-cases 2x to 5x " +"faster. (Contributed by Jacob Bower & Itamar Oren " +"in :gh:`102853`, :gh:`104140`, and :gh:`104138`)" msgstr "" #: whatsnew/3.12.rst:655 msgid "" "On Linux, :mod:`asyncio` uses :class:`asyncio.PidfdChildWatcher` by default " -"if :func:`os.pidfd_open` is available and functional instead of :class:" -"`asyncio.ThreadedChildWatcher`. (Contributed by Kumar Aditya in :gh:`98024`.)" +"if :func:`os.pidfd_open` is available and functional instead " +"of :class:`asyncio.ThreadedChildWatcher`. (Contributed by Kumar Aditya " +"in :gh:`98024`.)" msgstr "" #: whatsnew/3.12.rst:660 msgid "" -"The event loop now uses the best available child watcher for each platform (:" -"class:`asyncio.PidfdChildWatcher` if supported and :class:`asyncio." -"ThreadedChildWatcher` otherwise), so manually configuring a child watcher is " -"not recommended. (Contributed by Kumar Aditya in :gh:`94597`.)" +"The event loop now uses the best available child watcher for each platform " +"(:class:`asyncio.PidfdChildWatcher` if supported " +"and :class:`asyncio.ThreadedChildWatcher` otherwise), so manually " +"configuring a child watcher is not recommended. (Contributed by Kumar Aditya " +"in :gh:`94597`.)" msgstr "" #: whatsnew/3.12.rst:666 @@ -914,9 +921,9 @@ msgstr "" #: whatsnew/3.12.rst:673 msgid "" -":func:`asyncio.iscoroutine` now returns ``False`` for generators as :mod:" -"`asyncio` does not support legacy generator-based coroutines. (Contributed " -"by Kumar Aditya in :gh:`102748`.)" +":func:`asyncio.iscoroutine` now returns ``False`` for generators " +"as :mod:`asyncio` does not support legacy generator-based coroutines. " +"(Contributed by Kumar Aditya in :gh:`102748`.)" msgstr "" #: whatsnew/3.12.rst:677 @@ -932,8 +939,8 @@ msgstr "" #: whatsnew/3.12.rst:684 msgid "" "Add enums :data:`calendar.Month` and :data:`calendar.Day` defining months of " -"the year and days of the week. (Contributed by Prince Roshan in :gh:" -"`103636`.)" +"the year and days of the week. (Contributed by Prince Roshan " +"in :gh:`103636`.)" msgstr "" #: whatsnew/3.12.rst:689 @@ -943,8 +950,8 @@ msgstr "" #: whatsnew/3.12.rst:691 msgid "" "Add :const:`csv.QUOTE_NOTNULL` and :const:`csv.QUOTE_STRINGS` flags to " -"provide finer grained control of ``None`` and empty strings by :class:`csv." -"writer` objects." +"provide finer grained control of ``None`` and empty strings " +"by :class:`csv.writer` objects." msgstr "" #: whatsnew/3.12.rst:696 @@ -954,10 +961,10 @@ msgstr "" #: whatsnew/3.12.rst:698 msgid "" "Pseudo instruction opcodes (which are used by the compiler but do not appear " -"in executable bytecode) are now exposed in the :mod:`dis` module. :opcode:" -"`HAVE_ARGUMENT` is still relevant to real opcodes, but it is not useful for " -"pseudo instructions. Use the new :data:`dis.hasarg` collection instead. " -"(Contributed by Irit Katriel in :gh:`94216`.)" +"in executable bytecode) are now exposed in the :mod:`dis` " +"module. :opcode:`HAVE_ARGUMENT` is still relevant to real opcodes, but it is " +"not useful for pseudo instructions. Use the new :data:`dis.hasarg` " +"collection instead. (Contributed by Irit Katriel in :gh:`94216`.)" msgstr "" #: whatsnew/3.12.rst:706 @@ -1051,16 +1058,16 @@ msgstr "" #: whatsnew/3.12.rst:759 msgid "" -"Add :const:`os.PIDFD_NONBLOCK` to open a file descriptor for a process with :" -"func:`os.pidfd_open` in non-blocking mode. (Contributed by Kumar Aditya in :" -"gh:`93312`.)" +"Add :const:`os.PIDFD_NONBLOCK` to open a file descriptor for a process " +"with :func:`os.pidfd_open` in non-blocking mode. (Contributed by Kumar " +"Aditya in :gh:`93312`.)" msgstr "" #: whatsnew/3.12.rst:763 msgid "" ":class:`os.DirEntry` now includes an :meth:`os.DirEntry.is_junction` method " -"to check if the entry is a junction. (Contributed by Charles Machalow in :gh:" -"`99547`.)" +"to check if the entry is a junction. (Contributed by Charles Machalow " +"in :gh:`99547`.)" msgstr "" #: whatsnew/3.12.rst:767 @@ -1079,8 +1086,8 @@ msgid "" "with other platforms). ``st_dev`` may be up to 64 bits and ``st_ino`` up to " "128 bits depending on your file system, and ``st_rdev`` is always set to " "zero rather than incorrect values. Both functions may be significantly " -"faster on newer releases of Windows. (Contributed by Steve Dower in :gh:" -"`99726`.)" +"faster on newer releases of Windows. (Contributed by Steve Dower " +"in :gh:`99726`.)" msgstr "" #: whatsnew/3.12.rst:781 @@ -1114,10 +1121,10 @@ msgstr "" #: whatsnew/3.12.rst:800 msgid "" -"Add support for subclassing :class:`pathlib.PurePath` and :class:`pathlib." -"Path`, plus their Posix- and Windows-specific variants. Subclasses may " -"override the :meth:`pathlib.PurePath.with_segments` method to pass " -"information between path instances." +"Add support for subclassing :class:`pathlib.PurePath` " +"and :class:`pathlib.Path`, plus their Posix- and Windows-specific variants. " +"Subclasses may override the :meth:`pathlib.PurePath.with_segments` method to " +"pass information between path instances." msgstr "" #: whatsnew/3.12.rst:805 @@ -1131,22 +1138,23 @@ msgstr "" msgid "" "Add *walk_up* optional parameter to :meth:`pathlib.PurePath.relative_to` to " "allow the insertion of ``..`` entries in the result; this behavior is more " -"consistent with :func:`os.path.relpath`. (Contributed by Domenico Ragusa in :" -"gh:`84538`.)" +"consistent with :func:`os.path.relpath`. (Contributed by Domenico Ragusa " +"in :gh:`84538`.)" msgstr "" #: whatsnew/3.12.rst:814 msgid "" -"Add :meth:`pathlib.Path.is_junction` as a proxy to :func:`os.path." -"isjunction`. (Contributed by Charles Machalow in :gh:`99547`.)" +"Add :meth:`pathlib.Path.is_junction` as a proxy " +"to :func:`os.path.isjunction`. (Contributed by Charles Machalow " +"in :gh:`99547`.)" msgstr "" #: whatsnew/3.12.rst:817 msgid "" -"Add *case_sensitive* optional parameter to :meth:`pathlib.Path.glob`, :meth:" -"`pathlib.Path.rglob` and :meth:`pathlib.PurePath.match` for matching the " -"path's case sensitivity, allowing for more precise control over the matching " -"process." +"Add *case_sensitive* optional parameter " +"to :meth:`pathlib.Path.glob`, :meth:`pathlib.Path.rglob` " +"and :meth:`pathlib.PurePath.match` for matching the path's case sensitivity, " +"allowing for more precise control over the matching process." msgstr "" #: whatsnew/3.12.rst:822 @@ -1166,8 +1174,8 @@ msgstr "" #: whatsnew/3.12.rst:832 msgid "" -"Add :func:`random.binomialvariate`. (Contributed by Raymond Hettinger in :gh:" -"`81620`.)" +"Add :func:`random.binomialvariate`. (Contributed by Raymond Hettinger " +"in :gh:`81620`.)" msgstr "" #: whatsnew/3.12.rst:835 @@ -1230,24 +1238,26 @@ msgstr "" #: whatsnew/3.12.rst:873 msgid "" -"Add the :attr:`sqlite3.Connection.autocommit` attribute to :class:`sqlite3." -"Connection` and the *autocommit* parameter to :func:`sqlite3.connect` to " -"control :pep:`249`-compliant :ref:`transaction handling `. (Contributed by Erlend E. Aasland in :gh:`83638`.)" +"Add the :attr:`sqlite3.Connection.autocommit` attribute " +"to :class:`sqlite3.Connection` and the *autocommit* parameter " +"to :func:`sqlite3.connect` to control :pep:`249`-compliant :ref:`transaction " +"handling `. (Contributed by Erlend " +"E. Aasland in :gh:`83638`.)" msgstr "" #: whatsnew/3.12.rst:880 msgid "" -"Add *entrypoint* keyword-only parameter to :meth:`sqlite3.Connection." -"load_extension`, for overriding the SQLite extension entry point. " -"(Contributed by Erlend E. Aasland in :gh:`103015`.)" +"Add *entrypoint* keyword-only parameter " +"to :meth:`sqlite3.Connection.load_extension`, for overriding the SQLite " +"extension entry point. (Contributed by Erlend E. Aasland in :gh:`103015`.)" msgstr "" #: whatsnew/3.12.rst:885 msgid "" -"Add :meth:`sqlite3.Connection.getconfig` and :meth:`sqlite3.Connection." -"setconfig` to :class:`sqlite3.Connection` to make configuration changes to a " -"database connection. (Contributed by Erlend E. Aasland in :gh:`103489`.)" +"Add :meth:`sqlite3.Connection.getconfig` " +"and :meth:`sqlite3.Connection.setconfig` to :class:`sqlite3.Connection` to " +"make configuration changes to a database connection. (Contributed by Erlend " +"E. Aasland in :gh:`103489`.)" msgstr "" #: whatsnew/3.12.rst:891 @@ -1268,27 +1278,28 @@ msgstr "" #: whatsnew/3.12.rst:900 msgid "" "Add the :mod:`sys.monitoring` namespace to expose the new :ref:`PEP 669 " -"` monitoring API. (Contributed by Mark Shannon in :gh:" -"`103082`.)" +"` monitoring API. (Contributed by Mark Shannon " +"in :gh:`103082`.)" msgstr "" #: whatsnew/3.12.rst:904 msgid "" -"Add :func:`sys.activate_stack_trampoline` and :func:`sys." -"deactivate_stack_trampoline` for activating and deactivating stack profiler " -"trampolines, and :func:`sys.is_stack_trampoline_active` for querying if " -"stack profiler trampolines are active. (Contributed by Pablo Galindo and " -"Christian Heimes with contributions from Gregory P. Smith [Google] and Mark " -"Shannon in :gh:`96123`.)" +"Add :func:`sys.activate_stack_trampoline` " +"and :func:`sys.deactivate_stack_trampoline` for activating and deactivating " +"stack profiler trampolines, and :func:`sys.is_stack_trampoline_active` for " +"querying if stack profiler trampolines are active. (Contributed by Pablo " +"Galindo and Christian Heimes with contributions from Gregory P. Smith " +"[Google] and Mark Shannon in :gh:`96123`.)" msgstr "" #: whatsnew/3.12.rst:913 msgid "" "Add :data:`sys.last_exc` which holds the last unhandled exception that was " "raised (for post-mortem debugging use cases). Deprecate the three fields " -"that have the same information in its legacy form: :data:`sys.last_type`, :" -"data:`sys.last_value` and :data:`sys.last_traceback`. (Contributed by Irit " -"Katriel in :gh:`102778`.)" +"that have the same information in its legacy " +"form: :data:`sys.last_type`, :data:`sys.last_value` " +"and :data:`sys.last_traceback`. (Contributed by Irit Katriel " +"in :gh:`102778`.)" msgstr "" #: whatsnew/3.12.rst:1736 @@ -1324,10 +1335,10 @@ msgstr "" #: whatsnew/3.12.rst:935 msgid "" -"As of 3.12.4 on Windows, the default mode ``0o700`` used by :func:`tempfile." -"mkdtemp` now limits access to the new directory due to changes to :func:`os." -"mkdir`. This is a mitigation for :cve:`2024-4030`. (Contributed by Steve " -"Dower in :gh:`118486`.)" +"As of 3.12.4 on Windows, the default mode ``0o700`` used " +"by :func:`tempfile.mkdtemp` now limits access to the new directory due to " +"changes to :func:`os.mkdir`. This is a mitigation for :cve:`2024-4030`. " +"(Contributed by Steve Dower in :gh:`118486`.)" msgstr "" #: whatsnew/3.12.rst:941 @@ -1336,10 +1347,10 @@ msgstr "" #: whatsnew/3.12.rst:943 msgid "" -"Add :func:`threading.settrace_all_threads` and :func:`threading." -"setprofile_all_threads` that allow to set tracing and profiling functions in " -"all running threads in addition to the calling one. (Contributed by Pablo " -"Galindo in :gh:`93503`.)" +"Add :func:`threading.settrace_all_threads` " +"and :func:`threading.setprofile_all_threads` that allow to set tracing and " +"profiling functions in all running threads in addition to the calling one. " +"(Contributed by Pablo Galindo in :gh:`93503`.)" msgstr "" #: whatsnew/3.12.rst:949 @@ -1363,9 +1374,9 @@ msgstr "" #: whatsnew/3.12.rst:962 msgid "" "The :mod:`tokenize` module includes the changes introduced in :pep:`701`. " -"(Contributed by Marta Gómez Macías and Pablo Galindo in :gh:`102856`.) See :" -"ref:`whatsnew312-porting-to-python312` for more information on the changes " -"to the :mod:`tokenize` module." +"(Contributed by Marta Gómez Macías and Pablo Galindo in :gh:`102856`.) " +"See :ref:`whatsnew312-porting-to-python312` for more information on the " +"changes to the :mod:`tokenize` module." msgstr "" #: whatsnew/3.12.rst:968 @@ -1374,9 +1385,9 @@ msgstr "" #: whatsnew/3.12.rst:970 msgid "" -"Add :func:`types.get_original_bases` to allow for further introspection of :" -"ref:`user-defined-generics` when subclassed. (Contributed by James Hilton-" -"Balfe and Alex Waygood in :gh:`101827`.)" +"Add :func:`types.get_original_bases` to allow for further introspection " +"of :ref:`user-defined-generics` when subclassed. (Contributed by James " +"Hilton-Balfe and Alex Waygood in :gh:`101827`.)" msgstr "" #: whatsnew/3.12.rst:977 @@ -1385,15 +1396,16 @@ msgstr "" #: whatsnew/3.12.rst:979 msgid "" -":func:`isinstance` checks against :func:`runtime-checkable protocols ` now use :func:`inspect.getattr_static` rather than :func:" -"`hasattr` to lookup whether attributes exist. This means that descriptors " -"and :meth:`~object.__getattr__` methods are no longer unexpectedly evaluated " -"during ``isinstance()`` checks against runtime-checkable protocols. However, " -"it may also mean that some objects which used to be considered instances of " -"a runtime-checkable protocol may no longer be considered instances of that " -"protocol on Python 3.12+, and vice versa. Most users are unlikely to be " -"affected by this change. (Contributed by Alex Waygood in :gh:`102433`.)" +":func:`isinstance` checks against :func:`runtime-checkable protocols " +"` now use :func:`inspect.getattr_static` rather " +"than :func:`hasattr` to lookup whether attributes exist. This means that " +"descriptors and :meth:`~object.__getattr__` methods are no longer " +"unexpectedly evaluated during ``isinstance()`` checks against runtime-" +"checkable protocols. However, it may also mean that some objects which used " +"to be considered instances of a runtime-checkable protocol may no longer be " +"considered instances of that protocol on Python 3.12+, and vice versa. Most " +"users are unlikely to be affected by this change. (Contributed by Alex " +"Waygood in :gh:`102433`.)" msgstr "" #: whatsnew/3.12.rst:990 @@ -1438,8 +1450,8 @@ msgid "" "Most ``isinstance()`` checks against protocols with only a few members " "should be at least 2x faster than in 3.11, and some may be 20x faster or " "more. However, ``isinstance()`` checks against protocols with many members " -"may be slower than in Python 3.11. (Contributed by Alex Waygood in :gh:" -"`74690` and :gh:`103193`.)" +"may be slower than in Python 3.11. (Contributed by Alex Waygood " +"in :gh:`74690` and :gh:`103193`.)" msgstr "" #: whatsnew/3.12.rst:1023 @@ -1525,8 +1537,8 @@ msgstr "" #: whatsnew/3.12.rst:1075 msgid "" -"Speed up the regular expression substitution (functions :func:`re.sub` and :" -"func:`re.subn` and corresponding :class:`!re.Pattern` methods) for " +"Speed up the regular expression substitution (functions :func:`re.sub` " +"and :func:`re.subn` and corresponding :class:`!re.Pattern` methods) for " "replacement strings containing group references by 2--3 times. (Contributed " "by Serhiy Storchaka in :gh:`91524`.)" msgstr "" @@ -1540,16 +1552,16 @@ msgstr "" #: whatsnew/3.12.rst:1083 msgid "" "The :func:`tokenize.tokenize` and :func:`tokenize.generate_tokens` functions " -"are up to 64% faster as a side effect of the changes required to cover :pep:" -"`701` in the :mod:`tokenize` module. (Contributed by Marta Gómez Macías and " -"Pablo Galindo in :gh:`102856`.)" +"are up to 64% faster as a side effect of the changes required to " +"cover :pep:`701` in the :mod:`tokenize` module. (Contributed by Marta Gómez " +"Macías and Pablo Galindo in :gh:`102856`.)" msgstr "" #: whatsnew/3.12.rst:1088 msgid "" -"Speed up :func:`super` method calls and attribute loads via the new :opcode:" -"`LOAD_SUPER_ATTR` instruction. (Contributed by Carl Meyer and Vladimir " -"Matveev in :gh:`103497`.)" +"Speed up :func:`super` method calls and attribute loads via the " +"new :opcode:`LOAD_SUPER_ATTR` instruction. (Contributed by Carl Meyer and " +"Vladimir Matveev in :gh:`103497`.)" msgstr "" #: whatsnew/3.12.rst:1094 @@ -1558,23 +1570,23 @@ msgstr "" #: whatsnew/3.12.rst:1096 msgid "" -"Remove the :opcode:`!LOAD_METHOD` instruction. It has been merged into :" -"opcode:`LOAD_ATTR`. :opcode:`LOAD_ATTR` will now behave like the old :opcode:" -"`!LOAD_METHOD` instruction if the low bit of its oparg is set. (Contributed " -"by Ken Jin in :gh:`93429`.)" +"Remove the :opcode:`!LOAD_METHOD` instruction. It has been merged " +"into :opcode:`LOAD_ATTR`. :opcode:`LOAD_ATTR` will now behave like the " +"old :opcode:`!LOAD_METHOD` instruction if the low bit of its oparg is set. " +"(Contributed by Ken Jin in :gh:`93429`.)" msgstr "" #: whatsnew/3.12.rst:1101 msgid "" "Remove the :opcode:`!JUMP_IF_FALSE_OR_POP` and :opcode:`!" -"JUMP_IF_TRUE_OR_POP` instructions. (Contributed by Irit Katriel in :gh:" -"`102859`.)" +"JUMP_IF_TRUE_OR_POP` instructions. (Contributed by Irit Katriel " +"in :gh:`102859`.)" msgstr "" #: whatsnew/3.12.rst:1104 msgid "" -"Remove the :opcode:`!PRECALL` instruction. (Contributed by Mark Shannon in :" -"gh:`92925`.)" +"Remove the :opcode:`!PRECALL` instruction. (Contributed by Mark Shannon " +"in :gh:`92925`.)" msgstr "" #: whatsnew/3.12.rst:1107 @@ -1603,8 +1615,8 @@ msgstr "" #: whatsnew/3.12.rst:1119 msgid "" -"Add the :opcode:`!END_SEND` instruction. (Contributed by Mark Shannon in :gh:" -"`103082`.)" +"Add the :opcode:`!END_SEND` instruction. (Contributed by Mark Shannon " +"in :gh:`103082`.)" msgstr "" #: whatsnew/3.12.rst:1122 @@ -1621,11 +1633,12 @@ msgstr "" #: whatsnew/3.12.rst:1128 msgid "" -"Add the :opcode:`LOAD_FROM_DICT_OR_DEREF`, :opcode:" -"`LOAD_FROM_DICT_OR_GLOBALS`, and :opcode:`LOAD_LOCALS` opcodes as part of " -"the implementation of :pep:`695`. Remove the :opcode:`!LOAD_CLASSDEREF` " -"opcode, which can be replaced with :opcode:`LOAD_LOCALS` plus :opcode:" -"`LOAD_FROM_DICT_OR_DEREF`. (Contributed by Jelle Zijlstra in :gh:`103764`.)" +"Add " +"the :opcode:`LOAD_FROM_DICT_OR_DEREF`, :opcode:`LOAD_FROM_DICT_OR_GLOBALS`, " +"and :opcode:`LOAD_LOCALS` opcodes as part of the implementation " +"of :pep:`695`. Remove the :opcode:`!LOAD_CLASSDEREF` opcode, which can be " +"replaced with :opcode:`LOAD_LOCALS` plus :opcode:`LOAD_FROM_DICT_OR_DEREF`. " +"(Contributed by Jelle Zijlstra in :gh:`103764`.)" msgstr "" #: whatsnew/3.12.rst:1134 @@ -1636,8 +1649,8 @@ msgstr "" #: whatsnew/3.12.rst:1137 msgid "" -"Add the :opcode:`RETURN_CONST` instruction. (Contributed by Wenyang Wang in :" -"gh:`101632`.)" +"Add the :opcode:`RETURN_CONST` instruction. (Contributed by Wenyang Wang " +"in :gh:`101632`.)" msgstr "" #: whatsnew/3.12.rst:1140 @@ -1699,8 +1712,8 @@ msgstr "" #: whatsnew/3.12.rst:1171 deprecations/pending-removal-in-3.14.rst:26 msgid "" -"Use :class:`ast.Constant` instead. (Contributed by Serhiy Storchaka in :gh:" -"`90953`.)" +"Use :class:`ast.Constant` instead. (Contributed by Serhiy Storchaka " +"in :gh:`90953`.)" msgstr "" #: whatsnew/3.12.rst:1174 deprecations/pending-removal-in-3.14.rst:29 @@ -1709,18 +1722,18 @@ msgstr "" #: whatsnew/3.12.rst:1176 msgid "" -"The child watcher classes :class:`asyncio.MultiLoopChildWatcher`, :class:" -"`asyncio.FastChildWatcher`, :class:`asyncio.AbstractChildWatcher` and :class:" -"`asyncio.SafeChildWatcher` are deprecated and will be removed in Python " -"3.14. (Contributed by Kumar Aditya in :gh:`94597`.)" +"The child watcher " +"classes :class:`asyncio.MultiLoopChildWatcher`, :class:`asyncio.FastChildWatcher`, :class:`asyncio.AbstractChildWatcher` " +"and :class:`asyncio.SafeChildWatcher` are deprecated and will be removed in " +"Python 3.14. (Contributed by Kumar Aditya in :gh:`94597`.)" msgstr "" #: whatsnew/3.12.rst:1182 deprecations/pending-removal-in-3.14.rst:37 msgid "" -":func:`asyncio.set_child_watcher`, :func:`asyncio.get_child_watcher`, :meth:" -"`asyncio.AbstractEventLoopPolicy.set_child_watcher` and :meth:`asyncio." -"AbstractEventLoopPolicy.get_child_watcher` are deprecated and will be " -"removed in Python 3.14. (Contributed by Kumar Aditya in :gh:`94597`.)" +":func:`asyncio.set_child_watcher`, :func:`asyncio.get_child_watcher`, :meth:`asyncio.AbstractEventLoopPolicy.set_child_watcher` " +"and :meth:`asyncio.AbstractEventLoopPolicy.get_child_watcher` are deprecated " +"and will be removed in Python 3.14. (Contributed by Kumar Aditya " +"in :gh:`94597`.)" msgstr "" #: whatsnew/3.12.rst:1188 deprecations/pending-removal-in-3.14.rst:43 @@ -1734,32 +1747,36 @@ msgstr "" #: whatsnew/3.12.rst:1193 deprecations/pending-removal-in-future.rst:41 msgid "" ":mod:`calendar`: ``calendar.January`` and ``calendar.February`` constants " -"are deprecated and replaced by :data:`calendar.JANUARY` and :data:`calendar." -"FEBRUARY`. (Contributed by Prince Roshan in :gh:`103636`.)" +"are deprecated and replaced by :data:`calendar.JANUARY` " +"and :data:`calendar.FEBRUARY`. (Contributed by Prince Roshan " +"in :gh:`103636`.)" msgstr "" #: whatsnew/3.12.rst:1197 msgid "" ":mod:`collections.abc`: Deprecated :class:`collections.abc.ByteString`. " "Prefer :class:`Sequence` or :class:`collections.abc.Buffer`. For use in " -"typing, prefer a union, like ``bytes | bytearray``, or :class:`collections." -"abc.Buffer`. (Contributed by Shantanu Jain in :gh:`91896`.)" +"typing, prefer a union, like ``bytes | bytearray``, " +"or :class:`collections.abc.Buffer`. (Contributed by Shantanu Jain " +"in :gh:`91896`.)" msgstr "" #: whatsnew/3.12.rst:1202 msgid "" -":mod:`datetime`: :class:`datetime.datetime`'s :meth:`~datetime.datetime." -"utcnow` and :meth:`~datetime.datetime.utcfromtimestamp` are deprecated and " -"will be removed in a future version. Instead, use timezone-aware objects to " -"represent datetimes in UTC: respectively, call :meth:`~datetime.datetime." -"now` and :meth:`~datetime.datetime.fromtimestamp` with the *tz* parameter " -"set to :const:`datetime.UTC`. (Contributed by Paul Ganssle in :gh:`103857`.)" +":mod:`datetime`: :class:`datetime.datetime`'s :meth:`~datetime.datetime.utcnow` " +"and :meth:`~datetime.datetime.utcfromtimestamp` are deprecated and will be " +"removed in a future version. Instead, use timezone-aware objects to " +"represent datetimes in UTC: respectively, " +"call :meth:`~datetime.datetime.now` " +"and :meth:`~datetime.datetime.fromtimestamp` with the *tz* parameter set " +"to :const:`datetime.UTC`. (Contributed by Paul Ganssle in :gh:`103857`.)" msgstr "" #: whatsnew/3.12.rst:1210 msgid "" -":mod:`email`: Deprecate the *isdst* parameter in :func:`email.utils." -"localtime`. (Contributed by Alan Williams in :gh:`72346`.)" +":mod:`email`: Deprecate the *isdst* parameter " +"in :func:`email.utils.localtime`. (Contributed by Alan Williams " +"in :gh:`72346`.)" msgstr "" #: whatsnew/3.12.rst:1213 @@ -1801,8 +1818,8 @@ msgid "" ":mod:`itertools`: Deprecate the support for copy, deepcopy, and pickle " "operations, which is undocumented, inefficient, historically buggy, and " "inconsistent. This will be removed in 3.14 for a significant reduction in " -"code volume and maintenance burden. (Contributed by Raymond Hettinger in :gh:" -"`101588`.)" +"code volume and maintenance burden. (Contributed by Raymond Hettinger " +"in :gh:`101588`.)" msgstr "" #: whatsnew/3.12.rst:1233 @@ -1811,17 +1828,19 @@ msgid "" "start method will change to a safer one on Linux, BSDs, and other non-macOS " "POSIX platforms where ``'fork'`` is currently the default (:gh:`84559`). " "Adding a runtime warning about this was deemed too disruptive as the " -"majority of code is not expected to care. Use the :func:`~multiprocessing." -"get_context` or :func:`~multiprocessing.set_start_method` APIs to explicitly " -"specify when your code *requires* ``'fork'``. See :ref:`contexts and start " -"methods `." +"majority of code is not expected to care. Use " +"the :func:`~multiprocessing.get_context` " +"or :func:`~multiprocessing.set_start_method` APIs to explicitly specify when " +"your code *requires* ``'fork'``. See :ref:`contexts and start methods " +"`." msgstr "" #: whatsnew/3.12.rst:1243 msgid "" ":mod:`pkgutil`: :func:`pkgutil.find_loader` and :func:`pkgutil.get_loader` " -"are deprecated and will be removed in Python 3.14; use :func:`importlib.util." -"find_spec` instead. (Contributed by Nikita Sobolev in :gh:`97850`.)" +"are deprecated and will be removed in Python 3.14; " +"use :func:`importlib.util.find_spec` instead. (Contributed by Nikita Sobolev " +"in :gh:`97850`.)" msgstr "" #: whatsnew/3.12.rst:1248 @@ -1847,30 +1866,31 @@ msgstr "" #: whatsnew/3.12.rst:1261 msgid "" -"On POSIX platforms, :func:`os.fork` can now raise a :exc:" -"`DeprecationWarning` when it can detect being called from a multithreaded " -"process. There has always been a fundamental incompatibility with the POSIX " -"platform when doing so. Even if such code *appeared* to work. We added the " -"warning to raise awareness as issues encountered by code doing this are " -"becoming more frequent. See the :func:`os.fork` documentation for more " -"details along with `this discussion on fork being incompatible with threads " -"`_ for *why* we're now surfacing this longstanding " +"On POSIX platforms, :func:`os.fork` can now raise " +"a :exc:`DeprecationWarning` when it can detect being called from a " +"multithreaded process. There has always been a fundamental incompatibility " +"with the POSIX platform when doing so. Even if such code *appeared* to work. " +"We added the warning to raise awareness as issues encountered by code doing " +"this are becoming more frequent. See the :func:`os.fork` documentation for " +"more details along with `this discussion on fork being incompatible with " +"threads `_ for *why* we're now surfacing this longstanding " "platform compatibility problem to developers." msgstr "" #: whatsnew/3.12.rst:1271 msgid "" -"When this warning appears due to usage of :mod:`multiprocessing` or :mod:" -"`concurrent.futures` the fix is to use a different :mod:`multiprocessing` " -"start method such as ``\"spawn\"`` or ``\"forkserver\"``." +"When this warning appears due to usage of :mod:`multiprocessing` " +"or :mod:`concurrent.futures` the fix is to use a " +"different :mod:`multiprocessing` start method such as ``\"spawn\"`` or " +"``\"forkserver\"``." msgstr "" #: whatsnew/3.12.rst:1275 msgid "" ":mod:`shutil`: The *onerror* argument of :func:`shutil.rmtree` is " -"deprecated; use *onexc* instead. (Contributed by Irit Katriel in :gh:" -"`102828`.)" +"deprecated; use *onexc* instead. (Contributed by Irit Katriel " +"in :gh:`102828`.)" msgstr "" #: whatsnew/3.12.rst:1278 deprecations/pending-removal-in-3.14.rst:101 @@ -1896,9 +1916,10 @@ msgstr "" #: whatsnew/3.12.rst:1293 msgid "" -":mod:`sys`: The :data:`sys.last_type`, :data:`sys.last_value` and :data:`sys." -"last_traceback` fields are deprecated. Use :data:`sys.last_exc` instead. " -"(Contributed by Irit Katriel in :gh:`102778`.)" +":mod:`sys`: The :data:`sys.last_type`, :data:`sys.last_value` " +"and :data:`sys.last_traceback` fields are deprecated. " +"Use :data:`sys.last_exc` instead. (Contributed by Irit Katriel " +"in :gh:`102778`.)" msgstr "" #: whatsnew/3.12.rst:1297 @@ -1914,16 +1935,16 @@ msgstr "" #: whatsnew/3.12.rst:1303 msgid "" -":class:`typing.Hashable` and :class:`typing.Sized`, aliases for :class:" -"`collections.abc.Hashable` and :class:`collections.abc.Sized` respectively, " -"are deprecated. (:gh:`94309`.)" +":class:`typing.Hashable` and :class:`typing.Sized`, aliases " +"for :class:`collections.abc.Hashable` and :class:`collections.abc.Sized` " +"respectively, are deprecated. (:gh:`94309`.)" msgstr "" #: whatsnew/3.12.rst:1307 msgid "" -":class:`typing.ByteString`, deprecated since Python 3.9, now causes a :exc:" -"`DeprecationWarning` to be emitted when it is used. (Contributed by Alex " -"Waygood in :gh:`91896`.)" +":class:`typing.ByteString`, deprecated since Python 3.9, now causes " +"a :exc:`DeprecationWarning` to be emitted when it is used. (Contributed by " +"Alex Waygood in :gh:`91896`.)" msgstr "" #: whatsnew/3.12.rst:1311 @@ -1937,26 +1958,26 @@ msgstr "" #: whatsnew/3.12.rst:1317 msgid "" "The 3-arg signatures (type, value, traceback) of :meth:`coroutine throw() " -"`, :meth:`generator throw() ` and :meth:" -"`async generator throw() ` are deprecated and may be removed in " -"a future version of Python. Use the single-arg versions of these functions " -"instead. (Contributed by Ofey Chan in :gh:`89874`.)" +"`, :meth:`generator throw() ` " +"and :meth:`async generator throw() ` are deprecated and may be " +"removed in a future version of Python. Use the single-arg versions of these " +"functions instead. (Contributed by Ofey Chan in :gh:`89874`.)" msgstr "" #: whatsnew/3.12.rst:1323 msgid "" ":exc:`DeprecationWarning` is now raised when :attr:`~module.__package__` on " -"a module differs from :attr:`__spec__.parent ` (previously it was :exc:`ImportWarning`). (Contributed by Brett " -"Cannon in :gh:`65961`.)" +"a module differs from :attr:`__spec__.parent " +"` (previously it " +"was :exc:`ImportWarning`). (Contributed by Brett Cannon in :gh:`65961`.)" msgstr "" #: whatsnew/3.12.rst:1329 msgid "" "Setting :attr:`~module.__package__` or :attr:`~module.__cached__` on a " "module is deprecated, and will cease to be set or taken into consideration " -"by the import system in Python 3.14. (Contributed by Brett Cannon in :gh:" -"`65961`.)" +"by the import system in Python 3.14. (Contributed by Brett Cannon " +"in :gh:`65961`.)" msgstr "" #: whatsnew/3.12.rst:1333 @@ -1971,9 +1992,9 @@ msgstr "" #: whatsnew/3.12.rst:1339 msgid "" "Accessing :attr:`~codeobject.co_lnotab` on code objects was deprecated in " -"Python 3.10 via :pep:`626`, but it only got a proper :exc:" -"`DeprecationWarning` in 3.12, therefore it will be removed in 3.14. " -"(Contributed by Nikita Sobolev in :gh:`101866`.)" +"Python 3.10 via :pep:`626`, but it only got a " +"proper :exc:`DeprecationWarning` in 3.12, therefore it will be removed in " +"3.14. (Contributed by Nikita Sobolev in :gh:`101866`.)" msgstr "" #: deprecations/pending-removal-in-3.13.rst:2 @@ -2158,10 +2179,10 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:6 msgid "" -"Setting :attr:`~module.__loader__` on a module while failing to set :attr:" -"`__spec__.loader ` is deprecated. In " -"Python 3.14, :attr:`!__loader__` will cease to be set or taken into " -"consideration by the import system or the standard library." +"Setting :attr:`~module.__loader__` on a module while failing to " +"set :attr:`__spec__.loader ` is " +"deprecated. In Python 3.14, :attr:`!__loader__` will cease to be set or " +"taken into consideration by the import system or the standard library." msgstr "" #: deprecations/pending-removal-in-3.14.rst:16 @@ -2173,9 +2194,9 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:31 msgid "" -"The child watcher classes :class:`~asyncio.MultiLoopChildWatcher`, :class:" -"`~asyncio.FastChildWatcher`, :class:`~asyncio.AbstractChildWatcher` and :" -"class:`~asyncio.SafeChildWatcher` are deprecated and will be removed in " +"The child watcher " +"classes :class:`~asyncio.MultiLoopChildWatcher`, :class:`~asyncio.FastChildWatcher`, :class:`~asyncio.AbstractChildWatcher` " +"and :class:`~asyncio.SafeChildWatcher` are deprecated and will be removed in " "Python 3.14. (Contributed by Kumar Aditya in :gh:`94597`.)" msgstr "" @@ -2183,14 +2204,16 @@ msgstr "" msgid "" ":mod:`collections.abc`: Deprecated :class:`~collections.abc.ByteString`. " "Prefer :class:`!Sequence` or :class:`~collections.abc.Buffer`. For use in " -"typing, prefer a union, like ``bytes | bytearray``, or :class:`collections." -"abc.Buffer`. (Contributed by Shantanu Jain in :gh:`91896`.)" +"typing, prefer a union, like ``bytes | bytearray``, " +"or :class:`collections.abc.Buffer`. (Contributed by Shantanu Jain " +"in :gh:`91896`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:54 msgid "" -":mod:`email`: Deprecated the *isdst* parameter in :func:`email.utils." -"localtime`. (Contributed by Alan Williams in :gh:`72346`.)" +":mod:`email`: Deprecated the *isdst* parameter " +"in :func:`email.utils.localtime`. (Contributed by Alan Williams " +"in :gh:`72346`.)" msgstr "" #: deprecations/pending-removal-in-3.14.rst:57 @@ -2217,15 +2240,16 @@ msgid "" "on Linux, BSDs, and other non-macOS POSIX platforms where ``'fork'`` is " "currently the default (:gh:`84559`). Adding a runtime warning about this was " "deemed too disruptive as the majority of code is not expected to care. Use " -"the :func:`~multiprocessing.get_context` or :func:`~multiprocessing." -"set_start_method` APIs to explicitly specify when your code *requires* " -"``'fork'``. See :ref:`multiprocessing-start-methods`." +"the :func:`~multiprocessing.get_context` " +"or :func:`~multiprocessing.set_start_method` APIs to explicitly specify when " +"your code *requires* ``'fork'``. See :ref:`multiprocessing-start-methods`." msgstr "" #: deprecations/pending-removal-in-3.14.rst:87 msgid "" -":mod:`pathlib`: :meth:`~pathlib.PurePath.is_relative_to` and :meth:`~pathlib." -"PurePath.relative_to`: passing additional arguments is deprecated." +":mod:`pathlib`: :meth:`~pathlib.PurePath.is_relative_to` " +"and :meth:`~pathlib.PurePath.relative_to`: passing additional arguments is " +"deprecated." msgstr "" #: deprecations/pending-removal-in-3.14.rst:91 @@ -2253,15 +2277,15 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:105 msgid "" -":meth:`~sqlite3.Cursor.execute` and :meth:`~sqlite3.Cursor.executemany` if :" -"ref:`named placeholders ` are used and *parameters* is " -"a sequence instead of a :class:`dict`." +":meth:`~sqlite3.Cursor.execute` and :meth:`~sqlite3.Cursor.executemany` " +"if :ref:`named placeholders ` are used and " +"*parameters* is a sequence instead of a :class:`dict`." msgstr "" #: deprecations/pending-removal-in-3.14.rst:109 msgid "" -"date and datetime adapter, date and timestamp converter: see the :mod:" -"`sqlite3` documentation for suggested replacement recipes." +"date and datetime adapter, date and timestamp converter: see " +"the :mod:`sqlite3` documentation for suggested replacement recipes." msgstr "" #: deprecations/pending-removal-in-3.14.rst:112 @@ -2281,8 +2305,8 @@ msgstr "" #: deprecations/pending-removal-in-3.14.rst:122 msgid "" ":mod:`urllib`: :class:`!urllib.parse.Quoter` is deprecated: it was not " -"intended to be a public API. (Contributed by Gregory P. Smith in :gh:" -"`88168`.)" +"intended to be a public API. (Contributed by Gregory P. Smith " +"in :gh:`88168`.)" msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:2 @@ -2302,16 +2326,17 @@ msgstr "" msgid "" ":class:`locale`: :func:`locale.getdefaultlocale` was deprecated in Python " "3.11 and originally planned for removal in Python 3.13 (:gh:`90817`), but " -"removal has been postponed to Python 3.15. Use :func:`locale.setlocale`, :" -"func:`locale.getencoding` and :func:`locale.getlocale` instead. (Contributed " -"by Hugo van Kemenade in :gh:`111187`.)" +"removal has been postponed to Python 3.15. " +"Use :func:`locale.setlocale`, :func:`locale.getencoding` " +"and :func:`locale.getlocale` instead. (Contributed by Hugo van Kemenade " +"in :gh:`111187`.)" msgstr "" #: deprecations/pending-removal-in-3.15.rst:16 msgid "" ":mod:`pathlib`: :meth:`pathlib.PurePath.is_reserved` is deprecated and " -"scheduled for removal in Python 3.15. From Python 3.13 onwards, use ``os." -"path.isreserved`` to detect reserved paths on Windows." +"scheduled for removal in Python 3.15. From Python 3.13 onwards, use " +"``os.path.isreserved`` to detect reserved paths on Windows." msgstr "" #: deprecations/pending-removal-in-3.15.rst:21 @@ -2355,20 +2380,21 @@ msgstr "" #: deprecations/pending-removal-in-3.15.rst:47 msgid "" -":class:`typing.TypedDict`: When using the functional syntax to create a :" -"class:`!TypedDict` class, failing to pass a value to the *fields* parameter " -"(``TD = TypedDict(\"TD\")``) is deprecated. Passing ``None`` to the *fields* " -"parameter (``TD = TypedDict(\"TD\", None)``) is also deprecated. Both will " -"be disallowed in Python 3.15. To create a :class:`!TypedDict` class with 0 " -"fields, use ``class TD(TypedDict): pass`` or ``TD = TypedDict(\"TD\", {})``." +":class:`typing.TypedDict`: When using the functional syntax to create " +"a :class:`!TypedDict` class, failing to pass a value to the *fields* " +"parameter (``TD = TypedDict(\"TD\")``) is deprecated. Passing ``None`` to " +"the *fields* parameter (``TD = TypedDict(\"TD\", None)``) is also " +"deprecated. Both will be disallowed in Python 3.15. To create a :class:`!" +"TypedDict` class with 0 fields, use ``class TD(TypedDict): pass`` or ``TD = " +"TypedDict(\"TD\", {})``." msgstr "" #: deprecations/pending-removal-in-3.15.rst:54 msgid "" ":mod:`wave`: Deprecate the ``getmark()``, ``setmark()`` and ``getmarkers()`` " "methods of the :class:`wave.Wave_read` and :class:`wave.Wave_write` classes. " -"They will be removed in Python 3.15. (Contributed by Victor Stinner in :gh:" -"`105096`.)" +"They will be removed in Python 3.15. (Contributed by Victor Stinner " +"in :gh:`105096`.)" msgstr "" #: deprecations/pending-removal-in-3.16.rst:2 @@ -2433,10 +2459,10 @@ msgid "" "for example ``0in x``, ``1or x``, ``0if 1else 2``. It allows confusing and " "ambiguous expressions like ``[0x1for x in y]`` (which can be interpreted as " "``[0x1 for x in y]`` or ``[0x1f or x in y]``). A syntax warning is raised " -"if the numeric literal is immediately followed by one of keywords :keyword:" -"`and`, :keyword:`else`, :keyword:`for`, :keyword:`if`, :keyword:`in`, :" -"keyword:`is` and :keyword:`or`. In a future release it will be changed to a " -"syntax error. (:gh:`87999`)" +"if the numeric literal is immediately followed by one of " +"keywords :keyword:`and`, :keyword:`else`, :keyword:`for`, :keyword:`if`, :keyword:`in`, :keyword:`is` " +"and :keyword:`or`. In a future release it will be changed to a syntax " +"error. (:gh:`87999`)" msgstr "" #: deprecations/pending-removal-in-future.rst:26 @@ -2448,16 +2474,16 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:29 msgid "" -"Support for ``__float__()`` method returning a strict subclass of :class:" -"`float`: these methods will be required to return an instance of :class:" -"`float`." +"Support for ``__float__()`` method returning a strict subclass " +"of :class:`float`: these methods will be required to return an instance " +"of :class:`float`." msgstr "" #: deprecations/pending-removal-in-future.rst:32 msgid "" -"Support for ``__complex__()`` method returning a strict subclass of :class:" -"`complex`: these methods will be required to return an instance of :class:" -"`complex`." +"Support for ``__complex__()`` method returning a strict subclass " +"of :class:`complex`: these methods will be required to return an instance " +"of :class:`complex`." msgstr "" #: deprecations/pending-removal-in-future.rst:35 @@ -2466,10 +2492,10 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:36 msgid "" -"Passing a complex number as the *real* or *imag* argument in the :func:" -"`complex` constructor is now deprecated; it should only be passed as a " -"single positional argument. (Contributed by Serhiy Storchaka in :gh:" -"`109218`.)" +"Passing a complex number as the *real* or *imag* argument in " +"the :func:`complex` constructor is now deprecated; it should only be passed " +"as a single positional argument. (Contributed by Serhiy Storchaka " +"in :gh:`109218`.)" msgstr "" #: deprecations/pending-removal-in-future.rst:46 @@ -2484,14 +2510,14 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:51 msgid "" -":meth:`~datetime.datetime.utcnow`: use ``datetime.datetime.now(tz=datetime." -"UTC)``." +":meth:`~datetime.datetime.utcnow`: use " +"``datetime.datetime.now(tz=datetime.UTC)``." msgstr "" #: deprecations/pending-removal-in-future.rst:53 msgid "" -":meth:`~datetime.datetime.utcfromtimestamp`: use ``datetime.datetime." -"fromtimestamp(timestamp, tz=datetime.UTC)``." +":meth:`~datetime.datetime.utcfromtimestamp`: use " +"``datetime.datetime.fromtimestamp(timestamp, tz=datetime.UTC)``." msgstr "" #: deprecations/pending-removal-in-future.rst:56 @@ -2571,8 +2597,8 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:92 msgid "" -":class:`ssl.SSLContext`: :meth:`~ssl.SSLContext.set_npn_protocols` and :meth:" -"`!selected_npn_protocol` are deprecated: use ALPN instead." +":class:`ssl.SSLContext`: :meth:`~ssl.SSLContext.set_npn_protocols` " +"and :meth:`!selected_npn_protocol` are deprecated: use ALPN instead." msgstr "" #: deprecations/pending-removal-in-future.rst:95 @@ -2627,8 +2653,8 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:111 msgid "" -":meth:`!threading.Condition.notifyAll`: use :meth:`~threading.Condition." -"notify_all`." +":meth:`!threading.Condition.notifyAll`: " +"use :meth:`~threading.Condition.notify_all`." msgstr "" #: deprecations/pending-removal-in-future.rst:112 @@ -2637,14 +2663,14 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:113 msgid "" -":meth:`!threading.Thread.isDaemon`, :meth:`threading.Thread.setDaemon`: use :" -"attr:`threading.Thread.daemon` attribute." +":meth:`!threading.Thread.isDaemon`, :meth:`threading.Thread.setDaemon`: " +"use :attr:`threading.Thread.daemon` attribute." msgstr "" #: deprecations/pending-removal-in-future.rst:115 msgid "" -":meth:`!threading.Thread.getName`, :meth:`threading.Thread.setName`: use :" -"attr:`threading.Thread.name` attribute." +":meth:`!threading.Thread.getName`, :meth:`threading.Thread.setName`: " +"use :attr:`threading.Thread.name` attribute." msgstr "" #: deprecations/pending-removal-in-future.rst:117 @@ -2717,9 +2743,9 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:139 msgid "" -":mod:`urllib.request`: :class:`~urllib.request.URLopener` and :class:" -"`~urllib.request.FancyURLopener` style of invoking requests is deprecated. " -"Use newer :func:`~urllib.request.urlopen` functions and methods." +":mod:`urllib.request`: :class:`~urllib.request.URLopener` " +"and :class:`~urllib.request.FancyURLopener` style of invoking requests is " +"deprecated. Use newer :func:`~urllib.request.urlopen` functions and methods." msgstr "" #: deprecations/pending-removal-in-future.rst:143 @@ -2730,16 +2756,16 @@ msgstr "" #: deprecations/pending-removal-in-future.rst:146 msgid "" -":mod:`xml.etree.ElementTree`: Testing the truth value of an :class:`~xml." -"etree.ElementTree.Element` is deprecated. In a future release it will always " -"return ``True``. Prefer explicit ``len(elem)`` or ``elem is not None`` tests " -"instead." +":mod:`xml.etree.ElementTree`: Testing the truth value of " +"an :class:`~xml.etree.ElementTree.Element` is deprecated. In a future " +"release it will always return ``True``. Prefer explicit ``len(elem)`` or " +"``elem is not None`` tests instead." msgstr "" #: deprecations/pending-removal-in-future.rst:151 msgid "" -":meth:`zipimport.zipimporter.load_module` is deprecated: use :meth:" -"`~zipimport.zipimporter.exec_module` instead." +":meth:`zipimport.zipimporter.load_module` is deprecated: " +"use :meth:`~zipimport.zipimporter.exec_module` instead." msgstr "" #: whatsnew/3.12.rst:2234 @@ -2781,8 +2807,8 @@ msgstr "" #: whatsnew/3.12.rst:1377 msgid "" -":class:`configparser.ConfigParser` no longer has a ``readfp`` method. Use :" -"meth:`~configparser.ConfigParser.read_file` instead." +":class:`configparser.ConfigParser` no longer has a ``readfp`` method. " +"Use :meth:`~configparser.ConfigParser.read_file` instead." msgstr "" #: whatsnew/3.12.rst:1381 @@ -2859,8 +2885,8 @@ msgid "" "Remove the ``filename`` attribute of :mod:`gzip`'s :class:`gzip.GzipFile`, " "deprecated since Python 2.6, use the :attr:`~gzip.GzipFile.name` attribute " "instead. In write mode, the ``filename`` attribute added ``'.gz'`` file " -"extension if it was not present. (Contributed by Victor Stinner in :gh:" -"`94196`.)" +"extension if it was not present. (Contributed by Victor Stinner " +"in :gh:`94196`.)" msgstr "" #: whatsnew/3.12.rst:1434 @@ -2869,11 +2895,11 @@ msgstr "" #: whatsnew/3.12.rst:1436 msgid "" -"Remove the pure Python implementation of :mod:`hashlib`'s :func:`hashlib." -"pbkdf2_hmac`, deprecated in Python 3.10. Python 3.10 and newer requires " -"OpenSSL 1.1.1 (:pep:`644`): this OpenSSL version provides a C implementation " -"of :func:`~hashlib.pbkdf2_hmac` which is faster. (Contributed by Victor " -"Stinner in :gh:`94199`.)" +"Remove the pure Python implementation " +"of :mod:`hashlib`'s :func:`hashlib.pbkdf2_hmac`, deprecated in Python 3.10. " +"Python 3.10 and newer requires OpenSSL 1.1.1 (:pep:`644`): this OpenSSL " +"version provides a C implementation of :func:`~hashlib.pbkdf2_hmac` which is " +"faster. (Contributed by Victor Stinner in :gh:`94199`.)" msgstr "" #: whatsnew/3.12.rst:1470 @@ -2917,8 +2943,8 @@ msgstr "" #: whatsnew/3.12.rst:1464 msgid "" -"The :mod:`!imp` module has been removed. (Contributed by Barry Warsaw in :" -"gh:`98040`.)" +"The :mod:`!imp` module has been removed. (Contributed by Barry Warsaw " +"in :gh:`98040`.)" msgstr "" #: whatsnew/3.12.rst:1467 @@ -2963,8 +2989,8 @@ msgstr "" #: whatsnew/3.12.rst:1476 msgid "" -":attr:`importlib.machinery.SOURCE_SUFFIXES`, :attr:`importlib.machinery." -"EXTENSION_SUFFIXES`, and :attr:`importlib.machinery.BYTECODE_SUFFIXES`" +":attr:`importlib.machinery.SOURCE_SUFFIXES`, :attr:`importlib.machinery.EXTENSION_SUFFIXES`, " +"and :attr:`importlib.machinery.BYTECODE_SUFFIXES`" msgstr "" #: whatsnew/3.12.rst:1477 @@ -3080,10 +3106,10 @@ msgstr "" #: whatsnew/3.12.rst:1518 msgid "" "Remove :mod:`io`'s ``io.OpenWrapper`` and ``_pyio.OpenWrapper``, deprecated " -"in Python 3.10: just use :func:`open` instead. The :func:`open` (:func:`io." -"open`) function is a built-in function. Since Python 3.10, :func:`!_pyio." -"open` is also a static method. (Contributed by Victor Stinner in :gh:" -"`94169`.)" +"in Python 3.10: just use :func:`open` instead. The :func:`open` " +"(:func:`io.open`) function is a built-in function. Since Python " +"3.10, :func:`!_pyio.open` is also a static method. (Contributed by Victor " +"Stinner in :gh:`94169`.)" msgstr "" #: whatsnew/3.12.rst:1525 @@ -3103,10 +3129,10 @@ msgstr "" #: whatsnew/3.12.rst:1534 msgid "" -"The ``smtpd`` module has been removed according to the schedule in :pep:" -"`594`, having been deprecated in Python 3.4.7 and 3.5.4. Use the :pypi:" -"`aiosmtpd` PyPI module or any other :mod:`asyncio`-based server instead. " -"(Contributed by Oleg Iarygin in :gh:`93243`.)" +"The ``smtpd`` module has been removed according to the schedule " +"in :pep:`594`, having been deprecated in Python 3.4.7 and 3.5.4. Use " +"the :pypi:`aiosmtpd` PyPI module or any other :mod:`asyncio`-based server " +"instead. (Contributed by Oleg Iarygin in :gh:`93243`.)" msgstr "" #: whatsnew/3.12.rst:1543 @@ -3131,9 +3157,9 @@ msgstr "" #: whatsnew/3.12.rst:1552 msgid "" -"The ``sqlite3.OptimizedUnicode`` text factory has been an alias for :class:" -"`str` since Python 3.3. Code that previously set the text factory to " -"``OptimizedUnicode`` can either use ``str`` explicitly, or rely on the " +"The ``sqlite3.OptimizedUnicode`` text factory has been an alias " +"for :class:`str` since Python 3.3. Code that previously set the text factory " +"to ``OptimizedUnicode`` can either use ``str`` explicitly, or rely on the " "default value which is also ``str``." msgstr "" @@ -3163,12 +3189,12 @@ msgstr "" #: whatsnew/3.12.rst:1572 msgid "" "Remove the :func:`!ssl.wrap_socket` function, deprecated in Python 3.7: " -"instead, create a :class:`ssl.SSLContext` object and call its :class:`ssl." -"SSLContext.wrap_socket` method. Any package that still uses :func:`!ssl." -"wrap_socket` is broken and insecure. The function neither sends a SNI TLS " -"extension nor validates the server hostname. Code is subject to :cwe:`295` " -"(Improper Certificate Validation). (Contributed by Victor Stinner in :gh:" -"`94199`.)" +"instead, create a :class:`ssl.SSLContext` object and call " +"its :class:`ssl.SSLContext.wrap_socket` method. Any package that still " +"uses :func:`!ssl.wrap_socket` is broken and insecure. The function neither " +"sends a SNI TLS extension nor validates the server hostname. Code is subject " +"to :cwe:`295` (Improper Certificate Validation). (Contributed by Victor " +"Stinner in :gh:`94199`.)" msgstr "" #: whatsnew/3.12.rst:1583 @@ -3319,9 +3345,9 @@ msgstr "" #: whatsnew/3.12.rst:1615 msgid "" -"Undocumented :meth:`TestLoader.loadTestsFromModule ` parameter *use_load_tests* (deprecated and ignored " -"since Python 3.5)." +"Undocumented :meth:`TestLoader.loadTestsFromModule " +"` parameter *use_load_tests* " +"(deprecated and ignored since Python 3.5)." msgstr "" #: whatsnew/3.12.rst:1619 @@ -3365,8 +3391,9 @@ msgstr "" #: whatsnew/3.12.rst:1643 msgid "" "Remove :mod:`zipimport`'s ``find_loader()`` and ``find_module()`` methods, " -"deprecated in Python 3.10: use the ``find_spec()`` method instead. See :pep:" -"`451` for the rationale. (Contributed by Victor Stinner in :gh:`94379`.)" +"deprecated in Python 3.10: use the ``find_spec()`` method instead. " +"See :pep:`451` for the rationale. (Contributed by Victor Stinner " +"in :gh:`94379`.)" msgstr "" #: whatsnew/3.12.rst:1649 @@ -3375,20 +3402,20 @@ msgstr "" #: whatsnew/3.12.rst:1651 msgid "" -"Remove the ``suspicious`` rule from the documentation :file:`Makefile` and :" -"file:`Doc/tools/rstlint.py`, both in favor of `sphinx-lint `_. (Contributed by Julien Palard in :gh:" -"`98179`.)" +"Remove the ``suspicious`` rule from the documentation :file:`Makefile` " +"and :file:`Doc/tools/rstlint.py`, both in favor of `sphinx-lint `_. (Contributed by Julien Palard " +"in :gh:`98179`.)" msgstr "" #: whatsnew/3.12.rst:1656 msgid "" -"Remove the *keyfile* and *certfile* parameters from the :mod:`ftplib`, :mod:" -"`imaplib`, :mod:`poplib` and :mod:`smtplib` modules, and the *key_file*, " -"*cert_file* and *check_hostname* parameters from the :mod:`http.client` " -"module, all deprecated since Python 3.6. Use the *context* parameter " -"(*ssl_context* in :mod:`imaplib`) instead. (Contributed by Victor Stinner " -"in :gh:`94172`.)" +"Remove the *keyfile* and *certfile* parameters from " +"the :mod:`ftplib`, :mod:`imaplib`, :mod:`poplib` and :mod:`smtplib` modules, " +"and the *key_file*, *cert_file* and *check_hostname* parameters from " +"the :mod:`http.client` module, all deprecated since Python 3.6. Use the " +"*context* parameter (*ssl_context* in :mod:`imaplib`) instead. (Contributed " +"by Victor Stinner in :gh:`94172`.)" msgstr "" #: whatsnew/3.12.rst:1664 @@ -3399,8 +3426,8 @@ msgstr "" #: whatsnew/3.12.rst:1667 msgid "" -"Remove ``_use_broken_old_ctypes_structure_semantics_`` flag from :mod:" -"`ctypes` module. (Contributed by Nikita Sobolev in :gh:`99285`.)" +"Remove ``_use_broken_old_ctypes_structure_semantics_`` flag " +"from :mod:`ctypes` module. (Contributed by Nikita Sobolev in :gh:`99285`.)" msgstr "" #: whatsnew/3.12.rst:1999 @@ -3434,8 +3461,8 @@ msgid "" "integer values such as ``randrange(10.5)`` or ``randrange('10')`` has been " "changed from :exc:`ValueError` to :exc:`TypeError`. This also prevents bugs " "where ``randrange(1e25)`` would silently select from a larger range than " -"``randrange(10**25)``. (Originally suggested by Serhiy Storchaka :gh:" -"`86388`.)" +"``randrange(10**25)``. (Originally suggested by Serhiy " +"Storchaka :gh:`86388`.)" msgstr "" #: whatsnew/3.12.rst:1698 @@ -3451,8 +3478,8 @@ msgstr "" #: whatsnew/3.12.rst:1704 msgid "" "Remove the ``asyncore``-based ``smtpd`` module deprecated in Python 3.4.7 " -"and 3.5.4. A recommended replacement is the :mod:`asyncio`-based :pypi:" -"`aiosmtpd` PyPI module." +"and 3.5.4. A recommended replacement is the :mod:`asyncio`-" +"based :pypi:`aiosmtpd` PyPI module." msgstr "" #: whatsnew/3.12.rst:1708 @@ -3464,10 +3491,10 @@ msgstr "" #: whatsnew/3.12.rst:1713 msgid "" -"The :mod:`os` module no longer accepts bytes-like paths, like :class:" -"`bytearray` and :class:`memoryview` types: only the exact :class:`bytes` " -"type is accepted for bytes strings. (Contributed by Victor Stinner in :gh:" -"`98393`.)" +"The :mod:`os` module no longer accepts bytes-like paths, " +"like :class:`bytearray` and :class:`memoryview` types: only the " +"exact :class:`bytes` type is accepted for bytes strings. (Contributed by " +"Victor Stinner in :gh:`98393`.)" msgstr "" #: whatsnew/3.12.rst:1718 @@ -3496,21 +3523,23 @@ msgstr "" #: whatsnew/3.12.rst:1740 msgid "" -"When extracting tar files using :mod:`tarfile` or :func:`shutil." -"unpack_archive`, pass the *filter* argument to limit features that may be " -"surprising or dangerous. See :ref:`tarfile-extraction-filter` for details." +"When extracting tar files using :mod:`tarfile` " +"or :func:`shutil.unpack_archive`, pass the *filter* argument to limit " +"features that may be surprising or dangerous. See :ref:`tarfile-extraction-" +"filter` for details." msgstr "" #: whatsnew/3.12.rst:1745 msgid "" -"The output of the :func:`tokenize.tokenize` and :func:`tokenize." -"generate_tokens` functions is now changed due to the changes introduced in :" -"pep:`701`. This means that ``STRING`` tokens are not emitted any more for f-" -"strings and the tokens described in :pep:`701` are now produced instead: " -"``FSTRING_START``, ``FSTRING_MIDDLE`` and ``FSTRING_END`` are now emitted " -"for f-string \"string\" parts in addition to the appropriate tokens for the " -"tokenization in the expression components. For example for the f-string " -"``f\"start {1+1} end\"`` the old version of the tokenizer emitted::" +"The output of the :func:`tokenize.tokenize` " +"and :func:`tokenize.generate_tokens` functions is now changed due to the " +"changes introduced in :pep:`701`. This means that ``STRING`` tokens are not " +"emitted any more for f-strings and the tokens described in :pep:`701` are " +"now produced instead: ``FSTRING_START``, ``FSTRING_MIDDLE`` and " +"``FSTRING_END`` are now emitted for f-string \"string\" parts in addition to " +"the appropriate tokens for the tokenization in the expression components. " +"For example for the f-string ``f\"start {1+1} end\"`` the old version of the " +"tokenizer emitted::" msgstr "" #: whatsnew/3.12.rst:1754 @@ -3606,11 +3635,11 @@ msgstr "" #: whatsnew/3.12.rst:1810 msgid "" -"Add ``COMPILEALL_OPTS`` variable in :file:`Makefile` to override :mod:" -"`compileall` options (default: ``-j0``) in ``make install``. Also merged the " -"3 ``compileall`` commands into a single command to build .pyc files for all " -"optimization levels (0, 1, 2) at once. (Contributed by Victor Stinner in :gh:" -"`99289`.)" +"Add ``COMPILEALL_OPTS`` variable in :file:`Makefile` to " +"override :mod:`compileall` options (default: ``-j0``) in ``make install``. " +"Also merged the 3 ``compileall`` commands into a single command to " +"build .pyc files for all optimization levels (0, 1, 2) at once. (Contributed " +"by Victor Stinner in :gh:`99289`.)" msgstr "" #: whatsnew/3.12.rst:1816 @@ -3723,8 +3752,8 @@ msgstr "" #: whatsnew/3.12.rst:1870 msgid "" ":c:macro:`Py_TPFLAGS_ITEMS_AT_END` and :c:func:`PyObject_GetItemData` added " -"to allow safely extending certain variable-sized types, including :c:var:" -"`PyType_Type`." +"to allow safely extending certain variable-sized types, " +"including :c:var:`PyType_Type`." msgstr "" #: whatsnew/3.12.rst:1873 @@ -3739,10 +3768,10 @@ msgstr "" #: whatsnew/3.12.rst:1878 msgid "" -"Add the new :ref:`limited C API ` function :c:func:" -"`PyType_FromMetaclass`, which generalizes the existing :c:func:" -"`PyType_FromModuleAndSpec` using an additional metaclass argument. " -"(Contributed by Wenzel Jakob in :gh:`93012`.)" +"Add the new :ref:`limited C API ` " +"function :c:func:`PyType_FromMetaclass`, which generalizes the " +"existing :c:func:`PyType_FromModuleAndSpec` using an additional metaclass " +"argument. (Contributed by Wenzel Jakob in :gh:`93012`.)" msgstr "" #: whatsnew/3.12.rst:1883 @@ -3774,16 +3803,16 @@ msgid "" "makes vectorcall safe to use with mutable types (i.e. heap types without the " "immutable flag, :c:macro:`Py_TPFLAGS_IMMUTABLETYPE`). Mutable types that do " "not override :c:member:`~PyTypeObject.tp_call` now inherit the " -"``Py_TPFLAGS_HAVE_VECTORCALL`` flag. (Contributed by Petr Viktorin in :gh:" -"`93274`.)" +"``Py_TPFLAGS_HAVE_VECTORCALL`` flag. (Contributed by Petr Viktorin " +"in :gh:`93274`.)" msgstr "" #: whatsnew/3.12.rst:1900 msgid "" -"The :c:macro:`Py_TPFLAGS_MANAGED_DICT` and :c:macro:" -"`Py_TPFLAGS_MANAGED_WEAKREF` flags have been added. This allows extensions " -"classes to support object :attr:`~object.__dict__` and weakrefs with less " -"bookkeeping, using less memory and with faster access." +"The :c:macro:`Py_TPFLAGS_MANAGED_DICT` " +"and :c:macro:`Py_TPFLAGS_MANAGED_WEAKREF` flags have been added. This allows " +"extensions classes to support object :attr:`~object.__dict__` and weakrefs " +"with less bookkeeping, using less memory and with faster access." msgstr "" #: whatsnew/3.12.rst:1905 @@ -3813,9 +3842,9 @@ msgstr "" #: whatsnew/3.12.rst:1917 msgid "" -"Add two new public functions, :c:func:`PyEval_SetProfileAllThreads` and :c:" -"func:`PyEval_SetTraceAllThreads`, that allow to set tracing and profiling " -"functions in all running threads in addition to the calling one. " +"Add two new public functions, :c:func:`PyEval_SetProfileAllThreads` " +"and :c:func:`PyEval_SetTraceAllThreads`, that allow to set tracing and " +"profiling functions in all running threads in addition to the calling one. " "(Contributed by Pablo Galindo in :gh:`93503`.)" msgstr "" @@ -3828,11 +3857,11 @@ msgstr "" #: whatsnew/3.12.rst:1927 msgid "" -"The C API now permits registering callbacks via :c:func:" -"`PyDict_AddWatcher`, :c:func:`PyDict_Watch` and related APIs to be called " -"whenever a dictionary is modified. This is intended for use by optimizing " -"interpreters, JIT compilers, or debuggers. (Contributed by Carl Meyer in :gh:" -"`91052`.)" +"The C API now permits registering callbacks " +"via :c:func:`PyDict_AddWatcher`, :c:func:`PyDict_Watch` and related APIs to " +"be called whenever a dictionary is modified. This is intended for use by " +"optimizing interpreters, JIT compilers, or debuggers. (Contributed by Carl " +"Meyer in :gh:`91052`.)" msgstr "" #: whatsnew/3.12.rst:1933 @@ -3852,18 +3881,18 @@ msgstr "" #: whatsnew/3.12.rst:1942 msgid "" "Add :c:func:`PyFrame_GetVar` and :c:func:`PyFrame_GetVarString` functions to " -"get a frame variable by its name. (Contributed by Victor Stinner in :gh:" -"`91248`.)" +"get a frame variable by its name. (Contributed by Victor Stinner " +"in :gh:`91248`.)" msgstr "" #: whatsnew/3.12.rst:1946 msgid "" -"Add :c:func:`PyErr_GetRaisedException` and :c:func:" -"`PyErr_SetRaisedException` for saving and restoring the current exception. " -"These functions return and accept a single exception object, rather than the " -"triple arguments of the now-deprecated :c:func:`PyErr_Fetch` and :c:func:" -"`PyErr_Restore`. This is less error prone and a bit more efficient. " -"(Contributed by Mark Shannon in :gh:`101578`.)" +"Add :c:func:`PyErr_GetRaisedException` " +"and :c:func:`PyErr_SetRaisedException` for saving and restoring the current " +"exception. These functions return and accept a single exception object, " +"rather than the triple arguments of the now-deprecated :c:func:`PyErr_Fetch` " +"and :c:func:`PyErr_Restore`. This is less error prone and a bit more " +"efficient. (Contributed by Mark Shannon in :gh:`101578`.)" msgstr "" #: whatsnew/3.12.rst:1954 @@ -3876,9 +3905,9 @@ msgstr "" #: whatsnew/3.12.rst:1958 msgid "" "Add :c:func:`PyException_GetArgs` and :c:func:`PyException_SetArgs` as " -"convenience functions for retrieving and modifying the :attr:`~BaseException." -"args` passed to the exception's constructor. (Contributed by Mark Shannon " -"in :gh:`101578`.)" +"convenience functions for retrieving and modifying " +"the :attr:`~BaseException.args` passed to the exception's constructor. " +"(Contributed by Mark Shannon in :gh:`101578`.)" msgstr "" #: whatsnew/3.12.rst:1963 @@ -3947,17 +3976,18 @@ msgstr "" #: whatsnew/3.12.rst:1987 msgid "" -":pep:`684`: Add the new :c:func:`Py_NewInterpreterFromConfig` function and :" -"c:type:`PyInterpreterConfig`, which may be used to create sub-interpreters " -"with their own GILs. (See :ref:`whatsnew312-pep684` for more info.) " -"(Contributed by Eric Snow in :gh:`104110`.)" +":pep:`684`: Add the new :c:func:`Py_NewInterpreterFromConfig` function " +"and :c:type:`PyInterpreterConfig`, which may be used to create sub-" +"interpreters with their own GILs. (See :ref:`whatsnew312-pep684` for more " +"info.) (Contributed by Eric Snow in :gh:`104110`.)" msgstr "" #: whatsnew/3.12.rst:1993 msgid "" -"In the limited C API version 3.12, :c:func:`Py_INCREF` and :c:func:" -"`Py_DECREF` functions are now implemented as opaque function calls to hide " -"implementation details. (Contributed by Victor Stinner in :gh:`105387`.)" +"In the limited C API version 3.12, :c:func:`Py_INCREF` " +"and :c:func:`Py_DECREF` functions are now implemented as opaque function " +"calls to hide implementation details. (Contributed by Victor Stinner " +"in :gh:`105387`.)" msgstr "" #: whatsnew/3.12.rst:2001 @@ -3992,8 +4022,9 @@ msgstr "" #: whatsnew/3.12.rst:2020 msgid "" -"To get a list of subclasses, call the Python method :py:meth:`~type." -"__subclasses__` (using :c:func:`PyObject_CallMethod`, for example)." +"To get a list of subclasses, call the Python " +"method :py:meth:`~type.__subclasses__` (using :c:func:`PyObject_CallMethod`, " +"for example)." msgstr "" #: whatsnew/3.12.rst:2024 @@ -4001,37 +4032,38 @@ msgid "" "Add support of more formatting options (left aligning, octals, uppercase " "hexadecimals, :c:type:`intmax_t`, :c:type:`ptrdiff_t`, :c:type:`wchar_t` C " "strings, variable width and precision) in :c:func:`PyUnicode_FromFormat` " -"and :c:func:`PyUnicode_FromFormatV`. (Contributed by Serhiy Storchaka in :gh:" -"`98836`.)" +"and :c:func:`PyUnicode_FromFormatV`. (Contributed by Serhiy Storchaka " +"in :gh:`98836`.)" msgstr "" #: whatsnew/3.12.rst:2030 msgid "" -"An unrecognized format character in :c:func:`PyUnicode_FromFormat` and :c:" -"func:`PyUnicode_FromFormatV` now sets a :exc:`SystemError`. In previous " -"versions it caused all the rest of the format string to be copied as-is to " -"the result string, and any extra arguments discarded. (Contributed by Serhiy " -"Storchaka in :gh:`95781`.)" +"An unrecognized format character in :c:func:`PyUnicode_FromFormat` " +"and :c:func:`PyUnicode_FromFormatV` now sets a :exc:`SystemError`. In " +"previous versions it caused all the rest of the format string to be copied " +"as-is to the result string, and any extra arguments discarded. (Contributed " +"by Serhiy Storchaka in :gh:`95781`.)" msgstr "" #: whatsnew/3.12.rst:2036 msgid "" -"Fix wrong sign placement in :c:func:`PyUnicode_FromFormat` and :c:func:" -"`PyUnicode_FromFormatV`. (Contributed by Philip Georgi in :gh:`95504`.)" +"Fix wrong sign placement in :c:func:`PyUnicode_FromFormat` " +"and :c:func:`PyUnicode_FromFormatV`. (Contributed by Philip Georgi " +"in :gh:`95504`.)" msgstr "" #: whatsnew/3.12.rst:2040 msgid "" "Extension classes wanting to add a :attr:`~object.__dict__` or weak " -"reference slot should use :c:macro:`Py_TPFLAGS_MANAGED_DICT` and :c:macro:" -"`Py_TPFLAGS_MANAGED_WEAKREF` instead of ``tp_dictoffset`` and " +"reference slot should use :c:macro:`Py_TPFLAGS_MANAGED_DICT` " +"and :c:macro:`Py_TPFLAGS_MANAGED_WEAKREF` instead of ``tp_dictoffset`` and " "``tp_weaklistoffset``, respectively. The use of ``tp_dictoffset`` and " "``tp_weaklistoffset`` is still supported, but does not fully support " "multiple inheritance (:gh:`95589`), and performance may be worse. Classes " "declaring :c:macro:`Py_TPFLAGS_MANAGED_DICT` should call :c:func:`!" "_PyObject_VisitManagedDict` and :c:func:`!_PyObject_ClearManagedDict` to " -"traverse and clear their instance's dictionaries. To clear weakrefs, call :c:" -"func:`PyObject_ClearWeakRefs`, as before." +"traverse and clear their instance's dictionaries. To clear weakrefs, " +"call :c:func:`PyObject_ClearWeakRefs`, as before." msgstr "" #: whatsnew/3.12.rst:2052 @@ -4052,10 +4084,10 @@ msgstr "" #: whatsnew/3.12.rst:2062 msgid "" -"The interpreter's error indicator is now always normalized. This means that :" -"c:func:`PyErr_SetObject`, :c:func:`PyErr_SetString` and the other functions " -"that set the error indicator now normalize the exception before storing it. " -"(Contributed by Mark Shannon in :gh:`101578`.)" +"The interpreter's error indicator is now always normalized. This means " +"that :c:func:`PyErr_SetObject`, :c:func:`PyErr_SetString` and the other " +"functions that set the error indicator now normalize the exception before " +"storing it. (Contributed by Mark Shannon in :gh:`101578`.)" msgstr "" #: whatsnew/3.12.rst:2067 @@ -4095,8 +4127,8 @@ msgstr "" #: whatsnew/3.12.rst:2084 msgid "" "Note that :c:func:`PyType_FromMetaclass` (added in Python 3.12) already " -"disallows creating classes whose metaclass overrides ``tp_new`` (:meth:" -"`~object.__new__` in Python)." +"disallows creating classes whose metaclass overrides ``tp_new`` " +"(:meth:`~object.__new__` in Python)." msgstr "" #: whatsnew/3.12.rst:2088 @@ -4114,16 +4146,16 @@ msgstr "" #: whatsnew/3.12.rst:2097 msgid "" -"If initialization can be skipped, it can be done in :c:member:`~PyTypeObject." -"tp_init` instead." +"If initialization can be skipped, it can be done " +"in :c:member:`~PyTypeObject.tp_init` instead." msgstr "" #: whatsnew/3.12.rst:2099 msgid "" "If the metaclass doesn't need to be instantiated from Python, set its " -"``tp_new`` to ``NULL`` using the :c:macro:" -"`Py_TPFLAGS_DISALLOW_INSTANTIATION` flag. This makes it acceptable for " -"``PyType_From*`` functions." +"``tp_new`` to ``NULL`` using " +"the :c:macro:`Py_TPFLAGS_DISALLOW_INSTANTIATION` flag. This makes it " +"acceptable for ``PyType_From*`` functions." msgstr "" #: whatsnew/3.12.rst:2104 @@ -4159,10 +4191,10 @@ msgid "" ":c:struct:`PyLongObject` has had its internals changed for better " "performance. Although the internals of :c:struct:`PyLongObject` are private, " "they are used by some extension modules. The internal fields should no " -"longer be accessed directly, instead the API functions beginning ``PyLong_..." -"`` should be used instead. Two new *unstable* API functions are provided for " -"efficient access to the value of :c:struct:`PyLongObject`\\s which fit into " -"a single machine word:" +"longer be accessed directly, instead the API functions beginning " +"``PyLong_...`` should be used instead. Two new *unstable* API functions are " +"provided for efficient access to the value of :c:struct:`PyLongObject`\\s " +"which fit into a single machine word:" msgstr "" #: whatsnew/3.12.rst:2128 @@ -4184,11 +4216,11 @@ msgstr "" #: whatsnew/3.12.rst:2141 msgid "" -"In accordance with :pep:`699`, the ``ma_version_tag`` field in :c:type:" -"`PyDictObject` is deprecated for extension modules. Accessing this field " -"will generate a compiler warning at compile time. This field will be removed " -"in Python 3.14. (Contributed by Ramvikrams and Kumar Aditya in :gh:`101193`. " -"PEP by Ken Jin.)" +"In accordance with :pep:`699`, the ``ma_version_tag`` field " +"in :c:type:`PyDictObject` is deprecated for extension modules. Accessing " +"this field will generate a compiler warning at compile time. This field will " +"be removed in Python 3.14. (Contributed by Ramvikrams and Kumar Aditya " +"in :gh:`101193`. PEP by Ken Jin.)" msgstr "" #: whatsnew/3.12.rst:2146 @@ -4263,44 +4295,45 @@ msgstr "" #: whatsnew/3.12.rst:2164 msgid "" -":c:var:`Py_LegacyWindowsFSEncodingFlag`: use :c:member:`PyPreConfig." -"legacy_windows_fs_encoding`" +":c:var:`Py_LegacyWindowsFSEncodingFlag`: " +"use :c:member:`PyPreConfig.legacy_windows_fs_encoding`" msgstr "" #: whatsnew/3.12.rst:2165 msgid "" -":c:var:`Py_LegacyWindowsStdioFlag`: use :c:member:`PyConfig." -"legacy_windows_stdio`" +":c:var:`Py_LegacyWindowsStdioFlag`: " +"use :c:member:`PyConfig.legacy_windows_stdio`" msgstr "" #: whatsnew/3.12.rst:2166 msgid "" -":c:var:`!Py_FileSystemDefaultEncoding`: use :c:member:`PyConfig." -"filesystem_encoding`" +":c:var:`!Py_FileSystemDefaultEncoding`: " +"use :c:member:`PyConfig.filesystem_encoding`" msgstr "" #: whatsnew/3.12.rst:2167 msgid "" -":c:var:`!Py_HasFileSystemDefaultEncoding`: use :c:member:`PyConfig." -"filesystem_encoding`" +":c:var:`!Py_HasFileSystemDefaultEncoding`: " +"use :c:member:`PyConfig.filesystem_encoding`" msgstr "" #: whatsnew/3.12.rst:2168 msgid "" -":c:var:`!Py_FileSystemDefaultEncodeErrors`: use :c:member:`PyConfig." -"filesystem_errors`" +":c:var:`!Py_FileSystemDefaultEncodeErrors`: " +"use :c:member:`PyConfig.filesystem_errors`" msgstr "" #: whatsnew/3.12.rst:2169 msgid "" -":c:var:`!Py_UTF8Mode`: use :c:member:`PyPreConfig.utf8_mode` (see :c:func:" -"`Py_PreInitialize`)" +":c:var:`!Py_UTF8Mode`: use :c:member:`PyPreConfig.utf8_mode` " +"(see :c:func:`Py_PreInitialize`)" msgstr "" #: whatsnew/3.12.rst:2171 msgid "" -"The :c:func:`Py_InitializeFromConfig` API should be used with :c:type:" -"`PyConfig` instead. (Contributed by Victor Stinner in :gh:`77782`.)" +"The :c:func:`Py_InitializeFromConfig` API should be used " +"with :c:type:`PyConfig` instead. (Contributed by Victor Stinner " +"in :gh:`77782`.)" msgstr "" #: whatsnew/3.12.rst:2175 @@ -4323,8 +4356,8 @@ msgstr "" #: whatsnew/3.12.rst:2184 msgid "" -":c:struct:`PyMemberDef`, :c:func:`PyMember_GetOne` and :c:func:" -"`PyMember_SetOne`" +":c:struct:`PyMemberDef`, :c:func:`PyMember_GetOne` " +"and :c:func:`PyMember_SetOne`" msgstr "" #: whatsnew/3.12.rst:2186 @@ -4335,8 +4368,8 @@ msgstr "" #: whatsnew/3.12.rst:2188 msgid "" -"The flags :c:macro:`Py_READONLY` (previously ``READONLY``) and :c:macro:" -"`Py_AUDIT_READ` (previously all uppercase)" +"The flags :c:macro:`Py_READONLY` (previously ``READONLY``) " +"and :c:macro:`Py_AUDIT_READ` (previously all uppercase)" msgstr "" #: whatsnew/3.12.rst:2191 @@ -4357,14 +4390,15 @@ msgstr "" #: whatsnew/3.12.rst:2196 msgid "" -"The macros ``RESTRICTED`` and ``READ_RESTRICTED``, equivalents of :c:macro:" -"`Py_AUDIT_READ`." +"The macros ``RESTRICTED`` and ``READ_RESTRICTED``, equivalents " +"of :c:macro:`Py_AUDIT_READ`." msgstr "" #: whatsnew/3.12.rst:2198 msgid "" -"In some configurations, ```` is not included from :file:`Python." -"h`. It should be included manually when using ``offsetof()``." +"In some configurations, ```` is not included " +"from :file:`Python.h`. It should be included manually when using " +"``offsetof()``." msgstr "" #: whatsnew/3.12.rst:2201 @@ -4382,9 +4416,10 @@ msgstr "" #: whatsnew/3.12.rst:2209 msgid "" -":c:func:`PyErr_Fetch` and :c:func:`PyErr_Restore` are deprecated. Use :c:" -"func:`PyErr_GetRaisedException` and :c:func:`PyErr_SetRaisedException` " -"instead. (Contributed by Mark Shannon in :gh:`101578`.)" +":c:func:`PyErr_Fetch` and :c:func:`PyErr_Restore` are deprecated. " +"Use :c:func:`PyErr_GetRaisedException` " +"and :c:func:`PyErr_SetRaisedException` instead. (Contributed by Mark Shannon " +"in :gh:`101578`.)" msgstr "" #: whatsnew/3.12.rst:2214 @@ -4401,9 +4436,10 @@ msgstr "" #: whatsnew/3.12.rst:2220 msgid "" -"Using :c:func:`PyType_FromSpec`, :c:func:`PyType_FromSpecWithBases` or :c:" -"func:`PyType_FromModuleAndSpec` to create a class whose metaclass overrides :" -"c:member:`~PyTypeObject.tp_new` is deprecated. Call the metaclass instead." +"Using :c:func:`PyType_FromSpec`, :c:func:`PyType_FromSpecWithBases` " +"or :c:func:`PyType_FromModuleAndSpec` to create a class whose metaclass " +"overrides :c:member:`~PyTypeObject.tp_new` is deprecated. Call the metaclass " +"instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:4 @@ -4444,8 +4480,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:21 #: deprecations/c-api-pending-removal-in-3.14.rst:71 msgid "" -"The :c:func:`Py_InitializeFromConfig` API should be used with :c:type:" -"`PyConfig` instead." +"The :c:func:`Py_InitializeFromConfig` API should be used " +"with :c:type:`PyConfig` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:24 @@ -4507,8 +4543,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:48 msgid "" -":c:var:`Py_NoUserSiteDirectory`: Use :c:member:`PyConfig." -"user_site_directory` instead." +":c:var:`Py_NoUserSiteDirectory`: " +"Use :c:member:`PyConfig.user_site_directory` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:50 @@ -4529,38 +4565,38 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:57 msgid "" -":c:var:`Py_LegacyWindowsFSEncodingFlag`: Use :c:member:`PyPreConfig." -"legacy_windows_fs_encoding` instead." +":c:var:`Py_LegacyWindowsFSEncodingFlag`: " +"Use :c:member:`PyPreConfig.legacy_windows_fs_encoding` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:59 msgid "" -":c:var:`Py_LegacyWindowsStdioFlag`: Use :c:member:`PyConfig." -"legacy_windows_stdio` instead." +":c:var:`Py_LegacyWindowsStdioFlag`: " +"Use :c:member:`PyConfig.legacy_windows_stdio` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:61 msgid "" -":c:var:`!Py_FileSystemDefaultEncoding`: Use :c:member:`PyConfig." -"filesystem_encoding` instead." +":c:var:`!Py_FileSystemDefaultEncoding`: " +"Use :c:member:`PyConfig.filesystem_encoding` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:63 msgid "" -":c:var:`!Py_HasFileSystemDefaultEncoding`: Use :c:member:`PyConfig." -"filesystem_encoding` instead." +":c:var:`!Py_HasFileSystemDefaultEncoding`: " +"Use :c:member:`PyConfig.filesystem_encoding` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:65 msgid "" -":c:var:`!Py_FileSystemDefaultEncodeErrors`: Use :c:member:`PyConfig." -"filesystem_errors` instead." +":c:var:`!Py_FileSystemDefaultEncodeErrors`: " +"Use :c:member:`PyConfig.filesystem_errors` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.14.rst:67 msgid "" -":c:var:`!Py_UTF8Mode`: Use :c:member:`PyPreConfig.utf8_mode` instead. (see :" -"c:func:`Py_PreInitialize`)" +":c:var:`!Py_UTF8Mode`: Use :c:member:`PyPreConfig.utf8_mode` instead. " +"(see :c:func:`Py_PreInitialize`)" msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:4 @@ -4569,20 +4605,20 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:5 msgid "" -"The :c:func:`PyImport_ImportModuleNoBlock`: Use :c:func:" -"`PyImport_ImportModule` instead." +"The :c:func:`PyImport_ImportModuleNoBlock`: " +"Use :c:func:`PyImport_ImportModule` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:7 msgid "" -":c:func:`PyWeakref_GetObject` and :c:func:`PyWeakref_GET_OBJECT`: Use :c:" -"func:`!PyWeakref_GetRef` instead." +":c:func:`PyWeakref_GetObject` and :c:func:`PyWeakref_GET_OBJECT`: " +"Use :c:func:`!PyWeakref_GetRef` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:9 msgid "" -":c:type:`Py_UNICODE` type and the :c:macro:`!Py_UNICODE_WIDE` macro: Use :c:" -"type:`wchar_t` instead." +":c:type:`Py_UNICODE` type and the :c:macro:`!Py_UNICODE_WIDE` macro: " +"Use :c:type:`wchar_t` instead." msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:11 @@ -4617,8 +4653,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-3.15.rst:25 msgid "" -":c:func:`Py_GetPythonHome`: Get :c:member:`PyConfig.home` or the :envvar:" -"`PYTHONHOME` environment variable instead." +":c:func:`Py_GetPythonHome`: Get :c:member:`PyConfig.home` or " +"the :envvar:`PYTHONHOME` environment variable instead." msgstr "" #: deprecations/c-api-pending-removal-in-future.rst:4 @@ -4658,8 +4694,8 @@ msgstr "" #: deprecations/c-api-pending-removal-in-future.rst:19 msgid "" -":c:func:`PySlice_GetIndicesEx`: Use :c:func:`PySlice_Unpack` and :c:func:" -"`PySlice_AdjustIndices` instead." +":c:func:`PySlice_GetIndicesEx`: Use :c:func:`PySlice_Unpack` " +"and :c:func:`PySlice_AdjustIndices` instead." msgstr "" #: deprecations/c-api-pending-removal-in-future.rst:21 @@ -4823,9 +4859,9 @@ msgid "" "The :mod:`~email.generator` will now refuse to serialize (write) headers " "that are improperly folded or delimited, such that they would be parsed as " "multiple headers or joined with adjacent data. If you need to turn this " -"safety feature off, set :attr:`~email.policy.Policy." -"verify_generated_headers`. (Contributed by Bas Bloemsaat and Petr Viktorin " -"in :gh:`121650`.)" +"safety feature off, " +"set :attr:`~email.policy.Policy.verify_generated_headers`. (Contributed by " +"Bas Bloemsaat and Petr Viktorin in :gh:`121650`.)" msgstr "" #: whatsnew/3.12.rst:2284 diff --git a/whatsnew/3.2.po b/whatsnew/3.2.po index caff63fc6..d8fe247a6 100644 --- a/whatsnew/3.2.po +++ b/whatsnew/3.2.po @@ -89,10 +89,10 @@ msgstr "" #: whatsnew/3.2.rst:95 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." +"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 "" #: whatsnew/3.2.rst:101 @@ -209,8 +209,8 @@ msgstr "" #: whatsnew/3.2.rst:178 msgid "" -":ref:`upgrading-optparse-code` for details on the differences from :mod:" -"`optparse`." +":ref:`upgrading-optparse-code` for details on the differences " +"from :mod:`optparse`." msgstr "" #: whatsnew/3.2.rst:182 @@ -229,20 +229,20 @@ msgstr "" #: whatsnew/3.2.rst:191 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::" +"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 "" #: whatsnew/3.2.rst:197 msgid "" "{\"version\": 1,\n" -" \"formatters\": {\"brief\": {\"format\": \"%(levelname)-8s: %(name)-15s: " -"%(message)s\"},\n" -" \"full\": {\"format\": \"%(asctime)s %(name)-15s " -"%(levelname)-8s %(message)s\"}\n" +" \"formatters\": {\"brief\": {\"format\": \"%(levelname)-8s: %(name)-15s: %" +"(message)s\"},\n" +" \"full\": {\"format\": \"%(asctime)s %(name)-15s %" +"(levelname)-8s %(message)s\"}\n" " },\n" " \"handlers\": {\"console\": {\n" " \"class\": \"logging.StreamHandler\",\n" @@ -300,12 +300,12 @@ msgstr "" #: whatsnew/3.2.rst:241 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." +"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 "" #: whatsnew/3.2.rst:248 @@ -328,14 +328,15 @@ msgstr "" #: whatsnew/3.2.rst:260 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." +"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 "" #: whatsnew/3.2.rst:269 @@ -371,8 +372,8 @@ msgstr "" #: whatsnew/3.2.rst:287 msgid "" ":ref:`Code for computing prime numbers in parallel`, an example demonstrating :class:`~concurrent.futures." -"ProcessPoolExecutor`." +"example>`, an example " +"demonstrating :class:`~concurrent.futures.ProcessPoolExecutor`." msgstr "" #: whatsnew/3.2.rst:293 @@ -401,10 +402,11 @@ 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." +"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 "" #: whatsnew/3.2.rst:312 @@ -487,8 +489,8 @@ msgstr "" #: whatsnew/3.2.rst:373 msgid "" -"In Python itself, the tags are accessible from functions in the :mod:" -"`sysconfig` module::" +"In Python itself, the tags are accessible from functions in " +"the :mod:`sysconfig` module::" msgstr "" #: whatsnew/3.2.rst:376 @@ -608,11 +610,11 @@ 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::" +"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 "" #: whatsnew/3.2.rst:463 @@ -640,16 +642,16 @@ msgstr "" #: whatsnew/3.2.rst:483 msgid "" -"(Suggested by Raymond Hettinger and implemented by Eric Smith in :issue:" -"`6081`.)" +"(Suggested by Raymond Hettinger and implemented by Eric Smith " +"in :issue:`6081`.)" msgstr "" #: whatsnew/3.2.rst:486 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 :data:`sys." -"flags` attribute:" +"interactive mode. The option can be introspected using " +"the :data:`sys.flags` attribute:" msgstr "" #: whatsnew/3.2.rst:490 @@ -669,11 +671,11 @@ msgstr "" 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:`~object.__getattr__` or :meth:`~object." -"__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::" +"created dynamically by :meth:`~object.__getattr__` " +"or :meth:`~object.__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 "" #: whatsnew/3.2.rst:508 @@ -697,10 +699,10 @@ msgstr "" #: whatsnew/3.2.rst:521 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:" +"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 "" #: whatsnew/3.2.rst:532 @@ -760,11 +762,11 @@ msgstr "" #: whatsnew/3.2.rst:569 msgid "" ":ref:`Struct sequence types ` are now subclasses of " -"tuple. This means that C structures like those returned by :func:`os.stat`, :" -"func:`time.gmtime`, and :data:`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:" +"tuple. This means that C structures like those returned " +"by :func:`os.stat`, :func:`time.gmtime`, and :data:`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 "" #: whatsnew/3.2.rst:582 @@ -786,8 +788,8 @@ msgstr "" #: whatsnew/3.2.rst:592 msgid "" -"(Suggested by Barry Warsaw and implemented by Philip Jenvey in :issue:" -"`7301`.)" +"(Suggested by Barry Warsaw and implemented by Philip Jenvey " +"in :issue:`7301`.)" msgstr "" #: whatsnew/3.2.rst:594 @@ -801,10 +803,11 @@ msgstr "" #: whatsnew/3.2.rst:600 msgid "" -"A :exc:`ResourceWarning` is issued at interpreter shutdown if the :data:`gc." -"garbage` list isn't empty, and if :const:`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." +"A :exc:`ResourceWarning` is issued at interpreter shutdown if " +"the :data:`gc.garbage` list isn't empty, and " +"if :const:`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 "" #: whatsnew/3.2.rst:605 @@ -827,19 +830,19 @@ msgstr "" #: whatsnew/3.2.rst:619 msgid "" -"(Added by Antoine Pitrou and Georg Brandl in :issue:`10093` and :issue:" -"`477863`.)" +"(Added by Antoine Pitrou and Georg Brandl in :issue:`10093` " +"and :issue:`477863`.)" msgstr "" #: whatsnew/3.2.rst:621 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 :data:`sys.maxsize`. This makes *range* more interoperable with " -"lists::" +"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 :data:`sys.maxsize`. This makes *range* more " +"interoperable with lists::" msgstr "" #: whatsnew/3.2.rst:628 @@ -894,10 +897,10 @@ msgstr "" #: whatsnew/3.2.rst:664 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." +"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 "" #: whatsnew/3.2.rst:669 @@ -928,18 +931,19 @@ msgstr "" 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." +"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 "" #: whatsnew/3.2.rst:690 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." +"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 "" #: whatsnew/3.2.rst:695 @@ -959,31 +963,31 @@ msgstr "" #: whatsnew/3.2.rst:704 msgid "" -"Headers with unencoded non-ASCII bytes are deemed to be :rfc:`2047`\\ -" -"encoded using the *unknown-8bit* character set." +"Headers with unencoded non-ASCII bytes are deemed to be :rfc:`2047`\\ " +"-encoded using the *unknown-8bit* character set." msgstr "" #: whatsnew/3.2.rst:707 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*." +"input used to build the model, including message bodies with " +"a :mailheader:`Content-Transfer-Encoding` of *8bit*." msgstr "" #: whatsnew/3.2.rst:712 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." +"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 "" #: whatsnew/3.2.rst:718 msgid "" -"(Proposed and implemented by R. David Murray, :issue:`4661` and :issue:" -"`10321`.)" +"(Proposed and implemented by R. David Murray, :issue:`4661` " +"and :issue:`10321`.)" msgstr "" #: whatsnew/3.2.rst:721 @@ -992,8 +996,8 @@ msgstr "" #: whatsnew/3.2.rst:723 msgid "" -"The :mod:`xml.etree.ElementTree` package and its :mod:`!xml.etree." -"cElementTree` counterpart have been updated to version 1.3." +"The :mod:`xml.etree.ElementTree` package and its :mod:`!" +"xml.etree.cElementTree` counterpart have been updated to version 1.3." msgstr "" #: whatsnew/3.2.rst:726 @@ -1062,9 +1066,9 @@ msgstr "" #: whatsnew/3.2.rst:749 msgid "" -"For details of the update, see `Introducing ElementTree `_ on " -"Fredrik Lundh's website." +"For details of the update, see `Introducing ElementTree `_ on Fredrik Lundh's website." msgstr "" #: whatsnew/3.2.rst:753 @@ -1103,20 +1107,20 @@ msgstr "" #: whatsnew/3.2.rst:786 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`.)" +"Baker, Miki Tebeka, and Nick Coghlan; see `recipe 498245 `_\\, " +"`recipe 577479 `_\\, :issue:`10586`, and :issue:`10593`.)" msgstr "" #: whatsnew/3.2.rst:792 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:`~function." -"__annotations__` if defined. And now it also gracefully skips over missing " -"attributes such as :attr:`~function.__doc__` which might not be defined for " -"the wrapped callable." +"functions to be introspected. It also " +"copies :attr:`~function.__annotations__` if defined. And now it also " +"gracefully skips over missing attributes such as :attr:`~function.__doc__` " +"which might not be defined for the wrapped callable." msgstr "" #: whatsnew/3.2.rst:799 @@ -1127,21 +1131,22 @@ msgstr "" #: whatsnew/3.2.rst:804 msgid "" -"(By Nick Coghlan and Terrence Cole; :issue:`9567`, :issue:`3445`, and :issue:" -"`8814`.)" +"(By Nick Coghlan and Terrence Cole; :issue:`9567`, :issue:`3445`, " +"and :issue:`8814`.)" msgstr "" #: whatsnew/3.2.rst:807 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." +"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 "" #: whatsnew/3.2.rst:811 msgid "" -"For example, supplying *__eq__* and *__lt__* will enable :func:`~functools." -"total_ordering` to fill-in *__le__*, *__gt__* and *__ge__*::" +"For example, supplying *__eq__* and *__lt__* will " +"enable :func:`~functools.total_ordering` to fill-in *__le__*, *__gt__* and " +"*__ge__*::" msgstr "" #: whatsnew/3.2.rst:814 @@ -1211,18 +1216,19 @@ msgstr "" 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:" +"en.wikipedia.org/wiki/Saturation_arithmetic>`_ 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 "" #: whatsnew/3.2.rst:885 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." +"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 "" #: whatsnew/3.2.rst:889 @@ -1240,9 +1246,10 @@ msgstr "" #: whatsnew/3.2.rst:906 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:" +"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 "" #: whatsnew/3.2.rst:921 @@ -1366,8 +1373,8 @@ msgid "" ">>> from datetime import datetime, timezone\n" "\n" ">>> datetime.now(timezone.utc)\n" -"datetime.datetime(2010, 12, 8, 21, 4, 2, 923754, tzinfo=datetime.timezone." -"utc)\n" +"datetime.datetime(2010, 12, 8, 21, 4, 2, 923754, " +"tzinfo=datetime.timezone.utc)\n" "\n" ">>> datetime.strptime(\"01/01/2000 12:00 +0000\", \"%m/%d/%Y %H:%M %z\")\n" "datetime.datetime(2000, 1, 1, 12, 0, tzinfo=datetime.timezone.utc)" @@ -1375,9 +1382,9 @@ msgstr "" #: whatsnew/3.2.rst:1003 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." +"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 "" #: whatsnew/3.2.rst:1007 @@ -1396,9 +1403,9 @@ msgstr "" #: whatsnew/3.2.rst:1015 msgid "" -"Starting with Py3.2, use of the century guessing heuristic will emit a :exc:" -"`DeprecationWarning`. Instead, it is recommended that :data:`!time." -"accept2dyear` be set to ``False`` so that large date ranges can be used " +"Starting with Py3.2, use of the century guessing heuristic will emit " +"a :exc:`DeprecationWarning`. Instead, it is recommended that :data:`!" +"time.accept2dyear` be set to ``False`` so that large date ranges can be used " "without guesswork::" msgstr "" @@ -1423,16 +1430,16 @@ msgstr "" msgid "" "Several functions now have significantly expanded date ranges. When :data:`!" "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." +"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 "" #: whatsnew/3.2.rst:1040 msgid "" -"(Contributed by Alexander Belopolsky and Victor Stinner in :issue:" -"`1289118`, :issue:`5094`, :issue:`6641`, :issue:`2706`, :issue:`1777412`, :" -"issue:`8013`, and :issue:`10827`.)" +"(Contributed by Alexander Belopolsky and Victor Stinner " +"in :issue:`1289118`, :issue:`5094`, :issue:`6641`, :issue:`2706`, :issue:`1777412`, :issue:`8013`, " +"and :issue:`10827`.)" msgstr "" #: whatsnew/3.2.rst:1047 @@ -1498,8 +1505,8 @@ msgstr "" #: whatsnew/3.2.rst:1100 msgid "" -"The :mod:`abc` module now supports :func:`~abc.abstractclassmethod` and :" -"func:`~abc.abstractstaticmethod`." +"The :mod:`abc` module now supports :func:`~abc.abstractclassmethod` " +"and :func:`~abc.abstractstaticmethod`." msgstr "" #: whatsnew/3.2.rst:1103 @@ -1572,9 +1579,9 @@ msgstr "" msgid "" "When writing a :meth:`~object.__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." +"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 "" #: whatsnew/3.2.rst:1157 @@ -1609,8 +1616,8 @@ msgstr "" #: whatsnew/3.2.rst:1177 msgid "" -"In addition to dictionary-based configuration described above, the :mod:" -"`logging` package has many other improvements." +"In addition to dictionary-based configuration described above, " +"the :mod:`logging` package has many other improvements." msgstr "" #: whatsnew/3.2.rst:1180 @@ -1625,17 +1632,17 @@ msgstr "" 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::" +"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 "" #: whatsnew/3.2.rst:1191 msgid "" ">>> from logging import basicConfig\n" -">>> basicConfig(style='%', format=\"%(name)s -> %(levelname)s: " -"%(message)s\")\n" +">>> basicConfig(style='%', format=\"%(name)s -> %(levelname)s: %" +"(message)s\")\n" ">>> basicConfig(style='{', format=\"{name} -> {levelname} {message}\")\n" ">>> basicConfig(style='$', format=\"$name -> $levelname: $message\")" msgstr "" @@ -1643,19 +1650,19 @@ msgstr "" #: whatsnew/3.2.rst:1196 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 :" -"data:`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 :data:" -"`logging.raiseExceptions`. The new default handler is stored in :data:" -"`logging.lastResort`." +"default configuration using a :class:`~logging.StreamHandler` directed " +"to :data:`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 :data:`logging.raiseExceptions`. The new default handler is stored " +"in :data:`logging.lastResort`." msgstr "" #: whatsnew/3.2.rst:1204 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``." +"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 "" #: whatsnew/3.2.rst:1208 @@ -1671,16 +1678,17 @@ msgstr "" #: whatsnew/3.2.rst:1215 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``." +"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 "" #: whatsnew/3.2.rst:1219 msgid "" -"The :class:`csv.DictWriter` has a new method, :meth:`~csv.DictWriter." -"writeheader` for writing-out an initial row to document the field names::" +"The :class:`csv.DictWriter` has a new " +"method, :meth:`~csv.DictWriter.writeheader` for writing-out an initial row " +"to document the field names::" msgstr "" #: whatsnew/3.2.rst:1223 @@ -1708,15 +1716,16 @@ msgstr "" #: whatsnew/3.2.rst:1239 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." +"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 "" #: whatsnew/3.2.rst:1243 msgid "" -"As a convenience, this new functionality is used by :func:`~contextlib." -"contextmanager` so that no extra effort is needed to support both roles." +"As a convenience, this new functionality is used " +"by :func:`~contextlib.contextmanager` so that no extra effort is needed to " +"support both roles." msgstr "" #: whatsnew/3.2.rst:1247 @@ -1813,10 +1822,10 @@ msgstr "" #: whatsnew/3.2.rst:1303 msgid "" -"Some of the hashing details are exposed through a new attribute, :data:`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:" +"Some of the hashing details are exposed through a new " +"attribute, :data:`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 "" #: whatsnew/3.2.rst:1311 @@ -1833,30 +1842,32 @@ msgstr "" #: whatsnew/3.2.rst:1319 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`)." +"directly so there in no longer a need to use " +"the :meth:`~decimal.Decimal.from_float` method (:issue:`8257`)." msgstr "" #: whatsnew/3.2.rst:1323 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`)." +"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 "" #: whatsnew/3.2.rst:1327 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`):" +"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 "" #: whatsnew/3.2.rst:1338 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`)." +"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 "" #: whatsnew/3.2.rst:1343 @@ -1890,8 +1901,8 @@ msgstr "" #: whatsnew/3.2.rst:1363 msgid "" -"Other file-like objects such as :class:`mmap.mmap` and :func:`fileinput." -"input` also grew auto-closing context managers::" +"Other file-like objects such as :class:`mmap.mmap` " +"and :func:`fileinput.input` also grew auto-closing context managers::" msgstr "" #: whatsnew/3.2.rst:1366 @@ -1925,14 +1936,14 @@ msgstr "" #: whatsnew/3.2.rst:1382 msgid "" -"The :func:`os.popen` and :func:`subprocess.Popen` functions now support :" -"keyword:`with` statements for auto-closing of the file descriptors." +"The :func:`os.popen` and :func:`subprocess.Popen` functions now " +"support :keyword:`with` statements for auto-closing of the file descriptors." msgstr "" #: whatsnew/3.2.rst:1385 msgid "" -"(Contributed by Antoine Pitrou and Brian Curtin in :issue:`7461` and :issue:" -"`10554`.)" +"(Contributed by Antoine Pitrou and Brian Curtin in :issue:`7461` " +"and :issue:`10554`.)" msgstr "" #: whatsnew/3.2.rst:1389 @@ -1941,10 +1952,10 @@ msgstr "" #: whatsnew/3.2.rst:1391 msgid "" -"The :mod:`select` module now exposes a new, constant attribute, :const:" -"`~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." +"The :mod:`select` module now exposes a new, constant " +"attribute, :const:`~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 "" #: whatsnew/3.2.rst:1400 @@ -1957,16 +1968,16 @@ msgstr "" #: whatsnew/3.2.rst:1405 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." +":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 "" #: whatsnew/3.2.rst:1410 msgid "" -"The :mod:`gzip` module also gains the :func:`~gzip.compress` and :func:" -"`~gzip.decompress` functions for easier in-memory compression and " +"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 "" @@ -1982,9 +1993,10 @@ msgstr "" 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." +"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 "" #: whatsnew/3.2.rst:1437 @@ -2008,9 +2020,9 @@ 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``::" +"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 "" #: whatsnew/3.2.rst:1454 @@ -2075,11 +2087,12 @@ msgstr "" #: whatsnew/3.2.rst:1496 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``." +"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 "" #: whatsnew/3.2.rst:1505 @@ -2108,9 +2121,9 @@ msgstr "" #: whatsnew/3.2.rst:1522 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:" +"environment variables. The :mod:`os` module provides two new " +"functions, :func:`~os.fsencode` and :func:`~os.fsdecode`, for encoding and " +"decoding filenames:" msgstr "" #: whatsnew/3.2.rst:1532 @@ -2148,8 +2161,8 @@ msgstr "" #: whatsnew/3.2.rst:1551 msgid "" -"*copy_function*: is a callable that will be used to copy files. :func:" -"`shutil.copy2` is used by default." +"*copy_function*: is a callable that will be used to copy " +"files. :func:`shutil.copy2` is used by default." msgstr "" #: whatsnew/3.2.rst:1592 @@ -2167,11 +2180,11 @@ msgstr "" #: whatsnew/3.2.rst:1561 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)." +"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 "" #: whatsnew/3.2.rst:1569 @@ -2218,10 +2231,10 @@ msgstr "" #: whatsnew/3.2.rst:1602 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." +"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 "" #: whatsnew/3.2.rst:1607 @@ -2234,9 +2247,9 @@ msgstr "" #: whatsnew/3.2.rst:1612 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:" +"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 "" #: whatsnew/3.2.rst:1621 @@ -2307,8 +2320,9 @@ msgstr "" #: whatsnew/3.2.rst:1661 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." +"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 "" #: whatsnew/3.2.rst:1665 @@ -2321,15 +2335,16 @@ msgstr "" #: whatsnew/3.2.rst:1669 msgid "" "The version of OpenSSL being used is now accessible using the module " -"attributes :const:`ssl.OPENSSL_VERSION` (a string), :const:`ssl." -"OPENSSL_VERSION_INFO` (a 5-tuple), and :const:`ssl.OPENSSL_VERSION_NUMBER` " -"(an integer)." +"attributes :const:`ssl.OPENSSL_VERSION` (a " +"string), :const:`ssl.OPENSSL_VERSION_INFO` (a 5-tuple), " +"and :const:`ssl.OPENSSL_VERSION_NUMBER` (an integer)." msgstr "" #: whatsnew/3.2.rst:1674 msgid "" -"(Contributed by Antoine Pitrou in :issue:`8850`, :issue:`1589`, :issue:" -"`8322`, :issue:`5639`, :issue:`4870`, :issue:`8484`, and :issue:`8321`.)" +"(Contributed by Antoine Pitrou " +"in :issue:`8850`, :issue:`1589`, :issue:`8322`, :issue:`5639`, :issue:`4870`, :issue:`8484`, " +"and :issue:`8321`.)" msgstr "" #: whatsnew/3.2.rst:1678 @@ -2346,15 +2361,15 @@ msgstr "" #: whatsnew/3.2.rst:1685 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." +"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 "" #: whatsnew/3.2.rst:1689 msgid "" -"(Contributed by Antoine Pitrou in :issue:`9360` and Andrew Vant in :issue:" -"`1926`.)" +"(Contributed by Antoine Pitrou in :issue:`9360` and Andrew Vant " +"in :issue:`1926`.)" msgstr "" #: whatsnew/3.2.rst:1692 @@ -2400,15 +2415,16 @@ msgstr "" #: whatsnew/3.2.rst:1716 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." +"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 "" #: whatsnew/3.2.rst:1721 msgid "" -"Support for certificate checking and HTTPS virtual hosts were added to :" -"class:`~http.client.HTTPSConnection`." +"Support for certificate checking and HTTPS virtual hosts were added " +"to :class:`~http.client.HTTPSConnection`." msgstr "" #: whatsnew/3.2.rst:1724 @@ -2423,9 +2439,9 @@ msgstr "" #: whatsnew/3.2.rst:1731 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." +"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 "" #: whatsnew/3.2.rst:1735 @@ -2433,8 +2449,8 @@ 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`.)" +"incoming and outgoing traffic. (See work by Armin Ronacher " +"in :issue:`10980`.)" msgstr "" #: whatsnew/3.2.rst:1741 @@ -2469,15 +2485,17 @@ msgstr "" #: whatsnew/3.2.rst:1761 msgid "" -"Experimentation at the interactive prompt is now easier because the :class:" -"`unittest.TestCase` class can now be instantiated without arguments:" +"Experimentation at the interactive prompt is now easier because " +"the :class:`unittest.TestCase` class can now be instantiated without " +"arguments:" msgstr "" #: whatsnew/3.2.rst:1770 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::" +"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 "" #: whatsnew/3.2.rst:1775 @@ -2522,12 +2540,13 @@ msgstr "" #: whatsnew/3.2.rst:1799 msgid "" -"For example, :meth:`~unittest.TestCase.assertRegex` is the new name for :" -"meth:`!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." +"For example, :meth:`~unittest.TestCase.assertRegex` is the new name " +"for :meth:`!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 "" #: whatsnew/3.2.rst:1807 @@ -2602,8 +2621,8 @@ msgstr "" msgid "" "The :meth:`!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." +"debug optical illusions where tests like " +"``TestCase().assertDictContainsSubset({'a':1, 'b':2}, {'a':1})`` would fail." msgstr "" #: whatsnew/3.2.rst:1835 @@ -2617,9 +2636,9 @@ msgid "" "``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`." +"n``. The functions and methods affected " +"are :func:`~random.randrange`, :func:`~random.randint`, :func:`~random.choice`, :func:`~random.shuffle` " +"and :func:`~random.sample`." msgstr "" #: whatsnew/3.2.rst:1846 @@ -2665,9 +2684,9 @@ msgstr "" #: whatsnew/3.2.rst:1873 msgid "" -"The :mod:`tempfile` module has a new context manager, :class:`~tempfile." -"TemporaryDirectory` which provides easy deterministic cleanup of temporary " -"directories::" +"The :mod:`tempfile` module has a new context " +"manager, :class:`~tempfile.TemporaryDirectory` which provides easy " +"deterministic cleanup of temporary directories::" msgstr "" #: whatsnew/3.2.rst:1877 @@ -2686,9 +2705,9 @@ msgstr "" #: whatsnew/3.2.rst:1885 msgid "" -"The :mod:`inspect` module has a new function :func:`~inspect." -"getgeneratorstate` to easily identify the current state of a generator-" -"iterator::" +"The :mod:`inspect` module has a new " +"function :func:`~inspect.getgeneratorstate` to easily identify the current " +"state of a generator-iterator::" msgstr "" #: whatsnew/3.2.rst:1889 @@ -2716,9 +2735,9 @@ msgstr "" #: whatsnew/3.2.rst:1906 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::" +"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 "" #: whatsnew/3.2.rst:1911 @@ -2762,10 +2781,11 @@ msgstr "" #: whatsnew/3.2.rst:1942 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::" +"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 "" #: whatsnew/3.2.rst:1947 @@ -3022,8 +3042,8 @@ msgstr "" #: whatsnew/3.2.rst:2117 msgid "" -":file:`pdb.py` now has a ``-c`` option that executes commands as given in a :" -"file:`.pdbrc` script file." +":file:`pdb.py` now has a ``-c`` option that executes commands as given in " +"a :file:`.pdbrc` script file." msgstr "" #: whatsnew/3.2.rst:2119 @@ -3070,12 +3090,12 @@ msgstr "" #: whatsnew/3.2.rst:2135 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." +"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 "" #: whatsnew/3.2.rst:2142 @@ -3186,8 +3206,8 @@ msgstr "" #: whatsnew/3.2.rst:2223 msgid "" -"The :func:`~urllib.parse.urlparse` function now supports `IPv6 `_ addresses as described in :rfc:`2732`:" +"The :func:`~urllib.parse.urlparse` function now supports `IPv6 `_ addresses as described in :rfc:`2732`:" msgstr "" #: whatsnew/3.2.rst:2235 @@ -3211,8 +3231,8 @@ msgstr "" 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::" +"a string, then the *safe*, *encoding*, and *error* parameters are sent " +"to :func:`~urllib.parse.quote_plus` for encoding::" msgstr "" #: whatsnew/3.2.rst:2250 @@ -3226,17 +3246,17 @@ msgstr "" #: whatsnew/3.2.rst:2256 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:" +"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 "" #: whatsnew/3.2.rst:2265 msgid "" -"(Work by Nick Coghlan, Dan Mahn, and Senthil Kumaran in :issue:`2987`, :" -"issue:`5468`, and :issue:`9873`.)" +"(Work by Nick Coghlan, Dan Mahn, and Senthil Kumaran " +"in :issue:`2987`, :issue:`5468`, and :issue:`9873`.)" msgstr "" #: whatsnew/3.2.rst:2269 @@ -3261,8 +3281,8 @@ msgstr "" #: whatsnew/3.2.rst:2280 msgid "" -"As expected, the :meth:`~mailbox.Mailbox.add` method for :class:`mailbox." -"Mailbox` objects now accepts binary input." +"As expected, the :meth:`~mailbox.Mailbox.add` method " +"for :class:`mailbox.Mailbox` objects now accepts binary input." msgstr "" #: whatsnew/3.2.rst:2283 @@ -3274,19 +3294,19 @@ msgstr "" #: whatsnew/3.2.rst:2287 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*." +"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 "" #: whatsnew/3.2.rst:2293 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." +"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 "" #: whatsnew/3.2.rst:2298 @@ -3328,8 +3348,9 @@ msgid "" "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." +"in seconds. This parameter is tunable " +"through :func:`sys.setswitchinterval`. It currently defaults to 5 " +"milliseconds." msgstr "" #: whatsnew/3.2.rst:2327 @@ -3414,8 +3435,8 @@ msgstr "" #: whatsnew/3.2.rst:2374 msgid "" -"The `Timsort algorithm `_ used in :" -"meth:`list.sort` and :func:`sorted` now runs faster and uses less memory " +"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 " @@ -3453,11 +3474,12 @@ msgstr "" #: whatsnew/3.2.rst:2397 msgid "" -"The fast-search algorithm in stringlib is now used by the :meth:`~str." -"split`, :meth:`~str.rsplit`, :meth:`~str.splitlines` and :meth:`~str." -"replace` methods on :class:`bytes`, :class:`bytearray` and :class:`str` " -"objects. Likewise, the algorithm is also used by :meth:`~str.rfind`, :meth:" -"`~str.rindex`, :meth:`~str.rsplit` and :meth:`~str.rpartition`." +"The fast-search algorithm in stringlib is now used by " +"the :meth:`~str.split`, :meth:`~str.rsplit`, :meth:`~str.splitlines` " +"and :meth:`~str.replace` methods on :class:`bytes`, :class:`bytearray` " +"and :class:`str` objects. Likewise, the algorithm is also used " +"by :meth:`~str.rfind`, :meth:`~str.rindex`, :meth:`~str.rsplit` " +"and :meth:`~str.rpartition`." msgstr "" #: whatsnew/3.2.rst:2403 @@ -3479,12 +3501,12 @@ 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:`~http." -"server.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." -"ConfigParser` loads multi-line arguments a bit faster (:issue:`7113` by " -"Łukasz Langa)." +"implementation (:issue:`1569291` by Alexander Belopolsky). " +"The :class:`~http.server.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.ConfigParser` loads multi-line arguments a bit " +"faster (:issue:`7113` by Łukasz Langa)." msgstr "" #: whatsnew/3.2.rst:2422 @@ -3580,15 +3602,16 @@ msgstr "" #: whatsnew/3.2.rst:2477 msgid "" -"(Contributed by Raymond Hettinger; see `rationale `_.)" +"(Contributed by Raymond Hettinger; see `rationale `_.)" msgstr "" #: whatsnew/3.2.rst:2480 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`." +"module has an extensive section, :ref:`re-examples`. Likewise, " +"the :mod:`itertools` module continues to be updated with new :ref:`itertools-" +"recipes`." msgstr "" #: whatsnew/3.2.rst:2485 @@ -3642,17 +3665,17 @@ msgstr "" #: whatsnew/3.2.rst:2513 msgid "" -"In addition to the existing Subversion code repository at https://svn.python." -"org there is now a `Mercurial `_ repository " -"at https://hg.python.org/\\ ." +"In addition to the existing Subversion code repository at https://" +"svn.python.org there is now a `Mercurial `_ " +"repository at https://hg.python.org/\\ ." msgstr "" #: whatsnew/3.2.rst:2517 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." +"for members of the community to create and share external changesets. " +"See :pep:`385` for details." msgstr "" #: whatsnew/3.2.rst:2522 @@ -3724,8 +3747,8 @@ msgstr "" #: whatsnew/3.2.rst:2562 msgid "" -"(Suggested by Raymond Hettinger and implemented by Benjamin Peterson; :issue:" -"`9778`.)" +"(Suggested by Raymond Hettinger and implemented by Benjamin " +"Peterson; :issue:`9778`.)" msgstr "" #: whatsnew/3.2.rst:2565 @@ -3765,10 +3788,10 @@ msgstr "" #: whatsnew/3.2.rst:2585 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`)." +"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 "" #: whatsnew/3.2.rst:2590 @@ -3800,8 +3823,8 @@ msgid "" "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." +"https://www.activestate.com/activetcl/downloads>`_\\. See https://" +"www.python.org/download/mac/tcltk/ for additional details." msgstr "" #: whatsnew/3.2.rst:2611 @@ -3824,25 +3847,27 @@ msgstr "" #: whatsnew/3.2.rst:2621 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." +"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 "" #: whatsnew/3.2.rst:2627 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." +"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 "" #: whatsnew/3.2.rst:2632 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." +"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 "" #: whatsnew/3.2.rst:2637 @@ -3879,9 +3904,9 @@ msgstr "" #: whatsnew/3.2.rst:2653 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`.)" +"to :meth:`array.tobytes() ` " +"and :meth:`array.frombytes() ` for clarity. The old " +"names have been deprecated. (See :issue:`8990`.)" msgstr "" #: whatsnew/3.2.rst:2658 @@ -3914,19 +3939,19 @@ msgstr "" 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)``." +"reproduce Python 3.1 sequences, set the *version* argument to *1*, " +"``random.seed(s, version=1)``." msgstr "" #: whatsnew/3.2.rst:2676 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." +"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 "" #: whatsnew/3.2.rst:2684 @@ -3979,9 +4004,9 @@ msgstr "" #: whatsnew/3.2.rst:2711 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`." +"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 "" #: whatsnew/3.2.rst:2715 @@ -4001,9 +4026,9 @@ msgstr "" #: whatsnew/3.2.rst:2725 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`)." +"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 "" #: whatsnew/3.2.rst:2729 @@ -4024,8 +4049,8 @@ msgstr "" 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." +"APIs (such as :c:func:`PyEval_SaveThread` " +"and :c:func:`PyEval_RestoreThread`) should be used instead." msgstr "" #: whatsnew/3.2.rst:2741 diff --git a/whatsnew/3.3.po b/whatsnew/3.3.po index ec1f61c2c..cf7326bd1 100644 --- a/whatsnew/3.3.po +++ b/whatsnew/3.3.po @@ -112,8 +112,8 @@ msgstr "" #: whatsnew/3.3.rst:87 msgid "" -"Better unicode handling in the :ref:`email ` module (:term:" -"`provisional `)." +"Better unicode handling in the :ref:`email ` module " +"(:term:`provisional `)." msgstr "" #: whatsnew/3.3.rst:90 @@ -167,8 +167,8 @@ msgstr "" 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`)" +"various third party approaches to namespace packages, as described " +"in :pep:`420`)" msgstr "" #: whatsnew/3.3.rst:132 @@ -493,18 +493,20 @@ msgstr "" #: 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." +"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 "" #: 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:" +"constant from the :mod:`errno` module, you can catch the " +"adequate :exc:`OSError` subclass. The available subclasses are the " +"following:" msgstr "" #: whatsnew/3.3.rst:344 @@ -826,10 +828,10 @@ msgstr "" msgid "" "Functions and class objects have a new :attr:`~definition.__qualname__` " "attribute representing the \"path\" from the module top-level to their " -"definition. For global functions and classes, this is the same as :attr:" -"`~definition.__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." +"definition. For global functions and classes, this is the same " +"as :attr:`~definition.__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 "" #: whatsnew/3.3.rst:560 @@ -936,10 +938,11 @@ msgstr "" 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 " +"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 "" @@ -993,10 +996,10 @@ msgstr "" 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." +"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 "" #: whatsnew/3.3.rst:681 @@ -1021,14 +1024,15 @@ msgstr "" #: whatsnew/3.3.rst:694 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." +"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 "" #: whatsnew/3.3.rst:703 @@ -1054,11 +1058,11 @@ msgstr "" 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." +"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 "" #: whatsnew/3.3.rst:722 @@ -1072,10 +1076,11 @@ msgstr "" 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." +"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 "" #: whatsnew/3.3.rst:734 @@ -1106,9 +1111,9 @@ msgstr "" #: whatsnew/3.3.rst:749 msgid "" "Beyond the expanse of what :mod:`importlib` now exposes, there are other " -"visible changes to import. The biggest is that :data:`sys.meta_path` and :" -"data:`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 " +"visible changes to import. The biggest is that :data:`sys.meta_path` " +"and :data:`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." @@ -1126,9 +1131,10 @@ msgstr "" #: whatsnew/3.3.rst:762 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." +"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 "" #: whatsnew/3.3.rst:766 @@ -1160,9 +1166,9 @@ msgstr "" #: whatsnew/3.3.rst:783 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." +"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 "" #: whatsnew/3.3.rst:787 @@ -1176,8 +1182,8 @@ msgstr "" #: whatsnew/3.3.rst:791 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`)" +"the equality of the underlying sequences generated by those range objects. " +"(:issue:`13201`)" msgstr "" #: whatsnew/3.3.rst:795 @@ -1201,9 +1207,9 @@ msgstr "" #: whatsnew/3.3.rst:805 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`)." +"``copy()`` and ``clear()`` (:issue:`10516`). " +"Consequently, :class:`~collections.abc.MutableSequence` now also defines " +"a :meth:`~collections.abc.MutableSequence.clear` method (:issue:`11388`)." msgstr "" #: whatsnew/3.3.rst:810 @@ -1244,8 +1250,8 @@ 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." +"workarounds were sometimes employed, such as " +"the :c:func:`PyImport_ImportModuleNoBlock` C API function." msgstr "" #: whatsnew/3.3.rst:834 @@ -1281,8 +1287,8 @@ msgstr "" #: whatsnew/3.3.rst:852 msgid "" -":func:`hash`: hash randomization is enabled by default, see :meth:`object." -"__hash__` and :envvar:`PYTHONHASHSEED`." +":func:`hash`: hash randomization is enabled by default, " +"see :meth:`object.__hash__` and :envvar:`PYTHONHASHSEED`." msgstr "" #: whatsnew/3.3.rst:854 @@ -1296,8 +1302,8 @@ msgstr "" 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`)." +"documentation sections for the individual builtin sequence types " +"(:issue:`4966`)." msgstr "" #: whatsnew/3.3.rst:864 @@ -1313,10 +1319,11 @@ 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." +"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 "" #: whatsnew/3.3.rst:877 @@ -1391,14 +1398,14 @@ msgstr "" #: whatsnew/3.3.rst:2250 msgid "" -":class:`abc.abstractclassmethod` has been deprecated, use :class:" -"`classmethod` with :func:`abc.abstractmethod` instead." +":class:`abc.abstractclassmethod` has been deprecated, " +"use :class:`classmethod` with :func:`abc.abstractmethod` instead." msgstr "" #: whatsnew/3.3.rst:2252 msgid "" -":class:`abc.abstractstaticmethod` has been deprecated, use :class:" -"`staticmethod` with :func:`abc.abstractmethod` instead." +":class:`abc.abstractstaticmethod` has been deprecated, " +"use :class:`staticmethod` with :func:`abc.abstractmethod` instead." msgstr "" #: whatsnew/3.3.rst:929 @@ -1432,9 +1439,9 @@ msgstr "" #: whatsnew/3.3.rst:947 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`.)" +"the :mod:`base64` modern interface. For example, " +"``base64.b64decode('YWJj')`` returns ``b'abc'``. (Contributed by Catalin " +"Iacob in :issue:`13641`.)" msgstr "" #: whatsnew/3.3.rst:953 @@ -1477,9 +1484,9 @@ msgstr "" #: whatsnew/3.3.rst:974 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." +"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 "" #: whatsnew/3.3.rst:979 @@ -1499,9 +1506,9 @@ msgstr "" #: whatsnew/3.3.rst:988 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." +"``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 "" #: whatsnew/3.3.rst:993 @@ -1515,9 +1522,9 @@ msgstr "" #: whatsnew/3.3.rst:998 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." +"byte of an invalid byte sequence. For example, " +"``b'\\xff\\n'.decode('gb2312', 'replace')`` now returns a ``\\n`` after the " +"replacement character." msgstr "" #: whatsnew/3.3.rst:1002 @@ -1560,16 +1567,16 @@ msgstr "" #: whatsnew/3.3.rst:1023 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`.)" +"number of mappings as a single unit. (Written by Raymond Hettinger " +"for :issue:`11089`, made public in :issue:`11297`.)" msgstr "" #: whatsnew/3.3.rst:1027 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`)" +"collections classes. Aliases for ABCs are still present in " +"the :mod:`collections` module to preserve existing imports. (:issue:`11085`)" msgstr "" #: whatsnew/3.3.rst:1034 @@ -1605,8 +1612,8 @@ msgstr "" #: whatsnew/3.3.rst:1057 msgid "" -"Addition of salt and modular crypt format (hashing method) and the :func:" -"`~crypt.mksalt` function to the :mod:`crypt` module." +"Addition of salt and modular crypt format (hashing method) and " +"the :func:`~crypt.mksalt` function to the :mod:`crypt` module." msgstr "" #: whatsnew/3.3.rst:1060 @@ -1620,8 +1627,9 @@ msgstr "" #: whatsnew/3.3.rst:1065 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`)." +"functions when Unicode strings or characters are passed " +"(e.g. :c:func:`waddwstr`), and bytes functions otherwise " +"(e.g. :c:func:`waddstr`)." msgstr "" #: whatsnew/3.3.rst:1068 @@ -1657,8 +1665,8 @@ msgstr "" #: whatsnew/3.3.rst:1081 msgid "" "Equality comparisons between naive and aware :class:`~datetime.datetime` " -"instances now return :const:`False` instead of raising :exc:`TypeError` (:" -"issue:`15006`)." +"instances now return :const:`False` instead of raising :exc:`TypeError` " +"(:issue:`15006`)." msgstr "" #: whatsnew/3.3.rst:1084 @@ -1783,8 +1791,8 @@ msgstr "" #: whatsnew/3.3.rst:1130 msgid "" "If Python is compiled without threads, the C version automatically disables " -"the expensive thread local context machinery. In this case, the variable :" -"const:`~decimal.HAVE_THREADS` is set to ``False``." +"the expensive thread local context machinery. In this case, the " +"variable :const:`~decimal.HAVE_THREADS` is set to ``False``." msgstr "" #: whatsnew/3.3.rst:1137 @@ -1831,10 +1839,11 @@ msgstr "" #: whatsnew/3.3.rst:1150 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 " -"``999999``." +"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 ``999999``." msgstr "" #: whatsnew/3.3.rst:1155 @@ -1842,29 +1851,31 @@ 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." +"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 "" #: whatsnew/3.3.rst:1164 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\"." +"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 "" #: whatsnew/3.3.rst:1170 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." +"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 "" #: whatsnew/3.3.rst:1180 @@ -1895,18 +1906,18 @@ msgstr "" #: whatsnew/3.3.rst:1200 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`." +"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 "" #: whatsnew/3.3.rst:1213 @@ -1956,11 +1967,11 @@ msgstr "" #: whatsnew/3.3.rst:1235 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::" +"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 "" #: whatsnew/3.3.rst:1241 @@ -1990,10 +2001,10 @@ msgid "" "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." +"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 "" #: whatsnew/3.3.rst:1265 @@ -2051,8 +2062,8 @@ msgid "" "'Éric'\n" ">>> m['Date'] = email.utils.localtime()\n" ">>> m['Date'].datetime\n" -"datetime.datetime(2012, 5, 25, 21, 39, 24, 465484, tzinfo=datetime." -"timezone(datetime.timedelta(-1, 72000), 'EDT'))\n" +"datetime.datetime(2012, 5, 25, 21, 39, 24, 465484, " +"tzinfo=datetime.timezone(datetime.timedelta(-1, 72000), 'EDT'))\n" ">>> m['Date']\n" "'Fri, 25 May 2012 21:44:27 -0400'\n" ">>> print(m)\n" @@ -2065,8 +2076,8 @@ 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." +"deal with the :mod:`email.header` :meth:`~email.header.decode_header` " +"or :meth:`~email.header.make_header` functions." msgstr "" #: whatsnew/3.3.rst:1318 @@ -2113,8 +2124,8 @@ msgid "" "(Group(display_name='pals', addresses=(Address(display_name='Bob', " "username='bob', domain='example.com'), Address(display_name='Sally', " "username='sally', domain='example.com')), Group(display_name=None, " -"addresses=(Address(display_name='Bonzo', username='bonz', domain='laugh." -"com'),))" +"addresses=(Address(display_name='Bonzo', username='bonz', " +"domain='laugh.com'),))" msgstr "" #: whatsnew/3.3.rst:1343 @@ -2131,9 +2142,9 @@ msgstr "" #: whatsnew/3.3.rst:1351 msgid "" -"New :class:`~email.parser.BytesHeaderParser`, added to the :mod:`~email." -"parser` module to complement :class:`~email.parser.HeaderParser` and " -"complete the Bytes API." +"New :class:`~email.parser.BytesHeaderParser`, added to " +"the :mod:`~email.parser` module to " +"complement :class:`~email.parser.HeaderParser` and complete the Bytes API." msgstr "" #: whatsnew/3.3.rst:1355 @@ -2156,10 +2167,11 @@ msgstr "" #: whatsnew/3.3.rst:1364 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`." +"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 "" #: whatsnew/3.3.rst:1372 @@ -2170,24 +2182,25 @@ msgstr "" 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`.)" +"when creating the outgoing socket. (Contributed by Giampaolo Rodolà " +"in :issue:`8594`.)" msgstr "" #: whatsnew/3.3.rst:1379 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`.)" +"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 "" #: whatsnew/3.3.rst:1385 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`.)" +"listing format and deprecates :meth:`ftplib.FTP.nlst` " +"and :meth:`ftplib.FTP.dir`. (Contributed by Giampaolo Rodolà " +"in :issue:`11072`.)" msgstr "" #: whatsnew/3.3.rst:1391 @@ -2230,11 +2243,11 @@ msgstr "" #: whatsnew/3.3.rst:1417 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 accumulated headers are sent. (Contributed by Andrew Schaaf in :issue:" -"`3709`.)" +"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 accumulated headers are sent. (Contributed " +"by Andrew Schaaf in :issue:`3709`.)" msgstr "" #: whatsnew/3.3.rst:1423 @@ -2245,9 +2258,10 @@ msgstr "" #: whatsnew/3.3.rst:1426 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`.)" +":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 "" #: whatsnew/3.3.rst:1433 @@ -2257,14 +2271,12 @@ msgstr "" #: whatsnew/3.3.rst:1435 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`.)" +"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 "" #: whatsnew/3.3.rst:1445 @@ -2336,10 +2348,10 @@ msgstr "" #: whatsnew/3.3.rst:1487 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." +"*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 "" #: whatsnew/3.3.rst:1495 @@ -2412,8 +2424,8 @@ msgstr "" #: whatsnew/3.3.rst:1539 msgid "" ":class:`multiprocessing.Connection` objects can now be transferred over " -"multiprocessing connections. (Contributed by Richard Oudkerk in :issue:" -"`4892`.)" +"multiprocessing connections. (Contributed by Richard Oudkerk " +"in :issue:`4892`.)" msgstr "" #: whatsnew/3.3.rst:1543 @@ -2432,11 +2444,12 @@ msgstr "" #: whatsnew/3.3.rst:1552 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`.)" +"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 "" #: whatsnew/3.3.rst:1561 @@ -2456,8 +2469,8 @@ msgid "" ">>> with NNTP('news.gmane.org') as n:\n" "... n.group('gmane.comp.python.committers')\n" "...\n" -"('211 1755 1 1755 gmane.comp.python.committers', 1755, 1, 1755, 'gmane.comp." -"python.committers')\n" +"('211 1755 1 1755 gmane.comp.python.committers', 1755, 1, 1755, " +"'gmane.comp.python.committers')\n" ">>>" msgstr "" @@ -2472,9 +2485,9 @@ msgstr "" #: whatsnew/3.3.rst:1580 msgid "" "The :mod:`os` module has a new :func:`~os.pipe2` function that makes it " -"possible to create a pipe with :const:`~os.O_CLOEXEC` or :const:`~os." -"O_NONBLOCK` flags set atomically. This is especially useful to avoid race " -"conditions in multi-threaded programs." +"possible to create a pipe with :const:`~os.O_CLOEXEC` " +"or :const:`~os.O_NONBLOCK` flags set atomically. This is especially useful " +"to avoid race conditions in multi-threaded programs." msgstr "" #: whatsnew/3.3.rst:1585 @@ -2498,52 +2511,46 @@ 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`)." +"functions and introduces new functions to work on file descriptors " +"(:issue:`4761`, :issue:`10755` and :issue:`14626`)." msgstr "" #: whatsnew/3.3.rst:1601 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." +"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 "" #: whatsnew/3.3.rst:1605 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`." +"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 "" #: whatsnew/3.3.rst:1616 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." +"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 "" #: whatsnew/3.3.rst:1622 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." +"check. Platform support for this can be checked via " +"the :data:`~os.supports_effective_ids` set." msgstr "" #: whatsnew/3.3.rst:1627 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/" +"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 "" @@ -2562,37 +2569,32 @@ msgstr "" #: whatsnew/3.3.rst:1640 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`.)" +"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 "" #: whatsnew/3.3.rst:1646 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`.)" +"terminal attached to a file descriptor. See " +"also :func:`shutil.get_terminal_size`. (Contributed by Zbigniew Jędrzejewski-" +"Szmek in :issue:`13609`.)" msgstr "" #: whatsnew/3.3.rst:1653 msgid "" -"New functions to support Linux extended attributes (:issue:`12720`): :func:" -"`~os.getxattr`, :func:`~os.listxattr`, :func:`~os.removexattr`, :func:`~os." -"setxattr`." +"New functions to support Linux extended attributes " +"(:issue:`12720`): :func:`~os.getxattr`, :func:`~os.listxattr`, :func:`~os.removexattr`, :func:`~os.setxattr`." msgstr "" #: whatsnew/3.3.rst:1657 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`," +"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 "" #: whatsnew/3.3.rst:1666 @@ -2680,12 +2682,12 @@ msgstr "" #: whatsnew/3.3.rst:1696 msgid "" -"New constants :const:`~os.RTLD_LAZY`, :const:`~os.RTLD_NOW`, :const:`~os." -"RTLD_GLOBAL`, :const:`~os.RTLD_LOCAL`, :const:`~os.RTLD_NODELETE`, :const:" -"`~os.RTLD_NOLOAD`, and :const:`~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`.)" +"New " +"constants :const:`~os.RTLD_LAZY`, :const:`~os.RTLD_NOW`, :const:`~os.RTLD_GLOBAL`, :const:`~os.RTLD_LOCAL`, :const:`~os.RTLD_NODELETE`, :const:`~os.RTLD_NOLOAD`, " +"and :const:`~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 "" #: whatsnew/3.3.rst:1704 @@ -2715,8 +2717,9 @@ msgstr "" #: whatsnew/3.3.rst:1721 msgid "" -":class:`pickle.Pickler` objects now have an optional :attr:`~pickle.Pickler." -"dispatch_table` attribute allowing per-pickler reduction functions to be set." +":class:`pickle.Pickler` objects now have an " +"optional :attr:`~pickle.Pickler.dispatch_table` attribute allowing per-" +"pickler reduction functions to be set." msgstr "" #: whatsnew/3.3.rst:1725 @@ -2729,8 +2732,8 @@ msgstr "" #: whatsnew/3.3.rst:1731 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 " +"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 "" @@ -2763,22 +2766,23 @@ msgstr "" #: whatsnew/3.3.rst:1753 msgid "" ":class:`~sched.scheduler` class can now be safely used in multi-threaded " -"environments. (Contributed by Josiah Carlson and Giampaolo Rodolà in :issue:" -"`8684`.)" +"environments. (Contributed by Josiah Carlson and Giampaolo Rodolà " +"in :issue:`8684`.)" msgstr "" #: whatsnew/3.3.rst:1757 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`.)" +"constructor are now optional and defaults to :func:`time.time` " +"and :func:`time.sleep` respectively. (Contributed by Chris Clark " +"in :issue:`13245`.)" msgstr "" #: whatsnew/3.3.rst:1762 msgid "" ":meth:`~sched.scheduler.enter` and :meth:`~sched.scheduler.enterabs` " -"*argument* parameter is now optional. (Contributed by Chris Clark in :issue:" -"`13245`.)" +"*argument* parameter is now optional. (Contributed by Chris Clark " +"in :issue:`13245`.)" msgstr "" #: whatsnew/3.3.rst:1766 @@ -2805,9 +2809,9 @@ msgstr "" #: whatsnew/3.3.rst:1782 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." +"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 "" #: whatsnew/3.3.rst:1789 @@ -2866,9 +2870,9 @@ msgstr "" #: whatsnew/3.3.rst:1818 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`.)" +"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 "" #: whatsnew/3.3.rst:1825 @@ -2928,9 +2932,10 @@ msgstr "" #: whatsnew/3.3.rst:1850 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." +"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 "" #: whatsnew/3.3.rst:1854 @@ -2946,11 +2951,11 @@ msgstr "" #: whatsnew/3.3.rst:1862 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`.)" +"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 "" #: whatsnew/3.3.rst:1868 @@ -2962,9 +2967,10 @@ msgstr "" #: whatsnew/3.3.rst:1872 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`.)" +"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 "" #: whatsnew/3.3.rst:1878 @@ -3004,16 +3010,16 @@ msgstr "" #: whatsnew/3.3.rst:1894 msgid "" -"(Contributed by Matthias Fuchs, updated by Tiago Gonçalves in :issue:" -"`10141`.)" +"(Contributed by Matthias Fuchs, updated by Tiago Gonçalves " +"in :issue:`10141`.)" msgstr "" #: whatsnew/3.3.rst:1896 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 `__)." +"(https://en.wikipedia.org/wiki/Reliable_Datagram_Sockets and `https://" +"oss.oracle.com/projects/rds `__)." msgstr "" #: whatsnew/3.3.rst:1900 @@ -3035,11 +3041,11 @@ msgstr "" #: whatsnew/3.3.rst:1911 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`.)" +":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 "" #: whatsnew/3.3.rst:1919 @@ -3048,9 +3054,10 @@ msgstr "" #: whatsnew/3.3.rst:1921 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`.)" +"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 "" #: whatsnew/3.3.rst:1928 @@ -3085,16 +3092,16 @@ msgstr "" #: whatsnew/3.3.rst:1942 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`.)" +"be used if the private key is encrypted. (Contributed by Adam Simpkins " +"in :issue:`12803`.)" msgstr "" #: whatsnew/3.3.rst:1946 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`.)" +"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 "" #: whatsnew/3.3.rst:1951 @@ -3107,9 +3114,9 @@ msgstr "" #: whatsnew/3.3.rst:1955 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 :const:" -"`~ssl.OP_NO_COMPRESSION` can be used to disable compression. (Contributed by " -"Antoine Pitrou in :issue:`13634`.)" +"its new :meth:`~ssl.SSLSocket.compression` method. The new " +"attribute :const:`~ssl.OP_NO_COMPRESSION` can be used to disable " +"compression. (Contributed by Antoine Pitrou in :issue:`13634`.)" msgstr "" #: whatsnew/3.3.rst:1960 @@ -3121,9 +3128,9 @@ msgstr "" #: whatsnew/3.3.rst:1964 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`.)" +"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 "" #: whatsnew/3.3.rst:1968 @@ -3145,9 +3152,9 @@ msgstr "" #: whatsnew/3.3.rst:1979 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'." +"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 "" #: whatsnew/3.3.rst:1983 @@ -3178,8 +3185,8 @@ msgstr "" #: whatsnew/3.3.rst:2000 msgid "" "A new constant :const:`~subprocess.DEVNULL` allows suppressing output in a " -"platform-independent fashion. (Contributed by Ross Lagerwall in :issue:" -"`5870`.)" +"platform-independent fashion. (Contributed by Ross Lagerwall " +"in :issue:`5870`.)" msgstr "" #: whatsnew/3.3.rst:2006 @@ -3208,9 +3215,9 @@ msgstr "" #: whatsnew/3.3.rst:2023 msgid "" -":class:`tempfile.SpooledTemporaryFile`\\'s :meth:`~tempfile." -"SpooledTemporaryFile.truncate` method now accepts a ``size`` parameter. " -"(Contributed by Ryan Kelly in :issue:`9957`.)" +":class:`tempfile.SpooledTemporaryFile`\\'s :meth:`~tempfile.SpooledTemporaryFile.truncate` " +"method now accepts a ``size`` parameter. (Contributed by Ryan Kelly " +"in :issue:`9957`.)" msgstr "" #: whatsnew/3.3.rst:2029 @@ -3230,11 +3237,10 @@ msgstr "" #: whatsnew/3.3.rst:2039 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`.)" +":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 "" #: whatsnew/3.3.rst:2045 @@ -3289,16 +3295,16 @@ msgstr "" #: whatsnew/3.3.rst:2071 msgid "" -":func:`~time.clock_getres`, :func:`~time.clock_gettime` and :func:`~time." -"clock_settime` functions with :samp:`CLOCK_{xxx}` constants. (Contributed by " -"Victor Stinner in :issue:`10278`.)" +":func:`~time.clock_getres`, :func:`~time.clock_gettime` " +"and :func:`~time.clock_settime` functions with :samp:`CLOCK_{xxx}` " +"constants. (Contributed by Victor Stinner in :issue:`10278`.)" msgstr "" #: whatsnew/3.3.rst:2075 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." +"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 "" #: whatsnew/3.3.rst:2081 @@ -3314,8 +3320,8 @@ msgstr "" #: whatsnew/3.3.rst:2087 msgid "" "The new functions :func:`types.new_class` and :func:`types.prepare_class` " -"provide support for :pep:`3115` compliant dynamic type creation. (:issue:" -"`14588`)" +"provide support for :pep:`3115` compliant dynamic type creation. " +"(:issue:`14588`)" msgstr "" #: whatsnew/3.3.rst:2092 @@ -3326,8 +3332,8 @@ msgstr "" 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`.)" +"as context managers. (Contributed by Ezio Melotti and Winston Ewert " +"in :issue:`10775`.)" msgstr "" #: whatsnew/3.3.rst:2099 @@ -3362,12 +3368,12 @@ msgstr "" #: whatsnew/3.3.rst:2118 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`.)" +"(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 "" #: whatsnew/3.3.rst:2128 @@ -3377,12 +3383,12 @@ msgstr "" #: whatsnew/3.3.rst:2130 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." +"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 "" #: whatsnew/3.3.rst:2140 @@ -3442,8 +3448,8 @@ msgstr "" #: whatsnew/3.3.rst:2167 msgid "" -"(Contributed by Serhiy Storchaka, :issue:`14624`, :issue:`14738` and :issue:" -"`15026`.)" +"(Contributed by Serhiy Storchaka, :issue:`14624`, :issue:`14738` " +"and :issue:`15026`.)" msgstr "" #: whatsnew/3.3.rst:2172 @@ -3519,22 +3525,17 @@ msgid ":c:func:`PyUnicode_AsUCS4`, :c:func:`PyUnicode_AsUCS4Copy`" msgstr "" #: whatsnew/3.3.rst:2198 -msgid "" -":c:macro:`PyUnicode_DATA`, :c:macro:`PyUnicode_1BYTE_DATA`, :c:macro:" -"`PyUnicode_2BYTE_DATA`, :c:macro:`PyUnicode_4BYTE_DATA`" +msgid ":c:macro:`PyUnicode_DATA`, :c:macro:`PyUnicode_1BYTE_DATA`, :c:macro:`PyUnicode_2BYTE_DATA`, :c:macro:`PyUnicode_4BYTE_DATA`" msgstr "" #: whatsnew/3.3.rst:2200 msgid "" ":c:macro:`PyUnicode_KIND` with :c:enum:`PyUnicode_Kind` enum: :c:data:`!" -"PyUnicode_WCHAR_KIND`, :c:data:`PyUnicode_1BYTE_KIND`, :c:data:" -"`PyUnicode_2BYTE_KIND`, :c:data:`PyUnicode_4BYTE_KIND`" +"PyUnicode_WCHAR_KIND`, :c:data:`PyUnicode_1BYTE_KIND`, :c:data:`PyUnicode_2BYTE_KIND`, :c:data:`PyUnicode_4BYTE_KIND`" msgstr "" #: whatsnew/3.3.rst:2203 -msgid "" -":c:macro:`PyUnicode_READ`, :c:macro:`PyUnicode_READ_CHAR`, :c:macro:" -"`PyUnicode_WRITE`" +msgid ":c:macro:`PyUnicode_READ`, :c:macro:`PyUnicode_READ_CHAR`, :c:macro:`PyUnicode_WRITE`" msgstr "" #: whatsnew/3.3.rst:2204 @@ -3581,15 +3582,15 @@ msgstr "" #: whatsnew/3.3.rst:2230 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``)" +"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 "" #: whatsnew/3.3.rst:2233 msgid "" -":meth:`ftplib.FTP.nlst` and :meth:`ftplib.FTP.dir`: use :meth:`ftplib.FTP." -"mlsd`" +":meth:`ftplib.FTP.nlst` and :meth:`ftplib.FTP.dir`: " +"use :meth:`ftplib.FTP.mlsd`" msgstr "" #: whatsnew/3.3.rst:2235 @@ -3613,8 +3614,8 @@ msgstr "" #: whatsnew/3.3.rst:2242 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, " +"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 "" @@ -3650,14 +3651,14 @@ msgstr "" #: whatsnew/3.3.rst:2272 msgid "" -"Unicode functions and methods using :c:type:`Py_UNICODE` and :c:expr:" -"`Py_UNICODE*` types:" +"Unicode functions and methods using :c:type:`Py_UNICODE` " +"and :c:expr:`Py_UNICODE*` types:" msgstr "" #: whatsnew/3.3.rst:2275 msgid "" -":c:macro:`!PyUnicode_FromUnicode`: use :c:func:`PyUnicode_FromWideChar` or :" -"c:func:`PyUnicode_FromKindAndData`" +":c:macro:`!PyUnicode_FromUnicode`: use :c:func:`PyUnicode_FromWideChar` " +"or :c:func:`PyUnicode_FromKindAndData`" msgstr "" #: whatsnew/3.3.rst:2277 @@ -3668,14 +3669,14 @@ msgstr "" #: whatsnew/3.3.rst:2279 msgid "" -":c:macro:`!PyUnicode_AS_DATA`: use :c:macro:`PyUnicode_DATA` with :c:macro:" -"`PyUnicode_READ` and :c:macro:`PyUnicode_WRITE`" +":c:macro:`!PyUnicode_AS_DATA`: use :c:macro:`PyUnicode_DATA` " +"with :c:macro:`PyUnicode_READ` and :c:macro:`PyUnicode_WRITE`" msgstr "" #: whatsnew/3.3.rst:2281 msgid "" -":c:macro:`!PyUnicode_GET_SIZE`, :c:func:`!PyUnicode_GetSize`: use :c:macro:" -"`PyUnicode_GET_LENGTH` or :c:func:`PyUnicode_GetLength`" +":c:macro:`!PyUnicode_GET_SIZE`, :c:func:`!PyUnicode_GetSize`: " +"use :c:macro:`PyUnicode_GET_LENGTH` or :c:func:`PyUnicode_GetLength`" msgstr "" #: whatsnew/3.3.rst:2283 @@ -3686,8 +3687,8 @@ msgstr "" #: whatsnew/3.3.rst:2286 msgid "" -":c:func:`!PyUnicode_AsUnicodeCopy`: use :c:func:`PyUnicode_AsUCS4Copy` or :c:" -"func:`PyUnicode_AsWideCharString`" +":c:func:`!PyUnicode_AsUnicodeCopy`: use :c:func:`PyUnicode_AsUCS4Copy` " +"or :c:func:`PyUnicode_AsWideCharString`" msgstr "" #: whatsnew/3.3.rst:2288 @@ -3700,21 +3701,21 @@ msgstr "" #: whatsnew/3.3.rst:2293 msgid "" -":c:macro:`!Py_UNICODE_strlen()`: use :c:func:`PyUnicode_GetLength` or :c:" -"macro:`PyUnicode_GET_LENGTH`" +":c:macro:`!Py_UNICODE_strlen()`: use :c:func:`PyUnicode_GetLength` " +"or :c:macro:`PyUnicode_GET_LENGTH`" msgstr "" #: whatsnew/3.3.rst:2295 msgid "" -":c:macro:`!Py_UNICODE_strcat()`: use :c:func:`PyUnicode_CopyCharacters` or :" -"c:func:`PyUnicode_FromFormat`" +":c:macro:`!Py_UNICODE_strcat()`: use :c:func:`PyUnicode_CopyCharacters` " +"or :c:func:`PyUnicode_FromFormat`" msgstr "" #: whatsnew/3.3.rst:2297 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`" +":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 "" #: whatsnew/3.3.rst:2300 @@ -3727,8 +3728,8 @@ msgstr "" #: whatsnew/3.3.rst:2302 msgid "" -":c:macro:`!Py_UNICODE_strchr()`, :c:macro:`!Py_UNICODE_strrchr()`: use :c:" -"func:`PyUnicode_FindChar`" +":c:macro:`!Py_UNICODE_strchr()`, :c:macro:`!Py_UNICODE_strrchr()`: " +"use :c:func:`PyUnicode_FindChar`" msgstr "" #: whatsnew/3.3.rst:2304 @@ -3753,8 +3754,8 @@ msgstr "" #: whatsnew/3.3.rst:2311 msgid "" -":c:func:`!PyUnicode_EncodeUTF8`: use :c:func:`PyUnicode_AsUTF8` or :c:func:" -"`PyUnicode_AsUTF8String`" +":c:func:`!PyUnicode_EncodeUTF8`: use :c:func:`PyUnicode_AsUTF8` " +"or :c:func:`PyUnicode_AsUTF8String`" msgstr "" #: whatsnew/3.3.rst:2313 @@ -3767,14 +3768,14 @@ msgstr "" #: whatsnew/3.3.rst:2315 msgid "" -":c:func:`!PyUnicode_EncodeUnicodeEscape` use :c:func:" -"`PyUnicode_AsUnicodeEscapeString`" +":c:func:`!PyUnicode_EncodeUnicodeEscape` " +"use :c:func:`PyUnicode_AsUnicodeEscapeString`" msgstr "" #: whatsnew/3.3.rst:2317 msgid "" -":c:func:`!PyUnicode_EncodeRawUnicodeEscape` use :c:func:" -"`PyUnicode_AsRawUnicodeEscapeString`" +":c:func:`!PyUnicode_EncodeRawUnicodeEscape` " +"use :c:func:`PyUnicode_AsRawUnicodeEscapeString`" msgstr "" #: whatsnew/3.3.rst:2319 @@ -3796,8 +3797,8 @@ msgstr "" #: whatsnew/3.3.rst:2323 msgid "" -":c:func:`!PyUnicode_EncodeMBCS`: use :c:func:`PyUnicode_AsMBCSString` or :c:" -"func:`PyUnicode_EncodeCodePage` (with ``CP_ACP`` code_page)" +":c:func:`!PyUnicode_EncodeMBCS`: use :c:func:`PyUnicode_AsMBCSString` " +"or :c:func:`PyUnicode_EncodeCodePage` (with ``CP_ACP`` code_page)" msgstr "" #: whatsnew/3.3.rst:2325 @@ -3833,8 +3834,8 @@ msgstr "" #: whatsnew/3.3.rst:2347 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." +"environment variable to ``0`` to disable hash randomization. See also " +"the :meth:`object.__hash__` method." msgstr "" #: whatsnew/3.3.rst:2351 @@ -3848,19 +3849,19 @@ msgstr "" #: whatsnew/3.3.rst:2357 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." +":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 "" #: whatsnew/3.3.rst:2362 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." +"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 "" #: whatsnew/3.3.rst:2367 @@ -3878,8 +3879,9 @@ msgid "" "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." +"index of 0. It is preferred, though, that you " +"use :func:`importlib.import_module` rather than call :func:`__import__` " +"directly." msgstr "" #: whatsnew/3.3.rst:2380 @@ -3899,10 +3901,10 @@ msgstr "" msgid "" "Because ``None`` is now inserted into :data:`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 :" -"data:`sys.path_importer_cache` where it represents the use of implicit " +"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 :data:`sys.path_importer_cache` where it represents the use of implicit " "finders, but semantically it should not change anything." msgstr "" @@ -3920,16 +3922,16 @@ 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." +"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 "" #: whatsnew/3.3.rst:2409 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 " +"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 " @@ -3951,9 +3953,9 @@ msgstr "" #: whatsnew/3.3.rst:2425 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`)." +"``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 "" #: whatsnew/3.3.rst:2430 @@ -3974,9 +3976,9 @@ msgstr "" #: whatsnew/3.3.rst:2438 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`.)" +"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 "" #: whatsnew/3.3.rst:2442 @@ -4037,16 +4039,16 @@ msgid "" "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>`." +"reduction provided by :pep:`393`, you have to convert your code to the " +"new :doc:`Unicode API <../c-api/unicode>`." msgstr "" #: whatsnew/3.3.rst:2481 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." +"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 "" #: whatsnew/3.3.rst:2486 @@ -4057,8 +4059,8 @@ msgstr "" 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``." +"This also means that the value of *level* used " +"by :c:func:`PyImport_ImportModuleEx` is now ``0`` instead of ``-1``." msgstr "" #: whatsnew/3.3.rst:2495 diff --git a/whatsnew/3.4.po b/whatsnew/3.4.po index 81dff322e..153321f02 100644 --- a/whatsnew/3.4.po +++ b/whatsnew/3.4.po @@ -67,8 +67,8 @@ msgstr "" #: whatsnew/3.4.rst:89 msgid "" -"command line option for :ref:`isolated mode ` (:" -"issue:`16499`)." +"command line option for :ref:`isolated mode ` " +"(:issue:`16499`)." msgstr "" #: whatsnew/3.4.rst:91 @@ -79,8 +79,8 @@ msgstr "" #: whatsnew/3.4.rst:93 msgid "" -":ref:`A ModuleSpec Type ` for the Import System (:pep:" -"`451`). (Affects importer authors.)" +":ref:`A ModuleSpec Type ` for the Import System " +"(:pep:`451`). (Affects importer authors.)" msgstr "" #: whatsnew/3.4.rst:95 @@ -107,21 +107,21 @@ msgstr "" #: whatsnew/3.4.rst:104 msgid "" -":mod:`enum`: :ref:`Support for enumeration types ` (:pep:" -"`435`)." +":mod:`enum`: :ref:`Support for enumeration types ` " +"(:pep:`435`)." msgstr "" #: whatsnew/3.4.rst:106 msgid "" -":mod:`pathlib`: :ref:`Object-oriented filesystem paths ` (:" -"pep:`428`)." +":mod:`pathlib`: :ref:`Object-oriented filesystem paths ` " +"(:pep:`428`)." msgstr "" #: 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`)." +"selectors>`, built upon the :mod:`select` module primitives (part " +"of :pep:`3156`)." msgstr "" #: whatsnew/3.4.rst:111 @@ -142,8 +142,8 @@ msgstr "" #: whatsnew/3.4.rst:118 msgid "" -":ref:`Single-dispatch generic functions ` in :mod:" -"`functools` (:pep:`443`)." +":ref:`Single-dispatch generic functions ` " +"in :mod:`functools` (:pep:`443`)." msgstr "" #: whatsnew/3.4.rst:120 @@ -159,10 +159,10 @@ msgstr "" #: 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`)." +":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 "" #: whatsnew/3.4.rst:127 @@ -182,8 +182,8 @@ msgstr "" #: whatsnew/3.4.rst:134 msgid "" -":ref:`Secure and interchangeable hash algorithm ` (:pep:" -"`456`)." +":ref:`Secure and interchangeable hash algorithm ` " +"(:pep:`456`)." msgstr "" #: whatsnew/3.4.rst:136 @@ -194,8 +194,8 @@ msgstr "" #: whatsnew/3.4.rst:138 msgid "" -"New command line option for :ref:`isolated mode `, (:" -"issue:`16499`)." +"New command line option for :ref:`isolated mode `, " +"(:issue:`16499`)." msgstr "" #: whatsnew/3.4.rst:140 @@ -242,9 +242,9 @@ msgstr "" #: 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`)." +"certificate verification, including hostname matching " +"(:func:`ssl.match_hostname`) and CRLs (Certificate Revocation lists, " +"see :func:`ssl.SSLContext.load_verify_locations`)." msgstr "" #: whatsnew/3.4.rst:160 @@ -374,8 +374,8 @@ msgstr "" #: whatsnew/3.4.rst:247 msgid "" "However, as this migration is currently still incomplete, the legacy " -"versions of those guides remaining available as :ref:`install-index` and :" -"ref:`setuptools-index`." +"versions of those guides remaining available as :ref:`install-index` " +"and :ref:`setuptools-index`." msgstr "" #: whatsnew/3.4.rst:253 @@ -416,8 +416,7 @@ msgid ":func:`os.get_handle_inheritable`, :func:`os.set_handle_inheritable`" msgstr "" #: whatsnew/3.4.rst:274 -msgid "" -":meth:`socket.socket.get_inheritable`, :meth:`socket.socket.set_inheritable`" +msgid ":meth:`socket.socket.get_inheritable`, :meth:`socket.socket.set_inheritable`" msgstr "" #: whatsnew/3.4.rst:278 @@ -443,19 +442,20 @@ msgstr "" #: whatsnew/3.4.rst:294 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." +"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 "" #: whatsnew/3.4.rst:300 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`` " +"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 "" @@ -555,8 +555,8 @@ msgstr "" #: whatsnew/3.4.rst:373 msgid "" -"(Contributed by Nick Coghlan in :issue:`7475`, :issue:`17827`, :issue:" -"`17828` and :issue:`19619`.)" +"(Contributed by Nick Coghlan " +"in :issue:`7475`, :issue:`17827`, :issue:`17828` and :issue:`19619`.)" msgstr "" #: whatsnew/3.4.rst:380 @@ -578,9 +578,9 @@ msgid "" "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." +"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 "" #: whatsnew/3.4.rst:400 @@ -599,8 +599,8 @@ msgstr "" 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`.)" +"evaluating has no elements. (Contributed by Julian Berman " +"in :issue:`18111`.)" msgstr "" #: whatsnew/3.4.rst:411 @@ -610,9 +610,9 @@ msgstr "" #: whatsnew/3.4.rst:413 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`.)" +"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 "" #: whatsnew/3.4.rst:418 @@ -640,8 +640,8 @@ msgstr "" #: whatsnew/3.4.rst:431 msgid "" ":class:`bytes`.join() and :class:`bytearray`.join() now accept arbitrary " -"buffer objects as arguments. (Contributed by Antoine Pitrou in :issue:" -"`15958`.)" +"buffer objects as arguments. (Contributed by Antoine Pitrou " +"in :issue:`15958`.)" msgstr "" #: whatsnew/3.4.rst:435 @@ -660,9 +660,9 @@ msgstr "" #: whatsnew/3.4.rst:443 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`.)" +":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 "" #: whatsnew/3.4.rst:447 @@ -675,8 +675,8 @@ msgstr "" #: whatsnew/3.4.rst:451 msgid "" ":meth:`~object.__length_hint__` is now part of the formal language " -"specification (see :pep:`424`). (Contributed by Armin Ronacher in :issue:" -"`16148`.)" +"specification (see :pep:`424`). (Contributed by Armin Ronacher " +"in :issue:`16148`.)" msgstr "" #: whatsnew/3.4.rst:457 @@ -713,11 +713,11 @@ msgstr "" #: whatsnew/3.4.rst:483 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." +"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 "" #: whatsnew/3.4.rst:489 @@ -747,10 +747,10 @@ msgstr "" #: whatsnew/3.4.rst:509 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." +"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 "" #: whatsnew/3.4.rst:517 @@ -790,9 +790,9 @@ msgstr "" #: whatsnew/3.4.rst:546 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." +"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 "" #: whatsnew/3.4.rst:554 @@ -937,21 +937,22 @@ msgstr "" #: whatsnew/3.4.rst:646 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`.)" +"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 "" #: whatsnew/3.4.rst:651 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`.)" +"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 "" #: whatsnew/3.4.rst:661 @@ -993,21 +994,21 @@ msgstr "" #: whatsnew/3.4.rst:686 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 " +"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`.)" +"recommended only for utility scripts because it affects the global state " +"of :data:`sys.stdout`. (Contributed by Raymond Hettinger in :issue:`15805`.)" msgstr "" #: whatsnew/3.4.rst:697 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." +"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 "" #: whatsnew/3.4.rst:703 @@ -1028,8 +1029,8 @@ msgstr "" #: whatsnew/3.4.rst:714 msgid "" -"Functions :func:`~dis.show_code`, :func:`~dis.dis`, :func:`~dis.distb`, and :" -"func:`~dis.disassemble` now accept a keyword-only *file* argument that " +"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 "" @@ -1070,12 +1071,13 @@ msgstr "" 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::" +"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 "" #: whatsnew/3.4.rst:748 @@ -1096,16 +1098,16 @@ msgstr "" #: whatsnew/3.4.rst:761 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)``)." +":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 "" #: whatsnew/3.4.rst:766 msgid "" -"(Contributed by Nick Coghlan, Ryan Kelly and Thomas Kluyver in :issue:" -"`11816` and Claudiu Popa in :issue:`17916`.)" +"(Contributed by Nick Coghlan, Ryan Kelly and Thomas Kluyver " +"in :issue:`11816` and Claudiu Popa in :issue:`17916`.)" msgstr "" #: whatsnew/3.4.rst:769 @@ -1132,8 +1134,8 @@ msgid "" "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`.)" +"the :mod:`unittest` CLI). (Contributed by R. David Murray " +"in :issue:`11390`.)" msgstr "" #: whatsnew/3.4.rst:787 @@ -1161,10 +1163,10 @@ 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. " +"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 "" @@ -1173,8 +1175,8 @@ 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`.)" +"the default is ``False``. (Contributed by R. David Murray " +"in :issue:`18891`.)" msgstr "" #: whatsnew/3.4.rst:818 @@ -1186,12 +1188,13 @@ msgid "" "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`.)" +"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 "" #: whatsnew/3.4.rst:834 @@ -1212,8 +1215,8 @@ msgstr "" msgid "" "New module attribute :const:`~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`.)" +"the :func:`~filecmp.dircmp` function. (Contributed by Eli Bendersky " +"in :issue:`15442`.)" msgstr "" #: whatsnew/3.4.rst:850 @@ -1250,9 +1253,9 @@ msgstr "" #: whatsnew/3.4.rst:873 msgid "" -":func:`~functools.total_ordering` now supports a return value of :data:" -"`NotImplemented` from the underlying comparison function. (Contributed by " -"Katie Miller in :issue:`10042`.)" +":func:`~functools.total_ordering` now supports a return value " +"of :data:`NotImplemented` from the underlying comparison function. " +"(Contributed by Katie Miller in :issue:`10042`.)" msgstr "" #: whatsnew/3.4.rst:877 @@ -1300,11 +1303,11 @@ msgstr "" #: whatsnew/3.4.rst:907 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`.)" +"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 "" #: whatsnew/3.4.rst:916 @@ -1331,10 +1334,11 @@ msgstr "" #: whatsnew/3.4.rst:930 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`.)" +"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 "" #: whatsnew/3.4.rst:937 @@ -1373,9 +1377,9 @@ 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`.)" +"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 "" #: whatsnew/3.4.rst:964 @@ -1392,10 +1396,10 @@ msgstr "" #: whatsnew/3.4.rst:972 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." +"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 "" #: whatsnew/3.4.rst:980 @@ -1404,11 +1408,12 @@ msgstr "" #: whatsnew/3.4.rst:982 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`.)" +"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 "" #: whatsnew/3.4.rst:988 @@ -1421,9 +1426,9 @@ msgstr "" #: whatsnew/3.4.rst:993 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`.)" +"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 "" #: whatsnew/3.4.rst:997 @@ -1436,34 +1441,35 @@ msgstr "" #: whatsnew/3.4.rst:1002 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`.)" +"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 "" #: whatsnew/3.4.rst:1007 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 " +"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 "" #: whatsnew/3.4.rst:1012 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." +":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 "" #: whatsnew/3.4.rst:1016 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`.)" +":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 "" #: whatsnew/3.4.rst:1023 @@ -1488,21 +1494,23 @@ msgstr "" #: whatsnew/3.4.rst:1035 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`.)" +"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 "" #: whatsnew/3.4.rst:1041 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 " +":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 "" @@ -1520,17 +1528,18 @@ msgstr "" #: whatsnew/3.4.rst:1060 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." +":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 "" #: whatsnew/3.4.rst:1066 msgid "" "A new :attr:`~ipaddress.IPv4Address.is_global` property is ``True`` if an " -"address is globally routeable. (Contributed by Peter Moody in :issue:" -"`17400`.)" +"address is globally routeable. (Contributed by Peter Moody " +"in :issue:`17400`.)" msgstr "" #: whatsnew/3.4.rst:1072 @@ -1546,27 +1555,29 @@ msgstr "" #: whatsnew/3.4.rst:1078 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.)" +":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 "" #: whatsnew/3.4.rst:1083 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`.)" +":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 "" #: whatsnew/3.4.rst:1091 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`.)" +"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 "" #: whatsnew/3.4.rst:1100 @@ -1579,11 +1590,11 @@ msgid "" "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`.)" +"(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 "" #: whatsnew/3.4.rst:1113 @@ -1603,12 +1614,13 @@ msgstr "" #: whatsnew/3.4.rst:1124 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, " +"``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 "" @@ -1616,21 +1628,22 @@ msgstr "" #: whatsnew/3.4.rst:1134 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`.)" +"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 "" #: whatsnew/3.4.rst:1144 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`)." +"inherit unneeded handles/file descriptors from their parents (part " +"of :issue:`8713`)." msgstr "" #: whatsnew/3.4.rst:1148 @@ -1669,9 +1682,9 @@ msgstr "" #: whatsnew/3.4.rst:1172 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`)." +"` 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 "" #: whatsnew/3.4.rst:1177 @@ -1680,14 +1693,14 @@ msgid "" "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`.)" +"Yogesh Chaudhari, Victor Stinner, and Charles-François Natali " +"in :issue:`17914`.)" msgstr "" #: whatsnew/3.4.rst:1183 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 " +":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 "" @@ -1699,12 +1712,12 @@ msgstr "" #: whatsnew/3.4.rst:1190 msgid "" -":func:`os.open` supports two new flags on platforms that provide them, :" -"const:`~os.O_PATH` (un-opened file descriptor), and :const:`~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.)" +":func:`os.open` supports two new flags on platforms that provide " +"them, :const:`~os.O_PATH` (un-opened file descriptor), " +"and :const:`~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 "" #: whatsnew/3.4.rst:1198 @@ -1741,9 +1754,9 @@ 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." +"classes, very large strings and containers, and classes " +"whose :meth:`__new__` method takes keyword-only arguments. It also provides " +"some efficiency improvements." msgstr "" #: whatsnew/3.4.rst:1229 @@ -1761,12 +1774,13 @@ msgstr "" #: whatsnew/3.4.rst:1236 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 (:const:`~plistlib.FMT_XML`), it also now " -"supports the binary plist format (:const:`~plistlib.FMT_BINARY`). " -"(Contributed by Ronald Oussoren and others in :issue:`14455`.)" +"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 " +"(:const:`~plistlib.FMT_XML`), it also now supports the binary plist format " +"(:const:`~plistlib.FMT_BINARY`). (Contributed by Ronald Oussoren and others " +"in :issue:`14455`.)" msgstr "" #: whatsnew/3.4.rst:1246 @@ -1776,9 +1790,9 @@ msgstr "" #: whatsnew/3.4.rst:1248 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 " +"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 "" @@ -1788,8 +1802,8 @@ msgstr "" #: whatsnew/3.4.rst:1258 msgid "" -"The :mod:`pprint` module's :class:`~pprint.PrettyPrinter` class and its :" -"func:`~pprint.pformat`, and :func:`~pprint.pprint` functions have a new " +"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. " @@ -1818,27 +1832,28 @@ msgstr "" #: whatsnew/3.4.rst:1279 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`.)" +"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 "" #: whatsnew/3.4.rst:1285 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`.)" +"signature of the supplied callable. (Contributed by Larry Hastings " +"in :issue:`20710`.)" msgstr "" #: whatsnew/3.4.rst:1290 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." +"also been improved substantially by the underlying changes in " +"the :mod:`inspect` module." msgstr "" #: whatsnew/3.4.rst:1295 @@ -1884,17 +1899,18 @@ msgstr "" #: whatsnew/3.4.rst:1324 msgid "" "On Linux kernel version 2.6.36 or later, there are also some new Linux " -"specific constants: :const:`~resource.RLIMIT_MSGQUEUE`, :const:`~resource." -"RLIMIT_NICE`, :const:`~resource.RLIMIT_RTPRIO`, :const:`~resource." -"RLIMIT_RTTIME`, and :const:`~resource.RLIMIT_SIGPENDING`. (Contributed by " -"Christian Heimes in :issue:`19324`.)" +"specific " +"constants: :const:`~resource.RLIMIT_MSGQUEUE`, :const:`~resource.RLIMIT_NICE`, :const:`~resource.RLIMIT_RTPRIO`, :const:`~resource.RLIMIT_RTTIME`, " +"and :const:`~resource.RLIMIT_SIGPENDING`. (Contributed by Christian Heimes " +"in :issue:`19324`.)" msgstr "" #: whatsnew/3.4.rst:1330 msgid "" -"On FreeBSD version 9 and later, there some new FreeBSD specific constants: :" -"const:`~resource.RLIMIT_SBSIZE`, :const:`~resource.RLIMIT_SWAP`, and :const:" -"`~resource.RLIMIT_NPTS`. (Contributed by Claudiu Popa in :issue:`19343`.)" +"On FreeBSD version 9 and later, there some new FreeBSD specific " +"constants: :const:`~resource.RLIMIT_SBSIZE`, :const:`~resource.RLIMIT_SWAP`, " +"and :const:`~resource.RLIMIT_NPTS`. (Contributed by Claudiu Popa " +"in :issue:`19343`.)" msgstr "" #: whatsnew/3.4.rst:1337 @@ -1912,8 +1928,9 @@ msgstr "" #: whatsnew/3.4.rst:1344 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`.)" +"and :meth:`~select.devpoll.close` methods, as well as a new " +"attribute :attr:`~select.devpoll.closed`. (Contributed by Victor Stinner " +"in :issue:`18794`.)" msgstr "" #: whatsnew/3.4.rst:1351 @@ -1936,8 +1953,8 @@ 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`.)" +"this specific error. (Contributed by Atsuo Ishimoto and Hynek Schlawack " +"in :issue:`1492704`.)" msgstr "" #: whatsnew/3.4.rst:1369 @@ -1949,8 +1966,8 @@ msgid "" "The :class:`!SMTPServer` and :class:`!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`.)" +"avoid affecting the global socket map. (Contributed by Vinay Sajip " +"in :issue:`11959`.)" msgstr "" #: whatsnew/3.4.rst:1379 @@ -1978,8 +1995,8 @@ msgstr "" #: whatsnew/3.4.rst:1393 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`." +"`, :meth:`~socket.socket.get_inheritable` " +"and :meth:`~socket.socket.set_inheritable`." msgstr "" #: whatsnew/3.4.rst:1397 @@ -2031,37 +2048,40 @@ msgid "" "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`.)" +"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 "" #: whatsnew/3.4.rst:1440 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`.)" +":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 "" #: whatsnew/3.4.rst:1445 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`.)" +"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 "" #: whatsnew/3.4.rst:1452 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`.)" +":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 "" #: whatsnew/3.4.rst:1459 @@ -2069,45 +2089,46 @@ 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 :const:`~ssl.VERIFY_DEFAULT`, :const:`~ssl." -"VERIFY_CRL_CHECK_LEAF`, :const:`~ssl.VERIFY_CRL_CHECK_CHAIN`, or :const:" -"`~ssl.VERIFY_X509_STRICT`. OpenSSL does not do any CRL verification by " -"default. (Contributed by Christien Heimes in :issue:`8813`.)" +"the new " +"constants :const:`~ssl.VERIFY_DEFAULT`, :const:`~ssl.VERIFY_CRL_CHECK_LEAF`, :const:`~ssl.VERIFY_CRL_CHECK_CHAIN`, " +"or :const:`~ssl.VERIFY_X509_STRICT`. OpenSSL does not do any CRL " +"verification by default. (Contributed by Christien Heimes in :issue:`8813`.)" msgstr "" #: whatsnew/3.4.rst:1467 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`.)" +"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 "" #: whatsnew/3.4.rst:1478 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`.)" +"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 "" #: whatsnew/3.4.rst:1485 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`.)" +"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 "" #: whatsnew/3.4.rst:1489 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`.)" +"``calIssuers``, and ``OCSP`` URIs. (Contributed by Christian Heimes " +"in :issue:`18379`.)" msgstr "" #: whatsnew/3.4.rst:1495 @@ -2123,9 +2144,10 @@ msgstr "" #: whatsnew/3.4.rst:1501 msgid "" -"The module supports new :mod:`~stat.ST_MODE` flags, :mod:`~stat.S_IFDOOR`, :" -"const:`~stat.S_IFPORT`, and :const:`~stat.S_IFWHT`. (Contributed by " -"Christian Hiemes in :issue:`11016`.)" +"The module supports new :mod:`~stat.ST_MODE` " +"flags, :mod:`~stat.S_IFDOOR`, :const:`~stat.S_IFPORT`, " +"and :const:`~stat.S_IFWHT`. (Contributed by Christian Hiemes " +"in :issue:`11016`.)" msgstr "" #: whatsnew/3.4.rst:1507 @@ -2134,10 +2156,10 @@ msgstr "" #: whatsnew/3.4.rst:1509 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`.)" +"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 "" #: whatsnew/3.4.rst:1516 @@ -2185,9 +2207,9 @@ msgstr "" #: whatsnew/3.4.rst:1542 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`.)" +"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 "" #: whatsnew/3.4.rst:1548 @@ -2198,10 +2220,10 @@ msgstr "" 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`.)" +"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 "" #: whatsnew/3.4.rst:1557 @@ -2214,10 +2236,10 @@ msgid "" "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`.)" +"(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 "" #: whatsnew/3.4.rst:1572 @@ -2228,8 +2250,8 @@ msgstr "" 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`.)" +"and extract tarfile archives. (Contributed by Berker Peksag " +"in :issue:`13477`.)" msgstr "" #: whatsnew/3.4.rst:1580 @@ -2246,8 +2268,8 @@ msgid "" "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`.)" +"(Contributed by Antoine Pitrou and Serhiy Storchaka in :issue:`18585` " +"and :issue:`18725`.)" msgstr "" #: whatsnew/3.4.rst:1594 @@ -2270,8 +2292,8 @@ msgstr "" 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`.)" +"amount of memory consumed. (Contributed by Andrew Kuchling " +"in :issue:`1565525`.)" msgstr "" #: whatsnew/3.4.rst:1612 @@ -2294,40 +2316,41 @@ msgstr "" #: whatsnew/3.4.rst:1625 msgid "" -":mod:`urllib.request` now supports ``data:`` URLs via the :class:`~urllib." -"request.DataHandler` class. (Contributed by Mathias Panzenböck in :issue:" -"`16423`.)" +":mod:`urllib.request` now supports ``data:`` URLs via " +"the :class:`~urllib.request.DataHandler` class. (Contributed by Mathias " +"Panzenböck in :issue:`16423`.)" msgstr "" #: whatsnew/3.4.rst:1629 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`.)" +"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 "" #: whatsnew/3.4.rst:1634 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`.)" +":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 "" #: whatsnew/3.4.rst:1647 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`.)" +":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 "" #: whatsnew/3.4.rst:1654 @@ -2336,13 +2359,13 @@ msgstr "" #: whatsnew/3.4.rst:1656 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::" +"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 "" #: whatsnew/3.4.rst:1664 @@ -2397,9 +2420,9 @@ msgstr "" #: whatsnew/3.4.rst:1695 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 " +"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 " @@ -2441,8 +2464,8 @@ 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.)" +"installed in the virtual environment. (Contributed by Nick Coghlan " +"in :issue:`19552` as part of the :pep:`453` implementation.)" msgstr "" #: whatsnew/3.4.rst:1730 @@ -2470,9 +2493,9 @@ msgstr "" #: whatsnew/3.4.rst:1742 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`.)" +"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 "" #: whatsnew/3.4.rst:1748 @@ -2507,21 +2530,21 @@ msgstr "" #: whatsnew/3.4.rst:1766 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`.)" +"blocking applications to parse XML documents. An example can be seen " +"at :ref:`elementtree-pull-parsing`. (Contributed by Antoine Pitrou " +"in :issue:`17741`.)" msgstr "" #: whatsnew/3.4.rst:1771 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`.)" +"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 "" #: whatsnew/3.4.rst:1782 @@ -2530,18 +2553,18 @@ msgstr "" #: whatsnew/3.4.rst:1784 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`.)" +"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 "" #: whatsnew/3.4.rst:1790 msgid "" -"The *allowZip64* parameter to :class:`~zipfile.ZipFile` and :class:`~zipfile." -"PyZipfile` is now ``True`` by default. (Contributed by William Mallard in :" -"issue:`17201`.)" +"The *allowZip64* parameter to :class:`~zipfile.ZipFile` " +"and :class:`~zipfile.PyZipfile` is now ``True`` by default. (Contributed by " +"William Mallard in :issue:`17201`.)" msgstr "" #: whatsnew/3.4.rst:1797 @@ -2576,11 +2599,12 @@ msgstr "" #: whatsnew/3.4.rst:1824 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." +"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 "" #: whatsnew/3.4.rst:1833 @@ -2693,31 +2717,33 @@ msgstr "" #: whatsnew/3.4.rst:1909 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." +"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 "" #: whatsnew/3.4.rst:1913 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`.)" +"object allocator have been silenced. (Contributed by Dhiru Kholia " +"in :issue:`18596`.)" msgstr "" #: whatsnew/3.4.rst:1918 msgid "" -"The Windows build now uses `Address Space Layout Randomization `_ and `Data Execution " -"Prevention `_. " -"(Contributed by Christian Heimes in :issue:`16632`.)" +"The Windows build now uses `Address Space Layout Randomization `_ and `Data " +"Execution Prevention `_. (Contributed by Christian Heimes " +"in :issue:`16632`.)" msgstr "" #: whatsnew/3.4.rst:1923 msgid "" -"New function :c:func:`PyObject_LengthHint` is the C API equivalent of :func:" -"`operator.length_hint`. (Contributed by Armin Ronacher in :issue:`16148`.)" +"New function :c:func:`PyObject_LengthHint` is the C API equivalent " +"of :func:`operator.length_hint`. (Contributed by Armin Ronacher " +"in :issue:`16148`.)" msgstr "" #: whatsnew/3.4.rst:1931 @@ -2758,8 +2784,8 @@ msgstr "" 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`.)" +"script at the windows command prompt by just typing its name without the " +"``.py`` extension. (Contributed by Paul Moore in :issue:`18569`.)" msgstr "" #: whatsnew/3.4.rst:1961 @@ -2773,8 +2799,9 @@ msgstr "" #: whatsnew/3.4.rst:1967 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`.)" +"also checks for memory allocation leaks, " +"using :func:`sys.getallocatedblocks`. (Contributed by Antoine Pitrou " +"in :issue:`13390`.)" msgstr "" #: whatsnew/3.4.rst:1972 @@ -2799,15 +2826,15 @@ msgstr "" 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`.)" +"uses of :ref:`__prepare__ `. (Contributed by Benjamin Peterson " +"in :issue:`17853`.)" msgstr "" #: whatsnew/3.4.rst:1987 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`)." +"Stinner using his :pep:`445`-based ``pyfailmalloc`` tool " +"(:issue:`18408`, :issue:`18520`)." msgstr "" #: whatsnew/3.4.rst:1991 @@ -2827,10 +2854,10 @@ msgstr "" #: whatsnew/3.4.rst:2000 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`.)" +"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 "" #: whatsnew/3.4.rst:2005 @@ -2866,12 +2893,13 @@ msgstr "" #: whatsnew/3.4.rst:2027 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`.)" +"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 "" #: whatsnew/3.4.rst:2035 @@ -2904,8 +2932,8 @@ msgstr "" #: whatsnew/3.4.rst:2051 msgid "" -":func:`html.escape` is now 10x faster. (Contributed by Matt Bryant in :" -"issue:`18020`.)" +":func:`html.escape` is now 10x faster. (Contributed by Matt Bryant " +"in :issue:`18020`.)" msgstr "" #: whatsnew/3.4.rst:2054 @@ -2930,9 +2958,9 @@ msgstr "" 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``)." +"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 "" #: whatsnew/3.4.rst:2076 @@ -2943,23 +2971,25 @@ msgstr "" 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:`!find_module` are replaced by :meth:" -"`importlib.abc.PathEntryFinder.find_spec`; all of the :samp:`{xxx}Loader` " -"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." +"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:`!find_module` are " +"replaced by :meth:`importlib.abc.PathEntryFinder.find_spec`; all of " +"the :samp:`{xxx}Loader` 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 "" #: whatsnew/3.4.rst:2103 @@ -2984,8 +3014,8 @@ msgstr "" #: whatsnew/3.4.rst:2113 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." +"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 "" #: whatsnew/3.4.rst:2117 @@ -3002,12 +3032,12 @@ msgstr "" #: whatsnew/3.4.rst:2123 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." +"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 "" #: whatsnew/3.4.rst:2130 @@ -3027,9 +3057,9 @@ msgstr "" #: whatsnew/3.4.rst:2138 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." +"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 "" #: whatsnew/3.4.rst:2145 @@ -3105,8 +3135,8 @@ msgstr "" #: whatsnew/3.4.rst:2184 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`)." +"been meaningless since Python 3.2, when the \"new GIL\" was introduced " +"(:issue:`19199`)." msgstr "" #: whatsnew/3.4.rst:2188 @@ -3117,9 +3147,9 @@ msgstr "" #: whatsnew/3.4.rst:2191 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." +"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 "" #: whatsnew/3.4.rst:2195 @@ -3132,8 +3162,8 @@ msgstr "" #: whatsnew/3.4.rst:2200 msgid "" -"Support for loading the deprecated ``TYPE_INT64`` has been removed from :mod:" -"`marshal`. (Contributed by Dan Riti in :issue:`15480`.)" +"Support for loading the deprecated ``TYPE_INT64`` has been removed " +"from :mod:`marshal`. (Contributed by Dan Riti in :issue:`15480`.)" msgstr "" #: whatsnew/3.4.rst:2203 @@ -3150,16 +3180,16 @@ msgid "" "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." +"objects that do not have a __format__ method that handles it. " +"See :issue:`7994` for background." msgstr "" #: whatsnew/3.4.rst:2215 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`)." +":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 "" #: whatsnew/3.4.rst:2223 @@ -3203,12 +3233,12 @@ msgstr "" #: whatsnew/3.4.rst:2248 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`." +"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 "" #: whatsnew/3.4.rst:2256 @@ -3232,18 +3262,20 @@ msgstr "" #: whatsnew/3.4.rst:2268 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." +"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 "" #: whatsnew/3.4.rst:2274 msgid "" -"The module type now initializes the :attr:`~module.__package__` and :attr:" -"`~module.__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`.)" +"The module type now initializes the :attr:`~module.__package__` " +"and :attr:`~module.__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 "" #: whatsnew/3.4.rst:2280 @@ -3278,9 +3310,9 @@ msgid "" "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`." +"``'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 "" #: whatsnew/3.4.rst:2305 @@ -3293,14 +3325,14 @@ msgstr "" #: 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." +":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 "" #: whatsnew/3.4.rst:2319 @@ -3317,12 +3349,13 @@ msgstr "" #: 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." +":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 "" #: whatsnew/3.4.rst:2337 @@ -3335,8 +3368,8 @@ msgid "" "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`)." +"Cannon in :issue:`18416`). is specified on the command-line) " +"(:issue:`18416`)." msgstr "" #: whatsnew/3.4.rst:2348 @@ -3353,67 +3386,69 @@ 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`)." +"compliance with the language spec; Jython and PyPy already were. " +"(:issue:`17434`)." msgstr "" #: 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." +"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 "" #: 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." +"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 "" #: 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." +"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 "" #: 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`)." +"informative :exc:`ValueError` rather than the previous more " +"mysterious :exc:`AttributeError` (:issue:`9177`)." msgstr "" #: 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`)." +"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 "" #: 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`.)" +"special method returned one. This now raises a :exc:`TypeError`. " +"(:issue:`16290`.)" msgstr "" #: 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`)." +"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 "" #: whatsnew/3.4.rst:2398 @@ -3454,8 +3489,8 @@ msgid "" "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`)." +"``_removeTestAtIndex`` method that does nothing " +"(see :meth:`.TestSuite.__iter__`) (:issue:`11798`)." msgstr "" #: whatsnew/3.4.rst:2425 @@ -3488,8 +3523,8 @@ 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`)." +"add this keyword, with the appropriate value, to " +"any :class:`~html.parser.HTMLParser` calls in your code (:issue:`13633`)." msgstr "" #: whatsnew/3.4.rst:2446 @@ -3513,8 +3548,8 @@ msgid "" "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`)." +"stream in :mod:`~io.TextIOWrapper` to use its *newline* argument " +"(:issue:`15204`)." msgstr "" #: whatsnew/3.4.rst:2462 @@ -3544,10 +3579,10 @@ msgstr "" 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`)." +"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 "" #: whatsnew/3.4.rst:2486 @@ -3556,16 +3591,16 @@ msgstr "" #: 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." +":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 "" #: whatsnew/3.4.rst:2500 @@ -3578,10 +3613,10 @@ msgstr "" #: 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`)" +"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 "" #: whatsnew/3.4.rst:2510 diff --git a/whatsnew/3.5.po b/whatsnew/3.5.po index d029c0c90..6a5483d87 100644 --- a/whatsnew/3.5.po +++ b/whatsnew/3.5.po @@ -118,10 +118,10 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:101 @@ -185,8 +185,9 @@ msgstr "" #: 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.)" +"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 "" #: whatsnew/3.5.rst:143 @@ -344,9 +345,10 @@ msgstr "" #: 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`." +"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 "" #: whatsnew/3.5.rst:259 @@ -369,8 +371,8 @@ msgstr "" 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 " +"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 "" @@ -554,8 +556,8 @@ msgstr "" #: 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." +"Function annotation syntax has been a Python feature since version 3.0 " +"(:pep:`3107`), however the semantics of annotations has been left undefined." msgstr "" #: whatsnew/3.5.rst:410 @@ -587,18 +589,18 @@ msgstr "" #: whatsnew/3.5.rst:425 msgid "" -"While these annotations are available at runtime through the usual :attr:" -"`~object.__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." +"While these annotations are available at runtime through the " +"usual :attr:`~object.__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 "" #: 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." +"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 "" #: whatsnew/3.5.rst:437 @@ -742,37 +744,32 @@ msgstr "" #: 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`;" +":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 "" #: whatsnew/3.5.rst:529 msgid "" -"special cases: :func:`os.close` and :func:`os.dup2` now ignore :py:const:" -"`~errno.EINTR` errors; the syscall is not retried (see the PEP for the " -"rationale);" +"special cases: :func:`os.close` and :func:`os.dup2` now " +"ignore :py:const:`~errno.EINTR` errors; the syscall is not retried (see the " +"PEP for the rationale);" msgstr "" #: whatsnew/3.5.rst:533 msgid "" -":mod:`select` functions: :func:`devpoll.poll() `, :func:" -"`epoll.poll() `, :func:`kqueue.control() `, :func:`poll.poll() `, :func:`~select.select`;" +":mod:`select` functions: :func:`devpoll.poll() " +"`, :func:`epoll.poll() " +"`, :func:`kqueue.control() " +"`, :func:`poll.poll() " +"`, :func:`~select.select`;" msgstr "" #: 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`;" +"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 "" #: whatsnew/3.5.rst:545 @@ -809,18 +806,18 @@ msgstr "" #: 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." +"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 "" #: whatsnew/3.5.rst:575 msgid "" -"This is a backwards incompatible change, so to enable the new behavior, a :" -"term:`__future__` import is necessary::" +"This is a backwards incompatible change, so to enable the new behavior, " +"a :term:`__future__` import is necessary::" msgstr "" #: whatsnew/3.5.rst:578 @@ -937,15 +934,15 @@ msgstr "" #: 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 " +":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." +"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 "" #: whatsnew/3.5.rst:676 @@ -1001,22 +998,22 @@ msgstr "" #: 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`.)" +"The :option:`-b` option now affects comparisons of :class:`bytes` " +"with :class:`int`. (Contributed by Serhiy Storchaka in :issue:`23681`.)" msgstr "" #: 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`.)" +"encodings>`. (Contributed by Serhiy Storchaka in :issue:`22682` " +"and :issue:`22681`.)" msgstr "" #: 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`.)" +"Property docstrings are now writable. This is especially useful " +"for :func:`collections.namedtuple` docstrings. (Contributed by Berker Peksag " +"in :issue:`24064`.)" msgstr "" #: whatsnew/3.5.rst:719 @@ -1067,8 +1064,8 @@ msgstr "" #: whatsnew/3.5.rst:752 msgid "" -"The module implementation has been contributed by Paul Moore in :issue:" -"`23491`." +"The module implementation has been contributed by Paul Moore " +"in :issue:`23491`." msgstr "" #: whatsnew/3.5.rst:757 @@ -1085,10 +1082,10 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:773 @@ -1098,8 +1095,8 @@ msgstr "" #: 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." +"all changes introduced in Python 3.5 have also been backported to Python " +"3.4.x." msgstr "" #: whatsnew/3.5.rst:778 @@ -1108,9 +1105,9 @@ msgstr "" #: whatsnew/3.5.rst:780 msgid "" -"New debugging APIs: :meth:`loop.set_debug() ` and :" -"meth:`loop.get_debug() ` methods. (Contributed by " -"Victor Stinner.)" +"New debugging APIs: :meth:`loop.set_debug() ` " +"and :meth:`loop.get_debug() ` methods. (Contributed " +"by Victor Stinner.)" msgstr "" #: whatsnew/3.5.rst:784 @@ -1136,23 +1133,24 @@ msgstr "" #: 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.)" +"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 "" #: whatsnew/3.5.rst:803 msgid "" -"The :func:`~asyncio.async` function is deprecated in favor of :func:" -"`~asyncio.ensure_future`. (Contributed by Yury Selivanov.)" +"The :func:`~asyncio.async` function is deprecated in favor " +"of :func:`~asyncio.ensure_future`. (Contributed by Yury Selivanov.)" msgstr "" #: 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.)" +"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 "" #: whatsnew/3.5.rst:814 @@ -1163,8 +1161,8 @@ msgstr "" #: whatsnew/3.5.rst:818 msgid "" -"The ``JoinableQueue`` class was removed, in favor of the :class:`asyncio." -"Queue` class. (Contributed by Victor Stinner.)" +"The ``JoinableQueue`` class was removed, in favor of " +"the :class:`asyncio.Queue` class. (Contributed by Victor Stinner.)" msgstr "" #: whatsnew/3.5.rst:822 @@ -1213,9 +1211,9 @@ msgstr "" #: whatsnew/3.5.rst:850 msgid "" -"New :meth:`loop.get_exception_handler() ` method to get the current exception handler. " -"(Contributed by Yury Selivanov.)" +"New :meth:`loop.get_exception_handler() " +"` method to get the current exception " +"handler. (Contributed by Yury Selivanov.)" msgstr "" #: whatsnew/3.5.rst:854 @@ -1227,8 +1225,8 @@ msgstr "" #: whatsnew/3.5.rst:859 msgid "" -"The :meth:`loop.create_connection() ` and :" -"meth:`loop.create_server() ` methods are " +"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 "" @@ -1277,10 +1275,10 @@ msgstr "" #: 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`.)" +"The :func:`InteractiveInterpreter.showtraceback() " +"` method now prints the full " +"chained traceback, just like the interactive interpreter. (Contributed by " +"Claudiu Popa in :issue:`17442`.)" msgstr "" #: whatsnew/3.5.rst:901 @@ -1290,26 +1288,28 @@ msgstr "" #: 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`.)" +"makes it 4 to 100 times faster. (Contributed by Eric Snow " +"in :issue:`16991`.)" msgstr "" #: 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`.)" +":meth:`OrderedDict.items() " +"`, :meth:`OrderedDict.keys() " +"`, :meth:`OrderedDict.values() " +"` views now support :func:`reversed` " +"iteration. (Contributed by Serhiy Storchaka in :issue:`19505`.)" msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:921 @@ -1331,11 +1331,10 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:938 @@ -1345,9 +1344,9 @@ msgstr "" #: 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`.)" +"accepts *start* and *stop* arguments to match the corresponding methods " +"of :class:`tuple`, :class:`list`, etc. (Contributed by Devin Jeanpierre " +"in :issue:`23086`.)" msgstr "" #: whatsnew/3.5.rst:945 @@ -1358,10 +1357,9 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:953 @@ -1377,8 +1375,8 @@ msgstr "" #: 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`` " +"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 "" @@ -1392,10 +1390,11 @@ msgstr "" 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`.)" +"``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 "" #: whatsnew/3.5.rst:977 @@ -1424,10 +1423,10 @@ msgstr "" #: 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." +"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 "" #: whatsnew/3.5.rst:998 @@ -1512,8 +1511,8 @@ msgstr "" #: 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`.)" +"flag has the value ``\"n\"``. (Contributed by Claudiu Popa " +"in :issue:`18039`.)" msgstr "" #: whatsnew/3.5.rst:1061 @@ -1525,8 +1524,8 @@ 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`.)" +"``\"ISO-8859-1\"`` to ``\"utf-8\"``. (Contributed by Berker Peksag " +"in :issue:`2052`.)" msgstr "" #: whatsnew/3.5.rst:1070 @@ -1560,9 +1559,10 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1096 @@ -1571,19 +1571,20 @@ msgstr "" #: 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`.)" +"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 "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1110 @@ -1591,9 +1592,9 @@ 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`.)" +"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 "" #: whatsnew/3.5.rst:1117 @@ -1632,10 +1633,10 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1148 @@ -1667,8 +1668,8 @@ msgstr "" #: 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`.)" +"``\"x\"`` to request exclusive creation. (Contributed by Tim Heaney " +"in :issue:`19222`.)" msgstr "" #: whatsnew/3.5.rst:1174 @@ -1715,10 +1716,11 @@ msgstr "" #: 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 " +":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 "" @@ -1746,10 +1748,10 @@ msgstr "" #: 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." +"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 "" #: whatsnew/3.5.rst:1233 @@ -1766,12 +1768,12 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1247 @@ -1787,10 +1789,10 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1263 @@ -1806,11 +1808,11 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1275 @@ -1829,15 +1831,15 @@ msgstr "" #: 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`.)" +"are now picklable and hashable. (Contributed by Yury Selivanov " +"in :issue:`20726` and :issue:`20334`.)" msgstr "" #: whatsnew/3.5.rst:1289 msgid "" -"A new :meth:`BoundArguments.apply_defaults() ` method provides a way to set default values for missing " -"arguments::" +"A new :meth:`BoundArguments.apply_defaults() " +"` method provides a way to set " +"default values for missing arguments::" msgstr "" #: whatsnew/3.5.rst:1293 @@ -1855,34 +1857,34 @@ msgstr "" #: 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`.)" +"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 "" #: 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`.)" +"following of ``__wrapped__`` links. (Contributed by Yury Selivanov " +"in :issue:`20691`.)" msgstr "" #: 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`.)" +"function>` 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 "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1326 @@ -1892,10 +1894,10 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1336 @@ -1924,9 +1926,9 @@ msgstr "" #: 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::" +"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 "" #: whatsnew/3.5.rst:1354 @@ -1952,14 +1954,14 @@ msgstr "" 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`.)" +"to sort the keys alphabetically. (Contributed by Berker Peksag " +"in :issue:`21650`.)" msgstr "" #: 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. " +"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 "" @@ -2010,10 +2012,10 @@ msgstr "" #: 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::" +"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 "" #: whatsnew/3.5.rst:1416 @@ -2034,8 +2036,8 @@ msgstr "" 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`.)" +"settings used in an HTTP connection. (Contributed by Alex Gaynor " +"in :issue:`22788`.)" msgstr "" #: whatsnew/3.5.rst:1430 @@ -2063,9 +2065,9 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1451 @@ -2087,9 +2089,10 @@ msgstr "" #: 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`.)" +":func:`sharedctypes.synchronized() " +"` objects now support " +"the :term:`context manager` protocol. (Contributed by Charles-François " +"Natali in :issue:`21565`.)" msgstr "" #: whatsnew/3.5.rst:1468 @@ -2098,16 +2101,16 @@ msgstr "" #: 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`.)" +":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 "" #: 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`.)" +"perform matrix multiplication. (Contributed by Benjamin Peterson " +"in :issue:`21176`.)" msgstr "" #: whatsnew/3.5.rst:1480 @@ -2116,21 +2119,22 @@ msgstr "" #: 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`.)" +"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 "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1495 @@ -2144,8 +2148,8 @@ msgstr "" #: 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 (:const:`~os." -"O_NONBLOCK`.) (Contributed by Victor Stinner in :issue:`22054`.)" +"getting and setting a file descriptor's blocking mode " +"(:const:`~os.O_NONBLOCK`.) (Contributed by Victor Stinner in :issue:`22054`.)" msgstr "" #: whatsnew/3.5.rst:1504 @@ -2157,8 +2161,8 @@ msgstr "" #: 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::" +"common sub-path of each passed pathname. Unlike " +"the :func:`os.path.commonprefix` function, it always returns a valid path::" msgstr "" #: whatsnew/3.5.rst:1512 @@ -2216,16 +2220,18 @@ msgstr "" 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`.)" +"directory. (Contributed by Victor Salgado and Mayank Tripathi " +"in :issue:`19777`.)" msgstr "" #: 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." +"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 "" #: whatsnew/3.5.rst:1555 @@ -2308,10 +2314,10 @@ msgstr "" #: 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::" +"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 "" #: whatsnew/3.5.rst:1611 @@ -2404,9 +2410,9 @@ msgstr "" #: whatsnew/3.5.rst:1677 msgid "" -"The :class:`!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:`!" +"The :class:`!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 "" @@ -2443,16 +2449,16 @@ msgstr "" 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`.)" +"messages. (Contributed by Gavin Chappell and Maciej Szulik " +"in :issue:`16914`.)" msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1715 @@ -2462,8 +2468,8 @@ msgstr "" #: 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`.)" +"a :func:`~collections.namedtuple`. (Contributed by Claudiu Popa " +"in :issue:`18615`.)" msgstr "" #: whatsnew/3.5.rst:1723 @@ -2479,10 +2485,10 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1734 @@ -2496,9 +2502,9 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1746 @@ -2516,11 +2522,12 @@ msgstr "" #: 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." +"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 "" #: whatsnew/3.5.rst:1762 @@ -2547,23 +2554,23 @@ msgstr "" #: 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`." +"*Application-Layer Protocol Negotiation* TLS extension as described " +"in :rfc:`7301`." msgstr "" #: 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." +"The new :meth:`SSLContext.set_alpn_protocols() " +"` can be used to specify which protocols " +"a socket should advertise during the TLS handshake." msgstr "" #: whatsnew/3.5.rst:1783 msgid "" -"The new :meth:`SSLSocket.selected_alpn_protocol() ` returns the protocol that was selected during the " -"TLS handshake. The :const:`~ssl.HAS_ALPN` flag indicates whether ALPN " -"support is present." +"The new :meth:`SSLSocket.selected_alpn_protocol() " +"` returns the protocol that was " +"selected during the TLS handshake. The :const:`~ssl.HAS_ALPN` flag indicates " +"whether ALPN support is present." msgstr "" #: whatsnew/3.5.rst:1790 @@ -2573,15 +2580,15 @@ msgstr "" #: 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`.)" +"query the actual protocol version in use. (Contributed by Antoine Pitrou " +"in :issue:`20421`.)" msgstr "" #: 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`.)" +"The :class:`~ssl.SSLSocket` class now implements " +"a :meth:`SSLSocket.sendfile() ` method. (Contributed " +"by Giampaolo Rodola' in :issue:`17552`.)" msgstr "" #: whatsnew/3.5.rst:1800 @@ -2601,21 +2608,22 @@ msgstr "" #: 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. " +"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 "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1822 @@ -2674,10 +2682,11 @@ msgstr "" 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`.)" +"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 "" #: whatsnew/3.5.rst:1874 @@ -2694,8 +2703,8 @@ msgstr "" #: 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`.)" +"components of the Python version. (Contributed by Paul Moore " +"in :issue:`23437`.)" msgstr "" #: whatsnew/3.5.rst:1888 @@ -2705,16 +2714,16 @@ msgstr "" #: 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`.)" +"``\"x\"`` to request exclusive creation. (Contributed by Berker Peksag " +"in :issue:`21717`.)" msgstr "" #: whatsnew/3.5.rst:1893 msgid "" -"The :meth:`TarFile.extractall() ` and :meth:" -"`TarFile.extract() ` methods now take a keyword " -"argument *numeric_owner*. If set to ``True``, the extracted files and " -"directories will be owned by the numeric ``uid`` and ``gid`` from the " +"The :meth:`TarFile.extractall() ` " +"and :meth:`TarFile.extract() ` methods now take a " +"keyword argument *numeric_owner*. 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`.)" @@ -2734,9 +2743,10 @@ msgstr "" #: 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`.)" +"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 "" #: whatsnew/3.5.rst:1917 @@ -2792,9 +2802,10 @@ msgstr "" #: whatsnew/3.5.rst:1954 msgid "" -"New lightweight classes: :class:`~traceback.TracebackException`, :class:" -"`~traceback.StackSummary`, and :class:`~traceback.FrameSummary`. " -"(Contributed by Robert Collins in :issue:`17911`.)" +"New lightweight " +"classes: :class:`~traceback.TracebackException`, :class:`~traceback.StackSummary`, " +"and :class:`~traceback.FrameSummary`. (Contributed by Robert Collins " +"in :issue:`17911`.)" msgstr "" #: whatsnew/3.5.rst:1958 @@ -2811,16 +2822,16 @@ msgstr "" #: whatsnew/3.5.rst:1966 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`.)" +"` and :class:`generator-like " +"` objects into :term:`awaitables `. " +"(Contributed by Yury Selivanov in :issue:`24017`.)" msgstr "" #: whatsnew/3.5.rst:1972 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`.)" +"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 "" #: whatsnew/3.5.rst:1978 @@ -2839,13 +2850,13 @@ msgstr "" #: whatsnew/3.5.rst:1987 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`.)" +"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 "" #: whatsnew/3.5.rst:1994 @@ -2878,24 +2889,24 @@ msgstr "" #: whatsnew/3.5.rst:2013 msgid "" -"A new :meth:`Mock.assert_not_called() ` method to check if the mock object was called. " -"(Contributed by Kushal Das in :issue:`21262`.)" +"A new :meth:`Mock.assert_not_called() " +"` method to check if the mock object " +"was called. (Contributed by Kushal Das in :issue:`21262`.)" msgstr "" #: whatsnew/3.5.rst:2017 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`.)" +"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 "" #: whatsnew/3.5.rst:2022 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`.)" +"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 "" #: whatsnew/3.5.rst:2028 @@ -2904,35 +2915,38 @@ msgstr "" #: whatsnew/3.5.rst:2030 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`.)" +"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 "" #: whatsnew/3.5.rst:2039 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`.)" +"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 "" #: whatsnew/3.5.rst:2044 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`.)" +"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 "" #: whatsnew/3.5.rst:2048 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`.)" +"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 "" #: whatsnew/3.5.rst:2055 @@ -2941,9 +2955,9 @@ msgstr "" #: whatsnew/3.5.rst:2057 msgid "" -"The *headers* argument of the :class:`headers.Headers ` class constructor is now optional. (Contributed by Pablo Torres " -"Navarrete and SilentGhost in :issue:`5800`.)" +"The *headers* argument of the :class:`headers.Headers " +"` class constructor is now optional. (Contributed " +"by Pablo Torres Navarrete and SilentGhost in :issue:`5800`.)" msgstr "" #: whatsnew/3.5.rst:2063 @@ -2970,9 +2984,9 @@ msgstr "" #: whatsnew/3.5.rst:2077 msgid "" -"SAX parsers now support a character stream of the :class:`xmlreader." -"InputSource ` object. (Contributed by Serhiy " -"Storchaka in :issue:`2175`.)" +"SAX parsers now support a character stream of " +"the :class:`xmlreader.InputSource ` object. " +"(Contributed by Serhiy Storchaka in :issue:`2175`.)" msgstr "" #: whatsnew/3.5.rst:2081 @@ -3004,10 +3018,10 @@ msgstr "" #: whatsnew/3.5.rst:2099 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`.)" +"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 "" #: whatsnew/3.5.rst:2106 @@ -3017,9 +3031,9 @@ msgstr "" #: whatsnew/3.5.rst:2108 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. " +"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 "" @@ -3027,19 +3041,18 @@ msgstr "" 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`.)" +"to allocate memory for these objects. (Contributed by Victor Stinner " +"in :issue:`21233`.)" msgstr "" #: whatsnew/3.5.rst:2119 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`.)" +"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 "" #: whatsnew/3.5.rst:2127 @@ -3051,16 +3064,16 @@ msgstr "" #: whatsnew/3.5.rst:2130 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`.)" +"(Contributed by Serhiy Storchaka in :issue:`15381` and David Wilson " +"in :issue:`22003`.)" msgstr "" #: whatsnew/3.5.rst:2134 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`.)" +"best cases. (Contributed by Serhiy Storchaka in :issue:`20416` " +"and :issue:`23344`.)" msgstr "" #: whatsnew/3.5.rst:2139 @@ -3085,16 +3098,16 @@ msgstr "" #: whatsnew/3.5.rst:2149 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`.)" +"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 "" #: whatsnew/3.5.rst:2154 msgid "" "Method caching was slightly improved, yielding up to 5% performance " -"improvement in some benchmarks. (Contributed by Antoine Pitrou in :issue:" -"`22847`.)" +"improvement in some benchmarks. (Contributed by Antoine Pitrou " +"in :issue:`22847`.)" msgstr "" #: whatsnew/3.5.rst:2158 @@ -3117,10 +3130,11 @@ msgstr "" #: whatsnew/3.5.rst:2167 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`.)" +"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 "" #: whatsnew/3.5.rst:2174 @@ -3166,15 +3180,15 @@ msgstr "" #: whatsnew/3.5.rst:2191 msgid "" "A new :c:func:`PyCodec_NameReplaceErrors` function to replace the unicode " -"encode error with ``\\N{...}`` escapes. (Contributed by Serhiy Storchaka in :" -"issue:`19676`.)" +"encode error with ``\\N{...}`` escapes. (Contributed by Serhiy Storchaka " +"in :issue:`19676`.)" msgstr "" #: whatsnew/3.5.rst:2195 msgid "" "A new :c:func:`PyErr_FormatV` function similar to :c:func:`PyErr_Format`, " -"but accepts a :c:type:`va_list` argument. (Contributed by Antoine Pitrou in :" -"issue:`18711`.)" +"but accepts a :c:type:`va_list` argument. (Contributed by Antoine Pitrou " +"in :issue:`18711`.)" msgstr "" #: whatsnew/3.5.rst:2199 @@ -3187,16 +3201,16 @@ msgstr "" 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`.)" +"phase extension module initialization. (Contributed by Petr Viktorin " +"in :issue:`24268`.)" msgstr "" #: whatsnew/3.5.rst:2207 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.)" +"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 "" #: whatsnew/3.5.rst:2213 @@ -3304,8 +3318,8 @@ msgstr "" 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 " +"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 "" @@ -3331,8 +3345,8 @@ msgstr "" #: whatsnew/3.5.rst:2296 msgid "" -"The :func:`asyncio.async` function is deprecated in favor of :func:`~asyncio." -"ensure_future`." +"The :func:`asyncio.async` function is deprecated in favor " +"of :func:`~asyncio.ensure_future`." msgstr "" #: whatsnew/3.5.rst:2299 @@ -3346,19 +3360,20 @@ msgstr "" #: whatsnew/3.5.rst:2305 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." +"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 "" #: whatsnew/3.5.rst:2312 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`.)" +"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 "" #: whatsnew/3.5.rst:2317 @@ -3372,9 +3387,9 @@ msgstr "" #: whatsnew/3.5.rst:2322 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`.)" +"of :class:`inspect.Signature` are deprecated. Use the " +"new :meth:`Signature.from_callable() ` " +"method instead. (Contributed by Yury Selivanov in :issue:`24248`.)" msgstr "" #: whatsnew/3.5.rst:2327 @@ -3385,9 +3400,9 @@ msgstr "" #: whatsnew/3.5.rst:2330 msgid "" -"The :mod:`inspect` :func:`~inspect.getfullargspec`, :func:`~inspect." -"getcallargs`, and :func:`~inspect.formatargspec` functions are deprecated in " -"favor of the :func:`inspect.signature` API. (Contributed by Yury Selivanov " +"The :mod:`inspect` :func:`~inspect.getfullargspec`, :func:`~inspect.getcallargs`, " +"and :func:`~inspect.formatargspec` functions are deprecated in favor of " +"the :func:`inspect.signature` API. (Contributed by Yury Selivanov " "in :issue:`20438`.)" msgstr "" @@ -3413,10 +3428,10 @@ msgstr "" #: whatsnew/3.5.rst:2346 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`.)" +"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 "" #: whatsnew/3.5.rst:2353 @@ -3504,16 +3519,16 @@ msgstr "" 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." +"obscure and error-prone and has been removed in Python 3.5. " +"See :issue:`13936` for full details." msgstr "" #: whatsnew/3.5.rst:2408 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`.)" +"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 "" #: whatsnew/3.5.rst:2413 @@ -3527,12 +3542,12 @@ msgstr "" #: whatsnew/3.5.rst:2420 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`.)" +"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 "" #: whatsnew/3.5.rst:2426 @@ -3546,11 +3561,11 @@ msgstr "" #: whatsnew/3.5.rst:2432 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`)." +"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 "" #: whatsnew/3.5.rst:2438 @@ -3564,12 +3579,12 @@ msgstr "" #: whatsnew/3.5.rst:2443 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`.)" +"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 "" #: whatsnew/3.5.rst:2451 @@ -3586,28 +3601,29 @@ msgstr "" #: whatsnew/3.5.rst:2459 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`.)" +"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 "" #: whatsnew/3.5.rst:2469 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. sourceless 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." +"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. sourceless " +"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 "" #: whatsnew/3.5.rst:2480 @@ -3651,16 +3667,17 @@ msgid "" "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`.)" +"module and the :func:`help` function. (Contributed by Serhiy Storchaka " +"in :issue:`15582`.)" msgstr "" #: whatsnew/3.5.rst:2507 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`.)" +"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 "" #: whatsnew/3.5.rst:2514 @@ -3669,15 +3686,16 @@ msgstr "" #: whatsnew/3.5.rst:2516 msgid "" -"The undocumented :c:member:`!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." +"The undocumented :c:member:`!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 "" #: whatsnew/3.5.rst:2521 msgid "" -"The :c:type:`PyMemAllocator` structure was renamed to :c:type:" -"`PyMemAllocatorEx` and a new ``calloc`` field was added." +"The :c:type:`PyMemAllocator` structure was renamed " +"to :c:type:`PyMemAllocatorEx` and a new ``calloc`` field was added." msgstr "" #: whatsnew/3.5.rst:2524 @@ -3692,17 +3710,17 @@ msgstr "" msgid "" "Because the lack of the :attr:`~type.__module__` attribute breaks pickling " "and introspection, a deprecation warning is now raised for builtin types " -"without the :attr:`~type.__module__` attribute. This will be an :exc:" -"`AttributeError` in the future. (Contributed by Serhiy Storchaka in :issue:" -"`20204`.)" +"without the :attr:`~type.__module__` attribute. This will be " +"an :exc:`AttributeError` in the future. (Contributed by Serhiy Storchaka " +"in :issue:`20204`.)" msgstr "" #: whatsnew/3.5.rst:2535 msgid "" -"As part of the :pep:`492` implementation, the ``tp_reserved`` slot of :c:" -"type:`PyTypeObject` was replaced with a :c:member:`~PyTypeObject." -"tp_as_async` slot. Refer to :ref:`coro-objects` for new types, structures " -"and functions." +"As part of the :pep:`492` implementation, the ``tp_reserved`` slot " +"of :c:type:`PyTypeObject` was replaced with " +"a :c:member:`~PyTypeObject.tp_as_async` slot. Refer to :ref:`coro-objects` " +"for new types, structures and functions." msgstr "" #: whatsnew/3.5.rst:2542 @@ -3730,8 +3748,8 @@ msgstr "" #: whatsnew/3.5.rst:2556 msgid "" -"More selective regeneration targets are also defined - see :source:`Makefile." -"pre.in` for details." +"More selective regeneration targets are also defined - " +"see :source:`Makefile.pre.in` for details." msgstr "" #: whatsnew/3.5.rst:2572 diff --git a/whatsnew/3.6.po b/whatsnew/3.6.po index 9306695d5..1e1315114 100644 --- a/whatsnew/3.6.po +++ b/whatsnew/3.6.po @@ -83,12 +83,12 @@ msgstr "" #: whatsnew/3.6.rst:80 msgid "" -"The :ref:`dict ` type has been reimplemented to use a :ref:" -"`more compact representation ` based on `a proposal " -"by Raymond Hettinger `_ and similar to the `PyPy dict implementation`_. " -"This resulted in dictionaries using 20% to 25% less memory when compared to " -"Python 3.5." +"The :ref:`dict ` type has been reimplemented to use " +"a :ref:`more compact representation ` based on `a " +"proposal by Raymond Hettinger `_ and similar to the `PyPy dict " +"implementation`_. This resulted in dictionaries using 20% to 25% less " +"memory when compared to Python 3.5." msgstr "" #: whatsnew/3.6.rst:87 @@ -216,8 +216,8 @@ msgstr "" #: whatsnew/3.6.rst:159 msgid "" "``python.exe`` and ``pythonw.exe`` have been marked as long-path aware, " -"which means that the 260 character path limit may no longer apply. See :ref:" -"`removing the MAX_PATH limitation ` for details." +"which means that the 260 character path limit may no longer apply. " +"See :ref:`removing the MAX_PATH limitation ` for details." msgstr "" #: whatsnew/3.6.rst:163 @@ -229,9 +229,9 @@ msgstr "" #: whatsnew/3.6.rst:167 msgid "" -"A ``python36.zip`` file now works as a landmark to infer :envvar:" -"`PYTHONHOME`. See :ref:`the documentation ` for " -"more information." +"A ``python36.zip`` file now works as a landmark to " +"infer :envvar:`PYTHONHOME`. See :ref:`the documentation " +"` for more information." msgstr "" #: whatsnew/3.6.rst:176 @@ -244,8 +244,8 @@ msgstr "" #: whatsnew/3.6.rst:183 msgid "" -":pep:`498` introduces a new kind of string literals: *f-strings*, or :ref:" -"`formatted string literals `." +":pep:`498` introduces a new kind of string literals: *f-strings*, " +"or :ref:`formatted string literals `." msgstr "" #: whatsnew/3.6.rst:186 @@ -473,9 +473,9 @@ msgstr "" #: whatsnew/3.6.rst:348 msgid "" -"In order to allow zero-argument :func:`super` calls to work correctly from :" -"meth:`~object.__init_subclass__` implementations, custom metaclasses must " -"ensure that the new ``__classcell__`` namespace entry is propagated to " +"In order to allow zero-argument :func:`super` calls to work correctly " +"from :meth:`~object.__init_subclass__` implementations, custom metaclasses " +"must ensure that the new ``__classcell__`` namespace entry is propagated to " "``type.__new__`` (as described in :ref:`class-object-creation`)." msgstr "" @@ -497,13 +497,13 @@ msgstr "" #: whatsnew/3.6.rst:366 msgid "" -":pep:`487` extends the descriptor protocol to include the new optional :meth:" -"`~object.__set_name__` method. 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. In other words, " -"instances of descriptors can now know the attribute name of the descriptor " -"in the owner class::" +":pep:`487` extends the descriptor protocol to include the new " +"optional :meth:`~object.__set_name__` method. 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. In other " +"words, instances of descriptors can now know the attribute name of the " +"descriptor in the owner class::" msgstr "" #: whatsnew/3.6.rst:374 @@ -535,13 +535,13 @@ msgstr "" #: whatsnew/3.6.rst:404 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." +"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 "" #: whatsnew/3.6.rst:413 @@ -551,8 +551,8 @@ msgid "" "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. " +"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." @@ -560,26 +560,28 @@ msgstr "" #: whatsnew/3.6.rst:426 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, and most other functions and classes in the standard " -"library. The :class:`os.DirEntry` class and relevant classes in :mod:" -"`pathlib` have also been updated to implement :class:`os.PathLike`." +"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, and most other functions and " +"classes in the standard library. The :class:`os.DirEntry` class and " +"relevant classes in :mod:`pathlib` have also been updated to " +"implement :class:`os.PathLike`." msgstr "" #: whatsnew/3.6.rst:433 msgid "" "The hope 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)." +"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 "" #: whatsnew/3.6.rst:440 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::" +"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 "" #: whatsnew/3.6.rst:444 @@ -627,9 +629,10 @@ msgstr "" #: whatsnew/3.6.rst:476 msgid "" -":pep:`495` adds the new *fold* attribute to instances of :class:`datetime." -"datetime` and :class:`datetime.time` classes to differentiate between two " -"moments in time for which local times are the same::" +":pep:`495` adds the new *fold* attribute to instances " +"of :class:`datetime.datetime` and :class:`datetime.time` classes to " +"differentiate between two moments in time for which local times are the " +"same::" msgstr "" #: whatsnew/3.6.rst:480 @@ -678,17 +681,17 @@ msgstr "" 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'``." +"on Windows, provided those bytes are encoded with the encoding returned " +"by :func:`sys.getfilesystemencoding`, which now defaults to ``'utf-8'``." msgstr "" #: whatsnew/3.6.rst:516 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`." +"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 "" #: whatsnew/3.6.rst:522 @@ -704,8 +707,8 @@ msgstr "" #: whatsnew/3.6.rst:531 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." +"provide correctly read str objects to Python code. ``sys.stdin``, " +"``sys.stdout`` and ``sys.stderr`` now default to utf-8 encoding." msgstr "" #: whatsnew/3.6.rst:535 @@ -736,8 +739,9 @@ msgstr "" #: whatsnew/3.6.rst:554 msgid "" -"Also, the effective default class *execution* namespace (returned from :ref:" -"`type.__prepare__() `) is now an insertion-order-preserving mapping." +"Also, the effective default class *execution* namespace (returned " +"from :ref:`type.__prepare__() `) is now an insertion-order-" +"preserving mapping." msgstr "" #: whatsnew/3.6.rst:560 @@ -771,9 +775,9 @@ msgid "" "The :ref:`dict ` type now uses a \"compact\" representation " "based on `a proposal by Raymond Hettinger `_ which was `first implemented by PyPy " -"`_. The memory usage of the new :func:`dict` is between 20% and 25% " -"smaller compared to Python 3.5." +"`_. The memory usage of the new :func:`dict` is between 20% and " +"25% smaller compared to Python 3.5." msgstr "" #: whatsnew/3.6.rst:591 @@ -784,8 +788,8 @@ msgid "" "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)." +"versions of the language where random iteration order is still in effect, " +"e.g. Python 3.5)." msgstr "" #: whatsnew/3.6.rst:600 @@ -860,8 +864,9 @@ msgstr "" #: whatsnew/3.6.rst:647 msgid "" -"Detect violations of the Python memory allocator API. For example, :c:func:" -"`PyObject_Free` called on a memory block allocated by :c:func:`PyMem_Malloc`." +"Detect violations of the Python memory allocator API. For " +"example, :c:func:`PyObject_Free` called on a memory block allocated " +"by :c:func:`PyMem_Malloc`." msgstr "" #: whatsnew/3.6.rst:650 @@ -900,8 +905,9 @@ msgstr "" #: whatsnew/3.6.rst:666 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." +"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 "" #: whatsnew/3.6.rst:670 @@ -1008,8 +1014,8 @@ msgstr "" #: whatsnew/3.6.rst:742 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 :exc:" -"`SyntaxWarning`." +"first use of the affected name in the same scope. Previously this was " +"a :exc:`SyntaxWarning`." msgstr "" #: whatsnew/3.6.rst:746 @@ -1029,10 +1035,10 @@ msgstr "" #: whatsnew/3.6.rst:757 msgid "" -"Import now raises the new exception :exc:`ModuleNotFoundError` (subclass of :" -"exc:`ImportError`) when it cannot find a module. Code that currently checks " -"for ImportError (in try-except) will still work. (Contributed by Eric Snow " -"in :issue:`15767`.)" +"Import now raises the new exception :exc:`ModuleNotFoundError` (subclass " +"of :exc:`ImportError`) when it cannot find a module. Code that currently " +"checks for ImportError (in try-except) will still work. (Contributed by Eric " +"Snow in :issue:`15767`.)" msgstr "" #: whatsnew/3.6.rst:762 @@ -1061,8 +1067,8 @@ msgstr "" #: whatsnew/3.6.rst:781 msgid "" "Note that the pseudo-random generators in the :mod:`random` module should " -"*NOT* be used for security purposes. Use :mod:`secrets` on Python 3.6+ and :" -"func:`os.urandom` on Python 3.5 and earlier." +"*NOT* be used for security purposes. Use :mod:`secrets` on Python 3.6+ " +"and :func:`os.urandom` on Python 3.5 and earlier." msgstr "" #: whatsnew/3.6.rst:787 @@ -1167,9 +1173,9 @@ msgstr "" #: whatsnew/3.6.rst:850 msgid "" -"New :meth:`loop.get_exception_handler() ` method to get the current exception handler. " -"(Contributed by Yury Selivanov in :issue:`27040`.)" +"New :meth:`loop.get_exception_handler() " +"` method to get the current exception " +"handler. (Contributed by Yury Selivanov in :issue:`27040`.)" msgstr "" #: whatsnew/3.6.rst:854 @@ -1181,9 +1187,9 @@ msgstr "" #: whatsnew/3.6.rst:859 msgid "" -"The performance of :meth:`StreamReader.readexactly() ` has been improved. (Contributed by Mark Korenberg in :issue:" -"`28370`.)" +"The performance of :meth:`StreamReader.readexactly() " +"` has been improved. (Contributed by Mark " +"Korenberg in :issue:`28370`.)" msgstr "" #: whatsnew/3.6.rst:863 @@ -1210,9 +1216,9 @@ msgstr "" #: whatsnew/3.6.rst:879 msgid "" -"New :meth:`loop.connect_accepted_socket() ` method to be used by servers that accept " -"connections outside of asyncio, but that use asyncio to handle them. " +"New :meth:`loop.connect_accepted_socket() " +"` method to be used by servers that " +"accept connections outside of asyncio, but that use asyncio to handle them. " "(Contributed by Jim Fulton in :issue:`27392`.)" msgstr "" @@ -1260,10 +1266,10 @@ msgstr "" #: whatsnew/3.6.rst:914 msgid "" -"New constants: :const:`cmath.inf` and :const:`cmath.nan` to match :const:" -"`math.inf` and :const:`math.nan`, and also :const:`cmath.infj` and :const:" -"`cmath.nanj` to match the format used by complex repr. (Contributed by Mark " -"Dickinson in :issue:`23229`.)" +"New constants: :const:`cmath.inf` and :const:`cmath.nan` to " +"match :const:`math.inf` and :const:`math.nan`, and also :const:`cmath.infj` " +"and :const:`cmath.nanj` to match the format used by complex repr. " +"(Contributed by Mark Dickinson in :issue:`23229`.)" msgstr "" #: whatsnew/3.6.rst:921 @@ -1287,16 +1293,16 @@ msgstr "" #: whatsnew/3.6.rst:931 msgid "" "The new :class:`~collections.abc.AsyncGenerator` abstract base class " -"represents asynchronous generators. (Contributed by Yury Selivanov in :issue:" -"`28720`.)" +"represents asynchronous generators. (Contributed by Yury Selivanov " +"in :issue:`28720`.)" msgstr "" #: whatsnew/3.6.rst:935 msgid "" "The :func:`~collections.namedtuple` function now accepts an optional keyword " -"argument *module*, which, when specified, is used for the :attr:`~type." -"__module__` attribute of the returned named tuple class. (Contributed by " -"Raymond Hettinger in :issue:`17941`.)" +"argument *module*, which, when specified, is used for " +"the :attr:`~type.__module__` attribute of the returned named tuple class. " +"(Contributed by Raymond Hettinger in :issue:`17941`.)" msgstr "" #: whatsnew/3.6.rst:2295 @@ -1332,9 +1338,9 @@ 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`.)" +"``__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 "" #: whatsnew/3.6.rst:971 @@ -1353,10 +1359,10 @@ msgstr "" #: whatsnew/3.6.rst:981 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`.)" +"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 "" #: whatsnew/3.6.rst:986 @@ -1370,8 +1376,8 @@ msgstr "" #: whatsnew/3.6.rst:991 msgid "" "The :meth:`datetime.combine() ` now accepts an " -"optional *tzinfo* argument. (Contributed by Alexander Belopolsky in :issue:" -"`27661`.)" +"optional *tzinfo* argument. (Contributed by Alexander Belopolsky " +"in :issue:`27661`.)" msgstr "" #: whatsnew/3.6.rst:997 @@ -1381,9 +1387,9 @@ msgstr "" #: whatsnew/3.6.rst:999 msgid "" "New :meth:`Decimal.as_integer_ratio() ` " -"method that returns a pair ``(n, d)`` of integers that represent the given :" -"class:`~decimal.Decimal` instance as a fraction, in lowest terms and with a " -"positive denominator::" +"method that returns a pair ``(n, d)`` of integers that represent the " +"given :class:`~decimal.Decimal` instance as a fraction, in lowest terms and " +"with a positive denominator::" msgstr "" #: whatsnew/3.6.rst:1004 @@ -1402,9 +1408,9 @@ msgstr "" #: whatsnew/3.6.rst:1014 msgid "" -"The ``default_format`` attribute has been removed from ``distutils.command." -"sdist.sdist`` and the ``formats`` attribute defaults to ``['gztar']``. " -"Although not anticipated, any code relying on the presence of " +"The ``default_format`` attribute has been removed from " +"``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 "" @@ -1418,8 +1424,8 @@ 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`.)" +"documentation for the legacy API. (Contributed by R. David Murray " +"in :issue:`24277`.)" msgstr "" #: whatsnew/3.6.rst:1029 @@ -1436,12 +1442,13 @@ msgstr "" #: whatsnew/3.6.rst:1035 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`.)" +"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 "" #: whatsnew/3.6.rst:1044 @@ -1461,16 +1468,16 @@ msgstr "" #: whatsnew/3.6.rst:1054 msgid "" -"Two new enumeration base classes have been added to the :mod:`enum` module: :" -"class:`~enum.Flag` and :class:`~enum.IntFlags`. Both are used to define " -"constants that can be combined using the bitwise operators. (Contributed by " -"Ethan Furman in :issue:`23591`.)" +"Two new enumeration base classes have been added to the :mod:`enum` " +"module: :class:`~enum.Flag` and :class:`~enum.IntFlags`. Both are used to " +"define constants that can be combined using the bitwise operators. " +"(Contributed by Ethan Furman in :issue:`23591`.)" msgstr "" #: whatsnew/3.6.rst:1059 msgid "" -"Many standard library modules have been updated to use the :class:`~enum." -"IntFlags` class for their constants." +"Many standard library modules have been updated to use " +"the :class:`~enum.IntFlags` class for their constants." msgstr "" #: whatsnew/3.6.rst:1062 @@ -1533,19 +1540,19 @@ msgstr "" #: whatsnew/3.6.rst:1102 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.)" +"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 "" #: whatsnew/3.6.rst:1109 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`.)" +"available with OpenSSL 1.1.0 and newer. (Contributed by Christian Heimes " +"in :issue:`27928`.)" msgstr "" #: whatsnew/3.6.rst:1114 @@ -1554,10 +1561,10 @@ msgstr "" #: whatsnew/3.6.rst:1116 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`.)" +":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 "" #: whatsnew/3.6.rst:1123 @@ -1580,10 +1587,10 @@ msgid "" "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.)" +"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 "" #: whatsnew/3.6.rst:1141 @@ -1599,8 +1606,8 @@ msgstr "" #: whatsnew/3.6.rst:1147 msgid "" -"Multiple fixes for autocompletion. (Contributed by Louie Lu in :issue:" -"`15786`.)" +"Multiple fixes for autocompletion. (Contributed by Louie Lu " +"in :issue:`15786`.)" msgstr "" #: whatsnew/3.6.rst:1149 @@ -1651,8 +1658,8 @@ msgid "" "Editor code context option revised. Box displays all context lines up to " "maxlines. Clicking on a context line jumps the editor to that line. " "Context colors for custom themes is added to Highlights tab of Settings " -"dialog. (Contributed by Cheryl Sabella and Terry Jan Reedy in :issue:" -"`33642`, :issue:`33768`, and :issue:`33679`.)" +"dialog. (Contributed by Cheryl Sabella and Terry Jan Reedy " +"in :issue:`33642`, :issue:`33768`, and :issue:`33679`.)" msgstr "" #: whatsnew/3.6.rst:1182 @@ -1684,26 +1691,26 @@ msgstr "" #: whatsnew/3.6.rst:1201 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. (Contributed by Eric " -"Snow in :issue:`15767`.)" +"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. (Contributed by " +"Eric Snow in :issue:`15767`.)" msgstr "" #: whatsnew/3.6.rst:1206 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`." +":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 "" #: whatsnew/3.6.rst:1212 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`." +":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 "" #: whatsnew/3.6.rst:1219 @@ -1720,12 +1727,12 @@ msgstr "" #: whatsnew/3.6.rst:1226 msgid "" -"To reduce code churn when upgrading from Python 2.7 and the legacy :func:" -"`inspect.getargspec` API, the previously documented deprecation of :func:" -"`inspect.getfullargspec` has been reversed. While this function is " -"convenient for single/source Python 2/3 code bases, the richer :func:" -"`inspect.signature` interface remains the recommended approach for new code. " -"(Contributed by Nick Coghlan in :issue:`27172`)" +"To reduce code churn when upgrading from Python 2.7 and the " +"legacy :func:`inspect.getargspec` API, the previously documented deprecation " +"of :func:`inspect.getfullargspec` has been reversed. While this function is " +"convenient for single/source Python 2/3 code bases, the " +"richer :func:`inspect.signature` interface remains the recommended approach " +"for new code. (Contributed by Nick Coghlan in :issue:`27172`)" msgstr "" #: whatsnew/3.6.rst:1235 @@ -1745,10 +1752,10 @@ msgstr "" #: whatsnew/3.6.rst:1245 msgid "" -"The new :meth:`WatchedFileHandler.reopenIfNeeded() ` method has been added to add the ability " -"to check if the log file needs to be reopened. (Contributed by Marian Horban " -"in :issue:`24884`.)" +"The new :meth:`WatchedFileHandler.reopenIfNeeded() " +"` method has been added " +"to add the ability to check if the log file needs to be reopened. " +"(Contributed by Marian Horban in :issue:`24884`.)" msgstr "" #: whatsnew/3.6.rst:1252 @@ -1768,9 +1775,9 @@ msgstr "" #: whatsnew/3.6.rst:1262 msgid "" -":ref:`Proxy Objects ` returned by :func:" -"`multiprocessing.Manager` can now be nested. (Contributed by Davin Potts in :" -"issue:`6766`.)" +":ref:`Proxy Objects ` returned " +"by :func:`multiprocessing.Manager` can now be nested. (Contributed by Davin " +"Potts in :issue:`6766`.)" msgstr "" #: whatsnew/3.6.rst:2021 @@ -1790,11 +1797,12 @@ msgstr "" #: whatsnew/3.6.rst:1276 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`.)" +"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 "" #: whatsnew/3.6.rst:1286 @@ -1884,24 +1892,24 @@ msgstr "" #: whatsnew/3.6.rst:1347 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'``. " +"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 "" #: whatsnew/3.6.rst:1352 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`.)" +"to ``group()``. So ``mo['name']`` is now equivalent to " +"``mo.group('name')``. (Contributed by Eric Smith in :issue:`24454`.)" msgstr "" #: whatsnew/3.6.rst:1356 msgid "" -":class:`~re.Match` objects now support :meth:`index-like objects ` as group indices. (Contributed by Jeroen Demeyer and Xiang Zhang " -"in :issue:`27177`.)" +":class:`~re.Match` objects now support :meth:`index-like objects " +"` as group indices. (Contributed by Jeroen Demeyer and " +"Xiang Zhang in :issue:`27177`.)" msgstr "" #: whatsnew/3.6.rst:1363 @@ -1911,8 +1919,8 @@ msgstr "" #: whatsnew/3.6.rst:1365 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`.)" +"addition of input to the history list. (Contributed by Tyler Crompton " +"in :issue:`26870`.)" msgstr "" #: whatsnew/3.6.rst:1371 @@ -1923,8 +1931,8 @@ msgstr "" 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`.)" +"keywords. (Contributed by Serhiy Storchaka in :issue:`25011` " +"and :issue:`25209`.)" msgstr "" #: whatsnew/3.6.rst:1379 @@ -1966,9 +1974,9 @@ msgstr "" #: whatsnew/3.6.rst:1406 msgid "" -"The :func:`~socket.socket.ioctl` function now supports the :const:`~socket." -"SIO_LOOPBACK_FAST_PATH` control code. (Contributed by Daniel Stokes in :" -"issue:`26536`.)" +"The :func:`~socket.socket.ioctl` function now supports " +"the :const:`~socket.SIO_LOOPBACK_FAST_PATH` control code. (Contributed by " +"Daniel Stokes in :issue:`26536`.)" msgstr "" #: whatsnew/3.6.rst:1410 @@ -1981,16 +1989,16 @@ msgstr "" #: whatsnew/3.6.rst:1414 msgid "" "The :meth:`~socket.socket.setsockopt` now supports the ``setsockopt(level, " -"optname, None, optlen: int)`` form. (Contributed by Christian Heimes in :" -"issue:`27744`.)" +"optname, None, optlen: int)`` form. (Contributed by Christian Heimes " +"in :issue:`27744`.)" msgstr "" #: whatsnew/3.6.rst:1418 msgid "" "The socket module now supports the address family :const:`~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.)" +"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 "" #: whatsnew/3.6.rst:1424 @@ -2005,19 +2013,19 @@ msgstr "" #: whatsnew/3.6.rst:1431 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`.)" +"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 "" #: whatsnew/3.6.rst:1437 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`.)" +"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 "" #: whatsnew/3.6.rst:2037 @@ -2033,8 +2041,8 @@ msgstr "" #: whatsnew/3.6.rst:1450 msgid "" "3DES has been removed from the default cipher suites and ChaCha20 Poly1305 " -"cipher suites have been added. (Contributed by Christian Heimes in :issue:" -"`27850` and :issue:`27766`.)" +"cipher suites have been added. (Contributed by Christian Heimes " +"in :issue:`27850` and :issue:`27766`.)" msgstr "" #: whatsnew/3.6.rst:1454 @@ -2059,8 +2067,9 @@ msgstr "" #: whatsnew/3.6.rst:1467 msgid "" -"All constants and flags have been converted to :class:`~enum.IntEnum` and :" -"class:`~enum.IntFlags`. (Contributed by Christian Heimes in :issue:`28025`.)" +"All constants and flags have been converted to :class:`~enum.IntEnum` " +"and :class:`~enum.IntFlags`. (Contributed by Christian Heimes " +"in :issue:`28025`.)" msgstr "" #: whatsnew/3.6.rst:1471 @@ -2071,9 +2080,10 @@ msgstr "" #: whatsnew/3.6.rst:1475 msgid "" -"Added :attr:`ssl.SSLContext.post_handshake_auth` to enable and :meth:`ssl." -"SSLSocket.verify_client_post_handshake` to initiate TLS 1.3 post-handshake " -"authentication. (Contributed by Christian Heimes in :gh:`78851`.)" +"Added :attr:`ssl.SSLContext.post_handshake_auth` to enable " +"and :meth:`ssl.SSLSocket.verify_client_post_handshake` to initiate TLS 1.3 " +"post-handshake authentication. (Contributed by Christian Heimes " +"in :gh:`78851`.)" msgstr "" #: whatsnew/3.6.rst:1481 @@ -2093,8 +2103,8 @@ msgstr "" #: whatsnew/3.6.rst:1490 msgid "" ":mod:`struct` now supports IEEE 754 half-precision floats via the ``'e'`` " -"format specifier. (Contributed by Eli Stevens, Mark Dickinson in :issue:" -"`11734`.)" +"format specifier. (Contributed by Eli Stevens, Mark Dickinson " +"in :issue:`11734`.)" msgstr "" #: whatsnew/3.6.rst:1496 @@ -2105,9 +2115,9 @@ msgstr "" 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 explicitly call the :meth:`~subprocess." -"Popen.wait` method to read the exit status of the child process. " -"(Contributed by Victor Stinner in :issue:`26741`.)" +"protocol (``with proc: ...``) or explicitly call " +"the :meth:`~subprocess.Popen.wait` method to read the exit status of the " +"child process. (Contributed by Victor Stinner in :issue:`26741`.)" msgstr "" #: whatsnew/3.6.rst:1504 @@ -2154,8 +2164,8 @@ msgstr "" #: whatsnew/3.6.rst:1534 msgid "" -"The :class:`~time.struct_time` attributes :attr:`tm_gmtoff` and :attr:" -"`tm_zone` are now available on all platforms." +"The :class:`~time.struct_time` attributes :attr:`tm_gmtoff` " +"and :attr:`tm_zone` are now available on all platforms." msgstr "" #: whatsnew/3.6.rst:1539 @@ -2182,13 +2192,14 @@ msgstr "" #: whatsnew/3.6.rst:1554 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`)." +"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 "" #: whatsnew/3.6.rst:1567 @@ -2254,22 +2265,22 @@ msgstr "" msgid "" "The :mod:`typing` module has a much improved support for generic type " "aliases. For example ``Dict[str, Tuple[S, T]]`` is now a valid type " -"annotation. (Contributed by Guido van Rossum in `Github #195 `_.)" +"annotation. (Contributed by Guido van Rossum in `Github #195 `_.)" msgstr "" #: whatsnew/3.6.rst:1614 msgid "" -"The :class:`typing.ContextManager` class has been added for representing :" -"class:`contextlib.AbstractContextManager`. (Contributed by Brett Cannon in :" -"issue:`25609`.)" +"The :class:`typing.ContextManager` class has been added for " +"representing :class:`contextlib.AbstractContextManager`. (Contributed by " +"Brett Cannon in :issue:`25609`.)" msgstr "" #: whatsnew/3.6.rst:1618 msgid "" -"The :class:`typing.Collection` class has been added for representing :class:" -"`collections.abc.Collection`. (Contributed by Ivan Levkivskyi in :issue:" -"`27598`.)" +"The :class:`typing.Collection` class has been added for " +"representing :class:`collections.abc.Collection`. (Contributed by Ivan " +"Levkivskyi in :issue:`27598`.)" msgstr "" #: whatsnew/3.6.rst:1622 @@ -2278,16 +2289,16 @@ msgid "" "variables. 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. (Contributed by " -"Ivan Levkivskyi in `Github #280 `_.)" +"Ivan Levkivskyi in `Github #280 `_.)" msgstr "" #: whatsnew/3.6.rst:1629 msgid "" "A new :const:`~typing.TYPE_CHECKING` constant that is assumed to be ``True`` " "by the static type checkers, but is ``False`` at runtime. (Contributed by " -"Guido van Rossum in `Github #230 `_.)" +"Guido van Rossum in `Github #230 `_.)" msgstr "" #: whatsnew/3.6.rst:1634 @@ -2331,10 +2342,10 @@ msgstr "" #: whatsnew/3.6.rst:1660 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`.)" +"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 "" #: whatsnew/3.6.rst:1666 @@ -2351,9 +2362,10 @@ msgstr "" #: whatsnew/3.6.rst:1675 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`.)" +"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 "" #: whatsnew/3.6.rst:1683 @@ -2384,11 +2396,11 @@ msgstr "" #: whatsnew/3.6.rst:1701 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`)." +"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 "" #: whatsnew/3.6.rst:1707 @@ -2431,9 +2443,9 @@ msgstr "" #: whatsnew/3.6.rst:1730 msgid "" -"The \"Object allocated at\" traceback is new and is only displayed if :mod:" -"`tracemalloc` is tracing Python memory allocations and if the :mod:" -"`warnings` module was already imported." +"The \"Object allocated at\" traceback is new and is only displayed " +"if :mod:`tracemalloc` is tracing Python memory allocations and if " +"the :mod:`warnings` module was already imported." msgstr "" #: whatsnew/3.6.rst:1736 @@ -2452,9 +2464,9 @@ msgstr "" #: whatsnew/3.6.rst:1745 msgid "" -"Allowed keyword arguments to be passed to :func:`Beep `, :" -"func:`MessageBeep `, and :func:`PlaySound ` (:issue:`27982`)." +"Allowed keyword arguments to be passed to :func:`Beep " +"`, :func:`MessageBeep `, " +"and :func:`PlaySound ` (:issue:`27982`)." msgstr "" #: whatsnew/3.6.rst:1751 @@ -2507,8 +2519,8 @@ msgstr "" msgid "" "The Python interpreter now uses a 16-bit wordcode instead of bytecode which " "made a number of opcode optimizations possible. (Contributed by Demur Rumed " -"with input and reviews from Serhiy Storchaka and Victor Stinner in :issue:" -"`26647` and :issue:`28050`.)" +"with input and reviews from Serhiy Storchaka and Victor Stinner " +"in :issue:`26647` and :issue:`28050`.)" msgstr "" #: whatsnew/3.6.rst:1790 @@ -2540,8 +2552,8 @@ msgstr "" #: whatsnew/3.6.rst:1804 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`)." +"error handler ``surrogateescape`` (Contributed by Victor Stinner " +"in :issue:`25227`)." msgstr "" #: whatsnew/3.6.rst:1808 @@ -2573,8 +2585,8 @@ msgstr "" #: whatsnew/3.6.rst:1822 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`)." +"between 2x and 3.5x faster. (Contributed by Victor Stinner " +"in :issue:`25401`)." msgstr "" #: whatsnew/3.6.rst:1825 @@ -2585,19 +2597,19 @@ msgstr "" #: whatsnew/3.6.rst:1828 msgid "" -"Allocator functions of the :c:func:`PyMem_Malloc` domain (:c:macro:" -"`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. " +"Allocator functions of the :c:func:`PyMem_Malloc` domain " +"(:c:macro:`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 "" #: whatsnew/3.6.rst:1835 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`)." +"deserializing many small objects (Contributed by Victor Stinner " +"in :issue:`27056`)." msgstr "" #: whatsnew/3.6.rst:1839 @@ -2611,30 +2623,30 @@ msgstr "" #: whatsnew/3.6.rst:1845 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`)." +"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 "" #: whatsnew/3.6.rst:1849 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`)." +"about 1.5--4 times faster. (Contributed by Serhiy Storchaka " +"in :issue:`26032`)." msgstr "" #: whatsnew/3.6.rst:1853 msgid "" ":class:`xml.etree.ElementTree` parsing, iteration and deepcopy performance " -"has been significantly improved. (Contributed by Serhiy Storchaka in :issue:" -"`25638`, :issue:`25873`, and :issue:`25869`.)" +"has been significantly improved. (Contributed by Serhiy Storchaka " +"in :issue:`25638`, :issue:`25873`, and :issue:`25869`.)" msgstr "" #: whatsnew/3.6.rst:1858 msgid "" "Creation of :class:`fractions.Fraction` instances from floats and decimals " -"is now 2 to 3 times faster. (Contributed by Serhiy Storchaka in :issue:" -"`25971`.)" +"is now 2 to 3 times faster. (Contributed by Serhiy Storchaka " +"in :issue:`25971`.)" msgstr "" #: whatsnew/3.6.rst:1864 @@ -2645,8 +2657,8 @@ msgstr "" msgid "" "Python now requires some C99 support in the toolchain to build. Most " "notably, Python now uses standard integer types and macros in place of " -"custom macros like ``PY_LONG_LONG``. For more information, see :pep:`7` and :" -"issue:`17884`." +"custom macros like ``PY_LONG_LONG``. For more information, see :pep:`7` " +"and :issue:`17884`." msgstr "" #: whatsnew/3.6.rst:1871 @@ -2654,8 +2666,8 @@ msgid "" "Cross-compiling CPython with the Android NDK and the Android API level set " "to 21 (Android 5.0 Lollipop) 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`." +"emulator with only about 16 tests failures. See the Android meta-" +"issue :issue:`26865`." msgstr "" #: whatsnew/3.6.rst:1876 @@ -2702,8 +2714,8 @@ msgstr "" #: whatsnew/3.6.rst:1901 msgid "" -"The new :c:func:`PyErr_ResourceWarning` function can be used to generate a :" -"exc:`ResourceWarning` providing the source of the resource allocation. " +"The new :c:func:`PyErr_ResourceWarning` function can be used to generate " +"a :exc:`ResourceWarning` providing the source of the resource allocation. " "(Contributed by Victor Stinner in :issue:`26567`.)" msgstr "" @@ -2769,16 +2781,16 @@ msgid "" "The :meth:`__aiter__` method is now expected to return an asynchronous " "iterator directly instead of returning an awaitable as previously. Doing the " "former will trigger a :exc:`DeprecationWarning`. Backward compatibility " -"will be removed in Python 3.7. (Contributed by Yury Selivanov in :issue:" -"`27243`.)" +"will be removed in Python 3.7. (Contributed by Yury Selivanov " +"in :issue:`27243`.)" msgstr "" #: whatsnew/3.6.rst:1951 msgid "" "A backslash-character pair that is not a valid escape sequence now generates " -"a :exc:`DeprecationWarning`. Although this will eventually become a :exc:" -"`SyntaxError`, that will not be for several Python releases. (Contributed by " -"Emanuel Barry in :issue:`27364`.)" +"a :exc:`DeprecationWarning`. Although this will eventually become " +"a :exc:`SyntaxError`, that will not be for several Python releases. " +"(Contributed by Emanuel Barry in :issue:`27364`.)" msgstr "" #: whatsnew/3.6.rst:1956 @@ -2829,8 +2841,8 @@ msgstr "" msgid "" "The undocumented ``extra_path`` argument to the ``distutils.Distribution`` " "constructor is now considered deprecated and will raise a warning if set. " -"Support for this parameter will be removed in a future Python release. See :" -"issue:`27919` for details." +"Support for this parameter will be removed in a future Python release. " +"See :issue:`27919` for details." msgstr "" #: whatsnew/3.6.rst:1999 @@ -2845,12 +2857,12 @@ msgstr "" #: whatsnew/3.6.rst:2009 msgid "" -"The :meth:`importlib.machinery.SourceFileLoader.load_module` and :meth:" -"`importlib.machinery.SourcelessFileLoader.load_module` methods 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`." +"The :meth:`importlib.machinery.SourceFileLoader.load_module` " +"and :meth:`importlib.machinery.SourcelessFileLoader.load_module` methods 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 "" #: whatsnew/3.6.rst:2016 @@ -2864,8 +2876,8 @@ msgstr "" 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`.)" +"functions is now deprecated. (Contributed by Serhiy Storchaka " +"in :issue:`25791` and :issue:`26754`.)" msgstr "" #: whatsnew/3.6.rst:2031 @@ -2886,9 +2898,9 @@ msgstr "" #: whatsnew/3.6.rst:2043 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`.)" +"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 "" #: whatsnew/3.6.rst:2048 @@ -2919,9 +2931,10 @@ msgstr "" #: whatsnew/3.6.rst:2073 msgid "" -"As mitigation against DTD and external entity retrieval, the :mod:`xml.dom." -"minidom` and :mod:`xml.sax` modules no longer process external entities by " -"default. (Contributed by Christian Heimes in :gh:`61441`.)" +"As mitigation against DTD and external entity retrieval, " +"the :mod:`xml.dom.minidom` and :mod:`xml.sax` modules no longer process " +"external entities by default. (Contributed by Christian Heimes " +"in :gh:`61441`.)" msgstr "" #: whatsnew/3.6.rst:2080 @@ -2931,9 +2944,9 @@ msgstr "" #: whatsnew/3.6.rst:2082 msgid "" "Undocumented functions :c:func:`!PyUnicode_AsEncodedObject`, :c:func:`!" -"PyUnicode_AsDecodedObject`, :c:func:`!PyUnicode_AsEncodedUnicode` and :c:" -"func:`!PyUnicode_AsDecodedUnicode` are deprecated now. Use the :ref:`generic " -"codec based API ` instead." +"PyUnicode_AsDecodedObject`, :c:func:`!PyUnicode_AsEncodedUnicode` " +"and :c:func:`!PyUnicode_AsDecodedUnicode` are deprecated now. Use " +"the :ref:`generic codec based API ` instead." msgstr "" #: whatsnew/3.6.rst:2089 @@ -2960,41 +2973,41 @@ msgstr "" #: whatsnew/3.6.rst:2104 msgid "" "Unknown escapes consisting of ``'\\'`` and an ASCII letter in regular " -"expressions will now cause an error. In replacement templates for :func:`re." -"sub` they are still allowed, but deprecated. The :const:`re.LOCALE` flag can " -"now only be used with binary patterns." +"expressions will now cause an error. In replacement templates " +"for :func:`re.sub` they are still allowed, but deprecated. " +"The :const:`re.LOCALE` flag can now only be used with binary patterns." msgstr "" #: whatsnew/3.6.rst:2109 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. (Contributed by Yury Selivanov in :issue:`13248`.)" +"``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. (Contributed by Yury Selivanov in :issue:`13248`.)" msgstr "" #: whatsnew/3.6.rst:2114 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." +"``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 "" #: whatsnew/3.6.rst:2121 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)." +"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 "" #: whatsnew/3.6.rst:2125 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." +"Use :class:`io.TextIOWrapper` for reading compressed text files " +"in :term:`universal newlines` mode." msgstr "" #: whatsnew/3.6.rst:2130 @@ -3031,8 +3044,8 @@ 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`.)" +"to ``stderr`` instead of ``stdout``. (Contributed by Serhiy Storchaka " +"in :issue:`23034`.)" msgstr "" #: whatsnew/3.6.rst:2158 @@ -3042,8 +3055,8 @@ msgstr "" #: whatsnew/3.6.rst:2160 msgid "" ":func:`open() ` will no longer allow combining the ``'U'`` mode flag " -"with ``'+'``. (Contributed by Jeff Balogh and John O'Connor in :issue:" -"`2091`.)" +"with ``'+'``. (Contributed by Jeff Balogh and John O'Connor " +"in :issue:`2091`.)" msgstr "" #: whatsnew/3.6.rst:2164 @@ -3060,8 +3073,8 @@ msgstr "" #: whatsnew/3.6.rst:2170 msgid "" -"When :meth:`importlib.abc.Loader.exec_module` is defined, :meth:`importlib." -"abc.Loader.create_module` must also be defined." +"When :meth:`importlib.abc.Loader.exec_module` is " +"defined, :meth:`importlib.abc.Loader.create_module` must also be defined." msgstr "" #: whatsnew/3.6.rst:2173 @@ -3074,13 +3087,14 @@ msgstr "" msgid "" "The format of the :attr:`~codeobject.co_lnotab` attribute of code objects " "changed to support a negative line number delta. By default, Python does not " -"emit bytecode with a negative line number delta. Functions using :attr:" -"`frame.f_lineno`, ``PyFrame_GetLineNumber()`` or ``PyCode_Addr2Line()`` are " -"not affected. Functions directly decoding :attr:`!co_lnotab` should be " -"updated to use a signed 8-bit integer type for the line number delta, but " -"this is only required to support applications using a negative line number " -"delta. See ``Objects/lnotab_notes.txt`` for the :attr:`!co_lnotab` format " -"and how to decode it, and see the :pep:`511` for the rationale." +"emit bytecode with a negative line number delta. Functions " +"using :attr:`frame.f_lineno`, ``PyFrame_GetLineNumber()`` or " +"``PyCode_Addr2Line()`` are not affected. Functions directly decoding :attr:`!" +"co_lnotab` should be updated to use a signed 8-bit integer type for the line " +"number delta, but this is only required to support applications using a " +"negative line number delta. See ``Objects/lnotab_notes.txt`` for the :attr:`!" +"co_lnotab` format and how to decode it, and see the :pep:`511` for the " +"rationale." msgstr "" #: whatsnew/3.6.rst:2187 @@ -3093,28 +3107,26 @@ msgstr "" #: whatsnew/3.6.rst:2192 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`." +"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 "" #: whatsnew/3.6.rst:2197 msgid "" -"The :mod:`!imp` module now raises a :exc:`DeprecationWarning` instead of :" -"exc:`PendingDeprecationWarning`." +"The :mod:`!imp` module now raises a :exc:`DeprecationWarning` instead " +"of :exc:`PendingDeprecationWarning`." msgstr "" #: whatsnew/3.6.rst:2200 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. (Contributed by Joel Taddei and Jacek " -"Kołodziej in :issue:`23883`.)" +"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. (Contributed by Joel Taddei and Jacek Kołodziej in :issue:`23883`.)" msgstr "" #: whatsnew/3.6.rst:2211 @@ -3126,26 +3138,27 @@ msgstr "" #: whatsnew/3.6.rst:2215 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`.)" +"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 "" #: whatsnew/3.6.rst:2219 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. " +"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 "" #: whatsnew/3.6.rst:2228 msgid "" -":func:`spwd.getspnam` now raises a :exc:`PermissionError` instead of :exc:" -"`KeyError` if the user doesn't have privileges." +":func:`spwd.getspnam` now raises a :exc:`PermissionError` instead " +"of :exc:`KeyError` if the user doesn't have privileges." msgstr "" #: whatsnew/3.6.rst:2231 @@ -3167,11 +3180,12 @@ msgstr "" #: whatsnew/3.6.rst:2243 msgid "" -"All optional arguments 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`.)" +"All optional arguments 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 "" #: whatsnew/3.6.rst:2250 @@ -3182,14 +3196,15 @@ msgstr "" #: whatsnew/3.6.rst:2253 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." +"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 "" #: whatsnew/3.6.rst:2262 @@ -3216,26 +3231,27 @@ msgstr "" #: whatsnew/3.6.rst:2278 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. (Contributed " -"by Demian Brecht and Rolf Krahl with tweaks from Martin Panter in :issue:" -"`12319`.)" +"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. (Contributed by Demian Brecht and Rolf Krahl with tweaks from Martin " +"Panter in :issue:`12319`.)" msgstr "" #: whatsnew/3.6.rst:2287 msgid "" -"The :class:`~csv.DictReader` now returns rows of type :class:`~collections." -"OrderedDict`. (Contributed by Steve Holden in :issue:`27842`.)" +"The :class:`~csv.DictReader` now returns rows of " +"type :class:`~collections.OrderedDict`. (Contributed by Steve Holden " +"in :issue:`27842`.)" msgstr "" #: whatsnew/3.6.rst:2291 msgid "" "The :const:`crypt.METHOD_CRYPT` will no longer be added to ``crypt.methods`` " -"if unsupported by the platform. (Contributed by Victor Stinner in :issue:" -"`25287`.)" +"if unsupported by the platform. (Contributed by Victor Stinner " +"in :issue:`25287`.)" msgstr "" #: whatsnew/3.6.rst:2299 @@ -3254,8 +3270,8 @@ msgstr "" #: whatsnew/3.6.rst:2308 msgid "" "The :func:`mmap.write() ` function now returns the number of " -"bytes written like other write methods. (Contributed by Jakub Stasiak in :" -"issue:`26335`.)" +"bytes written like other write methods. (Contributed by Jakub Stasiak " +"in :issue:`26335`.)" msgstr "" #: whatsnew/3.6.rst:2312 @@ -3280,8 +3296,8 @@ msgid "" "unrecognized compression values. Previously a plain :exc:`RuntimeError` was " "raised. Additionally, calling :class:`~zipfile.ZipFile` methods on a closed " "ZipFile or calling the :meth:`~zipfile.ZipFile.write` method on a ZipFile " -"created with mode ``'r'`` will raise a :exc:`ValueError`. Previously, a :exc:" -"`RuntimeError` was raised in those scenarios." +"created with mode ``'r'`` will raise a :exc:`ValueError`. Previously, " +"a :exc:`RuntimeError` was raised in those scenarios." msgstr "" #: whatsnew/3.6.rst:2329 @@ -3298,13 +3314,14 @@ msgstr "" msgid "" "With the introduction of :exc:`ModuleNotFoundError`, import system consumers " "may start expecting import system replacements to raise that more specific " -"exception when appropriate, rather than the less-specific :exc:" -"`ImportError`. To provide future compatibility with such consumers, " -"implementers of alternative import systems that completely replace :func:" -"`__import__` will need to update their implementations to raise the new " -"subclass when a module can't be found at all. Implementers of compliant " -"plugins to the default import system shouldn't need to make any changes, as " -"the default import system will raise the new subclass when appropriate." +"exception when appropriate, rather than the less-" +"specific :exc:`ImportError`. To provide future compatibility with such " +"consumers, implementers of alternative import systems that completely " +"replace :func:`__import__` will need to update their implementations to " +"raise the new subclass when a module can't be found at all. Implementers of " +"compliant plugins to the default import system shouldn't need to make any " +"changes, as the default import system will raise the new subclass when " +"appropriate." msgstr "" #: whatsnew/3.6.rst:2348 @@ -3346,27 +3363,27 @@ msgstr "" msgid "" "The new :opcode:`FORMAT_VALUE` and :opcode:`BUILD_STRING` opcodes as part of " "the :ref:`formatted string literal ` implementation. " -"(Contributed by Eric Smith in :issue:`25483` and Serhiy Storchaka in :issue:" -"`27078`.)" +"(Contributed by Eric Smith in :issue:`25483` and Serhiy Storchaka " +"in :issue:`27078`.)" msgstr "" #: whatsnew/3.6.rst:2374 msgid "" "The new :opcode:`BUILD_CONST_KEY_MAP` opcode to optimize the creation of " -"dictionaries with constant keys. (Contributed by Serhiy Storchaka in :issue:" -"`27140`.)" +"dictionaries with constant keys. (Contributed by Serhiy Storchaka " +"in :issue:`27140`.)" msgstr "" #: whatsnew/3.6.rst:2378 msgid "" "The function call opcodes have been heavily reworked for better performance " -"and simpler implementation. The :opcode:`MAKE_FUNCTION`, :opcode:" -"`CALL_FUNCTION`, :opcode:`CALL_FUNCTION_KW` and :opcode:" -"`BUILD_MAP_UNPACK_WITH_CALL` opcodes have been modified, the new :opcode:" -"`CALL_FUNCTION_EX` and :opcode:`BUILD_TUPLE_UNPACK_WITH_CALL` have been " -"added, and ``CALL_FUNCTION_VAR``, ``CALL_FUNCTION_VAR_KW`` and " -"``MAKE_CLOSURE`` opcodes have been removed. (Contributed by Demur Rumed in :" -"issue:`27095`, and Serhiy Storchaka in :issue:`27213`, :issue:`28257`.)" +"and simpler implementation. " +"The :opcode:`MAKE_FUNCTION`, :opcode:`CALL_FUNCTION`, :opcode:`CALL_FUNCTION_KW` " +"and :opcode:`BUILD_MAP_UNPACK_WITH_CALL` opcodes have been modified, the " +"new :opcode:`CALL_FUNCTION_EX` and :opcode:`BUILD_TUPLE_UNPACK_WITH_CALL` " +"have been added, and ``CALL_FUNCTION_VAR``, ``CALL_FUNCTION_VAR_KW`` and " +"``MAKE_CLOSURE`` opcodes have been removed. (Contributed by Demur Rumed " +"in :issue:`27095`, and Serhiy Storchaka in :issue:`27213`, :issue:`28257`.)" msgstr "" #: whatsnew/3.6.rst:2389 @@ -3401,8 +3418,8 @@ msgstr "" #: whatsnew/3.6.rst:2409 msgid "" -"More selective regeneration targets are also defined - see :source:`Makefile." -"pre.in` for details." +"More selective regeneration targets are also defined - " +"see :source:`Makefile.pre.in` for details." msgstr "" #: whatsnew/3.6.rst:2425 @@ -3432,8 +3449,8 @@ msgstr "" msgid "" "The ``PyExc_RecursionErrorInst`` singleton that was part of the public API " "has been removed as its members being never cleared may cause a segfault " -"during finalization of the interpreter. (Contributed by Xavier de Gaye in :" -"issue:`22898` and :issue:`30697`.)" +"during finalization of the interpreter. (Contributed by Xavier de Gaye " +"in :issue:`22898` and :issue:`30697`.)" msgstr "" #: whatsnew/3.6.rst:2440 @@ -3471,12 +3488,12 @@ msgstr "" #: whatsnew/3.6.rst:2461 msgid "" -"Due to significant security concerns, the *reuse_address* parameter of :meth:" -"`asyncio.loop.create_datagram_endpoint` is no longer supported. This is " -"because of the behavior of the socket option ``SO_REUSEADDR`` in UDP. For " -"more details, see the documentation for ``loop.create_datagram_endpoint()``. " -"(Contributed by Kyle Stanley, Antoine Pitrou, and Yury Selivanov in :issue:" -"`37228`.)" +"Due to significant security concerns, the *reuse_address* parameter " +"of :meth:`asyncio.loop.create_datagram_endpoint` is no longer supported. " +"This is because of the behavior of the socket option ``SO_REUSEADDR`` in " +"UDP. For more details, see the documentation for " +"``loop.create_datagram_endpoint()``. (Contributed by Kyle Stanley, Antoine " +"Pitrou, and Yury Selivanov in :issue:`37228`.)" msgstr "" #: whatsnew/3.6.rst:2469 @@ -3486,13 +3503,14 @@ msgstr "" #: whatsnew/3.6.rst:2471 msgid "" "Earlier Python versions allowed using both ``;`` and ``&`` as query " -"parameter separators in :func:`urllib.parse.parse_qs` and :func:`urllib." -"parse.parse_qsl`. Due to security concerns, and to conform with newer W3C " -"recommendations, this has been changed to allow only a single separator key, " -"with ``&`` as the default. This change also affects :func:`cgi.parse` and :" -"func:`cgi.parse_multipart` as they use the affected functions internally. " -"For more details, please see their respective documentation. (Contributed by " -"Adam Goldschmidt, Senthil Kumaran and Ken Jin in :issue:`42967`.)" +"parameter separators in :func:`urllib.parse.parse_qs` " +"and :func:`urllib.parse.parse_qsl`. Due to security concerns, and to " +"conform with newer W3C recommendations, this has been changed to allow only " +"a single separator key, with ``&`` as the default. This change also " +"affects :func:`cgi.parse` and :func:`cgi.parse_multipart` as they use the " +"affected functions internally. For more details, please see their respective " +"documentation. (Contributed by Adam Goldschmidt, Senthil Kumaran and Ken Jin " +"in :issue:`42967`.)" msgstr "" #: whatsnew/3.6.rst:2482 @@ -3514,6 +3532,6 @@ msgid "" "forms of attacks. Following the WHATWG specification that updates RFC 3986, " "ASCII newline ``\\n``, ``\\r`` and tab ``\\t`` characters are stripped from " "the URL by the parser :func:`urllib.parse` preventing such attacks. The " -"removal characters are controlled by a new module level variable ``urllib." -"parse._UNSAFE_URL_BYTES_TO_REMOVE``. (See :gh:`88048`)" +"removal characters are controlled by a new module level variable " +"``urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE``. (See :gh:`88048`)" msgstr "" diff --git a/whatsnew/3.7.po b/whatsnew/3.7.po index 9e25487ba..db96fcf5c 100644 --- a/whatsnew/3.7.po +++ b/whatsnew/3.7.po @@ -31,8 +31,8 @@ msgstr "" #: whatsnew/3.7.rst:47 msgid "" "This article explains the new features in Python 3.7, compared to 3.6. " -"Python 3.7 was released on June 27, 2018. For full details, see the :ref:" -"`changelog `." +"Python 3.7 was released on June 27, 2018. For full details, see " +"the :ref:`changelog `." msgstr "" #: whatsnew/3.7.rst:53 @@ -111,8 +111,9 @@ msgstr "" #: whatsnew/3.7.rst:92 msgid "" -"The :mod:`asyncio` module has received new features, significant :ref:" -"`usability and performance improvements `." +"The :mod:`asyncio` module has received new features, " +"significant :ref:`usability and performance improvements " +"`." msgstr "" #: whatsnew/3.7.rst:95 @@ -170,14 +171,14 @@ msgstr "" #: whatsnew/3.7.rst:116 msgid "" "New documentation translations: `Japanese `_, " -"`French `_, and `Korean `_." +"`French `_, and `Korean `_." msgstr "" #: whatsnew/3.7.rst:120 msgid "" -"This release features notable performance improvements in many areas. The :" -"ref:`whatsnew37-perf` section lists them in detail." +"This release features notable performance improvements in many areas. " +"The :ref:`whatsnew37-perf` section lists them in detail." msgstr "" #: whatsnew/3.7.rst:123 @@ -285,9 +286,9 @@ msgid "" "automatically coerce that locale to an available UTF-8 based locale as " "described in the documentation of the new :envvar:`PYTHONCOERCECLOCALE` " "environment variable. Automatically setting ``LC_CTYPE`` this way means that " -"both the core interpreter and locale-aware C extensions (such as :mod:" -"`readline`) will assume the use of UTF-8 as the default text encoding, " -"rather than ASCII." +"both the core interpreter and locale-aware C extensions (such " +"as :mod:`readline`) will assume the use of UTF-8 as the default text " +"encoding, rather than ASCII." msgstr "" #: whatsnew/3.7.rst:200 @@ -300,16 +301,17 @@ msgstr "" msgid "" "As part of this change, the default error handler for :data:`~sys.stdin` " "and :data:`~sys.stdout` is now ``surrogateescape`` (rather than ``strict``) " -"when using any of the defined coercion target locales (currently ``C." -"UTF-8``, ``C.utf8``, and ``UTF-8``). The default error handler for :data:" -"`~sys.stderr` continues to be ``backslashreplace``, regardless of locale." +"when using any of the defined coercion target locales (currently " +"``C.UTF-8``, ``C.utf8``, and ``UTF-8``). The default error handler " +"for :data:`~sys.stderr` continues to be ``backslashreplace``, regardless of " +"locale." msgstr "" #: whatsnew/3.7.rst:209 msgid "" "Locale coercion is silent by default, but to assist in debugging potentially " -"locale related integration problems, explicit warnings (emitted directly on :" -"data:`~sys.stderr`) can be requested by setting " +"locale related integration problems, explicit warnings (emitted directly " +"on :data:`~sys.stderr`) can be requested by setting " "``PYTHONCOERCECLOCALE=warn``. This setting will also cause the Python " "runtime to emit a warning if the legacy C locale remains active when the " "core interpreter is initialized." @@ -348,8 +350,8 @@ msgstr "" #: whatsnew/3.7.rst:238 msgid "" "When in UTF-8 mode, CPython ignores the locale settings, and uses the UTF-8 " -"encoding by default. The error handlers for :data:`sys.stdin` and :data:" -"`sys.stdout` streams are set to ``surrogateescape``." +"encoding by default. The error handlers for :data:`sys.stdin` " +"and :data:`sys.stdout` streams are set to ``surrogateescape``." msgstr "" #: whatsnew/3.7.rst:242 @@ -400,9 +402,10 @@ msgid "" "Built-in ``breakpoint()`` calls :func:`sys.breakpointhook`. By default, the " "latter imports :mod:`pdb` and then calls ``pdb.set_trace()``, but by binding " "``sys.breakpointhook()`` to the function of your choosing, ``breakpoint()`` " -"can enter any debugger. Additionally, the environment variable :envvar:" -"`PYTHONBREAKPOINT` can be set to the callable of your debugger of choice. " -"Set ``PYTHONBREAKPOINT=0`` to completely disable built-in ``breakpoint()``." +"can enter any debugger. Additionally, the environment " +"variable :envvar:`PYTHONBREAKPOINT` can be set to the callable of your " +"debugger of choice. Set ``PYTHONBREAKPOINT=0`` to completely disable built-" +"in ``breakpoint()``." msgstr "" #: whatsnew/3.7.rst:282 @@ -431,11 +434,11 @@ msgid "" ":pep:`539` changes this by providing a new :ref:`Thread Specific Storage " "(TSS) API ` to CPython which supersedes use of " "the existing TLS API within the CPython interpreter, while deprecating the " -"existing API. The TSS API uses a new type :c:type:`Py_tss_t` instead of :c:" -"expr:`int` to represent TSS keys--an opaque type the definition of which may " -"depend on the underlying TLS implementation. Therefore, this will allow to " -"build CPython on platforms where the native TLS key is defined in a way that " -"cannot be safely cast to :c:expr:`int`." +"existing API. The TSS API uses a new type :c:type:`Py_tss_t` instead " +"of :c:expr:`int` to represent TSS keys--an opaque type the definition of " +"which may depend on the underlying TLS implementation. Therefore, this will " +"allow to build CPython on platforms where the native TLS key is defined in a " +"way that cannot be safely cast to :c:expr:`int`." msgstr "" #: whatsnew/3.7.rst:306 @@ -462,8 +465,8 @@ msgstr "" #: whatsnew/3.7.rst:323 msgid "" "Python 3.7 allows defining :meth:`__getattr__` on modules and will call it " -"whenever a module attribute is otherwise not found. Defining :meth:" -"`__dir__` on modules is now also allowed." +"whenever a module attribute is otherwise not found. " +"Defining :meth:`__dir__` on modules is now also allowed." msgstr "" #: whatsnew/3.7.rst:327 @@ -577,10 +580,11 @@ msgstr "" #: whatsnew/3.7.rst:393 msgid "" -"Previously both :exc:`DeprecationWarning` and :exc:" -"`PendingDeprecationWarning` were only visible when running tests, which " -"meant that developers primarily writing single file scripts or using Python " -"interactively could be surprised by breaking changes in the APIs they used." +"Previously both :exc:`DeprecationWarning` " +"and :exc:`PendingDeprecationWarning` were only visible when running tests, " +"which meant that developers primarily writing single file scripts or using " +"Python interactively could be surprised by breaking changes in the APIs they " +"used." msgstr "" #: whatsnew/3.7.rst:400 @@ -598,14 +602,14 @@ msgstr "" #: whatsnew/3.7.rst:409 msgid "" "Initially :pep:`484` was designed in such way that it would not introduce " -"*any* changes to the core CPython interpreter. Now type hints and the :mod:" -"`typing` module are extensively used by the community, so this restriction " -"is removed. The PEP introduces two special methods :meth:`__class_getitem__` " -"and ``__mro_entries__``, these methods are now used by most classes and " -"special constructs in :mod:`typing`. As a result, the speed of various " -"operations with types increased up to 7 times, the generic types can be used " -"without metaclass conflicts, and several long standing bugs in :mod:`typing` " -"module are fixed." +"*any* changes to the core CPython interpreter. Now type hints and " +"the :mod:`typing` module are extensively used by the community, so this " +"restriction is removed. The PEP introduces two special " +"methods :meth:`__class_getitem__` and ``__mro_entries__``, these methods are " +"now used by most classes and special constructs in :mod:`typing`. As a " +"result, the speed of various operations with types increased up to 7 times, " +"the generic types can be used without metaclass conflicts, and several long " +"standing bugs in :mod:`typing` module are fixed." msgstr "" #: whatsnew/3.7.rst:421 @@ -634,8 +638,8 @@ msgid "" "used for invalidation instead of the source timestamp. Such ``.pyc`` files " "are called \"hash-based\". By default, Python still uses timestamp-based " "invalidation and does not generate hash-based ``.pyc`` files at runtime. " -"Hash-based ``.pyc`` files may be generated with :mod:`py_compile` or :mod:" -"`compileall`." +"Hash-based ``.pyc`` files may be generated with :mod:`py_compile` " +"or :mod:`compileall`." msgstr "" #: whatsnew/3.7.rst:445 @@ -702,12 +706,12 @@ msgstr "" #: whatsnew/3.7.rst:486 msgid "" -"The new :option:`-X` ``dev`` command line option or the new :envvar:" -"`PYTHONDEVMODE` environment variable can be used to enable :ref:`Python " -"Development Mode `. When in development mode, Python performs " -"additional runtime checks that are too expensive to be enabled by default. " -"See :ref:`Python Development Mode ` documentation for the full " -"description." +"The new :option:`-X` ``dev`` command line option or the " +"new :envvar:`PYTHONDEVMODE` environment variable can be used to " +"enable :ref:`Python Development Mode `. When in development mode, " +"Python performs additional runtime checks that are too expensive to be " +"enabled by default. See :ref:`Python Development Mode ` " +"documentation for the full description." msgstr "" #: whatsnew/3.7.rst:495 @@ -716,17 +720,17 @@ msgstr "" #: whatsnew/3.7.rst:497 msgid "" -"An :keyword:`await` expression and comprehensions containing an :keyword:" -"`async for` clause were illegal in the expressions in :ref:`formatted string " -"literals ` due to a problem with the implementation. In Python " -"3.7 this restriction was lifted." +"An :keyword:`await` expression and comprehensions containing " +"an :keyword:`async for` clause were illegal in the expressions " +"in :ref:`formatted string literals ` due to a problem with the " +"implementation. In Python 3.7 this restriction was lifted." msgstr "" #: whatsnew/3.7.rst:502 msgid "" "More than 255 arguments can now be passed to a function, and a function can " -"now have more than 255 parameters. (Contributed by Serhiy Storchaka in :" -"issue:`12844` and :issue:`18896`.)" +"now have more than 255 parameters. (Contributed by Serhiy Storchaka " +"in :issue:`12844` and :issue:`18896`.)" msgstr "" #: whatsnew/3.7.rst:506 @@ -746,8 +750,8 @@ msgstr "" #: whatsnew/3.7.rst:514 msgid "" ":exc:`ImportError` now displays module name and module ``__file__`` path " -"when ``from ... import ...`` fails. (Contributed by Matthias Bussonnier in :" -"issue:`29546`.)" +"when ``from ... import ...`` fails. (Contributed by Matthias Bussonnier " +"in :issue:`29546`.)" msgstr "" #: whatsnew/3.7.rst:518 @@ -759,16 +763,17 @@ msgstr "" #: whatsnew/3.7.rst:522 msgid "" "``object.__format__(x, '')`` is now equivalent to ``str(x)`` rather than " -"``format(str(self), '')``. (Contributed by Serhiy Storchaka in :issue:" -"`28974`.)" +"``format(str(self), '')``. (Contributed by Serhiy Storchaka " +"in :issue:`28974`.)" msgstr "" #: whatsnew/3.7.rst:526 msgid "" -"In order to better support dynamic creation of stack traces, :class:`types." -"TracebackType` can now be instantiated from Python code, and the :attr:" -"`~traceback.tb_next` attribute on :ref:`tracebacks ` is " -"now writable. (Contributed by Nathaniel J. Smith in :issue:`30579`.)" +"In order to better support dynamic creation of stack " +"traces, :class:`types.TracebackType` can now be instantiated from Python " +"code, and the :attr:`~traceback.tb_next` attribute on :ref:`tracebacks " +"` is now writable. (Contributed by Nathaniel J. Smith " +"in :issue:`30579`.)" msgstr "" #: whatsnew/3.7.rst:532 @@ -781,9 +786,10 @@ msgstr "" #: whatsnew/3.7.rst:538 msgid "" -"The new :option:`-X` ``importtime`` option or the :envvar:" -"`PYTHONPROFILEIMPORTTIME` environment variable can be used to show the " -"timing of each module import. (Contributed by Inada Naoki in :issue:`31415`.)" +"The new :option:`-X` ``importtime`` option or " +"the :envvar:`PYTHONPROFILEIMPORTTIME` environment variable can be used to " +"show the timing of each module import. (Contributed by Inada Naoki " +"in :issue:`31415`.)" msgstr "" #: whatsnew/3.7.rst:545 @@ -826,9 +832,9 @@ msgstr "" msgid "" "The new :func:`~dataclasses.dataclass` decorator provides a way to declare " "*data classes*. A data class describes its attributes using class variable " -"annotations. Its constructor and other magic methods, such as :meth:" -"`~object.__repr__`, :meth:`~object.__eq__`, and :meth:`~object.__hash__` are " -"generated automatically." +"annotations. Its constructor and other magic methods, such " +"as :meth:`~object.__repr__`, :meth:`~object.__eq__`, " +"and :meth:`~object.__hash__` are generated automatically." msgstr "" #: whatsnew/3.7.rst:580 @@ -864,10 +870,10 @@ msgid "" "The new :mod:`importlib.resources` module provides several new APIs and one " "new ABC for access to, opening, and reading *resources* inside packages. " "Resources are roughly similar to files inside packages, but they needn't be " -"actual files on the physical file system. Module loaders can provide a :" -"meth:`get_resource_reader` function which returns a :class:`importlib.abc." -"ResourceReader` instance to support this new API. Built-in file path " -"loaders and zip file loaders both support this." +"actual files on the physical file system. Module loaders can provide " +"a :meth:`get_resource_reader` function which returns " +"a :class:`importlib.abc.ResourceReader` instance to support this new API. " +"Built-in file path loaders and zip file loaders both support this." msgstr "" #: whatsnew/3.7.rst:610 @@ -890,9 +896,9 @@ msgstr "" #: whatsnew/3.7.rst:625 msgid "" -"The new :meth:`ArgumentParser.parse_intermixed_args() ` method allows intermixing options and " -"positional arguments. (Contributed by paul.j3 in :issue:`14191`.)" +"The new :meth:`ArgumentParser.parse_intermixed_args() " +"` method allows intermixing " +"options and positional arguments. (Contributed by paul.j3 in :issue:`14191`.)" msgstr "" #: whatsnew/3.7.rst:1964 @@ -901,29 +907,29 @@ msgstr "" #: whatsnew/3.7.rst:636 msgid "" -"The :mod:`asyncio` module has received many new features, usability and :ref:" -"`performance improvements `. Notable changes " -"include:" +"The :mod:`asyncio` module has received many new features, usability " +"and :ref:`performance improvements `. Notable " +"changes include:" msgstr "" #: whatsnew/3.7.rst:640 msgid "" "The new :term:`provisional ` :func:`asyncio.run` function " "can be used to run a coroutine from synchronous code by automatically " -"creating and destroying the event loop. (Contributed by Yury Selivanov in :" -"issue:`32314`.)" +"creating and destroying the event loop. (Contributed by Yury Selivanov " +"in :issue:`32314`.)" msgstr "" #: whatsnew/3.7.rst:645 msgid "" "asyncio gained support for :mod:`contextvars`. :meth:`loop.call_soon() " -"`, :meth:`loop.call_soon_threadsafe() `, :meth:`loop.call_later() `, :meth:`loop.call_at() `, and :meth:" -"`Future.add_done_callback() ` have a new " -"optional keyword-only *context* parameter. :class:`Tasks ` now " -"track their context automatically. See :pep:`567` for more details. " -"(Contributed by Yury Selivanov in :issue:`32436`.)" +"`, :meth:`loop.call_soon_threadsafe() " +"`, :meth:`loop.call_later() " +"`, :meth:`loop.call_at() `, " +"and :meth:`Future.add_done_callback() ` " +"have a new optional keyword-only *context* parameter. :class:`Tasks " +"` now track their context automatically. See :pep:`567` for " +"more details. (Contributed by Yury Selivanov in :issue:`32436`.)" msgstr "" #: whatsnew/3.7.rst:656 @@ -936,25 +942,26 @@ msgstr "" #: whatsnew/3.7.rst:660 msgid "" "The new :meth:`loop.start_tls() ` method can be used " -"to upgrade an existing connection to TLS. (Contributed by Yury Selivanov in :" -"issue:`23749`.)" +"to upgrade an existing connection to TLS. (Contributed by Yury Selivanov " +"in :issue:`23749`.)" msgstr "" #: whatsnew/3.7.rst:664 msgid "" "The new :meth:`loop.sock_recv_into() ` method " "allows reading data from a socket directly into a provided buffer making it " -"possible to reduce data copies. (Contributed by Antoine Pitrou in :issue:" -"`31819`.)" +"possible to reduce data copies. (Contributed by Antoine Pitrou " +"in :issue:`31819`.)" msgstr "" #: whatsnew/3.7.rst:669 msgid "" -"The new :func:`asyncio.current_task` function returns the currently running :" -"class:`~asyncio.Task` instance, and the new :func:`asyncio.all_tasks` " -"function returns a set of all existing ``Task`` instances in a given loop. " -"The :meth:`!Task.current_task` and :meth:`!Task.all_tasks` methods have been " -"deprecated. (Contributed by Andrew Svetlov in :issue:`32250`.)" +"The new :func:`asyncio.current_task` function returns the currently " +"running :class:`~asyncio.Task` instance, and the " +"new :func:`asyncio.all_tasks` function returns a set of all existing " +"``Task`` instances in a given loop. The :meth:`!Task.current_task` " +"and :meth:`!Task.all_tasks` methods have been deprecated. (Contributed by " +"Andrew Svetlov in :issue:`32250`.)" msgstr "" #: whatsnew/3.7.rst:676 @@ -969,17 +976,17 @@ msgid "" "The new :func:`asyncio.get_running_loop` function returns the currently " "running loop, and raises a :exc:`RuntimeError` if no loop is running. This " "is in contrast with :func:`asyncio.get_event_loop`, which will *create* a " -"new event loop if none is running. (Contributed by Yury Selivanov in :issue:" -"`32269`.)" +"new event loop if none is running. (Contributed by Yury Selivanov " +"in :issue:`32269`.)" msgstr "" #: whatsnew/3.7.rst:686 msgid "" -"The new :meth:`StreamWriter.wait_closed() ` coroutine method allows waiting until the stream writer is " -"closed. The new :meth:`StreamWriter.is_closing() ` method can be used to determine if the writer is closing. " -"(Contributed by Andrew Svetlov in :issue:`32391`.)" +"The new :meth:`StreamWriter.wait_closed() " +"` coroutine method allows waiting until " +"the stream writer is closed. The new :meth:`StreamWriter.is_closing() " +"` method can be used to determine if the " +"writer is closing. (Contributed by Andrew Svetlov in :issue:`32391`.)" msgstr "" #: whatsnew/3.7.rst:692 @@ -991,27 +998,27 @@ msgstr "" #: whatsnew/3.7.rst:696 msgid "" -"The new :meth:`Future.get_loop() ` and ``Task." -"get_loop()`` methods return the instance of the loop on which a task or a " -"future were created. :meth:`Server.get_loop() ` " -"allows doing the same for :class:`asyncio.Server` objects. (Contributed by " -"Yury Selivanov in :issue:`32415` and Srinivas Reddy Thatiparthy in :issue:" -"`32418`.)" +"The new :meth:`Future.get_loop() ` and " +"``Task.get_loop()`` methods return the instance of the loop on which a task " +"or a future were created. :meth:`Server.get_loop() " +"` allows doing the same for :class:`asyncio.Server` " +"objects. (Contributed by Yury Selivanov in :issue:`32415` and Srinivas Reddy " +"Thatiparthy in :issue:`32418`.)" msgstr "" #: whatsnew/3.7.rst:704 msgid "" "It is now possible to control how instances of :class:`asyncio.Server` begin " "serving. Previously, the server would start serving immediately when " -"created. The new *start_serving* keyword argument to :meth:`loop." -"create_server() ` and :meth:`loop." -"create_unix_server() `, as well as :meth:" -"`Server.start_serving() `, and :meth:`Server." -"serve_forever() ` can be used to decouple " -"server instantiation and serving. The new :meth:`Server.is_serving() " -"` method returns ``True`` if the server is " -"serving. :class:`~asyncio.Server` objects are now asynchronous context " -"managers::" +"created. The new *start_serving* keyword argument " +"to :meth:`loop.create_server() ` " +"and :meth:`loop.create_unix_server() `, as " +"well as :meth:`Server.start_serving() `, " +"and :meth:`Server.serve_forever() ` can be " +"used to decouple server instantiation and serving. The " +"new :meth:`Server.is_serving() ` method returns " +"``True`` if the server is serving. :class:`~asyncio.Server` objects are now " +"asynchronous context managers::" msgstr "" #: whatsnew/3.7.rst:716 @@ -1030,27 +1037,27 @@ msgstr "" #: whatsnew/3.7.rst:725 msgid "" -"Callback objects returned by :func:`loop.call_later() ` gained the new :meth:`when() ` method " -"which returns an absolute scheduled callback timestamp. (Contributed by " -"Andrew Svetlov in :issue:`32741`.)" +"Callback objects returned by :func:`loop.call_later() " +"` gained the new :meth:`when() " +"` method which returns an absolute scheduled " +"callback timestamp. (Contributed by Andrew Svetlov in :issue:`32741`.)" msgstr "" #: whatsnew/3.7.rst:731 msgid "" -"The :meth:`loop.create_datagram_endpoint() \\ ` method gained support for Unix sockets. " -"(Contributed by Quentin Dawans in :issue:`31245`.)" +"The :meth:`loop.create_datagram_endpoint() \\ " +"` method gained support for Unix " +"sockets. (Contributed by Quentin Dawans in :issue:`31245`.)" msgstr "" #: whatsnew/3.7.rst:736 msgid "" "The :func:`asyncio.open_connection`, :func:`asyncio.start_server` " -"functions, :meth:`loop.create_connection() `, :meth:`loop.create_server() `, :meth:`loop.create_accepted_socket() ` methods and their corresponding UNIX socket " -"variants now accept the *ssl_handshake_timeout* keyword argument. " +"functions, :meth:`loop.create_connection() " +"`, :meth:`loop.create_server() " +"`, :meth:`loop.create_accepted_socket() " +"` methods and their corresponding UNIX " +"socket variants now accept the *ssl_handshake_timeout* keyword argument. " "(Contributed by Neil Aspinall in :issue:`29970`.)" msgstr "" @@ -1063,32 +1070,35 @@ msgstr "" #: whatsnew/3.7.rst:748 msgid "" -"The asyncio source has been converted to use the :keyword:`async`/:keyword:" -"`await` syntax. (Contributed by Andrew Svetlov in :issue:`32193`.)" +"The asyncio source has been converted to use " +"the :keyword:`async`/:keyword:`await` syntax. (Contributed by Andrew Svetlov " +"in :issue:`32193`.)" msgstr "" #: whatsnew/3.7.rst:752 msgid "" -"The new :meth:`ReadTransport.is_reading() ` method can be used to determine the reading state of the " -"transport. Additionally, calls to :meth:`ReadTransport.resume_reading() " -"` and :meth:`ReadTransport." -"pause_reading() ` are now idempotent. " -"(Contributed by Yury Selivanov in :issue:`32356`.)" +"The new :meth:`ReadTransport.is_reading() " +"` method can be used to determine the " +"reading state of the transport. Additionally, calls " +"to :meth:`ReadTransport.resume_reading() " +"` " +"and :meth:`ReadTransport.pause_reading() " +"` are now idempotent. (Contributed by " +"Yury Selivanov in :issue:`32356`.)" msgstr "" #: whatsnew/3.7.rst:760 msgid "" "Loop methods which accept socket paths now support passing :term:`path-like " -"objects `. (Contributed by Yury Selivanov in :issue:" -"`32066`.)" +"objects `. (Contributed by Yury Selivanov " +"in :issue:`32066`.)" msgstr "" #: whatsnew/3.7.rst:764 msgid "" "In :mod:`asyncio` TCP sockets on Linux are now created with ``TCP_NODELAY`` " -"flag set by default. (Contributed by Yury Selivanov and Victor Stinner in :" -"issue:`27456`.)" +"flag set by default. (Contributed by Yury Selivanov and Victor Stinner " +"in :issue:`27456`.)" msgstr "" #: whatsnew/3.7.rst:768 @@ -1161,8 +1171,8 @@ msgstr "" #: whatsnew/3.7.rst:816 msgid "" -":class:`ProcessPoolExecutor ` and :" -"class:`ThreadPoolExecutor ` now " +":class:`ProcessPoolExecutor ` " +"and :class:`ThreadPoolExecutor ` now " "support the new *initializer* and *initargs* constructor arguments. " "(Contributed by Antoine Pitrou in :issue:`21423`.)" msgstr "" @@ -1187,11 +1197,12 @@ msgstr "" #: whatsnew/3.7.rst:833 msgid "" -"The new :func:`~contextlib.asynccontextmanager`, :class:`~contextlib." -"AbstractAsyncContextManager`, and :class:`~contextlib.AsyncExitStack` have " -"been added to complement their synchronous counterparts. (Contributed by " -"Jelle Zijlstra in :issue:`29679` and :issue:`30241`, and by Alexander Mohr " -"and Ilya Kulakov in :issue:`29302`.)" +"The " +"new :func:`~contextlib.asynccontextmanager`, :class:`~contextlib.AbstractAsyncContextManager`, " +"and :class:`~contextlib.AsyncExitStack` have been added to complement their " +"synchronous counterparts. (Contributed by Jelle Zijlstra in :issue:`29679` " +"and :issue:`30241`, and by Alexander Mohr and Ilya Kulakov " +"in :issue:`29302`.)" msgstr "" #: whatsnew/3.7.rst:842 @@ -1201,8 +1212,8 @@ msgstr "" #: whatsnew/3.7.rst:844 msgid "" "The :mod:`cProfile` command line now accepts ``-m module_name`` as an " -"alternative to script path. (Contributed by Sanyam Khurana in :issue:" -"`21862`.)" +"alternative to script path. (Contributed by Sanyam Khurana " +"in :issue:`21862`.)" msgstr "" #: whatsnew/3.7.rst:849 @@ -1229,8 +1240,9 @@ msgstr "" msgid "" "The new :meth:`datetime.fromisoformat() ` " "method constructs a :class:`~datetime.datetime` object from a string in one " -"of the formats output by :meth:`datetime.isoformat() `. (Contributed by Paul Ganssle in :issue:`15873`.)" +"of the formats output by :meth:`datetime.isoformat() " +"`. (Contributed by Paul Ganssle " +"in :issue:`15873`.)" msgstr "" #: whatsnew/3.7.rst:867 @@ -1256,8 +1268,8 @@ msgstr "" #: whatsnew/3.7.rst:881 msgid "" "The :mod:`decimal` module now uses :ref:`context variables ` to store the decimal context. (Contributed by Yury Selivanov in :" -"issue:`32630`.)" +"pep567>` to store the decimal context. (Contributed by Yury Selivanov " +"in :issue:`32630`.)" msgstr "" #: whatsnew/3.7.rst:887 @@ -1326,8 +1338,8 @@ msgid "" "be used before a POSIX ``fork()`` call to make the GC copy-on-write friendly " "or to speed up collection. The new :func:`gc.unfreeze` functions reverses " "this operation. Additionally, :func:`gc.get_freeze_count` can be used to " -"obtain the number of frozen objects. (Contributed by Li Zekun in :issue:" -"`31558`.)" +"obtain the number of frozen objects. (Contributed by Li Zekun " +"in :issue:`31558`.)" msgstr "" #: whatsnew/3.7.rst:942 @@ -1347,9 +1359,10 @@ msgstr "" #: whatsnew/3.7.rst:952 msgid "" -":class:`~http.client.HTTPConnection` and :class:`~http.client." -"HTTPSConnection` now support the new *blocksize* argument for improved " -"upload throughput. (Contributed by Nir Soffer in :issue:`31945`.)" +":class:`~http.client.HTTPConnection` " +"and :class:`~http.client.HTTPSConnection` now support the new *blocksize* " +"argument for improved upload throughput. (Contributed by Nir Soffer " +"in :issue:`31945`.)" msgstr "" #: whatsnew/3.7.rst:958 @@ -1387,8 +1400,8 @@ msgstr "" #: whatsnew/3.7.rst:980 msgid "" -"Multiple fixes for autocompletion. (Contributed by Louie Lu in :issue:" -"`15786`.)" +"Multiple fixes for autocompletion. (Contributed by Louie Lu " +"in :issue:`15786`.)" msgstr "" #: whatsnew/3.7.rst:982 @@ -1427,8 +1440,8 @@ msgid "" "Editor code context option revised. Box displays all context lines up to " "maxlines. Clicking on a context line jumps the editor to that line. " "Context colors for custom themes is added to Highlights tab of Settings " -"dialog. (Contributed by Cheryl Sabella and Terry Jan Reedy in :issue:" -"`33642`, :issue:`33768`, and :issue:`33679`.)" +"dialog. (Contributed by Cheryl Sabella and Terry Jan Reedy " +"in :issue:`33642`, :issue:`33768`, and :issue:`33679`.)" msgstr "" #: whatsnew/3.7.rst:1009 @@ -1480,8 +1493,8 @@ msgid "" "Add optional line numbers for IDLE editor windows. Windows open without line " "numbers unless set otherwise in the General tab of the configuration " "dialog. Line numbers for an existing window are shown and hidden in the " -"Options menu. (Contributed by Tal Einat and Saimadhav Heblikar in :issue:" -"`17535`.)" +"Options menu. (Contributed by Tal Einat and Saimadhav Heblikar " +"in :issue:`17535`.)" msgstr "" #: whatsnew/3.7.rst:2017 @@ -1491,9 +1504,9 @@ msgstr "" #: whatsnew/3.7.rst:1046 msgid "" "The :class:`importlib.abc.ResourceReader` ABC was introduced to support the " -"loading of resources from packages. See also :ref:" -"`whatsnew37_importlib_resources`. (Contributed by Barry Warsaw, Brett Cannon " -"in :issue:`32248`.)" +"loading of resources from packages. See " +"also :ref:`whatsnew37_importlib_resources`. (Contributed by Barry Warsaw, " +"Brett Cannon in :issue:`32248`.)" msgstr "" #: whatsnew/3.7.rst:1051 @@ -1505,9 +1518,9 @@ msgstr "" #: whatsnew/3.7.rst:1055 msgid "" ":func:`importlib.find_spec` now raises :exc:`ModuleNotFoundError` instead " -"of :exc:`AttributeError` if the specified parent module is not a package (i." -"e. lacks a ``__path__`` attribute). (Contributed by Milan Oberkirch in :" -"issue:`30436`.)" +"of :exc:`AttributeError` if the specified parent module is not a package " +"(i.e. lacks a ``__path__`` attribute). (Contributed by Milan Oberkirch " +"in :issue:`30436`.)" msgstr "" #: whatsnew/3.7.rst:1060 @@ -1525,8 +1538,8 @@ msgstr "" msgid "" "The new :meth:`TextIOWrapper.reconfigure() ` " "method can be used to reconfigure the text stream with the new settings. " -"(Contributed by Antoine Pitrou in :issue:`30526` and INADA Naoki in :issue:" -"`15216`.)" +"(Contributed by Antoine Pitrou in :issue:`30526` and INADA Naoki " +"in :issue:`15216`.)" msgstr "" #: whatsnew/3.7.rst:1075 @@ -1535,10 +1548,10 @@ msgstr "" #: whatsnew/3.7.rst:1077 msgid "" -"The new ``subnet_of()`` and ``supernet_of()`` methods of :class:`ipaddress." -"IPv6Network` and :class:`ipaddress.IPv4Network` can be used for network " -"containment tests. (Contributed by Michel Albert and Cheryl Sabella in :" -"issue:`20825`.)" +"The new ``subnet_of()`` and ``supernet_of()`` methods " +"of :class:`ipaddress.IPv6Network` and :class:`ipaddress.IPv4Network` can be " +"used for network containment tests. (Contributed by Michel Albert and Cheryl " +"Sabella in :issue:`20825`.)" msgstr "" #: whatsnew/3.7.rst:1084 @@ -1547,9 +1560,9 @@ msgstr "" #: whatsnew/3.7.rst:1086 msgid "" -":func:`itertools.islice` now accepts :meth:`integer-like objects ` as start, stop, and slice arguments. (Contributed by Will " -"Roberts in :issue:`30537`.)" +":func:`itertools.islice` now accepts :meth:`integer-like objects " +"` as start, stop, and slice arguments. (Contributed by " +"Will Roberts in :issue:`30537`.)" msgstr "" #: whatsnew/3.7.rst:2035 @@ -1621,8 +1634,8 @@ msgstr "" #: whatsnew/3.7.rst:1136 msgid "" "The new :meth:`Database.Close() ` method can be used " -"to close the :abbr:`MSI` database. (Contributed by Berker Peksag in :issue:" -"`20486`.)" +"to close the :abbr:`MSI` database. (Contributed by Berker Peksag " +"in :issue:`20486`.)" msgstr "" #: whatsnew/3.7.rst:1142 @@ -1669,16 +1682,16 @@ msgstr "" #: whatsnew/3.7.rst:1168 msgid "" "The new :func:`~os.register_at_fork` function allows registering Python " -"callbacks to be executed at process fork. (Contributed by Antoine Pitrou in :" -"issue:`16500`.)" +"callbacks to be executed at process fork. (Contributed by Antoine Pitrou " +"in :issue:`16500`.)" msgstr "" #: whatsnew/3.7.rst:1172 msgid "" -"Added :func:`os.preadv` (combine the functionality of :func:`os.readv` and :" -"func:`os.pread`) and :func:`os.pwritev` functions (combine the functionality " -"of :func:`os.writev` and :func:`os.pwrite`). (Contributed by Pablo Galindo " -"in :issue:`31368`.)" +"Added :func:`os.preadv` (combine the functionality of :func:`os.readv` " +"and :func:`os.pread`) and :func:`os.pwritev` functions (combine the " +"functionality of :func:`os.writev` and :func:`os.pwrite`). (Contributed by " +"Pablo Galindo in :issue:`31368`.)" msgstr "" #: whatsnew/3.7.rst:1177 @@ -1696,9 +1709,9 @@ msgstr "" #: whatsnew/3.7.rst:1185 msgid "" -"The structure returned by :func:`os.stat` now contains the :attr:`~os." -"stat_result.st_fstype` attribute on Solaris and its derivatives. " -"(Contributed by Jesús Cea Avión in :issue:`32659`.)" +"The structure returned by :func:`os.stat` now contains " +"the :attr:`~os.stat_result.st_fstype` attribute on Solaris and its " +"derivatives. (Contributed by Jesús Cea Avión in :issue:`32659`.)" msgstr "" #: whatsnew/3.7.rst:1191 @@ -1738,9 +1751,9 @@ msgid "" ":func:`py_compile.compile` -- and by extension, :mod:`compileall` -- now " "respects the :envvar:`SOURCE_DATE_EPOCH` environment variable by " "unconditionally creating ``.pyc`` files for hash-based validation. This " -"allows for guaranteeing `reproducible builds `_ of ``.pyc`` files when they are created eagerly. (Contributed by " -"Bernhard M. Wiedemann in :issue:`29708`.)" +"allows for guaranteeing `reproducible builds `_ of ``.pyc`` files when they are created eagerly. (Contributed " +"by Bernhard M. Wiedemann in :issue:`29708`.)" msgstr "" #: whatsnew/3.7.rst:1222 @@ -1750,8 +1763,8 @@ msgstr "" #: whatsnew/3.7.rst:1224 msgid "" "The pydoc server can now bind to an arbitrary hostname specified by the new " -"``-n`` command-line argument. (Contributed by Feanil Patel in :issue:" -"`31128`.)" +"``-n`` command-line argument. (Contributed by Feanil Patel " +"in :issue:`31128`.)" msgstr "" #: whatsnew/3.7.rst:1230 @@ -1771,8 +1784,8 @@ msgstr "" #: whatsnew/3.7.rst:1239 msgid "" "The flags :const:`re.ASCII`, :const:`re.LOCALE` and :const:`re.UNICODE` can " -"be set within the scope of a group. (Contributed by Serhiy Storchaka in :" -"issue:`31690`.)" +"be set within the scope of a group. (Contributed by Serhiy Storchaka " +"in :issue:`31690`.)" msgstr "" #: whatsnew/3.7.rst:1243 @@ -1794,15 +1807,15 @@ msgstr "" msgid "" ":exc:`FutureWarning` is now emitted if a regular expression contains " "character set constructs that will change semantically in the future, such " -"as nested sets and set operations. (Contributed by Serhiy Storchaka in :" -"issue:`30349`.)" +"as nested sets and set operations. (Contributed by Serhiy Storchaka " +"in :issue:`30349`.)" msgstr "" #: whatsnew/3.7.rst:1257 msgid "" -"Compiled regular expression and match objects can now be copied using :func:" -"`copy.copy` and :func:`copy.deepcopy`. (Contributed by Serhiy Storchaka in :" -"issue:`10076`.)" +"Compiled regular expression and match objects can now be copied " +"using :func:`copy.copy` and :func:`copy.deepcopy`. (Contributed by Serhiy " +"Storchaka in :issue:`10076`.)" msgstr "" #: whatsnew/3.7.rst:1263 @@ -1832,16 +1845,16 @@ msgstr "" msgid "" "The new :func:`socket.close` function closes the passed socket file " "descriptor. This function should be used instead of :func:`os.close` for " -"better compatibility across platforms. (Contributed by Christian Heimes in :" -"issue:`32454`.)" +"better compatibility across platforms. (Contributed by Christian Heimes " +"in :issue:`32454`.)" msgstr "" #: whatsnew/3.7.rst:1283 msgid "" "The :mod:`socket` module now exposes the :const:`socket.TCP_CONGESTION` " -"(Linux 2.6.13), :const:`socket.TCP_USER_TIMEOUT` (Linux 2.6.37), and :const:" -"`socket.TCP_NOTSENT_LOWAT` (Linux 3.12) constants. (Contributed by Omar " -"Sandoval in :issue:`26273` and Nathaniel J. Smith in :issue:`29728`.)" +"(Linux 2.6.13), :const:`socket.TCP_USER_TIMEOUT` (Linux 2.6.37), " +"and :const:`socket.TCP_NOTSENT_LOWAT` (Linux 3.12) constants. (Contributed " +"by Omar Sandoval in :issue:`26273` and Nathaniel J. Smith in :issue:`29728`.)" msgstr "" #: whatsnew/3.7.rst:1289 @@ -1871,9 +1884,9 @@ msgstr "" #: whatsnew/3.7.rst:1305 msgid "" "Add a new :attr:`socketserver.ForkingMixIn.block_on_close` class attribute " -"to :class:`socketserver.ForkingMixIn` and :class:`socketserver." -"ThreadingMixIn` classes. Set the class attribute to ``False`` to get the " -"pre-3.7 behaviour." +"to :class:`socketserver.ForkingMixIn` " +"and :class:`socketserver.ThreadingMixIn` classes. Set the class attribute to " +"``False`` to get the pre-3.7 behaviour." msgstr "" #: whatsnew/3.7.rst:1311 @@ -1882,16 +1895,17 @@ msgstr "" #: whatsnew/3.7.rst:1313 msgid "" -":class:`sqlite3.Connection` now exposes the :meth:`~sqlite3.Connection." -"backup` method when the underlying SQLite library is at version 3.6.11 or " -"higher. (Contributed by Lele Gaifax in :issue:`27645`.)" +":class:`sqlite3.Connection` now exposes " +"the :meth:`~sqlite3.Connection.backup` method when the underlying SQLite " +"library is at version 3.6.11 or higher. (Contributed by Lele Gaifax " +"in :issue:`27645`.)" msgstr "" #: whatsnew/3.7.rst:1317 msgid "" -"The *database* argument of :func:`sqlite3.connect` now accepts any :term:" -"`path-like object`, instead of just a string. (Contributed by Anders " -"Lorentsen in :issue:`31843`.)" +"The *database* argument of :func:`sqlite3.connect` now accepts " +"any :term:`path-like object`, instead of just a string. (Contributed by " +"Anders Lorentsen in :issue:`31843`.)" msgstr "" #: whatsnew/3.7.rst:2067 @@ -1900,15 +1914,16 @@ msgstr "" #: whatsnew/3.7.rst:1325 msgid "" -"The :mod:`ssl` module now uses OpenSSL's builtin API instead of :func:`~ssl." -"match_hostname` to check a host name or an IP address. Values are validated " -"during TLS handshake. Any certificate validation error including failing " -"the host name check now raises :exc:`~ssl.SSLCertVerificationError` and " -"aborts the handshake with a proper TLS Alert message. The new exception " -"contains additional information. Host name validation can be customized " -"with :attr:`SSLContext.hostname_checks_common_name `. (Contributed by Christian Heimes in :issue:" -"`31399`.)" +"The :mod:`ssl` module now uses OpenSSL's builtin API instead " +"of :func:`~ssl.match_hostname` to check a host name or an IP address. " +"Values are validated during TLS handshake. Any certificate validation error " +"including failing the host name check now " +"raises :exc:`~ssl.SSLCertVerificationError` and aborts the handshake with a " +"proper TLS Alert message. The new exception contains additional " +"information. Host name validation can be customized " +"with :attr:`SSLContext.hostname_checks_common_name " +"`. (Contributed by Christian " +"Heimes in :issue:`31399`.)" msgstr "" #: whatsnew/3.7.rst:1336 @@ -1927,9 +1942,9 @@ msgstr "" #: whatsnew/3.7.rst:1344 msgid "" -":func:`~ssl.match_hostname` no longer supports partial wildcards like ``www*." -"example.org``. (Contributed by Mandeep Singh in :issue:`23033` and Christian " -"Heimes in :issue:`31399`.)" +":func:`~ssl.match_hostname` no longer supports partial wildcards like " +"``www*.example.org``. (Contributed by Mandeep Singh in :issue:`23033` and " +"Christian Heimes in :issue:`31399`.)" msgstr "" #: whatsnew/3.7.rst:1349 @@ -1944,11 +1959,11 @@ msgstr "" #: whatsnew/3.7.rst:1355 msgid "" "Validation of server certificates containing internationalized domain names " -"(IDNs) is now supported. As part of this change, the :attr:`SSLSocket." -"server_hostname ` attribute now stores the " -"expected hostname in A-label form (``\"xn--pythn-mua.org\"``), rather than " -"the U-label form (``\"pythön.org\"``). (Contributed by Nathaniel J. Smith " -"and Christian Heimes in :issue:`28414`.)" +"(IDNs) is now supported. As part of this change, " +"the :attr:`SSLSocket.server_hostname ` " +"attribute now stores the expected hostname in A-label form (``\"xn--pythn-" +"mua.org\"``), rather than the U-label form (``\"pythön.org\"``). " +"(Contributed by Nathaniel J. Smith and Christian Heimes in :issue:`28414`.)" msgstr "" #: whatsnew/3.7.rst:1362 @@ -1957,34 +1972,37 @@ msgid "" "OpenSSL 1.1.1. At the time of Python 3.7.0 release, OpenSSL 1.1.1 is still " "under development and TLS 1.3 hasn't been finalized yet. The TLS 1.3 " "handshake and protocol behaves slightly differently than TLS 1.2 and " -"earlier, see :ref:`ssl-tlsv1_3`. (Contributed by Christian Heimes in :issue:" -"`32947`, :issue:`20995`, :issue:`29136`, :issue:`30622` and :issue:`33618`)" +"earlier, see :ref:`ssl-tlsv1_3`. (Contributed by Christian Heimes " +"in :issue:`32947`, :issue:`20995`, :issue:`29136`, :issue:`30622` " +"and :issue:`33618`)" msgstr "" #: whatsnew/3.7.rst:1370 msgid "" ":class:`~ssl.SSLSocket` and :class:`~ssl.SSLObject` no longer have a public " "constructor. Direct instantiation was never a documented and supported " -"feature. Instances must be created with :class:`~ssl.SSLContext` methods :" -"meth:`~ssl.SSLContext.wrap_socket` and :meth:`~ssl.SSLContext.wrap_bio`. " -"(Contributed by Christian Heimes in :issue:`32951`)" +"feature. Instances must be created with :class:`~ssl.SSLContext` " +"methods :meth:`~ssl.SSLContext.wrap_socket` " +"and :meth:`~ssl.SSLContext.wrap_bio`. (Contributed by Christian Heimes " +"in :issue:`32951`)" msgstr "" #: whatsnew/3.7.rst:1376 msgid "" "OpenSSL 1.1 APIs for setting the minimum and maximum TLS protocol version " -"are available as :attr:`SSLContext.minimum_version ` and :attr:`SSLContext.maximum_version `. Supported protocols are indicated by several new flags, " -"such as :data:`~ssl.HAS_TLSv1_1`. (Contributed by Christian Heimes in :issue:" -"`32609`.)" +"are available as :attr:`SSLContext.minimum_version " +"` and :attr:`SSLContext.maximum_version " +"`. Supported protocols are indicated by " +"several new flags, such as :data:`~ssl.HAS_TLSv1_1`. (Contributed by " +"Christian Heimes in :issue:`32609`.)" msgstr "" #: whatsnew/3.7.rst:1383 msgid "" -"Added :attr:`ssl.SSLContext.post_handshake_auth` to enable and :meth:`ssl." -"SSLSocket.verify_client_post_handshake` to initiate TLS 1.3 post-handshake " -"authentication. (Contributed by Christian Heimes in :gh:`78851`.)" +"Added :attr:`ssl.SSLContext.post_handshake_auth` to enable " +"and :meth:`ssl.SSLSocket.verify_client_post_handshake` to initiate TLS 1.3 " +"post-handshake authentication. (Contributed by Christian Heimes " +"in :gh:`78851`.)" msgstr "" #: whatsnew/3.7.rst:1389 @@ -2021,19 +2039,21 @@ msgstr "" msgid "" "On Windows the default for *close_fds* was changed from ``False`` to " "``True`` when redirecting the standard handles. It's now possible to set " -"*close_fds* to true when redirecting the standard handles. See :class:" -"`subprocess.Popen`. This means that *close_fds* now defaults to ``True`` on " -"all supported platforms. (Contributed by Segev Finer in :issue:`19764`.)" +"*close_fds* to true when redirecting the standard handles. " +"See :class:`subprocess.Popen`. This means that *close_fds* now defaults to " +"``True`` on all supported platforms. (Contributed by Segev Finer " +"in :issue:`19764`.)" msgstr "" #: whatsnew/3.7.rst:1417 msgid "" -"The subprocess module is now more graceful when handling :exc:" -"`KeyboardInterrupt` during :func:`subprocess.call`, :func:`subprocess.run`, " -"or in a :class:`~subprocess.Popen` context manager. It now waits a short " -"amount of time for the child to exit, before continuing the handling of the " -"``KeyboardInterrupt`` exception. (Contributed by Gregory P. Smith in :issue:" -"`25942`.)" +"The subprocess module is now more graceful when " +"handling :exc:`KeyboardInterrupt` " +"during :func:`subprocess.call`, :func:`subprocess.run`, or in " +"a :class:`~subprocess.Popen` context manager. It now waits a short amount " +"of time for the child to exit, before continuing the handling of the " +"``KeyboardInterrupt`` exception. (Contributed by Gregory P. Smith " +"in :issue:`25942`.)" msgstr "" #: whatsnew/3.7.rst:2083 @@ -2042,8 +2062,8 @@ msgstr "" #: whatsnew/3.7.rst:1429 msgid "" -"The new :func:`sys.breakpointhook` hook function is called by the built-in :" -"func:`breakpoint`. (Contributed by Barry Warsaw in :issue:`31353`.)" +"The new :func:`sys.breakpointhook` hook function is called by the built-" +"in :func:`breakpoint`. (Contributed by Barry Warsaw in :issue:`31353`.)" msgstr "" #: whatsnew/3.7.rst:1433 @@ -2055,11 +2075,11 @@ msgstr "" #: whatsnew/3.7.rst:1437 msgid "" "The new :func:`sys.get_coroutine_origin_tracking_depth` function returns the " -"current coroutine origin tracking depth, as set by the new :func:`sys." -"set_coroutine_origin_tracking_depth`. :mod:`asyncio` has been converted to " -"use this new API instead of the deprecated :func:`sys." -"set_coroutine_wrapper`. (Contributed by Nathaniel J. Smith in :issue:" -"`32591`.)" +"current coroutine origin tracking depth, as set by the " +"new :func:`sys.set_coroutine_origin_tracking_depth`. :mod:`asyncio` has " +"been converted to use this new API instead of the " +"deprecated :func:`sys.set_coroutine_wrapper`. (Contributed by Nathaniel J. " +"Smith in :issue:`32591`.)" msgstr "" #: whatsnew/3.7.rst:1446 @@ -2068,8 +2088,8 @@ msgstr "" #: whatsnew/3.7.rst:1448 msgid "" -":pep:`564` adds six new functions with nanosecond resolution to the :mod:" -"`time` module:" +":pep:`564` adds six new functions with nanosecond resolution to " +"the :mod:`time` module:" msgstr "" #: whatsnew/3.7.rst:1458 @@ -2078,9 +2098,9 @@ msgstr "" #: whatsnew/3.7.rst:1460 msgid "" -":const:`time.CLOCK_BOOTTIME` (Linux): Identical to :const:`time." -"CLOCK_MONOTONIC`, except it also includes any time that the system is " -"suspended." +":const:`time.CLOCK_BOOTTIME` (Linux): Identical " +"to :const:`time.CLOCK_MONOTONIC`, except it also includes any time that the " +"system is suspended." msgstr "" #: whatsnew/3.7.rst:1463 @@ -2139,18 +2159,18 @@ msgstr "" #: whatsnew/3.7.rst:1499 msgid "" -"The new :class:`~types.WrapperDescriptorType`, :class:`~types." -"MethodWrapperType`, :class:`~types.MethodDescriptorType`, and :class:`~types." -"ClassMethodDescriptorType` classes are now available. (Contributed by Manuel " -"Krebber and Guido van Rossum in :issue:`29377`, and Serhiy Storchaka in :" -"issue:`32265`.)" +"The " +"new :class:`~types.WrapperDescriptorType`, :class:`~types.MethodWrapperType`, :class:`~types.MethodDescriptorType`, " +"and :class:`~types.ClassMethodDescriptorType` classes are now available. " +"(Contributed by Manuel Krebber and Guido van Rossum in :issue:`29377`, and " +"Serhiy Storchaka in :issue:`32265`.)" msgstr "" #: whatsnew/3.7.rst:1505 msgid "" "The new :func:`types.resolve_bases` function resolves MRO entries " -"dynamically as specified by :pep:`560`. (Contributed by Ivan Levkivskyi in :" -"issue:`32717`.)" +"dynamically as specified by :pep:`560`. (Contributed by Ivan Levkivskyi " +"in :issue:`32717`.)" msgstr "" #: whatsnew/3.7.rst:1511 @@ -2172,9 +2192,10 @@ msgstr "" msgid "" "The new ``-k`` command-line option allows filtering tests by a name " "substring or a Unix shell-like pattern. For example, ``python -m unittest -k " -"foo`` runs ``foo_tests.SomeTest.test_something``, ``bar_tests.SomeTest." -"test_foo``, but not ``bar_tests.FooTest.test_something``. (Contributed by " -"Jonas Haag in :issue:`32071`.)" +"foo`` runs ``foo_tests.SomeTest.test_something``, " +"``bar_tests.SomeTest.test_foo``, but not " +"``bar_tests.FooTest.test_something``. (Contributed by Jonas Haag " +"in :issue:`32071`.)" msgstr "" #: whatsnew/3.7.rst:1530 @@ -2190,10 +2211,11 @@ msgstr "" #: whatsnew/3.7.rst:1536 msgid "" -"The new :func:`~unittest.mock.seal` function allows sealing :class:" -"`~unittest.mock.Mock` instances, which will disallow further creation of " -"attribute mocks. The seal is applied recursively to all attributes that are " -"themselves mocks. (Contributed by Mario Corchero in :issue:`30541`.)" +"The new :func:`~unittest.mock.seal` function allows " +"sealing :class:`~unittest.mock.Mock` instances, which will disallow further " +"creation of attribute mocks. The seal is applied recursively to all " +"attributes that are themselves mocks. (Contributed by Mario Corchero " +"in :issue:`30541`.)" msgstr "" #: whatsnew/3.7.rst:1544 @@ -2226,8 +2248,8 @@ msgstr "" msgid "" "The new :attr:`UUID.is_safe ` attribute relays " "information from the platform about whether generated UUIDs are generated " -"with a multiprocessing-safe method. (Contributed by Barry Warsaw in :issue:" -"`22807`.)" +"with a multiprocessing-safe method. (Contributed by Barry Warsaw " +"in :issue:`22807`.)" msgstr "" #: whatsnew/3.7.rst:1567 @@ -2292,8 +2314,8 @@ msgstr "" #: whatsnew/3.7.rst:1598 msgid "" -"(Contributed by Nick Coghlan and Victor Stinner in :issue:`20361`, :issue:" -"`32043`, and :issue:`32230`.)" +"(Contributed by Nick Coghlan and Victor Stinner " +"in :issue:`20361`, :issue:`32043`, and :issue:`32230`.)" msgstr "" #: whatsnew/3.7.rst:1601 @@ -2309,9 +2331,10 @@ msgstr "" #: whatsnew/3.7.rst:1609 msgid "" -"As mitigation against DTD and external entity retrieval, the :mod:`xml.dom." -"minidom` and :mod:`xml.sax` modules no longer process external entities by " -"default. (Contributed by Christian Heimes in :gh:`61441`.)" +"As mitigation against DTD and external entity retrieval, " +"the :mod:`xml.dom.minidom` and :mod:`xml.sax` modules no longer process " +"external entities by default. (Contributed by Christian Heimes " +"in :gh:`61441`.)" msgstr "" #: whatsnew/3.7.rst:1616 @@ -2332,9 +2355,9 @@ msgstr "" #: whatsnew/3.7.rst:1627 msgid "" -":meth:`SimpleXMLRPCDispatcher.register_function ` can now be used as a decorator. (Contributed by " -"Xiang Zhang in :issue:`7769`.)" +":meth:`SimpleXMLRPCDispatcher.register_function " +"` can now be used as a decorator. " +"(Contributed by Xiang Zhang in :issue:`7769`.)" msgstr "" #: whatsnew/3.7.rst:1633 @@ -2378,10 +2401,10 @@ msgstr "" #: whatsnew/3.7.rst:1660 msgid "" -"A new API for thread-local storage has been implemented. See :ref:" -"`whatsnew37-pep539` for an overview and :ref:`thread-specific-storage-api` " -"for a complete reference. (Contributed by Masayuki Yamamoto in :issue:" -"`25658`.)" +"A new API for thread-local storage has been implemented. " +"See :ref:`whatsnew37-pep539` for an overview and :ref:`thread-specific-" +"storage-api` for a complete reference. (Contributed by Masayuki Yamamoto " +"in :issue:`25658`.)" msgstr "" #: whatsnew/3.7.rst:1665 @@ -2393,8 +2416,8 @@ msgstr "" #: whatsnew/3.7.rst:1668 msgid "" "The new :c:func:`PyImport_GetModule` function returns the previously " -"imported module with the given name. (Contributed by Eric Snow in :issue:" -"`28411`.)" +"imported module with the given name. (Contributed by Eric Snow " +"in :issue:`28411`.)" msgstr "" #: whatsnew/3.7.rst:1672 @@ -2411,76 +2434,79 @@ msgstr "" #: whatsnew/3.7.rst:1680 msgid "" -"The :mod:`tracemalloc` now exposes a C API through the new :c:func:" -"`PyTraceMalloc_Track` and :c:func:`PyTraceMalloc_Untrack` functions. " -"(Contributed by Victor Stinner in :issue:`30054`.)" +"The :mod:`tracemalloc` now exposes a C API through the " +"new :c:func:`PyTraceMalloc_Track` and :c:func:`PyTraceMalloc_Untrack` " +"functions. (Contributed by Victor Stinner in :issue:`30054`.)" msgstr "" #: whatsnew/3.7.rst:1685 msgid "" -"The new :c:func:`import__find__load__start` and :c:func:" -"`import__find__load__done` static markers can be used to trace module " -"imports. (Contributed by Christian Heimes in :issue:`31574`.)" +"The new :c:func:`import__find__load__start` " +"and :c:func:`import__find__load__done` static markers can be used to trace " +"module imports. (Contributed by Christian Heimes in :issue:`31574`.)" msgstr "" #: whatsnew/3.7.rst:1690 msgid "" -"The fields :c:member:`!name` and :c:member:`!doc` of structures :c:type:" -"`PyMemberDef`, :c:type:`PyGetSetDef`, :c:type:`PyStructSequence_Field`, :c:" -"type:`PyStructSequence_Desc`, and :c:struct:`wrapperbase` are now of type " -"``const char *`` rather of ``char *``. (Contributed by Serhiy Storchaka in :" -"issue:`28761`.)" +"The fields :c:member:`!name` and :c:member:`!doc` of " +"structures :c:type:`PyMemberDef`, :c:type:`PyGetSetDef`, :c:type:`PyStructSequence_Field`, :c:type:`PyStructSequence_Desc`, " +"and :c:struct:`wrapperbase` are now of type ``const char *`` rather of " +"``char *``. (Contributed by Serhiy Storchaka in :issue:`28761`.)" msgstr "" #: whatsnew/3.7.rst:1696 msgid "" -"The result of :c:func:`PyUnicode_AsUTF8AndSize` and :c:func:" -"`PyUnicode_AsUTF8` is now of type ``const char *`` rather of ``char *``. " -"(Contributed by Serhiy Storchaka in :issue:`28769`.)" +"The result of :c:func:`PyUnicode_AsUTF8AndSize` " +"and :c:func:`PyUnicode_AsUTF8` is now of type ``const char *`` rather of " +"``char *``. (Contributed by Serhiy Storchaka in :issue:`28769`.)" msgstr "" #: whatsnew/3.7.rst:1700 msgid "" -"The result of :c:func:`PyMapping_Keys`, :c:func:`PyMapping_Values` and :c:" -"func:`PyMapping_Items` is now always a list, rather than a list or a tuple. " -"(Contributed by Oren Milman in :issue:`28280`.)" +"The result of :c:func:`PyMapping_Keys`, :c:func:`PyMapping_Values` " +"and :c:func:`PyMapping_Items` is now always a list, rather than a list or a " +"tuple. (Contributed by Oren Milman in :issue:`28280`.)" msgstr "" #: whatsnew/3.7.rst:1704 msgid "" -"Added functions :c:func:`PySlice_Unpack` and :c:func:" -"`PySlice_AdjustIndices`. (Contributed by Serhiy Storchaka in :issue:`27867`.)" +"Added functions :c:func:`PySlice_Unpack` " +"and :c:func:`PySlice_AdjustIndices`. (Contributed by Serhiy Storchaka " +"in :issue:`27867`.)" msgstr "" #: whatsnew/3.7.rst:1707 msgid "" -":c:func:`PyOS_AfterFork` is deprecated in favour of the new functions :c:" -"func:`PyOS_BeforeFork`, :c:func:`PyOS_AfterFork_Parent` and :c:func:" -"`PyOS_AfterFork_Child`. (Contributed by Antoine Pitrou in :issue:`16500`.)" +":c:func:`PyOS_AfterFork` is deprecated in favour of the new " +"functions :c:func:`PyOS_BeforeFork`, :c:func:`PyOS_AfterFork_Parent` " +"and :c:func:`PyOS_AfterFork_Child`. (Contributed by Antoine Pitrou " +"in :issue:`16500`.)" msgstr "" #: whatsnew/3.7.rst:1712 msgid "" "The ``PyExc_RecursionErrorInst`` singleton that was part of the public API " "has been removed as its members being never cleared may cause a segfault " -"during finalization of the interpreter. Contributed by Xavier de Gaye in :" -"issue:`22898` and :issue:`30697`." +"during finalization of the interpreter. Contributed by Xavier de Gaye " +"in :issue:`22898` and :issue:`30697`." msgstr "" #: whatsnew/3.7.rst:1717 msgid "" -"Added C API support for timezones with timezone constructors :c:func:" -"`PyTimeZone_FromOffset` and :c:func:`PyTimeZone_FromOffsetAndName`, and " -"access to the UTC singleton with :c:data:`PyDateTime_TimeZone_UTC`. " -"Contributed by Paul Ganssle in :issue:`10381`." +"Added C API support for timezones with timezone " +"constructors :c:func:`PyTimeZone_FromOffset` " +"and :c:func:`PyTimeZone_FromOffsetAndName`, and access to the UTC singleton " +"with :c:data:`PyDateTime_TimeZone_UTC`. Contributed by Paul Ganssle " +"in :issue:`10381`." msgstr "" #: whatsnew/3.7.rst:1722 msgid "" -"The type of results of :c:func:`PyThread_start_new_thread` and :c:func:" -"`PyThread_get_thread_ident`, and the *id* parameter of :c:func:" -"`PyThreadState_SetAsyncExc` changed from :c:expr:`long` to :c:expr:`unsigned " -"long`. (Contributed by Serhiy Storchaka in :issue:`6532`.)" +"The type of results of :c:func:`PyThread_start_new_thread` " +"and :c:func:`PyThread_get_thread_ident`, and the *id* parameter " +"of :c:func:`PyThreadState_SetAsyncExc` changed from :c:expr:`long` " +"to :c:expr:`unsigned long`. (Contributed by Serhiy Storchaka " +"in :issue:`6532`.)" msgstr "" #: whatsnew/3.7.rst:1728 @@ -2493,12 +2519,12 @@ msgstr "" #: whatsnew/3.7.rst:1732 msgid "" "Changes to the startup sequence and the management of dynamic memory " -"allocators mean that the long documented requirement to call :c:func:" -"`Py_Initialize` before calling most C API functions is now relied on more " -"heavily, and failing to abide by it may lead to segfaults in embedding " -"applications. See the :ref:`porting-to-python-37` section in this document " -"and the :ref:`pre-init-safe` section in the C API documentation for more " -"details." +"allocators mean that the long documented requirement to " +"call :c:func:`Py_Initialize` before calling most C API functions is now " +"relied on more heavily, and failing to abide by it may lead to segfaults in " +"embedding applications. See the :ref:`porting-to-python-37` section in this " +"document and the :ref:`pre-init-safe` section in the C API documentation for " +"more details." msgstr "" #: whatsnew/3.7.rst:1740 @@ -2524,8 +2550,8 @@ msgstr "" #: whatsnew/3.7.rst:1752 msgid "" "The *start* and *end* parameters of :c:func:`PyUnicode_FindChar` are now " -"adjusted to behave like string slices. (Contributed by Xiang Zhang in :issue:" -"`28822`.)" +"adjusted to behave like string slices. (Contributed by Xiang Zhang " +"in :issue:`28822`.)" msgstr "" #: whatsnew/3.7.rst:1758 @@ -2534,16 +2560,16 @@ msgstr "" #: whatsnew/3.7.rst:1760 msgid "" -"Support for building ``--without-threads`` has been removed. The :mod:" -"`threading` module is now always available. (Contributed by Antoine Pitrou " -"in :issue:`31370`.)." +"Support for building ``--without-threads`` has been removed. " +"The :mod:`threading` module is now always available. (Contributed by Antoine " +"Pitrou in :issue:`31370`.)." msgstr "" #: whatsnew/3.7.rst:1764 msgid "" -"A full copy of libffi is no longer bundled for use when building the :mod:" -"`_ctypes ` module on non-OSX UNIX platforms. An installed copy of " -"libffi is now required when building ``_ctypes`` on such platforms. " +"A full copy of libffi is no longer bundled for use when building " +"the :mod:`_ctypes ` module on non-OSX UNIX platforms. An installed " +"copy of libffi is now required when building ``_ctypes`` on such platforms. " "(Contributed by Zachary Ware in :issue:`27979`.)" msgstr "" @@ -2572,15 +2598,15 @@ msgstr "" msgid "" "The overhead of calling many methods of various standard library classes " "implemented in C has been significantly reduced by porting more code to use " -"the ``METH_FASTCALL`` convention. (Contributed by Victor Stinner in :issue:" -"`29300`, :issue:`29507`, :issue:`29452`, and :issue:`29286`.)" +"the ``METH_FASTCALL`` convention. (Contributed by Victor Stinner " +"in :issue:`29300`, :issue:`29507`, :issue:`29452`, and :issue:`29286`.)" msgstr "" #: whatsnew/3.7.rst:1792 msgid "" "Various optimizations have reduced Python startup time by 10% on Linux and " -"up to 30% on macOS. (Contributed by Victor Stinner, INADA Naoki in :issue:" -"`29585`, and Ivan Levkivskyi in :issue:`31333`.)" +"up to 30% on macOS. (Contributed by Victor Stinner, INADA Naoki " +"in :issue:`29585`, and Ivan Levkivskyi in :issue:`31333`.)" msgstr "" #: whatsnew/3.7.rst:1797 @@ -2599,8 +2625,8 @@ msgstr "" #: whatsnew/3.7.rst:1806 msgid "" "The :func:`asyncio.get_event_loop` function has been reimplemented in C to " -"make it up to 15 times faster. (Contributed by Yury Selivanov in :issue:" -"`32296`.)" +"make it up to 15 times faster. (Contributed by Yury Selivanov " +"in :issue:`32296`.)" msgstr "" #: whatsnew/3.7.rst:1810 @@ -2629,16 +2655,17 @@ msgstr "" #: whatsnew/3.7.rst:1823 msgid "" -"As a result of :ref:`PEP 560 work `, the import time of :" -"mod:`typing` has been reduced by a factor of 7, and many typing operations " -"are now faster. (Contributed by Ivan Levkivskyi in :issue:`32226`.)" +"As a result of :ref:`PEP 560 work `, the import time " +"of :mod:`typing` has been reduced by a factor of 7, and many typing " +"operations are now faster. (Contributed by Ivan Levkivskyi " +"in :issue:`32226`.)" msgstr "" #: whatsnew/3.7.rst:1828 msgid "" ":func:`sorted` and :meth:`list.sort` have been optimized for common cases to " -"be up to 40-75% faster. (Contributed by Elliot Gorokhovsky in :issue:" -"`28685`.)" +"be up to 40-75% faster. (Contributed by Elliot Gorokhovsky " +"in :issue:`28685`.)" msgstr "" #: whatsnew/3.7.rst:1832 @@ -2650,8 +2677,9 @@ msgstr "" #: whatsnew/3.7.rst:1835 msgid "" ":func:`hasattr` and :func:`getattr` are now about 4 times faster when *name* " -"is not found and *obj* does not override :meth:`object.__getattr__` or :meth:" -"`object.__getattribute__`. (Contributed by INADA Naoki in :issue:`32544`.)" +"is not found and *obj* does not override :meth:`object.__getattr__` " +"or :meth:`object.__getattribute__`. (Contributed by INADA Naoki " +"in :issue:`32544`.)" msgstr "" #: whatsnew/3.7.rst:1840 @@ -2700,39 +2728,39 @@ msgstr "" msgid "" ":func:`re.compile` now converts ``flags`` parameter to int object if it is " "``RegexFlag``. It is now as fast as Python 3.5, and faster than Python 3.6 " -"by about 10% depending on the pattern. (Contributed by INADA Naoki in :issue:" -"`31671`.)" +"by about 10% depending on the pattern. (Contributed by INADA Naoki " +"in :issue:`31671`.)" msgstr "" #: whatsnew/3.7.rst:1871 msgid "" -"The :meth:`~selectors.BaseSelector.modify` methods of classes :class:" -"`selectors.EpollSelector`, :class:`selectors.PollSelector` and :class:" -"`selectors.DevpollSelector` may be around 10% faster under heavy loads. " -"(Contributed by Giampaolo Rodola' in :issue:`30014`)" +"The :meth:`~selectors.BaseSelector.modify` methods of " +"classes :class:`selectors.EpollSelector`, :class:`selectors.PollSelector` " +"and :class:`selectors.DevpollSelector` may be around 10% faster under heavy " +"loads. (Contributed by Giampaolo Rodola' in :issue:`30014`)" msgstr "" #: whatsnew/3.7.rst:1876 msgid "" "Constant folding has been moved from the peephole optimizer to the new AST " "optimizer, which is able perform optimizations more consistently. " -"(Contributed by Eugene Toder and INADA Naoki in :issue:`29469` and :issue:" -"`11549`.)" +"(Contributed by Eugene Toder and INADA Naoki in :issue:`29469` " +"and :issue:`11549`.)" msgstr "" #: whatsnew/3.7.rst:1881 msgid "" "Most functions and methods in :mod:`abc` have been rewritten in C. This " -"makes creation of abstract base classes, and calling :func:`isinstance` and :" -"func:`issubclass` on them 1.5x faster. This also reduces Python start-up " -"time by up to 10%. (Contributed by Ivan Levkivskyi and INADA Naoki in :issue:" -"`31333`)" +"makes creation of abstract base classes, and calling :func:`isinstance` " +"and :func:`issubclass` on them 1.5x faster. This also reduces Python start-" +"up time by up to 10%. (Contributed by Ivan Levkivskyi and INADA Naoki " +"in :issue:`31333`)" msgstr "" #: whatsnew/3.7.rst:1887 msgid "" -"Significant speed improvements to alternate constructors for :class:" -"`datetime.date` and :class:`datetime.datetime` by using fast-path " +"Significant speed improvements to alternate constructors " +"for :class:`datetime.date` and :class:`datetime.datetime` by using fast-path " "constructors when not constructing subclasses. (Contributed by Paul Ganssle " "in :issue:`32403`)" msgstr "" @@ -2759,9 +2787,10 @@ msgstr "" #: whatsnew/3.7.rst:1905 msgid "" "Trace hooks may now opt out of receiving the ``line`` and opt into receiving " -"the ``opcode`` events from the interpreter by setting the corresponding new :" -"attr:`~frame.f_trace_lines` and :attr:`~frame.f_trace_opcodes` attributes on " -"the frame being traced. (Contributed by Nick Coghlan in :issue:`31344`.)" +"the ``opcode`` events from the interpreter by setting the corresponding " +"new :attr:`~frame.f_trace_lines` and :attr:`~frame.f_trace_opcodes` " +"attributes on the frame being traced. (Contributed by Nick Coghlan " +"in :issue:`31344`.)" msgstr "" #: whatsnew/3.7.rst:1910 @@ -2771,8 +2800,8 @@ msgid "" "(previously unset), and their ``__spec__.origin`` is also set to ``None`` " "(previously the string ``\"namespace\"``). See :issue:`32305`. Also, the " "namespace module object's ``__spec__.loader`` is set to the same value as " -"``__loader__`` (previously, the former was set to ``None``). See :issue:" -"`32303`." +"``__loader__`` (previously, the former was set to ``None``). " +"See :issue:`32303`." msgstr "" #: whatsnew/3.7.rst:1918 @@ -2786,8 +2815,8 @@ msgstr "" msgid "" "The ``distutils`` ``upload`` command no longer tries to change CR end-of-" "line characters to CRLF. This fixes a corruption issue with sdists that " -"ended with a byte equivalent to CR. (Contributed by Bo Bayles in :issue:" -"`32304`.)" +"ended with a byte equivalent to CR. (Contributed by Bo Bayles " +"in :issue:`32304`.)" msgstr "" #: whatsnew/3.7.rst:1929 @@ -2812,8 +2841,9 @@ msgstr "" msgid "" "Returning a subclass of :class:`complex` from :meth:`object.__complex__` is " "deprecated and will be an error in future Python versions. This makes " -"``__complex__()`` consistent with :meth:`object.__int__` and :meth:`object." -"__float__`. (Contributed by Serhiy Storchaka in :issue:`28894`.)" +"``__complex__()`` consistent with :meth:`object.__int__` " +"and :meth:`object.__float__`. (Contributed by Serhiy Storchaka " +"in :issue:`28894`.)" msgstr "" #: whatsnew/3.7.rst:1951 @@ -2827,8 +2857,8 @@ msgstr "" #: whatsnew/3.7.rst:1956 msgid "" ":func:`aifc.openfp` has been deprecated and will be removed in Python 3.9. " -"Use :func:`aifc.open` instead. (Contributed by Brian Curtin in :issue:" -"`31985`.)" +"Use :func:`aifc.open` instead. (Contributed by Brian Curtin " +"in :issue:`31985`.)" msgstr "" #: whatsnew/3.7.rst:1966 @@ -2836,15 +2866,15 @@ msgid "" "Support for directly ``await``-ing instances of :class:`asyncio.Lock` and " "other asyncio synchronization primitives has been deprecated. An " "asynchronous context manager must be used in order to acquire and release " -"the synchronization resource. (Contributed by Andrew Svetlov in :issue:" -"`32253`.)" +"the synchronization resource. (Contributed by Andrew Svetlov " +"in :issue:`32253`.)" msgstr "" #: whatsnew/3.7.rst:1972 msgid "" "The :meth:`!asyncio.Task.current_task` and :meth:`!asyncio.Task.all_tasks` " -"methods have been deprecated. (Contributed by Andrew Svetlov in :issue:" -"`32250`.)" +"methods have been deprecated. (Contributed by Andrew Svetlov " +"in :issue:`32250`.)" msgstr "" #: whatsnew/3.7.rst:1980 @@ -2870,8 +2900,8 @@ msgid "" "classes will raise a :exc:`TypeError` (e.g. ``1 in Color``); similarly, " "attempting to check for non-Flag objects in a :class:`Flag` member will " "raise :exc:`TypeError` (e.g. ``1 in Perm.RW``); currently, both operations " -"return :const:`False` instead. (Contributed by Ethan Furman in :issue:" -"`33217`.)" +"return :const:`False` instead. (Contributed by Ethan Furman " +"in :issue:`33217`.)" msgstr "" #: whatsnew/3.7.rst:2009 @@ -2881,18 +2911,19 @@ msgstr "" #: whatsnew/3.7.rst:2011 msgid "" "Using non-integer value for selecting a plural form in :mod:`gettext` is now " -"deprecated. It never correctly worked. (Contributed by Serhiy Storchaka in :" -"issue:`28692`.)" +"deprecated. It never correctly worked. (Contributed by Serhiy Storchaka " +"in :issue:`28692`.)" msgstr "" #: whatsnew/3.7.rst:2019 msgid "" -"Methods :meth:`!MetaPathFinder.find_module` (replaced by :meth:" -"`MetaPathFinder.find_spec() `) and :" -"meth:`!PathEntryFinder.find_loader` (replaced by :meth:`PathEntryFinder." -"find_spec() `) both deprecated in " -"Python 3.4 now emit :exc:`DeprecationWarning`. (Contributed by Matthias " -"Bussonnier in :issue:`29576`.)" +"Methods :meth:`!MetaPathFinder.find_module` (replaced " +"by :meth:`MetaPathFinder.find_spec() " +"`) and :meth:`!" +"PathEntryFinder.find_loader` (replaced by :meth:`PathEntryFinder.find_spec() " +"`) both deprecated in Python 3.4 " +"now emit :exc:`DeprecationWarning`. (Contributed by Matthias Bussonnier " +"in :issue:`29576`.)" msgstr "" #: whatsnew/3.7.rst:2030 @@ -2924,22 +2955,24 @@ msgstr "" #: whatsnew/3.7.rst:2051 msgid "" ":mod:`!dummy_threading` and :mod:`!_dummy_thread` have been deprecated. It " -"is no longer possible to build Python with threading disabled. Use :mod:" -"`threading` instead. (Contributed by Antoine Pitrou in :issue:`31370`.)" +"is no longer possible to build Python with threading disabled. " +"Use :mod:`threading` instead. (Contributed by Antoine Pitrou " +"in :issue:`31370`.)" msgstr "" #: whatsnew/3.7.rst:2060 msgid "" -"The silent argument value truncation in :func:`socket.htons` and :func:" -"`socket.ntohs` has been deprecated. In future versions of Python, if the " -"passed argument is larger than 16 bits, an exception will be raised. " +"The silent argument value truncation in :func:`socket.htons` " +"and :func:`socket.ntohs` has been deprecated. In future versions of Python, " +"if the passed argument is larger than 16 bits, an exception will be raised. " "(Contributed by Oren Milman in :issue:`28332`.)" msgstr "" #: whatsnew/3.7.rst:2069 msgid "" -":func:`ssl.wrap_socket` is deprecated. Use :meth:`ssl.SSLContext." -"wrap_socket` instead. (Contributed by Christian Heimes in :issue:`28124`.)" +":func:`ssl.wrap_socket` is deprecated. " +"Use :meth:`ssl.SSLContext.wrap_socket` instead. (Contributed by Christian " +"Heimes in :issue:`28124`.)" msgstr "" #: whatsnew/3.7.rst:2075 @@ -2949,21 +2982,21 @@ msgstr "" #: whatsnew/3.7.rst:2077 msgid "" ":func:`sunau.openfp` has been deprecated and will be removed in Python 3.9. " -"Use :func:`sunau.open` instead. (Contributed by Brian Curtin in :issue:" -"`31985`.)" +"Use :func:`sunau.open` instead. (Contributed by Brian Curtin " +"in :issue:`31985`.)" msgstr "" #: whatsnew/3.7.rst:2085 msgid "" -"Deprecated :func:`sys.set_coroutine_wrapper` and :func:`sys." -"get_coroutine_wrapper`." +"Deprecated :func:`sys.set_coroutine_wrapper` " +"and :func:`sys.get_coroutine_wrapper`." msgstr "" #: whatsnew/3.7.rst:2088 msgid "" "The undocumented ``sys.callstats()`` function has been deprecated and will " -"be removed in a future Python version. (Contributed by Victor Stinner in :" -"issue:`28799`.)" +"be removed in a future Python version. (Contributed by Victor Stinner " +"in :issue:`28799`.)" msgstr "" #: whatsnew/3.7.rst:2094 @@ -2973,8 +3006,8 @@ msgstr "" #: whatsnew/3.7.rst:2096 msgid "" ":func:`wave.openfp` has been deprecated and will be removed in Python 3.9. " -"Use :func:`wave.open` instead. (Contributed by Brian Curtin in :issue:" -"`31985`.)" +"Use :func:`wave.open` instead. (Contributed by Brian Curtin " +"in :issue:`31985`.)" msgstr "" #: whatsnew/3.7.rst:2102 @@ -2986,16 +3019,16 @@ msgid "" "Function :c:func:`PySlice_GetIndicesEx` is deprecated and replaced with a " "macro if ``Py_LIMITED_API`` is not set or set to a value in the range " "between ``0x03050400`` and ``0x03060000`` (not inclusive), or is " -"``0x03060100`` or higher. (Contributed by Serhiy Storchaka in :issue:" -"`27867`.)" +"``0x03060100`` or higher. (Contributed by Serhiy Storchaka " +"in :issue:`27867`.)" msgstr "" #: whatsnew/3.7.rst:2109 msgid "" -":c:func:`PyOS_AfterFork` has been deprecated. Use :c:func:" -"`PyOS_BeforeFork`, :c:func:`PyOS_AfterFork_Parent` or :c:func:" -"`PyOS_AfterFork_Child()` instead. (Contributed by Antoine Pitrou in :issue:" -"`16500`.)" +":c:func:`PyOS_AfterFork` has been deprecated. " +"Use :c:func:`PyOS_BeforeFork`, :c:func:`PyOS_AfterFork_Parent` " +"or :c:func:`PyOS_AfterFork_Child()` instead. (Contributed by Antoine Pitrou " +"in :issue:`16500`.)" msgstr "" #: whatsnew/3.7.rst:2117 @@ -3040,10 +3073,10 @@ msgstr "" #: whatsnew/3.7.rst:2136 msgid "" "CPython's own `CI configuration file `_ provides an example of using the SSL :source:" -"`compatibility testing infrastructure ` in " -"CPython's test suite to build and link against OpenSSL 1.1.0 rather than an " -"outdated system provided OpenSSL." +"v3.7.13/.travis.yml>`_ provides an example of using the " +"SSL :source:`compatibility testing infrastructure ` in CPython's test suite to build and link against OpenSSL " +"1.1.0 rather than an outdated system provided OpenSSL." msgstr "" #: whatsnew/3.7.rst:2145 @@ -3100,9 +3133,9 @@ msgstr "" msgid "" "Removed previously deprecated in Python 2.4 classes ``Plist``, ``Dict`` and " "``_InternalDict`` in the :mod:`plistlib` module. Dict values in the result " -"of functions :func:`~plistlib.readPlist` and :func:`~plistlib." -"readPlistFromBytes` are now normal dicts. You no longer can use attribute " -"access to access items of these dictionaries." +"of functions :func:`~plistlib.readPlist` " +"and :func:`~plistlib.readPlistFromBytes` are now normal dicts. You no " +"longer can use attribute access to access items of these dictionaries." msgstr "" #: whatsnew/3.7.rst:2180 @@ -3124,9 +3157,9 @@ msgstr "" msgid "" "Direct instantiation of :class:`ssl.SSLSocket` and :class:`ssl.SSLObject` " "objects is now prohibited. The constructors were never documented, tested, " -"or designed as public constructors. Users were supposed to use :func:`ssl." -"wrap_socket` or :class:`ssl.SSLContext`. (Contributed by Christian Heimes " -"in :issue:`32951`.)" +"or designed as public constructors. Users were supposed to " +"use :func:`ssl.wrap_socket` or :class:`ssl.SSLContext`. (Contributed by " +"Christian Heimes in :issue:`32951`.)" msgstr "" #: whatsnew/3.7.rst:2197 @@ -3193,10 +3226,10 @@ msgstr "" #: whatsnew/3.7.rst:2243 msgid "" -":pep:`479` is enabled for all code in Python 3.7, meaning that :exc:" -"`StopIteration` exceptions raised directly or indirectly in coroutines and " -"generators are transformed into :exc:`RuntimeError` exceptions. (Contributed " -"by Yury Selivanov in :issue:`32670`.)" +":pep:`479` is enabled for all code in Python 3.7, meaning " +"that :exc:`StopIteration` exceptions raised directly or indirectly in " +"coroutines and generators are transformed into :exc:`RuntimeError` " +"exceptions. (Contributed by Yury Selivanov in :issue:`32670`.)" msgstr "" #: whatsnew/3.7.rst:2249 @@ -3224,8 +3257,8 @@ msgid "" "Python 3.7 now correctly raises a :exc:`SyntaxError`, as a generator " "expression always needs to be directly inside a set of parentheses and " "cannot have a comma on either side, and the duplication of the parentheses " -"can be omitted only on calls. (Contributed by Serhiy Storchaka in :issue:" -"`32012` and :issue:`32023`.)" +"can be omitted only on calls. (Contributed by Serhiy Storchaka " +"in :issue:`32012` and :issue:`32023`.)" msgstr "" #: whatsnew/3.7.rst:2266 @@ -3247,17 +3280,19 @@ msgstr "" #: whatsnew/3.7.rst:2278 msgid "" ":meth:`socketserver.ThreadingMixIn.server_close` now waits until all non-" -"daemon threads complete. Set the new :attr:`socketserver.ThreadingMixIn." -"block_on_close` class attribute to ``False`` to get the pre-3.7 behaviour. " -"(Contributed by Victor Stinner in :issue:`31233` and :issue:`33540`.)" +"daemon threads complete. Set the " +"new :attr:`socketserver.ThreadingMixIn.block_on_close` class attribute to " +"``False`` to get the pre-3.7 behaviour. (Contributed by Victor Stinner " +"in :issue:`31233` and :issue:`33540`.)" msgstr "" #: whatsnew/3.7.rst:2284 msgid "" ":meth:`socketserver.ForkingMixIn.server_close` now waits until all child " -"processes complete. Set the new :attr:`socketserver.ForkingMixIn." -"block_on_close` class attribute to ``False`` to get the pre-3.7 behaviour. " -"(Contributed by Victor Stinner in :issue:`31151` and :issue:`33540`.)" +"processes complete. Set the " +"new :attr:`socketserver.ForkingMixIn.block_on_close` class attribute to " +"``False`` to get the pre-3.7 behaviour. (Contributed by Victor Stinner " +"in :issue:`31151` and :issue:`33540`.)" msgstr "" #: whatsnew/3.7.rst:2290 @@ -3276,19 +3311,19 @@ msgstr "" #: whatsnew/3.7.rst:2298 msgid "" -"A format string argument for :meth:`string.Formatter.format` is now :ref:" -"`positional-only `. Passing it as a keyword " -"argument was deprecated in Python 3.5. (Contributed by Serhiy Storchaka in :" -"issue:`29193`.)" +"A format string argument for :meth:`string.Formatter.format` is " +"now :ref:`positional-only `. Passing it as a " +"keyword argument was deprecated in Python 3.5. (Contributed by Serhiy " +"Storchaka in :issue:`29193`.)" msgstr "" #: whatsnew/3.7.rst:2303 msgid "" -"Attributes :attr:`~http.cookies.Morsel.key`, :attr:`~http.cookies.Morsel." -"value` and :attr:`~http.cookies.Morsel.coded_value` of class :class:`http." -"cookies.Morsel` are now read-only. Assigning to them was deprecated in " -"Python 3.5. Use the :meth:`~http.cookies.Morsel.set` method for setting " -"them. (Contributed by Serhiy Storchaka in :issue:`29192`.)" +"Attributes :attr:`~http.cookies.Morsel.key`, :attr:`~http.cookies.Morsel.value` " +"and :attr:`~http.cookies.Morsel.coded_value` of " +"class :class:`http.cookies.Morsel` are now read-only. Assigning to them was " +"deprecated in Python 3.5. Use the :meth:`~http.cookies.Morsel.set` method " +"for setting them. (Contributed by Serhiy Storchaka in :issue:`29192`.)" msgstr "" #: whatsnew/3.7.rst:2311 @@ -3301,8 +3336,8 @@ msgstr "" #: whatsnew/3.7.rst:2317 msgid "" -"The :attr:`struct.Struct.format` type is now :class:`str` instead of :class:" -"`bytes`. (Contributed by Victor Stinner in :issue:`21071`.)" +"The :attr:`struct.Struct.format` type is now :class:`str` instead " +"of :class:`bytes`. (Contributed by Victor Stinner in :issue:`21071`.)" msgstr "" #: whatsnew/3.7.rst:2320 @@ -3335,10 +3370,10 @@ msgstr "" #: whatsnew/3.7.rst:2337 msgid "" -"Because :func:`shutil.rmtree` is now implemented using the :func:`os." -"scandir` function, the user specified handler *onerror* is now called with " -"the first argument ``os.scandir`` instead of ``os.listdir`` when listing the " -"directory is failed." +"Because :func:`shutil.rmtree` is now implemented using " +"the :func:`os.scandir` function, the user specified handler *onerror* is now " +"called with the first argument ``os.scandir`` instead of ``os.listdir`` when " +"listing the directory is failed." msgstr "" #: whatsnew/3.7.rst:2342 @@ -3401,40 +3436,43 @@ msgstr "" #: whatsnew/3.7.rst:2385 msgid "" -"On OSes that support :const:`socket.SOCK_NONBLOCK` or :const:`socket." -"SOCK_CLOEXEC` bit flags, the :attr:`socket.type ` no " -"longer has them applied. Therefore, checks like ``if sock.type == socket." -"SOCK_STREAM`` work as expected on all platforms. (Contributed by Yury " -"Selivanov in :issue:`32331`.)" +"On OSes that support :const:`socket.SOCK_NONBLOCK` " +"or :const:`socket.SOCK_CLOEXEC` bit flags, the :attr:`socket.type " +"` no longer has them applied. Therefore, checks like " +"``if sock.type == socket.SOCK_STREAM`` work as expected on all platforms. " +"(Contributed by Yury Selivanov in :issue:`32331`.)" msgstr "" #: whatsnew/3.7.rst:2392 msgid "" -"On Windows the default for the *close_fds* argument of :class:`subprocess." -"Popen` was changed from :const:`False` to :const:`True` when redirecting the " -"standard handles. If you previously depended on handles being inherited when " -"using :class:`subprocess.Popen` with standard io redirection, you will have " -"to pass ``close_fds=False`` to preserve the previous behaviour, or use :attr:" -"`STARTUPINFO.lpAttributeList `." +"On Windows the default for the *close_fds* argument " +"of :class:`subprocess.Popen` was changed from :const:`False` " +"to :const:`True` when redirecting the standard handles. If you previously " +"depended on handles being inherited when using :class:`subprocess.Popen` " +"with standard io redirection, you will have to pass ``close_fds=False`` to " +"preserve the previous behaviour, or use :attr:`STARTUPINFO.lpAttributeList " +"`." msgstr "" #: whatsnew/3.7.rst:2400 msgid "" ":meth:`importlib.machinery.PathFinder.invalidate_caches` -- which implicitly " -"affects :func:`importlib.invalidate_caches` -- now deletes entries in :data:" -"`sys.path_importer_cache` which are set to ``None``. (Contributed by Brett " -"Cannon in :issue:`33169`.)" +"affects :func:`importlib.invalidate_caches` -- now deletes entries " +"in :data:`sys.path_importer_cache` which are set to ``None``. (Contributed " +"by Brett Cannon in :issue:`33169`.)" msgstr "" #: whatsnew/3.7.rst:2405 msgid "" -"In :mod:`asyncio`, :meth:`loop.sock_recv() `, :meth:" -"`loop.sock_sendall() `, :meth:`loop.sock_accept() " -"`, :meth:`loop.getaddrinfo() `, :meth:`loop.getnameinfo() ` have " -"been changed to be proper coroutine methods to match their documentation. " -"Previously, these methods returned :class:`asyncio.Future` instances. " -"(Contributed by Yury Selivanov in :issue:`32327`.)" +"In :mod:`asyncio`, :meth:`loop.sock_recv() " +"`, :meth:`loop.sock_sendall() " +"`, :meth:`loop.sock_accept() " +"`, :meth:`loop.getaddrinfo() " +"`, :meth:`loop.getnameinfo() " +"` have been changed to be proper coroutine methods " +"to match their documentation. Previously, these methods " +"returned :class:`asyncio.Future` instances. (Contributed by Yury Selivanov " +"in :issue:`32327`.)" msgstr "" #: whatsnew/3.7.rst:2416 @@ -3447,16 +3485,16 @@ msgstr "" #: whatsnew/3.7.rst:2420 msgid "" ":attr:`Struct.format ` is now a :class:`str` instance " -"instead of a :class:`bytes` instance. (Contributed by Victor Stinner in :" -"issue:`21071`.)" +"instead of a :class:`bytes` instance. (Contributed by Victor Stinner " +"in :issue:`21071`.)" msgstr "" #: whatsnew/3.7.rst:2424 msgid "" ":mod:`argparse` subparsers can now be made mandatory by passing " -"``required=True`` to :meth:`ArgumentParser.add_subparsers() `. (Contributed by Anthony Sottile in :issue:" -"`26510`.)" +"``required=True`` to :meth:`ArgumentParser.add_subparsers() " +"`. (Contributed by Anthony Sottile " +"in :issue:`26510`.)" msgstr "" #: whatsnew/3.7.rst:2428 @@ -3474,8 +3512,9 @@ msgid "" "cannot tolerate such exceptions, the new :meth:`Calendar.itermonthdays3 " "` and :meth:`Calendar.itermonthdays4 " "` can be used. The new methods return " -"tuples and are not restricted by the range supported by :class:`datetime." -"date`. (Contributed by Alexander Belopolsky in :issue:`28292`.)" +"tuples and are not restricted by the range supported " +"by :class:`datetime.date`. (Contributed by Alexander Belopolsky " +"in :issue:`28292`.)" msgstr "" #: whatsnew/3.7.rst:2442 @@ -3487,9 +3526,9 @@ msgstr "" #: whatsnew/3.7.rst:2445 msgid "" "The ``submit()`` method of :class:`concurrent.futures.ThreadPoolExecutor` " -"and :class:`concurrent.futures.ProcessPoolExecutor` now raises a :exc:" -"`RuntimeError` if called during interpreter shutdown. (Contributed by Mark " -"Nemec in :issue:`33097`.)" +"and :class:`concurrent.futures.ProcessPoolExecutor` now raises " +"a :exc:`RuntimeError` if called during interpreter shutdown. (Contributed by " +"Mark Nemec in :issue:`33097`.)" msgstr "" #: whatsnew/3.7.rst:2450 @@ -3503,9 +3542,9 @@ msgstr "" #: whatsnew/3.7.rst:2456 msgid "" -"Several undocumented internal imports were removed. One example is that ``os." -"errno`` is no longer available; use ``import errno`` directly instead. Note " -"that such undocumented internal imports may be removed any time without " +"Several undocumented internal imports were removed. One example is that " +"``os.errno`` is no longer available; use ``import errno`` directly instead. " +"Note that such undocumented internal imports may be removed any time without " "notice, even in micro version releases." msgstr "" @@ -3516,13 +3555,13 @@ msgstr "" #: whatsnew/3.7.rst:2466 msgid "" "The function :c:func:`PySlice_GetIndicesEx` is considered unsafe for " -"resizable sequences. If the slice indices are not instances of :class:" -"`int`, but objects that implement the :meth:`!__index__` method, the " -"sequence can be resized after passing its length to :c:func:`!" +"resizable sequences. If the slice indices are not instances " +"of :class:`int`, but objects that implement the :meth:`!__index__` method, " +"the sequence can be resized after passing its length to :c:func:`!" "PySlice_GetIndicesEx`. This can lead to returning indices out of the length " -"of the sequence. For avoiding possible problems use new functions :c:func:" -"`PySlice_Unpack` and :c:func:`PySlice_AdjustIndices`. (Contributed by Serhiy " -"Storchaka in :issue:`27867`.)" +"of the sequence. For avoiding possible problems use new " +"functions :c:func:`PySlice_Unpack` and :c:func:`PySlice_AdjustIndices`. " +"(Contributed by Serhiy Storchaka in :issue:`27867`.)" msgstr "" #: whatsnew/3.7.rst:2477 @@ -3544,9 +3583,9 @@ msgstr "" #: whatsnew/3.7.rst:2489 msgid "" "The file used to override :data:`sys.path` is now called ``._pth`` instead of ``'sys.path'``. See :ref:" -"`windows_finding_modules` for more information. (Contributed by Steve Dower " -"in :issue:`28137`.)" +"executable>._pth`` instead of ``'sys.path'``. " +"See :ref:`windows_finding_modules` for more information. (Contributed by " +"Steve Dower in :issue:`28137`.)" msgstr "" #: whatsnew/3.7.rst:2496 @@ -3577,9 +3616,9 @@ msgstr "" #: whatsnew/3.7.rst:2515 msgid "" -"warnings filters added by an embedding application with :c:func:" -"`PySys_AddWarnOption` should now more consistently take precedence over the " -"default filters set by the interpreter" +"warnings filters added by an embedding application " +"with :c:func:`PySys_AddWarnOption` should now more consistently take " +"precedence over the default filters set by the interpreter" msgstr "" #: whatsnew/3.7.rst:2519 @@ -3588,8 +3627,8 @@ msgid "" "setting :c:data:`Py_BytesWarningFlag` to a value greater than one is no " "longer sufficient to both emit :exc:`BytesWarning` messages and have them " "converted to exceptions. Instead, the flag must be set (to cause the " -"warnings to be emitted in the first place), and an explicit ``error::" -"BytesWarning`` warnings filter added to convert them to exceptions." +"warnings to be emitted in the first place), and an explicit " +"``error::BytesWarning`` warnings filter added to convert them to exceptions." msgstr "" #: whatsnew/3.7.rst:2526 @@ -3618,8 +3657,9 @@ msgid "" "respects all of the same environment settings as :c:func:`Py_Main` (in " "earlier Python versions, it respected an ill-defined subset of those " "environment variables, while in Python 3.7.0 it didn't read any of them due " -"to :issue:`34247`). If this behavior is unwanted, set :c:data:" -"`Py_IgnoreEnvironmentFlag` to 1 before calling :c:func:`Py_Initialize`." +"to :issue:`34247`). If this behavior is unwanted, " +"set :c:data:`Py_IgnoreEnvironmentFlag` to 1 before " +"calling :c:func:`Py_Initialize`." msgstr "" #: whatsnew/3.7.rst:2546 @@ -3657,12 +3697,12 @@ msgstr "" #: whatsnew/3.7.rst:2568 msgid "" -"Due to significant security concerns, the *reuse_address* parameter of :meth:" -"`asyncio.loop.create_datagram_endpoint` is no longer supported. This is " -"because of the behavior of the socket option ``SO_REUSEADDR`` in UDP. For " -"more details, see the documentation for ``loop.create_datagram_endpoint()``. " -"(Contributed by Kyle Stanley, Antoine Pitrou, and Yury Selivanov in :issue:" -"`37228`.)" +"Due to significant security concerns, the *reuse_address* parameter " +"of :meth:`asyncio.loop.create_datagram_endpoint` is no longer supported. " +"This is because of the behavior of the socket option ``SO_REUSEADDR`` in " +"UDP. For more details, see the documentation for " +"``loop.create_datagram_endpoint()``. (Contributed by Kyle Stanley, Antoine " +"Pitrou, and Yury Selivanov in :issue:`37228`.)" msgstr "" #: whatsnew/3.7.rst:2576 @@ -3672,13 +3712,14 @@ msgstr "" #: whatsnew/3.7.rst:2578 msgid "" "Earlier Python versions allowed using both ``;`` and ``&`` as query " -"parameter separators in :func:`urllib.parse.parse_qs` and :func:`urllib." -"parse.parse_qsl`. Due to security concerns, and to conform with newer W3C " -"recommendations, this has been changed to allow only a single separator key, " -"with ``&`` as the default. This change also affects :func:`cgi.parse` and :" -"func:`cgi.parse_multipart` as they use the affected functions internally. " -"For more details, please see their respective documentation. (Contributed by " -"Adam Goldschmidt, Senthil Kumaran and Ken Jin in :issue:`42967`.)" +"parameter separators in :func:`urllib.parse.parse_qs` " +"and :func:`urllib.parse.parse_qsl`. Due to security concerns, and to " +"conform with newer W3C recommendations, this has been changed to allow only " +"a single separator key, with ``&`` as the default. This change also " +"affects :func:`cgi.parse` and :func:`cgi.parse_multipart` as they use the " +"affected functions internally. For more details, please see their respective " +"documentation. (Contributed by Adam Goldschmidt, Senthil Kumaran and Ken Jin " +"in :issue:`42967`.)" msgstr "" #: whatsnew/3.7.rst:2589 @@ -3700,8 +3741,8 @@ msgid "" "forms of attacks. Following the WHATWG specification that updates RFC 3986, " "ASCII newline ``\\n``, ``\\r`` and tab ``\\t`` characters are stripped from " "the URL by the parser :func:`urllib.parse` preventing such attacks. The " -"removal characters are controlled by a new module level variable ``urllib." -"parse._UNSAFE_URL_BYTES_TO_REMOVE``. (See :gh:`88048`)" +"removal characters are controlled by a new module level variable " +"``urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE``. (See :gh:`88048`)" msgstr "" #: whatsnew/3.7.rst:2606 diff --git a/whatsnew/3.8.po b/whatsnew/3.8.po index c22cb12ce..208c01ed3 100644 --- a/whatsnew/3.8.po +++ b/whatsnew/3.8.po @@ -31,8 +31,8 @@ msgstr "Raymond Hettinger" #: whatsnew/3.8.rst:47 msgid "" "This article explains the new features in Python 3.8, compared to 3.7. " -"Python 3.8 was released on October 14, 2019. For full details, see the :ref:" -"`changelog `." +"Python 3.8 was released on October 14, 2019. For full details, see " +"the :ref:`changelog `." msgstr "" "Bu makale, 3.7 ile karşılaştırıldığında Python 3.8 'deki yeni özellikleri " "açıklamaktadır. Tüm ayrıntılar için :ref:`changelog` 'a bakın." @@ -53,8 +53,9 @@ msgstr "Atama ifadeleri" msgid "" "There is new syntax ``:=`` that assigns values to variables as part of a " "larger expression. It is affectionately known as \"the walrus operator\" due " -"to its resemblance to `the eyes and tusks of a walrus `_." +"to its resemblance to `the eyes and tusks of a walrus `_." msgstr "" "Daha büyük bir ifadenin parçası olarak değişkenlere değerler atayan yeni " "sözdizimi ``:=`` var. Bir morsun `gözlerine ve dişlerine benzerliği " @@ -150,8 +151,8 @@ msgid "" "There is a new function parameter syntax ``/`` to indicate that some " "function parameters must be specified positionally and cannot be used as " "keyword arguments. This is the same notation shown by ``help()`` for C " -"functions annotated with Larry Hastings' `Argument Clinic `__ tool." +"functions annotated with Larry Hastings' `Argument Clinic `__ tool." msgstr "" "Bazı fonksiyon parametrelerinin konumsal olarak belirtilmesi gerektiğini ve " "anahtar kelime bağımsız değişkenleri olarak kullanılamayacağını belirtmek " @@ -308,11 +309,13 @@ msgstr "" #: whatsnew/3.8.rst:201 msgid "" -"The location of the cache is reported in :data:`sys.pycache_prefix` (:const:" -"`None` indicates the default location in ``__pycache__`` subdirectories)." +"The location of the cache is reported in :data:`sys.pycache_prefix` " +"(:const:`None` indicates the default location in ``__pycache__`` " +"subdirectories)." msgstr "" -"Önbelleğin konumu :data:`sys.pycache_prefix` içinde rapor edilir (:const:" -"`None`, ``__pycache__`` alt dizinlerindeki varsayılan konumu belirtir)." +"Önbelleğin konumu :data:`sys.pycache_prefix` içinde rapor edilir " +"(:const:`None`, ``__pycache__`` alt dizinlerindeki varsayılan konumu " +"belirtir)." #: whatsnew/3.8.rst:205 msgid "(Contributed by Carl Meyer in :issue:`33499`.)" @@ -338,18 +341,19 @@ msgid "" "Release builds and :ref:`debug builds ` are now ABI compatible: " "defining the ``Py_DEBUG`` macro no longer implies the ``Py_TRACE_REFS`` " "macro, which introduces the only ABI incompatibility. The ``Py_TRACE_REFS`` " -"macro, which adds the :func:`sys.getobjects` function and the :envvar:" -"`PYTHONDUMPREFS` environment variable, can be set using the new :option:`./" -"configure --with-trace-refs <--with-trace-refs>` build option. (Contributed " -"by Victor Stinner in :issue:`36465`.)" +"macro, which adds the :func:`sys.getobjects` function and " +"the :envvar:`PYTHONDUMPREFS` environment variable, can be set using the " +"new :option:`./configure --with-trace-refs <--with-trace-refs>` build " +"option. (Contributed by Victor Stinner in :issue:`36465`.)" msgstr "" "Release ve :ref:`hata ayıklama derlemeleri ` artık ABI ile " "uyumludur: ``Py_DEBUG`` makrosunu tanımlamak artık tek ABI uyumsuzluğunu " -"ortaya çıkaran ``Py_TRACE_REFS`` makrosunu gerektirmez. :func:`sys." -"getobjects` fonksiyonunu ve :envvar:`PYTHONDUMPREFS` ortam değişkenini " -"ekleyen ``Py_TRACE_REFS`` makrosu, yeni :option:`./configure --with-trace-" -"refs <--with-trace-refs>` derleme seçeneği kullanılarak ayarlanabilir." -"(Victor Stinner'ın' :issue:`36465` 'deki katkısıyla.)" +"ortaya çıkaran ``Py_TRACE_REFS`` makrosunu " +"gerektirmez. :func:`sys.getobjects` fonksiyonunu ve :envvar:`PYTHONDUMPREFS` " +"ortam değişkenini ekleyen ``Py_TRACE_REFS`` makrosu, yeni :option:`./" +"configure --with-trace-refs <--with-trace-refs>` derleme seçeneği " +"kullanılarak ayarlanabilir.(Victor Stinner'ın' :issue:`36465` 'deki " +"katkısıyla.)" #: whatsnew/3.8.rst:223 msgid "" @@ -409,8 +413,8 @@ msgid "" "On the other hand, ``pkg-config python3.8 --libs`` no longer contains ``-" "lpython3.8``. C extensions must not be linked to libpython (except on " "Android and Cygwin, whose cases are handled by the script); this change is " -"backward incompatible on purpose. (Contributed by Victor Stinner in :issue:" -"`36721`.)" +"backward incompatible on purpose. (Contributed by Victor Stinner " +"in :issue:`36721`.)" msgstr "" "Öte yandan, ``pkg-config python3.8 --libs`` artık ``-lpython3.8`` içermiyor. " "C uzantıları libpython'a bağlanmamalıdır (durumları dize tarafından işlenen " @@ -638,11 +642,11 @@ msgid "" "reference configuration, replacing global configuration variables and other " "private variables." msgstr "" -"Bu PEP ayrıca bu iç yapılara ``_PyRuntimeState.preconfig`` (:c:type:" -"`PyPreConfig` type) ve ``PyInterpreterState.config`` (:c:type:`PyConfig` " -"type) alanlarını ekler. ``PyInterpreterState.config``, global yapılandırma " -"değişkenlerinin ve diğer özel değişkenlerin yerini alarak yeni referans " -"yapılandırması haline gelir." +"Bu PEP ayrıca bu iç yapılara ``_PyRuntimeState.preconfig`` " +"(:c:type:`PyPreConfig` type) ve ``PyInterpreterState.config`` " +"(:c:type:`PyConfig` type) alanlarını ekler. ``PyInterpreterState.config``, " +"global yapılandırma değişkenlerinin ve diğer özel değişkenlerin yerini " +"alarak yeni referans yapılandırması haline gelir." #: whatsnew/3.8.rst:343 msgid "" @@ -667,8 +671,9 @@ msgstr "PEP 590: Vectorcall: CPython için hızlı arama protokolü" #: whatsnew/3.8.rst:354 msgid "" ":ref:`vectorcall` is added to the Python/C API. It is meant to formalize " -"existing optimizations which were already done for various classes. Any :ref:" -"`static type ` implementing a callable can use this protocol." +"existing optimizations which were already done for various classes. " +"Any :ref:`static type ` implementing a callable can use this " +"protocol." msgstr "" "Python/C API'sine :ref:`vectorcall` eklendi. Çeşitli sınıflar için zaten " "yapılmış olan mevcut optimizasyonları resmileştirmeyi amaçlamaktadır. Bir " @@ -689,11 +694,11 @@ msgstr "Tam açıklama için :pep:`590` 'a bakın." #: whatsnew/3.8.rst:365 msgid "" -"(Contributed by Jeroen Demeyer, Mark Shannon and Petr Viktorin in :issue:" -"`36974`.)" +"(Contributed by Jeroen Demeyer, Mark Shannon and Petr Viktorin " +"in :issue:`36974`.)" msgstr "" -"(Jeroen Demeyer, Mark Shannon ve Petr Viktorin'in katkılarıyla :issue:" -"`36974`.)" +"(Jeroen Demeyer, Mark Shannon ve Petr Viktorin'in " +"katkılarıyla :issue:`36974`.)" #: whatsnew/3.8.rst:369 msgid "Pickle protocol 5 with out-of-band data buffers" @@ -739,38 +744,38 @@ msgid "" "due to a problem with the implementation. In Python 3.8 this restriction " "was lifted. (Contributed by Serhiy Storchaka in :issue:`32489`.)" msgstr "" -"Bir :keyword:`continue` ifadesi, uygulamadaki bir sorun nedeniyle :keyword:" -"`finally` cümlesinde yasadışı idi. Python 3.8'de bu kısıtlama kaldırıldı. " -"(Serhiy Storchaka'nın :issue:`32489` 'daki katkısıyla.)" +"Bir :keyword:`continue` ifadesi, uygulamadaki bir sorun " +"nedeniyle :keyword:`finally` cümlesinde yasadışı idi. Python 3.8'de bu " +"kısıtlama kaldırıldı. (Serhiy Storchaka'nın :issue:`32489` 'daki katkısıyla.)" #: whatsnew/3.8.rst:393 msgid "" "The :class:`bool`, :class:`int`, and :class:`fractions.Fraction` types now " -"have an :meth:`~int.as_integer_ratio` method like that found in :class:" -"`float` and :class:`decimal.Decimal`. This minor API extension makes it " -"possible to write ``numerator, denominator = x.as_integer_ratio()`` and have " -"it work across multiple numeric types. (Contributed by Lisa Roach in :issue:" -"`33073` and Raymond Hettinger in :issue:`37819`.)" -msgstr "" -":class:`bool`, :class:`int` ve :class:`fractions.Fraction` türleri artık :" -"class:`float` ve :class:`decimal.Decimal` türlerinde olduğu gibi bir :meth:" -"`~int.as_integer_ratio` yöntemine sahiptir. Bu küçük API uzantısı " +"have an :meth:`~int.as_integer_ratio` method like that found " +"in :class:`float` and :class:`decimal.Decimal`. This minor API extension " +"makes it possible to write ``numerator, denominator = x.as_integer_ratio()`` " +"and have it work across multiple numeric types. (Contributed by Lisa Roach " +"in :issue:`33073` and Raymond Hettinger in :issue:`37819`.)" +msgstr "" +":class:`bool`, :class:`int` ve :class:`fractions.Fraction` türleri " +"artık :class:`float` ve :class:`decimal.Decimal` türlerinde olduğu gibi " +"bir :meth:`~int.as_integer_ratio` yöntemine sahiptir. Bu küçük API uzantısı " "``numerator, denominator = x.as_integer_ratio()`` yazmayı ve bunun birden " -"fazla sayısal türde çalışmasını mümkün kılmaktadır. (Lisa Roach tarafından :" -"issue:`33073` ve Raymond Hettinger tarafından :issue:`37819` ile katkıda " -"bulunulmuştur)" +"fazla sayısal türde çalışmasını mümkün kılmaktadır. (Lisa Roach " +"tarafından :issue:`33073` ve Raymond Hettinger tarafından :issue:`37819` ile " +"katkıda bulunulmuştur)" #: whatsnew/3.8.rst:401 msgid "" "Constructors of :class:`int`, :class:`float` and :class:`complex` will now " "use the :meth:`~object.__index__` special method, if available and the " -"corresponding method :meth:`~object.__int__`, :meth:`~object.__float__` or :" -"meth:`~object.__complex__` is not available. (Contributed by Serhiy " +"corresponding method :meth:`~object.__int__`, :meth:`~object.__float__` " +"or :meth:`~object.__complex__` is not available. (Contributed by Serhiy " "Storchaka in :issue:`20092`.)" msgstr "" -":class:`int`, :class:`float` ve :class:`complex` kurucuları artık :meth:" -"`~object.__index__` özel yöntemini kullanacak, eğer mevcutsa ve ilgili " -"yöntem :meth:`~object.__int__`, :meth:`~object.__float__` veya mevcut " +":class:`int`, :class:`float` ve :class:`complex` kurucuları " +"artık :meth:`~object.__index__` özel yöntemini kullanacak, eğer mevcutsa ve " +"ilgili yöntem :meth:`~object.__int__`, :meth:`~object.__float__` veya mevcut " "değilse :meth:`~object.__complex__` . (Serhiy Storchaka'nın :issue:`20092` " "'deki katkısıyla.)" @@ -799,8 +804,8 @@ msgstr "" #: whatsnew/3.8.rst:416 msgid "" -"Dict and dictviews are now iterable in reversed insertion order using :func:" -"`reversed`. (Contributed by Rémi Lapeyre in :issue:`33462`.)" +"Dict and dictviews are now iterable in reversed insertion order " +"using :func:`reversed`. (Contributed by Rémi Lapeyre in :issue:`33462`.)" msgstr "" "Dict ve dictviews artık :func:`reversed` kullanılarak tersine çevrilmiş " "ekleme sırasına göre yinelenebilir. (Rémi Lapeyre'nin :issue:`33462` 'deki " @@ -811,8 +816,8 @@ msgid "" "The syntax allowed for keyword names in function calls was further " "restricted. In particular, ``f((keyword)=arg)`` is no longer allowed. It was " "never intended to permit more than a bare name on the left-hand side of a " -"keyword argument assignment term. (Contributed by Benjamin Peterson in :" -"issue:`34641`.)" +"keyword argument assignment term. (Contributed by Benjamin Peterson " +"in :issue:`34641`.)" msgstr "" "Fonksiyon çağrılarında anahtar kelime isimleri için izin verilen sözdizimi " "daha da kısıtlandı. Özellikle, ``f((keyword)=arg)`` ifadesine artık izin " @@ -860,20 +865,21 @@ msgstr "" #: whatsnew/3.8.rst:445 msgid "" -"Arithmetic operations between subclasses of :class:`datetime.date` or :class:" -"`datetime.datetime` and :class:`datetime.timedelta` objects now return an " -"instance of the subclass, rather than the base class. This also affects the " -"return type of operations whose implementation (directly or indirectly) " -"uses :class:`datetime.timedelta` arithmetic, such as :meth:`~datetime." -"datetime.astimezone`. (Contributed by Paul Ganssle in :issue:`32417`.)" -msgstr "" -":class:`datetime.date` veya :class:`datetime.datetime` ve :class:`datetime." -"timedelta` nesnelerinin alt sınıfları arasındaki aritmetik işlemler artık " -"temel sınıf yerine alt sınıfın bir örneğini döndürmektedir. Bu, :meth:" -"`~datetime.datetime.astimezone` gibi uygulaması (doğrudan veya dolaylı " -"olarak) :class:`datetime.timedelta` aritmetiğini kullanan işlemlerin dönüş " -"türünü de etkiler. (Paul Ganssle tarafından :issue:`32417` ile katkıda " -"bulunulmuştur)" +"Arithmetic operations between subclasses of :class:`datetime.date` " +"or :class:`datetime.datetime` and :class:`datetime.timedelta` objects now " +"return an instance of the subclass, rather than the base class. This also " +"affects the return type of operations whose implementation (directly or " +"indirectly) uses :class:`datetime.timedelta` arithmetic, such " +"as :meth:`~datetime.datetime.astimezone`. (Contributed by Paul Ganssle " +"in :issue:`32417`.)" +msgstr "" +":class:`datetime.date` veya :class:`datetime.datetime` " +"ve :class:`datetime.timedelta` nesnelerinin alt sınıfları arasındaki " +"aritmetik işlemler artık temel sınıf yerine alt sınıfın bir örneğini " +"döndürmektedir. Bu, :meth:`~datetime.datetime.astimezone` gibi uygulaması " +"(doğrudan veya dolaylı olarak) :class:`datetime.timedelta` aritmetiğini " +"kullanan işlemlerin dönüş türünü de etkiler. (Paul Ganssle " +"tarafından :issue:`32417` ile katkıda bulunulmuştur)" #: whatsnew/3.8.rst:453 msgid "" @@ -894,18 +900,18 @@ msgstr "" #: whatsnew/3.8.rst:460 msgid "" -"Some advanced styles of programming require updating the :class:`types." -"CodeType` object for an existing function. Since code objects are " -"immutable, a new code object needs to be created, one that is modeled on the " -"existing code object. With 19 parameters, this was somewhat tedious. Now, " -"the new ``replace()`` method makes it possible to create a clone with a few " -"altered parameters." -msgstr "" -"Bazı gelişmiş programlama stilleri, mevcut bir fonksiyon için :class:`types." -"CodeType` nesnesinin güncellenmesini gerektirir. Kod nesneleri değişmez " -"olduğundan, mevcut kod nesnesini model alan yeni bir kod nesnesi " -"oluşturulması gerekir. 19 parametre ile bu biraz sıkıcıydı. Şimdi, yeni " -"``replace()`` yöntemi, birkaç değiştirilmiş parametre ile bir klon " +"Some advanced styles of programming require updating " +"the :class:`types.CodeType` object for an existing function. Since code " +"objects are immutable, a new code object needs to be created, one that is " +"modeled on the existing code object. With 19 parameters, this was somewhat " +"tedious. Now, the new ``replace()`` method makes it possible to create a " +"clone with a few altered parameters." +msgstr "" +"Bazı gelişmiş programlama stilleri, mevcut bir fonksiyon " +"için :class:`types.CodeType` nesnesinin güncellenmesini gerektirir. Kod " +"nesneleri değişmez olduğundan, mevcut kod nesnesini model alan yeni bir kod " +"nesnesi oluşturulması gerekir. 19 parametre ile bu biraz sıkıcıydı. Şimdi, " +"yeni ``replace()`` yöntemi, birkaç değiştirilmiş parametre ile bir klon " "oluşturmayı mümkün kılıyor." #: whatsnew/3.8.rst:467 @@ -965,10 +971,10 @@ msgid "" "integer solutions for ``4258𝑥 + 147𝑦 = 369``, first rewrite as ``4258𝑥 ≡ 369 " "(mod 147)`` then solve:" msgstr "" -"Modüler tersler, `lineer Diophantine denklemlerinin `_ çözümünde ortaya çıkar. Örneğin, ``4258𝑥 + " -"147𝑦 = 369`` tamsayı çözümlerini bulmak için, önce ``4258𝑥 ≡ 369 (mod 147)`` " -"olarak yeniden yazın ve sonra çözün:" +"Modüler tersler, `lineer Diophantine denklemlerinin `_ çözümünde ortaya çıkar. " +"Örneğin, ``4258𝑥 + 147𝑦 = 369`` tamsayı çözümlerini bulmak için, önce " +"``4258𝑥 ≡ 369 (mod 147)`` olarak yeniden yazın ve sonra çözün:" #: whatsnew/3.8.rst:505 msgid "(Contributed by Mark Dickinson in :issue:`36027`.)" @@ -1025,17 +1031,17 @@ msgid "" "elements long. Formerly, five was the limit. The new, optional sixth " "element is a callable with a ``(obj, state)`` signature. This allows the " "direct control over the state-updating behavior of a specific object. If " -"not *None*, this callable will have priority over the object's :meth:" -"`~__setstate__` method. (Contributed by Pierre Glaser and Olivier Grisel in :" -"issue:`35900`.)" +"not *None*, this callable will have priority over the " +"object's :meth:`~__setstate__` method. (Contributed by Pierre Glaser and " +"Olivier Grisel in :issue:`35900`.)" msgstr "" ":meth:`object.__reduce__` yöntemi artık iki ila altı eleman uzunluğunda bir " "tuple döndürebilir. Eskiden sınır beşti. Yeni, isteğe bağlı altıncı eleman " "``(obj, state)`` imzasına sahip bir çağrılabilirdir. Bu, belirli bir " "nesnenin durum güncelleme davranışı üzerinde doğrudan kontrol sağlar. Eğer " "*None* değilse, bu çağrılabilir öğe nesnenin :meth:`~__setstate__` yöntemine " -"göre önceliğe sahip olacaktır. (Pierre Glaser ve Olivier Grisel'in :issue:" -"`35900` 'deki katkılarıyla.)" +"göre önceliğe sahip olacaktır. (Pierre Glaser ve Olivier " +"Grisel'in :issue:`35900` 'deki katkılarıyla.)" #: whatsnew/3.8.rst:543 msgid "New Modules" @@ -1111,11 +1117,11 @@ msgstr ":func:`ast.parse` fonksiyonu bazı yeni bayraklara sahiptir:" #: whatsnew/3.8.rst:584 msgid "" -"``type_comments=True`` causes it to return the text of :pep:`484` and :pep:" -"`526` type comments associated with certain AST nodes;" +"``type_comments=True`` causes it to return the text of :pep:`484` " +"and :pep:`526` type comments associated with certain AST nodes;" msgstr "" -"``type_comments=True`` , belirli AST düğümleriyle ilişkili :pep:`484` ve :" -"pep:`526` tipi yorumların metnini döndürmesine neden olur;" +"``type_comments=True`` , belirli AST düğümleriyle ilişkili :pep:`484` " +"ve :pep:`526` tipi yorumların metnini döndürmesine neden olur;" #: whatsnew/3.8.rst:587 msgid "" @@ -1128,12 +1134,13 @@ msgstr "" #: whatsnew/3.8.rst:590 msgid "" "``feature_version=(3, N)`` allows specifying an earlier Python 3 version. " -"For example, ``feature_version=(3, 4)`` will treat :keyword:`async` and :" -"keyword:`await` as non-reserved words." +"For example, ``feature_version=(3, 4)`` will treat :keyword:`async` " +"and :keyword:`await` as non-reserved words." msgstr "" "``feature_version=(3, N)`` daha önceki bir Python 3 sürümünü belirtmeye izin " -"verir. Örneğin, ``feature_version=(3, 4)``, :keyword:`async` ve :keyword:" -"`await` sözcüklerini rezerve edilmemiş sözcükler olarak ele alacaktır." +"verir. Örneğin, ``feature_version=(3, 4)``, :keyword:`async` " +"ve :keyword:`await` sözcüklerini rezerve edilmemiş sözcükler olarak ele " +"alacaktır." #: whatsnew/3.8.rst:594 msgid "(Contributed by Guido van Rossum in :issue:`35766`.)" @@ -1187,11 +1194,13 @@ msgstr "" #: whatsnew/3.8.rst:629 msgid "" -"The actual implementation is significantly more complex. Thus, :func:" -"`asyncio.run` should be the preferred way of running asyncio programs." +"The actual implementation is significantly more complex. " +"Thus, :func:`asyncio.run` should be the preferred way of running asyncio " +"programs." msgstr "" -"Gerçek uygulama önemli ölçüde daha karmaşıktır. Bu nedenle, :func:`asyncio." -"run` asyncio programlarını çalıştırmak için tercih edilen yol olmalıdır." +"Gerçek uygulama önemli ölçüde daha karmaşıktır. Bu " +"nedenle, :func:`asyncio.run` asyncio programlarını çalıştırmak için tercih " +"edilen yol olmalıdır." #: whatsnew/3.8.rst:632 msgid "(Contributed by Yury Selivanov in :issue:`32314`.)" @@ -1206,8 +1215,8 @@ msgid "" msgstr "" "``python -m asyncio`` çalıştırıldığında yerel bir async REPL başlatılır. " "Bu, üst düzey bir :keyword:`await` içeren kodla hızlı denemeler yapılmasına " -"olanak tanır. Artık her çağrıda yeni bir olay döngüsü oluşturacak ``asyncio." -"run()`` fonksiyonunu doğrudan çağırmaya gerek yoktur:" +"olanak tanır. Artık her çağrıda yeni bir olay döngüsü oluşturacak " +"``asyncio.run()`` fonksiyonunu doğrudan çağırmaya gerek yoktur:" #: whatsnew/3.8.rst:639 msgid "" @@ -1227,24 +1236,25 @@ msgstr "(Yury Selivanov'un :issue:`37028` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1970 msgid "" -"The exception :class:`asyncio.CancelledError` now inherits from :class:" -"`BaseException` rather than :class:`Exception` and no longer inherits from :" -"class:`concurrent.futures.CancelledError`. (Contributed by Yury Selivanov " -"in :issue:`32528`.)" +"The exception :class:`asyncio.CancelledError` now inherits " +"from :class:`BaseException` rather than :class:`Exception` and no longer " +"inherits from :class:`concurrent.futures.CancelledError`. (Contributed by " +"Yury Selivanov in :issue:`32528`.)" msgstr "" -"İstisna :class:`asyncio.CancelledError` artık :class:`Exception` yerine :" -"class:`BaseException` 'dan miras alıyor ve artık :class:`concurrent.futures." -"CancelledError` 'dan miras almıyor. (Yury Selivanov'un :issue:`32528` 'deki " -"katkısıyla.)" +"İstisna :class:`asyncio.CancelledError` artık :class:`Exception` " +"yerine :class:`BaseException` 'dan miras alıyor ve " +"artık :class:`concurrent.futures.CancelledError` 'dan miras almıyor. (Yury " +"Selivanov'un :issue:`32528` 'deki katkısıyla.)" #: whatsnew/3.8.rst:656 msgid "" -"On Windows, the default event loop is now :class:`~asyncio." -"ProactorEventLoop`. (Contributed by Victor Stinner in :issue:`34687`.)" +"On Windows, the default event loop is " +"now :class:`~asyncio.ProactorEventLoop`. (Contributed by Victor Stinner " +"in :issue:`34687`.)" msgstr "" -"Windows'ta, varsayılan olay döngüsü artık :class:`~asyncio." -"ProactorEventLoop` şeklindedir. (Victor Stinner'ın :issue:`34687` 'deki " -"katkısıyla.)" +"Windows'ta, varsayılan olay döngüsü " +"artık :class:`~asyncio.ProactorEventLoop` şeklindedir. (Victor " +"Stinner'ın :issue:`34687` 'deki katkısıyla.)" #: whatsnew/3.8.rst:659 msgid "" @@ -1256,9 +1266,9 @@ msgstr "" #: whatsnew/3.8.rst:662 msgid "" -":class:`~asyncio.ProactorEventLoop` can now be interrupted by :exc:" -"`KeyboardInterrupt` (\"CTRL+C\"). (Contributed by Vladimir Matveev in :issue:" -"`23057`.)" +":class:`~asyncio.ProactorEventLoop` can now be interrupted " +"by :exc:`KeyboardInterrupt` (\"CTRL+C\"). (Contributed by Vladimir Matveev " +"in :issue:`23057`.)" msgstr "" ":class:`~asyncio.ProactorEventLoop` artık :exc:`KeyboardInterrupt` " "(\"CTRL+C\") ile kesilebilir. (Vladimir Matveev'in :issue:`23057` 'deki " @@ -1269,27 +1279,27 @@ msgid "" "Added :meth:`asyncio.Task.get_coro` for getting the wrapped coroutine within " "an :class:`asyncio.Task`. (Contributed by Alex Grönholm in :issue:`36999`.)" msgstr "" -"Bir :class:`asyncio.Task` içindeki sarılmış korutini almak için :meth:" -"`asyncio.Task.get_coro` eklendi. (Alex Grönholm'ın :issue:`36999` 'daki " -"katkısıyla.)" +"Bir :class:`asyncio.Task` içindeki sarılmış korutini almak " +"için :meth:`asyncio.Task.get_coro` eklendi. (Alex Grönholm'ın :issue:`36999` " +"'daki katkısıyla.)" #: whatsnew/3.8.rst:670 msgid "" "Asyncio tasks can now be named, either by passing the ``name`` keyword " -"argument to :func:`asyncio.create_task` or the :meth:`~asyncio.loop." -"create_task` event loop method, or by calling the :meth:`~asyncio.Task." -"set_name` method on the task object. The task name is visible in the " -"``repr()`` output of :class:`asyncio.Task` and can also be retrieved using " -"the :meth:`~asyncio.Task.get_name` method. (Contributed by Alex Grönholm in :" -"issue:`34270`.)" -msgstr "" -"Asyncio görevleri artık :func:`asyncio.create_task` veya :meth:`~asyncio." -"loop.create_task` olay döngüsü yöntemine ``name`` anahtar sözcük argümanı " -"geçirilerek ya da görev nesnesi üzerinde :meth:`~asyncio.Task.set_name` " -"yöntemi çağrılarak adlandırılabilir. Görev adı :class:`asyncio.Task` " -"metodunun ``repr()`` çıktısında görülebilir ve :meth:`~asyncio.Task." -"get_name` metodu kullanılarak da alınabilir. (Alex Grönholm'ın :issue:" -"`34270` 'teki katkısıyla.)" +"argument to :func:`asyncio.create_task` or " +"the :meth:`~asyncio.loop.create_task` event loop method, or by calling " +"the :meth:`~asyncio.Task.set_name` method on the task object. The task name " +"is visible in the ``repr()`` output of :class:`asyncio.Task` and can also be " +"retrieved using the :meth:`~asyncio.Task.get_name` method. (Contributed by " +"Alex Grönholm in :issue:`34270`.)" +msgstr "" +"Asyncio görevleri artık :func:`asyncio.create_task` " +"veya :meth:`~asyncio.loop.create_task` olay döngüsü yöntemine ``name`` " +"anahtar sözcük argümanı geçirilerek ya da görev nesnesi " +"üzerinde :meth:`~asyncio.Task.set_name` yöntemi çağrılarak adlandırılabilir. " +"Görev adı :class:`asyncio.Task` metodunun ``repr()`` çıktısında görülebilir " +"ve :meth:`~asyncio.Task.get_name` metodu kullanılarak da alınabilir. (Alex " +"Grönholm'ın :issue:`34270` 'teki katkısıyla.)" #: whatsnew/3.8.rst:678 msgid "" @@ -1300,8 +1310,8 @@ msgid "" "applications that support IPv4 and IPv6 by attempting to simultaneously " "connect using both. (Contributed by twisteroid ambassador in :issue:`33530`.)" msgstr "" -":func:`asyncio.loop.create_connection` 'a `Happy Eyeballs `_ desteği eklendi. Davranışı belirtmek " +":func:`asyncio.loop.create_connection` 'a `Happy Eyeballs `_ desteği eklendi. Davranışı belirtmek " "için iki yeni parametre eklendi: *happy_eyeballs_delay* ve *interleave*. " "Happy Eyeballs algoritması, IPv4 ve IPv6'yı destekleyen uygulamalarda, her " "ikisini de kullanarak aynı anda bağlanmaya çalışarak yanıt verebilirliği " @@ -1313,19 +1323,20 @@ msgstr "builtins" #: whatsnew/3.8.rst:690 msgid "" -"The :func:`compile` built-in has been improved to accept the ``ast." -"PyCF_ALLOW_TOP_LEVEL_AWAIT`` flag. With this new flag passed, :func:" -"`compile` will allow top-level ``await``, ``async for`` and ``async with`` " -"constructs that are usually considered invalid syntax. Asynchronous code " -"object marked with the ``CO_COROUTINE`` flag may then be returned. " -"(Contributed by Matthias Bussonnier in :issue:`34616`)" +"The :func:`compile` built-in has been improved to accept the " +"``ast.PyCF_ALLOW_TOP_LEVEL_AWAIT`` flag. With this new flag " +"passed, :func:`compile` will allow top-level ``await``, ``async for`` and " +"``async with`` constructs that are usually considered invalid syntax. " +"Asynchronous code object marked with the ``CO_COROUTINE`` flag may then be " +"returned. (Contributed by Matthias Bussonnier in :issue:`34616`)" msgstr "" ":func:`compile` yerleşik yapısı ``ast.PyCF_ALLOW_TOP_LEVEL_AWAIT`` bayrağını " -"kabul edecek şekilde geliştirilmiştir. Bu yeni bayrak geçildiğinde, :func:" -"`compile` genellikle geçersiz sözdizimi olarak kabul edilen üst düzey " -"``await``, ``async for`` ve ``async with`` yapılarına izin verecektir. Daha " -"sonra ``CO_COROUTINE`` bayrağı ile işaretlenmiş asenkron kod nesnesi " -"döndürülebilir. (Matthias Bussonnier'ın :issue:`34616` 'daki katkısıyla.)" +"kabul edecek şekilde geliştirilmiştir. Bu yeni bayrak " +"geçildiğinde, :func:`compile` genellikle geçersiz sözdizimi olarak kabul " +"edilen üst düzey ``await``, ``async for`` ve ``async with`` yapılarına izin " +"verecektir. Daha sonra ``CO_COROUTINE`` bayrağı ile işaretlenmiş asenkron " +"kod nesnesi döndürülebilir. (Matthias Bussonnier'ın :issue:`34616` 'daki " +"katkısıyla.)" #: whatsnew/3.8.rst:699 msgid "collections" @@ -1333,19 +1344,20 @@ msgstr "collections" #: whatsnew/3.8.rst:701 msgid "" -"The :meth:`~collections.somenamedtuple._asdict` method for :func:" -"`collections.namedtuple` now returns a :class:`dict` instead of a :class:" -"`collections.OrderedDict`. This works because regular dicts have guaranteed " -"ordering since Python 3.7. If the extra features of :class:`OrderedDict` are " -"required, the suggested remediation is to cast the result to the desired " -"type: ``OrderedDict(nt._asdict())``. (Contributed by Raymond Hettinger in :" -"issue:`35864`.)" -msgstr "" -":func:`collections.namedtuple` için :meth:`~collections.somenamedtuple." -"_asdict` yöntemi artık :class:`collections.OrderedDict` yerine bir :class:" -"`dict` döndürüyor. Bu işe yarıyor çünkü normal dictler Python 3.7'den beri " -"garantili sıralamaya sahip. Eğer :class:`OrderedDict` 'in ekstra özellikleri " -"gerekiyorsa, önerilen çözüm sonucu istenen türe dönüştürmektir: " +"The :meth:`~collections.somenamedtuple._asdict` method " +"for :func:`collections.namedtuple` now returns a :class:`dict` instead of " +"a :class:`collections.OrderedDict`. This works because regular dicts have " +"guaranteed ordering since Python 3.7. If the extra features " +"of :class:`OrderedDict` are required, the suggested remediation is to cast " +"the result to the desired type: ``OrderedDict(nt._asdict())``. (Contributed " +"by Raymond Hettinger in :issue:`35864`.)" +msgstr "" +":func:`collections.namedtuple` " +"için :meth:`~collections.somenamedtuple._asdict` yöntemi " +"artık :class:`collections.OrderedDict` yerine bir :class:`dict` döndürüyor. " +"Bu işe yarıyor çünkü normal dictler Python 3.7'den beri garantili sıralamaya " +"sahip. Eğer :class:`OrderedDict` 'in ekstra özellikleri gerekiyorsa, " +"önerilen çözüm sonucu istenen türe dönüştürmektir: " "``OrderedDict(nt._asdict())``. (Raymond Hettinger'ın :issue:`35864` 'teki " "katkısıyla.)" @@ -1386,10 +1398,10 @@ msgid "" "memory while still preserving the field order. (Contributed by Michael Selik " "in :issue:`34003`.)" msgstr "" -":class:`csv.DictReader` artık :class:`collections.OrderedDict` yerine :class:" -"`dict` örneklerini döndürüyor. Araç artık daha hızlı ve alan sırasını " -"korurken daha az bellek kullanıyor. (Michael Selik' in :issue:`34003` 'teki " -"katkısıyla.)" +":class:`csv.DictReader` artık :class:`collections.OrderedDict` " +"yerine :class:`dict` örneklerini döndürüyor. Araç artık daha hızlı ve alan " +"sırasını korurken daha az bellek kullanıyor. (Michael Selik' " +"in :issue:`34003` 'teki katkısıyla.)" #: whatsnew/3.8.rst:735 msgid "curses" @@ -1415,16 +1427,17 @@ msgid "" "parameter to specify flags for the underlying ``LoadLibraryEx`` call. The " "default flags are set to only load DLL dependencies from trusted locations, " "including the path where the DLL is stored (if a full or partial path is " -"used to load the initial DLL) and paths added by :func:`~os." -"add_dll_directory`. (Contributed by Steve Dower in :issue:`36085`.)" +"used to load the initial DLL) and paths added " +"by :func:`~os.add_dll_directory`. (Contributed by Steve Dower " +"in :issue:`36085`.)" msgstr "" "Windows üzerinde, :class:`~ctypes.CDLL` ve alt sınıfları artık temel " "``LoadLibraryEx`` çağrısı için bayrakları belirtmek üzere bir *winmode* " "parametresi kabul etmektedir. Varsayılan bayraklar, DLL'nin depolandığı yol " -"(ilk DLL'yi yüklemek için tam veya kısmi bir yol kullanılmışsa) ve :func:" -"`~os.add_dll_directory` tarafından eklenen yollar dahil olmak üzere, " -"yalnızca güvenilir konumlardan DLL bağımlılıklarını yükleyecek şekilde " -"ayarlanmıştır. (Steve Dower'ın :issue:`36085` 'teki katkısıyla.)" +"(ilk DLL'yi yüklemek için tam veya kısmi bir yol kullanılmışsa) " +"ve :func:`~os.add_dll_directory` tarafından eklenen yollar dahil olmak " +"üzere, yalnızca güvenilir konumlardan DLL bağımlılıklarını yükleyecek " +"şekilde ayarlanmıştır. (Steve Dower'ın :issue:`36085` 'teki katkısıyla.)" #: whatsnew/3.8.rst:754 msgid "datetime" @@ -1433,17 +1446,19 @@ msgstr "datetime" #: whatsnew/3.8.rst:756 #, fuzzy msgid "" -"Added new alternate constructors :meth:`datetime.date.fromisocalendar` and :" -"meth:`datetime.datetime.fromisocalendar`, which construct :class:`~datetime." -"date` and :class:`~datetime.datetime` objects respectively from ISO year, " -"week number, and weekday; these are the inverse of each class's " -"``isocalendar`` method. (Contributed by Paul Ganssle in :issue:`36004`.)" -msgstr "" -"ISO yılı, hafta numarası ve haftanın gününden sırasıyla :class:`date` ve :" -"class:`datetime` nesnelerini oluşturan yeni alternatif kurucular :meth:" -"`datetime.date.fromisocalendar` ve :meth:`datetime.datetime.fromisocalendar` " -"eklendi; bunlar her sınıfın ``isocalendar`` yönteminin tersidir. (Paul " -"Ganssle'ın :issue:`36004` 'teki katkısıyla.)" +"Added new alternate constructors :meth:`datetime.date.fromisocalendar` " +"and :meth:`datetime.datetime.fromisocalendar`, which " +"construct :class:`~datetime.date` and :class:`~datetime.datetime` objects " +"respectively from ISO year, week number, and weekday; these are the inverse " +"of each class's ``isocalendar`` method. (Contributed by Paul Ganssle " +"in :issue:`36004`.)" +msgstr "" +"ISO yılı, hafta numarası ve haftanın gününden sırasıyla :class:`date` " +"ve :class:`datetime` nesnelerini oluşturan yeni alternatif " +"kurucular :meth:`datetime.date.fromisocalendar` " +"ve :meth:`datetime.datetime.fromisocalendar` eklendi; bunlar her sınıfın " +"``isocalendar`` yönteminin tersidir. (Paul Ganssle'ın :issue:`36004` 'teki " +"katkısıyla.)" #: whatsnew/3.8.rst:764 msgid "functools" @@ -1479,8 +1494,8 @@ msgid "" "Added a new :func:`functools.cached_property` decorator, for computed " "properties cached for the life of the instance. ::" msgstr "" -"Örneğin ömrü boyunca önbelleğe alınan hesaplanmış özellikler için yeni bir :" -"func:`functools.cached_property` dekoratörü eklendi:" +"Örneğin ömrü boyunca önbelleğe alınan hesaplanmış özellikler için yeni " +"bir :func:`functools.cached_property` dekoratörü eklendi:" #: whatsnew/3.8.rst:782 msgid "" @@ -1503,12 +1518,12 @@ msgstr "(Carl Meyer'ın :issue:`21145` 'teki katkısıyla.)" #: whatsnew/3.8.rst:796 msgid "" "Added a new :func:`functools.singledispatchmethod` decorator that converts " -"methods into :term:`generic functions ` using :term:" -"`single dispatch`::" +"methods into :term:`generic functions ` " +"using :term:`single dispatch`::" msgstr "" "Metotları :term:`single dispatch` kullanarak :term:`generic functions " -"` haline dönüştüren yeni bir :func:`functools." -"singledispatchmethod` dekoratörü eklendi::" +"` haline dönüştüren yeni " +"bir :func:`functools.singledispatchmethod` dekoratörü eklendi::" #: whatsnew/3.8.rst:800 msgid "" @@ -1626,8 +1641,8 @@ msgid "" "Added optional line numbers for IDLE editor windows. Windows open without " "line numbers unless set otherwise in the General tab of the configuration " "dialog. Line numbers for an existing window are shown and hidden in the " -"Options menu. (Contributed by Tal Einat and Saimadhav Heblikar in :issue:" -"`17535`.)" +"Options menu. (Contributed by Tal Einat and Saimadhav Heblikar " +"in :issue:`17535`.)" msgstr "" "IDLE düzenleyici pencereleri için isteğe bağlı satır numaraları eklendi. " "Yapılandırma iletişim kutusunun Genel sekmesinde aksi ayarlanmadığı sürece " @@ -1658,11 +1673,11 @@ msgstr "3.8.1'deki yenilikler:" #: whatsnew/3.8.rst:878 msgid "" -"Add option to toggle cursor blink off. (Contributed by Zackery Spytz in :" -"issue:`4603`.)" +"Add option to toggle cursor blink off. (Contributed by Zackery Spytz " +"in :issue:`4603`.)" msgstr "" -"İmleç yanıp sönmesini kapatmak için seçenek ekleyin. (Zackery Spytz'in :" -"issue:`4603` 'teki katkısıyla.)" +"İmleç yanıp sönmesini kapatmak için seçenek ekleyin. (Zackery " +"Spytz'in :issue:`4603` 'teki katkısıyla.)" #: whatsnew/3.8.rst:881 msgid "" @@ -1803,8 +1818,8 @@ msgid "" "(Suggested by Raymond Hettinger, implemented by Donghee Na, and reviewed by " "Vinay Sajip in :issue:`33897`.)" msgstr "" -"(Raymond Hettinger tarafından önerildi, Dong-hee Na tarafından uygulandı ve :" -"issue:`33897` 'de Vinay Sajip tarafından gözden geçirildi.)" +"(Raymond Hettinger tarafından önerildi, Dong-hee Na tarafından uygulandı " +"ve :issue:`33897` 'de Vinay Sajip tarafından gözden geçirildi.)" #: whatsnew/3.8.rst:955 msgid "math" @@ -1852,11 +1867,11 @@ msgstr "(Pablo Galindo'nun :issue:`35606` 'daki katkısıyla.)" #: whatsnew/3.8.rst:975 msgid "" -"Added two new combinatoric functions :func:`math.perm` and :func:`math." -"comb`::" +"Added two new combinatoric functions :func:`math.perm` " +"and :func:`math.comb`::" msgstr "" -"İki yeni kombinatorik fonksiyon eklendi :func:`math.perm` ve :func:`math." -"comb`::" +"İki yeni kombinatorik fonksiyon eklendi :func:`math.perm` " +"ve :func:`math.comb`::" #: whatsnew/3.8.rst:977 msgid "" @@ -1871,8 +1886,9 @@ msgid "" "(Contributed by Yash Aggarwal, Keller Fuchs, Serhiy Storchaka, and Raymond " "Hettinger in :issue:`37128`, :issue:`37178`, and :issue:`35431`.)" msgstr "" -"(Yash Aggarwal, Keller Fuchs, Serhiy Storchaka ve Raymond Hettinger'ın :" -"issue:`37128`, :issue:`37178` ve :issue:`35431` 'deki katkılarıyla.)" +"(Yash Aggarwal, Keller Fuchs, Serhiy Storchaka ve Raymond " +"Hettinger'ın :issue:`37128`, :issue:`37178` ve :issue:`35431` 'deki " +"katkılarıyla.)" #: whatsnew/3.8.rst:985 msgid "" @@ -1915,12 +1931,12 @@ msgstr "mmap" #: whatsnew/3.8.rst:1006 msgid "" "The :class:`mmap.mmap` class now has an :meth:`~mmap.mmap.madvise` method to " -"access the ``madvise()`` system call. (Contributed by Zackery Spytz in :" -"issue:`32941`.)" +"access the ``madvise()`` system call. (Contributed by Zackery Spytz " +"in :issue:`32941`.)" msgstr "" ":class:`mmap.mmap` sınıfı artık ``madvise()`` sistem çağrısına erişmek için " -"bir :meth:`~mmap.mmap.madvise` yöntemine sahiptir. (Zackery Spytz'in :issue:" -"`32941` 'deki katkısıyla.)" +"bir :meth:`~mmap.mmap.madvise` yöntemine sahiptir. (Zackery " +"Spytz'in :issue:`32941` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1012 msgid "multiprocessing" @@ -1931,8 +1947,8 @@ msgid "" "Added new :mod:`multiprocessing.shared_memory` module. (Contributed by Davin " "Potts in :issue:`35813`.)" msgstr "" -"Yeni :mod:`multiprocessing.shared_memory` modülü eklendi. (Davin Potts'un :" -"issue:`35813` 'deki katkısıyla.)" +"Yeni :mod:`multiprocessing.shared_memory` modülü eklendi. (Davin " +"Potts'un :issue:`35813` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1017 msgid "" @@ -1950,13 +1966,13 @@ msgstr "os" msgid "" "Added new function :func:`~os.add_dll_directory` on Windows for providing " "additional search paths for native dependencies when importing extension " -"modules or loading DLLs using :mod:`ctypes`. (Contributed by Steve Dower in :" -"issue:`36085`.)" +"modules or loading DLLs using :mod:`ctypes`. (Contributed by Steve Dower " +"in :issue:`36085`.)" msgstr "" "Eklenti modüllerini içe aktarırken veya :mod:`ctypes` kullanarak DLL'leri " "yüklerken yerel bağımlılıklar için ek arama yolları sağlamak için Windows'ta " -"yeni :func:`~os.add_dll_directory` fonksiyonu eklendi. (Steve Dower'ın :" -"issue:`36085` 'teki katkısıyla.)" +"yeni :func:`~os.add_dll_directory` fonksiyonu eklendi. (Steve " +"Dower'ın :issue:`36085` 'teki katkısıyla.)" #: whatsnew/3.8.rst:1029 msgid "" @@ -1974,30 +1990,30 @@ msgid "" "symlinks and directory junctions) has been delegated to the operating " "system. Specifically, :func:`os.stat` will now traverse anything supported " "by the operating system, while :func:`os.lstat` will only open reparse " -"points that identify as \"name surrogates\" while others are opened as for :" -"func:`os.stat`. In all cases, :attr:`stat_result.st_mode` will only have " -"``S_IFLNK`` set for symbolic links and not other kinds of reparse points. To " -"identify other kinds of reparse point, check the new :attr:`stat_result." -"st_reparse_tag` attribute." +"points that identify as \"name surrogates\" while others are opened as " +"for :func:`os.stat`. In all cases, :attr:`stat_result.st_mode` will only " +"have ``S_IFLNK`` set for symbolic links and not other kinds of reparse " +"points. To identify other kinds of reparse point, check the " +"new :attr:`stat_result.st_reparse_tag` attribute." msgstr "" "Windows'ta, yeniden ayrıştırma noktalarını (sembolik bağlantılar ve dizin " "bağlantıları dahil) işlemek için manuel mantığın çoğu işletim sistemine " "devredilmiştir. Özellikle, :func:`os.stat` artık işletim sistemi tarafından " "desteklenen her şeyi geçerken, :func:`os.lstat` yalnızca \"isim vekilleri\" " -"olarak tanımlanan yeniden ayrıştırma noktalarını açacak, diğerleri ise :func:" -"`os.stat` için olduğu gibi açılacaktır. Her durumda, :attr:`stat_result." -"st_mode` sadece sembolik bağlantılar için ``S_IFLNK`` ayarına sahip olacak, " -"diğer türdeki ayrıştırma noktaları için olmayacaktır. Diğer yeniden " -"ayrıştırma noktası türlerini tanımlamak için yeni :attr:`stat_result." -"st_reparse_tag` niteliğini kontrol edin." +"olarak tanımlanan yeniden ayrıştırma noktalarını açacak, diğerleri " +"ise :func:`os.stat` için olduğu gibi açılacaktır. Her " +"durumda, :attr:`stat_result.st_mode` sadece sembolik bağlantılar için " +"``S_IFLNK`` ayarına sahip olacak, diğer türdeki ayrıştırma noktaları için " +"olmayacaktır. Diğer yeniden ayrıştırma noktası türlerini tanımlamak için " +"yeni :attr:`stat_result.st_reparse_tag` niteliğini kontrol edin." #: whatsnew/3.8.rst:1042 msgid "" "On Windows, :func:`os.readlink` is now able to read directory junctions. " "Note that :func:`~os.path.islink` will return ``False`` for directory " "junctions, and so code that checks ``islink`` first will continue to treat " -"junctions as directories, while code that handles errors from :func:`os." -"readlink` may now treat junctions as links." +"junctions as directories, while code that handles errors " +"from :func:`os.readlink` may now treat junctions as links." msgstr "" "Windows üzerinde, :func:`os.readlink` artık dizin bağlantılarını " "okuyabilmektedir. :func:`~os.path.islink` dizin bağlantıları için ``False`` " @@ -2015,28 +2031,27 @@ msgstr "os.path" #: whatsnew/3.8.rst:1054 msgid "" -":mod:`os.path` functions that return a boolean result like :func:`~os.path." -"exists`, :func:`~os.path.lexists`, :func:`~os.path.isdir`, :func:`~os.path." -"isfile`, :func:`~os.path.islink`, and :func:`~os.path.ismount` now return " -"``False`` instead of raising :exc:`ValueError` or its subclasses :exc:" -"`UnicodeEncodeError` and :exc:`UnicodeDecodeError` for paths that contain " -"characters or bytes unrepresentable at the OS level. (Contributed by Serhiy " -"Storchaka in :issue:`33721`.)" -msgstr "" -":func:`~os.path.exists`, :func:`~os.path.lexists`, :func:`~os.path.isdir`, :" -"func:`~os.path.isfile`, :func:`~os.path.islink` ve :func:`~os.path. ismount` " -"gibi boolean sonuç döndüren :mod:`os.path` fonksiyonları artık işletim " -"sistemi düzeyinde temsil edilemeyen karakterler veya baytlar içeren yollar " -"için :exc:`ValueError` veya alt sınıfları :exc:`UnicodeEncodeError` ve :exc:" -"`UnicodeDecodeError` yerine ``False`` döndürüyor. (Serhiy Storchaka'nın :" -"issue:`33721` 'deki katkısıyla.)" +":mod:`os.path` functions that return a boolean result " +"like :func:`~os.path.exists`, :func:`~os.path.lexists`, :func:`~os.path.isdir`, :func:`~os.path.isfile`, :func:`~os.path.islink`, " +"and :func:`~os.path.ismount` now return ``False`` instead of " +"raising :exc:`ValueError` or its subclasses :exc:`UnicodeEncodeError` " +"and :exc:`UnicodeDecodeError` for paths that contain characters or bytes " +"unrepresentable at the OS level. (Contributed by Serhiy Storchaka " +"in :issue:`33721`.)" +msgstr "" +":func:`~os.path.exists`, :func:`~os.path.lexists`, :func:`~os.path.isdir`, :func:`~os.path.isfile`, :func:`~os.path.islink` " +"ve :func:`~os.path. ismount` gibi boolean sonuç döndüren :mod:`os.path` " +"fonksiyonları artık işletim sistemi düzeyinde temsil edilemeyen karakterler " +"veya baytlar içeren yollar için :exc:`ValueError` veya alt " +"sınıfları :exc:`UnicodeEncodeError` ve :exc:`UnicodeDecodeError` yerine " +"``False`` döndürüyor. (Serhiy Storchaka'nın :issue:`33721` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1965 msgid "" ":func:`~os.path.expanduser` on Windows now prefers the :envvar:`USERPROFILE` " "environment variable and does not use :envvar:`HOME`, which is not normally " -"set for regular user accounts. (Contributed by Anthony Sottile in :issue:" -"`36264`.)" +"set for regular user accounts. (Contributed by Anthony Sottile " +"in :issue:`36264`.)" msgstr "" "Windows üzerinde :func:`~os.path.expanduser` artık :envvar:`USERPROFILE` " "ortam değişkenini tercih ediyor ve normalde normal kullanıcı hesapları için " @@ -2066,24 +2081,21 @@ msgstr "pathlib" #: whatsnew/3.8.rst:1079 #, fuzzy msgid "" -":mod:`pathlib.Path` methods that return a boolean result like :meth:" -"`~pathlib.Path.exists`, :meth:`~pathlib.Path.is_dir`, :meth:`~pathlib.Path." -"is_file`, :meth:`~pathlib.Path.is_mount`, :meth:`~pathlib.Path.is_symlink`, :" -"meth:`~pathlib.Path.is_block_device`, :meth:`~pathlib.Path.is_char_device`, :" -"meth:`~pathlib.Path.is_fifo`, :meth:`~pathlib.Path.is_socket` now return " -"``False`` instead of raising :exc:`ValueError` or its subclass :exc:" -"`UnicodeEncodeError` for paths that contain characters unrepresentable at " -"the OS level. (Contributed by Serhiy Storchaka in :issue:`33721`.)" -msgstr "" -":meth:`~pathlib.Path.exists()`, :meth:`~pathlib.Path.is_dir()`, :meth:" -"`~pathlib. Path.is_file()`, :meth:`~pathlib.Path.is_mount()`, :meth:" -"`~pathlib.Path.is_symlink()`, :meth:`~pathlib.Path.is_block_device()`, :meth:" -"`~pathlib. Path.is_char_device()`, :meth:`~pathlib.Path.is_fifo()`, :meth:" -"`~pathlib.Path.is_socket()` gibi boolean sonuç döndüren :mod:`pathlib.Path` " -"metotları artık işletim sistemi seviyesinde temsil edilemeyen karakterler " -"içeren yollar için :exc:`ValueError` veya alt sınıfı :exc:" -"`UnicodeEncodeError` yükseltmek yerine ``False`` döndürüyor. (Serhiy " -"Storchaka'nın :issue:`33721` 'deki katkısıyla.)" +":mod:`pathlib.Path` methods that return a boolean result " +"like :meth:`~pathlib.Path.exists`, :meth:`~pathlib.Path.is_dir`, :meth:`~pathlib.Path.is_file`, :meth:`~pathlib.Path.is_mount`, :meth:`~pathlib.Path.is_symlink`, :meth:`~pathlib.Path.is_block_device`, :meth:`~pathlib.Path.is_char_device`, :meth:`~pathlib.Path.is_fifo`, :meth:`~pathlib.Path.is_socket` " +"now return ``False`` instead of raising :exc:`ValueError` or its " +"subclass :exc:`UnicodeEncodeError` for paths that contain characters " +"unrepresentable at the OS level. (Contributed by Serhiy Storchaka " +"in :issue:`33721`.)" +msgstr "" +":meth:`~pathlib.Path.exists()`, :meth:`~pathlib.Path.is_dir()`, :meth:`~pathlib. " +"Path.is_file()`, :meth:`~pathlib.Path.is_mount()`, :meth:`~pathlib.Path.is_symlink()`, :meth:`~pathlib.Path.is_block_device()`, :meth:`~pathlib. " +"Path.is_char_device()`, :meth:`~pathlib.Path.is_fifo()`, :meth:`~pathlib.Path.is_socket()` " +"gibi boolean sonuç döndüren :mod:`pathlib.Path` metotları artık işletim " +"sistemi seviyesinde temsil edilemeyen karakterler içeren yollar " +"için :exc:`ValueError` veya alt sınıfı :exc:`UnicodeEncodeError` yükseltmek " +"yerine ``False`` döndürüyor. (Serhiy Storchaka'nın :issue:`33721` 'deki " +"katkısıyla.)" #: whatsnew/3.8.rst:1089 msgid "" @@ -2100,10 +2112,11 @@ msgstr "pickle" #: whatsnew/3.8.rst:1100 msgid "" -":mod:`pickle` extensions subclassing the C-optimized :class:`~pickle." -"Pickler` can now override the pickling logic of functions and classes by " -"defining the special :meth:`~pickle.Pickler.reducer_override` method. " -"(Contributed by Pierre Glaser and Olivier Grisel in :issue:`35900`.)" +":mod:`pickle` extensions subclassing the C-" +"optimized :class:`~pickle.Pickler` can now override the pickling logic of " +"functions and classes by defining the " +"special :meth:`~pickle.Pickler.reducer_override` method. (Contributed by " +"Pierre Glaser and Olivier Grisel in :issue:`35900`.)" msgstr "" "C-optimized :class:`~pickle.Pickler` alt sınıfını kullanan :mod:`pickle` " "uzantıları artık özel :meth:`~pickle.Pickler.reducer_override` yöntemini " @@ -2117,12 +2130,12 @@ msgstr "plistlib" #: whatsnew/3.8.rst:1109 msgid "" "Added new :class:`plistlib.UID` and enabled support for reading and writing " -"NSKeyedArchiver-encoded binary plists. (Contributed by Jon Janzen in :issue:" -"`26707`.)" +"NSKeyedArchiver-encoded binary plists. (Contributed by Jon Janzen " +"in :issue:`26707`.)" msgstr "" "Yeni :class:`plistlib.UID` eklendi ve NSKeyedArchiver ile kodlanmış ikili " -"plistleri okuma ve yazma desteği etkinleştirildi. (Jon Janzen tarafından :" -"issue:`26707` 'deki katkısıyla.)" +"plistleri okuma ve yazma desteği etkinleştirildi. (Jon Janzen " +"tarafından :issue:`26707` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1115 msgid "pprint" @@ -2153,8 +2166,8 @@ msgstr "" #: whatsnew/3.8.rst:1126 msgid "" ">>> from pprint import pprint, pp\n" -">>> d = dict(source='input.txt', operation='filter', destination='output." -"txt')\n" +">>> d = dict(source='input.txt', operation='filter', " +"destination='output.txt')\n" ">>> pp(d, width=40) # Original order\n" "{'source': 'input.txt',\n" " 'operation': 'filter',\n" @@ -2187,8 +2200,8 @@ msgstr "shlex" #: whatsnew/3.8.rst:1150 msgid "" -"The new :func:`shlex.join` function acts as the inverse of :func:`shlex." -"split`. (Contributed by Bo Bayles in :issue:`32102`.)" +"The new :func:`shlex.join` function acts as the inverse " +"of :func:`shlex.split`. (Contributed by Bo Bayles in :issue:`32102`.)" msgstr "" "Yeni :func:`shlex.join` fonksiyonu :func:`shlex.split` fonksiyonunun tersi " "gibi davranır. (Bo Bayles'in :issue:`32102` 'deki katkısıyla.)" @@ -2221,12 +2234,12 @@ msgstr "" #: whatsnew/3.8.rst:1165 msgid "" ":func:`shutil.rmtree` on Windows now removes directory junctions without " -"recursively removing their contents first. (Contributed by Steve Dower in :" -"issue:`37834`.)" +"recursively removing their contents first. (Contributed by Steve Dower " +"in :issue:`37834`.)" msgstr "" "windows üzerinde :func:`shutil.rmtree` artık dizin bağlantılarını önce " -"içeriklerini özyinelemeli olarak kaldırmadan kaldırıyor. (Steve Dower'ın :" -"issue:`37834` 'teki katkısıyla.)" +"içeriklerini özyinelemeli olarak kaldırmadan kaldırıyor. (Steve " +"Dower'ın :issue:`37834` 'teki katkısıyla.)" #: whatsnew/3.8.rst:1171 msgid "socket" @@ -2242,20 +2255,20 @@ msgid "" msgstr "" "Aynı soket üzerinde hem IPv4 hem de IPv6 bağlantılarını kabul etmek de dahil " "olmak üzere bir sunucu soketi oluştururken genellikle gerekli görevleri " -"otomatikleştirmek için :meth:`~socket.create_server()` ve :meth:`~socket." -"has_dualstack_ipv6()` kolaylık fonksiyonları eklendi. (Giampaolo " -"Rodolà'nın :issue:`17561` 'deki katkısıyla.)" +"otomatikleştirmek için :meth:`~socket.create_server()` " +"ve :meth:`~socket.has_dualstack_ipv6()` kolaylık fonksiyonları eklendi. " +"(Giampaolo Rodolà'nın :issue:`17561` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1178 #, fuzzy msgid "" -"The :func:`socket.if_nameindex`, :func:`socket.if_nametoindex`, and :func:" -"`socket.if_indextoname` functions have been implemented on Windows. " -"(Contributed by Zackery Spytz in :issue:`37007`.)" +"The :func:`socket.if_nameindex`, :func:`socket.if_nametoindex`, " +"and :func:`socket.if_indextoname` functions have been implemented on " +"Windows. (Contributed by Zackery Spytz in :issue:`37007`.)" msgstr "" -":func:`socket.if_nameindex()`, :func:`socket.if_nametoindex()` ve :func:" -"`socket.if_indextoname()` fonksiyonları Windows'ta uygulanmıştır. (Zackery " -"Spytz'in :issue:`37007` 'deki katkısıyla.)" +":func:`socket.if_nameindex()`, :func:`socket.if_nametoindex()` " +"ve :func:`socket.if_indextoname()` fonksiyonları Windows'ta uygulanmıştır. " +"(Zackery Spytz'in :issue:`37007` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1184 msgid "ssl" @@ -2263,14 +2276,15 @@ msgstr "ssl" #: whatsnew/3.8.rst:1186 msgid "" -"Added :attr:`~ssl.SSLContext.post_handshake_auth` to enable and :meth:`~ssl." -"SSLSocket.verify_client_post_handshake` to initiate TLS 1.3 post-handshake " -"authentication. (Contributed by Christian Heimes in :issue:`34670`.)" +"Added :attr:`~ssl.SSLContext.post_handshake_auth` to enable " +"and :meth:`~ssl.SSLSocket.verify_client_post_handshake` to initiate TLS 1.3 " +"post-handshake authentication. (Contributed by Christian Heimes " +"in :issue:`34670`.)" msgstr "" -"TLS 1.3 post-handshake kimlik doğrulamasını başlatmak için :attr:`~ssl." -"SSLContext.post_handshake_auth` etkinleştirildi ve :meth:`~ssl.SSLSocket." -"verify_client_post_handshake` eklendi. (Christian Heimes'in :issue:`34670` " -"'teki katkısıyla.)" +"TLS 1.3 post-handshake kimlik doğrulamasını başlatmak " +"için :attr:`~ssl.SSLContext.post_handshake_auth` etkinleştirildi " +"ve :meth:`~ssl.SSLSocket.verify_client_post_handshake` eklendi. (Christian " +"Heimes'in :issue:`34670` 'teki katkısıyla.)" #: whatsnew/3.8.rst:1193 msgid "statistics" @@ -2279,13 +2293,13 @@ msgstr "statistics" #: whatsnew/3.8.rst:1195 #, fuzzy msgid "" -"Added :func:`statistics.fmean` as a faster, floating-point variant of :func:" -"`statistics.mean`. (Contributed by Raymond Hettinger and Steven D'Aprano " -"in :issue:`35904`.)" +"Added :func:`statistics.fmean` as a faster, floating-point variant " +"of :func:`statistics.mean`. (Contributed by Raymond Hettinger and Steven " +"D'Aprano in :issue:`35904`.)" msgstr "" "Eklenen :func:`statistics.fmean`, :func:`statistics.mean()` 'in daha hızlı, " -"kayan noktalı bir çeşididir. (Raymond Hettinger ve Steven D'Aprano 'nun :" -"issue:`35904` 'taki katkılarıyla.)" +"kayan noktalı bir çeşididir. (Raymond Hettinger ve Steven D'Aprano " +"'nun :issue:`35904` 'taki katkılarıyla.)" #: whatsnew/3.8.rst:1199 #, fuzzy @@ -2293,8 +2307,8 @@ msgid "" "Added :func:`statistics.geometric_mean` (Contributed by Raymond Hettinger " "in :issue:`27181`.)" msgstr "" -":func:`statistics.geometric_mean()` eklendi (Raymond Hettinger'ın :issue:" -"`27181` 'deki katkısıyla.)" +":func:`statistics.geometric_mean()` eklendi (Raymond " +"Hettinger'ın :issue:`27181` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1202 msgid "" @@ -2321,8 +2335,8 @@ msgid "" "in :issue:`36018`.)" msgstr "" "Rastgele bir değişkenin normal dağılımlarını oluşturmak ve işlemek için bir " -"araç olan :class:`statistics.NormalDist` eklendi. (Raymond Hettinger'ın :" -"issue:`36018` 'deki katkısıyla. )" +"araç olan :class:`statistics.NormalDist` eklendi. (Raymond " +"Hettinger'ın :issue:`36018` 'deki katkısıyla. )" #: whatsnew/3.8.rst:1215 msgid "" @@ -2392,32 +2406,34 @@ msgstr "threading" #: whatsnew/3.8.rst:1262 msgid "" -"Add a new :func:`threading.excepthook` function which handles uncaught :meth:" -"`threading.Thread.run` exception. It can be overridden to control how " -"uncaught :meth:`threading.Thread.run` exceptions are handled. (Contributed " -"by Victor Stinner in :issue:`1230540`.)" +"Add a new :func:`threading.excepthook` function which handles " +"uncaught :meth:`threading.Thread.run` exception. It can be overridden to " +"control how uncaught :meth:`threading.Thread.run` exceptions are handled. " +"(Contributed by Victor Stinner in :issue:`1230540`.)" msgstr "" -"Yakalanmamış :meth:`threading.Thread.run` istisnalarını işleyen yeni bir :" -"func:`threading.excepthook` fonksiyonu ekleyin. Yakalanmamış :meth:" -"`threading.Thread.run` istisnalarının nasıl işleneceğini kontrol etmek için " -"geçersiz kılınabilir. (Victor Stinner'ın :issue:`1230540` 'taki katkısıyla.)" +"Yakalanmamış :meth:`threading.Thread.run` istisnalarını işleyen yeni " +"bir :func:`threading.excepthook` fonksiyonu ekleyin. " +"Yakalanmamış :meth:`threading.Thread.run` istisnalarının nasıl işleneceğini " +"kontrol etmek için geçersiz kılınabilir. (Victor Stinner'ın :issue:`1230540` " +"'taki katkısıyla.)" #: whatsnew/3.8.rst:1267 msgid "" -"Add a new :func:`threading.get_native_id` function and a :data:`~threading." -"Thread.native_id` attribute to the :class:`threading.Thread` class. These " -"return the native integral Thread ID of the current thread assigned by the " -"kernel. This feature is only available on certain platforms, see :func:" -"`get_native_id ` for more information. (Contributed " -"by Jake Tesler in :issue:`36084`.)" -msgstr "" -"Yeni bir :func:`threading.get_native_id` fonksiyonu ve :data:`~threading." -"Thread.native_id` niteliğini :class:`threading.Thread` sınıfına ekleyin. " -"Bunlar, çekirdek tarafından atanan geçerli iş parçacığının yerel integral İş " -"Parçacığı Kimliğini döndürür. Bu özellik yalnızca belirli platformlarda " -"kullanılabilir, daha fazla bilgi için :func:`get_native_id ` bölümüne bakın. (Jake Tesler'ın :issue:`36084` 'teki " -"katkısıyla.)" +"Add a new :func:`threading.get_native_id` function and " +"a :data:`~threading.Thread.native_id` attribute to " +"the :class:`threading.Thread` class. These return the native integral Thread " +"ID of the current thread assigned by the kernel. This feature is only " +"available on certain platforms, see :func:`get_native_id " +"` for more information. (Contributed by Jake Tesler " +"in :issue:`36084`.)" +msgstr "" +"Yeni bir :func:`threading.get_native_id` fonksiyonu " +"ve :data:`~threading.Thread.native_id` niteliğini :class:`threading.Thread` " +"sınıfına ekleyin. Bunlar, çekirdek tarafından atanan geçerli iş parçacığının " +"yerel integral İş Parçacığı Kimliğini döndürür. Bu özellik yalnızca belirli " +"platformlarda kullanılabilir, daha fazla bilgi için :func:`get_native_id " +"` bölümüne bakın. (Jake Tesler'ın :issue:`36084` " +"'teki katkısıyla.)" #: whatsnew/3.8.rst:1277 msgid "tokenize" @@ -2432,8 +2448,8 @@ msgid "" msgstr "" ":mod:`tokenize` modülü artık sonda yeni bir satır olmayan girdi " "sağlandığında örtük olarak bir ``NEWLINE`` belirteci yayar. Bu davranış " -"artık C tokenizer'ın dahili olarak yaptığı ile eşleşiyor. (Ammar Askar'ın :" -"issue:`33899` 'daki katkısıyla.)" +"artık C tokenizer'ın dahili olarak yaptığı ile eşleşiyor. (Ammar " +"Askar'ın :issue:`33899` 'daki katkısıyla.)" #: whatsnew/3.8.rst:1286 msgid "tkinter" @@ -2441,15 +2457,15 @@ msgstr "tkinter" #: whatsnew/3.8.rst:1288 msgid "" -"Added methods :meth:`~tkinter.Spinbox.selection_from`, :meth:`~tkinter." -"Spinbox.selection_present`, :meth:`~tkinter.Spinbox.selection_range` and :" -"meth:`~tkinter.Spinbox.selection_to` in the :class:`tkinter.Spinbox` class. " -"(Contributed by Juliette Monsel in :issue:`34829`.)" +"Added " +"methods :meth:`~tkinter.Spinbox.selection_from`, :meth:`~tkinter.Spinbox.selection_present`, :meth:`~tkinter.Spinbox.selection_range` " +"and :meth:`~tkinter.Spinbox.selection_to` in the :class:`tkinter.Spinbox` " +"class. (Contributed by Juliette Monsel in :issue:`34829`.)" msgstr "" -":class:`tkinter.Spinbox` sınıfına :meth:`~tkinter.Spinbox.selection_from`, :" -"meth:`~tkinter.Spinbox.selection_present`, :meth:`~tkinter.Spinbox." -"selection_range` ve :meth:`~tkinter.Spinbox.selection_to` yöntemleri " -"eklendi. (Juliette Monsel'ın :issue:`34829` 'daki katkısıyla.)" +":class:`tkinter.Spinbox` " +"sınıfına :meth:`~tkinter.Spinbox.selection_from`, :meth:`~tkinter.Spinbox.selection_present`, :meth:`~tkinter.Spinbox.selection_range` " +"ve :meth:`~tkinter.Spinbox.selection_to` yöntemleri eklendi. (Juliette " +"Monsel'ın :issue:`34829` 'daki katkısıyla.)" #: whatsnew/3.8.rst:1295 msgid "" @@ -2461,13 +2477,15 @@ msgstr "" #: whatsnew/3.8.rst:1299 msgid "" -"The :class:`tkinter.PhotoImage` class now has :meth:`~tkinter.PhotoImage." -"transparency_get` and :meth:`~tkinter.PhotoImage.transparency_set` methods. " -"(Contributed by Zackery Spytz in :issue:`25451`.)" +"The :class:`tkinter.PhotoImage` class now " +"has :meth:`~tkinter.PhotoImage.transparency_get` " +"and :meth:`~tkinter.PhotoImage.transparency_set` methods. (Contributed by " +"Zackery Spytz in :issue:`25451`.)" msgstr "" -":class:`tkinter.PhotoImage` sınıfı artık :meth:`~tkinter.PhotoImage." -"transparency_get` ve :meth:`~tkinter.PhotoImage.transparency_set` " -"yöntemlerine sahiptir. (Zackery Spytz'in :issue:`25451` 'deki katkısıyla.)" +":class:`tkinter.PhotoImage` sınıfı " +"artık :meth:`~tkinter.PhotoImage.transparency_get` " +"ve :meth:`~tkinter.PhotoImage.transparency_set` yöntemlerine sahiptir. " +"(Zackery Spytz'in :issue:`25451` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1306 msgid "time" @@ -2492,13 +2510,13 @@ msgstr ":mod:`typing` modülü birkaç yeni özellik içerir:" #: whatsnew/3.8.rst:1317 msgid "" -"A dictionary type with per-key types. See :pep:`589` and :class:`typing." -"TypedDict`. TypedDict uses only string keys. By default, every key is " -"required to be present. Specify \"total=False\" to allow keys to be " -"optional::" +"A dictionary type with per-key types. See :pep:`589` " +"and :class:`typing.TypedDict`. TypedDict uses only string keys. By default, " +"every key is required to be present. Specify \"total=False\" to allow keys " +"to be optional::" msgstr "" -"Anahtar başına türleri olan bir sözlük türü. Bakınız :pep:`589` ve :class:" -"`typing.TypedDict`. TypedDict yalnızca dize anahtarları kullanır. " +"Anahtar başına türleri olan bir sözlük türü. Bakınız :pep:`589` " +"ve :class:`typing.TypedDict`. TypedDict yalnızca dize anahtarları kullanır. " "Varsayılan olarak, her anahtarın mevcut olması gerekir. Anahtarların isteğe " "bağlı olmasına izin vermek için \"total=False\" belirtin::" @@ -2528,14 +2546,15 @@ msgstr "" #: whatsnew/3.8.rst:1334 msgid "" -"\"Final\" variables, functions, methods and classes. See :pep:`591`, :class:" -"`typing.Final` and :func:`typing.final`. The final qualifier instructs a " -"static type checker to restrict subclassing, overriding, or reassignment::" +"\"Final\" variables, functions, methods and classes. " +"See :pep:`591`, :class:`typing.Final` and :func:`typing.final`. The final " +"qualifier instructs a static type checker to restrict subclassing, " +"overriding, or reassignment::" msgstr "" -"\"Final\" değişkenler, fonksiyonlar, metotlar ve sınıflar. Bakınız :pep:" -"`591`, :class:`typing.Final` ve :func:`typing.final`. Final niteleyicisi " -"statik tip denetleyicisine alt sınıflamayı, geçersiz kılmayı veya yeniden " -"atamayı kısıtlama talimatı verir::" +"\"Final\" değişkenler, fonksiyonlar, metotlar ve sınıflar. " +"Bakınız :pep:`591`, :class:`typing.Final` ve :func:`typing.final`. Final " +"niteleyicisi statik tip denetleyicisine alt sınıflamayı, geçersiz kılmayı " +"veya yeniden atamayı kısıtlama talimatı verir::" #: whatsnew/3.8.rst:1339 msgid "pi: Final[float] = 3.1415926536" @@ -2543,13 +2562,13 @@ msgstr "" #: whatsnew/3.8.rst:1341 msgid "" -"Protocol definitions. See :pep:`544`, :class:`typing.Protocol` and :func:" -"`typing.runtime_checkable`. Simple ABCs like :class:`typing.SupportsInt` " -"are now ``Protocol`` subclasses." +"Protocol definitions. See :pep:`544`, :class:`typing.Protocol` " +"and :func:`typing.runtime_checkable`. Simple ABCs " +"like :class:`typing.SupportsInt` are now ``Protocol`` subclasses." msgstr "" -"Protokol tanımları. Bakınız :pep:`544`, :class:`typing.Protocol` ve :func:" -"`typing.runtime_checkable`. :class:`typing.SupportsInt` gibi basit ABC'ler " -"artık ``Protocol`` alt sınıflarıdır." +"Protokol tanımları. Bakınız :pep:`544`, :class:`typing.Protocol` " +"ve :func:`typing.runtime_checkable`. :class:`typing.SupportsInt` gibi basit " +"ABC'ler artık ``Protocol`` alt sınıflarıdır." #: whatsnew/3.8.rst:1345 msgid "New protocol class :class:`typing.SupportsIndex`." @@ -2593,8 +2612,8 @@ msgstr "unittest" msgid "" "Added :class:`~unittest.mock.AsyncMock` to support an asynchronous version " "of :class:`~unittest.mock.Mock`. Appropriate new assert functions for " -"testing have been added as well. (Contributed by Lisa Roach in :issue:" -"`26467`)." +"testing have been added as well. (Contributed by Lisa Roach " +"in :issue:`26467`)." msgstr "" "Eklenen :class:`~unittest.mock.AsyncMock`, :class:`~unittest.mock.Mock` 'un " "asenkron versiyonunu desteklemektedir. Test için uygun yeni savunma " @@ -2604,15 +2623,17 @@ msgstr "" #: whatsnew/3.8.rst:1370 #, fuzzy msgid "" -"Added :func:`~unittest.addModuleCleanup` and :meth:`~unittest.TestCase." -"addClassCleanup` to unittest to support cleanups for :func:`~unittest." -"setUpModule` and :meth:`~unittest.TestCase.setUpClass`. (Contributed by Lisa " -"Roach in :issue:`24412`.)" +"Added :func:`~unittest.addModuleCleanup` " +"and :meth:`~unittest.TestCase.addClassCleanup` to unittest to support " +"cleanups for :func:`~unittest.setUpModule` " +"and :meth:`~unittest.TestCase.setUpClass`. (Contributed by Lisa Roach " +"in :issue:`24412`.)" msgstr "" -"Unitteste :func:`~unittest.setUpModule()` ve :meth:`~unittest.TestCase." -"setUpClass()` için temizleme işlemlerini desteklemek üzere :func:`~unittest." -"addModuleCleanup()` ve :meth:`~unittest.TestCase.addClassCleanup()` eklendi. " -"(Lisa Roach 'un :issue:`24412` 'deki katkısıyla.)" +"Unitteste :func:`~unittest.setUpModule()` " +"ve :meth:`~unittest.TestCase.setUpClass()` için temizleme işlemlerini " +"desteklemek üzere :func:`~unittest.addModuleCleanup()` " +"ve :meth:`~unittest.TestCase.addClassCleanup()` eklendi. (Lisa Roach " +"'un :issue:`24412` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1376 msgid "" @@ -2693,9 +2714,10 @@ msgstr "xml" #: whatsnew/3.8.rst:1424 msgid "" -"As mitigation against DTD and external entity retrieval, the :mod:`xml.dom." -"minidom` and :mod:`xml.sax` modules no longer process external entities by " -"default. (Contributed by Christian Heimes in :issue:`17239`.)" +"As mitigation against DTD and external entity retrieval, " +"the :mod:`xml.dom.minidom` and :mod:`xml.sax` modules no longer process " +"external entities by default. (Contributed by Christian Heimes " +"in :issue:`17239`.)" msgstr "" "DTD ve harici varlık alımına karşı hafifletme olarak, :mod:`xml.dom.minidom` " "ve :mod:`xml.sax` modülleri artık varsayılan olarak harici varlıkları " @@ -2716,22 +2738,23 @@ msgstr "" #: whatsnew/3.8.rst:1434 #, fuzzy msgid "" -"The :mod:`xml.etree.ElementTree` module provides a new function :func:`–xml." -"etree.ElementTree.canonicalize` that implements C14N 2.0. (Contributed by " -"Stefan Behnel in :issue:`13611`.)" +"The :mod:`xml.etree.ElementTree` module provides a new function :func:`–" +"xml.etree.ElementTree.canonicalize` that implements C14N 2.0. (Contributed " +"by Stefan Behnel in :issue:`13611`.)" msgstr "" ":mod:`xml.etree.ElementTree` modülü, C14N 2.0'ı uygulayan yeni bir :func:`-" -"xml.etree.ElementTree.canonicalize()` fonksiyonu sağlar. (Stefan Behnel'ın :" -"issue:`13611` 'deki katkısıyla.)" +"xml.etree.ElementTree.canonicalize()` fonksiyonu sağlar. (Stefan " +"Behnel'ın :issue:`13611` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1438 msgid "" "The target object of :class:`xml.etree.ElementTree.XMLParser` can receive " "namespace declaration events through the new callback methods ``start_ns()`` " -"and ``end_ns()``. Additionally, the :class:`xml.etree.ElementTree." -"TreeBuilder` target can be configured to process events about comments and " -"processing instructions to include them in the generated tree. (Contributed " -"by Stefan Behnel in :issue:`36676` and :issue:`36673`.)" +"and ``end_ns()``. Additionally, " +"the :class:`xml.etree.ElementTree.TreeBuilder` target can be configured to " +"process events about comments and processing instructions to include them in " +"the generated tree. (Contributed by Stefan Behnel in :issue:`36676` " +"and :issue:`36673`.)" msgstr "" ":class:`xml.etree.ElementTree.XMLParser` hedef nesnesi, yeni ``start_ns()`` " "ve ``end_ns()`` geri çağırma yöntemleri aracılığıyla ad alanı bildirimi " @@ -2768,10 +2791,10 @@ msgid "" "in some cases for better performance. Currently, it is only used on macOS " "and Linux (using glibc 2.24 or newer) if all these conditions are met:" msgstr "" -":mod:`subprocess` modülü artık daha iyi performans için bazı durumlarda :" -"func:`os.posix_spawn` fonksiyonunu kullanabilir. Şu anda, yalnızca macOS ve " -"Linux'ta (glibc 2.24 veya daha yenisini kullanan) tüm bu koşullar yerine " -"getirilirse kullanılmaktadır:" +":mod:`subprocess` modülü artık daha iyi performans için bazı " +"durumlarda :func:`os.posix_spawn` fonksiyonunu kullanabilir. Şu anda, " +"yalnızca macOS ve Linux'ta (glibc 2.24 veya daha yenisini kullanan) tüm bu " +"koşullar yerine getirilirse kullanılmaktadır:" #: whatsnew/3.8.rst:1464 msgid "*close_fds* is false;" @@ -2796,32 +2819,32 @@ msgstr "" #: whatsnew/3.8.rst:1471 msgid "" -":func:`shutil.copyfile`, :func:`shutil.copy`, :func:`shutil.copy2`, :func:" -"`shutil.copytree` and :func:`shutil.move` use platform-specific \"fast-" -"copy\" syscalls on Linux and macOS in order to copy the file more " -"efficiently. \"fast-copy\" means that the copying operation occurs within " -"the kernel, avoiding the use of userspace buffers in Python as in \"``outfd." -"write(infd.read())``\". On Windows :func:`shutil.copyfile` uses a bigger " -"default buffer size (1 MiB instead of 16 KiB) and a :func:`memoryview`-based " -"variant of :func:`shutil.copyfileobj` is used. The speedup for copying a 512 " -"MiB file within the same partition is about +26% on Linux, +50% on macOS and " +":func:`shutil.copyfile`, :func:`shutil.copy`, :func:`shutil.copy2`, :func:`shutil.copytree` " +"and :func:`shutil.move` use platform-specific \"fast-copy\" syscalls on " +"Linux and macOS in order to copy the file more efficiently. \"fast-copy\" " +"means that the copying operation occurs within the kernel, avoiding the use " +"of userspace buffers in Python as in \"``outfd.write(infd.read())``\". On " +"Windows :func:`shutil.copyfile` uses a bigger default buffer size (1 MiB " +"instead of 16 KiB) and a :func:`memoryview`-based variant " +"of :func:`shutil.copyfileobj` is used. The speedup for copying a 512 MiB " +"file within the same partition is about +26% on Linux, +50% on macOS and " "+40% on Windows. Also, much less CPU cycles are consumed. See :ref:`shutil-" "platform-dependent-efficient-copy-operations` section. (Contributed by " "Giampaolo Rodolà in :issue:`33671`.)" msgstr "" -":func:`shutil.copyfile`, :func:`shutil.copy`, :func:`shutil.copy2`, :func:" -"`shutil.copytree` ve :func:`shutil.move`, dosyayı daha verimli bir şekilde " -"kopyalamak için Linux ve macOS'ta platforma özgü \"fast-copy\" sistem " -"çağrılarını kullanır. \"fast-copy\", kopyalama işleminin çekirdek içinde " -"gerçekleştiği ve Python'da \"``outfd.write(infd.read())``\" gibi kullanıcı " -"alanı tamponlarının kullanılmasından kaçınıldığı anlamına gelir. Windows " +":func:`shutil.copyfile`, :func:`shutil.copy`, :func:`shutil.copy2`, :func:`shutil.copytree` " +"ve :func:`shutil.move`, dosyayı daha verimli bir şekilde kopyalamak için " +"Linux ve macOS'ta platforma özgü \"fast-copy\" sistem çağrılarını kullanır. " +"\"fast-copy\", kopyalama işleminin çekirdek içinde gerçekleştiği ve " +"Python'da \"``outfd.write(infd.read())``\" gibi kullanıcı alanı " +"tamponlarının kullanılmasından kaçınıldığı anlamına gelir. Windows " "üzerinde :func:`shutil.copyfile` daha büyük bir varsayılan tampon boyutu " -"kullanır (16 KiB yerine 1 MiB) ve :func:`shutil.copyfileobj` 'nin :func:" -"`memoryview` tabanlı bir çeşidi kullanılır. Aynı bölüm içinde 512 MiB'lık " -"bir dosyayı kopyalamak için hızlanma yaklaşık olarak Linux'te +26%, macOS'da " -"+50% ve Windows'ta +40%'tır. Ayrıca, çok daha az CPU döngüsü tüketilir. Bkz :" -"ref:`shutil-platform-dependent-efficient-copy-operations` bölümü. (Giampaolo " -"Rodolà'nın :issue:`33671` 'deki katkısıyla.)" +"kullanır (16 KiB yerine 1 MiB) ve :func:`shutil.copyfileobj` " +"'nin :func:`memoryview` tabanlı bir çeşidi kullanılır. Aynı bölüm içinde 512 " +"MiB'lık bir dosyayı kopyalamak için hızlanma yaklaşık olarak Linux'te +26%, " +"macOS'da +50% ve Windows'ta +40%'tır. Ayrıca, çok daha az CPU döngüsü " +"tüketilir. Bkz :ref:`shutil-platform-dependent-efficient-copy-operations` " +"bölümü. (Giampaolo Rodolà'nın :issue:`33671` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1487 msgid "" @@ -2923,19 +2946,20 @@ msgstr "" msgid "" "Reduced an overhead of converting arguments passed to many builtin functions " "and methods. This sped up calling some simple builtin functions and methods " -"up to 20--50%. (Contributed by Serhiy Storchaka in :issue:`23867`, :issue:" -"`35582` and :issue:`36127`.)" +"up to 20--50%. (Contributed by Serhiy Storchaka " +"in :issue:`23867`, :issue:`35582` and :issue:`36127`.)" msgstr "" "Birçok yerleşik fonksiyon ve metoda aktarılan argümanları dönüştürme yükü " "azaltıldı. Bu, bazı basit yerleşik fonksiyonların ve yöntemlerin " -"çağrılmasını %20--50'ye kadar hızlandırdı. (Serhiy Storchaka'nın :issue:" -"`23867`, :issue:`35582` ve :issue:`36127` 'deki katkılarıyla.)" +"çağrılmasını %20--50'ye kadar hızlandırdı. (Serhiy " +"Storchaka'nın :issue:`23867`, :issue:`35582` ve :issue:`36127` 'deki " +"katkılarıyla.)" #: whatsnew/3.8.rst:1531 msgid "" "``LOAD_GLOBAL`` instruction now uses new \"per opcode cache\" mechanism. It " -"is about 40% faster now. (Contributed by Yury Selivanov and Inada Naoki in :" -"issue:`26219`.)" +"is about 40% faster now. (Contributed by Yury Selivanov and Inada Naoki " +"in :issue:`26219`.)" msgstr "" "``LOAD_GLOBAL`` komutu artık yeni \"işlem kodu başına önbellek\" " "mekanizmasını kullanıyor. Şimdi yaklaşık 40% daha hızlı. (Yury Selivanov ve " @@ -2949,13 +2973,13 @@ msgstr "Derleme ve C API Değişiklikleri" msgid "" "Default :data:`sys.abiflags` became an empty string: the ``m`` flag for " "pymalloc became useless (builds with and without pymalloc are ABI " -"compatible) and so has been removed. (Contributed by Victor Stinner in :" -"issue:`36707`.)" +"compatible) and so has been removed. (Contributed by Victor Stinner " +"in :issue:`36707`.)" msgstr "" "Varsayılan :data:`sys.abiflags` boş bir dize haline geldi: pymalloc için " "``m`` bayrağı işe yaramaz hale geldi (hem pymalloc içeren hem de içermeyen " -"derlemeler ABI uyumludur) ve bu nedenle kaldırıldı. (Victor Stinner'ın :" -"issue:`36707` 'deki katkısıyla.)" +"derlemeler ABI uyumludur) ve bu nedenle kaldırıldı. (Victor " +"Stinner'ın :issue:`36707` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1543 msgid "Example of changes:" @@ -3028,8 +3052,8 @@ msgid "" "(Contributed by Victor Stinner in :issue:`35134` and :issue:`35081`, work " "initiated by Eric Snow in Python 3.7.)" msgstr "" -"(Eric Snow tarafından Python 3.7'de başlatılan çalışmaya :issue:`35134` ve :" -"issue:`35081` 'de Victor Stinner tarafından katkı sağlanmıştır.)" +"(Eric Snow tarafından Python 3.7'de başlatılan çalışmaya :issue:`35134` " +"ve :issue:`35081` 'de Victor Stinner tarafından katkı sağlanmıştır.)" #: whatsnew/3.8.rst:1570 msgid "" @@ -3059,8 +3083,8 @@ msgid "" "Private functions: :c:func:`!_PyObject_GC_TRACK`, :c:func:`!" "_PyObject_GC_UNTRACK`, :c:func:`!_Py_Dealloc`" msgstr "" -"Özel fonksiyonlar: :c:func:`_PyObject_GC_TRACK`, :c:func:" -"`_PyObject_GC_UNTRACK`, :c:func:`_Py_Dealloc`" +"Özel " +"fonksiyonlar: :c:func:`_PyObject_GC_TRACK`, :c:func:`_PyObject_GC_UNTRACK`, :c:func:`_Py_Dealloc`" #: whatsnew/3.8.rst:1580 msgid "(Contributed by Victor Stinner in :issue:`35059`.)" @@ -3082,8 +3106,8 @@ msgstr "" #: whatsnew/3.8.rst:1587 msgid "" "The result of :c:func:`PyExceptionClass_Name` is now of type ``const char " -"*`` rather of ``char *``. (Contributed by Serhiy Storchaka in :issue:" -"`33818`.)" +"*`` rather of ``char *``. (Contributed by Serhiy Storchaka " +"in :issue:`33818`.)" msgstr "" ":c:func:`PyExceptionClass_Name` sonucu artık ``char *`` yerine ``const char " "*`` türündedir. (Serhiy Storchaka'nın :issue:`33818` 'deki katkısıyla.)" @@ -3126,18 +3150,19 @@ msgstr "(Antoine Pitrou'nun :issue:`32388` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1606 msgid "" -"Functions that convert Python number to C integer like :c:func:" -"`PyLong_AsLong` and argument parsing functions like :c:func:" -"`PyArg_ParseTuple` with integer converting format units like ``'i'`` will " -"now use the :meth:`~object.__index__` special method instead of :meth:" -"`~object.__int__`, if available. The deprecation warning will be emitted " -"for objects with the ``__int__()`` method but without the ``__index__()`` " -"method (like :class:`~decimal.Decimal` and :class:`~fractions.Fraction`). :" -"c:func:`PyNumber_Check` will now return ``1`` for objects implementing " -"``__index__()``. :c:func:`PyNumber_Long`, :c:func:`PyNumber_Float` and :c:" -"func:`PyFloat_AsDouble` also now use the ``__index__()`` method if " -"available. (Contributed by Serhiy Storchaka in :issue:`36048` and :issue:" -"`20092`.)" +"Functions that convert Python number to C integer " +"like :c:func:`PyLong_AsLong` and argument parsing functions " +"like :c:func:`PyArg_ParseTuple` with integer converting format units like " +"``'i'`` will now use the :meth:`~object.__index__` special method instead " +"of :meth:`~object.__int__`, if available. The deprecation warning will be " +"emitted for objects with the ``__int__()`` method but without the " +"``__index__()`` method (like :class:`~decimal.Decimal` " +"and :class:`~fractions.Fraction`). :c:func:`PyNumber_Check` will now return " +"``1`` for objects implementing " +"``__index__()``. :c:func:`PyNumber_Long`, :c:func:`PyNumber_Float` " +"and :c:func:`PyFloat_AsDouble` also now use the ``__index__()`` method if " +"available. (Contributed by Serhiy Storchaka in :issue:`36048` " +"and :issue:`20092`.)" msgstr "" ":c:func:`PyLong_AsLong` gibi Python sayısını C tamsayısına dönüştüren " "fonksiyonlar ve :c:func:`PyArg_ParseTuple` gibi ``'i'`` gibi tamsayı " @@ -3145,26 +3170,27 @@ msgstr "" "mümkünse :meth:`~object.__int__` yerine :meth:`~object.__index__` özel " "metodunu kullanacaktır. Kullanımdan kaldırma uyarısı, ``__int__()`` yöntemi " "olan ancak ``index__()`` yöntemi olmayan nesneler (:class:`~decimal.Decimal` " -"ve :class:`~fractions.Fraction` gibi) için verilecektir. :c:func:" -"`PyNumber_Check` artık ``__index__()`` yöntemini uygulayan nesneler için " -"``1`` değerini döndürecektir. :c:func:`PyNumber_Long`, :c:func:" -"`PyNumber_Float` ve :c:func:`PyFloat_AsDouble` artık mümkünse " -"``__index__()`` yöntemini de kullanmaktadır. (Serhiy Storchaka'nın :issue:" -"`36048` ve :issue:`20092` 'deki katkılarıyla.)" +"ve :class:`~fractions.Fraction` gibi) için " +"verilecektir. :c:func:`PyNumber_Check` artık ``__index__()`` yöntemini " +"uygulayan nesneler için ``1`` değerini " +"döndürecektir. :c:func:`PyNumber_Long`, :c:func:`PyNumber_Float` " +"ve :c:func:`PyFloat_AsDouble` artık mümkünse ``__index__()`` yöntemini de " +"kullanmaktadır. (Serhiy Storchaka'nın :issue:`36048` ve :issue:`20092` 'deki " +"katkılarıyla.)" #: whatsnew/3.8.rst:1620 msgid "" -"Heap-allocated type objects will now increase their reference count in :c:" -"func:`PyObject_Init` (and its parallel macro ``PyObject_INIT``) instead of " -"in :c:func:`PyType_GenericAlloc`. Types that modify instance allocation or " -"deallocation may need to be adjusted. (Contributed by Eddie Elizondo in :" -"issue:`35810`.)" +"Heap-allocated type objects will now increase their reference count " +"in :c:func:`PyObject_Init` (and its parallel macro ``PyObject_INIT``) " +"instead of in :c:func:`PyType_GenericAlloc`. Types that modify instance " +"allocation or deallocation may need to be adjusted. (Contributed by Eddie " +"Elizondo in :issue:`35810`.)" msgstr "" -"Yığın tahsisli tip nesneleri artık referans sayılarını :c:func:" -"`PyType_GenericAlloc` yerine :c:func:`PyObject_Init` (ve paralel makrosu " -"``PyObject_INIT``) içinde artıracaktır. Örnek paylaştırma veya serbest " -"bırakma işlemini değiştiren türlerin ayarlanması gerekebilir. (Eddie " -"Elizondo'nun :issue:`35810` 'daki katkısıyla.)" +"Yığın tahsisli tip nesneleri artık referans " +"sayılarını :c:func:`PyType_GenericAlloc` yerine :c:func:`PyObject_Init` (ve " +"paralel makrosu ``PyObject_INIT``) içinde artıracaktır. Örnek paylaştırma " +"veya serbest bırakma işlemini değiştiren türlerin ayarlanması gerekebilir. " +"(Eddie Elizondo'nun :issue:`35810` 'daki katkısıyla.)" #: whatsnew/3.8.rst:1626 #, fuzzy @@ -3183,13 +3209,14 @@ msgstr "" #, fuzzy msgid "" ":c:func:`!Py_SetPath` now sets :data:`sys.executable` to the program full " -"path (:c:func:`Py_GetProgramFullPath`) rather than to the program name (:c:" -"func:`Py_GetProgramName`). (Contributed by Victor Stinner in :issue:`38234`.)" +"path (:c:func:`Py_GetProgramFullPath`) rather than to the program name " +"(:c:func:`Py_GetProgramName`). (Contributed by Victor Stinner " +"in :issue:`38234`.)" msgstr "" -":c:func:`Py_SetPath` artık :data:`sys.executable` 'ı program adına (:c:func:" -"`Py_GetProgramName`) yerine programın tam yoluna (:c:func:" -"`Py_GetProgramFullPath`) ayarlıyor. (Victor Stinner'ın :issue:`38234` 'teki " -"katkısıyla.)" +":c:func:`Py_SetPath` artık :data:`sys.executable` 'ı program adına " +"(:c:func:`Py_GetProgramName`) yerine programın tam yoluna " +"(:c:func:`Py_GetProgramFullPath`) ayarlıyor. (Victor " +"Stinner'ın :issue:`38234` 'teki katkısıyla.)" #: whatsnew/3.8.rst:1638 msgid "Deprecated" @@ -3198,45 +3225,47 @@ msgstr "Kullanımdan kaldırıldı" #: whatsnew/3.8.rst:1640 msgid "" "The distutils ``bdist_wininst`` command is now deprecated, use " -"``bdist_wheel`` (wheel packages) instead. (Contributed by Victor Stinner in :" -"issue:`37481`.)" +"``bdist_wheel`` (wheel packages) instead. (Contributed by Victor Stinner " +"in :issue:`37481`.)" msgstr "" "Distutils ``bdist_wininst`` komutu artık kullanımdan kaldırılmıştır, bunun " -"yerine ``bdist_wheel`` (tekerlek paketleri) kullanın. (Victor Stinner'ın :" -"issue:`37481` 'deki katkısıyla.)" +"yerine ``bdist_wheel`` (tekerlek paketleri) kullanın. (Victor " +"Stinner'ın :issue:`37481` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1644 msgid "" -"Deprecated methods ``getchildren()`` and ``getiterator()`` in the :mod:`~xml." -"etree.ElementTree` module now emit a :exc:`DeprecationWarning` instead of :" -"exc:`PendingDeprecationWarning`. They will be removed in Python 3.9. " -"(Contributed by Serhiy Storchaka in :issue:`29209`.)" +"Deprecated methods ``getchildren()`` and ``getiterator()`` in " +"the :mod:`~xml.etree.ElementTree` module now emit " +"a :exc:`DeprecationWarning` instead of :exc:`PendingDeprecationWarning`. " +"They will be removed in Python 3.9. (Contributed by Serhiy Storchaka " +"in :issue:`29209`.)" msgstr "" ":mod:`~xml.etree.ElementTree` modülündeki kullanımdan kaldırılan " -"``getchildren()`` ve ``getiterator()`` yöntemleri artık :exc:" -"`PendingDeprecationWarning` yerine bir :exc:`DeprecationWarning` yayıyor. " -"Python 3.9'da kaldırılacaklar. (Serhiy Storchaka'nın :issue:`29209` 'daki " -"katkısıyla.)" +"``getchildren()`` ve ``getiterator()`` yöntemleri " +"artık :exc:`PendingDeprecationWarning` yerine bir :exc:`DeprecationWarning` " +"yayıyor. Python 3.9'da kaldırılacaklar. (Serhiy Storchaka'nın :issue:`29209` " +"'daki katkısıyla.)" #: whatsnew/3.8.rst:1650 msgid "" -"Passing an object that is not an instance of :class:`concurrent.futures." -"ThreadPoolExecutor` to :meth:`loop.set_default_executor() ` is deprecated and will be prohibited in Python 3.9. " -"(Contributed by Elvis Pranskevichus in :issue:`34075`.)" +"Passing an object that is not an instance " +"of :class:`concurrent.futures.ThreadPoolExecutor` " +"to :meth:`loop.set_default_executor() ` " +"is deprecated and will be prohibited in Python 3.9. (Contributed by Elvis " +"Pranskevichus in :issue:`34075`.)" msgstr "" "Bir :class:`concurrent.futures.ThreadPoolExecutor` örneği olmayan bir " -"nesneyi :meth:`loop.set_default_executor() ` 'a geçirmek kullanımdan kaldırılmıştır ve Python " -"3.9'da yasaklanacaktır. (Elvis Pranskevichus'un :issue:`34075` 'teki " -"katkısıyla.)" +"nesneyi :meth:`loop.set_default_executor() " +"` 'a geçirmek kullanımdan kaldırılmıştır " +"ve Python 3.9'da yasaklanacaktır. (Elvis Pranskevichus'un :issue:`34075` " +"'teki katkısıyla.)" #: whatsnew/3.8.rst:1656 #, fuzzy msgid "" -"The :meth:`~object.__getitem__` methods of :class:`xml.dom.pulldom." -"DOMEventStream`, :class:`wsgiref.util.FileWrapper` and :class:`fileinput." -"FileInput` have been deprecated." +"The :meth:`~object.__getitem__` methods " +"of :class:`xml.dom.pulldom.DOMEventStream`, :class:`wsgiref.util.FileWrapper` " +"and :class:`fileinput.FileInput` have been deprecated." msgstr "" ":class:`xml.dom.pulldom.DOMEventStream`, :class:`wsgiref.util.FileWrapper` " "ve :class:`fileinput.FileInput` metotlarının :meth:`__getitem__` metotları " @@ -3245,8 +3274,8 @@ msgstr "" #: whatsnew/3.8.rst:1660 msgid "" "Implementations of these methods have been ignoring their *index* parameter, " -"and returning the next item instead. (Contributed by Berker Peksag in :issue:" -"`9372`.)" +"and returning the next item instead. (Contributed by Berker Peksag " +"in :issue:`9372`.)" msgstr "" "Bu yöntemlerin uygulamaları *index* parametresini yok saymakta ve bunun " "yerine bir sonraki öğeyi döndürmektedir. (Berker Peksag'ın :issue:`9372` " @@ -3278,46 +3307,40 @@ msgstr "" msgid "" ":class:`ast.NodeVisitor` methods ``visit_Num()``, ``visit_Str()``, " "``visit_Bytes()``, ``visit_NameConstant()`` and ``visit_Ellipsis()`` are " -"deprecated now and will not be called in future Python versions. Add the :" -"meth:`~ast.NodeVisitor.visit_Constant` method to handle all constant nodes. " -"(Contributed by Serhiy Storchaka in :issue:`36917`.)" +"deprecated now and will not be called in future Python versions. Add " +"the :meth:`~ast.NodeVisitor.visit_Constant` method to handle all constant " +"nodes. (Contributed by Serhiy Storchaka in :issue:`36917`.)" msgstr "" ":class:`ast.NodeVisitor` metotları ``visit_Num()``, ``visit_Str()``, " "``visit_Bytes()``, ``visit_NameConstant()`` ve ``visit_Ellipsis()`` artık " "kullanımdan kaldırılmıştır ve gelecekteki Python sürümlerinde " -"çağrılmayacaktır. Tüm sabit düğümleri işlemek için :meth:`~ast.NodeVisitor." -"visit_Constant` yöntemini ekleyin. (Serhiy Storchaka'nın :issue:`36917` " -"'deki katkısıyla.)" +"çağrılmayacaktır. Tüm sabit düğümleri işlemek " +"için :meth:`~ast.NodeVisitor.visit_Constant` yöntemini ekleyin. (Serhiy " +"Storchaka'nın :issue:`36917` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1680 msgid "" "The :func:`asyncio.coroutine` :term:`decorator` is deprecated and will be " -"removed in version 3.10. Instead of ``@asyncio.coroutine``, use :keyword:" -"`async def` instead. (Contributed by Andrew Svetlov in :issue:`36921`.)" +"removed in version 3.10. Instead of ``@asyncio.coroutine``, " +"use :keyword:`async def` instead. (Contributed by Andrew Svetlov " +"in :issue:`36921`.)" msgstr "" ":func:`asyncio.coroutine` :term:`decorator` kullanımdan kaldırılmıştır ve " -"3.10 sürümünde kaldırılacaktır. ``@asyncio.coroutine`` yerine :keyword:" -"`async def` kullanın. (Andrew Svetlov'un :issue:`36921` 'deki katkısıyla.)" +"3.10 sürümünde kaldırılacaktır. ``@asyncio.coroutine`` " +"yerine :keyword:`async def` kullanın. (Andrew Svetlov'un :issue:`36921` " +"'deki katkısıyla.)" #: whatsnew/3.8.rst:1685 msgid "" "In :mod:`asyncio`, the explicit passing of a *loop* argument has been " -"deprecated and will be removed in version 3.10 for the following: :func:" -"`asyncio.sleep`, :func:`asyncio.gather`, :func:`asyncio.shield`, :func:" -"`asyncio.wait_for`, :func:`asyncio.wait`, :func:`asyncio.as_completed`, :" -"class:`asyncio.Task`, :class:`asyncio.Lock`, :class:`asyncio.Event`, :class:" -"`asyncio.Condition`, :class:`asyncio.Semaphore`, :class:`asyncio." -"BoundedSemaphore`, :class:`asyncio.Queue`, :func:`asyncio." -"create_subprocess_exec`, and :func:`asyncio.create_subprocess_shell`." +"deprecated and will be removed in version 3.10 for the " +"following: :func:`asyncio.sleep`, :func:`asyncio.gather`, :func:`asyncio.shield`, :func:`asyncio.wait_for`, :func:`asyncio.wait`, :func:`asyncio.as_completed`, :class:`asyncio.Task`, :class:`asyncio.Lock`, :class:`asyncio.Event`, :class:`asyncio.Condition`, :class:`asyncio.Semaphore`, :class:`asyncio.BoundedSemaphore`, :class:`asyncio.Queue`, :func:`asyncio.create_subprocess_exec`, " +"and :func:`asyncio.create_subprocess_shell`." msgstr "" ":mod:`asyncio` içinde, bir *loop* argümanının açıkça geçilmesi kullanımdan " -"kaldırılmıştır ve 3.10 sürümünde aşağıdakiler için kaldırılacaktır: :func:" -"`asyncio.sleep`, :func:`asyncio.gather`, :func:`asyncio.shield`, :func:" -"`asyncio.wait_for`, :func:`asyncio.wait`, :func:`asyncio.as_completed`, :" -"class:`asyncio.Task`, :class:`asyncio.Lock`, :class:`asyncio.Event`, :class:" -"`asyncio.Condition`, :class:`asyncio.Semaphore`, :class:`asyncio." -"BoundedSemaphore`, :class:`asyncio.Queue`, :func:`asyncio." -"create_subprocess_exec`, ve :func:`asyncio.create_subprocess_shell`." +"kaldırılmıştır ve 3.10 sürümünde aşağıdakiler için " +"kaldırılacaktır: :func:`asyncio.sleep`, :func:`asyncio.gather`, :func:`asyncio.shield`, :func:`asyncio.wait_for`, :func:`asyncio.wait`, :func:`asyncio.as_completed`, :class:`asyncio.Task`, :class:`asyncio.Lock`, :class:`asyncio.Event`, :class:`asyncio.Condition`, :class:`asyncio.Semaphore`, :class:`asyncio.BoundedSemaphore`, :class:`asyncio.Queue`, :func:`asyncio.create_subprocess_exec`, " +"ve :func:`asyncio.create_subprocess_shell`." #: whatsnew/3.8.rst:1695 msgid "" @@ -3332,36 +3355,37 @@ msgstr "" #: whatsnew/3.8.rst:1699 msgid "" "The following functions and methods are deprecated in the :mod:`gettext` " -"module: :func:`~gettext.lgettext`, :func:`~gettext.ldgettext`, :func:" -"`~gettext.lngettext` and :func:`~gettext.ldngettext`. They return encoded " -"bytes, and it's possible that you will get unexpected Unicode-related " -"exceptions if there are encoding problems with the translated strings. It's " -"much better to use alternatives which return Unicode strings in Python 3. " -"These functions have been broken for a long time." +"module: :func:`~gettext.lgettext`, :func:`~gettext.ldgettext`, :func:`~gettext.lngettext` " +"and :func:`~gettext.ldngettext`. They return encoded bytes, and it's " +"possible that you will get unexpected Unicode-related exceptions if there " +"are encoding problems with the translated strings. It's much better to use " +"alternatives which return Unicode strings in Python 3. These functions have " +"been broken for a long time." msgstr "" "Aşağıdaki fonksiyonlar ve yöntemler :mod:`gettext` modülünde kullanımdan " -"kaldırılmıştır: :func:`~gettext.lgettext`, :func:`~gettext.ldgettext`, :func:" -"`~gettext.lngettext` ve :func:`~gettext.ldngettext`. Bunlar kodlanmış " -"baytlar döndürür ve çevrilen dizelerde kodlama sorunları varsa Unicode ile " -"ilgili beklenmedik istisnalar almanız olasıdır. Python 3'te Unicode " -"dizgileri döndüren alternatifleri kullanmak çok daha iyidir. Bu fonksiyonlar " -"uzun süredir bozuk." +"kaldırılmıştır: :func:`~gettext.lgettext`, :func:`~gettext.ldgettext`, :func:`~gettext.lngettext` " +"ve :func:`~gettext.ldngettext`. Bunlar kodlanmış baytlar döndürür ve " +"çevrilen dizelerde kodlama sorunları varsa Unicode ile ilgili beklenmedik " +"istisnalar almanız olasıdır. Python 3'te Unicode dizgileri döndüren " +"alternatifleri kullanmak çok daha iyidir. Bu fonksiyonlar uzun süredir bozuk." #: whatsnew/3.8.rst:1707 msgid "" -"Function :func:`~gettext.bind_textdomain_codeset`, methods :meth:`~gettext." -"NullTranslations.output_charset` and :meth:`~gettext.NullTranslations." -"set_output_charset`, and the *codeset* parameter of functions :func:" -"`~gettext.translation` and :func:`~gettext.install` are also deprecated, " -"since they are only used for the ``l*gettext()`` functions. (Contributed by " -"Serhiy Storchaka in :issue:`33710`.)" -msgstr "" -":func:`~gettext.bind_textdomain_codeset` fonksiyonu, :meth:`~gettext." -"NullTranslations.output_charset` ve :meth:`~gettext.NullTranslations." -"set_output_charset` yöntemleri ve :func:`~gettext.translation` ve :func:" -"`~gettext.install` fonksiyonlarının *codeset* parametresi de yalnızca " -"``l*gettext()`` fonksiyonları için kullanıldığından kullanımdan " -"kaldırılmıştır. (Serhiy Storchaka'nın :issue:`33710` 'daki katkısıyla.)" +"Function :func:`~gettext.bind_textdomain_codeset`, " +"methods :meth:`~gettext.NullTranslations.output_charset` " +"and :meth:`~gettext.NullTranslations.set_output_charset`, and the *codeset* " +"parameter of functions :func:`~gettext.translation` " +"and :func:`~gettext.install` are also deprecated, since they are only used " +"for the ``l*gettext()`` functions. (Contributed by Serhiy Storchaka " +"in :issue:`33710`.)" +msgstr "" +":func:`~gettext.bind_textdomain_codeset` " +"fonksiyonu, :meth:`~gettext.NullTranslations.output_charset` " +"ve :meth:`~gettext.NullTranslations.set_output_charset` yöntemleri " +"ve :func:`~gettext.translation` ve :func:`~gettext.install` fonksiyonlarının " +"*codeset* parametresi de yalnızca ``l*gettext()`` fonksiyonları için " +"kullanıldığından kullanımdan kaldırılmıştır. (Serhiy " +"Storchaka'nın :issue:`33710` 'daki katkısıyla.)" #: whatsnew/3.8.rst:1715 #, fuzzy @@ -3376,19 +3400,20 @@ msgstr "" #: whatsnew/3.8.rst:1719 msgid "" "Many builtin and extension functions that take integer arguments will now " -"emit a deprecation warning for :class:`~decimal.Decimal`\\ s, :class:" -"`~fractions.Fraction`\\ s and any other objects that can be converted to " -"integers only with a loss (e.g. that have the :meth:`~object.__int__` method " -"but do not have the :meth:`~object.__index__` method). In future version " -"they will be errors. (Contributed by Serhiy Storchaka in :issue:`36048`.)" -msgstr "" -"Tamsayı argümanları alan birçok yerleşik ve uzantı fonksiyonu artık :class:" -"`~decimal.Decimal`, :class:`~fractions.Fraction` ve yalnızca bir kayıpla " -"tamsayılara dönüştürülebilen diğer nesneler (örneğin :meth:`~object.__int__` " -"yöntemine sahip olan ancak :meth:`~object.__index__` yöntemine sahip " -"olmayan) için bir kullanımdan kaldırma uyarısı verecektir. Gelecek sürümde " -"bunlar hata olacaktır. (Serhiy Storchaka'nın :issue:`36048` 'deki " -"katkısıyla.)" +"emit a deprecation warning for :class:`~decimal.Decimal`\\ " +"s, :class:`~fractions.Fraction`\\ s and any other objects that can be " +"converted to integers only with a loss (e.g. that have " +"the :meth:`~object.__int__` method but do not have " +"the :meth:`~object.__index__` method). In future version they will be " +"errors. (Contributed by Serhiy Storchaka in :issue:`36048`.)" +msgstr "" +"Tamsayı argümanları alan birçok yerleşik ve uzantı fonksiyonu " +"artık :class:`~decimal.Decimal`, :class:`~fractions.Fraction` ve yalnızca " +"bir kayıpla tamsayılara dönüştürülebilen diğer nesneler " +"(örneğin :meth:`~object.__int__` yöntemine sahip olan " +"ancak :meth:`~object.__index__` yöntemine sahip olmayan) için bir " +"kullanımdan kaldırma uyarısı verecektir. Gelecek sürümde bunlar hata " +"olacaktır. (Serhiy Storchaka'nın :issue:`36048` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1727 msgid "Deprecated passing the following arguments as keyword arguments:" @@ -3398,13 +3423,13 @@ msgstr "" #: whatsnew/3.8.rst:1729 msgid "" -"*func* in :func:`functools.partialmethod`, :func:`weakref.finalize`, :meth:" -"`profile.Profile.runcall`, :meth:`cProfile.Profile.runcall`, :meth:`bdb.Bdb." -"runcall`, :meth:`trace.Trace.runfunc` and :func:`curses.wrapper`." +"*func* " +"in :func:`functools.partialmethod`, :func:`weakref.finalize`, :meth:`profile.Profile.runcall`, :meth:`cProfile.Profile.runcall`, :meth:`bdb.Bdb.runcall`, :meth:`trace.Trace.runfunc` " +"and :func:`curses.wrapper`." msgstr "" -"*func* in :func:`functools.partialmethod`, :func:`weakref.finalize`, :meth:" -"`profile.Profile.runcall`, :meth:`cProfile.Profile.runcall`, :meth:`bdb.Bdb." -"runcall`, :meth:`trace.Trace.runfunc` and :func:`curses.wrapper`." +"*func* " +"in :func:`functools.partialmethod`, :func:`weakref.finalize`, :meth:`profile.Profile.runcall`, :meth:`cProfile.Profile.runcall`, :meth:`bdb.Bdb.runcall`, :meth:`trace.Trace.runfunc` " +"and :func:`curses.wrapper`." #: whatsnew/3.8.rst:1733 msgid "*function* in :meth:`unittest.TestCase.addCleanup`." @@ -3412,33 +3437,33 @@ msgstr ":meth:`unittest.TestCase.addCleanup` içindeki *fonksiyon*." #: whatsnew/3.8.rst:1734 msgid "" -"*fn* in the :meth:`~concurrent.futures.Executor.submit` method of :class:" -"`concurrent.futures.ThreadPoolExecutor` and :class:`concurrent.futures." -"ProcessPoolExecutor`." +"*fn* in the :meth:`~concurrent.futures.Executor.submit` method " +"of :class:`concurrent.futures.ThreadPoolExecutor` " +"and :class:`concurrent.futures.ProcessPoolExecutor`." msgstr "" -"*fn* içinde :meth:`~concurrent.futures.Executor.submit` yöntemi :class:" -"`concurrent.futures.ThreadPoolExecutor` ve :class:`concurrent.futures." -"ProcessPoolExecutor`." +"*fn* içinde :meth:`~concurrent.futures.Executor.submit` " +"yöntemi :class:`concurrent.futures.ThreadPoolExecutor` " +"ve :class:`concurrent.futures.ProcessPoolExecutor`." #: whatsnew/3.8.rst:1737 msgid "" -"*callback* in :meth:`contextlib.ExitStack.callback`, :meth:`contextlib." -"AsyncExitStack.callback` and :meth:`contextlib.AsyncExitStack." -"push_async_callback`." +"*callback* " +"in :meth:`contextlib.ExitStack.callback`, :meth:`contextlib.AsyncExitStack.callback` " +"and :meth:`contextlib.AsyncExitStack.push_async_callback`." msgstr "" -":meth:`contextlib.ExitStack.callback`, :meth:`contextlib.AsyncExitStack." -"callback` ve :meth:`contextlib.AsyncExitStack.push_async_callback` içinde " -"*geri arama*." +":meth:`contextlib.ExitStack.callback`, :meth:`contextlib.AsyncExitStack.callback` " +"ve :meth:`contextlib.AsyncExitStack.push_async_callback` içinde *geri arama*." #: whatsnew/3.8.rst:1740 msgid "" "*c* and *typeid* in the :meth:`~multiprocessing.managers.Server.create` " -"method of :class:`multiprocessing.managers.Server` and :class:" -"`multiprocessing.managers.SharedMemoryServer`." +"method of :class:`multiprocessing.managers.Server` " +"and :class:`multiprocessing.managers.SharedMemoryServer`." msgstr "" -"*c* ve *typeid* öğeleri :class:`multiprocessing.managers.Server` ve :class:" -"`multiprocessing.managers.SharedMemoryServer` öğelerinin :meth:" -"`~multiprocessing.managers.Server.create` yönteminde yer alır." +"*c* ve *typeid* öğeleri :class:`multiprocessing.managers.Server` " +"ve :class:`multiprocessing.managers.SharedMemoryServer` " +"öğelerinin :meth:`~multiprocessing.managers.Server.create` yönteminde yer " +"alır." #: whatsnew/3.8.rst:1743 msgid "*obj* in :func:`weakref.finalize`." @@ -3489,21 +3514,22 @@ msgid "" "Victor Stinner in :issue:`35345`.)" msgstr "" "Python 3.3'ten beri kullanımda olmayan :func:`platform.popen` fonksiyonu " -"kaldırıldı: bunun yerine :func:`os.popen` kullanın. (Victor Stinner'ın :" -"issue:`35345` 'teki katkısıyla.)" +"kaldırıldı: bunun yerine :func:`os.popen` kullanın. (Victor " +"Stinner'ın :issue:`35345` 'teki katkısıyla.)" #: whatsnew/3.8.rst:1767 msgid "" "The function :func:`time.clock` has been removed, after having been " -"deprecated since Python 3.3: use :func:`time.perf_counter` or :func:`time." -"process_time` instead, depending on your requirements, to have well-defined " -"behavior. (Contributed by Matthias Bussonnier in :issue:`36895`.)" +"deprecated since Python 3.3: use :func:`time.perf_counter` " +"or :func:`time.process_time` instead, depending on your requirements, to " +"have well-defined behavior. (Contributed by Matthias Bussonnier " +"in :issue:`36895`.)" msgstr "" "Python 3.3'ten beri kullanımdan kaldırılan :func:`time.clock` fonksiyonu " "kaldırıldı: iyi tanımlanmış davranışa sahip olmak için gereksinimlerinize " -"bağlı olarak bunun yerine :func:`time.perf_counter` veya :func:`time." -"process_time` kullanın. (Matthias Bussonnier'ın :issue:`36895` 'teki " -"katkısıyla.)" +"bağlı olarak bunun yerine :func:`time.perf_counter` " +"veya :func:`time.process_time` kullanın. (Matthias " +"Bussonnier'ın :issue:`36895` 'teki katkısıyla.)" #: whatsnew/3.8.rst:1773 msgid "" @@ -3550,16 +3576,17 @@ msgstr "" #: whatsnew/3.8.rst:1789 msgid "" -"Removed the ``doctype()`` method of :class:`~xml.etree.ElementTree." -"XMLParser`. (Contributed by Serhiy Storchaka in :issue:`29209`.)" +"Removed the ``doctype()`` method " +"of :class:`~xml.etree.ElementTree.XMLParser`. (Contributed by Serhiy " +"Storchaka in :issue:`29209`.)" msgstr "" ":class:`~xml.etree.ElementTree.XMLParser` metodunun ``doctype()`` metodu " "kaldırıldı. (Serhiy Storchaka'nın :issue:`29209` 'daki katkısıyla.)" #: whatsnew/3.8.rst:1792 msgid "" -"\"unicode_internal\" codec is removed. (Contributed by Inada Naoki in :issue:" -"`36297`.)" +"\"unicode_internal\" codec is removed. (Contributed by Inada Naoki " +"in :issue:`36297`.)" msgstr "" "\"unicode_internal\" codec'i kaldırıldı. (Inada Naoki'nin :issue:`36297` " "'deki katkısıyla.)" @@ -3574,23 +3601,25 @@ msgstr "" #: whatsnew/3.8.rst:1799 msgid "" -"The ``bufsize`` keyword argument of :func:`fileinput.input` and :func:" -"`fileinput.FileInput` which was ignored and deprecated since Python 3.6 has " -"been removed. :issue:`36952` (Contributed by Matthias Bussonnier.)" +"The ``bufsize`` keyword argument of :func:`fileinput.input` " +"and :func:`fileinput.FileInput` which was ignored and deprecated since " +"Python 3.6 has been removed. :issue:`36952` (Contributed by Matthias " +"Bussonnier.)" msgstr "" -"Python 3.6'dan beri göz ardı edilen ve kullanımdan kaldırılan :func:" -"`fileinput.input` ve :func:`fileinput.FileInput` anahtar kelime argümanı " -"``bufsize`` kaldırıldı. :issue:`36952` (Matthias Bussonnier'ın katkısıyla.)" +"Python 3.6'dan beri göz ardı edilen ve kullanımdan " +"kaldırılan :func:`fileinput.input` ve :func:`fileinput.FileInput` anahtar " +"kelime argümanı ``bufsize`` kaldırıldı. :issue:`36952` (Matthias " +"Bussonnier'ın katkısıyla.)" #: whatsnew/3.8.rst:1803 msgid "" -"The functions :func:`sys.set_coroutine_wrapper` and :func:`sys." -"get_coroutine_wrapper` deprecated in Python 3.7 have been removed; :issue:" -"`36933` (Contributed by Matthias Bussonnier.)" +"The functions :func:`sys.set_coroutine_wrapper` " +"and :func:`sys.get_coroutine_wrapper` deprecated in Python 3.7 have been " +"removed; :issue:`36933` (Contributed by Matthias Bussonnier.)" msgstr "" -"Python 3.7'de kullanımdan kaldırılan :func:`sys.set_coroutine_wrapper` ve :" -"func:`sys.get_coroutine_wrapper` fonksiyonları kaldırıldı; :issue:`36933` " -"(Matthias Bussonnier'ın katkısıyla.)" +"Python 3.7'de kullanımdan kaldırılan :func:`sys.set_coroutine_wrapper` " +"ve :func:`sys.get_coroutine_wrapper` fonksiyonları " +"kaldırıldı; :issue:`36933` (Matthias Bussonnier'ın katkısıyla.)" #: whatsnew/3.8.rst:1809 msgid "Porting to Python 3.8" @@ -3626,15 +3655,16 @@ msgid "" "(``is`` and ``is not``) are used with certain types of literals (e.g. " "strings, numbers). These can often work by accident in CPython, but are not " "guaranteed by the language spec. The warning advises users to use equality " -"tests (``==`` and ``!=``) instead. (Contributed by Serhiy Storchaka in :" -"issue:`34850`.)" +"tests (``==`` and ``!=``) instead. (Contributed by Serhiy Storchaka " +"in :issue:`34850`.)" msgstr "" "Derleyici artık kimlik kontrolleri (``is`` ve ``is not``) belirli türdeki " -"değişmezlerle (örneğin dizeler, sayılar) kullanıldığında bir :exc:" -"`SyntaxWarning` üretiyor. Bunlar CPython'da genellikle kazara çalışabilir, " -"ancak dil özellikleri tarafından garanti edilmez. Uyarı, kullanıcılara " -"bunun yerine eşitlik testlerini (``==`` ve ``!=``) kullanmalarını önerir. " -"(Serhiy Storchaka'nın :issue:`34850` 'deki katkısıyla.)" +"değişmezlerle (örneğin dizeler, sayılar) kullanıldığında " +"bir :exc:`SyntaxWarning` üretiyor. Bunlar CPython'da genellikle kazara " +"çalışabilir, ancak dil özellikleri tarafından garanti edilmez. Uyarı, " +"kullanıcılara bunun yerine eşitlik testlerini (``==`` ve ``!=``) " +"kullanmalarını önerir. (Serhiy Storchaka'nın :issue:`34850` 'deki " +"katkısıyla.)" #: whatsnew/3.8.rst:1830 msgid "" @@ -3650,12 +3680,12 @@ msgstr "" #: whatsnew/3.8.rst:1835 msgid "" -"Removed ``__str__`` implementations from builtin types :class:`bool`, :class:" -"`int`, :class:`float`, :class:`complex` and few classes from the standard " -"library. They now inherit ``__str__()`` from :class:`object`. As result, " -"defining the ``__repr__()`` method in the subclass of these classes will " -"affect their string representation. (Contributed by Serhiy Storchaka in :" -"issue:`36793`.)" +"Removed ``__str__`` implementations from builtin " +"types :class:`bool`, :class:`int`, :class:`float`, :class:`complex` and few " +"classes from the standard library. They now inherit ``__str__()`` " +"from :class:`object`. As result, defining the ``__repr__()`` method in the " +"subclass of these classes will affect their string representation. " +"(Contributed by Serhiy Storchaka in :issue:`36793`.)" msgstr "" ":class:`bool`, :class:`int`, :class:`float`, :class:`complex` yerleşik " "türlerinden ve standart kütüphanedeki birkaç sınıftan ``__str__`` " @@ -3670,24 +3700,25 @@ msgid "" "On AIX, :data:`sys.platform` doesn't contain the major version anymore. It " "is always ``'aix'``, instead of ``'aix3'`` .. ``'aix7'``. Since older " "Python versions include the version number, so it is recommended to always " -"use ``sys.platform.startswith('aix')``. (Contributed by M. Felt in :issue:" -"`36588`.)" +"use ``sys.platform.startswith('aix')``. (Contributed by M. Felt " +"in :issue:`36588`.)" msgstr "" "AIX üzerinde, :attr:`sys.platform` artık ana sürümü içermemektedir. Bu her " "zaman ``'aix3'`` ... ``'aix7'`` yerine ``'aix'`` şeklindedir. Eski Python " -"sürümleri sürüm numarasını içerdiğinden, her zaman ``sys.platform." -"startswith('aix')`` kullanılması önerilir. (M. Felt'in :issue:`36588` 'deki " -"katkısıyla.)" +"sürümleri sürüm numarasını içerdiğinden, her zaman " +"``sys.platform.startswith('aix')`` kullanılması önerilir. (M. " +"Felt'in :issue:`36588` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1848 #, fuzzy msgid "" ":c:func:`!PyEval_AcquireLock` and :c:func:`!PyEval_AcquireThread` now " "terminate the current thread if called while the interpreter is finalizing, " -"making them consistent with :c:func:`PyEval_RestoreThread`, :c:func:" -"`Py_END_ALLOW_THREADS`, and :c:func:`PyGILState_Ensure`. If this behavior is " -"not desired, guard the call by checking :c:func:`!_Py_IsFinalizing` or :func:" -"`sys.is_finalizing`. (Contributed by Joannah Nanjekye in :issue:`36475`.)" +"making them consistent " +"with :c:func:`PyEval_RestoreThread`, :c:func:`Py_END_ALLOW_THREADS`, " +"and :c:func:`PyGILState_Ensure`. If this behavior is not desired, guard the " +"call by checking :c:func:`!_Py_IsFinalizing` or :func:`sys.is_finalizing`. " +"(Contributed by Joannah Nanjekye in :issue:`36475`.)" msgstr "" ":c:func:`PyEval_AcquireLock` ve :c:func:`PyEval_AcquireThread` artık " "yorumlayıcı sonlandırılırken çağrılırsa geçerli iş parçacığını " @@ -3722,20 +3753,20 @@ msgid "" "child process fails with a non-zero :attr:`~Popen.returncode`. (Contributed " "by Joannah Nanjekye and Victor Stinner in :issue:`35537`.)" msgstr "" -":class:`subprocess.Popen` artık daha iyi performans için bazı durumlarda :" -"func:`os.posix_spawn` kullanabilir. Linux ve QEMU Kullanıcı Emülasyonu için " -"Windows Alt Sisteminde, :func:`os.posix_spawn` kullanan :class:`Popen` " -"kurucusu artık \"eksik program\" gibi hatalarda bir istisna oluşturmuyor. " -"Bunun yerine alt süreç sıfır olmayan bir :attr:`~Popen.returncode` ile " -"başarısız olur. (Joannah Nanjekye ve Victor Stinner'ın :issue:`35537` 'deki " -"katkılarıyla.)" +":class:`subprocess.Popen` artık daha iyi performans için bazı " +"durumlarda :func:`os.posix_spawn` kullanabilir. Linux ve QEMU Kullanıcı " +"Emülasyonu için Windows Alt Sisteminde, :func:`os.posix_spawn` " +"kullanan :class:`Popen` kurucusu artık \"eksik program\" gibi hatalarda bir " +"istisna oluşturmuyor. Bunun yerine alt süreç sıfır olmayan " +"bir :attr:`~Popen.returncode` ile başarısız olur. (Joannah Nanjekye ve " +"Victor Stinner'ın :issue:`35537` 'deki katkılarıyla.)" #: whatsnew/3.8.rst:1872 msgid "" "The *preexec_fn* argument of * :class:`subprocess.Popen` is no longer " "compatible with subinterpreters. The use of the parameter in a " -"subinterpreter now raises :exc:`RuntimeError`. (Contributed by Eric Snow in :" -"issue:`34651`, modified by Christian Heimes in :issue:`37951`.)" +"subinterpreter now raises :exc:`RuntimeError`. (Contributed by Eric Snow " +"in :issue:`34651`, modified by Christian Heimes in :issue:`37951`.)" msgstr "" ":class:`subprocess.Popen` parametresinin *preexec_fn* argümanı artık alt " "yorumlayıcılarla uyumlu değildir. Parametrenin bir alt yorumlayıcıda " @@ -3763,67 +3794,70 @@ msgstr "" #: whatsnew/3.8.rst:1891 msgid "" -"The :meth:`~tkinter.ttk.Treeview.selection` method of the :class:`tkinter." -"ttk.Treeview` class no longer takes arguments. Using it with arguments for " -"changing the selection was deprecated in Python 3.6. Use specialized " -"methods like :meth:`~tkinter.ttk.Treeview.selection_set` for changing the " -"selection. (Contributed by Serhiy Storchaka in :issue:`31508`.)" +"The :meth:`~tkinter.ttk.Treeview.selection` method of " +"the :class:`tkinter.ttk.Treeview` class no longer takes arguments. Using it " +"with arguments for changing the selection was deprecated in Python 3.6. Use " +"specialized methods like :meth:`~tkinter.ttk.Treeview.selection_set` for " +"changing the selection. (Contributed by Serhiy Storchaka in :issue:`31508`.)" msgstr "" -":class:`tkinter.ttk.Treeview` sınıfının :meth:`~tkinter.ttk.Treeview." -"selection` yöntemi artık argüman almıyor. Seçimi değiştirmek için " -"argümanlarla kullanılması Python 3.6'da kullanımdan kaldırılmıştır. Seçimi " -"değiştirmek için :meth:`~tkinter.ttk.Treeview.selection_set` gibi özel " -"yöntemler kullanın. (Serhiy Storchaka'ın :issue:`31508` 'deki katkısıyla.)" +":class:`tkinter.ttk.Treeview` " +"sınıfının :meth:`~tkinter.ttk.Treeview.selection` yöntemi artık argüman " +"almıyor. Seçimi değiştirmek için argümanlarla kullanılması Python 3.6'da " +"kullanımdan kaldırılmıştır. Seçimi değiştirmek " +"için :meth:`~tkinter.ttk.Treeview.selection_set` gibi özel yöntemler " +"kullanın. (Serhiy Storchaka'ın :issue:`31508` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1897 msgid "" -"The :meth:`writexml`, :meth:`toxml` and :meth:`toprettyxml` methods of :mod:" -"`xml.dom.minidom`, and the :meth:`write` method of :mod:`xml.etree`, now " -"preserve the attribute order specified by the user. (Contributed by Diego " -"Rojas and Raymond Hettinger in :issue:`34160`.)" +"The :meth:`writexml`, :meth:`toxml` and :meth:`toprettyxml` methods " +"of :mod:`xml.dom.minidom`, and the :meth:`write` method of :mod:`xml.etree`, " +"now preserve the attribute order specified by the user. (Contributed by " +"Diego Rojas and Raymond Hettinger in :issue:`34160`.)" msgstr "" -":mod:`xml.dom.minidom` metodunun :meth:`writexml`, :meth:`toxml` ve :meth:" -"`toprettyxml` metotları ve :mod:`xml.etree` metodunun :meth:`write` metodu " -"artık kullanıcı tarafından belirtilen öznitelik sırasını korumaktadır. " -"(Diego Rojas ve Raymond Hettinger'ın :issue:`34160` 'daki katkılarıyla.)" +":mod:`xml.dom.minidom` metodunun :meth:`writexml`, :meth:`toxml` " +"ve :meth:`toprettyxml` metotları ve :mod:`xml.etree` metodunun :meth:`write` " +"metodu artık kullanıcı tarafından belirtilen öznitelik sırasını " +"korumaktadır. (Diego Rojas ve Raymond Hettinger'ın :issue:`34160` 'daki " +"katkılarıyla.)" #: whatsnew/3.8.rst:1902 msgid "" -"A :mod:`dbm.dumb` database opened with flags ``'r'`` is now read-only. :func:" -"`dbm.dumb.open` with flags ``'r'`` and ``'w'`` no longer creates a database " -"if it does not exist. (Contributed by Serhiy Storchaka in :issue:`32749`.)" +"A :mod:`dbm.dumb` database opened with flags ``'r'`` is now read-" +"only. :func:`dbm.dumb.open` with flags ``'r'`` and ``'w'`` no longer creates " +"a database if it does not exist. (Contributed by Serhiy Storchaka " +"in :issue:`32749`.)" msgstr "" "Bir :mod:`dbm.dumb` veritabanı ``'r'`` bayraklarıyla açıldığında artık salt " "okunurdur. :func:`dbm.dumb.open`, ``'r'`` ve ``'w'`` bayraklarıyla artık " -"mevcut değilse bir veritabanı oluşturmaz. (Serhiy Storchaka'nın :issue:" -"`32749` 'daki katkısıyla.)" +"mevcut değilse bir veritabanı oluşturmaz. (Serhiy " +"Storchaka'nın :issue:`32749` 'daki katkısıyla.)" #: whatsnew/3.8.rst:1907 msgid "" -"The ``doctype()`` method defined in a subclass of :class:`~xml.etree." -"ElementTree.XMLParser` will no longer be called and will emit a :exc:" -"`RuntimeWarning` instead of a :exc:`DeprecationWarning`. Define the :meth:" -"`doctype() ` method on a target " -"for handling an XML doctype declaration. (Contributed by Serhiy Storchaka " -"in :issue:`29209`.)" +"The ``doctype()`` method defined in a subclass " +"of :class:`~xml.etree.ElementTree.XMLParser` will no longer be called and " +"will emit a :exc:`RuntimeWarning` instead of a :exc:`DeprecationWarning`. " +"Define the :meth:`doctype() ` " +"method on a target for handling an XML doctype declaration. (Contributed by " +"Serhiy Storchaka in :issue:`29209`.)" msgstr "" ":class:`~xml.etree.ElementTree.XMLParser` alt sınıfında tanımlanan " "``doctype()`` yöntemi artık çağrılmayacak ve bir :exc:`DeprecationWarning` " "yerine bir :exc:`RuntimeWarning` yayacaktır. Bir XML doctype bildirimini " -"işlemek için bir hedef üzerinde :meth:`doctype() ` yöntemini tanımlayın. (Serhiy Storchaka'nın :issue:" -"`29209` 'daki katkısıyla.)" +"işlemek için bir hedef üzerinde :meth:`doctype() " +"` yöntemini tanımlayın. (Serhiy " +"Storchaka'nın :issue:`29209` 'daki katkısıyla.)" #: whatsnew/3.8.rst:1914 msgid "" "A :exc:`RuntimeError` is now raised when the custom metaclass doesn't " -"provide the ``__classcell__`` entry in the namespace passed to ``type." -"__new__``. A :exc:`DeprecationWarning` was emitted in Python 3.6--3.7. " -"(Contributed by Serhiy Storchaka in :issue:`23722`.)" +"provide the ``__classcell__`` entry in the namespace passed to " +"``type.__new__``. A :exc:`DeprecationWarning` was emitted in Python " +"3.6--3.7. (Contributed by Serhiy Storchaka in :issue:`23722`.)" msgstr "" "Özel metaclass, ``type.__new__`` 'e aktarılan ad alanında ``__classcell__`` " -"girdisini sağlamadığında artık bir :exc:`RuntimeError` ortaya çıkıyor. Bir :" -"exc:`DeprecationWarning` Python 3.6--3.7` 'de yayınlandı (Serhiy " +"girdisini sağlamadığında artık bir :exc:`RuntimeError` ortaya çıkıyor. " +"Bir :exc:`DeprecationWarning` Python 3.6--3.7` 'de yayınlandı (Serhiy " "Storchaka'nın :issue:`23722` 'deki katkısıyla.)" #: whatsnew/3.8.rst:1919 @@ -3836,15 +3870,14 @@ msgstr "" #: whatsnew/3.8.rst:1922 msgid "" -":func:`shutil.copyfile`, :func:`shutil.copy`, :func:`shutil.copy2`, :func:" -"`shutil.copytree` and :func:`shutil.move` use platform-specific \"fast-" -"copy\" syscalls (see :ref:`shutil-platform-dependent-efficient-copy-" -"operations` section)." +":func:`shutil.copyfile`, :func:`shutil.copy`, :func:`shutil.copy2`, :func:`shutil.copytree` " +"and :func:`shutil.move` use platform-specific \"fast-copy\" syscalls " +"(see :ref:`shutil-platform-dependent-efficient-copy-operations` section)." msgstr "" -":func:`shutil.copyfile`, :func:`shutil.copy`, :func:`shutil.copy2`, :func:" -"`shutil.copytree` ve :func:`shutil.move` platforma özgü \"fast-copy\" sistem " -"çağrılarını kullanır (bkz. :ref:`shutil-platform-dependent-efficient-copy-" -"operations` bölümü)." +":func:`shutil.copyfile`, :func:`shutil.copy`, :func:`shutil.copy2`, :func:`shutil.copytree` " +"ve :func:`shutil.move` platforma özgü \"fast-copy\" sistem çağrılarını " +"kullanır (bkz. :ref:`shutil-platform-dependent-efficient-copy-operations` " +"bölümü)." #: whatsnew/3.8.rst:1927 msgid "" @@ -3911,22 +3944,24 @@ msgstr "" #: whatsnew/3.8.rst:1954 msgid "" -"Deleting a key from a read-only :mod:`dbm` database (:mod:`dbm.dumb`, :mod:" -"`dbm.gnu` or :mod:`dbm.ndbm`) raises :attr:`error` (:exc:`dbm.dumb.error`, :" -"exc:`dbm.gnu.error` or :exc:`dbm.ndbm.error`) instead of :exc:`KeyError`. " -"(Contributed by Xiang Zhang in :issue:`33106`.)" +"Deleting a key from a read-only :mod:`dbm` database " +"(:mod:`dbm.dumb`, :mod:`dbm.gnu` or :mod:`dbm.ndbm`) raises :attr:`error` " +"(:exc:`dbm.dumb.error`, :exc:`dbm.gnu.error` or :exc:`dbm.ndbm.error`) " +"instead of :exc:`KeyError`. (Contributed by Xiang Zhang in :issue:`33106`.)" msgstr "" -"Salt okunur :mod:`dbm` veritabanından bir anahtar silindiğinde (:mod:`dbm." -"dumb`, :mod:`dbm.gnu` veya :mod:`dbm.ndbm`) :exc:`KeyError` yerine :attr:" -"`error` (:exc:`dbm.dumb.error`, :exc:`dbm.gnu.error` veya :exc:`dbm.ndbm." -"error`) ortaya çıkar. (Xiang Zhang'ın :issue:`33106` 'teki katkılarıyla.)" +"Salt okunur :mod:`dbm` veritabanından bir anahtar silindiğinde " +"(:mod:`dbm.dumb`, :mod:`dbm.gnu` veya :mod:`dbm.ndbm`) :exc:`KeyError` " +"yerine :attr:`error` (:exc:`dbm.dumb.error`, :exc:`dbm.gnu.error` " +"veya :exc:`dbm.ndbm.error`) ortaya çıkar. (Xiang Zhang'ın :issue:`33106` " +"'teki katkılarıyla.)" #: whatsnew/3.8.rst:1959 msgid "" -"Simplified AST for literals. All constants will be represented as :class:" -"`ast.Constant` instances. Instantiating old classes ``Num``, ``Str``, " -"``Bytes``, ``NameConstant`` and ``Ellipsis`` will return an instance of " -"``Constant``. (Contributed by Serhiy Storchaka in :issue:`32892`.)" +"Simplified AST for literals. All constants will be represented " +"as :class:`ast.Constant` instances. Instantiating old classes ``Num``, " +"``Str``, ``Bytes``, ``NameConstant`` and ``Ellipsis`` will return an " +"instance of ``Constant``. (Contributed by Serhiy Storchaka " +"in :issue:`32892`.)" msgstr "" "Değişmezler için basitleştirilmiş AST. Tüm sabitler :class:`ast.Constant` " "örnekleri olarak temsil edilecektir. Eski ``Num``, ``Str``, ``Bytes``, " @@ -3963,15 +3998,16 @@ msgstr ":class:`asyncio.BufferedProtocol` kararlı API'ye geçiş yaptı." msgid "" "DLL dependencies for extension modules and DLLs loaded with :mod:`ctypes` on " "Windows are now resolved more securely. Only the system paths, the directory " -"containing the DLL or PYD file, and directories added with :func:`~os." -"add_dll_directory` are searched for load-time dependencies. Specifically, :" -"envvar:`PATH` and the current working directory are no longer used, and " -"modifications to these will no longer have any effect on normal DLL " -"resolution. If your application relies on these mechanisms, you should check " -"for :func:`~os.add_dll_directory` and if it exists, use it to add your DLLs " -"directory while loading your library. Note that Windows 7 users will need to " -"ensure that Windows Update KB2533623 has been installed (this is also " -"verified by the installer). (Contributed by Steve Dower in :issue:`36085`.)" +"containing the DLL or PYD file, and directories added " +"with :func:`~os.add_dll_directory` are searched for load-time dependencies. " +"Specifically, :envvar:`PATH` and the current working directory are no longer " +"used, and modifications to these will no longer have any effect on normal " +"DLL resolution. If your application relies on these mechanisms, you should " +"check for :func:`~os.add_dll_directory` and if it exists, use it to add your " +"DLLs directory while loading your library. Note that Windows 7 users will " +"need to ensure that Windows Update KB2533623 has been installed (this is " +"also verified by the installer). (Contributed by Steve Dower " +"in :issue:`36085`.)" msgstr "" "Windows üzerinde :mod:`ctypes` ile yüklenen uzantı modülleri ve DLL'ler için " "DLL bağımlılıkları artık daha güvenli bir şekilde çözümlenmektedir. Yükleme " @@ -3979,12 +4015,13 @@ msgstr "" "içeren dizin ve :func:`~os.add_dll_directory` ile eklenen dizinler aranır. " "Özellikle, :envvar:`PATH` ve geçerli çalışma dizini artık kullanılmamaktadır " "ve bunlarda yapılan değişikliklerin normal DLL çözümlemesi üzerinde herhangi " -"bir etkisi olmayacaktır. Uygulamanız bu mekanizmalara güveniyorsa, :func:" -"`~os.add_dll_directory` dosyasını kontrol etmeli ve varsa, kütüphanenizi " -"yüklerken DLL'lerinizin dizinini eklemek için kullanmalısınız. Windows 7 " -"kullanıcılarının Windows Update KB2533623'ün yüklendiğinden emin olmaları " -"gerektiğini unutmayın (bu aynı zamanda yükleyici tarafından da doğrulanır). " -"(Steve Dower'ın :issue:`36085` 'teki katkısıyla.)" +"bir etkisi olmayacaktır. Uygulamanız bu mekanizmalara " +"güveniyorsa, :func:`~os.add_dll_directory` dosyasını kontrol etmeli ve " +"varsa, kütüphanenizi yüklerken DLL'lerinizin dizinini eklemek için " +"kullanmalısınız. Windows 7 kullanıcılarının Windows Update KB2533623'ün " +"yüklendiğinden emin olmaları gerektiğini unutmayın (bu aynı zamanda " +"yükleyici tarafından da doğrulanır). (Steve Dower'ın :issue:`36085` 'teki " +"katkısıyla.)" #: whatsnew/3.8.rst:2001 msgid "" @@ -3993,8 +4030,8 @@ msgid "" "in :issue:`36623`.)" msgstr "" "Pgen ile ilgili başlık dosyaları ve fonksiyonlar, saf bir Python " -"uygulamasıyla değiştirildikten sonra kaldırılmıştır. (Pablo Galindo'nun :" -"issue:`36623` 'teki katkısıyla.)" +"uygulamasıyla değiştirildikten sonra kaldırılmıştır. (Pablo " +"Galindo'nun :issue:`36623` 'teki katkısıyla.)" #: whatsnew/3.8.rst:2005 msgid "" @@ -4034,8 +4071,8 @@ msgstr "" ":c:struct:`PyCompilerFlags` yapısı yeni bir *cf_feature_version* alanına " "sahiptir. Bu alan ``PY_MINOR_VERSION`` olarak başlatılmalıdır. Bu alan " "varsayılan olarak yok sayılır ve yalnızca *cf_flags* içinde " -"``PyCF_ONLY_AST`` bayrağı ayarlanmışsa kullanılır. (Guido van Rossum'un :" -"issue:`35766` 'teki katkısıyla.)" +"``PyCF_ONLY_AST`` bayrağı ayarlanmışsa kullanılır. (Guido van " +"Rossum'un :issue:`35766` 'teki katkısıyla.)" #: whatsnew/3.8.rst:2024 #, fuzzy @@ -4068,27 +4105,27 @@ msgstr "" #: whatsnew/3.8.rst:2037 msgid "" -"Use of ``#`` variants of formats in parsing or building value (e.g. :c:func:" -"`PyArg_ParseTuple`, :c:func:`Py_BuildValue`, :c:func:" -"`PyObject_CallFunction`, etc.) without ``PY_SSIZE_T_CLEAN`` defined raises " -"``DeprecationWarning`` now. It will be removed in 3.10 or 4.0. Read :ref:" -"`arg-parsing` for detail. (Contributed by Inada Naoki in :issue:`36381`.)" +"Use of ``#`` variants of formats in parsing or building value " +"(e.g. :c:func:`PyArg_ParseTuple`, :c:func:`Py_BuildValue`, :c:func:`PyObject_CallFunction`, " +"etc.) without ``PY_SSIZE_T_CLEAN`` defined raises ``DeprecationWarning`` " +"now. It will be removed in 3.10 or 4.0. Read :ref:`arg-parsing` for detail. " +"(Contributed by Inada Naoki in :issue:`36381`.)" msgstr "" "Ayrıştırma veya değer oluşturmada biçimlerin ``#`` varyantlarının kullanımı " -"(örneğin :c:func:`PyArg_ParseTuple`, :c:func:`Py_BuildValue`, :c:func:" -"`PyObject_CallFunction`, vb.) ``PY_SSIZE_T_CLEAN`` tanımlanmadan artık " -"``DeprecationWarning`` verir. Bu uyarı 3.10 veya 4.0'da kaldırılacaktır. " -"Ayrıntılar için :ref:`arg-parsing` sayfasını okuyun. (Inada Naoki'nin :issue:" -"`36381` 'teki katkısıyla.)" +"(örneğin :c:func:`PyArg_ParseTuple`, :c:func:`Py_BuildValue`, :c:func:`PyObject_CallFunction`, " +"vb.) ``PY_SSIZE_T_CLEAN`` tanımlanmadan artık ``DeprecationWarning`` verir. " +"Bu uyarı 3.10 veya 4.0'da kaldırılacaktır. Ayrıntılar için :ref:`arg-" +"parsing` sayfasını okuyun. (Inada Naoki'nin :issue:`36381` 'teki katkısıyla.)" #: whatsnew/3.8.rst:2043 msgid "" -"Instances of heap-allocated types (such as those created with :c:func:" -"`PyType_FromSpec`) hold a reference to their type object. Increasing the " -"reference count of these type objects has been moved from :c:func:" -"`PyType_GenericAlloc` to the more low-level functions, :c:func:" -"`PyObject_Init` and :c:func:`PyObject_INIT`. This makes types created " -"through :c:func:`PyType_FromSpec` behave like other classes in managed code." +"Instances of heap-allocated types (such as those created " +"with :c:func:`PyType_FromSpec`) hold a reference to their type object. " +"Increasing the reference count of these type objects has been moved " +"from :c:func:`PyType_GenericAlloc` to the more low-level " +"functions, :c:func:`PyObject_Init` and :c:func:`PyObject_INIT`. This makes " +"types created through :c:func:`PyType_FromSpec` behave like other classes in " +"managed code." msgstr "" "Yığın tahsisli tiplerin örnekleri (örneğin :c:func:`PyType_FromSpec` ile " "oluşturulanlar) tip nesnelerine bir referans tutar. Bu tip nesnelerinin " @@ -4127,14 +4164,14 @@ msgstr "" #, fuzzy msgid "" "Remove :c:macro:`Py_INCREF` on the type object after allocating an instance " -"- if any. This may happen after calling :c:macro:`PyObject_New`, :c:macro:" -"`PyObject_NewVar`, :c:func:`PyObject_GC_New`, :c:func:`PyObject_GC_NewVar`, " -"or any other custom allocator that uses :c:func:`PyObject_Init` or :c:func:" -"`PyObject_INIT`." -msgstr "" -"Varsa, bir örnek ayırdıktan sonra tür nesnesi üzerindeki :c:macro:" -"`Py_INCREF` öğesini kaldırın. Bu, :c:func:`PyObject_New`, :c:func:" -"`PyObject_NewVar`, :c:func:`PyObject_GC_New`, :c:func:`PyObject_GC_NewVar` " +"- if any. This may happen after " +"calling :c:macro:`PyObject_New`, :c:macro:`PyObject_NewVar`, :c:func:`PyObject_GC_New`, :c:func:`PyObject_GC_NewVar`, " +"or any other custom allocator that uses :c:func:`PyObject_Init` " +"or :c:func:`PyObject_INIT`." +msgstr "" +"Varsa, bir örnek ayırdıktan sonra tür nesnesi " +"üzerindeki :c:macro:`Py_INCREF` öğesini kaldırın. " +"Bu, :c:func:`PyObject_New`, :c:func:`PyObject_NewVar`, :c:func:`PyObject_GC_New`, :c:func:`PyObject_GC_NewVar` " "veya :c:func:`PyObject_Init` veya :c:func:`PyObject_INIT` kullanan herhangi " "bir özel ayırıcı çağrıldıktan sonra gerçekleşebilir." @@ -4204,15 +4241,17 @@ msgid "" "The interpreter does not pretend to support binary compatibility of " "extension types across feature releases, anymore. A :c:type:`PyTypeObject` " "exported by a third-party extension module is supposed to have all the slots " -"expected in the current Python version, including :c:member:`~PyTypeObject." -"tp_finalize` (:c:macro:`Py_TPFLAGS_HAVE_FINALIZE` is not checked anymore " -"before reading :c:member:`~PyTypeObject.tp_finalize`)." +"expected in the current Python version, " +"including :c:member:`~PyTypeObject.tp_finalize` " +"(:c:macro:`Py_TPFLAGS_HAVE_FINALIZE` is not checked anymore before " +"reading :c:member:`~PyTypeObject.tp_finalize`)." msgstr "" "Yorumlayıcı, artık özellik sürümleri arasında uzantı türlerinin ikili " "uyumluluğunu destekliyormuş gibi davranmıyor. Üçüncü taraf bir uzantı " -"modülü tarafından dışa aktarılan bir :c:type:`PyTypeObject`, :c:member:" -"`~PyTypeObject.tp_finalize` dahil olmak üzere mevcut Python sürümünde " -"beklenen tüm yuvalara sahip olmalıdır (:const:`Py_TPFLAGS_HAVE_FINALIZE` " +"modülü tarafından dışa aktarılan " +"bir :c:type:`PyTypeObject`, :c:member:`~PyTypeObject.tp_finalize` dahil " +"olmak üzere mevcut Python sürümünde beklenen tüm yuvalara sahip olmalıdır " +"(:const:`Py_TPFLAGS_HAVE_FINALIZE` " "artık :c:member:`~PyTypeObject.tp_finalize` okunmadan önce kontrol " "edilmiyor)." @@ -4252,16 +4291,16 @@ msgstr "" #: whatsnew/3.8.rst:2137 msgid "" "The location of an installed :file:`pythonXY.dll` will depend on the " -"installation options and the version and language of Windows. See :ref:" -"`using-on-windows` for more information. The resulting library should be " -"placed in the same directory as :file:`pythonXY.lib`, which is generally " -"the :file:`libs` directory under your Python installation." +"installation options and the version and language of Windows. " +"See :ref:`using-on-windows` for more information. The resulting library " +"should be placed in the same directory as :file:`pythonXY.lib`, which is " +"generally the :file:`libs` directory under your Python installation." msgstr "" "Yüklü bir :file:`pythonXY.dll` dosyasının konumu, kurulum seçeneklerine ve " -"Windows'un sürümüne ve diline bağlı olacaktır. Daha fazla bilgi için :ref:" -"`Windows'ta kullanma ` konusuna bakın. Ortaya çıkan " -"kitaplık, genellikle Python kurulumunuzun altındaki :file:`libs` dizini " -"olan :file:`pythonXY.lib` ile aynı dizine yerleştirilmelidir." +"Windows'un sürümüne ve diline bağlı olacaktır. Daha fazla bilgi " +"için :ref:`Windows'ta kullanma ` konusuna bakın. Ortaya " +"çıkan kitaplık, genellikle Python kurulumunuzun altındaki :file:`libs` " +"dizini olan :file:`pythonXY.lib` ile aynı dizine yerleştirilmelidir." #: whatsnew/3.8.rst:2143 msgid "(Contributed by Steve Dower in :issue:`37351`.)" @@ -4279,28 +4318,29 @@ msgid "" "code for :keyword:`break`, :keyword:`continue` and :keyword:`return`." msgstr "" "Yorumlayıcı döngüsü, blok yığınını açma mantığı derleyiciye taşınarak " -"basitleştirilmiştir. Derleyici artık değer yığınını ayarlamak ve :keyword:" -"`break`, :keyword:`continue` ve :keyword:`return` için temizleme kodunu " -"çağırmak için açık talimatlar yayınlar." +"basitleştirilmiştir. Derleyici artık değer yığınını ayarlamak " +"ve :keyword:`break`, :keyword:`continue` ve :keyword:`return` için temizleme " +"kodunu çağırmak için açık talimatlar yayınlar." #: whatsnew/3.8.rst:2155 msgid "" -"Removed opcodes :opcode:`BREAK_LOOP`, :opcode:`CONTINUE_LOOP`, :opcode:" -"`SETUP_LOOP` and :opcode:`SETUP_EXCEPT`. Added new opcodes :opcode:" -"`ROT_FOUR`, :opcode:`BEGIN_FINALLY`, :opcode:`CALL_FINALLY` and :opcode:" -"`POP_FINALLY`. Changed the behavior of :opcode:`END_FINALLY` and :opcode:" -"`WITH_CLEANUP_START`." +"Removed " +"opcodes :opcode:`BREAK_LOOP`, :opcode:`CONTINUE_LOOP`, :opcode:`SETUP_LOOP` " +"and :opcode:`SETUP_EXCEPT`. Added new " +"opcodes :opcode:`ROT_FOUR`, :opcode:`BEGIN_FINALLY`, :opcode:`CALL_FINALLY` " +"and :opcode:`POP_FINALLY`. Changed the behavior of :opcode:`END_FINALLY` " +"and :opcode:`WITH_CLEANUP_START`." msgstr "" -":opcode:`BREAK_LOOP`, :opcode:`CONTINUE_LOOP`, :opcode:`SETUP_LOOP` ve :" -"opcode:`SETUP_EXCEPT` kodları kaldırıldı. Yeni :opcode:`ROT_FOUR`, :opcode:" -"`BEGIN_FINALLY`, :opcode:`CALL_FINALLY` ve :opcode:`POP_FINALLY` kodları " -"eklendi. :opcode:`END_FINALLY` ve :opcode:`WITH_CLEANUP_START` davranışları " -"değiştirildi." +":opcode:`BREAK_LOOP`, :opcode:`CONTINUE_LOOP`, :opcode:`SETUP_LOOP` " +"ve :opcode:`SETUP_EXCEPT` kodları kaldırıldı. " +"Yeni :opcode:`ROT_FOUR`, :opcode:`BEGIN_FINALLY`, :opcode:`CALL_FINALLY` " +"ve :opcode:`POP_FINALLY` kodları eklendi. :opcode:`END_FINALLY` " +"ve :opcode:`WITH_CLEANUP_START` davranışları değiştirildi." #: whatsnew/3.8.rst:2161 msgid "" -"(Contributed by Mark Shannon, Antoine Pitrou and Serhiy Storchaka in :issue:" -"`17611`.)" +"(Contributed by Mark Shannon, Antoine Pitrou and Serhiy Storchaka " +"in :issue:`17611`.)" msgstr "" "(Mark Shannon, Antoine Pitrou ve Serhiy Storchaka'nın :issue:`17611` 'deki " "katkılarıyla.)" @@ -4433,10 +4473,10 @@ msgid "" msgstr "" "Kıyaslamalar `python.org `_ " "adresinde bulunan macOS 64-bit yapılarını çalıştıran bir `Intel® Core™ " -"i7-4960HQ işlemci `_ üzerinde ölçülmüştür. Kıyaslama betiği zamanlamaları nanosaniye " -"cinsinden gösterir." +"i7-4960HQ işlemci `_ " +"üzerinde ölçülmüştür. Kıyaslama betiği zamanlamaları nanosaniye cinsinden " +"gösterir." #: whatsnew/3.8.rst:2237 msgid "Notable changes in Python 3.8.1" @@ -4444,19 +4484,19 @@ msgstr "Python 3.8.1'deki önemli değişiklikler" #: whatsnew/3.8.rst:2239 msgid "" -"Due to significant security concerns, the *reuse_address* parameter of :meth:" -"`asyncio.loop.create_datagram_endpoint` is no longer supported. This is " -"because of the behavior of the socket option ``SO_REUSEADDR`` in UDP. For " -"more details, see the documentation for ``loop.create_datagram_endpoint()``. " -"(Contributed by Kyle Stanley, Antoine Pitrou, and Yury Selivanov in :issue:" -"`37228`.)" +"Due to significant security concerns, the *reuse_address* parameter " +"of :meth:`asyncio.loop.create_datagram_endpoint` is no longer supported. " +"This is because of the behavior of the socket option ``SO_REUSEADDR`` in " +"UDP. For more details, see the documentation for " +"``loop.create_datagram_endpoint()``. (Contributed by Kyle Stanley, Antoine " +"Pitrou, and Yury Selivanov in :issue:`37228`.)" msgstr "" -"Önemli güvenlik endişeleri nedeniyle, :meth:`asyncio.loop." -"create_datagram_endpoint` parametresinin *reuse_address* parametresi artık " -"desteklenmemektedir. Bunun nedeni UDP'deki ``SO_REUSEADDR`` soket " -"seçeneğinin davranışıdır. Daha fazla ayrıntı için ``loop." -"create_datagram_endpoint()`` belgelerine bakın. (Kyle Stanley, Antoine " -"Pitrou ve Yury Selivanov'un :issue:`37228` 'deki katkılarıyla.)" +"Önemli güvenlik endişeleri " +"nedeniyle, :meth:`asyncio.loop.create_datagram_endpoint` parametresinin " +"*reuse_address* parametresi artık desteklenmemektedir. Bunun nedeni UDP'deki " +"``SO_REUSEADDR`` soket seçeneğinin davranışıdır. Daha fazla ayrıntı için " +"``loop.create_datagram_endpoint()`` belgelerine bakın. (Kyle Stanley, " +"Antoine Pitrou ve Yury Selivanov'un :issue:`37228` 'deki katkılarıyla.)" #: whatsnew/3.8.rst:2247 #, fuzzy @@ -4490,23 +4530,24 @@ msgstr "Python 3.8.8'deki önemli değişiklikler" #: whatsnew/3.8.rst:2264 msgid "" "Earlier Python versions allowed using both ``;`` and ``&`` as query " -"parameter separators in :func:`urllib.parse.parse_qs` and :func:`urllib." -"parse.parse_qsl`. Due to security concerns, and to conform with newer W3C " -"recommendations, this has been changed to allow only a single separator key, " -"with ``&`` as the default. This change also affects :func:`cgi.parse` and :" -"func:`cgi.parse_multipart` as they use the affected functions internally. " -"For more details, please see their respective documentation. (Contributed by " -"Adam Goldschmidt, Senthil Kumaran and Ken Jin in :issue:`42967`.)" -msgstr "" -"Daha önceki Python sürümleri :func:`urllib.parse.parse_qs` ve :func:`urllib." -"parse.parse_qsl` içinde sorgu parametresi ayırıcıları olarak hem ``;`` hem " -"de ``&`` kullanılmasına izin veriyordu. Güvenlik endişeleri nedeniyle ve " -"daha yeni W3C önerilerine uymak için, bu, varsayılan olarak ``&`` ile " -"yalnızca tek bir ayırıcı anahtara izin verecek şekilde değiştirildi. Bu " -"değişiklik aynı zamanda :func:`cgi.parse` ve :func:`cgi.parse_multipart` " -"fonksiyonlarını da etkilemektedir. Daha fazla ayrıntı için lütfen ilgili " -"belgelere bakın. (Adam Goldschmidt, Senthil Kumaran ve Ken Jin'in :issue:" -"`42967` 'deki katkılarıyla.)" +"parameter separators in :func:`urllib.parse.parse_qs` " +"and :func:`urllib.parse.parse_qsl`. Due to security concerns, and to " +"conform with newer W3C recommendations, this has been changed to allow only " +"a single separator key, with ``&`` as the default. This change also " +"affects :func:`cgi.parse` and :func:`cgi.parse_multipart` as they use the " +"affected functions internally. For more details, please see their respective " +"documentation. (Contributed by Adam Goldschmidt, Senthil Kumaran and Ken Jin " +"in :issue:`42967`.)" +msgstr "" +"Daha önceki Python sürümleri :func:`urllib.parse.parse_qs` " +"ve :func:`urllib.parse.parse_qsl` içinde sorgu parametresi ayırıcıları " +"olarak hem ``;`` hem de ``&`` kullanılmasına izin veriyordu. Güvenlik " +"endişeleri nedeniyle ve daha yeni W3C önerilerine uymak için, bu, varsayılan " +"olarak ``&`` ile yalnızca tek bir ayırıcı anahtara izin verecek şekilde " +"değiştirildi. Bu değişiklik aynı zamanda :func:`cgi.parse` " +"ve :func:`cgi.parse_multipart` fonksiyonlarını da etkilemektedir. Daha fazla " +"ayrıntı için lütfen ilgili belgelere bakın. (Adam Goldschmidt, Senthil " +"Kumaran ve Ken Jin'in :issue:`42967` 'deki katkılarıyla.)" #: whatsnew/3.8.rst:2275 #, fuzzy @@ -4546,9 +4587,9 @@ msgstr "" #: whatsnew/3.8.rst:2299 msgid "" -"(Originally contributed by Ronald Oussoren and Lawrence D'Anna in :gh:" -"`85272`, with fixes by FX Coudert and Eli Rykoff, and backported to 3.8 by " -"Maxime Bélanger and Ned Deily)" +"(Originally contributed by Ronald Oussoren and Lawrence D'Anna " +"in :gh:`85272`, with fixes by FX Coudert and Eli Rykoff, and backported to " +"3.8 by Maxime Bélanger and Ned Deily)" msgstr "" #: whatsnew/3.8.rst:2307 @@ -4558,11 +4599,12 @@ msgstr "" #: whatsnew/3.8.rst:2309 msgid "" "The presence of newline or tab characters in parts of a URL allows for some " -"forms of attacks. Following the WHATWG specification that updates :rfc:" -"`3986`, ASCII newline ``\\n``, ``\\r`` and tab ``\\t`` characters are " -"stripped from the URL by the parser in :mod:`urllib.parse` preventing such " -"attacks. The removal characters are controlled by a new module level " -"variable ``urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE``. (See :issue:`43882`)" +"forms of attacks. Following the WHATWG specification that " +"updates :rfc:`3986`, ASCII newline ``\\n``, ``\\r`` and tab ``\\t`` " +"characters are stripped from the URL by the parser in :mod:`urllib.parse` " +"preventing such attacks. The removal characters are controlled by a new " +"module level variable ``urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE``. " +"(See :issue:`43882`)" msgstr "" #: whatsnew/3.8.rst:2318 @@ -4631,6 +4673,6 @@ msgstr "" #~ "Added :meth:`pathlib.Path.link_to()` which creates a hard link pointing " #~ "to a path. (Contributed by Joannah Nanjekye in :issue:`26978`)" #~ msgstr "" -#~ "Bir yola işaret eden sabit bir bağlantı oluşturan :meth:`pathlib.Path." -#~ "link_to()` eklendi. (Joannah Nanjekye'nin :issue:`26978` 'deki " -#~ "katkısıyla.)" +#~ "Bir yola işaret eden sabit bir bağlantı " +#~ "oluşturan :meth:`pathlib.Path.link_to()` eklendi. (Joannah " +#~ "Nanjekye'nin :issue:`26978` 'deki katkısıyla.)" diff --git a/whatsnew/3.9.po b/whatsnew/3.9.po index 9f8c24bd6..3f0bfd9cc 100644 --- a/whatsnew/3.9.po +++ b/whatsnew/3.9.po @@ -32,8 +32,8 @@ msgstr "Łukasz Langa" #, fuzzy msgid "" "This article explains the new features in Python 3.9, compared to 3.8. " -"Python 3.9 was released on October 5, 2020. For full details, see the :ref:" -"`changelog `." +"Python 3.9 was released on October 5, 2020. For full details, see " +"the :ref:`changelog `." msgstr "" "Bu makale Python 3.9' daki 3.8' e kıyasla yeni özellikleri açıklamaktadır. " "Python 3.9 5 Ekim 2020 tarihinde yayınlandı." @@ -85,8 +85,8 @@ msgid "" ":func:`os.pidfd_open` added that allows process management without races and " "signals." msgstr "" -"Yarışlar ve sinyaller olmadan süreç yönetimine izin veren :func:`os." -"pidfd_open` eklendi." +"Yarışlar ve sinyaller olmadan süreç yönetimine izin " +"veren :func:`os.pidfd_open` eklendi." #: whatsnew/3.9.rst:76 msgid "Interpreter improvements:" @@ -107,8 +107,8 @@ msgid "" "a number of Python builtins (range, tuple, set, frozenset, list, dict) are " "now sped up using :pep:`590` vectorcall;" msgstr "" -"bir dizi python gömülüleri (range, tuple, set, frozenset, list, dict) :pep:" -"`590` vectorcall kullanılarak hızlandırıldı;" +"bir dizi python gömülüleri (range, tuple, set, frozenset, list, " +"dict) :pep:`590` vectorcall kullanılarak hızlandırıldı;" #: whatsnew/3.9.rst:83 msgid "garbage collection does not block on resurrected objects;" @@ -117,30 +117,28 @@ msgstr "çöp toplama, dirilen nesnelerde engellemez;" #: whatsnew/3.9.rst:84 #, fuzzy msgid "" -"a number of Python modules (:mod:`!_abc`, :mod:`audioop`, :mod:`!_bz2`, :mod:" -"`!_codecs`, :mod:`!_contextvars`, :mod:`!_crypt`, :mod:`!_functools`, :mod:`!" -"_json`, :mod:`!_locale`, :mod:`math`, :mod:`operator`, :mod:`resource`, :mod:" -"`time`, :mod:`!_weakref`) now use multiphase initialization as defined by " -"PEP 489;" +"a number of Python modules (:mod:`!_abc`, :mod:`audioop`, :mod:`!" +"_bz2`, :mod:`!_codecs`, :mod:`!_contextvars`, :mod:`!_crypt`, :mod:`!" +"_functools`, :mod:`!_json`, :mod:`!" +"_locale`, :mod:`math`, :mod:`operator`, :mod:`resource`, :mod:`time`, :mod:`!" +"_weakref`) now use multiphase initialization as defined by PEP 489;" msgstr "" -"bir dizi Python modülü (:mod:`_abc`, :mod:`audioop`, :mod:`_bz2`, :mod:" -"`_codecs`, :mod:`_contextvars`, :mod:`_crypt`, :mod:`_functools`, :mod:" -"`_json`, :mod:`_locale`, :mod:`math`, :mod:`operator`, :mod:`resource`, :mod:" -"`time`, :mod:`_weakref`) PEP 489 tarafından tanımlandığı gibi çok fazlı " -"başlatma kullanır;" +"bir dizi Python modülü " +"(:mod:`_abc`, :mod:`audioop`, :mod:`_bz2`, :mod:`_codecs`, :mod:`_contextvars`, :mod:`_crypt`, :mod:`_functools`, :mod:`_json`, :mod:`_locale`, :mod:`math`, :mod:`operator`, :mod:`resource`, :mod:`time`, :mod:`_weakref`) " +"PEP 489 tarafından tanımlandığı gibi çok fazlı başlatma kullanır;" #: whatsnew/3.9.rst:89 #, fuzzy msgid "" -"a number of standard library modules (:mod:`audioop`, :mod:`ast`, :mod:" -"`grp`, :mod:`!_hashlib`, :mod:`pwd`, :mod:`!_posixsubprocess`, :mod:" -"`random`, :mod:`select`, :mod:`struct`, :mod:`termios`, :mod:`zlib`) are now " -"using the stable ABI defined by PEP 384." +"a number of standard library modules " +"(:mod:`audioop`, :mod:`ast`, :mod:`grp`, :mod:`!" +"_hashlib`, :mod:`pwd`, :mod:`!" +"_posixsubprocess`, :mod:`random`, :mod:`select`, :mod:`struct`, :mod:`termios`, :mod:`zlib`) " +"are now using the stable ABI defined by PEP 384." msgstr "" -"bir dizi standart kitaplık modülleri (:mod:`audioop`, :mod:`ast`, :mod:" -"`grp`, :mod:`_hashlib`, :mod:`pwd`, :mod:`_posixsubprocess`, :mod:`random`, :" -"mod:`select`, :mod:`struct`, :mod:`termios`, :mod:`zlib`) artık PEP 384 " -"tarafından tanımlanan kararlı ABI'yi kullanıyor." +"bir dizi standart kitaplık modülleri " +"(:mod:`audioop`, :mod:`ast`, :mod:`grp`, :mod:`_hashlib`, :mod:`pwd`, :mod:`_posixsubprocess`, :mod:`random`, :mod:`select`, :mod:`struct`, :mod:`termios`, :mod:`zlib`) " +"artık PEP 384 tarafından tanımlanan kararlı ABI'yi kullanıyor." #: whatsnew/3.9.rst:94 msgid "New library modules:" @@ -188,9 +186,9 @@ msgstr "" "Python 3'teki birçok işlevsellik korunmuştur. Python 2 desteğinin sona " "ermesiyle bu geriye dönük uyumluluk katmanları kaldırıldı veya yakında " "kaldırılacak. Çoğu, birkaç yıl boyunca bir :exc:`DeprecationWarning` uyarısı " -"yayınladı. Örneğin, ``collections.abc.Mapping`` yerine ``collections." -"Mappin`` kullanmak, 2012'de yayınlanan Python 3.3'ten bu yana bir :exc:" -"`DeprecationWarning` yayar." +"yayınladı. Örneğin, ``collections.abc.Mapping`` yerine " +"``collections.Mappin`` kullanmak, 2012'de yayınlanan Python 3.3'ten bu yana " +"bir :exc:`DeprecationWarning` yayar." #: whatsnew/3.9.rst:117 msgid "" @@ -220,9 +218,9 @@ msgstr "" #: whatsnew/3.9.rst:126 msgid "" "Aliases to :ref:`Abstract Base Classes ` " -"in the :mod:`collections` module, like ``collections.Mapping`` alias to :" -"class:`collections.abc.Mapping`, are kept for one last release for backward " -"compatibility. They will be removed from Python 3.10." +"in the :mod:`collections` module, like ``collections.Mapping`` alias " +"to :class:`collections.abc.Mapping`, are kept for one last release for " +"backward compatibility. They will be removed from Python 3.10." msgstr "" ":mod:`collections` modülünde :ref:`Soyut Temel Sınıflar ` için takma adlar, :class:`collections.abc.Mapping` " @@ -257,13 +255,13 @@ msgstr "Sözlük Birleştirme ve Güncelleme Operatörleri" #: whatsnew/3.9.rst:145 msgid "" -"Merge (``|``) and update (``|=``) operators have been added to the built-in :" -"class:`dict` class. Those complement the existing ``dict.update`` and " +"Merge (``|``) and update (``|=``) operators have been added to the built-" +"in :class:`dict` class. Those complement the existing ``dict.update`` and " "``{**d1, **d2}`` methods of merging dictionaries." msgstr "" "Gömülü :class:`dict` sınıfına birleştirme (``|``) ve güncelleme (``|=``) " -"operatörleri eklendi. Bunlar, sözlükleri birleştirmenin mevcut ``dict." -"update`` ve ``{**d1, **d2}`` yöntemlerini tamamlar." +"operatörleri eklendi. Bunlar, sözlükleri birleştirmenin mevcut " +"``dict.update`` ve ``{**d1, **d2}`` yöntemlerini tamamlar." #: whatsnew/3.9.rst:282 msgid "Example::" @@ -281,11 +279,11 @@ msgstr "" #: whatsnew/3.9.rst:158 msgid "" -"See :pep:`584` for a full description. (Contributed by Brandt Bucher in :" -"issue:`36144`.)" +"See :pep:`584` for a full description. (Contributed by Brandt Bucher " +"in :issue:`36144`.)" msgstr "" -"Tam açıklama için :pep:`584` sayfasına bakınız. (Brandt Bucher tarafından :" -"issue:`36144` ile katkıda bulunulmuştur)" +"Tam açıklama için :pep:`584` sayfasına bakınız. (Brandt Bucher " +"tarafından :issue:`36144` ile katkıda bulunulmuştur)" #: whatsnew/3.9.rst:162 msgid "New String Methods to Remove Prefixes and Suffixes" @@ -293,19 +291,19 @@ msgstr "Önekleri ve Sonekleri Kaldırmak için Yeni Dize Yöntemleri" #: whatsnew/3.9.rst:164 msgid "" -":meth:`str.removeprefix(prefix)` and :meth:`str." -"removesuffix(suffix)` have been added to easily remove an " -"unneeded prefix or a suffix from a string. Corresponding ``bytes``, " -"``bytearray``, and ``collections.UserString`` methods have also been added. " -"See :pep:`616` for a full description. (Contributed by Dennis Sweeney in :" -"issue:`39939`.)" +":meth:`str.removeprefix(prefix)` " +"and :meth:`str.removesuffix(suffix)` have been added to " +"easily remove an unneeded prefix or a suffix from a string. Corresponding " +"``bytes``, ``bytearray``, and ``collections.UserString`` methods have also " +"been added. See :pep:`616` for a full description. (Contributed by Dennis " +"Sweeney in :issue:`39939`.)" msgstr "" -":meth:`str.removeprefix(prefix)` ve :meth:`str." -"removesuffix(suffix)`, gereksiz bir öneki veya bir soneki " -"bir dizeden kolayca kaldırmak için eklenmiştir. Karşılık gelen ``bytes``, " -"``bytearray`` ve ``collections.UserString`` yöntemleri de eklenmiştir. Tam " -"açıklama için :pep:`616` 'ya bakın. (Dennis Sweeney tarafından :issue:" -"`39939` 'da katılmıştır.)" +":meth:`str.removeprefix(prefix)` " +"ve :meth:`str.removesuffix(suffix)`, gereksiz bir öneki " +"veya bir soneki bir dizeden kolayca kaldırmak için eklenmiştir. Karşılık " +"gelen ``bytes``, ``bytearray`` ve ``collections.UserString`` yöntemleri de " +"eklenmiştir. Tam açıklama için :pep:`616` 'ya bakın. (Dennis Sweeney " +"tarafından :issue:`39939` 'da katılmıştır.)" #: whatsnew/3.9.rst:172 msgid "Type Hinting Generics in Standard Collections" @@ -382,10 +380,10 @@ msgid "" "(``PYTHONOLDPARSER=1``)." msgstr "" "Python 3.10'da, eski ayrıştırıcı ve buna bağlı olan tüm fonksiyonlar " -"silinecektir (öncelikle uzun süredir kullanımdan kaldırılmış olan :mod:" -"`parser` modülü). *yalnızca* Python 3.9'da, bir komut satırı anahtarı (``-X " -"oldparser``) veya bir ortam değişkeni (``PYTHONOLDPARSER=1``) kullanarak " -"LL(1) ayrıştırıcısına geri dönebilirsiniz." +"silinecektir (öncelikle uzun süredir kullanımdan kaldırılmış " +"olan :mod:`parser` modülü). *yalnızca* Python 3.9'da, bir komut satırı " +"anahtarı (``-X oldparser``) veya bir ortam değişkeni (``PYTHONOLDPARSER=1``) " +"kullanarak LL(1) ayrıştırıcısına geri dönebilirsiniz." #: whatsnew/3.9.rst:211 msgid "" @@ -401,9 +399,9 @@ msgstr "Başka Dil Değişiklikleri" #: whatsnew/3.9.rst:218 msgid "" -":func:`__import__` now raises :exc:`ImportError` instead of :exc:" -"`ValueError`, which used to occur when a relative import went past its top-" -"level package. (Contributed by Ngalim Siregar in :issue:`37444`.)" +":func:`__import__` now raises :exc:`ImportError` instead " +"of :exc:`ValueError`, which used to occur when a relative import went past " +"its top-level package. (Contributed by Ngalim Siregar in :issue:`37444`.)" msgstr "" ":func:`__import__` artık :exc:`ImportError` değerini, eskiden göreli bir içe " "aktarma üst düzey paketini geçtiğinde oluşan :exc:`ValueError` yerine " @@ -412,27 +410,27 @@ msgstr "" #: whatsnew/3.9.rst:223 msgid "" "Python now gets the absolute path of the script filename specified on the " -"command line (ex: ``python3 script.py``): the ``__file__`` attribute of the :" -"mod:`__main__` module became an absolute path, rather than a relative path. " -"These paths now remain valid after the current directory is changed by :func:" -"`os.chdir`. As a side effect, the traceback also displays the absolute path " -"for :mod:`__main__` module frames in this case. (Contributed by Victor " -"Stinner in :issue:`20443`.)" +"command line (ex: ``python3 script.py``): the ``__file__`` attribute of " +"the :mod:`__main__` module became an absolute path, rather than a relative " +"path. These paths now remain valid after the current directory is changed " +"by :func:`os.chdir`. As a side effect, the traceback also displays the " +"absolute path for :mod:`__main__` module frames in this case. (Contributed " +"by Victor Stinner in :issue:`20443`.)" msgstr "" "Python artık komut satırında belirtilen betik dosya adının mutlak yolunu " "alıyor (örn: ``python3 script.py``): :mod:`__main__` modülünün ``__file__`` " "özniteliği, mutlak bir yol haline geldi. göreceli bir yoldan daha. Bu " "yollar, geçerli dizin :func:`os.chdir` tarafından değiştirildikten sonra " -"artık geçerliliğini koruyor. Bir yan etki olarak geri izleme, bu durumda :" -"mod:`__main__` modül çerçeveleri için mutlak yolu da görüntüler. (Victor " -"Stinner tarafından :issue:`20443` 'de katılmıştır.)" +"artık geçerliliğini koruyor. Bir yan etki olarak geri izleme, bu " +"durumda :mod:`__main__` modül çerçeveleri için mutlak yolu da görüntüler. " +"(Victor Stinner tarafından :issue:`20443` 'de katılmıştır.)" #: whatsnew/3.9.rst:231 msgid "" "In the :ref:`Python Development Mode ` and in :ref:`debug build " "`, the *encoding* and *errors* arguments are now checked for " -"string encoding and decoding operations. Examples: :func:`open`, :meth:`str." -"encode` and :meth:`bytes.decode`." +"string encoding and decoding operations. " +"Examples: :func:`open`, :meth:`str.encode` and :meth:`bytes.decode`." msgstr "" ":ref:`Python Development Mode ` ve :ref:`debug build ` " "içinde, *encoding* ve *errors* argümanları artık dize kodlama ve kod çözme " @@ -458,9 +456,10 @@ msgid "" "objects. (Contributed by Serhiy Storchaka in :issue:`28029`.)" msgstr "" "``\"\".replace(\"\", s, n)`` artık sıfır olmayan tüm ``n`` için boş bir dize " -"yerine ``s`` döndürür. Artık ``\"\".replace(\"\", s)`` ile tutarlıdır. :" -"class:`bytes` ve :class:`bytearray` nesneleri için benzer değişiklikler " -"vardır. (Serhiy Storchaka tarafından :issue:`28029` 'da katılmıştır.)" +"yerine ``s`` döndürür. Artık ``\"\".replace(\"\", s)`` ile " +"tutarlıdır. :class:`bytes` ve :class:`bytearray` nesneleri için benzer " +"değişiklikler vardır. (Serhiy Storchaka tarafından :issue:`28029` 'da " +"katılmıştır.)" #: whatsnew/3.9.rst:246 msgid "" @@ -488,10 +487,10 @@ msgstr "" #: whatsnew/3.9.rst:256 msgid "" -"Parallel running of :meth:`~agen.aclose` / :meth:`~agen.asend` / :meth:" -"`~agen.athrow` is now prohibited, and ``ag_running`` now reflects the actual " -"running status of the async generator. (Contributed by Yury Selivanov in :" -"issue:`30773`.)" +"Parallel running " +"of :meth:`~agen.aclose` / :meth:`~agen.asend` / :meth:`~agen.athrow` is now " +"prohibited, and ``ag_running`` now reflects the actual running status of the " +"async generator. (Contributed by Yury Selivanov in :issue:`30773`.)" msgstr "" ":meth:`~agen.aclose` / :meth:`~agen.asend` / :meth:`~agen.athrow` 'nın " "paralel çalışması artık yasaklanmıştır ve ``ag_running`` artık zaman uyumsuz " @@ -501,21 +500,23 @@ msgstr "" #: whatsnew/3.9.rst:261 msgid "" "Unexpected errors in calling the ``__iter__`` method are no longer masked by " -"``TypeError`` in the :keyword:`in` operator and functions :func:`~operator." -"contains`, :func:`~operator.indexOf` and :func:`~operator.countOf` of the :" -"mod:`operator` module. (Contributed by Serhiy Storchaka in :issue:`40824`.)" +"``TypeError`` in the :keyword:`in` operator and " +"functions :func:`~operator.contains`, :func:`~operator.indexOf` " +"and :func:`~operator.countOf` of the :mod:`operator` module. (Contributed by " +"Serhiy Storchaka in :issue:`40824`.)" msgstr "" "``__iter__`` yöntemini çağırmadaki beklenmeyen hatalar artık :keyword:`in` " -"operatöründe ve :mod:`operator` modülünün :func:`~operator.contains`, :func:" -"`~operator.indexOf` ve :func:`~operator.countOf` fonksiyonlarında " -"``TypeError`` tarafından maskelenmiyor. ( :issue:`40824` içinde Serhiy " -"Storchaka tarafından katılmıştır.)" +"operatöründe ve :mod:`operator` " +"modülünün :func:`~operator.contains`, :func:`~operator.indexOf` " +"ve :func:`~operator.countOf` fonksiyonlarında ``TypeError`` tarafından " +"maskelenmiyor. ( :issue:`40824` içinde Serhiy Storchaka tarafından " +"katılmıştır.)" #: whatsnew/3.9.rst:267 msgid "" "Unparenthesized lambda expressions can no longer be the expression part in " -"an ``if`` clause in comprehensions and generator expressions. See :issue:" -"`41848` and :issue:`43755` for details." +"an ``if`` clause in comprehensions and generator expressions. " +"See :issue:`41848` and :issue:`43755` for details." msgstr "" "Parantezsiz lambda ifadeleri artık kavramalarda ve üreteç ifadelerinde bir " "``if`` yan tümcesinde ifade parçası olamaz. Ayrıntılar için :issue:`41848` " @@ -532,8 +533,9 @@ msgstr "zoneinfo" #: whatsnew/3.9.rst:278 msgid "" "The :mod:`zoneinfo` module brings support for the IANA time zone database to " -"the standard library. It adds :class:`zoneinfo.ZoneInfo`, a concrete :class:" -"`datetime.tzinfo` implementation backed by the system's time zone data." +"the standard library. It adds :class:`zoneinfo.ZoneInfo`, a " +"concrete :class:`datetime.tzinfo` implementation backed by the system's time " +"zone data." msgstr "" ":mod:`zoneinfo` modülü, standart kitaplığa IANA saat dilimi veritabanı " "desteği getirir. Sistemin saat dilimi verileri tarafından desteklenen somut " @@ -587,10 +589,10 @@ msgstr "graphlib" #: whatsnew/3.9.rst:315 msgid "" -"A new module, :mod:`graphlib`, was added that contains the :class:`graphlib." -"TopologicalSorter` class to offer functionality to perform topological " -"sorting of graphs. (Contributed by Pablo Galindo, Tim Peters and Larry " -"Hastings in :issue:`17005`.)" +"A new module, :mod:`graphlib`, was added that contains " +"the :class:`graphlib.TopologicalSorter` class to offer functionality to " +"perform topological sorting of graphs. (Contributed by Pablo Galindo, Tim " +"Peters and Larry Hastings in :issue:`17005`.)" msgstr "" "Grafiklerin topolojik sıralamasını gerçekleştirmek üzere işlevsellik sunmak " "için :class:`graphlib.TopologicalSorter` sınıfını içeren :mod:`graphlib` " @@ -608,8 +610,8 @@ msgstr "ast" #: whatsnew/3.9.rst:327 msgid "" "Added the *indent* option to :func:`~ast.dump` which allows it to produce a " -"multiline indented output. (Contributed by Serhiy Storchaka in :issue:" -"`37995`.)" +"multiline indented output. (Contributed by Serhiy Storchaka " +"in :issue:`37995`.)" msgstr "" ":func:`~ast.dump` dosyasına *indent* seçeneği eklendi, bu da çok satırlı " "girintili bir çıktı üretmesini sağlar. ( :issue:`37995` içinde Serhiy " @@ -624,9 +626,9 @@ msgid "" msgstr "" ":mod:`ast` modülüne, bir :class:`ast.AST` nesnesini ayrıştırmak ve " "ayrıştırıldığında eşdeğer bir :class:`ast.AST` nesnesi üretecek kod içeren " -"bir dize üretmek için kullanılabilen bir fonksiyon olarak :func:`ast." -"unparse` eklendi. ( :issue:`38870` 'de Pablo Galindo ve Batuhan Taskaya'nın " -"katkısıyla.)" +"bir dize üretmek için kullanılabilen bir fonksiyon " +"olarak :func:`ast.unparse` eklendi. ( :issue:`38870` 'de Pablo Galindo ve " +"Batuhan Taskaya'nın katkısıyla.)" #: whatsnew/3.9.rst:336 msgid "" @@ -642,33 +644,34 @@ msgstr "asyncio" #: whatsnew/3.9.rst:342 msgid "" -"Due to significant security concerns, the *reuse_address* parameter of :meth:" -"`asyncio.loop.create_datagram_endpoint` is no longer supported. This is " -"because of the behavior of the socket option ``SO_REUSEADDR`` in UDP. For " -"more details, see the documentation for ``loop.create_datagram_endpoint()``. " -"(Contributed by Kyle Stanley, Antoine Pitrou, and Yury Selivanov in :issue:" -"`37228`.)" +"Due to significant security concerns, the *reuse_address* parameter " +"of :meth:`asyncio.loop.create_datagram_endpoint` is no longer supported. " +"This is because of the behavior of the socket option ``SO_REUSEADDR`` in " +"UDP. For more details, see the documentation for " +"``loop.create_datagram_endpoint()``. (Contributed by Kyle Stanley, Antoine " +"Pitrou, and Yury Selivanov in :issue:`37228`.)" msgstr "" -"Önemli güvenlik kaygıları nedeniyle, :meth:`asyncio.loop." -"create_datagram_endpoint` 'in *reuse_address* parametresi artık " -"desteklenmemektedir. Bunun nedeni, UDP'deki ``SO_REUSEADDR`` soket " -"seçeneğinin davranışıdır. Daha fazla ayrıntı için ``loop." -"create_datagram_endpoint()`` belgelerine bakın. (Kyle Stanley, Antoine " -"Pitrou ve Yury Selivanov'un katkılarıyla :issue:`37228`.)" +"Önemli güvenlik kaygıları " +"nedeniyle, :meth:`asyncio.loop.create_datagram_endpoint` 'in *reuse_address* " +"parametresi artık desteklenmemektedir. Bunun nedeni, UDP'deki " +"``SO_REUSEADDR`` soket seçeneğinin davranışıdır. Daha fazla ayrıntı için " +"``loop.create_datagram_endpoint()`` belgelerine bakın. (Kyle Stanley, " +"Antoine Pitrou ve Yury Selivanov'un katkılarıyla :issue:`37228`.)" #: whatsnew/3.9.rst:349 msgid "" -"Added a new :term:`coroutine` :meth:`~asyncio.loop." -"shutdown_default_executor` that schedules a shutdown for the default " -"executor that waits on the :class:`~concurrent.futures.ThreadPoolExecutor` " -"to finish closing. Also, :func:`asyncio.run` has been updated to use the " -"new :term:`coroutine`. (Contributed by Kyle Stanley in :issue:`34037`.)" +"Added a " +"new :term:`coroutine` :meth:`~asyncio.loop.shutdown_default_executor` that " +"schedules a shutdown for the default executor that waits on " +"the :class:`~concurrent.futures.ThreadPoolExecutor` to finish closing. " +"Also, :func:`asyncio.run` has been updated to use the new :term:`coroutine`. " +"(Contributed by Kyle Stanley in :issue:`34037`.)" msgstr "" ":class:`~concurrent.futures.ThreadPoolExecutor` üzerinde kapanışı bitirmeyi " -"bekleyen varsayılan yürütücü için bir kapatma programlayan yeni bir :term:" -"`coroutine` :meth:`~asyncio.loop.shutdown_default_executor` eklendi. " -"Ayrıca, :func:`asyncio.run` yeni :term:`coroutine` kelimesini kullanacak " -"şekilde güncellendi. (Kyle Stanley tarafından :issue:`34037` 'de " +"bekleyen varsayılan yürütücü için bir kapatma programlayan yeni " +"bir :term:`coroutine` :meth:`~asyncio.loop.shutdown_default_executor` " +"eklendi. Ayrıca, :func:`asyncio.run` yeni :term:`coroutine` kelimesini " +"kullanacak şekilde güncellendi. (Kyle Stanley tarafından :issue:`34037` 'de " "katılmıştır.)" #: whatsnew/3.9.rst:355 @@ -683,16 +686,17 @@ msgstr "" msgid "" "Added a new :term:`coroutine` :func:`asyncio.to_thread`. It is mainly used " "for running IO-bound functions in a separate thread to avoid blocking the " -"event loop, and essentially works as a high-level version of :meth:`~asyncio." -"loop.run_in_executor` that can directly take keyword arguments. (Contributed " -"by Kyle Stanley and Yury Selivanov in :issue:`32309`.)" +"event loop, and essentially works as a high-level version " +"of :meth:`~asyncio.loop.run_in_executor` that can directly take keyword " +"arguments. (Contributed by Kyle Stanley and Yury Selivanov " +"in :issue:`32309`.)" msgstr "" "Yeni bir :term:`coroutine` :func:`asyncio.to_thread` eklendi. Olay döngüsünü " "engellemekten kaçınmak için GÇ'ye bağlı işlevleri ayrı bir iş parçacığında " -"çalıştırmak için kullanılır ve temel olarak :meth:`~asyncio.loop." -"run_in_executor` öğesinin doğrudan anahtar sözcük bağımsız değişkenlerini " -"alabilen üst düzey bir sürümü olarak çalışır. ( :issue:`32309` 'da Kyle " -"Stanley ve Yuri Selivanov tarafından katılmıştır.)" +"çalıştırmak için kullanılır ve temel " +"olarak :meth:`~asyncio.loop.run_in_executor` öğesinin doğrudan anahtar " +"sözcük bağımsız değişkenlerini alabilen üst düzey bir sürümü olarak çalışır. " +"( :issue:`32309` 'da Kyle Stanley ve Yuri Selivanov tarafından katılmıştır.)" #: whatsnew/3.9.rst:364 msgid "" @@ -710,8 +714,8 @@ msgstr "" #, fuzzy msgid "" ":mod:`asyncio` now raises :exc:`TypeError` when calling incompatible methods " -"with an :class:`ssl.SSLSocket` socket. (Contributed by Ido Michael in :issue:" -"`37404`.)" +"with an :class:`ssl.SSLSocket` socket. (Contributed by Ido Michael " +"in :issue:`37404`.)" msgstr "" ":mod:`asyncio` artık bir :class:`ssl.SSLSocket` soketi ile uyumsuz yöntemler " "çağrıldığında :exc:`TyperError` hatası veriyor. ( :issue:`37404` içinde Ido " @@ -736,8 +740,8 @@ msgid "" "Added new options for path manipulation in resulting ``.pyc`` files: " "*stripdir*, *prependdir*, *limit_sl_dest* parameters and -s, -p, -e command " "line options. Added the possibility to specify the option for an " -"optimization level multiple times. (Contributed by Lumír 'Frenzy' Balhar in :" -"issue:`38112`.)" +"optimization level multiple times. (Contributed by Lumír 'Frenzy' Balhar " +"in :issue:`38112`.)" msgstr "" "Ortaya çıkan ``.pyc`` dosyalarında yol işleme için yeni seçenekler eklendi: " "*stripdir*, *prependdir*, *limit_sl_dest* parametreleri ve -s, -p, -e komut " @@ -750,10 +754,11 @@ msgstr "concurrent.futures" #: whatsnew/3.9.rst:386 msgid "" -"Added a new *cancel_futures* parameter to :meth:`concurrent.futures.Executor." -"shutdown` that cancels all pending futures which have not started running, " -"instead of waiting for them to complete before shutting down the executor. " -"(Contributed by Kyle Stanley in :issue:`39349`.)" +"Added a new *cancel_futures* parameter " +"to :meth:`concurrent.futures.Executor.shutdown` that cancels all pending " +"futures which have not started running, instead of waiting for them to " +"complete before shutting down the executor. (Contributed by Kyle Stanley " +"in :issue:`39349`.)" msgstr "" ":meth:`concurrent.futures.Executor.shutdown` öğesine, yürütücüyü kapatmadan " "önce tamamlanmalarını beklemek yerine çalışmaya başlamamış bekleyen tüm " @@ -767,11 +772,11 @@ msgid "" "compatibility with subinterpreters and predictability in their shutdown " "processes. (Contributed by Kyle Stanley in :issue:`39812`.)" msgstr "" -":class:`~concurrent.futures.ThreadPoolExecutor` ve :class:`~concurrent." -"futures.ProcessPoolExecutor` 'dan arka plan programı konuları kaldırıldı. " -"Bu, alt yorumlayıcılarla uyumluluğu ve kapatma süreçlerinde " -"öngörülebilirliği geliştirir. (Kyle Stanley tarafından :issue:`39812` 'de " -"katılmıştır.)" +":class:`~concurrent.futures.ThreadPoolExecutor` " +"ve :class:`~concurrent.futures.ProcessPoolExecutor` 'dan arka plan programı " +"konuları kaldırıldı. Bu, alt yorumlayıcılarla uyumluluğu ve kapatma " +"süreçlerinde öngörülebilirliği geliştirir. (Kyle Stanley " +"tarafından :issue:`39812` 'de katılmıştır.)" #: whatsnew/3.9.rst:397 msgid "" @@ -792,13 +797,13 @@ msgstr "curses" #: whatsnew/3.9.rst:405 msgid "" -"Added :func:`curses.get_escdelay`, :func:`curses.set_escdelay`, :func:" -"`curses.get_tabsize`, and :func:`curses.set_tabsize` functions. (Contributed " -"by Anthony Sottile in :issue:`38312`.)" +"Added :func:`curses.get_escdelay`, :func:`curses.set_escdelay`, :func:`curses.get_tabsize`, " +"and :func:`curses.set_tabsize` functions. (Contributed by Anthony Sottile " +"in :issue:`38312`.)" msgstr "" -":func:`curses.get_escdelay`, :func:`curses.set_escdelay`, :func:`curses." -"get_tabsize` ve :func:`curses.set_tabsize` işlevleri eklendi. (Anthony " -"Sottile tarafından :issue:`38312` 'de katılmıştır.)" +":func:`curses.get_escdelay`, :func:`curses.set_escdelay`, :func:`curses.get_tabsize` " +"ve :func:`curses.set_tabsize` işlevleri eklendi. (Anthony Sottile " +"tarafından :issue:`38312` 'de katılmıştır.)" #: whatsnew/3.9.rst:410 msgid "datetime" @@ -807,15 +812,16 @@ msgstr "datetime" #: whatsnew/3.9.rst:411 #, fuzzy msgid "" -"The :meth:`~datetime.date.isocalendar` of :class:`datetime.date` and :meth:" -"`~datetime.datetime.isocalendar` of :class:`datetime.datetime` methods now " -"returns a :func:`~collections.namedtuple` instead of a :class:`tuple`. " -"(Contributed by Donghee Na in :issue:`24416`.)" +"The :meth:`~datetime.date.isocalendar` of :class:`datetime.date` " +"and :meth:`~datetime.datetime.isocalendar` of :class:`datetime.datetime` " +"methods now returns a :func:`~collections.namedtuple` instead of " +"a :class:`tuple`. (Contributed by Donghee Na in :issue:`24416`.)" msgstr "" -":class:`datetime.date` öğesinin :meth:`~datetime.date.isocalendar()` ve :" -"class:`datetime.datetime` öğesinin :meth:`~datetime.datetime.isocalendar()` " -"metotları artık bir :class:`tuple` yerine :func:`~collections.namedtuple` " -"döndürüyor. (Dong-hee Na tarafından :issue:`24416` 'da katılmıştır.)" +":class:`datetime.date` öğesinin :meth:`~datetime.date.isocalendar()` " +"ve :class:`datetime.datetime` " +"öğesinin :meth:`~datetime.datetime.isocalendar()` metotları artık " +"bir :class:`tuple` yerine :func:`~collections.namedtuple` döndürüyor. (Dong-" +"hee Na tarafından :issue:`24416` 'da katılmıştır.)" #: whatsnew/3.9.rst:417 msgid "distutils" @@ -828,8 +834,8 @@ msgid "" "Christian Heimes in :issue:`40698`.)" msgstr "" ":command:`upload` komutu artık SHA2-256 ve Blake2b-256 hash özetleri " -"oluşturuyor. MD5 özetini engelleyen platformlarda MD5'i atlar. ( :issue:" -"`40698` içinde Christian Heimes tarafından katılmıştır.)" +"oluşturuyor. MD5 özetini engelleyen platformlarda MD5'i atlar. " +"( :issue:`40698` içinde Christian Heimes tarafından katılmıştır.)" #: whatsnew/3.9.rst:424 msgid "fcntl" @@ -839,12 +845,12 @@ msgstr "fcntl" #, fuzzy msgid "" "Added constants :const:`~fcntl.F_OFD_GETLK`, :const:`~fcntl.F_OFD_SETLK` " -"and :const:`~fcntl.F_OFD_SETLKW`. (Contributed by Donghee Na in :issue:" -"`38602`.)" +"and :const:`~fcntl.F_OFD_SETLKW`. (Contributed by Donghee Na " +"in :issue:`38602`.)" msgstr "" -":data:`~fcntl.F_OFD_GETLK`, :data:`~fcntl.F_OFD_SETLK` ve :data:`~fcntl." -"F_OFD_SETLKW` sabitleri eklendi. (Dong-hee Na tarafından :issue:`38602` 'de " -"katılmıştır.)" +":data:`~fcntl.F_OFD_GETLK`, :data:`~fcntl.F_OFD_SETLK` " +"ve :data:`~fcntl.F_OFD_SETLKW` sabitleri eklendi. (Dong-hee Na " +"tarafından :issue:`38602` 'de katılmıştır.)" #: whatsnew/3.9.rst:431 msgid "ftplib" @@ -853,15 +859,15 @@ msgstr "ftplib" #: whatsnew/3.9.rst:433 #, fuzzy msgid "" -":class:`~ftplib.FTP` and :class:`~ftplib.FTP_TLS` now raise a :class:" -"`ValueError` if the given timeout for their constructor is zero to prevent " -"the creation of a non-blocking socket. (Contributed by Donghee Na in :issue:" -"`39259`.)" +":class:`~ftplib.FTP` and :class:`~ftplib.FTP_TLS` now raise " +"a :class:`ValueError` if the given timeout for their constructor is zero to " +"prevent the creation of a non-blocking socket. (Contributed by Donghee Na " +"in :issue:`39259`.)" msgstr "" -":class:`~ftplib.FTP` ve :class:`~ftplib.FTP_TLS` artık bir :class:" -"`ValueError` oluşturucuları için verilen zaman aşımı sıfır ise bloke olmayan " -"bir soketin oluşturulmasını engelliyor. (Dong-hee Na tarafından :issue:" -"`39259` 'da katılmıştır.)" +":class:`~ftplib.FTP` ve :class:`~ftplib.FTP_TLS` artık " +"bir :class:`ValueError` oluşturucuları için verilen zaman aşımı sıfır ise " +"bloke olmayan bir soketin oluşturulmasını engelliyor. (Dong-hee Na " +"tarafından :issue:`39259` 'da katılmıştır.)" #: whatsnew/3.9.rst:438 msgid "gc" @@ -872,8 +878,8 @@ msgid "" "When the garbage collector makes a collection in which some objects " "resurrect (they are reachable from outside the isolated cycles after the " "finalizers have been executed), do not block the collection of all objects " -"that are still unreachable. (Contributed by Pablo Galindo and Tim Peters in :" -"issue:`38379`.)" +"that are still unreachable. (Contributed by Pablo Galindo and Tim Peters " +"in :issue:`38379`.)" msgstr "" "Çöp toplayıcı, bazı nesnelerin diriltildiği bir koleksiyon oluşturduğunda " "(sonlandırıcılar yürütüldükten sonra yalıtılmış döngülerin dışından " @@ -884,8 +890,8 @@ msgstr "" #: whatsnew/3.9.rst:445 msgid "" "Added a new function :func:`gc.is_finalized` to check if an object has been " -"finalized by the garbage collector. (Contributed by Pablo Galindo in :issue:" -"`39322`.)" +"finalized by the garbage collector. (Contributed by Pablo Galindo " +"in :issue:`39322`.)" msgstr "" "Bir nesnenin çöp toplayıcı tarafından sonlandırılıp sonlandırılmadığını " "kontrol etmek için :func:`gc.is_finalized` adlı yeni bir işlev eklendi. " @@ -913,9 +919,9 @@ msgid "" msgstr "" "Yerleşik karma modüller, OpenSSL tabanlı uygulamanın kullanımını zorlamak " "için artık ``./configure --without-builtin-hashlib-hashes`` ile devre dışı " -"bırakılabilir veya e.g. ``./configure --with-builtin-hashlib-hashes=sha3," -"blake2`` ile seçici olarak etkinleştirilebilir. (Christian Heimes " -"tarafından :issue:`40479` 'da katılmıştır)" +"bırakılabilir veya e.g. ``./configure --with-builtin-hashlib-" +"hashes=sha3,blake2`` ile seçici olarak etkinleştirilebilir. (Christian " +"Heimes tarafından :issue:`40479` 'da katılmıştır)" #: whatsnew/3.9.rst:464 msgid "http" @@ -938,8 +944,8 @@ msgstr "IDLE ve idlelib" #: whatsnew/3.9.rst:472 msgid "" -"Added option to toggle cursor blink off. (Contributed by Zackery Spytz in :" -"issue:`4603`.)" +"Added option to toggle cursor blink off. (Contributed by Zackery Spytz " +"in :issue:`4603`.)" msgstr "" "İmlecin yanıp sönmesini kapatmak için seçenek eklendi. ( :issue:`4603` " "içinde Zackery Spytz tarafından katılmıştır.)" @@ -967,8 +973,8 @@ msgstr "3.9 bakım sürümlerinde yenilikler" #: whatsnew/3.9.rst:483 msgid "" "Make IDLE invoke :func:`sys.excepthook` (when started without '-n'). User " -"hooks were previously ignored. (Contributed by Ken Hilton in :issue:" -"`43008`.)" +"hooks were previously ignored. (Contributed by Ken Hilton " +"in :issue:`43008`.)" msgstr "" "IDLE'yi başlatın :func:`sys.excepthook` ('-n' olmadan başlatıldığında). " "Kullanıcı kancaları daha önce yok sayılırdı. ( :issue:`43008` 'de Ken Hilton " @@ -983,10 +989,10 @@ msgid "" "Rearrange the settings dialog. Split the General tab into Windows and Shell/" "Ed tabs. Move help sources, which extend the Help menu, to the Extensions " "tab. Make space for new options and shorten the dialog. The latter makes " -"the dialog better fit small screens. (Contributed by Terry Jan Reedy in :" -"issue:`40468`.) Move the indent space setting from the Font tab to the new " -"Windows tab. (Contributed by Mark Roseman and Terry Jan Reedy in :issue:" -"`33962`.)" +"the dialog better fit small screens. (Contributed by Terry Jan Reedy " +"in :issue:`40468`.) Move the indent space setting from the Font tab to the " +"new Windows tab. (Contributed by Mark Roseman and Terry Jan Reedy " +"in :issue:`33962`.)" msgstr "" "Ayarlar iletişim kutusunu yeniden düzenleyin. Genel sekmesini Windows ve " "Kabuk/Ed sekmelerine ayırın. Yardım menüsünü genişleten yardım kaynaklarını " @@ -1012,18 +1018,19 @@ msgstr "imaplib" #, fuzzy msgid "" ":class:`~imaplib.IMAP4` and :class:`~imaplib.IMAP4_SSL` now have an optional " -"*timeout* parameter for their constructors. Also, the :meth:`~imaplib.IMAP4." -"open` method now has an optional *timeout* parameter with this change. The " -"overridden methods of :class:`~imaplib.IMAP4_SSL` and :class:`~imaplib." -"IMAP4_stream` were applied to this change. (Contributed by Donghee Na in :" -"issue:`38615`.)" +"*timeout* parameter for their constructors. Also, " +"the :meth:`~imaplib.IMAP4.open` method now has an optional *timeout* " +"parameter with this change. The overridden methods " +"of :class:`~imaplib.IMAP4_SSL` and :class:`~imaplib.IMAP4_stream` were " +"applied to this change. (Contributed by Donghee Na in :issue:`38615`.)" msgstr "" ":class:`~imaplib.IMAP4` ve :class:`~imaplib.IMAP4_SSL` artık kurucuları için " -"isteğe bağlı bir *timeout* parametresine sahip. Ayrıca, :meth:`~imaplib." -"IMAP4.open` yöntemi artık bu değişiklikle birlikte isteğe bağlı bir " -"*timeout* parametresine sahip. Bu değişikliğe geçersiz kılınan :class:" -"`~imaplib.IMAP4_SSL` ve :class:`~imaplib.IMAP4_stream` yöntemleri uygulandı. " -"(Dong-hee Na tarafından :issue:`38615` 'de katılmıştır.)" +"isteğe bağlı bir *timeout* parametresine sahip. " +"Ayrıca, :meth:`~imaplib.IMAP4.open` yöntemi artık bu değişiklikle birlikte " +"isteğe bağlı bir *timeout* parametresine sahip. Bu değişikliğe geçersiz " +"kılınan :class:`~imaplib.IMAP4_SSL` ve :class:`~imaplib.IMAP4_stream` " +"yöntemleri uygulandı. (Dong-hee Na tarafından :issue:`38615` 'de " +"katılmıştır.)" #: whatsnew/3.9.rst:510 #, fuzzy @@ -1037,10 +1044,10 @@ msgid "" msgstr "" ":meth:`imaplib.IMAP4.unselect` eklendi. :meth:`imaplib.IMAP4.unselect` " "sunucunun seçilen posta kutusuyla ilişkili kaynaklarını serbest bırakır ve " -"sunucuyu kimliği doğrulanmış duruma döndürür. Bu komut :meth:`imaplib.IMAP4." -"close` ile aynı eylemleri gerçekleştirir, tek fark şu anda seçili olan posta " -"kutusundan hiçbir mesajın kalıcı olarak kaldırılmamasıdır. (Dong-hee Na " -"tarafından :issue:`40375` 'de katılmıştır.)" +"sunucuyu kimliği doğrulanmış duruma döndürür. Bu " +"komut :meth:`imaplib.IMAP4.close` ile aynı eylemleri gerçekleştirir, tek " +"fark şu anda seçili olan posta kutusundan hiçbir mesajın kalıcı olarak " +"kaldırılmamasıdır. (Dong-hee Na tarafından :issue:`40375` 'de katılmıştır.)" #: whatsnew/3.9.rst:518 msgid "importlib" @@ -1048,15 +1055,15 @@ msgstr "importlib" #: whatsnew/3.9.rst:520 msgid "" -"To improve consistency with import statements, :func:`importlib.util." -"resolve_name` now raises :exc:`ImportError` instead of :exc:`ValueError` for " -"invalid relative import attempts. (Contributed by Ngalim Siregar in :issue:" -"`37444`.)" +"To improve consistency with import " +"statements, :func:`importlib.util.resolve_name` now " +"raises :exc:`ImportError` instead of :exc:`ValueError` for invalid relative " +"import attempts. (Contributed by Ngalim Siregar in :issue:`37444`.)" msgstr "" -"İçe aktarma ifadeleriyle tutarlılığı artırmak için :func:`importlib.util." -"resolve_name` artık geçersiz göreli içe aktarma girişimleri için :exc:" -"`ValueError` yerine :exc:`ImportError` değerini yükseltiyor. ( :issue:" -"`37444` içinde Ngalim Siregar tarafından katılmıştır.)" +"İçe aktarma ifadeleriyle tutarlılığı artırmak " +"için :func:`importlib.util.resolve_name` artık geçersiz göreli içe aktarma " +"girişimleri için :exc:`ValueError` yerine :exc:`ImportError` değerini " +"yükseltiyor. ( :issue:`37444` içinde Ngalim Siregar tarafından katılmıştır.)" #: whatsnew/3.9.rst:525 msgid "" @@ -1091,8 +1098,8 @@ msgstr "inspect" #: whatsnew/3.9.rst:539 msgid "" ":attr:`inspect.BoundArguments.arguments` is changed from ``OrderedDict`` to " -"regular dict. (Contributed by Inada Naoki in :issue:`36350` and :issue:" -"`39775`.)" +"regular dict. (Contributed by Inada Naoki in :issue:`36350` " +"and :issue:`39775`.)" msgstr "" ":attr:`inspect.BoundArguments.arguments`, ``OrderedDict`` yerine normal dict " "olarak değiştirildi. ( :issue:`36350` ve :issue:`39775` içinde Inada Naoki " @@ -1113,20 +1120,21 @@ msgstr "" #: whatsnew/3.9.rst:547 msgid "" "Scoped IPv6 addresses can be parsed using :class:`ipaddress.IPv6Address`. If " -"present, scope zone ID is available through the :attr:`~ipaddress." -"IPv6Address.scope_id` attribute. (Contributed by Oleksandr Pavliuk in :issue:" -"`34788`.)" +"present, scope zone ID is available through " +"the :attr:`~ipaddress.IPv6Address.scope_id` attribute. (Contributed by " +"Oleksandr Pavliuk in :issue:`34788`.)" msgstr "" "Kapsamlı IPv6 adresleri :class:`ipaddress.IPv6Address` kullanılarak " -"ayrıştırılabilir. Varsa, kapsam bölgesi kimliği :attr:`~ipaddress." -"IPv6Address.scope_id` özelliği aracılığıyla kullanılabilir. (Oleksandr " -"Pavliuk tarafından :issue:`34788` 'de katılmıştır.)" +"ayrıştırılabilir. Varsa, kapsam bölgesi " +"kimliği :attr:`~ipaddress.IPv6Address.scope_id` özelliği aracılığıyla " +"kullanılabilir. (Oleksandr Pavliuk tarafından :issue:`34788` 'de " +"katılmıştır.)" #: whatsnew/3.9.rst:551 msgid "" "Starting with Python 3.9.5 the :mod:`ipaddress` module no longer accepts any " -"leading zeros in IPv4 address strings. (Contributed by Christian Heimes in :" -"issue:`36384`)." +"leading zeros in IPv4 address strings. (Contributed by Christian Heimes " +"in :issue:`36384`)." msgstr "" "Python 3.9.5'ten itibaren :mod:`ipaddress` modülü artık IPv4 adres " "dizelerinde baştaki sıfırları kabul etmemektedir. ( :issue:`36384` içinde " @@ -1179,9 +1187,9 @@ msgstr "multiprocessing" #: whatsnew/3.9.rst:577 msgid "" -"The :class:`multiprocessing.SimpleQueue` class has a new :meth:" -"`~multiprocessing.SimpleQueue.close` method to explicitly close the queue. " -"(Contributed by Victor Stinner in :issue:`30966`.)" +"The :class:`multiprocessing.SimpleQueue` class has a " +"new :meth:`~multiprocessing.SimpleQueue.close` method to explicitly close " +"the queue. (Contributed by Victor Stinner in :issue:`30966`.)" msgstr "" ":class:`multiprocessing.SimpleQueue` sınıfı, kuyruğu açıkça kapatmak için " "yeni bir :meth:`~multiprocessing.SimpleQueue.close` yöntemine sahiptir. " @@ -1194,15 +1202,15 @@ msgstr "nntplib" #: whatsnew/3.9.rst:585 #, fuzzy msgid "" -":class:`~nntplib.NNTP` and :class:`~nntplib.NNTP_SSL` now raise a :class:" -"`ValueError` if the given timeout for their constructor is zero to prevent " -"the creation of a non-blocking socket. (Contributed by Donghee Na in :issue:" -"`39259`.)" +":class:`~nntplib.NNTP` and :class:`~nntplib.NNTP_SSL` now raise " +"a :class:`ValueError` if the given timeout for their constructor is zero to " +"prevent the creation of a non-blocking socket. (Contributed by Donghee Na " +"in :issue:`39259`.)" msgstr "" -":class:`~nntplib.NNTP` ve :class:`~nntplib.NNTP_SSL` artık bir :class:" -"`ValueError` oluşturucuları için verilen zaman aşımı sıfır ise bloke olmayan " -"bir yuvanın oluşturulmasını engelliyor. (Dong-hee Na tarafından :issue:" -"`39259` 'da katılmıştır.)" +":class:`~nntplib.NNTP` ve :class:`~nntplib.NNTP_SSL` artık " +"bir :class:`ValueError` oluşturucuları için verilen zaman aşımı sıfır ise " +"bloke olmayan bir yuvanın oluşturulmasını engelliyor. (Dong-hee Na " +"tarafından :issue:`39259` 'da katılmıştır.)" #: whatsnew/3.9.rst:590 msgid "os" @@ -1220,12 +1228,13 @@ msgstr "" #: whatsnew/3.9.rst:595 #, fuzzy msgid "" -"Exposed the Linux-specific :func:`os.pidfd_open` (:issue:`38692`) and :const:" -"`os.P_PIDFD` (:issue:`38713`) for process management with file descriptors." +"Exposed the Linux-specific :func:`os.pidfd_open` (:issue:`38692`) " +"and :const:`os.P_PIDFD` (:issue:`38713`) for process management with file " +"descriptors." msgstr "" -"Dosya tanımlayıcılarla süreç yönetimi için Linux'a özgü :func:`os." -"pidfd_open` (:issue:`38692`) ve :data:`os.P_PIDFD` (:issue:`38713`) " -"kullanıma sunuldu." +"Dosya tanımlayıcılarla süreç yönetimi için Linux'a " +"özgü :func:`os.pidfd_open` (:issue:`38692`) ve :data:`os.P_PIDFD` " +"(:issue:`38713`) kullanıma sunuldu." #: whatsnew/3.9.rst:599 msgid "" @@ -1259,11 +1268,12 @@ msgstr "pathlib" #: whatsnew/3.9.rst:613 #, fuzzy msgid "" -"Added :meth:`pathlib.Path.readlink` which acts similarly to :func:`os." -"readlink`. (Contributed by Girts Folkmanis in :issue:`30618`)" +"Added :meth:`pathlib.Path.readlink` which acts similarly " +"to :func:`os.readlink`. (Contributed by Girts Folkmanis in :issue:`30618`)" msgstr "" -":func:`os.readlink` 'e benzer şekilde davranan :meth:`pathlib.Path." -"readlink()` eklendi. (Girts Folkmanis'in katkılarıyla :issue:`30618`)" +":func:`os.readlink` 'e benzer şekilde " +"davranan :meth:`pathlib.Path.readlink()` eklendi. (Girts Folkmanis'in " +"katkılarıyla :issue:`30618`)" #: whatsnew/3.9.rst:618 msgid "pdb" @@ -1274,8 +1284,9 @@ msgid "" "On Windows now :class:`~pdb.Pdb` supports ``~/.pdbrc``. (Contributed by Tim " "Hopper and Dan Lidral-Porter in :issue:`20523`.)" msgstr "" -"Artık Windows'ta :class:`~pdb.Pdb` ``~/.pdbrc`` desteklemektedir. ( :issue:" -"`20523` içinde Tim Hopper ve Dan Lidral-Porter tarafından katılmıştır.)" +"Artık Windows'ta :class:`~pdb.Pdb` ``~/.pdbrc`` desteklemektedir. " +"( :issue:`20523` içinde Tim Hopper ve Dan Lidral-Porter tarafından " +"katılmıştır.)" #: whatsnew/3.9.rst:624 msgid "poplib" @@ -1284,15 +1295,15 @@ msgstr "poplib" #: whatsnew/3.9.rst:626 #, fuzzy msgid "" -":class:`~poplib.POP3` and :class:`~poplib.POP3_SSL` now raise a :class:" -"`ValueError` if the given timeout for their constructor is zero to prevent " -"the creation of a non-blocking socket. (Contributed by Donghee Na in :issue:" -"`39259`.)" +":class:`~poplib.POP3` and :class:`~poplib.POP3_SSL` now raise " +"a :class:`ValueError` if the given timeout for their constructor is zero to " +"prevent the creation of a non-blocking socket. (Contributed by Donghee Na " +"in :issue:`39259`.)" msgstr "" -":class:`~poplib.POP3` ve :class:`~poplib.POP3_SSL` artık bir :class:" -"`ValueError` oluşturucuları için verilen zaman aşımı sıfır ise bloke olmayan " -"bir yuva oluşturulmasını engelliyor. (Dong-hee Na tarafından :issue:`39259` " -"'da katılmıştır.)" +":class:`~poplib.POP3` ve :class:`~poplib.POP3_SSL` artık " +"bir :class:`ValueError` oluşturucuları için verilen zaman aşımı sıfır ise " +"bloke olmayan bir yuva oluşturulmasını engelliyor. (Dong-hee Na " +"tarafından :issue:`39259` 'da katılmıştır.)" #: whatsnew/3.9.rst:631 msgid "pprint" @@ -1340,12 +1351,12 @@ msgstr "signal" #: whatsnew/3.9.rst:653 msgid "" "Exposed the Linux-specific :func:`signal.pidfd_send_signal` for sending to " -"signals to a process using a file descriptor instead of a pid. (:issue:" -"`38712`)" +"signals to a process using a file descriptor instead of a pid. " +"(:issue:`38712`)" msgstr "" "Bir pid yerine bir dosya tanımlayıcı kullanarak bir işleme sinyal göndermek " -"için Linux'a özgü :func:`signal.pidfd_send_signal` ortaya çıktı. (:issue:" -"`38712`)" +"için Linux'a özgü :func:`signal.pidfd_send_signal` ortaya çıktı. " +"(:issue:`38712`)" #: whatsnew/3.9.rst:657 msgid "smtplib" @@ -1354,15 +1365,15 @@ msgstr "smtplib" #: whatsnew/3.9.rst:659 #, fuzzy msgid "" -":class:`~smtplib.SMTP` and :class:`~smtplib.SMTP_SSL` now raise a :class:" -"`ValueError` if the given timeout for their constructor is zero to prevent " -"the creation of a non-blocking socket. (Contributed by Donghee Na in :issue:" -"`39259`.)" +":class:`~smtplib.SMTP` and :class:`~smtplib.SMTP_SSL` now raise " +"a :class:`ValueError` if the given timeout for their constructor is zero to " +"prevent the creation of a non-blocking socket. (Contributed by Donghee Na " +"in :issue:`39259`.)" msgstr "" -":class:`~smtplib.SMTP` ve :class:`~smtplib.SMTP_SSL` artık bir :class:" -"`ValueError` oluşturucuları için verilen zaman aşımı sıfır ise bloke olmayan " -"bir soketin oluşturulmasını engelliyor. (Dong-hee Na tarafından :issue:" -"`39259` 'da katılmıştır.)" +":class:`~smtplib.SMTP` ve :class:`~smtplib.SMTP_SSL` artık " +"bir :class:`ValueError` oluşturucuları için verilen zaman aşımı sıfır ise " +"bloke olmayan bir soketin oluşturulmasını engelliyor. (Dong-hee Na " +"tarafından :issue:`39259` 'da katılmıştır.)" #: whatsnew/3.9.rst:663 #, fuzzy @@ -1380,13 +1391,14 @@ msgstr "socket" #: whatsnew/3.9.rst:669 #, fuzzy msgid "" -"The :mod:`socket` module now exports the :const:`~socket." -"CAN_RAW_JOIN_FILTERS` constant on Linux 4.1 and greater. (Contributed by " -"Stefan Tatschner and Zackery Spytz in :issue:`25780`.)" +"The :mod:`socket` module now exports " +"the :const:`~socket.CAN_RAW_JOIN_FILTERS` constant on Linux 4.1 and greater. " +"(Contributed by Stefan Tatschner and Zackery Spytz in :issue:`25780`.)" msgstr "" -":mod:`socket` modülü artık Linux 4.1 ve üzeri sürümlerde :data:`~socket." -"CAN_RAW_JOIN_FILTERS` sabitini dışa aktarıyor. (Stefan Tatschner ve Zackery " -"Spytz tarafından :issue:`25780` 'de katılmıştır.)" +":mod:`socket` modülü artık Linux 4.1 ve üzeri " +"sürümlerde :data:`~socket.CAN_RAW_JOIN_FILTERS` sabitini dışa aktarıyor. " +"(Stefan Tatschner ve Zackery Spytz tarafından :issue:`25780` 'de " +"katılmıştır.)" #: whatsnew/3.9.rst:673 #, fuzzy @@ -1400,9 +1412,9 @@ msgstr "" #: whatsnew/3.9.rst:676 msgid "" -"The socket module now has the :func:`socket.send_fds` and :func:`socket." -"recv_fds` functions. (Contributed by Joannah Nanjekye, Shinya Okano and " -"Victor Stinner in :issue:`28724`.)" +"The socket module now has the :func:`socket.send_fds` " +"and :func:`socket.recv_fds` functions. (Contributed by Joannah Nanjekye, " +"Shinya Okano and Victor Stinner in :issue:`28724`.)" msgstr "" "Soket modülü artık :func:`socket.send_fds` ve :func:`socket.recv_fds` " "fonksiyonlarına sahiptir. (Joannah Nanjekye, Shinya Okano ve Victor " @@ -1421,8 +1433,8 @@ msgid "" msgstr "" "AIX üzerinde :func:`~time.thread_time` artık 10 milisaniye çözünürlüğe sahip " "``clock_gettime(CLOCK_THREAD_CPUTIME_ID)`` yerine nanosaniye çözünürlüğe " -"sahip ``thread_cputime()`` ile uygulanmaktadır. (Batuhan Taşkaya :issue:" -"`40192` 'de katılmıştır)" +"sahip ``thread_cputime()`` ile uygulanmaktadır. (Batuhan " +"Taşkaya :issue:`40192` 'de katılmıştır)" #: whatsnew/3.9.rst:690 msgid "sys" @@ -1481,8 +1493,8 @@ msgid "" "to :func:`typing.get_type_hints` to access the metadata at runtime. " "(Contributed by Till Varoquaux and Konstantin Kashin.)" msgstr "" -":pep:`593`, mevcut türleri bağlama özel meta verilerle süslemek için bir :" -"data:`typing.Annotated` tipi ve çalışma zamanında meta verilere erişmek " +":pep:`593`, mevcut türleri bağlama özel meta verilerle süslemek için " +"bir :data:`typing.Annotated` tipi ve çalışma zamanında meta verilere erişmek " "için :func:`typing.get_type_hints` için yeni ``include_extras`` " "parametresini tanıttı. (Till Varoquaux ve Konstantin Kashin'in katkılarıyla.)" @@ -1521,10 +1533,11 @@ msgstr "xml" #: whatsnew/3.9.rst:735 msgid "" -"White space characters within attributes are now preserved when serializing :" -"mod:`xml.etree.ElementTree` to XML file. EOLNs are no longer normalized to " -"\"\\n\". This is the result of discussion about how to interpret section " -"2.11 of XML spec. (Contributed by Mefistotelis in :issue:`39011`.)" +"White space characters within attributes are now preserved when " +"serializing :mod:`xml.etree.ElementTree` to XML file. EOLNs are no longer " +"normalized to \"\\n\". This is the result of discussion about how to " +"interpret section 2.11 of XML spec. (Contributed by Mefistotelis " +"in :issue:`39011`.)" msgstr "" "Nitelikler içindeki boşluk karakterleri artık :mod:`xml.etree.ElementTree` " "XML dosyasına serileştirilirken korunur. EOLN'ler artık \"\\n\" olarak " @@ -1577,12 +1590,12 @@ msgstr "" #: whatsnew/3.9.rst:762 msgid "" "Previously, the bytecode evaluation loop was interrupted at each instruction " -"until the main thread handles signals. (Contributed by Victor Stinner in :" -"issue:`40010`.)" +"until the main thread handles signals. (Contributed by Victor Stinner " +"in :issue:`40010`.)" msgstr "" "Önceden, bayt kodu değerlendirme döngüsü, ana iş parçacığı sinyalleri " -"işleyene kadar her komutta kesintiye uğruyordu. (Victor Stinner tarafından :" -"issue:`40010` 'da katılmıştır.)" +"işleyene kadar her komutta kesintiye uğruyordu. (Victor Stinner " +"tarafından :issue:`40010` 'da katılmıştır.)" #: whatsnew/3.9.rst:766 msgid "" @@ -1606,15 +1619,17 @@ msgstr "" #: whatsnew/3.9.rst:774 #, fuzzy msgid "" -"A number of Python builtins (:class:`range`, :class:`tuple`, :class:`set`, :" -"class:`frozenset`, :class:`list`, :class:`dict`) are now sped up by using :" -"pep:`590` vectorcall protocol. (Contributed by Donghee Na, Mark Shannon, " -"Jeroen Demeyer and Petr Viktorin in :issue:`37207`.)" +"A number of Python builtins " +"(:class:`range`, :class:`tuple`, :class:`set`, :class:`frozenset`, :class:`list`, :class:`dict`) " +"are now sped up by using :pep:`590` vectorcall protocol. (Contributed by " +"Donghee Na, Mark Shannon, Jeroen Demeyer and Petr Viktorin " +"in :issue:`37207`.)" msgstr "" -"Bir dizi Python yerleşik yapısı (:class:`range`, :class:`tuple`, :class:" -"`set`, :class:`frozenset`, :class:`list`, :class:`dict`) artık :pep:`590` " -"vectorcall protokolü kullanılarak hızlandırıldı. (Dong-hee Na, Mark Shannon, " -"Jeroen Demeyer ve Petr Viktorin'in :issue:`37207` 'deki katkılarıyla.)" +"Bir dizi Python yerleşik yapısı " +"(:class:`range`, :class:`tuple`, :class:`set`, :class:`frozenset`, :class:`list`, :class:`dict`) " +"artık :pep:`590` vectorcall protokolü kullanılarak hızlandırıldı. (Dong-hee " +"Na, Mark Shannon, Jeroen Demeyer ve Petr Viktorin'in :issue:`37207` 'deki " +"katkılarıyla.)" #: whatsnew/3.9.rst:779 msgid "" @@ -1622,9 +1637,9 @@ msgid "" "much larger than the base set. (Suggested by Evgeny Kapun with code " "contributed by Michele Orrù in :issue:`8425`.)" msgstr "" -"Diğer kümenin temel kümeden çok daha büyük olduğu durumlar için :func:`~set." -"difference_update` optimize edildi. ( :issue:`8425` içinde Michele Orrù " -"tarafından sağlanan kodla Evgeny Kapun tarafından önerilmiştir.)" +"Diğer kümenin temel kümeden çok daha büyük olduğu durumlar " +"için :func:`~set.difference_update` optimize edildi. ( :issue:`8425` içinde " +"Michele Orrù tarafından sağlanan kodla Evgeny Kapun tarafından önerilmiştir.)" #: whatsnew/3.9.rst:783 msgid "" @@ -1637,8 +1652,8 @@ msgstr "" "Python'un küçük nesne ayırıcısı (``obmalloc.c``) artık (1'den fazla değil) " "bir boş arenanın işletim sistemine döndürmeden anında yeniden kullanım için " "kullanılabilir kalmasına izin veriyor. Bu, her yinelemede bir arenanın " -"yeniden yaratılıp yok edilebileceği basit döngülerde çarpışmayı önler. ( :" -"issue:`37257` içinde Tim Peters tarafından katılmıştır.)" +"yeniden yaratılıp yok edilebileceği basit döngülerde çarpışmayı önler. " +"( :issue:`37257` içinde Tim Peters tarafından katılmıştır.)" #: whatsnew/3.9.rst:789 #, fuzzy @@ -1750,17 +1765,17 @@ msgid "" "These results were generated from the variable access benchmark script at: " "``Tools/scripts/var_access_benchmark.py``. The benchmark script displays " "timings in nanoseconds. The benchmarks were measured on an `Intel® Core™ " -"i7-4960HQ processor `_ running the macOS 64-bit builds found at `python.org `_." +"i7-4960HQ processor `_ running " +"the macOS 64-bit builds found at `python.org `_." msgstr "" "Bu sonuçlar, ``Tools/scripts/var_access_benchmark.py`` adresindeki değişken " "erişim kıyaslama betiğinden oluşturulmuştur. Kıyaslama komut dosyası, " "nanosaniye cinsinden zamanlamaları görüntüler. Kıyaslamalar, `python.org " "`_ adresinde bulunan macOS 64-bit " -"yapılarını çalıştıran bir `Intel® Core™ i7-4960HQ processor `_ üzerinde ölçülmüştür." #: whatsnew/3.9.rst:853 @@ -1770,8 +1785,8 @@ msgstr "Deprecated" #: whatsnew/3.9.rst:855 msgid "" "The distutils ``bdist_msi`` command is now deprecated, use ``bdist_wheel`` " -"(wheel packages) instead. (Contributed by Hugo van Kemenade in :issue:" -"`39586`.)" +"(wheel packages) instead. (Contributed by Hugo van Kemenade " +"in :issue:`39586`.)" msgstr "" "Distutils ``bdist_msi`` komutu artık kullanımdan kaldırılmıştır, bunun " "yerine ``bdist_wheel`` (tekerlek paketleri) kullanın. ( :issue:`39586` " @@ -1808,15 +1823,16 @@ msgstr "" #: whatsnew/3.9.rst:870 #, fuzzy msgid "" -"The Public C API functions :c:func:`!PyParser_SimpleParseStringFlags`, :c:" -"func:`!PyParser_SimpleParseStringFlagsFilename`, :c:func:`!" +"The Public C API functions :c:func:`!" +"PyParser_SimpleParseStringFlags`, :c:func:`!" +"PyParser_SimpleParseStringFlagsFilename`, :c:func:`!" "PyParser_SimpleParseFileFlags` and :c:func:`!PyNode_Compile` are deprecated " "and will be removed in Python 3.10 together with the old parser." msgstr "" -"Genel C API işlevleri :c:func:`PyParser_SimpleParseStringFlags`, :c:func:" -"`PyParser_SimpleParseStringFlagsFilename`, :c:func:" -"`PyParser_SimpleParseFileFlags` ve :c:func:`PyNode_Compile` eskimiştir ve " -"Python 3.10'da eski ayrıştırıcı ile birlikte kaldırılacaktır." +"Genel C API " +"işlevleri :c:func:`PyParser_SimpleParseStringFlags`, :c:func:`PyParser_SimpleParseStringFlagsFilename`, :c:func:`PyParser_SimpleParseFileFlags` " +"ve :c:func:`PyNode_Compile` eskimiştir ve Python 3.10'da eski ayrıştırıcı " +"ile birlikte kaldırılacaktır." #: whatsnew/3.9.rst:875 msgid "" @@ -1827,38 +1843,39 @@ msgid "" msgstr "" "Bir boole bağlamında :data:`NotImplemented` kullanmak, neredeyse tamamen " "yanlış zengin karşılaştırıcı uygulamalarının bir sonucu olduğu için " -"kullanımdan kaldırılmıştır. Python'un gelecekteki bir sürümünde :exc:" -"`TypeError` haline getirilecektir. ( :issue:`35712` içinde Josh Rosenberg " -"tarafından katılmıştır.)" +"kullanımdan kaldırılmıştır. Python'un gelecekteki bir " +"sürümünde :exc:`TypeError` haline getirilecektir. ( :issue:`35712` içinde " +"Josh Rosenberg tarafından katılmıştır.)" #: whatsnew/3.9.rst:881 msgid "" "The :mod:`random` module currently accepts any hashable type as a possible " "seed value. Unfortunately, some of those types are not guaranteed to have a " "deterministic hash value. After Python 3.9, the module will restrict its " -"seeds to :const:`None`, :class:`int`, :class:`float`, :class:`str`, :class:" -"`bytes`, and :class:`bytearray`." +"seeds " +"to :const:`None`, :class:`int`, :class:`float`, :class:`str`, :class:`bytes`, " +"and :class:`bytearray`." msgstr "" ":mod:`random` modülü şu anda herhangi bir hashable türünü olası bir tohum " "değeri olarak kabul ediyor. Ne yazık ki, bu türlerden bazılarının " "deterministik bir hash değerine sahip olduğu garanti edilmiyor. Python " -"3.9'dan sonra, modül tohumlarını :const:`None`, :class:`int`, :class:" -"`float`, :class:`str`, :class:`bytes` ve :class:`bytearray` " -"ilesınırlayacaktır." +"3.9'dan sonra, modül " +"tohumlarını :const:`None`, :class:`int`, :class:`float`, :class:`str`, :class:`bytes` " +"ve :class:`bytearray` ilesınırlayacaktır." #: whatsnew/3.9.rst:887 msgid "" "Opening the :class:`~gzip.GzipFile` file for writing without specifying the " "*mode* argument is deprecated. In future Python versions it will always be " "opened for reading by default. Specify the *mode* argument for opening it " -"for writing and silencing a warning. (Contributed by Serhiy Storchaka in :" -"issue:`28286`.)" +"for writing and silencing a warning. (Contributed by Serhiy Storchaka " +"in :issue:`28286`.)" msgstr "" ":class:`~gzip.GzipFile` dosyasının *mode* bağımsız değişkeni belirtilmeden " "yazmak için açılması kullanımdan kaldırılmıştır. Gelecekteki Python " "sürümlerinde, her zaman varsayılan olarak okumak için açılacaktır. Bir uyarı " -"yazmak ve susturmak için açmak için *mode* argümanını belirtin. ( :issue:" -"`28286` içinde Serhiy Storchaka tarafından katılmıştır.)" +"yazmak ve susturmak için açmak için *mode* argümanını belirtin. " +"( :issue:`28286` içinde Serhiy Storchaka tarafından katılmıştır.)" #: whatsnew/3.9.rst:893 #, fuzzy @@ -1887,9 +1904,9 @@ msgid "" "binhex4 and hexbin4 standards are now deprecated. The :mod:`!binhex` module " "and the following :mod:`binascii` functions are now deprecated:" msgstr "" -"binhex4 ve hexbin4 standartları artık kullanımdan kaldırılmıştır. :mod:" -"`binhex` modülü ve aşağıdaki :mod:`binascii` fonksiyonları artık kullanımdan " -"kaldırılmıştır:" +"binhex4 ve hexbin4 standartları artık kullanımdan " +"kaldırılmıştır. :mod:`binhex` modülü ve aşağıdaki :mod:`binascii` " +"fonksiyonları artık kullanımdan kaldırılmıştır:" #: whatsnew/3.9.rst:905 #, fuzzy @@ -1924,8 +1941,8 @@ msgid "" ":mod:`ast` classes ``Suite``, ``Param``, ``AugLoad`` and ``AugStore`` are " "considered deprecated and will be removed in future Python versions. They " "were not generated by the parser and not accepted by the code generator in " -"Python 3. (Contributed by Batuhan Taskaya in :issue:`39639` and :issue:" -"`39969` and Serhiy Storchaka in :issue:`39988`.)" +"Python 3. (Contributed by Batuhan Taskaya in :issue:`39639` " +"and :issue:`39969` and Serhiy Storchaka in :issue:`39988`.)" msgstr "" ":mod:`ast` sınıfları ``Suite``, ``Param``, ``AugLoad`` ve ``AugStore`` " "kullanımdan kaldırılmış kabul edilir ve gelecekteki Python sürümlerinde " @@ -1938,10 +1955,10 @@ msgstr "" #, fuzzy msgid "" "The :c:func:`!PyEval_InitThreads` and :c:func:`!PyEval_ThreadsInitialized` " -"functions are now deprecated and will be removed in Python 3.11. Calling :c:" -"func:`!PyEval_InitThreads` now does nothing. The :term:`GIL` is initialized " -"by :c:func:`Py_Initialize` since Python 3.7. (Contributed by Victor Stinner " -"in :issue:`39877`.)" +"functions are now deprecated and will be removed in Python 3.11. " +"Calling :c:func:`!PyEval_InitThreads` now does nothing. The :term:`GIL` is " +"initialized by :c:func:`Py_Initialize` since Python 3.7. (Contributed by " +"Victor Stinner in :issue:`39877`.)" msgstr "" ":c:func:`PyEval_InitThreads` ve :c:func:`PyEval_ThreadsInitialized` " "işlevleri artık kullanımdan kaldırılmıştır ve Python 3.11'de " @@ -1963,8 +1980,8 @@ msgstr "" #, fuzzy msgid "" ":func:`!smtpd.MailmanProxy` is now deprecated as it is unusable without an " -"external module, ``mailman``. (Contributed by Samuel Colvin in :issue:" -"`35800`.)" +"external module, ``mailman``. (Contributed by Samuel Colvin " +"in :issue:`35800`.)" msgstr "" ":func:`smtpd.MailmanProxy`, harici bir modül olan ``mailman`` olmadan " "kullanılamaz olduğundan artık kullanımdan kaldırılmıştır. (Samuel Colvin " @@ -1984,8 +2001,8 @@ msgstr "" "lib2to3'ün LL(1) ayrıştırıcısı tarafından ayrıştırılamayan yeni dil " "sözdizimini içerebilir. ``lib2to3`` modülü, gelecekteki bir Python sürümünde " "standart kitaplıktan kaldırılabilir. `LibCST`_ veya `parso`_ gibi üçüncü " -"taraf alternatiflerini göz önünde bulundurun. (Carl Meyer tarafından :issue:" -"`40360` 'da katılmıştır.)" +"taraf alternatiflerini göz önünde bulundurun. (Carl Meyer " +"tarafından :issue:`40360` 'da katılmıştır.)" #: whatsnew/3.9.rst:943 msgid "" @@ -2011,15 +2028,16 @@ msgid "" ":class:`nntplib.NNTP`: ``xpath()`` and ``xgtitle()`` methods have been " "removed. These methods are deprecated since Python 3.3. Generally, these " "extensions are not supported or not enabled by NNTP server administrators. " -"For ``xgtitle()``, please use :meth:`nntplib.NNTP.descriptions` or :meth:" -"`nntplib.NNTP.description` instead. (Contributed by Donghee Na in :issue:" -"`39366`.)" +"For ``xgtitle()``, please use :meth:`nntplib.NNTP.descriptions` " +"or :meth:`nntplib.NNTP.description` instead. (Contributed by Donghee Na " +"in :issue:`39366`.)" msgstr "" ":class:`nntplib.NNTP`: ``xpath()`` ve ``xgtitle()`` yöntemleri kaldırıldı. " "Bu yöntemler Python 3.3'ten beri kullanımdan kaldırılmıştır. Genel olarak, " "bu uzantılar NNTP sunucu yöneticileri tarafından desteklenmez veya " -"etkinleştirilmez. ``xgtitle()`` için lütfen bunun yerine :meth:`nntplib.NNTP." -"descriptions` veya :meth:`nntplib.NNTP.description` kullanın. (Dong-hee Na " +"etkinleştirilmez. ``xgtitle()`` için lütfen bunun " +"yerine :meth:`nntplib.NNTP.descriptions` " +"veya :meth:`nntplib.NNTP.description` kullanın. (Dong-hee Na " "tarafından :issue:`39366` 'da katılmıştır.)" #: whatsnew/3.9.rst:963 @@ -2048,14 +2066,14 @@ msgstr "" #: whatsnew/3.9.rst:973 msgid "" "The ``sys.getcheckinterval()`` and ``sys.setcheckinterval()`` functions have " -"been removed. They were deprecated since Python 3.2. Use :func:`sys." -"getswitchinterval` and :func:`sys.setswitchinterval` instead. (Contributed " -"by Victor Stinner in :issue:`37392`.)" +"been removed. They were deprecated since Python 3.2. " +"Use :func:`sys.getswitchinterval` and :func:`sys.setswitchinterval` instead. " +"(Contributed by Victor Stinner in :issue:`37392`.)" msgstr "" "``sys.getcheckinterval()`` ve ``sys.setcheckinterval()`` işlevleri " -"kaldırıldı. Python 3.2'den beri kullanımdan kaldırıldılar. Bunun yerine :" -"func:`sys.getswitchinterval` ve :func:`sys.setswitchinterval` kullanın. " -"(Victor Stinner tarafından :issue:`37392` 'de katılmıştır.)" +"kaldırıldı. Python 3.2'den beri kullanımdan kaldırıldılar. Bunun " +"yerine :func:`sys.getswitchinterval` ve :func:`sys.setswitchinterval` " +"kullanın. (Victor Stinner tarafından :issue:`37392` 'de katılmıştır.)" #: whatsnew/3.9.rst:978 msgid "" @@ -2098,40 +2116,43 @@ msgid "" "instead. (Contributed by Donghee Na in :issue:`37804`.)" msgstr "" ":meth:`~threading.Thread.isAlive()` :class:`threading.Thread` yöntemi " -"kaldırıldı. Python 3.8'den beri kullanımdan kaldırılmıştır. Bunun yerine :" -"meth:`~threading.Thread.is_alive()` kullanın. (Dong-hee Na tarafından :issue:" -"`37804` 'de katılmıştır.)" +"kaldırıldı. Python 3.8'den beri kullanımdan kaldırılmıştır. Bunun " +"yerine :meth:`~threading.Thread.is_alive()` kullanın. (Dong-hee Na " +"tarafından :issue:`37804` 'de katılmıştır.)" #: whatsnew/3.9.rst:996 msgid "" -"Methods ``getchildren()`` and ``getiterator()`` of classes :class:`~xml." -"etree.ElementTree.ElementTree` and :class:`~xml.etree.ElementTree.Element` " -"in the :mod:`~xml.etree.ElementTree` module have been removed. They were " -"deprecated in Python 3.2. Use ``iter(x)`` or ``list(x)`` instead of ``x." -"getchildren()`` and ``x.iter()`` or ``list(x.iter())`` instead of ``x." -"getiterator()``. (Contributed by Serhiy Storchaka in :issue:`36543`.)" -msgstr "" -":mod:`~xml.etree.ElementTree` modülündeki :class:`~xml.etree.ElementTree." -"ElementTree` ve :class:`~xml.etree.ElementTree.Element` sınıflarının " -"``getchildren()`` ve ``getiterator()`` yöntemleri kaldırıldı . Python 3.2'de " -"kullanımdan kaldırıldılar. ``x.getchildren()`` yerine ``iter(x)`` ve ``x." -"getiterator()`` yerine ``x.iter()`` veya ``list(x.iter())`` kullanın. ( :" -"issue:`36543` içinde Serhiy Storchaka tarafından katılmıştır.)" +"Methods ``getchildren()`` and ``getiterator()`` of " +"classes :class:`~xml.etree.ElementTree.ElementTree` " +"and :class:`~xml.etree.ElementTree.Element` in " +"the :mod:`~xml.etree.ElementTree` module have been removed. They were " +"deprecated in Python 3.2. Use ``iter(x)`` or ``list(x)`` instead of " +"``x.getchildren()`` and ``x.iter()`` or ``list(x.iter())`` instead of " +"``x.getiterator()``. (Contributed by Serhiy Storchaka in :issue:`36543`.)" +msgstr "" +":mod:`~xml.etree.ElementTree` " +"modülündeki :class:`~xml.etree.ElementTree.ElementTree` " +"ve :class:`~xml.etree.ElementTree.Element` sınıflarının ``getchildren()`` ve " +"``getiterator()`` yöntemleri kaldırıldı . Python 3.2'de kullanımdan " +"kaldırıldılar. ``x.getchildren()`` yerine ``iter(x)`` ve ``x.getiterator()`` " +"yerine ``x.iter()`` veya ``list(x.iter())`` kullanın. ( :issue:`36543` " +"içinde Serhiy Storchaka tarafından katılmıştır.)" #: whatsnew/3.9.rst:1004 msgid "" "The old :mod:`plistlib` API has been removed, it was deprecated since Python " -"3.4. Use the :func:`~plistlib.load`, :func:`~plistlib.loads`, :func:" -"`~plistlib.dump`, and :func:`~plistlib.dumps` functions. Additionally, the " -"*use_builtin_types* parameter was removed, standard :class:`bytes` objects " -"are always used instead. (Contributed by Jon Janzen in :issue:`36409`.)" +"3.4. Use " +"the :func:`~plistlib.load`, :func:`~plistlib.loads`, :func:`~plistlib.dump`, " +"and :func:`~plistlib.dumps` functions. Additionally, the *use_builtin_types* " +"parameter was removed, standard :class:`bytes` objects are always used " +"instead. (Contributed by Jon Janzen in :issue:`36409`.)" msgstr "" "Eski :mod:`plistlib` API'si kaldırıldı, Python 3.4'ten beri kullanımdan " -"kaldırıldı. :func:`~plistlib.load`, :func:`~plistlib.loads`, :func:" -"`~plistlib.dump` ve :func:`~plistlib.dumps` işlevlerini kullanın. Ek olarak, " -"*use_builtin_types* parametresi kaldırıldı, bunun yerine her zaman standart :" -"class:`bytes` nesneleri kullanıldı. (Jon Janzen tarafından :issue:`36409` " -"'da katılmıştır.)" +"kaldırıldı. :func:`~plistlib.load`, :func:`~plistlib.loads`, :func:`~plistlib.dump` " +"ve :func:`~plistlib.dumps` işlevlerini kullanın. Ek olarak, " +"*use_builtin_types* parametresi kaldırıldı, bunun yerine her zaman " +"standart :class:`bytes` nesneleri kullanıldı. (Jon Janzen " +"tarafından :issue:`36409` 'da katılmıştır.)" #: whatsnew/3.9.rst:1010 msgid "" @@ -2148,14 +2169,14 @@ msgstr "" #: whatsnew/3.9.rst:1015 msgid "" "``base64.encodestring()`` and ``base64.decodestring()``, aliases deprecated " -"since Python 3.1, have been removed: use :func:`base64.encodebytes` and :" -"func:`base64.decodebytes` instead. (Contributed by Victor Stinner in :issue:" -"`39351`.)" +"since Python 3.1, have been removed: use :func:`base64.encodebytes` " +"and :func:`base64.decodebytes` instead. (Contributed by Victor Stinner " +"in :issue:`39351`.)" msgstr "" "Python 3.1'den beri kullanımdan kaldırılan ``base64.encodestring()`` ve " -"``base64.decodestring()`` takma adları kaldırıldı: bunun yerine :func:" -"`base64.encodebytes` ve :func:`base64.decodebytes` kullanın. (Victor Stinner " -"tarafından :issue:`39351` 'de katılmıştır.)" +"``base64.decodestring()`` takma adları kaldırıldı: bunun " +"yerine :func:`base64.encodebytes` ve :func:`base64.decodebytes` kullanın. " +"(Victor Stinner tarafından :issue:`39351` 'de katılmıştır.)" #: whatsnew/3.9.rst:1020 msgid "" @@ -2182,9 +2203,9 @@ msgstr "" #: whatsnew/3.9.rst:1029 msgid "" "The *encoding* parameter of :func:`json.loads` has been removed. As of " -"Python 3.1, it was deprecated and ignored; using it has emitted a :exc:" -"`DeprecationWarning` since Python 3.8. (Contributed by Inada Naoki in :issue:" -"`39377`)" +"Python 3.1, it was deprecated and ignored; using it has emitted " +"a :exc:`DeprecationWarning` since Python 3.8. (Contributed by Inada Naoki " +"in :issue:`39377`)" msgstr "" ":func:`json.loads` öğesinin *encoding* parametresi kaldırıldı. Python " "3.1'den itibaren kullanımdan kaldırıldı ve göz ardı edildi; onu kullanmak " @@ -2207,10 +2228,10 @@ msgstr "" #, fuzzy msgid "" "The :func:`!sys.getcounts` function, the ``-X showalloccount`` command line " -"option and the ``show_alloc_count`` field of the C structure :c:type:" -"`PyConfig` have been removed. They required a special Python build by " -"defining ``COUNT_ALLOCS`` macro. (Contributed by Victor Stinner in :issue:" -"`39489`.)" +"option and the ``show_alloc_count`` field of the C " +"structure :c:type:`PyConfig` have been removed. They required a special " +"Python build by defining ``COUNT_ALLOCS`` macro. (Contributed by Victor " +"Stinner in :issue:`39489`.)" msgstr "" "C yapısının :func:`sys.getcounts` işlevi, ``-X showalloccount`` komut satırı " "seçeneği ve :c:type:`PyConfig` ``show_alloc_count`` alanı kaldırıldı. " @@ -2221,13 +2242,13 @@ msgstr "" msgid "" "The ``_field_types`` attribute of the :class:`typing.NamedTuple` class has " "been removed. It was deprecated since Python 3.8. Use the " -"``__annotations__`` attribute instead. (Contributed by Serhiy Storchaka in :" -"issue:`40182`.)" +"``__annotations__`` attribute instead. (Contributed by Serhiy Storchaka " +"in :issue:`40182`.)" msgstr "" ":class:`typing.NamedTuple` sınıfının ``_field_types`` özniteliği kaldırıldı. " "Python 3.8'den beri kullanımdan kaldırılmıştır. Bunun yerine " -"``__annotations__`` özelliğini kullanın. (Serhiy Storchaka'nın :issue:" -"`40182` 'deki katkısıyla)" +"``__annotations__`` özelliğini kullanın. (Serhiy " +"Storchaka'nın :issue:`40182` 'deki katkısıyla)" #: whatsnew/3.9.rst:1050 #, fuzzy @@ -2244,14 +2265,14 @@ msgstr "" #, fuzzy msgid "" "The :meth:`!asyncio.Task.current_task` and :meth:`!asyncio.Task.all_tasks` " -"have been removed. They were deprecated since Python 3.7 and you can use :" -"func:`asyncio.current_task` and :func:`asyncio.all_tasks` instead. " +"have been removed. They were deprecated since Python 3.7 and you can " +"use :func:`asyncio.current_task` and :func:`asyncio.all_tasks` instead. " "(Contributed by Rémi Lapeyre in :issue:`40967`)" msgstr "" ":meth:`asyncio.Task.current_task` ve :meth:`asyncio.Task.all_tasks` " -"kaldırıldı. Python 3.7'den beri kullanımdan kaldırıldılar ve bunun yerine :" -"func:`asyncio.current_task` ve :func:`asyncio.all_tasks` kullanabilirsiniz. " -"(Rémi Lapeyre tarafından :issue:`40967` 'de katılmıştır)" +"kaldırıldı. Python 3.7'den beri kullanımdan kaldırıldılar ve bunun " +"yerine :func:`asyncio.current_task` ve :func:`asyncio.all_tasks` " +"kullanabilirsiniz. (Rémi Lapeyre tarafından :issue:`40967` 'de katılmıştır)" #: whatsnew/3.9.rst:1059 msgid "" @@ -2283,13 +2304,14 @@ msgstr "Python API'sindeki Değişiklikler" #: whatsnew/3.9.rst:1075 msgid "" -":func:`__import__` and :func:`importlib.util.resolve_name` now raise :exc:" -"`ImportError` where it previously raised :exc:`ValueError`. Callers catching " -"the specific exception type and supporting both Python 3.9 and earlier " -"versions will need to catch both using ``except (ImportError, ValueError):``." +":func:`__import__` and :func:`importlib.util.resolve_name` now " +"raise :exc:`ImportError` where it previously raised :exc:`ValueError`. " +"Callers catching the specific exception type and supporting both Python 3.9 " +"and earlier versions will need to catch both using ``except (ImportError, " +"ValueError):``." msgstr "" -":func:`__import__` ve :func:`importlib.util.resolve_name` şimdi daha önce :" -"exc:`ValueError` oluşturduğu yerde :exc:`ImportError` 'u yükseltiyor. " +":func:`__import__` ve :func:`importlib.util.resolve_name` şimdi daha " +"önce :exc:`ValueError` oluşturduğu yerde :exc:`ImportError` 'u yükseltiyor. " "Belirli istisna türünü yakalayan ve hem Python 3.9 hem de önceki sürümleri " "destekleyen arayanların, ``except (ImportError, ValueError):`` kullanarak " "her ikisini de yakalaması gerekir." @@ -2305,8 +2327,9 @@ msgstr "" #: whatsnew/3.9.rst:1083 #, fuzzy msgid "" -"The :meth:`select.epoll.unregister` method no longer ignores the :const:" -"`~errno.EBADF` error. (Contributed by Victor Stinner in :issue:`39239`.)" +"The :meth:`select.epoll.unregister` method no longer ignores " +"the :const:`~errno.EBADF` error. (Contributed by Victor Stinner " +"in :issue:`39239`.)" msgstr "" ":meth:`select.epoll.unregister` yöntemi artık :data:`~errno.EBADF` hatasını " "yok saymıyor. (Victor Stinner tarafından :issue:`39239` 'da katılmıştır.)" @@ -2355,15 +2378,14 @@ msgstr "" #: whatsnew/3.9.rst:1105 msgid "" -":meth:`asyncio.loop.shutdown_default_executor` has been added to :class:" -"`~asyncio.AbstractEventLoop`, meaning alternative event loops that inherit " -"from it should have this method defined. (Contributed by Kyle Stanley in :" -"issue:`34037`.)" +":meth:`asyncio.loop.shutdown_default_executor` has been added " +"to :class:`~asyncio.AbstractEventLoop`, meaning alternative event loops that " +"inherit from it should have this method defined. (Contributed by Kyle " +"Stanley in :issue:`34037`.)" msgstr "" -":meth:`asyncio.loop.shutdown_default_executor`, :class:`~asyncio." -"AbstractEventLoop` öğesine eklendi, yani ondan devralan alternatif olay " -"döngülerinde bu yöntem tanımlanmalıdır. (Kyle Stanley tarafından :issue:" -"`34037` 'de katılmıştır.)" +":meth:`asyncio.loop.shutdown_default_executor`, :class:`~asyncio.AbstractEventLoop` " +"öğesine eklendi, yani ondan devralan alternatif olay döngülerinde bu yöntem " +"tanımlanmalıdır. (Kyle Stanley tarafından :issue:`34037` 'de katılmıştır.)" #: whatsnew/3.9.rst:1110 msgid "" @@ -2387,39 +2409,40 @@ msgid "" msgstr "" "``array('u')`` artık C tipi olarak ``Py_UNICODE`` yerine ``wchar_t`` " "kullanıyor. Python 3.3'ten bu yana ``Py_UNICODE`` ``wchar_t`` takma adı " -"olduğundan, bu değişiklik davranışını etkilemez. (Inada Naoki tarafından :" -"issue:`34538` 'de katılmıştır.)" +"olduğundan, bu değişiklik davranışını etkilemez. (Inada Naoki " +"tarafından :issue:`34538` 'de katılmıştır.)" #: whatsnew/3.9.rst:1120 msgid "" "The :func:`logging.getLogger` API now returns the root logger when passed " "the name ``'root'``, whereas previously it returned a non-root logger named " "``'root'``. This could affect cases where user code explicitly wants a non-" -"root logger named ``'root'``, or instantiates a logger using ``logging." -"getLogger(__name__)`` in some top-level module called ``'root.py'``. " -"(Contributed by Vinay Sajip in :issue:`37742`.)" +"root logger named ``'root'``, or instantiates a logger using " +"``logging.getLogger(__name__)`` in some top-level module called " +"``'root.py'``. (Contributed by Vinay Sajip in :issue:`37742`.)" msgstr "" ":func:`logging.getLogger` API'si artık ``root'`` adı iletildiğinde kök " "kaydediciyi döndürürken, daha önce ``'root'`` adlı kök olmayan bir günlükçü " "döndürdü. Bu, kullanıcı kodunun ``'root'`` adlı kök olmayan bir günlükçüyü " -"açıkça istediği veya ``'root.py'`` adlı bazı üst düzey modüllerde ``logging." -"getLogger(__name__)`` kullanarak bir günlükçü başlattığı durumları " +"açıkça istediği veya ``'root.py'`` adlı bazı üst düzey modüllerde " +"``logging.getLogger(__name__)`` kullanarak bir günlükçü başlattığı durumları " "etkileyebilir. ( :issue:`37742` içinde Vinay Sajip tarafından katılmıştır.)" #: whatsnew/3.9.rst:1127 #, fuzzy msgid "" -"Division handling of :class:`~pathlib.PurePath` now returns :data:" -"`NotImplemented` instead of raising a :exc:`TypeError` when passed something " -"other than an instance of ``str`` or :class:`~pathlib.PurePath`. This " -"allows creating compatible classes that don't inherit from those mentioned " -"types. (Contributed by Roger Aiudi in :issue:`34775`)." +"Division handling of :class:`~pathlib.PurePath` now " +"returns :data:`NotImplemented` instead of raising a :exc:`TypeError` when " +"passed something other than an instance of ``str`` " +"or :class:`~pathlib.PurePath`. This allows creating compatible classes that " +"don't inherit from those mentioned types. (Contributed by Roger Aiudi " +"in :issue:`34775`)." msgstr "" -":class:`~pathlib.PurePath` 'nın bölümleme işlemi, ``str`` veya :class:" -"`~pathlib.PurePath` örneğinden başka bir şey iletildiğinde bir :exc:" -"`TypeError` yükseltmek yerine artık ``NotImplemented`` döndürüyor. Bu, " -"belirtilen türlerden miras almayan uyumlu sınıflar oluşturmaya izin verir. " -"( :issue:`34775` içinde Roger Aiudi tarafından katılmıştır)." +":class:`~pathlib.PurePath` 'nın bölümleme işlemi, ``str`` " +"veya :class:`~pathlib.PurePath` örneğinden başka bir şey iletildiğinde " +"bir :exc:`TypeError` yükseltmek yerine artık ``NotImplemented`` döndürüyor. " +"Bu, belirtilen türlerden miras almayan uyumlu sınıflar oluşturmaya izin " +"verir. ( :issue:`34775` içinde Roger Aiudi tarafından katılmıştır)." #: whatsnew/3.9.rst:1133 msgid "" @@ -2440,17 +2463,17 @@ msgstr "" #: whatsnew/3.9.rst:1141 msgid "" -":func:`codecs.lookup` now normalizes the encoding name the same way as :func:" -"`encodings.normalize_encoding`, except that :func:`codecs.lookup` also " -"converts the name to lower case. For example, ``\"latex+latin1\"`` encoding " -"name is now normalized to ``\"latex_latin1\"``. (Contributed by Jordon Xu " -"in :issue:`37751`.)" +":func:`codecs.lookup` now normalizes the encoding name the same way " +"as :func:`encodings.normalize_encoding`, except that :func:`codecs.lookup` " +"also converts the name to lower case. For example, ``\"latex+latin1\"`` " +"encoding name is now normalized to ``\"latex_latin1\"``. (Contributed by " +"Jordon Xu in :issue:`37751`.)" msgstr "" -":func:`codecs.lookup` artık kodlama adını :func:`encodings." -"normalize_encoding` ile aynı şekilde normalleştirir, ancak :func:`codecs." -"lookup` ayrıca adı küçük harfe dönüştürür. Örneğin, ``\"latex+latin1\"`` " -"kodlama adı artık ``\"latex_latin1\"`` olarak normalleştirildi. ( :issue:" -"`37751` 'de Jordon Xu tarafından katılmıştır.)" +":func:`codecs.lookup` artık kodlama " +"adını :func:`encodings.normalize_encoding` ile aynı şekilde normalleştirir, " +"ancak :func:`codecs.lookup` ayrıca adı küçük harfe dönüştürür. Örneğin, " +"``\"latex+latin1\"`` kodlama adı artık ``\"latex_latin1\"`` olarak " +"normalleştirildi. ( :issue:`37751` 'de Jordon Xu tarafından katılmıştır.)" #: whatsnew/3.9.rst:1149 msgid "Changes in the C API" @@ -2462,18 +2485,19 @@ msgid "" "with :c:func:`PyType_FromSpec` and similar APIs) hold a reference to their " "type object since Python 3.8. As indicated in the \"Changes in the C API\" " "of Python 3.8, for the vast majority of cases, there should be no side " -"effect but for types that have a custom :c:member:`~PyTypeObject." -"tp_traverse` function, ensure that all custom ``tp_traverse`` functions of " -"heap-allocated types visit the object's type." -msgstr "" -":ref:`heap-allocated type ` örnekleri ( :c:func:" -"`PyType_FromSpec` ve benzer API'ler ile oluşturulanlar gibi), Python 3.8'den " -"bu yana tür nesnesine bir başvuru içerir. Python 3.8'in \"C API'sindeki " -"Değişiklikler\" bölümünde belirtildiği gibi, vakaların büyük çoğunluğu için " -"herhangi bir yan etki olmamalıdır, ancak özel bir :c:member:`~PyTypeObject." -"tp_traverse` 'ya sahip türler için tüm özel ``tp_traverse`` yığın " -"işlevlerinin yapıldığından emin olun. tahsis edilen tipler, nesnenin tipini " -"ziyaret eder." +"effect but for types that have a " +"custom :c:member:`~PyTypeObject.tp_traverse` function, ensure that all " +"custom ``tp_traverse`` functions of heap-allocated types visit the object's " +"type." +msgstr "" +":ref:`heap-allocated type ` örnekleri " +"( :c:func:`PyType_FromSpec` ve benzer API'ler ile oluşturulanlar gibi), " +"Python 3.8'den bu yana tür nesnesine bir başvuru içerir. Python 3.8'in \"C " +"API'sindeki Değişiklikler\" bölümünde belirtildiği gibi, vakaların büyük " +"çoğunluğu için herhangi bir yan etki olmamalıdır, ancak özel " +"bir :c:member:`~PyTypeObject.tp_traverse` 'ya sahip türler için tüm özel " +"``tp_traverse`` yığın işlevlerinin yapıldığından emin olun. tahsis edilen " +"tipler, nesnenin tipini ziyaret eder." #: whatsnew/3.9.rst:1161 msgid "" @@ -2531,8 +2555,8 @@ msgstr "(Daha fazla bilgi için bkz. :issue:`35810` ve :issue:`40217`.)" msgid "" "The functions ``PyEval_CallObject``, ``PyEval_CallFunction``, " "``PyEval_CallMethod`` and ``PyEval_CallObjectWithKeywords`` are deprecated. " -"Use :c:func:`PyObject_Call` and its variants instead. (See more details in :" -"issue:`29548`.)" +"Use :c:func:`PyObject_Call` and its variants instead. (See more details " +"in :issue:`29548`.)" msgstr "" "``PyEval_CallObject``, ``PyEval_CallFunction``, ``PyEval_CallMethod`` ve " "``PyEval_CallObjectWithKeywords`` işlevleri kullanımdan kaldırılmıştır. " @@ -2545,9 +2569,9 @@ msgstr "CPython bayt kodu değişiklikleri" #: whatsnew/3.9.rst:1206 msgid "" -"The :opcode:`LOAD_ASSERTION_ERROR` opcode was added for handling the :" -"keyword:`assert` statement. Previously, the assert statement would not work " -"correctly if the :exc:`AssertionError` exception was being shadowed. " +"The :opcode:`LOAD_ASSERTION_ERROR` opcode was added for handling " +"the :keyword:`assert` statement. Previously, the assert statement would not " +"work correctly if the :exc:`AssertionError` exception was being shadowed. " "(Contributed by Zackery Spytz in :issue:`34880`.)" msgstr "" ":opcode:`LOAD_ASSERTION_ERROR` işlem kodu, :keyword:`assert` ifadesini " @@ -2591,15 +2615,15 @@ msgstr "Yapı Değişiklikleri" #, fuzzy msgid "" "Added ``--with-platlibdir`` option to the ``configure`` script: name of the " -"platform-specific library directory, stored in the new :data:`sys." -"platlibdir` attribute. See :data:`sys.platlibdir` attribute for more " -"information. (Contributed by Jan Matějek, Matěj Cepl, Charalampos Stratakis " -"and Victor Stinner in :issue:`1294959`.)" -msgstr "" -"``configure`` betiğine ``--with-platlibdir`` seçeneği eklendi: yeni :attr:" -"`sys.platlibdir` özniteliğinde saklanan platforma özgü kitaplık dizininin " -"adı. Daha fazla bilgi için :attr:`sys.platlibdir` niteliğine bakın. (Jan " -"Matějek, Matěj Cepl, Charalampos Stratakis ve Victor Stinner'ın " +"platform-specific library directory, stored in the " +"new :data:`sys.platlibdir` attribute. See :data:`sys.platlibdir` attribute " +"for more information. (Contributed by Jan Matějek, Matěj Cepl, Charalampos " +"Stratakis and Victor Stinner in :issue:`1294959`.)" +msgstr "" +"``configure`` betiğine ``--with-platlibdir`` seçeneği eklendi: " +"yeni :attr:`sys.platlibdir` özniteliğinde saklanan platforma özgü kitaplık " +"dizininin adı. Daha fazla bilgi için :attr:`sys.platlibdir` niteliğine " +"bakın. (Jan Matějek, Matěj Cepl, Charalampos Stratakis ve Victor Stinner'ın " "katkılarıyla :issue:`1294959`.)" #: whatsnew/3.9.rst:1231 @@ -2607,8 +2631,8 @@ msgid "" "The ``COUNT_ALLOCS`` special build macro has been removed. (Contributed by " "Victor Stinner in :issue:`39489`.)" msgstr "" -"``COUNT_ALLOCS`` özel yapı makrosu kaldırıldı. (Victor Stinner tarafından :" -"issue:`39489` 'da katılmıştır.)" +"``COUNT_ALLOCS`` özel yapı makrosu kaldırıldı. (Victor Stinner " +"tarafından :issue:`39489` 'da katılmıştır.)" #: whatsnew/3.9.rst:1234 #, fuzzy @@ -2617,9 +2641,9 @@ msgid "" "functions are now required to build Python. (Contributed by Victor Stinner " "in :issue:`39395`.)" msgstr "" -"Windows olmayan platformlarda, Python'u oluşturmak için artık :c:func:" -"`setenv` ve :c:func:`unsetenv` işlevleri gereklidir. (Victor Stinner " -"tarafından :issue:`39395` 'de katılmıştır.)" +"Windows olmayan platformlarda, Python'u oluşturmak için " +"artık :c:func:`setenv` ve :c:func:`unsetenv` işlevleri gereklidir. (Victor " +"Stinner tarafından :issue:`39395` 'de katılmıştır.)" #: whatsnew/3.9.rst:1238 msgid "" @@ -2627,8 +2651,8 @@ msgid "" "officially unsupported. (See :issue:`10945` for more details.)" msgstr "" "Windows dışı platformlarda, ``bdist_wininst`` yükleyicilerin oluşturulması " -"artık resmi olarak desteklenmemektedir. (Daha fazla ayrıntı için bkz. :issue:" -"`10945`.)" +"artık resmi olarak desteklenmemektedir. (Daha fazla ayrıntı için " +"bkz. :issue:`10945`.)" #: whatsnew/3.9.rst:1241 msgid "" @@ -2642,8 +2666,8 @@ msgid "" msgstr "" "Python'u macOS'ta kaynaktan derlerken, ``_tkinter``, macOS'un eski " "sürümlerinde olduğu gibi, ``/Library/Frameworks`` içine yüklenmişlerse artık " -"sistem dışı Tcl ve Tk çerçeveleriyle bağlantı kuruyor. Bir macOS SDK, :" -"option:`--enable-universalsdk` veya ``-isysroot`` kullanılarak açıkça " +"sistem dışı Tcl ve Tk çerçeveleriyle bağlantı kuruyor. Bir macOS " +"SDK, :option:`--enable-universalsdk` veya ``-isysroot`` kullanılarak açıkça " "yapılandırılmışsa, yalnızca SDK'nın kendisi aranır. Varsayılan davranış yine " "de ``--with-tcltk-includes`` ve ``--with-tcltk-libs`` ile geçersiz " "kılınabilir. ( :issue:`34956` içinde Ned Deily tarafından katılmıştır.)" @@ -2682,8 +2706,8 @@ msgstr "" "setinin daha hızlı bir yapı oluşturduğuna dair hiçbir garanti vermiyoruz. " "Sonuçlar ortama, iş yüküne ve derleyici araç zincirine bağlı " "olabileceğinden, önemseyen kullanıcılar kendi ilgili kıyaslamalarını " -"çalıştırmalıdır. (Daha fazla ayrıntı için bkz. :issue:`36044` ve :issue:" -"`37707`.)" +"çalıştırmalıdır. (Daha fazla ayrıntı için bkz. :issue:`36044` " +"ve :issue:`37707`.)" #: whatsnew/3.9.rst:1268 msgid "C API Changes" @@ -2694,26 +2718,26 @@ msgstr "C API'sindeki değişiklikler" msgid "" ":pep:`573`: Added :c:func:`PyType_FromModuleAndSpec` to associate a module " "with a class; :c:func:`PyType_GetModule` and :c:func:`PyType_GetModuleState` " -"to retrieve the module and its state; and :c:type:`PyCMethod` and :c:macro:" -"`METH_METHOD` to allow a method to access the class it was defined in. " -"(Contributed by Marcel Plch and Petr Viktorin in :issue:`38787`.)" -msgstr "" -":pep:`573`: Bir modülü bir sınıfla ilişkilendirmek için :c:func:" -"`PyType_FromModuleAndSpec` eklendi; modülü ve durumunu almak için :c:func:" -"`PyType_GetModule` ve :c:func:`PyType_GetModuleState`; ve bir yöntemin " -"tanımlandığı sınıfa erişmesine izin vermek için :c:data:`PyCMethod` ve :c:" -"data:`METH_METHOD`. ( :issue:`38787` içinde Marcel Plch ve Petr Viktorin " -"tarafından katılmıştır.)" +"to retrieve the module and its state; and :c:type:`PyCMethod` " +"and :c:macro:`METH_METHOD` to allow a method to access the class it was " +"defined in. (Contributed by Marcel Plch and Petr Viktorin in :issue:`38787`.)" +msgstr "" +":pep:`573`: Bir modülü bir sınıfla ilişkilendirmek " +"için :c:func:`PyType_FromModuleAndSpec` eklendi; modülü ve durumunu almak " +"için :c:func:`PyType_GetModule` ve :c:func:`PyType_GetModuleState`; ve bir " +"yöntemin tanımlandığı sınıfa erişmesine izin vermek için :c:data:`PyCMethod` " +"ve :c:data:`METH_METHOD`. ( :issue:`38787` içinde Marcel Plch ve Petr " +"Viktorin tarafından katılmıştır.)" #: whatsnew/3.9.rst:1280 msgid "" -"Added :c:func:`PyFrame_GetCode` function: get a frame code. Added :c:func:" -"`PyFrame_GetBack` function: get the frame next outer frame. (Contributed by " -"Victor Stinner in :issue:`40421`.)" +"Added :c:func:`PyFrame_GetCode` function: get a frame code. " +"Added :c:func:`PyFrame_GetBack` function: get the frame next outer frame. " +"(Contributed by Victor Stinner in :issue:`40421`.)" msgstr "" -":c:func:`PyFrame_GetCode` işlevi eklendi: bir çerçeve kodu alın. :c:func:" -"`PyFrame_GetBack` işlevi eklendi: sonraki dış çerçeveyi alın. (Victor " -"Stinner tarafından :issue:`40421` 'de katılmıştır.)" +":c:func:`PyFrame_GetCode` işlevi eklendi: bir çerçeve kodu " +"alın. :c:func:`PyFrame_GetBack` işlevi eklendi: sonraki dış çerçeveyi alın. " +"(Victor Stinner tarafından :issue:`40421` 'de katılmıştır.)" #: whatsnew/3.9.rst:1284 msgid "" @@ -2725,19 +2749,19 @@ msgstr "" #: whatsnew/3.9.rst:1287 msgid "" -"Added :c:func:`PyThreadState_GetInterpreter` and :c:func:" -"`PyInterpreterState_Get` functions to get the interpreter. Added :c:func:" -"`PyThreadState_GetFrame` function to get the current frame of a Python " -"thread state. Added :c:func:`PyThreadState_GetID` function: get the unique " -"identifier of a Python thread state. (Contributed by Victor Stinner in :" -"issue:`39947`.)" +"Added :c:func:`PyThreadState_GetInterpreter` " +"and :c:func:`PyInterpreterState_Get` functions to get the interpreter. " +"Added :c:func:`PyThreadState_GetFrame` function to get the current frame of " +"a Python thread state. Added :c:func:`PyThreadState_GetID` function: get the " +"unique identifier of a Python thread state. (Contributed by Victor Stinner " +"in :issue:`39947`.)" msgstr "" -"Yorumlayıcıyı almak için :c:func:`PyThreadState_GetInterpreter` ve :c:func:" -"`PyInterpreterState_Get` işlevleri eklendi. Python iş parçacığı durumunun " -"geçerli çerçevesini almak için :c:func:`PyThreadState_GetFrame` işlevi " -"eklendi. :c:func:`PyThreadState_GetID` işlevi eklendi: Python iş parçacığı " -"durumunun benzersiz tanımlayıcısını alın. (Victor Stinner tarafından :issue:" -"`39947` 'de katılmıştır.)" +"Yorumlayıcıyı almak için :c:func:`PyThreadState_GetInterpreter` " +"ve :c:func:`PyInterpreterState_Get` işlevleri eklendi. Python iş parçacığı " +"durumunun geçerli çerçevesini almak için :c:func:`PyThreadState_GetFrame` " +"işlevi eklendi. :c:func:`PyThreadState_GetID` işlevi eklendi: Python iş " +"parçacığı durumunun benzersiz tanımlayıcısını alın. (Victor Stinner " +"tarafından :issue:`39947` 'de katılmıştır.)" #: whatsnew/3.9.rst:1295 msgid "" @@ -2766,8 +2790,8 @@ msgid "" "access ``PyThreadState.recursion_depth`` field (the structure is opaque in " "the limited C API)." msgstr "" -"Sınırlı API için normal işlevler olarak :c:func:`Py_EnterRecursiveCall` ve :" -"c:func:`Py_LeaveRecursiveCall` sağlayın. Önceden, makrolar olarak " +"Sınırlı API için normal işlevler olarak :c:func:`Py_EnterRecursiveCall` " +"ve :c:func:`Py_LeaveRecursiveCall` sağlayın. Önceden, makrolar olarak " "tanımlanmıştı, ancak bu makrolar, ``PyThreadState.recursion_Definition`` " "alanına erişemeyen sınırlı C API'si ile derlenmiyordu (sınırlı C API'sinde " "yapı opaktır)." @@ -2796,24 +2820,24 @@ msgstr "" #: whatsnew/3.9.rst:1317 msgid "" -"Added the functions :c:func:`PyObject_GC_IsTracked` and :c:func:" -"`PyObject_GC_IsFinalized` to the public API to allow to query if Python " -"objects are being currently tracked or have been already finalized by the " -"garbage collector respectively. (Contributed by Pablo Galindo Salgado in :" -"issue:`40241`.)" +"Added the functions :c:func:`PyObject_GC_IsTracked` " +"and :c:func:`PyObject_GC_IsFinalized` to the public API to allow to query if " +"Python objects are being currently tracked or have been already finalized by " +"the garbage collector respectively. (Contributed by Pablo Galindo Salgado " +"in :issue:`40241`.)" msgstr "" -"Genel API'ye :c:func:`PyObject_GC_IsTracked` ve :c:func:" -"`PyObject_GC_IsFinalized` işlevleri, Python nesnelerinin şu anda izlenip " -"izlenmediğini veya çöp toplayıcı tarafından halihazırda sonlandırılıp " -"sonlandırılmadığını sorgulamaya izin vermek için eklendi. (Pablo Galindo " -"Salgado tarafından :issue:`40241` 'de katılmıştır.)" +"Genel API'ye :c:func:`PyObject_GC_IsTracked` " +"ve :c:func:`PyObject_GC_IsFinalized` işlevleri, Python nesnelerinin şu anda " +"izlenip izlenmediğini veya çöp toplayıcı tarafından halihazırda " +"sonlandırılıp sonlandırılmadığını sorgulamaya izin vermek için eklendi. " +"(Pablo Galindo Salgado tarafından :issue:`40241` 'de katılmıştır.)" #: whatsnew/3.9.rst:1323 #, fuzzy msgid "" "Added :c:func:`!_PyObject_FunctionStr` to get a user-friendly string " -"representation of a function-like object. (Patch by Jeroen Demeyer in :issue:" -"`37645`.)" +"representation of a function-like object. (Patch by Jeroen Demeyer " +"in :issue:`37645`.)" msgstr "" "İşlev benzeri bir nesnenin kullanıcı dostu bir dize temsilini elde etmek " "için :c:func:`_PyObject_FunctionStr` eklendi. (Yama, Jeroen Demeyer " @@ -2824,15 +2848,15 @@ msgid "" "Added :c:func:`PyObject_CallOneArg` for calling an object with one " "positional argument (Patch by Jeroen Demeyer in :issue:`37483`.)" msgstr "" -"Tek bir konum bağımsız değişkeni olan bir nesneyi çağırmak için :c:func:" -"`PyObject_CallOneArg` eklendi (Yama Jeroen Demeyer tarafından :issue:`37483` " -"içinde.)" +"Tek bir konum bağımsız değişkeni olan bir nesneyi çağırmak " +"için :c:func:`PyObject_CallOneArg` eklendi (Yama Jeroen Demeyer " +"tarafından :issue:`37483` içinde.)" #: whatsnew/3.9.rst:1335 msgid "" "``PyInterpreterState.eval_frame`` (:pep:`523`) now requires a new mandatory " -"*tstate* parameter (``PyThreadState*``). (Contributed by Victor Stinner in :" -"issue:`38500`.)" +"*tstate* parameter (``PyThreadState*``). (Contributed by Victor Stinner " +"in :issue:`38500`.)" msgstr "" "``PyInterpreterState.eval_frame`` (:pep:`523`) artık yeni bir zorunlu " "*tstate* parametresi (``PyThreadState*``) gerektiriyor. (Victor Stinner " @@ -2840,23 +2864,24 @@ msgstr "" #: whatsnew/3.9.rst:1339 msgid "" -"Extension modules: :c:member:`~PyModuleDef.m_traverse`, :c:member:" -"`~PyModuleDef.m_clear` and :c:member:`~PyModuleDef.m_free` functions of :c:" -"type:`PyModuleDef` are no longer called if the module state was requested " -"but is not allocated yet. This is the case immediately after the module is " -"created and before the module is executed (:c:data:`Py_mod_exec` function). " -"More precisely, these functions are not called if :c:member:`~PyModuleDef." -"m_size` is greater than 0 and the module state (as returned by :c:func:" -"`PyModule_GetState`) is ``NULL``." -msgstr "" -"Genişletme modülleri: :c:member:`~PyModuleDef.m_traverse`, :c:member:" -"`~PyModuleDef.m_clear` and :c:member:`~PyModuleDef.m_free` functions of :c:" -"type:`PyModuleDef`, modül durumu talep edilmiş ancak henüz tahsisedilmemişse " -"artık çağrılmaz. Bu, modül oluşturulduktan hemen sonra vemodül " -"çalıştırılmadan önceki durumdur (:c:data:`Py_mod_exec` işlevi).Daha kesin " -"olarak, bu işlevler :c:member:`~PyModuleDef.m_size` 0'dan büyükse ve modül " -"durumu ( :c:func:`PyModule_GetState` tarafından döndürülen) ``NULL`` ise " -"çağrılmaz." +"Extension " +"modules: :c:member:`~PyModuleDef.m_traverse`, :c:member:`~PyModuleDef.m_clear` " +"and :c:member:`~PyModuleDef.m_free` functions of :c:type:`PyModuleDef` are " +"no longer called if the module state was requested but is not allocated yet. " +"This is the case immediately after the module is created and before the " +"module is executed (:c:data:`Py_mod_exec` function). More precisely, these " +"functions are not called if :c:member:`~PyModuleDef.m_size` is greater than " +"0 and the module state (as returned by :c:func:`PyModule_GetState`) is " +"``NULL``." +msgstr "" +"Genişletme " +"modülleri: :c:member:`~PyModuleDef.m_traverse`, :c:member:`~PyModuleDef.m_clear` " +"and :c:member:`~PyModuleDef.m_free` functions of :c:type:`PyModuleDef`, " +"modül durumu talep edilmiş ancak henüz tahsisedilmemişse artık çağrılmaz. " +"Bu, modül oluşturulduktan hemen sonra vemodül çalıştırılmadan önceki " +"durumdur (:c:data:`Py_mod_exec` işlevi).Daha kesin olarak, bu " +"işlevler :c:member:`~PyModuleDef.m_size` 0'dan büyükse ve modül durumu " +"( :c:func:`PyModule_GetState` tarafından döndürülen) ``NULL`` ise çağrılmaz." #: whatsnew/3.9.rst:1348 msgid "" @@ -2885,10 +2910,11 @@ msgid "" "``0``). This is significant when embedding Python on Windows. (Contributed " "by Zackery Spytz in :issue:`8901`.)" msgstr "" -"Windows kayıt defteri ``-E`` seçeneği kullanıldığında ( :c:member:`PyConfig." -"use_environment` ``0`` olarak ayarlanmışsa) :data:`sys.path` öğesini " -"başlatmak için artık kullanılmaz. Bu, Python'u Windows'a yerleştirirken " -"önemlidir. ( :issue:`8901` içinde Zackery Spytz tarafından katılmıştır.)" +"Windows kayıt defteri ``-E`` seçeneği kullanıldığında " +"( :c:member:`PyConfig.use_environment` ``0`` olarak " +"ayarlanmışsa) :data:`sys.path` öğesini başlatmak için artık kullanılmaz. Bu, " +"Python'u Windows'a yerleştirirken önemlidir. ( :issue:`8901` içinde Zackery " +"Spytz tarafından katılmıştır.)" #: whatsnew/3.9.rst:1361 msgid "" @@ -2904,8 +2930,8 @@ msgstr "" #, fuzzy msgid "" "The :c:type:`!PyGC_Head` structure is now opaque. It is only defined in the " -"internal C API (``pycore_gc.h``). (Contributed by Victor Stinner in :issue:" -"`40241`.)" +"internal C API (``pycore_gc.h``). (Contributed by Victor Stinner " +"in :issue:`40241`.)" msgstr "" ":c:type:`PyGC_Head` yapısı artık opaktır. Yalnızca dahili C API'sinde " "(``pycore_gc.h``) tanımlanır. (Victor Stinner tarafından :issue:`40241` 'de " @@ -2914,25 +2940,26 @@ msgstr "" #: whatsnew/3.9.rst:1369 #, fuzzy msgid "" -"The ``Py_UNICODE_COPY``, ``Py_UNICODE_FILL``, ``PyUnicode_WSTR_LENGTH``, :c:" -"func:`!PyUnicode_FromUnicode`, :c:func:`!PyUnicode_AsUnicode`, " -"``_PyUnicode_AsUnicode``, and :c:func:`!PyUnicode_AsUnicodeAndSize` are " -"marked as deprecated in C. They have been deprecated by :pep:`393` since " -"Python 3.3. (Contributed by Inada Naoki in :issue:`36346`.)" +"The ``Py_UNICODE_COPY``, ``Py_UNICODE_FILL``, " +"``PyUnicode_WSTR_LENGTH``, :c:func:`!PyUnicode_FromUnicode`, :c:func:`!" +"PyUnicode_AsUnicode`, ``_PyUnicode_AsUnicode``, and :c:func:`!" +"PyUnicode_AsUnicodeAndSize` are marked as deprecated in C. They have been " +"deprecated by :pep:`393` since Python 3.3. (Contributed by Inada Naoki " +"in :issue:`36346`.)" msgstr "" -"``Py_UNICODE_COPY``, ``Py_UNICODE_FILL``, ``PyUnicode_WSTR_LENGTH``, :c:func:" -"`PyUnicode_FromUnicode`, :c:func:`PyUnicode_AsUnicode`, " +"``Py_UNICODE_COPY``, ``Py_UNICODE_FILL``, " +"``PyUnicode_WSTR_LENGTH``, :c:func:`PyUnicode_FromUnicode`, :c:func:`PyUnicode_AsUnicode`, " "``_PyUnicode_AsUnicode``, ve :c:func:`PyUnicode_AsUnicodeAndSize`, C'de " -"kullanımdan kaldırıldı olarak işaretlenmiştir. Python 3.3'ten beri :pep:" -"`393` tarafından kullanımdan kaldırılmıştır. (Inada Naoki tarafından :issue:" -"`36346` 'da katılmıştır.)" +"kullanımdan kaldırıldı olarak işaretlenmiştir. Python 3.3'ten " +"beri :pep:`393` tarafından kullanımdan kaldırılmıştır. (Inada Naoki " +"tarafından :issue:`36346` 'da katılmıştır.)" #: whatsnew/3.9.rst:1376 msgid "" "The :c:func:`Py_FatalError` function is replaced with a macro which logs " "automatically the name of the current function, unless the " -"``Py_LIMITED_API`` macro is defined. (Contributed by Victor Stinner in :" -"issue:`39882`.)" +"``Py_LIMITED_API`` macro is defined. (Contributed by Victor Stinner " +"in :issue:`39882`.)" msgstr "" ":c:func:`Py_FatalError` fonksiyonu, ``Py_LIMITED_API`` makrosu " "tanımlanmadığı sürece geçerli fonksiyonun adını otomatik olarak kaydeden bir " @@ -2945,8 +2972,8 @@ msgid "" "keyword names. (See :issue:`37540` for more information.)" msgstr "" "Vectorcall protokolü artık arayan kişinin anahtar kelime adları olarak " -"yalnızca dizeleri iletmesini gerektirir. (Daha fazla bilgi için bkz. :issue:" -"`37540`.)" +"yalnızca dizeleri iletmesini gerektirir. (Daha fazla bilgi için " +"bkz. :issue:`37540`.)" #: whatsnew/3.9.rst:1384 msgid "" @@ -2961,10 +2988,10 @@ msgstr ":c:func:`PyObject_IS_GC` makrosu bir fonksiyona dönüştürüldü." #: whatsnew/3.9.rst:1388 #, fuzzy msgid "" -"The :c:func:`!PyObject_NEW` macro becomes an alias to the :c:macro:" -"`PyObject_New` macro, and the :c:func:`!PyObject_NEW_VAR` macro becomes an " -"alias to the :c:macro:`PyObject_NewVar` macro. They no longer access " -"directly the :c:member:`PyTypeObject.tp_basicsize` member." +"The :c:func:`!PyObject_NEW` macro becomes an alias to " +"the :c:macro:`PyObject_New` macro, and the :c:func:`!PyObject_NEW_VAR` macro " +"becomes an alias to the :c:macro:`PyObject_NewVar` macro. They no longer " +"access directly the :c:member:`PyTypeObject.tp_basicsize` member." msgstr "" ":c:func:`PyObject_NEW` makrosu :c:func:`PyObject_New` makrosunun takma adı " "olur ve :c:func:`PyObject_NEW_VAR` makrosu :c:func:`PyObject_NewVar` " @@ -2986,8 +3013,8 @@ msgid "" ":c:func:`PyObject_CheckBuffer` macro was converted to a function: the macro " "accessed directly the :c:member:`PyTypeObject.tp_as_buffer` member." msgstr "" -":c:func:`PyObject_CheckBuffer` makrosu bir fonksiyona dönüştürüldü: makro :c:" -"member:`PyTypeObject.tp_as_buffer` üyesine doğrudan erişti." +":c:func:`PyObject_CheckBuffer` makrosu bir fonksiyona dönüştürüldü: " +"makro :c:member:`PyTypeObject.tp_as_buffer` üyesine doğrudan erişti." #: whatsnew/3.9.rst:1400 msgid "" @@ -3007,12 +3034,12 @@ msgstr "(Daha fazla ayrıntı için bkz. :issue:`40170`.)" #: whatsnew/3.9.rst:1409 msgid "" "Excluded ``PyFPE_START_PROTECT()`` and ``PyFPE_END_PROTECT()`` macros of " -"``pyfpe.h`` from the limited C API. (Contributed by Victor Stinner in :issue:" -"`38835`.)" +"``pyfpe.h`` from the limited C API. (Contributed by Victor Stinner " +"in :issue:`38835`.)" msgstr "" "``pyfpe.h`` dosyasının ``PyFPE_START_PROTECT()`` ve ``PyFPE_END_PROTECT()`` " -"makroları sınırlı C API'sinden hariç tutuldu. (Victor Stinner tarafından :" -"issue:`38835` 'de katılmıştır.)" +"makroları sınırlı C API'sinden hariç tutuldu. (Victor Stinner " +"tarafından :issue:`38835` 'de katılmıştır.)" #: whatsnew/3.9.rst:1413 msgid "" @@ -3032,11 +3059,11 @@ msgstr "Aşağıdaki fonksiyonlar sınırlı C API'sinden çıkarıldı:" #: whatsnew/3.9.rst:1422 msgid "" -"``PyThreadState_DeleteCurrent()`` (Contributed by Joannah Nanjekye in :issue:" -"`37878`.)" +"``PyThreadState_DeleteCurrent()`` (Contributed by Joannah Nanjekye " +"in :issue:`37878`.)" msgstr "" -"``PyThreadState_DeleteCurrent()`` (Joannah Nanjekye tarafından :issue:" -"`37878` 'de katılmıştır.)" +"``PyThreadState_DeleteCurrent()`` (Joannah Nanjekye " +"tarafından :issue:`37878` 'de katılmıştır.)" #: whatsnew/3.9.rst:1424 msgid "``_Py_CheckRecursionLimit``" @@ -3120,8 +3147,8 @@ msgstr "" "``_PyRuntime.getframe`` kancası kaldırıldı ve ``_PyRuntime.getframe`` için " "takma ad olan ``_PyThreadState_GetFrame`` makrosu kaldırıldı. Yalnızca " "dahili C API'si tarafından açığa çıkarıldılar. Ayrıca " -"``PyThreadFrameGetter`` türü kaldırıldı. (Victor Stinner tarafından :issue:" -"`39946` 'da katılmıştır.)" +"``PyThreadFrameGetter`` türü kaldırıldı. (Victor Stinner " +"tarafından :issue:`39946` 'da katılmıştır.)" #: whatsnew/3.9.rst:1452 msgid "" @@ -3198,9 +3225,9 @@ msgid "" "used instead. (Contributed by Inada Naoki in :issue:`36346`.)" msgstr "" "``Py_UNICODE_MATCH`` kaldırıldı. :pep:`393` tarafından kullanımdan " -"kaldırıldı ve Python 3.3'ten beri bozuldu. Bunun yerine :c:func:" -"`PyUnicode_Tailmatch` fonksiyonu kullanılabilir. (Inada Naoki tarafından :" -"issue:`36346` 'da katılmıştır.)" +"kaldırıldı ve Python 3.3'ten beri bozuldu. Bunun " +"yerine :c:func:`PyUnicode_Tailmatch` fonksiyonu kullanılabilir. (Inada Naoki " +"tarafından :issue:`36346` 'da katılmıştır.)" #: whatsnew/3.9.rst:1479 msgid "" @@ -3211,8 +3238,8 @@ msgid "" "``_Py_InitializeFromWideArgs``, ``_PyFloat_Repr``, ``_PyFloat_Digits``, " "``_PyFloat_DigitsInit``, ``PyFrame_ExtendStack``, ``_PyAIterWrapper_Type``, " "``PyNullImporter_Type``, ``PyCmpWrapper_Type``, ``PySortWrapper_Type``, " -"``PyNoArgsFunction``. (Contributed by Pablo Galindo Salgado in :issue:" -"`39372`.)" +"``PyNoArgsFunction``. (Contributed by Pablo Galindo Salgado " +"in :issue:`39372`.)" msgstr "" "Tanımlanan ancak uygulama içermeyen arabirimlerin başlık dosyaları " "temizlendi. Kaldırılmakta olan genel API sembolleri şunlardır: : " @@ -3230,8 +3257,9 @@ msgstr "Python 3.9.1'deki önemli değişiklikler" #: whatsnew/3.9.rst:1495 msgid "" -"The behavior of :class:`typing.Literal` was changed to conform with :pep:" -"`586` and to match the behavior of static type checkers specified in the PEP." +"The behavior of :class:`typing.Literal` was changed to conform " +"with :pep:`586` and to match the behavior of static type checkers specified " +"in the PEP." msgstr "" ":class:`typing.Literal` davranışı, :pep:`586` ile uyumlu olacak ve PEP'de " "belirtilen statik tip denetleyicilerin davranışıyla eşleşecek şekilde " @@ -3333,13 +3361,14 @@ msgid "" "``collections.abc.Callable[[int, str], str]`` will have ``__args__`` of " "``(int, str, str)``; previously this was ``([int, str], str)``. To allow " "this change, :class:`types.GenericAlias` can now be subclassed, and a " -"subclass will be returned when subscripting the :class:`collections.abc." -"Callable` type. Code which accesses the arguments via :func:`typing." -"get_args` or ``__args__`` need to account for this change. A :exc:" -"`DeprecationWarning` may be emitted for invalid forms of parameterizing :" -"class:`collections.abc.Callable` which may have passed silently in Python " -"3.9.1. This :exc:`DeprecationWarning` will become a :exc:`TypeError` in " -"Python 3.10. (Contributed by Ken Jin in :issue:`42195`.)" +"subclass will be returned when subscripting " +"the :class:`collections.abc.Callable` type. Code which accesses the " +"arguments via :func:`typing.get_args` or ``__args__`` need to account for " +"this change. A :exc:`DeprecationWarning` may be emitted for invalid forms " +"of parameterizing :class:`collections.abc.Callable` which may have passed " +"silently in Python 3.9.1. This :exc:`DeprecationWarning` will become " +"a :exc:`TypeError` in Python 3.10. (Contributed by Ken Jin " +"in :issue:`42195`.)" msgstr "" ":class:`collections.abc.Callable` jenerik artık tip parametrelerini " "düzleştiriyor, şu anda :data:`typing.Callable` 'ın yaptığına benzer. Bu, " @@ -3347,13 +3376,13 @@ msgstr "" "``(int, str, str)``; olacağı anlamına gelir önceden bu ``([int, str], str)`` " "idi. Bu değişikliğe izin vermek için, :class:`types.GenericAlias` artık alt " "sınıflara ayrılabilir ve :class:`collections.abc.Callable` tipi abone " -"olurken bir alt sınıf döndürülür. Bağımsız değişkenlere :func:`typing." -"get_args` veya ``__args__`` aracılığıyla erişen kodun bu değişikliği hesaba " -"katması gerekir. Python 3.9.1'de sessizce geçmiş olabilecek :class:" -"`collections.abc.Callable` parametreleştirmenin geçersiz biçimleri için bir :" -"exc:`DeprecationWarning` yayınlanabilir. Python 3.10'da bu :exc:" -"`DeprecationWarning` bir :exc:`TypeError` olacaktır. ( :issue:`42195` içinde " -"Ken Jin tarafından katılmıştır.)" +"olurken bir alt sınıf döndürülür. Bağımsız " +"değişkenlere :func:`typing.get_args` veya ``__args__`` aracılığıyla erişen " +"kodun bu değişikliği hesaba katması gerekir. Python 3.9.1'de sessizce geçmiş " +"olabilecek :class:`collections.abc.Callable` parametreleştirmenin geçersiz " +"biçimleri için bir :exc:`DeprecationWarning` yayınlanabilir. Python 3.10'da " +"bu :exc:`DeprecationWarning` bir :exc:`TypeError` olacaktır. " +"( :issue:`42195` içinde Ken Jin tarafından katılmıştır.)" #: whatsnew/3.9.rst:1577 msgid "urllib.parse" @@ -3362,23 +3391,24 @@ msgstr "urllib.parse" #: whatsnew/3.9.rst:1554 msgid "" "Earlier Python versions allowed using both ``;`` and ``&`` as query " -"parameter separators in :func:`urllib.parse.parse_qs` and :func:`urllib." -"parse.parse_qsl`. Due to security concerns, and to conform with newer W3C " -"recommendations, this has been changed to allow only a single separator key, " -"with ``&`` as the default. This change also affects :func:`cgi.parse` and :" -"func:`cgi.parse_multipart` as they use the affected functions internally. " -"For more details, please see their respective documentation. (Contributed by " -"Adam Goldschmidt, Senthil Kumaran and Ken Jin in :issue:`42967`.)" -msgstr "" -"Önceki Python sürümleri, :func:`urllib.parse.parse_qs` ve :func:`urllib." -"parse.parse_qsl` içinde sorgu parametresi ayırıcıları olarak hem ``;`` hem " -"de ``&`` kullanılmasına izin veriyordu. Güvenlik endişeleri nedeniyle ve " -"daha yeni W3C tavsiyelerine uymak için bu, varsayılan olarak ``&`` ile " -"yalnızca tek bir ayırıcı anahtara izin verecek şekilde değiştirildi. Bu " -"değişiklik, etkilenen fonksiyonlar dahili olarak kullandıkları için :func:" -"`cgi.parse` ve :func:`cgi.parse_multipart` 'ı da etkiler. Daha fazla ayrıntı " -"için lütfen ilgili belgelere bakın. (Adam Goldschmidt, Senthil Kumaran ve " -"Ken Jin'in katkılarıyla :issue:`42967`.)" +"parameter separators in :func:`urllib.parse.parse_qs` " +"and :func:`urllib.parse.parse_qsl`. Due to security concerns, and to " +"conform with newer W3C recommendations, this has been changed to allow only " +"a single separator key, with ``&`` as the default. This change also " +"affects :func:`cgi.parse` and :func:`cgi.parse_multipart` as they use the " +"affected functions internally. For more details, please see their respective " +"documentation. (Contributed by Adam Goldschmidt, Senthil Kumaran and Ken Jin " +"in :issue:`42967`.)" +msgstr "" +"Önceki Python sürümleri, :func:`urllib.parse.parse_qs` " +"ve :func:`urllib.parse.parse_qsl` içinde sorgu parametresi ayırıcıları " +"olarak hem ``;`` hem de ``&`` kullanılmasına izin veriyordu. Güvenlik " +"endişeleri nedeniyle ve daha yeni W3C tavsiyelerine uymak için bu, " +"varsayılan olarak ``&`` ile yalnızca tek bir ayırıcı anahtara izin verecek " +"şekilde değiştirildi. Bu değişiklik, etkilenen fonksiyonlar dahili olarak " +"kullandıkları için :func:`cgi.parse` ve :func:`cgi.parse_multipart` 'ı da " +"etkiler. Daha fazla ayrıntı için lütfen ilgili belgelere bakın. (Adam " +"Goldschmidt, Senthil Kumaran ve Ken Jin'in katkılarıyla :issue:`42967`.)" #: whatsnew/3.9.rst:1565 #, fuzzy @@ -3402,11 +3432,12 @@ msgstr "Python 3.9.1'deki önemli değişiklikler" #: whatsnew/3.9.rst:1579 msgid "" "The presence of newline or tab characters in parts of a URL allows for some " -"forms of attacks. Following the WHATWG specification that updates :rfc:" -"`3986`, ASCII newline ``\\n``, ``\\r`` and tab ``\\t`` characters are " -"stripped from the URL by the parser in :mod:`urllib.parse` preventing such " -"attacks. The removal characters are controlled by a new module level " -"variable ``urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE``. (See :gh:`88048`)" +"forms of attacks. Following the WHATWG specification that " +"updates :rfc:`3986`, ASCII newline ``\\n``, ``\\r`` and tab ``\\t`` " +"characters are stripped from the URL by the parser in :mod:`urllib.parse` " +"preventing such attacks. The removal characters are controlled by a new " +"module level variable ``urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE``. " +"(See :gh:`88048`)" msgstr "" #: whatsnew/3.9.rst:1587