# Copyright (C) 2001 Python Software Foundation

# This file is distributed under the same license as the Python package.

# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.

#

#, fuzzy

msgid ""

msgstr ""

"Project-Id-Version: Python 3.14\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2026-09-15 00:20+0000\n"

"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

"Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"

"tw)\n"

"Language: zh_TW\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

#: ../../whatsnew/3.14.rst:4

msgid "What's new in Python 3.14"

msgstr "Python 3.14 有什麼新功能"

#: ../../whatsnew/3.14.rst:0

msgid "Editors"

msgstr "編輯者"

#: ../../whatsnew/3.14.rst:6

msgid "Adam Turner and Hugo van Kemenade"

msgstr "Adam Turner 和 Hugo van Kemenade"

#: ../../whatsnew/3.14.rst:48

msgid ""

"This article explains the new features in Python 3.14, compared to 3.13. "

"Python 3.14 was released on 7 October 2025. For full details, see the :ref:"

"`changelog <changelog>`."

msgstr ""

"本文介紹了 Python 3.14 與 3.13 相比多了哪些新功能。Python 3.14 已於 2025 年 "

"10 月 7 日發布。完整詳情請見 :ref:`changelog <changelog>`。"

#: ../../whatsnew/3.14.rst:54

msgid ":pep:`745` -- Python 3.14 release schedule"

msgstr ":pep:`745` - Python 3.14 發佈時程"

#: ../../whatsnew/3.14.rst:58

msgid "Summary -- Release highlights"

msgstr "發布重點摘要"

#: ../../whatsnew/3.14.rst:63

msgid ""

"Python 3.14 is the latest stable release of the Python programming language, "

"with a mix of changes to the language, the implementation, and the standard "

"library. The biggest changes include :ref:`template string literals "

"<whatsnew314-template-string-literals>`, :ref:`deferred evaluation of "

"annotations <whatsnew314-deferred-annotations>`, and support for :ref:"

"`subinterpreters <whatsnew314-multiple-interpreters>` in the standard "

"library."

msgstr ""

"Python 3.14 是 Python 程式語言的最新穩定版本，包含了語言、實作和標準函式庫的"

"各種變更。最大的變更包括\\ :ref:`模板字串字面值 <whatsnew314-template-string-"

"literals>`、:ref:`延遲型別註解的求值 <whatsnew314-deferred-annotations>`，以"

"及標準函式庫中對\\ :ref:`子直譯器 <whatsnew314-multiple-interpreters>`\\ 的支"

"援。"

#: ../../whatsnew/3.14.rst:72

msgid ""

"The library changes include significantly improved capabilities for :ref:"

"`introspection in asyncio <whatsnew314-asyncio-introspection>`, :ref:"

"`support for Zstandard <whatsnew314-zstandard>` via a new :mod:`compression."

"zstd` module, syntax highlighting in the REPL, as well as the usual "

"deprecations and removals, and improvements in user-friendliness and "

"correctness."

msgstr ""

#: ../../whatsnew/3.14.rst:79

msgid ""

"This article doesn't attempt to provide a complete specification of all new "

"features, but instead gives a convenient overview. For full details refer to "

"the documentation, such as the :ref:`Library Reference <library-index>` and :"

"ref:`Language Reference <reference-index>`. To understand the complete "

"implementation and design rationale for a change, refer to the PEP for a "

"particular new feature; but note that PEPs usually are not kept up-to-date "

"once a feature has been fully implemented. See `Porting to Python 3.14`_ for "

"guidance on upgrading from earlier versions of Python."

msgstr ""

#: ../../whatsnew/3.14.rst:95

msgid "Interpreter improvements:"

msgstr "直譯器的改進："

#: ../../whatsnew/3.14.rst:97

msgid ""

":pep:`649` and :pep:`749`: :ref:`Deferred evaluation of annotations "

"<whatsnew314-deferred-annotations>`"

msgstr ""

#: ../../whatsnew/3.14.rst:99

msgid ""

":pep:`734`: :ref:`Multiple interpreters in the standard library <whatsnew314-"

"multiple-interpreters>`"

msgstr ""

#: ../../whatsnew/3.14.rst:101

msgid ""

":pep:`750`: :ref:`Template strings <whatsnew314-template-string-literals>`"

msgstr ""

#: ../../whatsnew/3.14.rst:102

msgid ""

":pep:`758`: :ref:`Allow except and except* expressions without brackets "

"<whatsnew314-bracketless-except>`"

msgstr ""

#: ../../whatsnew/3.14.rst:104

msgid ""

":pep:`765`: :ref:`Control flow in finally blocks <whatsnew314-finally-"

"syntaxwarning>`"

msgstr ""

#: ../../whatsnew/3.14.rst:106

msgid ""

