@@ -11,7 +11,7 @@ msgid ""
1111msgstr ""
1212"Project-Id-Version : Python 3.13\n "
1313"Report-Msgid-Bugs-To : \n "
14- "POT-Creation-Date : 2025-01-03 14:16 +0000\n "
14+ "POT-Creation-Date : 2025-07-25 15:00 +0000\n "
1515"PO-Revision-Date : 2025-07-18 19:20+0000\n "
1616"Last-Translator : Rafael Fontenelle <rffontenelle@gmail.com>, 2025\n "
1717"Language-Team : Portuguese (Brazil) (https://app.transifex.com/python-doc/ "
@@ -591,19 +591,19 @@ msgid ""
591591"following fields:"
592592msgstr ""
593593
594- #: ../../c-api/memory.rst:423 ../../c-api/memory.rst:670
594+ #: ../../c-api/memory.rst:423 ../../c-api/memory.rst:674
595595msgid "Field"
596596msgstr "Campo"
597597
598- #: ../../c-api/memory.rst:423 ../../c-api/memory.rst:670
598+ #: ../../c-api/memory.rst:423 ../../c-api/memory.rst:674
599599msgid "Meaning"
600600msgstr "Significado"
601601
602- #: ../../c-api/memory.rst:425 ../../c-api/memory.rst:672
602+ #: ../../c-api/memory.rst:425 ../../c-api/memory.rst:676
603603msgid "``void *ctx``"
604604msgstr "``void *ctx``"
605605
606- #: ../../c-api/memory.rst:425 ../../c-api/memory.rst:672
606+ #: ../../c-api/memory.rst:425 ../../c-api/memory.rst:676
607607msgid "user context passed as first argument"
608608msgstr ""
609609
@@ -1007,92 +1007,99 @@ msgid ""
10071007"envvar:`PYTHONMALLOC` environment variable (ex: ``PYTHONMALLOC=malloc``)."
10081008msgstr ""
10091009
1010- #: ../../c-api/memory.rst:660
1010+ #: ../../c-api/memory.rst:659
1011+ msgid ""
1012+ "Typically, it makes sense to disable the pymalloc allocator when building "
1013+ "Python with AddressSanitizer (:option:`--with-address-sanitizer`) which "
1014+ "helps uncover low level bugs within the C code."
1015+ msgstr ""
1016+
1017+ #: ../../c-api/memory.rst:664
10111018msgid "Customize pymalloc Arena Allocator"
10121019msgstr ""
10131020
1014- #: ../../c-api/memory.rst:666
1021+ #: ../../c-api/memory.rst:670
10151022msgid ""
10161023"Structure used to describe an arena allocator. The structure has three "
10171024"fields:"
10181025msgstr ""
10191026
1020- #: ../../c-api/memory.rst:674
1027+ #: ../../c-api/memory.rst:678
10211028msgid "``void* alloc(void *ctx, size_t size)``"
10221029msgstr "``void* alloc(void *ctx, size_t size)``"
10231030
1024- #: ../../c-api/memory.rst:674
1031+ #: ../../c-api/memory.rst:678
10251032msgid "allocate an arena of size bytes"
10261033msgstr ""
10271034
1028- #: ../../c-api/memory.rst:676
1035+ #: ../../c-api/memory.rst:680
10291036msgid "``void free(void *ctx, void *ptr, size_t size)``"
10301037msgstr "``void free(void *ctx, void *ptr, size_t size)``"
10311038
1032- #: ../../c-api/memory.rst:676
1039+ #: ../../c-api/memory.rst:680
10331040msgid "free an arena"
10341041msgstr ""
10351042
1036- #: ../../c-api/memory.rst:681
1043+ #: ../../c-api/memory.rst:685
10371044msgid "Get the arena allocator."
10381045msgstr ""
10391046
1040- #: ../../c-api/memory.rst:685
1047+ #: ../../c-api/memory.rst:689
10411048msgid "Set the arena allocator."
10421049msgstr ""
10431050
1044- #: ../../c-api/memory.rst:690
1051+ #: ../../c-api/memory.rst:694
10451052msgid "The mimalloc allocator"
10461053msgstr ""
10471054
1048- #: ../../c-api/memory.rst:694
1055+ #: ../../c-api/memory.rst:698
10491056msgid ""
10501057"Python supports the mimalloc allocator when the underlying platform support "
10511058"is available. mimalloc \" is a general purpose allocator with excellent "
10521059"performance characteristics. Initially developed by Daan Leijen for the "
10531060"runtime systems of the Koka and Lean languages.\" "
10541061msgstr ""
10551062
1056- #: ../../c-api/memory.rst:699
1063+ #: ../../c-api/memory.rst:703
10571064msgid "tracemalloc C API"
10581065msgstr ""
10591066
1060- #: ../../c-api/memory.rst:705
1067+ #: ../../c-api/memory.rst:709
10611068msgid "Track an allocated memory block in the :mod:`tracemalloc` module."
10621069msgstr ""
10631070
1064- #: ../../c-api/memory.rst:707
1071+ #: ../../c-api/memory.rst:711
10651072msgid ""
10661073"Return ``0`` on success, return ``-1`` on error (failed to allocate memory "
10671074"to store the trace). Return ``-2`` if tracemalloc is disabled."
10681075msgstr ""
10691076
1070- #: ../../c-api/memory.rst:710
1077+ #: ../../c-api/memory.rst:714
10711078msgid "If memory block is already tracked, update the existing trace."
10721079msgstr ""
10731080
1074- #: ../../c-api/memory.rst:714
1081+ #: ../../c-api/memory.rst:718
10751082msgid ""
10761083"Untrack an allocated memory block in the :mod:`tracemalloc` module. Do "
10771084"nothing if the block was not tracked."
10781085msgstr ""
10791086
1080- #: ../../c-api/memory.rst:717
1087+ #: ../../c-api/memory.rst:721
10811088msgid "Return ``-2`` if tracemalloc is disabled, otherwise return ``0``."
10821089msgstr ""
10831090
1084- #: ../../c-api/memory.rst:723
1091+ #: ../../c-api/memory.rst:727
10851092msgid "Examples"
10861093msgstr "Exemplos"
10871094
1088- #: ../../c-api/memory.rst:725
1095+ #: ../../c-api/memory.rst:729
10891096msgid ""
10901097"Here is the example from section :ref:`memoryoverview`, rewritten so that "
10911098"the I/O buffer is allocated from the Python heap by using the first function "
10921099"set::"
10931100msgstr ""
10941101
1095- #: ../../c-api/memory.rst:728
1102+ #: ../../c-api/memory.rst:732
10961103msgid ""
10971104"PyObject *res;\n"
10981105"char *buf = (char *) PyMem_Malloc(BUFSIZ); /* for I/O */\n"
@@ -1105,11 +1112,11 @@ msgid ""
11051112"return res;"
11061113msgstr ""
11071114
1108- #: ../../c-api/memory.rst:738
1115+ #: ../../c-api/memory.rst:742
11091116msgid "The same code using the type-oriented function set::"
11101117msgstr ""
11111118
1112- #: ../../c-api/memory.rst:740
1119+ #: ../../c-api/memory.rst:744
11131120msgid ""
11141121"PyObject *res;\n"
11151122"char *buf = PyMem_New(char, BUFSIZ); /* for I/O */\n"
@@ -1122,7 +1129,7 @@ msgid ""
11221129"return res;"
11231130msgstr ""
11241131
1125- #: ../../c-api/memory.rst:750
1132+ #: ../../c-api/memory.rst:754
11261133msgid ""
11271134"Note that in the two examples above, the buffer is always manipulated via "
11281135"functions belonging to the same set. Indeed, it is required to use the same "
@@ -1132,7 +1139,7 @@ msgid ""
11321139"different allocators operating on different heaps. ::"
11331140msgstr ""
11341141
1135- #: ../../c-api/memory.rst:757
1142+ #: ../../c-api/memory.rst:761
11361143msgid ""
11371144"char *buf1 = PyMem_New(char, BUFSIZ);\n"
11381145"char *buf2 = (char *) malloc(BUFSIZ);\n"
@@ -1143,14 +1150,14 @@ msgid ""
11431150"free(buf1); /* Fatal -- should be PyMem_Del() */"
11441151msgstr ""
11451152
1146- #: ../../c-api/memory.rst:765
1153+ #: ../../c-api/memory.rst:769
11471154msgid ""
11481155"In addition to the functions aimed at handling raw memory blocks from the "
11491156"Python heap, objects in Python are allocated and released with :c:macro:"
11501157"`PyObject_New`, :c:macro:`PyObject_NewVar` and :c:func:`PyObject_Del`."
11511158msgstr ""
11521159
1153- #: ../../c-api/memory.rst:769
1160+ #: ../../c-api/memory.rst:773
11541161msgid ""
11551162"These will be explained in the next chapter on defining and implementing new "
11561163"object types in C."
0 commit comments