Merge 3.10 into 2.7

github-actions · github-actions · commit 5799a7febe3a · 2022-11-04T23:11:13.000Z
diff --git a/c-api/gcsupport.po b/c-api/gcsupport.po
@@ -10,7 +10,8 @@ msgstr ""
 "POT-Creation-Date: 2020-02-09 18:46+0900\n"
 "PO-Revision-Date: 2018-05-22 04:24+0000\n"
 "Last-Translator: tomo\n"
-"Language-Team: Portuguese (Brazil) (http://www.transifex.com/python-doc/python-27/language/pt_BR/)\n"
+"Language-Team: Portuguese (Brazil) (http://www.transifex.com/python-doc/"
+"python-27/language/pt_BR/)\n"
 "Language: pt_BR\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -24,11 +25,11 @@ msgstr "Suporte a Coleta de Lixo Cíclica"
 #: ../../c-api/gcsupport.rst:8
 msgid ""
 "Python's support for detecting and collecting garbage which involves "
-"circular references requires support from object types which are "
-"\"containers\" for other objects which may also be containers.  Types which "
-"do not store references to other objects, or which only store references to "
-"atomic types (such as numbers or strings), do not need to provide any "
-"explicit support for garbage collection."
+"circular references requires support from object types which are \"containers"
+"\" for other objects which may also be containers.  Types which do not store "
+"references to other objects, or which only store references to atomic types "
+"(such as numbers or strings), do not need to provide any explicit support "
+"for garbage collection."
 msgstr ""
 
 #: ../../c-api/gcsupport.rst:18
@@ -46,33 +47,40 @@ msgid ""
 "documented here.  For convenience these objects will be referred to as "
 "container objects."
 msgstr ""
+"Objetos com esse tipo de sinalizador definido devem seguir as regras "
+"documentadas aqui. Por conveniência esses objetos serão referenciados como "
+"objetos de contêiner."
 
 #: ../../c-api/gcsupport.rst:31
 msgid "Constructors for container types must conform to two rules:"
-msgstr ""
+msgstr "Construtores para tipos de contêiner devem obedecer a duas regras:"
 
 #: ../../c-api/gcsupport.rst:33
 msgid ""
 "The memory for the object must be allocated using :c:func:`PyObject_GC_New` "
 "or :c:func:`PyObject_GC_NewVar`."
 msgstr ""
+"A memória para o objeto deve ser alocada usando :c:func:`PyObject_GC_New` "
+"ou :c:func:`PyObject_GC_NewVar`."
 
 #: ../../c-api/gcsupport.rst:36
 msgid ""
 "Once all the fields which may contain references to other containers are "
 "initialized, it must call :c:func:`PyObject_GC_Track`."
 msgstr ""
+"Uma vez que todos os campos que podem conter referências a outros containers "
+"foram inicializados, deve-se chamar  :c:func:`PyObject_GC_Track`."
 
 #: ../../c-api/gcsupport.rst:42
 msgid ""
-"Analogous to :c:func:`PyObject_New` but for container objects with the "
-":const:`Py_TPFLAGS_HAVE_GC` flag set."
+"Analogous to :c:func:`PyObject_New` but for container objects with the :"
+"const:`Py_TPFLAGS_HAVE_GC` flag set."
 msgstr ""
 
 #: ../../c-api/gcsupport.rst:48
 msgid ""
-"Analogous to :c:func:`PyObject_NewVar` but for container objects with the "
-":const:`Py_TPFLAGS_HAVE_GC` flag set."
+"Analogous to :c:func:`PyObject_NewVar` but for container objects with the :"
+"const:`Py_TPFLAGS_HAVE_GC` flag set."
 msgstr ""
 
 #: ../../c-api/gcsupport.rst:51
@@ -119,8 +127,8 @@ msgstr ""
 
 #: ../../c-api/gcsupport.rst:83
 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:86
@@ -130,24 +138,24 @@ msgstr ""
 
 #: ../../c-api/gcsupport.rst:91
 msgid ""
-"Releases memory allocated to an object using :c:func:`PyObject_GC_New` or "
-":c:func:`PyObject_GC_NewVar`."
+"Releases memory allocated to an object using :c:func:`PyObject_GC_New` or :c:"
+"func:`PyObject_GC_NewVar`."
 msgstr ""
 
 #: ../../c-api/gcsupport.rst:97
 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:106
 msgid ""
-"A macro version of :c:func:`PyObject_GC_UnTrack`.  It should not be used for"
-" extension modules."
+"A macro version of :c:func:`PyObject_GC_UnTrack`.  It should not be used for "
+"extension modules."
 msgstr ""
 
 #: ../../c-api/gcsupport.rst:109
@@ -158,12 +166,12 @@ msgstr ""
 
 #: ../../c-api/gcsupport.rst:114
 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:121
@@ -184,10 +192,10 @@ msgstr ""
 
 #: ../../c-api/gcsupport.rst:133
 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:140
@@ -199,8 +207,8 @@ msgstr ""
 
 #: ../../c-api/gcsupport.rst:155
 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:161
diff --git a/library/email.errors.po b/library/email.errors.po
@@ -10,7 +10,8 @@ msgstr ""
 "POT-Creation-Date: 2020-02-09 18:46+0900\n"
 "PO-Revision-Date: 2015-11-28 19:21+0000\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: Portuguese (Brazil) (http://www.transifex.com/python-doc/python-27/language/pt_BR/)\n"
+"Language-Team: Portuguese (Brazil) (http://www.transifex.com/python-doc/"
+"python-27/language/pt_BR/)\n"
 "Language: pt_BR\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -19,7 +20,7 @@ msgstr ""
 
 #: ../../library/email.errors.rst:2
 msgid ":mod:`email.errors`: Exception and Defect classes"
-msgstr ""
+msgstr ":mod:`email.errors`: Classes de Erro e Defeito."
 
 #: ../../library/email.errors.rst:8
 msgid ""
@@ -36,17 +37,16 @@ msgstr ""
 
 #: ../../library/email.errors.rst:20
 msgid ""
-"This is the base class for exceptions raised by the "
-":class:`~email.parser.Parser` class.  It is derived from "
-":exc:`MessageError`."
+"This is the base class for exceptions raised by the :class:`~email.parser."
+"Parser` class.  It is derived from :exc:`MessageError`."
 msgstr ""
 
 #: ../../library/email.errors.rst:26 ../../library/email.errors.rst:39
 msgid ""
-"Raised under some error conditions when parsing the :rfc:`2822` headers of a"
-" message, this class is derived from :exc:`MessageParseError`. It can be "
-"raised from the :meth:`Parser.parse <email.parser.Parser.parse>` or "
-":meth:`Parser.parsestr <email.parser.Parser.parsestr>` methods."
+"Raised under some error conditions when parsing the :rfc:`2822` headers of a "
+"message, this class is derived from :exc:`MessageParseError`. It can be "
+"raised from the :meth:`Parser.parse <email.parser.Parser.parse>` or :meth:"
+"`Parser.parsestr <email.parser.Parser.parsestr>` methods."
 msgstr ""
 
 #: ../../library/email.errors.rst:31
@@ -60,26 +60,26 @@ msgstr ""
 #: ../../library/email.errors.rst:44
 msgid ""
 "Situations where it can be raised include not being able to find the "
-"starting or terminating boundary in a :mimetype:`multipart/\\*` message when"
-" strict parsing is used."
+"starting or terminating boundary in a :mimetype:`multipart/\\*` message when "
+"strict parsing is used."
 msgstr ""
 
 #: ../../library/email.errors.rst:51
 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:57
 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
@@ -88,8 +88,8 @@ msgid ""
 "can find while parsing messages.  Note that the defects are added to the "
 "message where the problem was found, so for example, if a message nested "
 "inside a :mimetype:`multipart/alternative` had a malformed header, that "
-"nested message object would have a defect, but the containing messages would"
-" not."
+"nested message object would have a defect, but the containing messages would "
+"not."
 msgstr ""
 
 #: ../../library/email.errors.rst:70
@@ -104,14 +104,14 @@ msgstr ""
 
 #: ../../library/email.errors.rst:76
 msgid ""
-":class:`NoBoundaryInMultipartDefect` -- A message claimed to be a multipart,"
-" but had no :mimetype:`boundary` parameter."
+":class:`NoBoundaryInMultipartDefect` -- A message claimed to be a multipart, "
+"but had no :mimetype:`boundary` parameter."
 msgstr ""
 
 #: ../../library/email.errors.rst:79
 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:82
@@ -122,8 +122,8 @@ msgstr ""
 
 #: ../../library/email.errors.rst:85
 msgid ""
-":class:`MisplacedEnvelopeHeaderDefect` - A \"Unix From\" header was found in"
-" the middle of a header block."
+":class:`MisplacedEnvelopeHeaderDefect` - A \"Unix From\" header was found in "
+"the middle of a header block."
 msgstr ""
 
 #: ../../library/email.errors.rst:88
@@ -134,9 +134,8 @@ msgstr ""
 
 #: ../../library/email.errors.rst:91
 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 ""