":pep:`768`: :ref:`Safe external debugger interface for CPython <whatsnew314-"

"remote-debugging>`"

msgstr ""

#: ../../whatsnew/3.14.rst:108

msgid ":ref:`A new type of interpreter <whatsnew314-tail-call-interpreter>`"

msgstr ""

#: ../../whatsnew/3.14.rst:109

msgid ""

":ref:`Free-threaded mode improvements <whatsnew314-free-threaded-cpython>`"

msgstr ""

#: ../../whatsnew/3.14.rst:110

msgid ":ref:`Improved error messages <whatsnew314-improved-error-messages>`"

msgstr ""

#: ../../whatsnew/3.14.rst:111

msgid ":ref:`Incremental garbage collection <whatsnew314-incremental-gc>`"

msgstr ""

#: ../../whatsnew/3.14.rst:113

msgid "Significant improvements in the standard library:"

msgstr "標準函式庫中的顯著改進"

#: ../../whatsnew/3.14.rst:115

msgid ""

":pep:`784`: :ref:`Zstandard support in the standard library <whatsnew314-"

"zstandard>`"

msgstr ""

#: ../../whatsnew/3.14.rst:117

msgid ":ref:`whatsnew314-asyncio-introspection`"

msgstr ":ref:`whatsnew314-asyncio-introspection`"

#: ../../whatsnew/3.14.rst:118

msgid ":ref:`whatsnew314-concurrent-warnings-control`"

msgstr ":ref:`whatsnew314-concurrent-warnings-control`"

#: ../../whatsnew/3.14.rst:119

msgid ""

":ref:`Syntax highlighting in the default interactive shell <whatsnew314-"

"pyrepl-highlighting>`, and color output in several standard library CLIs"

msgstr ""

#: ../../whatsnew/3.14.rst:123

msgid "C API improvements:"

msgstr "C API 改進："

#: ../../whatsnew/3.14.rst:125

msgid ":pep:`741`: :ref:`Python configuration C API <whatsnew314-capi-config>`"

msgstr ":pep:`741`: :ref:`Python 配置 C API <whatsnew314-capi-config>`"

#: ../../whatsnew/3.14.rst:127

msgid "Platform support:"

msgstr "平台支援："

#: ../../whatsnew/3.14.rst:129

msgid ""

":pep:`776`: Emscripten is now an :ref:`officially supported platform "

"<whatsnew314-build-changes>`, at :pep:`tier 3 <11#tier-3>`."

msgstr ""

#: ../../whatsnew/3.14.rst:132

msgid "Release changes:"

msgstr ""

#: ../../whatsnew/3.14.rst:134

msgid ""

":pep:`779`: :ref:`Free-threaded Python is officially supported <whatsnew314-"

"free-threaded-now-supported>`"

msgstr ""

#: ../../whatsnew/3.14.rst:136

msgid ""

":pep:`761`: :ref:`PGP signatures have been discontinued for official "

"releases <whatsnew314-no-more-pgp>`"

msgstr ""

#: ../../whatsnew/3.14.rst:138

msgid ""

":ref:`Windows and macOS binary releases now support the experimental just-in-"

"time compiler <whatsnew314-jit-compiler>`"

msgstr ""

#: ../../whatsnew/3.14.rst:140

msgid ""

":ref:`Binary releases for Android are now provided <whatsnew314-build-"

"changes>`"

msgstr ""

#: ../../whatsnew/3.14.rst:144

msgid "New features"

msgstr "新增功能"

#: ../../whatsnew/3.14.rst:149

msgid ":pep:`649` & :pep:`749`: Deferred evaluation of annotations"

msgstr ""

#: ../../whatsnew/3.14.rst:151

msgid ""

"The :term:`annotations <annotation>` on functions, classes, and modules are "

"no longer evaluated eagerly. Instead, annotations are stored in special-"

"purpose :term:`annotate functions <annotate function>` and evaluated only "

"when necessary (except if ``from __future__ import annotations`` is used)."

msgstr ""

#: ../../whatsnew/3.14.rst:156

msgid ""

"This change is designed to improve performance and usability of annotations "

"in Python in most circumstances. The runtime cost for defining annotations "

"is minimized, but it remains possible to introspect annotations at runtime. "

"It is no longer necessary to enclose annotations in strings if they contain "

"forward references."

msgstr ""

#: ../../whatsnew/3.14.rst:162

msgid ""

"The new :mod:`annotationlib` module provides tools for inspecting deferred "

"annotations. Annotations may be evaluated in the :attr:`~annotationlib."

"Format.VALUE` format (which evaluates annotations to runtime values, similar "

"to the behavior in earlier Python versions), the :attr:`~annotationlib."

"Format.FORWARDREF` format (which replaces undefined names with special "

"markers), and the :attr:`~annotationlib.Format.STRING` format (which returns "

