Skip to content

Commit 6dec6e2

Browse files
author
Autobuild bot on TravisCI
committed
[skip ci] Update .po files
1 parent e71d99d commit 6dec6e2

File tree

8 files changed

+7166
-7133
lines changed

8 files changed

+7166
-7133
lines changed

‎c-api/type.po

+57-45
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ msgid ""
1515
msgstr ""
1616
"Project-Id-Version: Python 3.9\n"
1717
"Report-Msgid-Bugs-To: \n"
18-
"POT-Creation-Date: 2020-09-02 03:58+0000\n"
18+
"POT-Creation-Date: 2020-09-05 04:00+0000\n"
1919
"PO-Revision-Date: 2017-02-16 17:39+0000\n"
2020
"Last-Translator: tomo, 2020\n"
2121
"Language-Team: Japanese (https://www.transifex.com/python-doc/teams/5390/ja/)\n"
@@ -162,212 +162,224 @@ msgid ""
162162
"created using :c:func:`PyType_FromModuleAndSpec`."
163163
msgstr ""
164164

165-
#: ../../c-api/type.rst:117 ../../c-api/type.rst:128
165+
#: ../../c-api/type.rst:117 ../../c-api/type.rst:135
166166
msgid ""
167167
"If no module is associated with the given type, sets :py:class:`TypeError` "
168168
"and returns ``NULL``."
169169
msgstr ""
170170

171-
#: ../../c-api/type.rst:124
171+
#: ../../c-api/type.rst:120
172+
msgid ""
173+
"This function is usually used to get the module in which a method is "
174+
"defined. Note that in such a method, ``PyType_GetModule(Py_TYPE(self))`` may"
175+
" not return the intended result. ``Py_TYPE(self)`` may be a *subclass* of "
176+
"the intended class, and subclasses are not necessarily defined in the same "
177+
"module as their superclass. See :c:type:`PyCMethod` to get the class that "
178+
"defines the method."
179+
msgstr ""
180+
181+
#: ../../c-api/type.rst:131
172182
msgid ""
173183
"Return the state of the module object associated with the given type. This "
174184
"is a shortcut for calling :c:func:`PyModule_GetState()` on the result of "
175185
":c:func:`PyType_GetModule`."
176186
msgstr ""
177187

178-
#: ../../c-api/type.rst:131
188+
#: ../../c-api/type.rst:138
179189
msgid ""
180190
"If the *type* has an associated module but its state is ``NULL``, returns "
181191
"``NULL`` without setting an exception."
182192
msgstr ""
183193

184-
#: ../../c-api/type.rst:138
194+
#: ../../c-api/type.rst:145
185195
msgid "Creating Heap-Allocated Types"
186196
msgstr ""
187197

188-
#: ../../c-api/type.rst:140
198+
#: ../../c-api/type.rst:147
189199
msgid ""
190200
"The following functions and structs are used to create :ref:`heap types "
191201
"<heap-types>`."
192202
msgstr ""
193203

194-
#: ../../c-api/type.rst:145
204+
#: ../../c-api/type.rst:152
195205
msgid ""
196206
"Creates and returns a heap type object from the *spec* "
197207
"(:const:`Py_TPFLAGS_HEAPTYPE`)."
198208
msgstr ""
199209

200-
#: ../../c-api/type.rst:148
210+
#: ../../c-api/type.rst:155
201211
msgid ""
202212
"If *bases* is a tuple, the created heap type contains all types contained in"
203213
" it as base types."
204214
msgstr ""
205215

206-
#: ../../c-api/type.rst:151
216+
#: ../../c-api/type.rst:158
207217
msgid ""
208218
"If *bases* is ``NULL``, the *Py_tp_base* slot is used instead. If that also "
209219
"is ``NULL``, the new type derives from :class:`object`."
210220
msgstr ""
211221

212-
#: ../../c-api/type.rst:154
222+
#: ../../c-api/type.rst:161
213223
msgid ""
214-
"The *module* must be a module object or ``NULL``. If not ``NULL``, the "
215-
"module is associated with the new type and can later be retreived with "
216-
":c:func:`PyType_GetModule`."
224+
"The *module* argument can be used to record the module in which the new "
225+
"class is defined. It must be a module object or ``NULL``. If not ``NULL``, "
226+
"the module is associated with the new type and can later be retreived with "
227+
":c:func:`PyType_GetModule`. The associated module is not inherited by "
228+
"subclasses; it must be specified for each class individually."
217229
msgstr ""
218230

219-
#: ../../c-api/type.rst:158
231+
#: ../../c-api/type.rst:168
220232
msgid "This function calls :c:func:`PyType_Ready` on the new type."
221233
msgstr ""
222234

