Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit5799a7f

Browse files
author
github-actions
committed
Merge 3.10 into 2.7
1 parent3733feb commit5799a7f

File tree

2 files changed

+71
-64
lines changed

2 files changed

+71
-64
lines changed

‎c-api/gcsupport.po

Lines changed: 41 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,8 @@ msgstr ""
1010
"POT-Creation-Date:2020-02-09 18:46+0900\n"
1111
"PO-Revision-Date:2018-05-22 04:24+0000\n"
1212
"Last-Translator:tomo\n"
13-
"Language-Team:Portuguese (Brazil) (http://www.transifex.com/python-doc/python-27/language/pt_BR/)\n"
13+
"Language-Team:Portuguese (Brazil) (http://www.transifex.com/python-doc/"
14+
"python-27/language/pt_BR/)\n"
1415
"Language:pt_BR\n"
1516
"MIME-Version:1.0\n"
1617
"Content-Type:text/plain; charset=UTF-8\n"
@@ -24,11 +25,11 @@ msgstr "Suporte a Coleta de Lixo Cíclica"
2425
#:../../c-api/gcsupport.rst:8
2526
msgid""
2627
"Python's support for detecting and collecting garbage which involves "
27-
"circular references requires support from object types which are "
28-
"\"containers\" for other objects which may also be containers. Types which "
29-
"do not storereferences to other objects, or which only store references to "
30-
"atomic types(such as numbers or strings), do not need to provide any "
31-
"explicit supportfor garbage collection."
28+
"circular references requires support from object types which are\"containers"
29+
"\" for other objects which may also be containers. Types which do not store "
30+
"references to other objects, or which only store references to atomic types "
31+
"(such as numbers or strings), do not need to provide any explicit support "
32+
"for garbage collection."
3233
msgstr""
3334

3435
#:../../c-api/gcsupport.rst:18
@@ -46,33 +47,40 @@ msgid ""
4647
"documented here. For convenience these objects will be referred to as "
4748
"container objects."
4849
msgstr""
50+
"Objetos com esse tipo de sinalizador definido devem seguir as regras "
51+
"documentadas aqui. Por conveniência esses objetos serão referenciados como "
52+
"objetos de contêiner."
4953

5054
#:../../c-api/gcsupport.rst:31
5155
msgid"Constructors for container types must conform to two rules:"
52-
msgstr""
56+
msgstr"Construtores para tipos de contêiner devem obedecer a duas regras:"
5357

5458
#:../../c-api/gcsupport.rst:33
5559
msgid""
5660
"The memory for the object must be allocated using :c:func:`PyObject_GC_New` "
5761
"or :c:func:`PyObject_GC_NewVar`."
5862
msgstr""
63+
"A memória para o objeto deve ser alocada usando :c:func:`PyObject_GC_New` "
64+
"ou :c:func:`PyObject_GC_NewVar`."
5965

6066
#:../../c-api/gcsupport.rst:36
6167
msgid""
6268
"Once all the fields which may contain references to other containers are "
6369
"initialized, it must call :c:func:`PyObject_GC_Track`."
6470
msgstr""
71+
"Uma vez que todos os campos que podem conter referências a outros containers "
72+
"foram inicializados, deve-se chamar :c:func:`PyObject_GC_Track`."
6573

6674
#:../../c-api/gcsupport.rst:42
6775
msgid""
68-
"Analogous to :c:func:`PyObject_New` but for container objects with the "
69-
":const:`Py_TPFLAGS_HAVE_GC` flag set."
76+
"Analogous to :c:func:`PyObject_New` but for container objects with the:"
77+
"const:`Py_TPFLAGS_HAVE_GC` flag set."
7078
msgstr""
7179

7280
#:../../c-api/gcsupport.rst:48
7381
msgid""
74-
"Analogous to :c:func:`PyObject_NewVar` but for container objects with the "
75-
":const:`Py_TPFLAGS_HAVE_GC` flag set."
82+
"Analogous to :c:func:`PyObject_NewVar` but for container objects with the:"
83+
"const:`Py_TPFLAGS_HAVE_GC` flag set."
7684
msgstr""
7785