"annotations as strings)."

msgstr ""

#: ../../whatsnew/3.14.rst:169

msgid "This example shows how these formats behave:"

msgstr ""

#: ../../whatsnew/3.14.rst:171

msgid ""

">>> from annotationlib import get_annotations, Format\n"

">>> def func(arg: Undefined):\n"

"... pass\n"

">>> get_annotations(func, format=Format.VALUE)\n"

"Traceback (most recent call last):\n"

" ...\n"

"NameError: name 'Undefined' is not defined\n"

">>> get_annotations(func, format=Format.FORWARDREF)\n"

"{'arg': ForwardRef('Undefined', owner=<function func at 0x...>)}\n"

">>> get_annotations(func, format=Format.STRING)\n"

"{'arg': 'Undefined'}"

msgstr ""

">>> from annotationlib import get_annotations, Format\n"

">>> def func(arg: Undefined):\n"

"... pass\n"

">>> get_annotations(func, format=Format.VALUE)\n"

"Traceback (most recent call last):\n"

" ...\n"

"NameError: name 'Undefined' is not defined\n"

">>> get_annotations(func, format=Format.FORWARDREF)\n"

"{'arg': ForwardRef('Undefined', owner=<function func at 0x...>)}\n"

">>> get_annotations(func, format=Format.STRING)\n"

"{'arg': 'Undefined'}"

#: ../../whatsnew/3.14.rst:185

msgid ""

"The :ref:`porting <whatsnew314-porting-annotations>` section contains "

"guidance on changes that may be needed due to these changes, though in the "

"majority of cases, code will continue working as-is."

msgstr ""

#: ../../whatsnew/3.14.rst:189

msgid ""

"(Contributed by Jelle Zijlstra in :pep:`749` and :gh:`119180`; :pep:`649` "

"was written by Larry Hastings.)"

msgstr ""

"（由 Jelle Zijlstra 於 :pep:`749` 和 :gh:`119180` 貢獻；:pep:`649` 由 Larry "

"Hastings 撰寫。）"

#: ../../whatsnew/3.14.rst:194

msgid ":pep:`649`"

msgstr ":pep:`649`"

#: ../../whatsnew/3.14.rst:195

msgid "Deferred Evaluation Of Annotations Using Descriptors"

msgstr ""

#: ../../whatsnew/3.14.rst:196

msgid ":pep:`749`"

msgstr ":pep:`749`"

#: ../../whatsnew/3.14.rst:197

msgid "Implementing PEP 649"

msgstr "實作 PEP 649"

#: ../../whatsnew/3.14.rst:203

msgid ":pep:`734`: Multiple interpreters in the standard library"

msgstr ""

#: ../../whatsnew/3.14.rst:205

msgid ""

"The CPython runtime supports running multiple copies of Python in the same "

"process simultaneously and has done so for over 20 years. Each of these "

"separate copies is called an 'interpreter'. However, the feature had been "

"available only through the :ref:`C-API <sub-interpreter-support>`."

msgstr ""

#: ../../whatsnew/3.14.rst:211

msgid ""

"That limitation is removed in Python 3.14, with the new :mod:`concurrent."

"interpreters` module."

msgstr ""

#: ../../whatsnew/3.14.rst:214

msgid ""

"There are at least two notable reasons why using multiple interpreters has "

"significant benefits:"

msgstr ""

#: ../../whatsnew/3.14.rst:217

msgid "they support a new (to Python), human-friendly concurrency model"

msgstr ""

#: ../../whatsnew/3.14.rst:218

msgid "true multi-core parallelism"

msgstr ""

#: ../../whatsnew/3.14.rst:220

msgid ""

"For some use cases, concurrency in software improves efficiency and can "

"simplify design, at a high level. At the same time, implementing and "

"maintaining all but the simplest concurrency is often a struggle for the "

"human brain. That especially applies to plain threads (for example, :mod:"

"`threading`), where all memory is shared between all threads."

msgstr ""

#: ../../whatsnew/3.14.rst:227

msgid ""

"With multiple isolated interpreters, you can take advantage of a class of "

"concurrency models, like Communicating Sequential Processes (CSP) or the "

"actor model, that have found success in other programming languages, like "

"Smalltalk, Erlang, Haskell, and Go. Think of multiple interpreters as "

"threads but with opt-in sharing."

msgstr ""

#: ../../whatsnew/3.14.rst:234

msgid ""

"Regarding multi-core parallelism: as of Python 3.12, interpreters are now "

"sufficiently isolated from one another to be used in parallel (see :pep:"

"`684`). This unlocks a variety of CPU-intensive use cases for Python that "

"were limited by the :term:`GIL`."

msgstr ""

#: ../../whatsnew/3.14.rst:239

msgid ""