223-
#: ../../c-api/type.rst:164
235+
#: ../../c-api/type.rst:174
224236
msgid "Equivalent to ``PyType_FromModuleAndSpec(NULL, spec, bases)``."
225237
msgstr ""
226238

227-
#: ../../c-api/type.rst:170
239+
#: ../../c-api/type.rst:180
228240
msgid "Equivalent to ``PyType_FromSpecWithBases(spec, NULL)``."
229241
msgstr ""
230242

231-
#: ../../c-api/type.rst:174
243+
#: ../../c-api/type.rst:184
232244
msgid "Structure defining a type's behavior."
233245
msgstr ""
234246

235-
#: ../../c-api/type.rst:178
247+
#: ../../c-api/type.rst:188
236248
msgid "Name of the type, used to set :c:member:`PyTypeObject.tp_name`."
237249
msgstr ""
238250

239-
#: ../../c-api/type.rst:183
251+
#: ../../c-api/type.rst:193
240252
msgid ""
241253
"Size of the instance in bytes, used to set "
242254
":c:member:`PyTypeObject.tp_basicsize` and "
243255
":c:member:`PyTypeObject.tp_itemsize`."
244256
msgstr ""
245257

246-
#: ../../c-api/type.rst:189
258+
#: ../../c-api/type.rst:199
247259
msgid "Type flags, used to set :c:member:`PyTypeObject.tp_flags`."
248260
msgstr ""
249261

250-
#: ../../c-api/type.rst:191
262+
#: ../../c-api/type.rst:201
251263
msgid ""
252264
"If the ``Py_TPFLAGS_HEAPTYPE`` flag is not set, "
253265
":c:func:`PyType_FromSpecWithBases` sets it automatically."
254266
msgstr ""
255267

256-
#: ../../c-api/type.rst:196
268+
#: ../../c-api/type.rst:206
257269
msgid ""
258270
"Array of :c:type:`PyType_Slot` structures. Terminated by the special slot "
259271
"value ``{0, NULL}``."
260272
msgstr ""
261273

262-
#: ../../c-api/type.rst:201
274+
#: ../../c-api/type.rst:211
263275
msgid ""
264276
"Structure defining optional functionality of a type, containing a slot ID "
265277
"and a value pointer."
266278
msgstr ""
267279

268-
#: ../../c-api/type.rst:206
280+
#: ../../c-api/type.rst:216
269281
msgid "A slot ID."
270282
msgstr ""
271283

272-
#: ../../c-api/type.rst:208
284+
#: ../../c-api/type.rst:218
273285
msgid ""
274286
"Slot IDs are named like the field names of the structures "
275287
":c:type:`PyTypeObject`, :c:type:`PyNumberMethods`, "
276288
":c:type:`PySequenceMethods`, :c:type:`PyMappingMethods` and "
277289
":c:type:`PyAsyncMethods` with an added ``Py_`` prefix. For example, use:"
278290
msgstr ""
279291

280-
#: ../../c-api/type.rst:214
292+
#: ../../c-api/type.rst:224
281293
msgid "``Py_tp_dealloc`` to set :c:member:`PyTypeObject.tp_dealloc`"
282294
msgstr ""
283295

284-
#: ../../c-api/type.rst:215
296+
#: ../../c-api/type.rst:225
285297
msgid "``Py_nb_add`` to set :c:member:`PyNumberMethods.nb_add`"
286298
msgstr ""
287299

288-
#: ../../c-api/type.rst:216
300+
#: ../../c-api/type.rst:226
289301
msgid "``Py_sq_length`` to set :c:member:`PySequenceMethods.sq_length`"
290302
msgstr ""
291303

292-
#: ../../c-api/type.rst:218
304+
#: ../../c-api/type.rst:228
293305
msgid ""
294306
"The following fields cannot be set at all using :c:type:`PyType_Spec` and "
295307
":c:type:`PyType_Slot`:"
296308
msgstr ""
297309

298-
#: ../../c-api/type.rst:221
310+
#: ../../c-api/type.rst:231
299311
msgid ":c:member:`~PyTypeObject.tp_dict`"
300312
msgstr ":c:member:`~PyTypeObject.tp_dict`"
301313

302-
#: ../../c-api/type.rst:222
314+
#: ../../c-api/type.rst:232
303315
msgid ":c:member:`~PyTypeObject.tp_mro`"
304316
msgstr ""
305317

306-
#: ../../c-api/type.rst:223
318+
#: ../../c-api/type.rst:233
307319
msgid ":c:member:`~PyTypeObject.tp_cache`"
308320
msgstr ""
309321