7886
#:../../c-api/gcsupport.rst:51
@@ -119,8 +127,8 @@ msgstr ""
119127

120128
#:../../c-api/gcsupport.rst:83
121129
msgid""
122-
"Before fields which refer to other containers are invalidated, "
123-
":c:func:`PyObject_GC_UnTrack` must be called."
130+
"Before fields which refer to other containers are invalidated,:c:func:"
131+
"`PyObject_GC_UnTrack` must be called."
124132
msgstr""
125133

126134
#:../../c-api/gcsupport.rst:86
@@ -130,24 +138,24 @@ msgstr ""
130138

131139
#:../../c-api/gcsupport.rst:91
132140
msgid""
133-
"Releases memory allocated to an object using :c:func:`PyObject_GC_New` or "
134-
":c:func:`PyObject_GC_NewVar`."
141+
"Releases memory allocated to an object using :c:func:`PyObject_GC_New` or:c:"
142+
"func:`PyObject_GC_NewVar`."
135143
msgstr""
136144

137145
#:../../c-api/gcsupport.rst:97
138146
msgid""
139147
"Remove the object *op* from the set of container objects tracked by the "
140148
"collector. Note that :c:func:`PyObject_GC_Track` can be called again on "
141-
"this object to add it back to the set of tracked objects. The deallocator "
142-
"(:c:member:`~PyTypeObject.tp_dealloc` handler) should call this for the "
143-
"objectbefore any of the fields used by the "
144-
":c:member:`~PyTypeObject.tp_traverse`handler become invalid."
149+
"this object to add it back to the set of tracked objects. The deallocator(:"
150+
"c:member:`~PyTypeObject.tp_dealloc` handler) should call this for the object "
151+
"before any of the fields used by the :c:member:`~PyTypeObject.tp_traverse` "
152+
"handler become invalid."
145153
msgstr""
146154

147155
#:../../c-api/gcsupport.rst:106
148156
msgid""
149-
"A macro version of :c:func:`PyObject_GC_UnTrack`. It should not be used for"
150-
"extension modules."
157+
"A macro version of :c:func:`PyObject_GC_UnTrack`. It should not be used for"
158+
"extension modules."
151159
msgstr""
152160

153161
#:../../c-api/gcsupport.rst:109
@@ -158,12 +166,12 @@ msgstr ""
158166

159167
#:../../c-api/gcsupport.rst:114
160168
msgid""
161-
"Type of the visitor function passed to the "
162-
":c:member:`~PyTypeObject.tp_traverse` handler. The function should be called"
163-
" with an object totraverse as *object* and the third parameter to the "
164-
":c:member:`~PyTypeObject.tp_traverse` handler as *arg*. The Python core "
165-
"uses several visitorfunctions to implement cyclic garbage detection; it's "
166-
"not expected thatusers will need to write their own visitor functions."
169+
"Type of the visitor function passed to the:c:member:`~PyTypeObject."
170+
"tp_traverse` handler. The function should be called with an object to"
171+
"traverse as *object* and the third parameter to the:c:member:`~PyTypeObject."
172+
"tp_traverse` handler as *arg*. The Python core uses several visitor "
173+
"functions to implement cyclic garbage detection; it's not expected that "
174+
"users will need to write their own visitor functions."
167175
msgstr""
168176

169177
#:../../c-api/gcsupport.rst:121
@@ -184,10 +192,10 @@ msgstr ""
184192

185193
#:../../c-api/gcsupport.rst:133
186194
msgid""
187-
"To simplify writing :c:member:`~PyTypeObject.tp_traverse` handlers, a "
188-
":c:func:`Py_VISIT` macro is provided. In order to use this macro, the "
189-
":c:member:`~PyTypeObject.tp_traverse` implementation must name its arguments"
190-
"exactly *visit* and *arg*:"
195+
"To simplify writing :c:member:`~PyTypeObject.tp_traverse` handlers, a:c:"
196+
"func:`Py_VISIT` macro is provided. In order to use this macro, the:c:"
197+
"member:`~PyTypeObject.tp_traverse` implementation must name its arguments"
198+
"exactly *visit* and *arg*:"
191199
msgstr""
192200