"Using multiple interpreters is similar in many ways to :mod:"

"`multiprocessing`, in that they both provide isolated logical \"processes\" "

"that can run in parallel, with no sharing by default. However, when using "

"multiple interpreters, an application will use fewer system resources and "

"will operate more efficiently (since it stays within the same process). "

"Think of multiple interpreters as having the isolation of processes with the "

"efficiency of threads."

msgstr ""

#: ../../whatsnew/3.14.rst:250

msgid ""

"While the feature has been around for decades, multiple interpreters have "

"not been used widely, due to low awareness and the lack of a standard "

"library module. Consequently, they currently have several notable "

"limitations, which are expected to improve significantly now that the "

"feature is going mainstream."

msgstr ""

#: ../../whatsnew/3.14.rst:256

msgid "Current limitations:"

msgstr ""

#: ../../whatsnew/3.14.rst:258

msgid "starting each interpreter has not been optimized yet"

msgstr ""

#: ../../whatsnew/3.14.rst:259

msgid ""

"each interpreter uses more memory than necessary (work continues on "

"extensive internal sharing between interpreters)"

msgstr ""

#: ../../whatsnew/3.14.rst:261

msgid ""

"there aren't many options *yet* for truly sharing objects or other data "

"between interpreters (other than :type:`memoryview`)"

msgstr ""

#: ../../whatsnew/3.14.rst:263

msgid ""

"many third-party extension modules on PyPI are not yet compatible with "

"multiple interpreters (all standard library extension modules *are* "

"compatible)"

msgstr ""

#: ../../whatsnew/3.14.rst:266

msgid ""

"the approach to writing applications that use multiple isolated interpreters "

"is mostly unfamiliar to Python users, for now"

msgstr ""

#: ../../whatsnew/3.14.rst:269

msgid ""

"The impact of these limitations will depend on future CPython improvements, "

"how interpreters are used, and what the community solves through PyPI "

"packages. Depending on the use case, the limitations may not have much "

"impact, so try it out!"

msgstr ""

#: ../../whatsnew/3.14.rst:274

msgid ""

"Furthermore, future CPython releases will reduce or eliminate overhead and "

"provide utilities that are less appropriate on PyPI. In the meantime, most "

"of the limitations can also be addressed through extension modules, meaning "

"PyPI packages can fill any gap for 3.14, and even back to 3.12 where "

"interpreters were finally properly isolated and stopped sharing the :term:"

"`GIL`. Likewise, libraries on PyPI are expected to emerge for high-level "

"abstractions on top of interpreters."

msgstr ""

#: ../../whatsnew/3.14.rst:282

msgid ""

"Regarding extension modules, work is in progress to update some PyPI "

"projects, as well as tools like Cython, pybind11, nanobind, and PyO3. The "

"steps for isolating an extension module are found at :ref:`isolating-"

"extensions-howto`. Isolating a module has a lot of overlap with what is "

"required to support :ref:`free-threading <whatsnew314-free-threaded-"

"cpython>`, so the ongoing work in the community in that area will help "

"accelerate support for multiple interpreters."

msgstr ""

#: ../../whatsnew/3.14.rst:291

msgid ""

"Also added in 3.14: :ref:`concurrent.futures.InterpreterPoolExecutor "

"<whatsnew314-concurrent-futures-interp-pool>`."

msgstr ""

#: ../../whatsnew/3.14.rst:294

msgid "(Contributed by Eric Snow in :gh:`134939`.)"

msgstr "（由 Eric Snow 於 :gh:`134939` 貢獻。）"

#: ../../whatsnew/3.14.rst:296

msgid ":pep:`734`"

msgstr ":pep:`734`"

#: ../../whatsnew/3.14.rst:302

msgid ":pep:`750`: Template string literals"

msgstr ""

#: ../../whatsnew/3.14.rst:304

msgid ""

"Template strings are a new mechanism for custom string processing. They "

"share the familiar syntax of f-strings but, unlike f-strings, return an "

"object representing the static and interpolated parts of the string, instead "

"of a simple :class:`str`."

msgstr ""

#: ../../whatsnew/3.14.rst:309

msgid "To write a t-string, use a ``'t'`` prefix instead of an ``'f'``:"

msgstr ""

#: ../../whatsnew/3.14.rst:311

msgid ""

">>> variety = 'Stilton'\n"

">>> template = t'Try some {variety} cheese!'\n"

">>> type(template)\n"

"<class 'string.templatelib.Template'>"

msgstr ""

">>> variety = 'Stilton'\n"

">>> template = t'Try some {variety} cheese!'\n"

">>> type(template)\n"

"<class 'string.templatelib.Template'>"

#: ../../whatsnew/3.14.rst:318

msgid ""

":class:`~string.templatelib.Template` objects provide access to the static "

