@@ -12,7 +12,7 @@ msgid ""
1212msgstr ""
1313"Project-Id-Version : Python 3.13\n "
1414"Report-Msgid-Bugs-To : \n "
15- "POT-Creation-Date : 2024-09-13 14:16 +0000\n "
15+ "POT-Creation-Date : 2024-09-27 14:17 +0000\n "
1616"PO-Revision-Date : 2021-06-28 00:49+0000\n "
1717"
Last-Translator :
Rafael Fontenelle <[email protected] >, 2024\n "
1818"Language-Team : Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n "
@@ -146,12 +146,9 @@ msgid ""
146146"details on how every domain allocates memory or what internal functions each "
147147"domain calls is considered an implementation detail, but for debugging "
148148"purposes a simplified table can be found at :ref:`here <default-memory-"
149- "allocators>`. There is no hard requirement to use the memory returned by the "
150- "allocation functions belonging to a given domain for only the purposes "
151- "hinted by that domain (although this is the recommended practice). For "
152- "example, one could use the memory returned by :c:func:`PyMem_RawMalloc` for "
153- "allocating Python objects or the memory returned by :c:func:"
154- "`PyObject_Malloc` for allocating memory for buffers."
149+ "allocators>`. The APIs used to allocate and free a block of memory must be "
150+ "from the same domain. For example, :c:func:`PyMem_Free` must be used to free "
151+ "memory allocated using :c:func:`PyMem_Malloc`."
155152msgstr ""
156153
157154msgid "The three allocation domains are:"
@@ -161,25 +158,37 @@ msgid ""
161158"Raw domain: intended for allocating memory for general-purpose memory "
162159"buffers where the allocation *must* go to the system allocator or where the "
163160"allocator can operate without the :term:`GIL`. The memory is requested "
164- "directly to the system."
161+ "directly from the system. See :ref:`Raw Memory Interface <raw-"
162+ "memoryinterface>`."
165163msgstr ""
166164
167165msgid ""
168166"\" Mem\" domain: intended for allocating memory for Python buffers and "
169167"general-purpose memory buffers where the allocation must be performed with "
170- "the :term:`GIL` held. The memory is taken from the Python private heap."
168+ "the :term:`GIL` held. The memory is taken from the Python private heap. See :"
169+ "ref:`Memory Interface <memoryinterface>`."
171170msgstr ""
172171
173172msgid ""
174- "Object domain: intended for allocating memory belonging to Python objects. "
175- "The memory is taken from the Python private heap."
173+ "Object domain: intended for allocating memory for Python objects. The memory "
174+ "is taken from the Python private heap. See :ref:`Object allocators "
175+ "<objectinterface>`."
176176msgstr ""
177177
178178msgid ""
179- "When freeing memory previously allocated by the allocating functions "
180- "belonging to a given domain,the matching specific deallocating functions "
181- "must be used. For example, :c:func:`PyMem_Free` must be used to free memory "
182- "allocated using :c:func:`PyMem_Malloc`."
179+ "The :term:`free-threaded <free threading>` build requires that only Python "
180+ "objects are allocated using the \" object\" domain and that all Python "
181+ "objects are allocated using that domain. This differs from the prior Python "
182+ "versions, where this was only a best practice and not a hard requirement."
183+ msgstr ""
184+
185+ msgid ""
186+ "For example, buffers (non-Python objects) should be allocated using :c:func:"
187+ "`PyMem_Malloc`, :c:func:`PyMem_RawMalloc`, or :c:func:`malloc`, but not :c:"
188+ "func:`PyObject_Malloc`."
189+ msgstr ""
190+
191+ msgid "See :ref:`Memory Allocation APIs <free-threaded-memory-allocation>`."
183192msgstr ""
184193
185194msgid "Raw Memory Interface"
0 commit comments