310-
#: ../../c-api/type.rst:224
322+
#: ../../c-api/type.rst:234
311323
msgid ":c:member:`~PyTypeObject.tp_subclasses`"
312324
msgstr ""
313325

314-
#: ../../c-api/type.rst:225
326+
#: ../../c-api/type.rst:235
315327
msgid ":c:member:`~PyTypeObject.tp_weaklist`"
316328
msgstr ""
317329

318-
#: ../../c-api/type.rst:226
330+
#: ../../c-api/type.rst:236
319331
msgid ":c:member:`~PyTypeObject.tp_vectorcall`"
320332
msgstr ":c:member:`~PyTypeObject.tp_vectorcall`"
321333

322-
#: ../../c-api/type.rst:227
334+
#: ../../c-api/type.rst:237
323335
msgid ""
324336
":c:member:`~PyTypeObject.tp_weaklistoffset` (see :ref:`PyMemberDef "
325337
"<pymemberdef-offsets>`)"
326338
msgstr ""
327339

328-
#: ../../c-api/type.rst:229
340+
#: ../../c-api/type.rst:239
329341
msgid ""
330342
":c:member:`~PyTypeObject.tp_dictoffset` (see :ref:`PyMemberDef <pymemberdef-"
331343
"offsets>`)"
332344
msgstr ""
333345

334-
#: ../../c-api/type.rst:231
346+
#: ../../c-api/type.rst:241
335347
msgid ""
336348
":c:member:`~PyTypeObject.tp_vectorcall_offset` (see :ref:`PyMemberDef "
337349
"<pymemberdef-offsets>`)"
338350
msgstr ""
339351

340-
#: ../../c-api/type.rst:234
352+
#: ../../c-api/type.rst:244
341353
msgid ""
342354
"The following fields cannot be set using :c:type:`PyType_Spec` and "
343355
":c:type:`PyType_Slot` under the limited API:"
344356
msgstr ""
345357

346-
#: ../../c-api/type.rst:237
358+
#: ../../c-api/type.rst:247
347359
msgid ":c:member:`~PyBufferProcs.bf_getbuffer`"
348360
msgstr ":c:member:`~PyBufferProcs.bf_getbuffer`"
349361

350-
#: ../../c-api/type.rst:238
362+
#: ../../c-api/type.rst:248
351363
msgid ":c:member:`~PyBufferProcs.bf_releasebuffer`"
352364
msgstr ":c:member:`~PyBufferProcs.bf_releasebuffer`"
353365

354-
#: ../../c-api/type.rst:240
366+
#: ../../c-api/type.rst:250
355367
msgid ""
356368
"Setting :c:data:`Py_tp_bases` may be problematic on some platforms. To avoid"
357369
" issues, use the *bases* argument of :py:func:`PyType_FromSpecWithBases` "
358370
"instead."
359371
msgstr ""
360372

361-
#: ../../c-api/type.rst:246
373+
#: ../../c-api/type.rst:256
362374
msgid "Slots in :c:type:`PyBufferProcs` in may be set in the unlimited API."
363375
msgstr ""
364376

365-
#: ../../c-api/type.rst:250
377+
#: ../../c-api/type.rst:260
366378
msgid ""
367379
"The desired value of the slot. In most cases, this is a pointer to a "
368380
"function."
369381
msgstr ""
370382

371-
#: ../../c-api/type.rst:253
383+
#: ../../c-api/type.rst:263
372384
msgid "May not be ``NULL``."
373385
msgstr ""

‎library/asyncio-dev.po

+29-16
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ msgid ""
1212
msgstr ""
1313
"Project-Id-Version: Python 3.9\n"
1414
"Report-Msgid-Bugs-To: \n"
15-
"POT-Creation-Date: 2020-06-23 03:25+0000\n"
15+
"POT-Creation-Date: 2020-09-05 04:00+0000\n"
1616
"PO-Revision-Date: 2017-02-16 17:48+0000\n"
1717
"Last-Translator: Masato HASHIMOTO <cabezon.hashimoto@gmail.com>, 2017\n"
1818
"Language-Team: Japanese (https://www.transifex.com/python-doc/teams/5390/ja/)\n"
@@ -165,82 +165,95 @@ msgid ""
165165
" in."
166166
msgstr ""
167167