"and interpolated (in curly braces) parts of a string *before* they are "

"combined. Iterate over :class:`!Template` instances to access their parts in "

"order:"

msgstr ""

#: ../../whatsnew/3.14.rst:327

msgid ""

">>> list(template)\n"

"['Try some ', Interpolation('Stilton', 'variety', None, ''), ' cheese!']"

msgstr ""

">>> list(template)\n"

"['Try some ', Interpolation('Stilton', 'variety', None, ''), ' cheese!']"

#: ../../whatsnew/3.14.rst:332

msgid ""

"It's easy to write (or call) code to process :class:`!Template` instances. "

"For example, here's a function that renders static parts lowercase and :"

"class:`~string.templatelib.Interpolation` instances uppercase:"

msgstr ""

#: ../../whatsnew/3.14.rst:336

msgid ""

"from string.templatelib import Interpolation\n"

"\n"

"def lower_upper(template):\n"

" \"\"\"Render static parts lowercase and interpolations uppercase.\"\"\"\n"

" parts = []\n"

" for part in template:\n"

" if isinstance(part, Interpolation):\n"

" parts.append(str(part.value).upper())\n"

" else:\n"

" parts.append(part.lower())\n"

" return ''.join(parts)\n"

"\n"

"name = 'Wenslydale'\n"

"template = t'Mister {name}'\n"

"assert lower_upper(template) == 'mister WENSLYDALE'"

msgstr ""

#: ../../whatsnew/3.14.rst:354

msgid ""

"Because :class:`!Template` instances distinguish between static strings and "

"interpolations at runtime, they can be useful for sanitising user input. "

"Writing a :func:`!html` function that escapes user input in HTML is an "

"exercise left to the reader! Template processing code can provide improved "

"flexibility. For instance, a more advanced :func:`!html` function could "

"accept a :class:`!dict` of HTML attributes directly in the template:"

msgstr ""

#: ../../whatsnew/3.14.rst:362

msgid ""

"attributes = {'src': 'limburger.jpg', 'alt': 'lovely cheese'}\n"

"template = t'<img {attributes}>'\n"

"assert html(template) == '<img src=\"limburger.jpg\" alt=\"lovely cheese\" /"

">'"

msgstr ""

#: ../../whatsnew/3.14.rst:368

msgid ""

"Of course, template processing code does not need to return a string-like "

"result. An even *more* advanced :func:`!html` could return a custom type "

"representing a DOM-like structure."

msgstr ""

#: ../../whatsnew/3.14.rst:372

msgid ""

"With t-strings in place, developers can write systems that sanitise SQL, "

"make safe shell operations, improve logging, tackle modern ideas in web "

"development (HTML, CSS, and so on), and implement lightweight custom "

"business DSLs."

msgstr ""

#: ../../whatsnew/3.14.rst:376

msgid ""

"(Contributed by Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, "

"Lysandros Nikolaou, Dave Peck, Adam Turner, Jelle Zijlstra, Bénédikt Tran, "

"and Pablo Galindo Salgado in :gh:`132661`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:380

msgid ":pep:`750`."

msgstr ":pep:`750`。"

#: ../../whatsnew/3.14.rst:386

msgid ":pep:`768`: Safe external debugger interface"

msgstr ""

#: ../../whatsnew/3.14.rst:388

msgid ""

"Python 3.14 introduces a zero-overhead debugging interface that allows "

"debuggers and profilers to safely attach to running Python processes without "

"stopping or restarting them. This is a significant enhancement to Python's "

"debugging capabilities, meaning that unsafe alternatives are no longer "

"required."

msgstr ""

#: ../../whatsnew/3.14.rst:394

msgid ""

"The new interface provides safe execution points for attaching debugger code "

"without modifying the interpreter's normal execution path or adding any "

"overhead at runtime. Due to this, tools can now inspect and interact with "

"Python applications in real-time, which is a crucial capability for high-"

"availability systems and production environments."

msgstr ""

#: ../../whatsnew/3.14.rst:401

msgid ""

"For convenience, this interface is implemented in the :func:`sys."

"remote_exec` function. For example:"

msgstr ""

#: ../../whatsnew/3.14.rst:404

msgid ""

"import sys\n"

"from tempfile import NamedTemporaryFile\n"

"\n"

"with NamedTemporaryFile(mode='w', suffix='.py', delete=False) as f:\n"

" script_path = f.name\n"

" f.write(f'import my_debugger; my_debugger.connect({os.getpid()})')\n"

"\n"

"# Execute in process with PID 1234\n"

"print('Behold! An offering:')\n"

"sys.remote_exec(1234, script_path)"

msgstr ""

"import sys\n"

"from tempfile import NamedTemporaryFile\n"

"\n"

"with NamedTemporaryFile(mode='w', suffix='.py', delete=False) as f:\n"

