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