168-
#: ../../library/asyncio-dev.rst:114
168+
#: ../../library/asyncio-dev.rst:110
169+
msgid ""
170+
"There is currently no way to schedule coroutines or callbacks directly from "
171+
"a different process (such as one started with :mod:`multiprocessing`). The "
172+
":ref:`Event Loop Methods <asyncio-event-loop>` section lists APIs that can "
173+
"read from pipes and watch file descriptors without blocking the event loop. "
174+
"In addition, asyncio's :ref:`Subprocess <asyncio-subprocess>` APIs provide a"
175+
" way to start a process and communicate with it from the event loop. Lastly,"
176+
" the aforementioned :meth:`loop.run_in_executor` method can also be used "
177+
"with a :class:`concurrent.futures.ProcessPoolExecutor` to execute code in a "
178+
"different process."
179+
msgstr ""
180+
181+
#: ../../library/asyncio-dev.rst:124
169182
msgid "Running Blocking Code"
170183
msgstr ""
171184

172-
#: ../../library/asyncio-dev.rst:116
185+
#: ../../library/asyncio-dev.rst:126
173186
msgid ""
174187
"Blocking (CPU-bound) code should not be called directly. For example, if a "
175188
"function performs a CPU-intensive calculation for 1 second, all concurrent "
176189
"asyncio Tasks and IO operations would be delayed by 1 second."
177190
msgstr ""
178191

179-
#: ../../library/asyncio-dev.rst:121
192+
#: ../../library/asyncio-dev.rst:131
180193
msgid ""
181194
"An executor can be used to run a task in a different thread or even in a "
182195
"different process to avoid blocking the OS thread with the event loop. See "
183196
"the :meth:`loop.run_in_executor` method for more details."
184197
msgstr ""
185198

186-
#: ../../library/asyncio-dev.rst:130
199+
#: ../../library/asyncio-dev.rst:140
187200
msgid "Logging"
188201
msgstr "ログ記録"
189202

190-
#: ../../library/asyncio-dev.rst:132
203+
#: ../../library/asyncio-dev.rst:142
191204
msgid ""
192205
"asyncio uses the :mod:`logging` module and all logging is performed via the "
193206
"``\"asyncio\"`` logger."
194207
msgstr ""
195208

196-
#: ../../library/asyncio-dev.rst:135
209+
#: ../../library/asyncio-dev.rst:145
197210
msgid ""
198211
"The default log level is :py:data:`logging.INFO`, which can be easily "
199212
"adjusted::"
200213
msgstr ""
201214

202-
#: ../../library/asyncio-dev.rst:144
215+
#: ../../library/asyncio-dev.rst:154
203216
msgid "Detect never-awaited coroutines"
204217
msgstr ""
205218

206-
#: ../../library/asyncio-dev.rst:146
219+
#: ../../library/asyncio-dev.rst:156
207220
msgid ""
208221
"When a coroutine function is called, but not awaited (e.g. ``coro()`` "
209222
"instead of ``await coro()``) or the coroutine is not scheduled with "
210223
":meth:`asyncio.create_task`, asyncio will emit a :exc:`RuntimeWarning`::"
211224
msgstr ""
212225

213-
#: ../../library/asyncio-dev.rst:161 ../../library/asyncio-dev.rst:206
226+
#: ../../library/asyncio-dev.rst:171 ../../library/asyncio-dev.rst:216
214227
msgid "Output::"
215228
msgstr "出力::"
216229

217-
#: ../../library/asyncio-dev.rst:166 ../../library/asyncio-dev.rst:222
230+
#: ../../library/asyncio-dev.rst:176 ../../library/asyncio-dev.rst:232
218231
msgid "Output in debug mode::"
219232
msgstr "デバッグモードの出力::"
220233

221-
#: ../../library/asyncio-dev.rst:179
234+
#: ../../library/asyncio-dev.rst:189
222235
msgid ""
223236
"The usual fix is to either await the coroutine or call the "
224237
":meth:`asyncio.create_task` function::"
225238
msgstr ""
226239

227-
#: ../../library/asyncio-dev.rst:187
240+
#: ../../library/asyncio-dev.rst:197
228241
msgid "Detect never-retrieved exceptions"
229242
msgstr ""
230243

231-
#: ../../library/asyncio-dev.rst:189
244+
#: ../../library/asyncio-dev.rst:199
232245
msgid ""
233246
"If a :meth:`Future.set_exception` is called but the Future object is never "
234247
"awaited on, the exception would never be propagated to the user code. In "
235248
"this case, asyncio would emit a log message when the Future object is "
236249
"garbage collected."
237250
msgstr ""
238251

239-
#: ../../library/asyncio-dev.rst:194
252+
#: ../../library/asyncio-dev.rst:204
240253
msgid "Example of an unhandled exception::"
241254
msgstr ""
242255

243-
#: ../../library/asyncio-dev.rst:217
256+
#: ../../library/asyncio-dev.rst:227
244257
msgid ""
245258
":ref:`Enable the debug mode <asyncio-debug-mode>` to get the traceback where"
246259
" the task was created::"

0 commit comments

Comments
 (0)