" script_path = f.name\n"

" f.write(f'import my_debugger; my_debugger.connect({os.getpid()})')\n"

"\n"

"# 在 PID 1234 的行程中執行\n"

"print('Behold! An offering:')\n"

"sys.remote_exec(1234, script_path)"

#: ../../whatsnew/3.14.rst:418

msgid ""

"This function allows sending Python code to be executed in a target process "

"at the next safe execution point. However, tool authors can also implement "

"the protocol directly as described in the PEP, which details the underlying "

"mechanisms used to safely attach to running processes."

msgstr ""

#: ../../whatsnew/3.14.rst:424

msgid ""

"The debugging interface has been carefully designed with security in mind "

"and includes several mechanisms to control access:"

msgstr ""

#: ../../whatsnew/3.14.rst:427

msgid "A :envvar:`PYTHON_DISABLE_REMOTE_DEBUG` environment variable."

msgstr ""

#: ../../whatsnew/3.14.rst:428

msgid "A :option:`-X disable-remote-debug` command-line option."

msgstr ""

#: ../../whatsnew/3.14.rst:429

msgid ""

"A :option:`--without-remote-debug` configure flag to completely disable the "

"feature at build time."

msgstr ""

#: ../../whatsnew/3.14.rst:432

msgid ""

"(Contributed by Pablo Galindo Salgado, Matt Wozniski, and Ivona Stojanovic "

"in :gh:`131591`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:435

msgid ":pep:`768`."

msgstr ":pep:`768`。"

#: ../../whatsnew/3.14.rst:441

msgid "A new type of interpreter"

msgstr ""

#: ../../whatsnew/3.14.rst:443

msgid ""

"A new type of interpreter has been added to CPython. It uses tail calls "

"between small C functions that implement individual Python opcodes, rather "

"than one large C ``case`` statement. For certain newer compilers, this "

"interpreter provides significantly better performance. Preliminary "

"benchmarks suggest a geometric mean of 3-5% faster on the standard "

"``pyperformance`` benchmark suite, depending on platform and architecture. "

"The baseline is Python 3.14 built with Clang 19, without this new "

"interpreter."

msgstr ""

#: ../../whatsnew/3.14.rst:452

msgid ""

"This interpreter currently only works with Clang 19 and newer on x86-64 and "

"AArch64 architectures. However, a future release of GCC is expected to "

"support this as well."

msgstr ""

#: ../../whatsnew/3.14.rst:456

msgid ""

"This feature is opt-in for now. Enabling profile-guided optimization is "

"highly recommended when using the new interpreter as it is the only "

"configuration that has been tested and validated for improved performance. "

"For further information, see :option:`--with-tail-call-interp`."

msgstr ""

#: ../../whatsnew/3.14.rst:463

msgid ""

"This is not to be confused with `tail call optimization`__ of Python "

"functions, which is currently not implemented in CPython."

msgstr ""

#: ../../whatsnew/3.14.rst:466

msgid ""

"This new interpreter type is an internal implementation detail of the "

"CPython interpreter. It doesn't change the visible behavior of Python "

"programs at all. It can improve their performance, but doesn't change "

"anything else."

msgstr ""

#: ../../whatsnew/3.14.rst:472

msgid ""

"(Contributed by Ken Jin in :gh:`128563`, with ideas on how to implement this "

"in CPython by Mark Shannon, Garrett Gu, Haoran Xu, and Josh Haberman.)"

msgstr ""

#: ../../whatsnew/3.14.rst:479

msgid "Free-threaded mode improvements"

msgstr ""

#: ../../whatsnew/3.14.rst:481

msgid ""

"CPython's free-threaded mode (:pep:`703`), initially added in 3.13, has been "

"significantly improved in Python 3.14. The implementation described in PEP "

"703 has been finished, including C API changes, and temporary workarounds in "

"the interpreter were replaced with more permanent solutions. The "

"specializing adaptive interpreter (:pep:`659`) is now enabled in free-"

"threaded mode, which along with many other optimizations greatly improves "

"its performance. The performance penalty on single-threaded code in free-"

"threaded mode is now roughly 5-10%, depending on the platform and C compiler "

"used."

msgstr ""

#: ../../whatsnew/3.14.rst:492

msgid ""

"From Python 3.14, when compiling extension modules for the free-threaded "

"build of CPython on Windows, the preprocessor variable ``Py_GIL_DISABLED`` "

"now needs to be specified by the build backend, as it will no longer be "

"determined automatically by the C compiler. For a running interpreter, the "

"setting that was used at compile time can be found using :func:`sysconfig."

"get_config_var`."

msgstr ""

#: ../../whatsnew/3.14.rst:498

msgid ""

"The new :option:`-X context_aware_warnings <-X>` flag controls if :ref:"