193201
#:../../c-api/gcsupport.rst:140
@@ -199,8 +207,8 @@ msgstr ""
199207

200208
#:../../c-api/gcsupport.rst:155
201209
msgid""
202-
"The :c:member:`~PyTypeObject.tp_clear` handler must be of the "
203-
":c:type:`inquiry` type, or *NULL* if the object is immutable."
210+
"The :c:member:`~PyTypeObject.tp_clear` handler must be of the:c:type:"
211+
"`inquiry` type, or *NULL* if the object is immutable."
204212
msgstr""
205213

206214
#:../../c-api/gcsupport.rst:161

‎library/email.errors.po

Lines changed: 30 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,8 @@ msgstr ""
1010
"POT-Creation-Date:2020-02-09 18:46+0900\n"
1111
"PO-Revision-Date:2015-11-28 19:21+0000\n"
1212
"Last-Translator:FULL NAME <EMAIL@ADDRESS>\n"
13-
"Language-Team:Portuguese (Brazil) (http://www.transifex.com/python-doc/python-27/language/pt_BR/)\n"
13+
"Language-Team:Portuguese (Brazil) (http://www.transifex.com/python-doc/"
14+
"python-27/language/pt_BR/)\n"
1415
"Language:pt_BR\n"
1516
"MIME-Version:1.0\n"
1617
"Content-Type:text/plain; charset=UTF-8\n"
@@ -19,7 +20,7 @@ msgstr ""
1920

2021
#:../../library/email.errors.rst:2
2122
msgid":mod:`email.errors`: Exception and Defect classes"
22-
msgstr""
23+
msgstr":mod:`email.errors`: Classes de Erro e Defeito."
2324

2425
#:../../library/email.errors.rst:8
2526
msgid""
@@ -36,17 +37,16 @@ msgstr ""
3637

3738
#:../../library/email.errors.rst:20
3839
msgid""
39-
"This is the base class for exceptions raised by the "
40-
":class:`~email.parser.Parser` class. It is derived from "
41-
":exc:`MessageError`."
40+
"This is the base class for exceptions raised by the :class:`~email.parser."
41+
"Parser` class. It is derived from :exc:`MessageError`."
4242
msgstr""
4343

4444
#:../../library/email.errors.rst:26../../library/email.errors.rst:39
4545
msgid""
46-
"Raised under some error conditions when parsing the :rfc:`2822` headers of a"
47-
"message, this class is derived from :exc:`MessageParseError`. It can be "
48-
"raised from the :meth:`Parser.parse <email.parser.Parser.parse>` or "
49-
":meth:`Parser.parsestr <email.parser.Parser.parsestr>` methods."
46+
"Raised under some error conditions when parsing the :rfc:`2822` headers of a"
47+
"message, this class is derived from :exc:`MessageParseError`. It can be "
48+
"raised from the :meth:`Parser.parse <email.parser.Parser.parse>` or:meth:"
49+
"`Parser.parsestr <email.parser.Parser.parsestr>` methods."
5050
msgstr""
5151

5252
#:../../library/email.errors.rst:31
@@ -60,26 +60,26 @@ msgstr ""
6060
#:../../library/email.errors.rst:44
6161
msgid""
6262
"Situations where it can be raised include not being able to find the "
63-
"starting or terminating boundary in a :mimetype:`multipart/\\*` message when"
64-
"strict parsing is used."
63+
"starting or terminating boundary in a :mimetype:`multipart/\\*` message when"
64+
"strict parsing is used."
6565
msgstr""
6666

