@@ -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-27 14:15 +0000\n "
14+ "POT-Creation-Date : 2025-12-03 14:17 +0000\n "
1515"PO-Revision-Date : 2025-09-16 00:00+0000\n "
1616"Last-Translator : python-doc bot, 2025\n "
1717"Language-Team : Indonesian (https://app.transifex.com/python-doc/teams/5390/ "
@@ -36,11 +36,9 @@ msgid ""
3636msgstr ""
3737
3838msgid ""
39- "The free-threaded mode is working and continues to be improved, but there is "
40- "some additional overhead in single-threaded workloads compared to the "
41- "regular build. Additionally, third-party packages, in particular ones with "
42- "an :term:`extension module`, may not be ready for use in a free-threaded "
43- "build, and will re-enable the :term:`GIL`."
39+ "Some third-party packages, in particular ones with an :term:`extension "
40+ "module`, may not be ready for use in a free-threaded build, and will re-"
41+ "enable the :term:`GIL`."
4442msgstr ""
4543
4644msgid ""
@@ -148,86 +146,50 @@ msgid "Immortalization"
148146msgstr ""
149147
150148msgid ""
151- "The free-threaded build of the 3.13 release makes some objects :term:"
152- "`immortal`. Immortal objects are not deallocated and have reference counts "
153- "that are never modified. This is done to avoid reference count contention "
154- "that would prevent efficient multi-threaded scaling."
149+ "In the free-threaded build, some objects are :term:`immortal`. Immortal "
150+ "objects are not deallocated and have reference counts that are never "
151+ "modified. This is done to avoid reference count contention that would "
152+ "prevent efficient multi-threaded scaling."
155153msgstr ""
156154
157- msgid ""
158- "An object will be made immortal when a new thread is started for the first "
159- "time after the main thread is running. The following objects are "
160- "immortalized:"
161- msgstr ""
162-
163- msgid ""
164- ":ref:`function <user-defined-funcs>` objects declared at the module level"
165- msgstr ""
166-
167- msgid ":ref:`method <instance-methods>` descriptors"
168- msgstr ""
169-
170- msgid ":ref:`code <code-objects>` objects"
171- msgstr ""
172-
173- msgid ":term:`module` objects and their dictionaries"
174- msgstr ""
175-
176- msgid ":ref:`classes <classes>` (type objects)"
155+ msgid "As of the 3.14 release, immortalization is limited to:"
177156msgstr ""
178157
179158msgid ""
180- "Because immortal objects are never deallocated, applications that create "
181- "many objects of these types may see increased memory usage under Python "
182- "3.13. This has been addressed in the 3.14 release, where the aforementioned "
183- "objects use deferred reference counting to avoid reference count contention."
159+ "Code constants: numeric literals, string literals, and tuple literals "
160+ "composed of other constants."
184161msgstr ""
185162
186- msgid ""
187- "Additionally, numeric and string literals in the code as well as strings "
188- "returned by :func:`sys.intern` are also immortalized in the 3.13 release. "
189- "This behavior is part of the 3.14 release as well and it is expected to "
190- "remain in future free-threaded builds."
163+ msgid "Strings interned by :func:`sys.intern`."
191164msgstr ""
192165
193166msgid "Frame objects"
194167msgstr ""
195168
196169msgid ""
197- "It is not safe to access :ref:`frame <frame-objects>` objects from other "
198- "threads and doing so may cause your program to crash . This means that :"
199- "func:`sys._current_frames` is generally not safe to use in a free-threaded "
200- "build. Functions like :func:`inspect.currentframe` and :func:`sys."
201- "_getframe` are generally safe as long as the resulting frame object is not "
202- "passed to another thread."
170+ "It is not safe to access :attr:`frame.f_locals` from a :ref:`frame <frame-"
171+ "objects>` object if that frame is currently executing in another thread, and "
172+ "doing so may crash the interpreter."
203173msgstr ""
204174
205175msgid "Iterators"
206176msgstr "*Iterators*"
207177
208178msgid ""
209- "Sharing the same iterator object between multiple threads is generally not "
210- "safe and threads may see duplicate or missing elements when iterating or "
211- "crash the interpreter ."
179+ "It is generally not thread-safe to access the same iterator object from "
180+ "multiple threads concurrently, and threads may see duplicate or missing "
181+ "elements ."
212182msgstr ""
213183
214184msgid "Single-threaded performance"
215185msgstr ""
216186
217187msgid ""
218188"The free-threaded build has additional overhead when executing Python code "
219- "compared to the default GIL-enabled build. In 3.13, this overhead is about "
220- "40% on the `pyperformance <https://pyperformance.readthedocs.io/>`_ suite. "
221- "Programs that spend most of their time in C extensions or I/O will see less "
222- "of an impact. The largest impact is because the specializing adaptive "
223- "interpreter (:pep:`659`) is disabled in the free-threaded build."
224- msgstr ""
225-
226- msgid ""
227- "The specializing adaptive interpreter has been re-enabled in a thread-safe "
228- "way in the 3.14 release. The performance penalty on single-threaded code in "
229- "free-threaded mode is now roughly 5-10%, depending on the platform and C "
230- "compiler used."
189+ "compared to the default GIL-enabled build. The amount of overhead depends "
190+ "on the workload and hardware. On the pyperformance benchmark suite, the "
191+ "average overhead ranges from about 1% on macOS aarch64 to 8% on x86-64 Linux "
192+ "systems."
231193msgstr ""
232194
233195msgid "Behavioral changes"
0 commit comments