"`concurrent safe warnings control <whatsnew314-concurrent-warnings-control>` "

"is enabled. The flag defaults to true for the free-threaded build and false "

"for the GIL-enabled build."

msgstr ""

#: ../../whatsnew/3.14.rst:503

msgid ""

"A new :data:`~sys.flags.thread_inherit_context` flag has been added, which "

"if enabled means that threads created with :class:`threading.Thread` start "

"with a copy of the :class:`~contextvars.Context()` of the caller of :meth:"

"`~threading.Thread.start`. Most significantly, this makes the warning "

"filtering context established by :class:`~warnings.catch_warnings` be "

"\"inherited\" by threads (or asyncio tasks) started within that context. It "

"also affects other modules that use context variables, such as the :mod:"

"`decimal` context manager. This flag defaults to true for the free-threaded "

"build and false for the GIL-enabled build."

msgstr ""

#: ../../whatsnew/3.14.rst:514

msgid ""

"(Contributed by Sam Gross, Matt Page, Neil Schemenauer, Thomas Wouters, "

"Donghee Na, Kirill Podoprigora, Ken Jin, Itamar Oren, Brett Simmers, Dino "

"Viehland, Nathan Goldbaum, Ralf Gommers, Lysandros Nikolaou, Kumar Aditya, "

"Edgar Margffoy, and many others. Some of these contributors are employed by "

"Meta, which has continued to provide significant engineering resources to "

"support this project.)"

msgstr ""

#: ../../whatsnew/3.14.rst:525

msgid "Improved error messages"

msgstr "改善錯誤訊息"

#: ../../whatsnew/3.14.rst:527

msgid ""

"The interpreter now provides helpful suggestions when it detects typos in "

"Python keywords. When a word that closely resembles a Python keyword is "

"encountered, the interpreter will suggest the correct keyword in the error "

"message. This feature helps programmers quickly identify and fix common "

"typing mistakes. For example:"

msgstr ""

#: ../../whatsnew/3.14.rst:533

msgid ""

">>> whille True:\n"

"... pass\n"

"Traceback (most recent call last):\n"

" File \"<stdin>\", line 1\n"

" whille True:\n"

" ^^^^^^\n"

"SyntaxError: invalid syntax. Did you mean 'while'?"

msgstr ""

">>> whille True:\n"

"... pass\n"

"Traceback (most recent call last):\n"

" File \"<stdin>\", line 1\n"

" whille True:\n"

" ^^^^^^\n"

"SyntaxError: invalid syntax. Did you mean 'while'?"

#: ../../whatsnew/3.14.rst:543

msgid ""

"While the feature focuses on the most common cases, some variations of "

"misspellings may still result in regular syntax errors. (Contributed by "

"Pablo Galindo in :gh:`132449`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:547

msgid ""

":keyword:`elif` statements that follow an :keyword:`else` block now have a "

"specific error message. (Contributed by Steele Farnsworth in :gh:`129902`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:551

msgid ""

">>> if who == \"me\":\n"

"... print(\"It's me!\")\n"

"... else:\n"

"... print(\"It's not me!\")\n"

"... elif who is None:\n"

"... print(\"Who is it?\")\n"

"File \"<stdin>\", line 5\n"

" elif who is None:\n"

" ^^^^\n"

"SyntaxError: 'elif' block follows an 'else' block"

msgstr ""

">>> if who == \"me\":\n"

"... print(\"It's me!\")\n"

"... else:\n"

"... print(\"It's not me!\")\n"

"... elif who is None:\n"

"... print(\"Who is it?\")\n"

"File \"<stdin>\", line 5\n"

" elif who is None:\n"

" ^^^^\n"

"SyntaxError: 'elif' block follows an 'else' block"

#: ../../whatsnew/3.14.rst:564

msgid ""

"If a statement is passed to the :ref:`if_expr` after :keyword:`else`, or one "

"of :keyword:`pass`, :keyword:`break`, or :keyword:`continue` is passed "

"before :keyword:`if`, then the error message highlights where the :token:"

"`~python-grammar:expression` is required. (Contributed by Sergey Miryanov "

"in :gh:`129515`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:570

msgid ""

">>> x = 1 if True else pass\n"

"Traceback (most recent call last):\n"

" File \"<string>\", line 1\n"

" x = 1 if True else pass\n"

" ^^^^\n"

"SyntaxError: expected expression after 'else', but statement is given\n"

"\n"

">>> x = continue if True else break\n"

"Traceback (most recent call last):\n"

" File \"<string>\", line 1\n"

" x = continue if True else break\n"

" ^^^^^^^^\n"

"SyntaxError: expected expression before 'if', but statement is given"

msgstr ""

">>> x = 1 if True else pass\n"

"Traceback (most recent call last):\n"