6767
#:../../library/email.errors.rst:51
6868
msgid""
6969
"Raised when a payload is added to a :class:`~email.message.Message` object "
7070
"using :meth:`add_payload`, but the payload is already a scalar and the "
71-
"message's :mailheader:`Content-Type` main type is not either "
72-
":mimetype:`multipart` or missing. :exc:`MultipartConversionError` multiply "
73-
"inheritsfrom :exc:`MessageError` and the built-in :exc:`TypeError`."
71+
"message's :mailheader:`Content-Type` main type is not either:mimetype:"
72+
"`multipart` or missing. :exc:`MultipartConversionError` multiply inherits "
73+
"from :exc:`MessageError` and the built-in :exc:`TypeError`."
7474
msgstr""
7575

7676
#:../../library/email.errors.rst:57
7777
msgid""
7878
"Since :meth:`Message.add_payload` is deprecated, this exception is rarely "
79-
"raised in practice. However the exception may also be raised if the "
80-
":meth:`~email.message.Message.attach` method is called on an instance of a "
81-
"classderived from :class:`~email.mime.nonmultipart.MIMENonMultipart` (e.g. "
82-
":class:`~email.mime.image.MIMEImage`)."
79+
"raised in practice. However the exception may also be raised if the:meth:"
80+
"`~email.message.Message.attach` method is called on an instance of a class "
81+
"derived from :class:`~email.mime.nonmultipart.MIMENonMultipart` (e.g.:class:"
82+
"`~email.mime.image.MIMEImage`)."
8383
msgstr""
8484

8585
#:../../library/email.errors.rst:64
@@ -88,8 +88,8 @@ msgid ""
8888
"can find while parsing messages. Note that the defects are added to the "
8989
"message where the problem was found, so for example, if a message nested "
9090
"inside a :mimetype:`multipart/alternative` had a malformed header, that "
91-
"nested message object would have a defect, but the containing messages would"
92-
"not."
91+
"nested message object would have a defect, but the containing messages would"
92+
"not."
9393
msgstr""
9494

9595
#:../../library/email.errors.rst:70
@@ -104,14 +104,14 @@ msgstr ""
104104

105105
#:../../library/email.errors.rst:76
106106
msgid""
107-
":class:`NoBoundaryInMultipartDefect` -- A message claimed to be a multipart,"
108-
"but had no :mimetype:`boundary` parameter."
107+
":class:`NoBoundaryInMultipartDefect` -- A message claimed to be a multipart,"
108+
"but had no :mimetype:`boundary` parameter."
109109
msgstr""
110110

111111
#:../../library/email.errors.rst:79
112112
msgid""
113-
":class:`StartBoundaryNotFoundDefect` -- The start boundary claimed in the "
114-
":mailheader:`Content-Type` header was never found."
113+
":class:`StartBoundaryNotFoundDefect` -- The start boundary claimed in the:"
114+
"mailheader:`Content-Type` header was never found."
115115
msgstr""
116116

117117
#:../../library/email.errors.rst:82
@@ -122,8 +122,8 @@ msgstr ""
122122

123123
#:../../library/email.errors.rst:85
124124
msgid""
125-
":class:`MisplacedEnvelopeHeaderDefect` - A\"Unix From\" header was found in"
126-
"the middle of a header block."
125+
":class:`MisplacedEnvelopeHeaderDefect` - A\"Unix From\" header was found in"
126+
"the middle of a header block."
127127
msgstr""
128128

129129
#:../../library/email.errors.rst:88
@@ -134,9 +134,8 @@ msgstr ""
134134

135135
#:../../library/email.errors.rst:91
136136
msgid""
137-
":class:`MultipartInvariantViolationDefect` -- A message claimed to be a "
138-
":mimetype:`multipart`, but no subparts were found. Note that when a message"
139-
" has this defect, its :meth:`~email.message.Message.is_multipart` method may"
140-
" return false even though its content type claims to be "
141-
":mimetype:`multipart`."
137+
":class:`MultipartInvariantViolationDefect` -- A message claimed to be a :"
138+
"mimetype:`multipart`, but no subparts were found. Note that when a message "
139+
"has this defect, its :meth:`~email.message.Message.is_multipart` method may "
140+
"return false even though its content type claims to be :mimetype:`multipart`."
142141
msgstr""

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp