@@ -11,7 +11,7 @@ msgid ""
1111msgstr ""
1212"Project-Id-Version : Python 3.14\n "
1313"Report-Msgid-Bugs-To : \n "
14- "POT-Creation-Date : 2025-11-03 14:20 +0000\n "
14+ "POT-Creation-Date : 2025-11-07 14:15 +0000\n "
1515"PO-Revision-Date : 2025-09-16 00:00+0000\n "
1616"Last-Translator : python-doc bot, 2025\n "
1717"Language-Team : Japanese (https://app.transifex.com/python-doc/teams/5390/ "
@@ -299,6 +299,10 @@ msgstr ""
299299"辞書内の要素の数を返します。辞書に対して ``len(p)`` を実行するのと同じです。"
300300
301301#: ../../c-api/dict.rst:250
302+ msgid "Similar to :c:func:`PyDict_Size`, but without error checking."
303+ msgstr ""
304+
305+ #: ../../c-api/dict.rst:255
302306msgid ""
303307"Iterate over all key-value pairs in the dictionary *p*. The :c:type:"
304308"`Py_ssize_t` referred to by *ppos* must be initialized to ``0`` prior to the "
@@ -324,11 +328,11 @@ msgstr ""
324328"この値は内部的な辞書構造体のオフセットを表現しており、構造体はスパースなの"
325329"で、オフセットの値に一貫性がないためです。"
326330
327- #: ../../c-api/dict.rst:261
331+ #: ../../c-api/dict.rst:266
328332msgid "For example::"
329333msgstr "例えば::"
330334
331- #: ../../c-api/dict.rst:263
335+ #: ../../c-api/dict.rst:268
332336msgid ""
333337"PyObject *key, *value;\n"
334338"Py_ssize_t pos = 0;\n"
@@ -339,7 +343,7 @@ msgid ""
339343"}"
340344msgstr ""
341345
342- #: ../../c-api/dict.rst:271
346+ #: ../../c-api/dict.rst:276
343347msgid ""
344348"The dictionary *p* should not be mutated during iteration. It is safe to "
345349"modify the values of the keys as you iterate over the dictionary, but only "
@@ -349,7 +353,7 @@ msgstr ""
349353"応する値を変更しても大丈夫になりましたが、キーの集合を変更しないことが前提で"
350354"す。以下に例を示します::"
351355
352- #: ../../c-api/dict.rst:275
356+ #: ../../c-api/dict.rst:280
353357msgid ""
354358"PyObject *key, *value;\n"
355359"Py_ssize_t pos = 0;\n"
@@ -370,14 +374,14 @@ msgid ""
370374"}"
371375msgstr ""
372376
373- #: ../../c-api/dict.rst:293
377+ #: ../../c-api/dict.rst:298
374378msgid ""
375379"The function is not thread-safe in the :term:`free-threaded <free "
376380"threading>` build without external synchronization. You can use :c:macro:"
377381"`Py_BEGIN_CRITICAL_SECTION` to lock the dictionary while iterating over it::"
378382msgstr ""
379383
380- #: ../../c-api/dict.rst:298
384+ #: ../../c-api/dict.rst:303
381385msgid ""
382386"Py_BEGIN_CRITICAL_SECTION(self->dict);\n"
383387"while (PyDict_Next(self->dict, &pos, &key, &value)) {\n"
@@ -386,7 +390,7 @@ msgid ""
386390"Py_END_CRITICAL_SECTION();"
387391msgstr ""
388392
389- #: ../../c-api/dict.rst:306
393+ #: ../../c-api/dict.rst:311
390394msgid ""
391395"On the free-threaded build, this function can be used safely inside a "
392396"critical section. However, the references returned for *pkey* and *pvalue* "
@@ -397,7 +401,7 @@ msgid ""
397401"`Py_NewRef`)."
398402msgstr ""
399403
400- #: ../../c-api/dict.rst:316
404+ #: ../../c-api/dict.rst:321
401405msgid ""
402406"Iterate over mapping object *b* adding key-value pairs to dictionary *a*. "
403407"*b* may be a dictionary, or any object supporting :c:func:`PyMapping_Keys` "
@@ -414,7 +418,7 @@ msgstr ""
414418"行います。成功した場合には ``0`` を返し、例外が送出された場合には ``-1`` を返"
415419"します。"
416420
417- #: ../../c-api/dict.rst:326
421+ #: ../../c-api/dict.rst:331
418422msgid ""
419423"This is the same as ``PyDict_Merge(a, b, 1)`` in C, and is similar to ``a."
420424"update(b)`` in Python except that :c:func:`PyDict_Update` doesn't fall back "
@@ -427,7 +431,7 @@ msgstr ""
427431"性を持たない場合にキー/値ペアのシーケンスを反復することはありません。成功した"
428432"場合には ``0`` を返し、例外が送出された場合には ``-1`` を返します。"
429433
430- #: ../../c-api/dict.rst:335
434+ #: ../../c-api/dict.rst:340
431435msgid ""
432436"Update or merge into dictionary *a*, from the key-value pairs in *seq2*. "
433437"*seq2* must be an iterable object producing iterable objects of length 2, "
@@ -443,57 +447,57 @@ msgstr ""
443447"は ``-1`` を返します。(戻り値以外は) 等価な Python コードを書くと、以下のよう"
444448"になります::"
445449
446- #: ../../c-api/dict.rst:342
450+ #: ../../c-api/dict.rst:347
447451msgid ""
448452"def PyDict_MergeFromSeq2(a, seq2, override):\n"
449453" for key, value in seq2:\n"
450454" if override or key not in a:\n"
451455" a[key] = value"
452456msgstr ""
453457
454- #: ../../c-api/dict.rst:349
458+ #: ../../c-api/dict.rst:354
455459msgid ""
456460"Register *callback* as a dictionary watcher. Return a non-negative integer "
457461"id which must be passed to future calls to :c:func:`PyDict_Watch`. In case "
458462"of error (e.g. no more watcher IDs available), return ``-1`` and set an "
459463"exception."
460464msgstr ""
461465
462- #: ../../c-api/dict.rst:358
466+ #: ../../c-api/dict.rst:363
463467msgid ""
464468"Clear watcher identified by *watcher_id* previously returned from :c:func:"
465469"`PyDict_AddWatcher`. Return ``0`` on success, ``-1`` on error (e.g. if the "
466470"given *watcher_id* was never registered.)"
467471msgstr ""
468472
469- #: ../../c-api/dict.rst:366
473+ #: ../../c-api/dict.rst:371
470474msgid ""
471475"Mark dictionary *dict* as watched. The callback granted *watcher_id* by :c:"
472476"func:`PyDict_AddWatcher` will be called when *dict* is modified or "
473477"deallocated. Return ``0`` on success or ``-1`` on error."
474478msgstr ""
475479
476- #: ../../c-api/dict.rst:374
480+ #: ../../c-api/dict.rst:379
477481msgid ""
478482"Mark dictionary *dict* as no longer watched. The callback granted "
479483"*watcher_id* by :c:func:`PyDict_AddWatcher` will no longer be called when "
480484"*dict* is modified or deallocated. The dict must previously have been "
481485"watched by this watcher. Return ``0`` on success or ``-1`` on error."
482486msgstr ""
483487
484- #: ../../c-api/dict.rst:383
488+ #: ../../c-api/dict.rst:388
485489msgid ""
486490"Enumeration of possible dictionary watcher events: ``PyDict_EVENT_ADDED``, "
487491"``PyDict_EVENT_MODIFIED``, ``PyDict_EVENT_DELETED``, "
488492"``PyDict_EVENT_CLONED``, ``PyDict_EVENT_CLEARED``, or "
489493"``PyDict_EVENT_DEALLOCATED``."
490494msgstr ""
491495
492- #: ../../c-api/dict.rst:391
496+ #: ../../c-api/dict.rst:396
493497msgid "Type of a dict watcher callback function."
494498msgstr ""
495499
496- #: ../../c-api/dict.rst:393
500+ #: ../../c-api/dict.rst:398
497501msgid ""
498502"If *event* is ``PyDict_EVENT_CLEARED`` or ``PyDict_EVENT_DEALLOCATED``, both "
499503"*key* and *new_value* will be ``NULL``. If *event* is ``PyDict_EVENT_ADDED`` "
@@ -502,22 +506,22 @@ msgid ""
502506"dictionary and *new_value* will be ``NULL``."
503507msgstr ""
504508
505- #: ../../c-api/dict.rst:399
509+ #: ../../c-api/dict.rst:404
506510msgid ""
507511"``PyDict_EVENT_CLONED`` occurs when *dict* was previously empty and another "
508512"dict is merged into it. To maintain efficiency of this operation, per-key "
509513"``PyDict_EVENT_ADDED`` events are not issued in this case; instead a single "
510514"``PyDict_EVENT_CLONED`` is issued, and *key* will be the source dictionary."
511515msgstr ""
512516
513- #: ../../c-api/dict.rst:405
517+ #: ../../c-api/dict.rst:410
514518msgid ""
515519"The callback may inspect but must not modify *dict*; doing so could have "
516520"unpredictable effects, including infinite recursion. Do not trigger Python "
517521"code execution in the callback, as it could modify the dict as a side effect."
518522msgstr ""
519523
520- #: ../../c-api/dict.rst:409
524+ #: ../../c-api/dict.rst:414
521525msgid ""
522526"If *event* is ``PyDict_EVENT_DEALLOCATED``, taking a new reference in the "
523527"callback to the about-to-be-destroyed dictionary will resurrect it and "
@@ -526,20 +530,20 @@ msgid ""
526530"again."
527531msgstr ""
528532
529- #: ../../c-api/dict.rst:415
533+ #: ../../c-api/dict.rst:420
530534msgid ""
531535"Callbacks occur before the notified modification to *dict* takes place, so "
532536"the prior state of *dict* can be inspected."
533537msgstr ""
534538
535- #: ../../c-api/dict.rst:418
539+ #: ../../c-api/dict.rst:423
536540msgid ""
537541"If the callback sets an exception, it must return ``-1``; this exception "
538542"will be printed as an unraisable exception using :c:func:"
539543"`PyErr_WriteUnraisable`. Otherwise it should return ``0``."
540544msgstr ""
541545
542- #: ../../c-api/dict.rst:422
546+ #: ../../c-api/dict.rst:427
543547msgid ""
544548"There may already be a pending exception set on entry to the callback. In "
545549"this case, the callback should return ``0`` with the same exception still "
0 commit comments