" File \"<string>\", line 1\n"

" x = 1 if True else pass\n"

" ^^^^\n"

"SyntaxError: expected expression after 'else', but statement is given\n"

"\n"

">>> x = continue if True else break\n"

"Traceback (most recent call last):\n"

" File \"<string>\", line 1\n"

" x = continue if True else break\n"

" ^^^^^^^^\n"

"SyntaxError: expected expression before 'if', but statement is given"

#: ../../whatsnew/3.14.rst:586

msgid ""

"When incorrectly closed strings are detected, the error message suggests "

"that the string may be intended to be part of the string. (Contributed by "

"Pablo Galindo in :gh:`88535`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:590

msgid ""

">>> \"The interesting object \"The important object\" is very important\"\n"

"Traceback (most recent call last):\n"

"SyntaxError: invalid syntax. Is this intended to be part of the string?"

msgstr ""

">>> \"The interesting object \"The important object\" is very important\"\n"

"Traceback (most recent call last):\n"

"SyntaxError: invalid syntax. Is this intended to be part of the string?"

#: ../../whatsnew/3.14.rst:596

msgid ""

"When strings have incompatible prefixes, the error now shows which prefixes "

"are incompatible. (Contributed by Nikita Sobolev in :gh:`133197`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:600

msgid ""

">>> ub'abc'\n"

" File \"<python-input-0>\", line 1\n"

" ub'abc'\n"

" ^^\n"

"SyntaxError: 'u' and 'b' prefixes are incompatible"

msgstr ""

">>> ub'abc'\n"

" File \"<python-input-0>\", line 1\n"

" ub'abc'\n"

" ^^\n"

"SyntaxError: 'u' and 'b' prefixes are incompatible"

#: ../../whatsnew/3.14.rst:608

msgid "Improved error messages when using ``as`` with incompatible targets in:"

msgstr ""

#: ../../whatsnew/3.14.rst:610

msgid "Imports: ``import ... as ...``"

msgstr ""

#: ../../whatsnew/3.14.rst:611

msgid "From imports: ``from ... import ... as ...``"

msgstr ""

#: ../../whatsnew/3.14.rst:612

msgid "Except handlers: ``except ... as ...``"

msgstr ""

#: ../../whatsnew/3.14.rst:613

msgid "Pattern-match cases: ``case ... as ...``"

msgstr ""

#: ../../whatsnew/3.14.rst:615

msgid ""

"(Contributed by Nikita Sobolev in :gh:`123539`, :gh:`123562`, and :gh:"

"`123440`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:617

msgid ""

"Improved error message when trying to add an instance of an unhashable type "

"to a :class:`dict` or :class:`set`. (Contributed by CF Bolz-Tereick and "

"Victor Stinner in :gh:`132828`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:621

msgid ""

">>> s = set()\n"

">>> s.add({'pages': 12, 'grade': 'A'})\n"

"Traceback (most recent call last):\n"

" File \"<python-input-1>\", line 1, in <module>\n"

" s.add({'pages': 12, 'grade': 'A'})\n"

" ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n"

"TypeError: cannot use 'dict' as a set element (unhashable type: 'dict')\n"

">>> d = {}\n"

">>> l = [1, 2, 3]\n"

">>> d[l] = 12\n"

"Traceback (most recent call last):\n"

" File \"<python-input-4>\", line 1, in <module>\n"

" d[l] = 12\n"

" ~^^^\n"

"TypeError: cannot use 'list' as a dict key (unhashable type: 'list')"

msgstr ""

">>> s = set()\n"

">>> s.add({'pages': 12, 'grade': 'A'})\n"

"Traceback (most recent call last):\n"

" File \"<python-input-1>\", line 1, in <module>\n"

" s.add({'pages': 12, 'grade': 'A'})\n"

" ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n"

"TypeError: cannot use 'dict' as a set element (unhashable type: 'dict')\n"

">>> d = {}\n"

">>> l = [1, 2, 3]\n"

">>> d[l] = 12\n"

"Traceback (most recent call last):\n"

" File \"<python-input-4>\", line 1, in <module>\n"

" d[l] = 12\n"

" ~^^^\n"

"TypeError: cannot use 'list' as a dict key (unhashable type: 'list')"

#: ../../whatsnew/3.14.rst:639

msgid ""

"Improved error message when an object supporting the synchronous context "

"manager protocol is entered using :keyword:`async with` instead of :keyword:"

"`with`, and vice versa for the asynchronous context manager protocol. "

"(Contributed by Bénédikt Tran in :gh:`128398`.)"

msgstr ""

#: ../../whatsnew/3.14.rst:649

msgid ":pep:`784`: Zstandard support in the standard library"

msgstr ":pep:`784`：標準函式庫中的 Zstandard 支援"