# Python 3.12 有什麼新功能

編輯者:

  Adam Turner

本文介紹了 Python 3.12 與 3.11 相比多了哪些新功能。 Python 3.12 於 2023 年 10 月 2 日發布。完整詳情請見 changelog。

也參考

PEP 693 -- Python 3.12 發佈時程

## 發布重點摘要

Python 3.12 是 Python 程式語言的穩定版本，包含了語言和標準函式庫的綜合變更。標準函式庫的變更主要集中在清理棄用的 API、可用性和正確性。值得注意的是，`distutils` 套件已從標準函式庫中移除。`os` 和 `pathlib` 中的檔案系統支援進行了許多改進，並且有數個模組得到更好的效能。

語言變更主要集中在可用性，因為 f-字串已經移除了許多限制，並且持續改進 'Did you mean ...' 建議。新的型別參數語法和 `type` 陳述式改進了泛型型別和型別別名在與靜態型別檢查器一起使用上的效率。

這篇文章並不試圖提供所有新功能的完整規格，而是提供一個方便的概覽。完整詳情應參考文件，如標準函式庫參考和語言參考。如果你想了解某個新功能的完整實作和設計理念，請參考該功能的 PEP；但請注意 PEP 通常在功能完全實作後就不再更新。

新增語法特性：

- PEP 695，型別參數語法和 `type` 陳述式

新增語法特性：

- PEP 701，文法中的 f-字串

直譯器改進：

- PEP 684，直譯器各別持有的 GIL

- PEP 669，低影響監控

- Improved 'Did you mean ...' suggestions for `NameError`, `ImportError`, and `SyntaxError` exceptions

Python 資料模型改進：

- PEP 688, using the buffer protocol from Python

標準函式庫中的顯著改進

- `pathlib.Path` 類別現在支援子類別化

- `os` 模組在 Windows 支援上有了數項改進

- 一個命令列介面已被加入 `sqlite3` 模組中

- `isinstance()` checks against `runtime-checkable protocols` enjoy a speed up of between two and 20 times

- `asyncio` 套件進行了許多效能改進，一些基準測試顯示速度提高了 75%。

- 一個命令列介面已被加入 `uuid` 模組中

- Due to the changes in PEP 701, producing tokens via the `tokenize` module is up to 64% faster.

安全性改進：

- Replace the builtin `hashlib` implementations of SHA1, SHA3, SHA2-384, SHA2-512, and MD5 with formally verified code from the HACL* project. These builtin implementations remain as fallbacks that are only used when OpenSSL does not provide them.

C API 改進：

- PEP 697，不穩定 C API 層

- PEP 683, immortal objects

CPython 實作改進：

- PEP 709, comprehension inlining

- CPython support for the Linux `perf` profiler

- Implement stack overflow protection on supported platforms

新增型別特性：

- PEP 692、使用 `TypedDict` 來標註 **kwargs

- PEP 698、`typing.override()` 裝飾器

重要的棄用、刪除或限制：

- PEP 623: Remove `wstr` from Unicode objects in Python's C API, reducing the size of every `str` object by at least 8 bytes.

- PEP 632: Remove the `distutils` package. See the migration guide for advice replacing the APIs it provided. The third-party Setuptools package continues to provide `distutils`, if you still require it in Python 3.12 and beyond.

- gh-95299: Do not pre-install `setuptools` in virtual environments created with `venv`. This means that `distutils`, `setuptools`, `pkg_resources`, and `easy_install` will no longer available by default; to access these run `pip install setuptools` in the activated virtual environment.

- `asynchat`、`asyncore` 和 `imp` 模組以及幾個 `unittest.TestCase` 的方法別名已被刪除。

## 新增功能

### PEP 695：型別參數語法

Generic classes and functions under PEP 484 were declared using a verbose syntax that left the scope of type parameters unclear and required explicit declarations of variance.

PEP 695 introduces a new, more compact and explicit way to create generic classes and functions:

    def max[T](args: Iterable[T]) -> T:
        ...

    class list[T]:
        def __getitem__(self, index: int, /) -> T:
            ...

        def append(self, element: T) -> None:
            ...

In addition, the PEP introduces a new way to declare type aliases using the `type` statement, which creates an instance of `TypeAliasType`:

    type Point = tuple[float, float]

型別別名也可以是泛型：

    type Point[T] = tuple[T, T]

The new syntax allows declaring `TypeVarTuple` and `ParamSpec` parameters, as well as `TypeVar` parameters with bounds or constraints:

    type IntFunc[**P] = Callable[P, int]  # ParamSpec
    type LabeledTuple[*Ts] = tuple[str, *Ts]  # TypeVarTuple
    type HashableSequence[T: Hashable] = Sequence[T]  # 帶有邊界的 TypeVar
    type IntOrStrSequence[T: (int, str)] = Sequence[T]  # 帶有限制的 TypeVar

The value of type aliases and the bound and constraints of type variables created through this syntax are evaluated only on demand (see lazy evaluation). This means type aliases are able to refer to other types defined later in the file.

Type parameters declared through a type parameter list are visible within the scope of the declaration and any nested scopes, but not in the outer scope. For example, they can be used in the type annotations for the methods of a generic class or in the class body. However, they cannot be used in the module scope after the class is defined. See Type parameter lists for a detailed description of the runtime semantics of type parameters.

In order to support these scoping semantics, a new kind of scope is introduced, the annotation scope. Annotation scopes behave for the most part like function scopes, but interact differently with enclosing class scopes. In Python 3.13, annotations will also be evaluated in annotation scopes.

詳情請見 PEP 695。

（PEP 由 Eric Traut 撰寫。由 Jelle Zijlstra、Eric Traut 和其他人在 gh-103764 中實作。）

### PEP 701: Syntactic formalization of f-strings

PEP 701 lifts some restrictions on the usage of f-strings. Expression components inside f-strings can now be any valid Python expression, including strings reusing the same quote as the containing f-string, multi-line expressions, comments, backslashes, and unicode escape sequences. Let's cover these in detail:

- Quote reuse: in Python 3.11, reusing the same quotes as the enclosing f-string raises a `SyntaxError`, forcing the user to either use other available quotes (like using double quotes or triple quotes if the f-string uses single quotes). In Python 3.12, you can now do things like this:

      >>> songs = ['Take me back to Eden', 'Alkaline', 'Ascensionism']
      >>> f"This is the playlist: {", ".join(songs)}"
      'This is the playlist: Take me back to Eden, Alkaline, Ascensionism'

  Note that before this change there was no explicit limit in how f-strings can be nested, but the fact that string quotes cannot be reused inside the expression component of f-strings made it impossible to nest f-strings arbitrarily. In fact, this is the most nested f-string that could be written:

      >>> f"""{f'''{f'{f"{1+1}"}'}'''}"""
      '2'

  As now f-strings can contain any valid Python expression inside expression components, it is now possible to nest f-strings arbitrarily:

      >>> f"{f"{f"{f"{f"{f"{1+1}"}"}"}"}"}"
      '2'

- Multi-line expressions and comments: In Python 3.11, f-string expressions must be defined in a single line, even if the expression within the f-string could normally span multiple lines (like literal lists being defined over multiple lines), making them harder to read. In Python 3.12 you can now define f-strings spanning multiple lines, and add inline comments:

      >>> f"This is the playlist: {", ".join([
      ...     'Take me back to Eden',  # My, my, those eyes like fire
      ...     'Alkaline',              # Not acid nor alkaline
      ...     'Ascensionism'           # Take to the broken skies at last
      ... ])}"
      'This is the playlist: Take me back to Eden, Alkaline, Ascensionism'

- Backslashes and unicode characters: before Python 3.12 f-string expressions couldn't contain any `\` character. This also affected unicode escape sequences (such as `\N{snowman}`) as these contain the `\N` part that previously could not be part of expression components of f-strings. Now, you can define expressions like this:

      >>> print(f"This is the playlist: {"\n".join(songs)}")
      This is the playlist: Take me back to Eden
      Alkaline
      Ascensionism
      >>> print(f"This is the playlist: {"\N{BLACK HEART SUIT}".join(songs)}")
      This is the playlist: Take me back to Eden♥Alkaline♥Ascensionism

詳情請見 PEP 701。

As a positive side-effect of how this feature has been implemented (by parsing f-strings with the PEG parser), now error messages for f-strings are more precise and include the exact location of the error. For example, in Python 3.11, the following f-string raises a `SyntaxError`:

    >>> my_string = f"{x z y}" + f"{1 + 1}"
      File "<stdin>", line 1
        (x z y)
         ^^^
    SyntaxError: f-string: invalid syntax. Perhaps you forgot a comma?

but the error message doesn't include the exact location of the error within the line and also has the expression artificially surrounded by parentheses. In Python 3.12, as f-strings are parsed with the PEG parser, error messages can be more precise and show the entire line:

    >>> my_string = f"{x z y}" + f"{1 + 1}"
      File "<stdin>", line 1
        my_string = f"{x z y}" + f"{1 + 1}"
                       ^^^
    SyntaxError: invalid syntax. Perhaps you forgot a comma?

(Contributed by Pablo Galindo, Batuhan Taskaya, Lysandros Nikolaou, Cristián Maureira-Fredes and Marta Gómez in gh-102856. PEP written by Pablo Galindo, Batuhan Taskaya, Lysandros Nikolaou and Marta Gómez).

### PEP 684：直譯器各別持有的 GIL

PEP 684 引入了直譯器各別持有的 GIL，因此子直譯器現在可以使用各個直譯器特有的 GIL 來建立。這使得 Python 程式可以充分利用多個 CPU 核心。目前這僅透過 C-API 使用，不過 Python API 預計在 3.13 中釋出。

Use the new `Py_NewInterpreterFromConfig()` function to create an interpreter with its own GIL:

    PyInterpreterConfig config = {
        .check_multi_interp_extensions = 1,
        .gil = PyInterpreterConfig_OWN_GIL,
    };
    PyThreadState *tstate = NULL;
    PyStatus status = Py_NewInterpreterFromConfig(&tstate, &config);
    if (PyStatus_Exception(status)) {
        return -1;
    }
    /* 新的直譯器現在會在目前執行緒中啟用。 */

For further examples how to use the C-API for sub-interpreters with a per-interpreter GIL, see `Modules/_xxsubinterpretersmodule.c`.

（由 Eric Snow 於 gh-104210 等貢獻。）

### PEP 669: Low impact monitoring for CPython

PEP 669 defines a new `API` for profilers, debuggers, and other tools to monitor events in CPython. It covers a wide range of events, including calls, returns, lines, exceptions, jumps, and more. This means that you only pay for what you use, providing support for near-zero overhead debuggers and coverage tools. See `sys.monitoring` for details.

（由 Mark Shannon 於 gh-103082 中貢獻。）

### PEP 688：使緩衝區協定可在 Python 中存取

PEP 688 introduces a way to use the buffer protocol from Python code. Classes that implement the `__buffer__()` method are now usable as buffer types.

The new `collections.abc.Buffer` ABC provides a standard way to represent buffer objects, for example in type annotations. The new `inspect.BufferFlags` enum represents the flags that can be used to customize buffer creation. (Contributed by Jelle Zijlstra in gh-102500.)

### PEP 709: Comprehension inlining

Dictionary, list, and set comprehensions are now inlined, rather than creating a new single-use function object for each execution of the comprehension. This speeds up execution of a comprehension by up to two times. See PEP 709 for further details.

Comprehension iteration variables remain isolated and don't overwrite a variable of the same name in the outer scope, nor are they visible after the comprehension. Inlining does result in a few visible behavior changes:

- There is no longer a separate frame for the comprehension in tracebacks, and tracing/profiling no longer shows the comprehension as a function call.

- The `symtable` module will no longer produce child symbol tables for each comprehension; instead, the comprehension's locals will be included in the parent function's symbol table.

- Calling `locals()` inside a comprehension now includes variables from outside the comprehension, and no longer includes the synthetic `.0` variable for the comprehension "argument".

- A comprehension iterating directly over `locals()` (e.g. `[k for k in locals()]`) may see "RuntimeError: dictionary changed size during iteration" when run under tracing (e.g. code coverage measurement). This is the same behavior already seen in e.g. `for k in locals():`. To avoid the error, first create a list of keys to iterate over: `keys = list(locals()); [k for k in keys]`.

（由 Carl Meyer 和 Vladimir Matveev 於 PEP 709 中貢獻。）

### 改善錯誤訊息

- Modules from the standard library are now potentially suggested as part of the error messages displayed by the interpreter when a `NameError` is raised to the top level. (Contributed by Pablo Galindo in gh-98254.)

      >>> sys.version_info
      Traceback (most recent call last):
        File "<stdin>", line 1, in <module>
      NameError: name 'sys' is not defined. Did you forget to import 'sys'?

- Improve the error suggestion for `NameError` exceptions for instances. Now if a `NameError` is raised in a method and the instance has an attribute that's exactly equal to the name in the exception, the suggestion will include `self.<NAME>` instead of the closest match in the method scope. (Contributed by Pablo Galindo in gh-99139.)

      >>> class A:
      ...    def __init__(self):
      ...        self.blech = 1
      ...
      ...    def foo(self):
      ...        somethin = blech
      ...
      >>> A().foo()
      Traceback (most recent call last):
        File "<stdin>", line 1
          somethin = blech
                     ^^^^^
      NameError: name 'blech' is not defined. Did you mean: 'self.blech'?

- Improve the `SyntaxError` error message when the user types `import x from y` instead of `from y import x`. (Contributed by Pablo Galindo in gh-98931.)

      >>> import a.y.z from b.y.z
      Traceback (most recent call last):
        File "<stdin>", line 1
          import a.y.z from b.y.z
          ^^^^^^^^^^^^^^^^^^^^^^^
      SyntaxError: Did you mean to use 'from ... import ...' instead?

- `ImportError` exceptions raised from failed `from <module> import <name>` statements now include suggestions for the value of `<name>` based on the available names in `<module>`. (Contributed by Pablo Galindo in gh-91058.)

      >>> from collections import chainmap
      Traceback (most recent call last):
        File "<stdin>", line 1, in <module>
      ImportError: cannot import name 'chainmap' from 'collections'. Did you mean: 'ChainMap'?

## 型別提示相關的新特性

本節涵蓋了影響型別提示和 `typing` 模組的主要變更。

### PEP 692: Using `TypedDict` for more precise `**kwargs` typing

Typing `**kwargs` in a function signature as introduced by PEP 484 allowed for valid annotations only in cases where all of the `**kwargs` were of the same type.

PEP 692 specifies a more precise way of typing `**kwargs` by relying on typed dictionaries:

    from typing import TypedDict, Unpack

    class Movie(TypedDict):
      name: str
      year: int

    def foo(**kwargs: Unpack[Movie]): ...

詳情請見 PEP 692。

（由 Franek Magiera 於 gh-103629 中貢獻。）

### PEP 698：覆蓋靜態型別的裝飾器

A new decorator `typing.override()` has been added to the `typing` module. It indicates to type checkers that the method is intended to override a method in a superclass. This allows type checkers to catch mistakes where a method that is intended to override something in a base class does not in fact do so.

範例：

    from typing import override

    class Base:
      def get_color(self) -> str:
        return "blue"

    class GoodChild(Base):
      @override  # ok: overrides Base.get_color
      def get_color(self) -> str:
        return "yellow"

    class BadChild(Base):
      @override  # type checker error: does not override Base.get_color
      def get_colour(self) -> str:
        return "red"

詳情請見 PEP 698。

（由 Steven Troxler 於 gh-101561 中貢獻。）

## 其他語言更動

- The parser now raises `SyntaxError` when parsing source code containing null bytes. (Contributed by Pablo Galindo in gh-96670.)

- A backslash-character pair that is not a valid escape sequence now generates a `SyntaxWarning`, instead of `DeprecationWarning`. For example, `re.compile("\d+\.\d+")` now emits a `SyntaxWarning` (`"\d"` is an invalid escape sequence, use raw strings for regular expression: `re.compile(r"\d+\.\d+")`). In a future Python version, `SyntaxError` will eventually be raised, instead of `SyntaxWarning`. (Contributed by Victor Stinner in gh-98401.)

- Octal escapes with value larger than `0o377` (ex: `"\477"`), deprecated in Python 3.11, now produce a `SyntaxWarning`, instead of `DeprecationWarning`. In a future Python version they will be eventually a `SyntaxError`. (Contributed by Victor Stinner in gh-98401.)

- Variables used in the target part of comprehensions that are not stored to can now be used in assignment expressions (`:=`). For example, in `[(b := 1) for a, b.prop in some_iter]`, the assignment to `b` is now allowed. Note that assigning to variables stored to in the target part of comprehensions (like `a`) is still disallowed, as per PEP 572. (Contributed by Nikita Sobolev in gh-100581.)

- Exceptions raised in a class or type's `__set_name__` method are no longer wrapped by a `RuntimeError`. Context information is added to the exception as a PEP 678 note. (Contributed by Irit Katriel in gh-77757.)

- When a `try-except*` construct handles the entire `ExceptionGroup` and raises one other exception, that exception is no longer wrapped in an `ExceptionGroup`. Also changed in version 3.11.4. (Contributed by Irit Katriel in gh-103590.)

- The Garbage Collector now runs only on the eval breaker mechanism of the Python bytecode evaluation loop instead of object allocations. The GC can also run when `PyErr_CheckSignals()` is called so C extensions that need to run for a long time without executing any Python code also have a chance to execute the GC periodically. (Contributed by Pablo Galindo in gh-97922.)

- All builtin and extension callables expecting boolean parameters now accept arguments of any type instead of just `bool` and `int`. (Contributed by Serhiy Storchaka in gh-60203.)

- `memoryview` now supports the half-float type (the "e" format code). (Contributed by Donghee Na and Antoine Pitrou in gh-90751.)

- `slice` objects are now hashable, allowing them to be used as dict keys and set items. (Contributed by Will Bradshaw, Furkan Onder, and Raymond Hettinger in gh-101264.)

- `sum()` now uses Neumaier summation to improve accuracy and commutativity when summing floats or mixed ints and floats. (Contributed by Raymond Hettinger in gh-100425.)

- `ast.parse()` now raises `SyntaxError` instead of `ValueError` when parsing source code containing null bytes. (Contributed by Pablo Galindo in gh-96670.)

- The extraction methods in `tarfile`, and `shutil.unpack_archive()`, have a new a filter argument that allows limiting tar features than may be surprising or dangerous, such as creating files outside the destination directory. See tarfile extraction filters for details. In Python 3.14, the default will switch to `'data'`. (Contributed by Petr Viktorin in PEP 706.)

- `types.MappingProxyType` instances are now hashable if the underlying mapping is hashable. (Contributed by Serhiy Storchaka in gh-87995.)

- 透過新的環境變數 `PYTHONPERFSUPPORT` 和命令列選項 `-X perf` 以及新的 `sys.activate_stack_trampoline()`、`sys.deactivate_stack_trampoline()` 和 `sys.is_stack_trampoline_active()` 函式，新增對效能分析器的支援。（由 Pablo Galindo 設計。由 Pablo Galindo 和 Christian Heimes 貢獻，Gregory P. Smith [Google] 和 Mark Shannon 在 gh-96123 中也有貢獻。）

## 新增模組

- 無。

## 改進的模組

### array

- The `array.array` class now supports subscripting, making it a generic type. (Contributed by Jelle Zijlstra in gh-98658.)

### asyncio

- The performance of writing to sockets in `asyncio` has been significantly improved. `asyncio` now avoids unnecessary copying when writing to sockets and uses `sendmsg()` if the platform supports it. (Contributed by Kumar Aditya in gh-91166.)

- Add `asyncio.eager_task_factory()` and `asyncio.create_eager_task_factory()` functions to allow opting an event loop in to eager task execution, making some use-cases 2x to 5x faster. (Contributed by Jacob Bower & Itamar Oren in gh-102853, gh-104140, and gh-104138)

- On Linux, `asyncio` uses `asyncio.PidfdChildWatcher` by default if `os.pidfd_open()` is available and functional instead of `asyncio.ThreadedChildWatcher`. (Contributed by Kumar Aditya in gh-98024.)

- The event loop now uses the best available child watcher for each platform (`asyncio.PidfdChildWatcher` if supported and `asyncio.ThreadedChildWatcher` otherwise), so manually configuring a child watcher is not recommended. (Contributed by Kumar Aditya in gh-94597.)

- Add loop_factory parameter to `asyncio.run()` to allow specifying a custom event loop factory. (Contributed by Kumar Aditya in gh-99388.)

- Add C implementation of `asyncio.current_task()` for 4x-6x speedup. (Contributed by Itamar Oren and Pranav Thulasiram Bhat in gh-100344.)

- `asyncio.iscoroutine()` now returns `False` for generators as `asyncio` does not support legacy generator-based coroutines. (Contributed by Kumar Aditya in gh-102748.)

- `asyncio.wait()` and `asyncio.as_completed()` now accepts generators yielding tasks. (Contributed by Kumar Aditya in gh-78530.)

### calendar

- Add enums `calendar.Month` and `calendar.Day` defining months of the year and days of the week. (Contributed by Prince Roshan in gh-103636.)

### csv

- Add `csv.QUOTE_NOTNULL` and `csv.QUOTE_STRINGS` flags to provide finer grained control of `None` and empty strings by `reader` and `writer` objects.

### dis

- Pseudo instruction opcodes (which are used by the compiler but do not appear in executable bytecode) are now exposed in the `dis` module. `HAVE_ARGUMENT` is still relevant to real opcodes, but it is not useful for pseudo instructions. Use the new `dis.hasarg` collection instead. (Contributed by Irit Katriel in gh-94216.)

- Add the `dis.hasexc` collection to signify instructions that set an exception handler. (Contributed by Irit Katriel in gh-94216.)

### fractions

- Objects of type `fractions.Fraction` now support float-style formatting. (Contributed by Mark Dickinson in gh-100161.)

### importlib.resources

- `importlib.resources.as_file()` 現在支援資源目錄。（由 Jason R. Coombs 於 gh-97930 中貢獻。）

- 將 `importlib.resources.files()` 的第一個參數重新命名為 anchor。（由 Jason R. Coombs 於 gh-100598 中貢獻。）

### inspect

- 新增 `inspect.markcoroutinefunction()` 以標記會回傳 coroutine 的同步函式，以供 `inspect.iscoroutinefunction()` 使用。（由 Carlton Gibson 於 gh-99247 中貢獻。）

- 新增 `inspect.getasyncgenstate()` 和 `inspect.getasyncgenlocals()` 以確定非同步產生器的目前狀態。（由 Thomas Krennwallner 於 gh-79940 中貢獻。）

- `inspect.getattr_static()` 的效能已大幅改善。大多數對該函式的呼叫應該比 Python 3.11 中快至少 2 倍。（由 Alex Waygood 於 gh-103193 中貢獻。）

### itertools

- 新增 `itertools.batched()` 以將元素收集到大小均等的元組中，其中最後一批次可能比其他的少。（由 Raymond Hettinger 於 gh-98363 中貢獻。）

### math

- 新增 `math.sumprod()` 以計算乘積總和。（由 Raymond Hettinger 於 gh-100485 中貢獻。）

- Extend `math.nextafter()` to include a steps argument for moving up or down multiple steps at a time. (Contributed by Matthias Goergens, Mark Dickinson, and Raymond Hettinger in gh-94906.)

### os

- Add `os.PIDFD_NONBLOCK` to open a file descriptor for a process with `os.pidfd_open()` in non-blocking mode. (Contributed by Kumar Aditya in gh-93312.)

- `os.DirEntry` now includes an `os.DirEntry.is_junction()` method to check if the entry is a junction. (Contributed by Charles Machalow in gh-99547.)

- Add `os.listdrives()`, `os.listvolumes()` and `os.listmounts()` functions on Windows for enumerating drives, volumes and mount points. (Contributed by Steve Dower in gh-102519.)

- `os.stat()` and `os.lstat()` are now more accurate on Windows. The `st_birthtime` field will now be filled with the creation time of the file, and `st_ctime` is deprecated but still contains the creation time (but in the future will return the last metadata change, for consistency with other platforms). `st_dev` may be up to 64 bits and `st_ino` up to 128 bits depending on your file system, and `st_rdev` is always set to zero rather than incorrect values. Both functions may be significantly faster on newer releases of Windows. (Contributed by Steve Dower in gh-99726.)

### os.path

- 新增 `os.path.isjunction()` 以檢查給定路徑是否為連結點 (junction)。（由 Charles Machalow 於 gh-99547 中貢獻。）

- 新增 `os.path.splitroot()` 以將路徑分割為三元組 `(drive, root, tail)`。（由 Barney Gale 於 gh-101000 中貢獻。）

### pathlib

- Add support for subclassing `pathlib.PurePath` and `pathlib.Path`, plus their Posix- and Windows-specific variants. Subclasses may override the `pathlib.PurePath.with_segments()` method to pass information between path instances.

- Add `pathlib.Path.walk()` for walking the directory trees and generating all file or directory names within them, similar to `os.walk()`. (Contributed by Stanislav Zmiev in gh-90385.)

- Add walk_up optional parameter to `pathlib.PurePath.relative_to()` to allow the insertion of `..` entries in the result; this behavior is more consistent with `os.path.relpath()`. (Contributed by Domenico Ragusa in gh-84538.)

- Add `pathlib.Path.is_junction()` as a proxy to `os.path.isjunction()`. (Contributed by Charles Machalow in gh-99547.)

- Add case_sensitive optional parameter to `pathlib.Path.glob()`, `pathlib.Path.rglob()` and `pathlib.PurePath.match()` for matching the path's case sensitivity, allowing for more precise control over the matching process.

### platform

- Add support for detecting Windows 11 and Windows Server releases past 2012. Previously, lookups on Windows Server platforms newer than Windows Server 2012 and on Windows 11 would return `Windows-10`. (Contributed by Steve Dower in gh-89545.)

### pdb

- Add convenience variables to hold values temporarily for debug session and provide quick access to values like the current frame or the return value. (Contributed by Tian Gao in gh-103693.)

### random

- 新增 `random.binomialvariate()`。（由 Raymond Hettinger 於 gh-81620 中貢獻。）

- 將預設值 `lambd=1.0` 加入至 `random.expovariate()` 中。（由 Raymond Hettinger 在 gh-100234 中貢獻。）

### shutil

- `shutil.make_archive()` now passes the root_dir argument to custom archivers which support it. In this case it no longer temporarily changes the current working directory of the process to root_dir to perform archiving. (Contributed by Serhiy Storchaka in gh-74696.)

- `shutil.rmtree()` now accepts a new argument onexc which is an error handler like onerror but which expects an exception instance rather than a (typ, val, tb) triplet. onerror is deprecated. (Contributed by Irit Katriel in gh-102828.)

- `shutil.which()` now consults the PATHEXT environment variable to find matches within PATH on Windows even when the given cmd includes a directory component. (Contributed by Charles Machalow in gh-103179.)

  `shutil.which()` will call `NeedCurrentDirectoryForExePathW` when querying for executables on Windows to determine if the current working directory should be prepended to the search path. (Contributed by Charles Machalow in gh-103179.)

  `shutil.which()` will return a path matching the cmd with a component from `PATHEXT` prior to a direct match elsewhere in the search path on Windows. (Contributed by Charles Machalow in gh-103179.)

### sqlite3

- 新增命令列介面。（由 Erlend E. Aasland 於 gh-77617 中貢獻。）

- Add the `sqlite3.Connection.autocommit` attribute to `sqlite3.Connection` and the autocommit parameter to `sqlite3.connect()` to control PEP 249-compliant transaction handling. (Contributed by Erlend E. Aasland in gh-83638.)

- Add entrypoint keyword-only parameter to `sqlite3.Connection.load_extension()`, for overriding the SQLite extension entry point. (Contributed by Erlend E. Aasland in gh-103015.)

- Add `sqlite3.Connection.getconfig()` and `sqlite3.Connection.setconfig()` to `sqlite3.Connection` to make configuration changes to a database connection. (Contributed by Erlend E. Aasland in gh-103489.)

### statistics

- Extend `statistics.correlation()` to include as a `ranked` method for computing the Spearman correlation of ranked data. (Contributed by Raymond Hettinger in gh-95861.)

### sys

- Add the `sys.monitoring` namespace to expose the new PEP 669 monitoring API. (Contributed by Mark Shannon in gh-103082.)

- Add `sys.activate_stack_trampoline()` and `sys.deactivate_stack_trampoline()` for activating and deactivating stack profiler trampolines, and `sys.is_stack_trampoline_active()` for querying if stack profiler trampolines are active. (Contributed by Pablo Galindo and Christian Heimes with contributions from Gregory P. Smith [Google] and Mark Shannon in gh-96123.)

- Add `sys.last_exc` which holds the last unhandled exception that was raised (for post-mortem debugging use cases). Deprecate the three fields that have the same information in its legacy form: `sys.last_type`, `sys.last_value` and `sys.last_traceback`. (Contributed by Irit Katriel in gh-102778.)

- `sys._current_exceptions()` now returns a mapping from thread-id to an exception instance, rather than to a `(typ, exc, tb)` tuple. (Contributed by Irit Katriel in gh-103176.)

- `sys.setrecursionlimit()` and `sys.getrecursionlimit()`. The recursion limit now applies only to Python code. Builtin functions do not use the recursion limit, but are protected by a different mechanism that prevents recursion from causing a virtual machine crash.

### tempfile

- `tempfile.NamedTemporaryFile` 函式新增了一個選擇性參數 delete_on_close （由 Evgeny Zorin 於 gh-58451 中貢獻。）

- `tempfile.mkdtemp()` 現在總是會傳回絕對路徑，即使提供給 dir 參數的引數是相對路徑。

### threading

- Add `threading.settrace_all_threads()` and `threading.setprofile_all_threads()` that allow to set tracing and profiling functions in all running threads in addition to the calling one. (Contributed by Pablo Galindo in gh-93503.)

### tkinter

- `tkinter.Canvas.coords()` now flattens its arguments. It now accepts not only coordinates as separate arguments (`x1, y1, x2, y2, ...`) and a sequence of coordinates (`[x1, y1, x2, y2, ...]`), but also coordinates grouped in pairs (`(x1, y1), (x2, y2), ...` and `[(x1, y1), (x2, y2), ...]`), like `create_*()` methods. (Contributed by Serhiy Storchaka in gh-94473.)

### tokenize

- The `tokenize` module includes the changes introduced in PEP 701. (Contributed by Marta Gómez Macías and Pablo Galindo in gh-102856.) See 移植至 Python 3.12 for more information on the changes to the `tokenize` module.

### types

- Add `types.get_original_bases()` to allow for further introspection of 使用者定義泛型型別 when subclassed. (Contributed by James Hilton-Balfe and Alex Waygood in gh-101827.)

### typing

- `isinstance()` checks against `runtime-checkable protocols` now use `inspect.getattr_static()` rather than `hasattr()` to lookup whether attributes exist. This means that descriptors and `__getattr__()` methods are no longer unexpectedly evaluated during `isinstance()` checks against runtime-checkable protocols. However, it may also mean that some objects which used to be considered instances of a runtime-checkable protocol may no longer be considered instances of that protocol on Python 3.12+, and vice versa. Most users are unlikely to be affected by this change. (Contributed by Alex Waygood in gh-102433.)

- The members of a runtime-checkable protocol are now considered "frozen" at runtime as soon as the class has been created. Monkey-patching attributes onto a runtime-checkable protocol will still work, but will have no impact on `isinstance()` checks comparing objects to the protocol. For example:

      >>> from typing import Protocol, runtime_checkable
      >>> @runtime_checkable
      ... class HasX(Protocol):
      ...     x = 1
      ...
      >>> class Foo: ...
      ...
      >>> f = Foo()
      >>> isinstance(f, HasX)
      False
      >>> f.x = 1
      >>> isinstance(f, HasX)
      True
      >>> HasX.y = 2
      >>> isinstance(f, HasX)  # 沒有改變，即便 HasX 現在有 "y" 屬性
      True

  This change was made in order to speed up `isinstance()` checks against runtime-checkable protocols.

- The performance profile of `isinstance()` checks against `runtime-checkable protocols` has changed significantly. Most `isinstance()` checks against protocols with only a few members should be at least 2x faster than in 3.11, and some may be 20x faster or more. However, `isinstance()` checks against protocols with many members may be slower than in Python 3.11. (Contributed by Alex Waygood in gh-74690 and gh-103193.)

- All `typing.TypedDict` and `typing.NamedTuple` classes now have the `__orig_bases__` attribute. (Contributed by Adrian Garcia Badaracco in gh-103699.)

- 新增 `frozen_default` 參數至 `typing.dataclass_transform()`。（由 Erik De Bonte 於 gh-99957 中貢獻。）

### unicodedata

- The Unicode database has been updated to version 15.0.0. (Contributed by Benjamin Peterson in gh-96734).

### unittest

新增 `--durations` 命令列選項，顯示 N 個最慢的測試案例：

    python3 -m unittest --durations=3 lib.tests.test_threading
    .....
    Slowest test durations
    ----------------------------------------------------------------------
    1.210s     test_timeout (Lib.test.test_threading.BarrierTests)
    1.003s     test_default_timeout (Lib.test.test_threading.BarrierTests)
    0.518s     test_timeout (Lib.test.test_threading.EventTests)

    (0.000 durations hidden.  Use -v to show these durations.)
    ----------------------------------------------------------------------
    Ran 158 tests in 9.869s

    OK (skipped=3)

（由 Giampaolo Rodola 於 gh-48330 中貢獻。）

### uuid

- 新增一個命令列介面。（由 Adam Chhina 於 gh-88597 中貢獻。）

## 最佳化

- Remove `wstr` and `wstr_length` members from Unicode objects. It reduces object size by 8 or 16 bytes on 64bit platform. (PEP 623) (Contributed by Inada Naoki in gh-92536.)

- Add experimental support for using the BOLT binary optimizer in the build process, which improves performance by 1-5%. (Contributed by Kevin Modzelewski in gh-90536 and tuned by Donghee Na in gh-101525)

- Speed up the regular expression substitution (functions `re.sub()` and `re.subn()` and corresponding `re.Pattern` methods) for replacement strings containing group references by 2--3 times. (Contributed by Serhiy Storchaka in gh-91524.)

- 透過延遲運算較繁重的字串格式化來加速 `asyncio.Task` 的建立。（由 Itamar Oren 於 gh-103793 中貢獻。）

- The `tokenize.tokenize()` and `tokenize.generate_tokens()` functions are up to 64% faster as a side effect of the changes required to cover PEP 701 in the `tokenize` module. (Contributed by Marta Gómez Macías and Pablo Galindo in gh-102856.)

- Speed up `super()` method calls and attribute loads via the new `LOAD_SUPER_ATTR` instruction. (Contributed by Carl Meyer and Vladimir Matveev in gh-103497.)

## CPython 位元組碼變更

- 移除 `LOAD_METHOD` 指令。它已經合併至 `LOAD_ATTR`。`LOAD_ATTR` 現在會像舊的 `LOAD_METHOD` 指令一樣行為，如果其 oparg 的低位元 (low bit) 有被設定。（由 Ken Jin 於 gh-93429 中貢獻。）

- 移除 `JUMP_IF_FALSE_OR_POP` 和 `JUMP_IF_TRUE_OR_POP` 指令。（由 Irit Katriel 於 gh-102859 中貢獻。）

- 移除 `PRECALL` 指令。（由 Mark Shannon 於 gh-92925 中貢獻。）

- 新增 `BINARY_SLICE` 和 `STORE_SLICE` 指令。（由 Mark Shannon 於 gh-94163 中貢獻。）

- 新增 `CALL_INTRINSIC_1` 指令。（由 Mark Shannon 於 gh-99005 中貢獻。）

- 新增 `CALL_INTRINSIC_2` 指令。（由 Irit Katriel 於 gh-101799 中貢獻。）

- 新增 `CLEANUP_THROW` 指令。（由 Brandt Bucher 於 gh-90997 中貢獻。）

- 新增 `END_SEND` 指令。（由 Mark Shannon 於 gh-103082 中貢獻。）

- 新增 `LOAD_FAST_AND_CLEAR` 指令作為 PEP 709 實作的一部分。（由 Carl Meyer 於 gh-101441 中貢獻。）

- 新增 `LOAD_FAST_CHECK` 指令。（由 Dennis Sweeney 於 gh-93143 中貢獻。）

- 新增 `LOAD_FROM_DICT_OR_DEREF`、`LOAD_FROM_DICT_OR_GLOBALS` 和 `LOAD_LOCALS` 操作碼作為 PEP 695 實作的一部分。移除 `LOAD_CLASSDEREF` 操作碼，可以用 `LOAD_LOCALS` 加上 `LOAD_FROM_DICT_OR_DEREF` 來取代。（由 Jelle Zijlstra 於 gh-103764 中貢獻。）

- 新增 `LOAD_SUPER_ATTR` 指令。（由 Carl Meyer 和 Vladimir Matveev 於 gh-103497 中貢獻。）

- 新增 `RETURN_CONST` 指令。（由 Wenyang Wang 於 gh-101632 中貢獻。）

## Demos and Tools

- Remove the `Tools/demo/` directory which contained old demo scripts. A copy can be found in the old-demos project. (Contributed by Victor Stinner in gh-97681.)

- Remove outdated example scripts of the `Tools/scripts/` directory. A copy can be found in the old-demos project. (Contributed by Victor Stinner in gh-97669.)

## 已棄用

- `argparse`：`argparse.BooleanOptionalAction` 的 type、choices 和 metavar 參數已被棄用，將在 3.14 中移除。 (由 Nikita Sobolev 於 gh-92248 貢獻。)

- `ast`：以下 `ast` 功能自 Python 3.8 起已在文件中被棄用，現在在存取或使用時會在 runtime 發出 `DeprecationWarning`，並將在 Python 3.14 中移除：

  - `ast.Num`

  - `ast.Str`

  - `ast.Bytes`

  - `ast.NameConstant`

  - `ast.Ellipsis`

  請改用 `ast.Constant`。（由 Serhiy Storchaka 於 gh-90953 貢獻。）

- `asyncio`：

  - 已棄用並將在 Python 3.14 中移除的 child watcher 類別：`asyncio.MultiLoopChildWatcher`、`asyncio.FastChildWatcher`、`asyncio.AbstractChildWatcher` 和 `asyncio.SafeChildWatcher`。 (由 Kumar Aditya 於 gh-94597 貢獻。)

  - `asyncio.set_child_watcher()`、`asyncio.get_child_watcher()`、`asyncio.AbstractEventLoopPolicy.set_child_watcher()` 和 `asyncio.AbstractEventLoopPolicy.get_child_watcher()` 已被棄用並將在 Python 3.14 中移除。（由 Kumar Aditya 於 gh-94597 貢獻。）

  - 預設事件迴圈策略的 `get_event_loop()` 方法現在會在沒有設定目前事件迴圈且決定建立一個時發出 `DeprecationWarning`。 (由 Serhiy Storchaka 和 Guido van Rossum 於 gh-100160 貢獻。)

- `calendar`：`calendar.January` 和 `calendar.February` 常數已被棄用並被 `calendar.JANUARY` 和 `calendar.FEBRUARY` 取代。 (由 Prince Roshan 於 gh-103636 貢獻。)

- `collections.abc`：棄用 `collections.abc.ByteString`。

  使用 `isinstance(obj, collections.abc.Buffer)` 來測試 `obj` 是否在 runtime 實作了緩衝區協定。在型別註解的使用中，請用 `Buffer` 或明確指定你的程式碼所支援型別的聯集（例如 `bytes | bytearray | memoryview`）。

  `ByteString` 最初被設計為一個抽象類別，以作為 `bytes` 和 `bytearray` 的超型別 (supertype)。然而由於 ABC 從未擁有任何方法，知道一個物件是 `ByteString` 的實例從未真正告訴你任何關於該物件的有用資訊。其他常見的緩衝區型別如 `memoryview` 也從未被理解為 `ByteString` 的子型別（無論是在 runtime 還是由靜態型別檢查器）。

  更多細節請見 PEP 688。（由 Shantanu Jain 於 gh-91896 貢獻。）

- `datetime`: `datetime.datetime`'s `utcnow()` and `utcfromtimestamp()` are deprecated and will be removed in a future version. Instead, use timezone-aware objects to represent datetimes in UTC: respectively, call `now()` and `fromtimestamp()` with the tz parameter set to `datetime.UTC`. (Contributed by Paul Ganssle in gh-103857.)

- `email`：棄用 `email.utils.localtime()` 中的 isdst 參數。（由 Alan Williams 於 gh-72346 中貢獻。）

- `importlib.abc`：棄用下列類別，預定於 Python 3.14 中移除：

  - `importlib.abc.ResourceReader`

  - `importlib.abc.Traversable`

  - `importlib.abc.TraversableResources`

  請改用 `importlib.resources.abc` 類別：

  - `importlib.resources.abc.Traversable`

  - `importlib.resources.abc.TraversableResources`

  （由 Jason R. Coombs 和 Hugo van Kemenade 貢獻於 gh-93963。）

- `itertools`: Deprecate the support for copy, deepcopy, and pickle operations, which is undocumented, inefficient, historically buggy, and inconsistent. This will be removed in 3.14 for a significant reduction in code volume and maintenance burden. (Contributed by Raymond Hettinger in gh-101588.)

- `multiprocessing`: In Python 3.14, the default `multiprocessing` start method will change to a safer one on Linux, BSDs, and other non-macOS POSIX platforms where `'fork'` is currently the default (gh-84559). Adding a runtime warning about this was deemed too disruptive as the majority of code is not expected to care. Use the `get_context()` or `set_start_method()` APIs to explicitly specify when your code requires `'fork'`. See contexts and start methods.

- `pkgutil`：`pkgutil.find_loader()` 和 `pkgutil.get_loader()` 已被棄用並將在 Python 3.14 中移除；請改用 `importlib.util.find_spec()`。（由 Nikita Sobolev 於 gh-97850 中貢獻。）

- `pty`: The module has two undocumented `master_open()` and `slave_open()` functions that have been deprecated since Python 2 but only gained a proper `DeprecationWarning` in 3.12. Remove them in 3.14. (Contributed by Soumendra Ganguly and Gregory P. Smith in gh-85984.)

- `os`：

  - The `st_ctime` fields return by `os.stat()` and `os.lstat()` on Windows are deprecated. In a future release, they will contain the last metadata change time, consistent with other platforms. For now, they still contain the creation time, which is also available in the new `st_birthtime` field. (Contributed by Steve Dower in gh-99726.)

  - On POSIX platforms, `os.fork()` can now raise a `DeprecationWarning` when it can detect being called from a multithreaded process. There has always been a fundamental incompatibility with the POSIX platform when doing so. Even if such code appeared to work. We added the warning to raise awareness as issues encountered by code doing this are becoming more frequent. See the `os.fork()` documentation for more details along with this discussion on fork being incompatible with threads for why we're now surfacing this longstanding platform compatibility problem to developers.

  When this warning appears due to usage of `multiprocessing` or `concurrent.futures` the fix is to use a different `multiprocessing` start method such as `"spawn"` or `"forkserver"`.

- `shutil`：`shutil.rmtree()` 的 onerror 引數已被棄用，請改用 onexc。（由 Irit Katriel 於 gh-102828 中貢獻。）

- `sqlite3`：

  - default adapters and converters are now deprecated. Instead, use the Adapter and converter recipes and tailor them to your needs. (Contributed by Erlend E. Aasland in gh-90016.)

  - In `execute()`, `DeprecationWarning` is now emitted when named placeholders are used together with parameters supplied as a sequence instead of as a `dict`. Starting from Python 3.14, using named placeholders with parameters supplied as a sequence will raise a `ProgrammingError`. (Contributed by Erlend E. Aasland in gh-101698.)

- `sys`：`sys.last_type`、`sys.last_value` 和 `sys.last_traceback` 欄位已被棄用。請改用 `sys.last_exc`。（由 Irit Katriel 於 gh-102778 中貢獻。）

- `tarfile`: Extracting tar archives without specifying filter is deprecated until Python 3.14, when `'data'` filter will become the default. See Extraction filters for details.

- `typing`：

  - `typing.Hashable` and `typing.Sized`, aliases for `collections.abc.Hashable` and `collections.abc.Sized` respectively, are deprecated. (gh-94309.)

  - 自 Python 3.9 起已被棄用的 `typing.ByteString` 現在在使用時會發出 `DeprecationWarning`。（由 Alex Waygood 於 gh-91896 中貢獻。）

- `xml.etree.ElementTree`: The module now emits `DeprecationWarning` when testing the truth value of an `xml.etree.ElementTree.Element`. Before, the Python implementation emitted `FutureWarning`, and the C implementation emitted nothing. (Contributed by Jacob Walls in gh-83122.)

- The 3-arg signatures (type, value, traceback) of `coroutine throw()`, `generator throw()` and `async generator throw()` are deprecated and may be removed in a future version of Python. Use the single-arg versions of these functions instead. (Contributed by Ofey Chan in gh-89874.)

- `DeprecationWarning` is now raised when `__package__` on a module differs from `__spec__.parent` (previously it was `ImportWarning`). (Contributed by Brett Cannon in gh-65961.)

- Setting `__package__` or `__cached__` on a module is deprecated, and will cease to be set or taken into consideration by the import system in Python 3.14. (Contributed by Brett Cannon in gh-65961.)

- The bitwise inversion operator (`~`) on bool is deprecated. It will throw an error in Python 3.16. Use `not` for logical negation of bools instead. In the rare case that you really need the bitwise inversion of the underlying `int`, convert to int explicitly: `~int(x)`. (Contributed by Tim Hoffmann in gh-103487.)

- 自 3.10 起，於程式碼物件存取 `co_lnotab` 的功能已在 PEP 626 中被棄用，但只在 3.12 中於適時發出 `DeprecationWarning`。可能在 3.15 中移除。（由 Nikita Sobolev 於 gh-101866 貢獻。）

### Python 3.13 中待移除的項目

模組（請見 PEP 594）：

- `aifc`

- `audioop`

- `cgi`

- `cgitb`

- `chunk`

- `crypt`

- `imghdr`

- `mailcap`

- `msilib`

- `nis`

- `nntplib`

- `ossaudiodev`

- `pipes`

- `sndhdr`

- `spwd`

- `sunau`

- `telnetlib`

- `uu`

- `xdrlib`

其他模組：

- `lib2to3` 和 2to3 程式 (gh-84540)

API：

- `configparser.LegacyInterpolation` (gh-90765)

- `locale.resetlocale()` (gh-90817)

- `turtle.RawTurtle.settiltangle()` (gh-50096)

- `unittest.findTestCases()` (gh-50096)

- `unittest.getTestCaseNames()` (gh-50096)

- `unittest.makeSuite()` (gh-50096)

- `unittest.TestProgram.usageExit()` (gh-67048)

- `webbrowser.MacOSX` (gh-86421)

- `classmethod` 描述器鏈接 (gh-89519)

- `importlib.resources` 的已棄用方法：

  - `contents()`

  - `is_resource()`

  - `open_binary()`

  - `open_text()`

  - `path()`

  - `read_binary()`

  - `read_text()`

  請改用 `importlib.resources.files()`。請參閱 importlib-resources: Migrating from Legacy (gh-106531)

### Python 3.14 中待移除的項目

- `argparse`：`argparse.BooleanOptionalAction` 的 type、choices 和 metavar 參數已被棄用，將在 3.14 中移除。 (由 Nikita Sobolev 於 gh-92248 貢獻。)

- `ast`：自 Python 3.8 起，下列功能已在文件中被棄用，現在在存取或使用時會於 runtime 發出 `DeprecationWarning`，並將在 Python 3.14 中移除：

  - `ast.Num`

  - `ast.Str`

  - `ast.Bytes`

  - `ast.NameConstant`

  - `ast.Ellipsis`

  請改用 `ast.Constant`。（由 Serhiy Storchaka 於 gh-90953 貢獻。）

- `asyncio`：

  - 已棄用並將在 Python 3.14 中移除的 child watcher 類別：`asyncio.MultiLoopChildWatcher`、`asyncio.FastChildWatcher`、`asyncio.AbstractChildWatcher` 和 `asyncio.SafeChildWatcher`。 (由 Kumar Aditya 於 gh-94597 貢獻。)

  - `asyncio.set_child_watcher()`、`asyncio.get_child_watcher()`、`asyncio.AbstractEventLoopPolicy.set_child_watcher()` 和 `asyncio.AbstractEventLoopPolicy.get_child_watcher()` 已被棄用並將在 Python 3.14 中移除。（由 Kumar Aditya 於 gh-94597 貢獻。）

  - 預設事件迴圈策略的 `get_event_loop()` 方法現在會在沒有設定目前事件迴圈且決定建立一個時發出 `DeprecationWarning`。 (由 Serhiy Storchaka 和 Guido van Rossum 於 gh-100160 貢獻。)

- `email`：已棄用 `email.utils.localtime()` 中的 isdst 參數。（由 Alan Williams 於 gh-72346 貢獻。）

- `importlib.abc` 的已棄用類別：

  - `importlib.abc.ResourceReader`

  - `importlib.abc.Traversable`

  - `importlib.abc.TraversableResources`

  請改用 `importlib.resources.abc` 類別：

  - `importlib.resources.abc.Traversable`

  - `importlib.resources.abc.TraversableResources`

  （由 Jason R. Coombs 和 Hugo van Kemenade 貢獻於 gh-93963。）

- `itertools` 有不以文件記錄、效率低下、過去常有 bug 且不一致的 copy、deepcopy 和 pickle 操作支援。將在 3.14 中移除以大幅減少程式碼量和維護負擔。 (由 Raymond Hettinger 於 gh-101588 貢獻。)

- `multiprocessing`：預設的啟動方法將在 Linux、BSD 和其他非 macOS POSIX 平台上更改為更安全的 方法，目前 `'fork'` 是預設值 (gh-84559)。對此增加一個 runtime 警告被認為太過擾人，因為 大多數程式碼不會在意。請使用 `get_context()` 或 `set_start_method()` API 來明確指定你的程式碼何時需要 `'fork'`。請參閱 Contexts and start methods。

- `pathlib`：已棄用 `is_relative_to()` 和 `relative_to()`：額外引數的傳遞已被棄用。

- `pkgutil`：`pkgutil.find_loader()` 和 `pkgutil.get_loader()` 現在會引發 `DeprecationWarning`；請改用 `importlib.util.find_spec()`。 (由 Nikita Sobolev 於 gh-97850 貢獻。)

- `pty`：

  - `master_open()`：請用 `pty.openpty()`。

  - `slave_open()`：請用 `pty.openpty()`。

- `sqlite3`：

  - `version` 和 `version_info`。

  - `execute()` 和 `executemany()`，如果使用 named placeholders 且 parameters 是序列而不是 `dict`。

- `urllib`：`urllib.parse.Quoter` 已被棄用：它並非預期的公開 API。(由 Gregory P. Smith 於 gh-88168 貢獻。)

### Python 3.15 中待移除的項目

- 引入系統 (import system)：

  - 在模組上設定 `__cached__` 而沒有設定 `__spec__.cached` 的做法已被棄用。在 Python 3.15 中，引入系統或標準函式庫將不再設定或考慮 `__cached__`。(gh-97879)

  - 在模組上設定 `__package__` 而沒有設定 `__spec__.parent` 的做法已被棄用。在 Python 3.15 中，引入系統或標準函式庫將不再設定或考慮 `__package__`。(gh-97879)

- `ctypes`：

  - 自 Python 3.13 起，未記錄的 `ctypes.SetPointerType()` 函式已被棄用。

- `http.server`：

  - 過時且很少使用的 `CGIHTTPRequestHandler` 自 Python 3.13 起已被棄用。不存在直接的替代。任何東西都比 CGI 更好地將 Web 伺服器與請求處理程序介接起來。

  - 自 Python 3.13 起，python -m http.server 命令列介面的 `--cgi` 旗標已被棄用。

- `importlib`：

  - `load_module()` method：請改用 `exec_module()`。

- `locale`：

  - `getdefaultlocale()` 已在 Python 3.11 中被棄用，原本計劃在 Python 3.13 中移除 (gh-90817)，但被延後至 Python 3.15。請改用 `getlocale()`、`setlocale()` 和 `getencoding()`。 (由 Hugo van Kemenade 於 gh-111187 貢獻。)

- `pathlib`：

  - `PurePath.is_reserved()` 已自 Python 3.13 被棄用。請用 `os.path.isreserved()` 來偵測 Windows 上的保留路徑。

- `platform`：

  - 自 Python 3.13 起，`java_ver()` 已被棄用。此函式僅對 Jython 支援有用，具有令人困惑的 API，基本上未經測試。

- `sysconfig`：

  - `sysconfig.is_python_build()` 的 check_home 引數自 Python 3.12 起已被棄用。

- `threading`：

  - `RLock()` 在 Python 3.15 中將不接受任何引數。自 Python 3.14 起，傳遞任何引數的用法已被棄用，因為 Python 版本不允許任何引數，但 C 版本允許任意數量的位置或關鍵字引數，並忽略每個引數。

- `types`：

  - `types.CodeType`：自 3.10 起，存取 `co_lnotab` 已在 PEP 626 中被棄用，並計劃在 3.12 中移除，但只在 3.12 中於適當時發出 `DeprecationWarning`。可能在 3.15 中移除。（由 Nikita Sobolev 於 gh-101866 貢獻。）

- `typing`：

  - 用於建立 `NamedTuple` 類別的未以文件記錄之關鍵字引數語法 (`Point = NamedTuple("Point", x=int, y=int)`) 已自 Python 3.13 棄用。請改用基於類別的語法或函式語法 (functional syntax)。

  - 當使用 `TypedDict` 的函式語法時，未傳遞值給 fields 參數 (`TD = TypedDict("TD")`) 或傳遞 `None` (`TD = TypedDict("TD", None)`) 的做法自 Python 3.13 起已被棄用。請使用 `class TD(TypedDict): pass` 或 `TD = TypedDict("TD", {})` 來建立具有零個欄位的 TypedDict。

  - 自 Python 3.13 起，`typing.no_type_check_decorator()` 裝飾器函式已被棄用。在 `typing` 模組中使用了八年之後，它尚未得到任何主要型別檢查器的支援。

- `wave`：

  - 已棄用 `Wave_read` 和 `Wave_write` 類別的 `getmark()`、`setmark()` 和 `getmarkers()` 方法自 Python 3.13 被棄用。

- `zipimport`：

  - `load_module()` 自 Python 3.10 被棄用。請改用 `exec_module()`。（由 Jiahao Li 於 gh-125746 貢獻。）

### Python 3.16 中待移除的項目

- 引入系統 (import system)：

  - 在模組上設定 `__loader__` 而沒有設定 `__spec__.loader` 的做法將於 Python 3.16 被棄用。在 Python 3.16 中，引入系統或標準函式庫將不再設定或考慮 `__loader__`。

- `array`：

  - 自 Python 3.3 起，`'u'` 格式碼 (`wchar_t`) 在文件中已被棄用，自 Python 3.13 起在 runtime 已被棄用。請使用 `'w'` 格式碼 (`Py_UCS4`) 來取代 Unicode 字元。

- `asyncio`：

  - `asyncio.iscoroutinefunction()` 已被棄用並將在 Python 3.16 中移除；請改用 `inspect.iscoroutinefunction()`。（由 Jiahao Li 和 Kumar Aditya 於 gh-122875 貢獻。）

  - `asyncio` 策略系統已被棄用並將在 Python 3.16 中移除。特別是以下類別和函式已被棄用：

    - `asyncio.AbstractEventLoopPolicy`

    - `asyncio.DefaultEventLoopPolicy`

    - `asyncio.WindowsSelectorEventLoopPolicy`

    - `asyncio.WindowsProactorEventLoopPolicy`

    - `asyncio.get_event_loop_policy()`

    - `asyncio.set_event_loop_policy()`

    使用者應該使用 `asyncio.run()` 或 `asyncio.Runner` 搭配 loop_factory 來使用所需的事件迴圈實作。

    例如在 Windows 上使用 `asyncio.SelectorEventLoop`：

        import asyncio

        async def main():
            ...

        asyncio.run(main(), loop_factory=asyncio.SelectorEventLoop)

    （由 Kumar Aditya 於 gh-127949 貢獻。）

- `builtins`：

  - 自 Python 3.12 起，布林型別的位元反轉 `~True` 或 `~False` 已被棄用，因為它會產生不預期且不直觀的結果（`-2` 和 `-1`）。使用 `not x` 代替布林值的邏輯否定。在極少數情況下，你需要對底層的整數進行位元反轉，請明確轉換為 `~int(x)` (`~int(x)`)。

- `functools`：

  - 自 Python 3.14 起，使用 function 或 sequence 關鍵字引數呼叫 `functools.reduce()` 的 Python 實作已被棄用。

- `logging`：

  對具有 strm 引數的自訂日誌記錄處理函式的支援已被棄用，並計劃在 Python 3.16 中移除。請改用 stream 引數。（由 Mariusz Felisiak 於 gh-115032 貢獻。）

- `mimetypes`：

  - 有效的副檔名以 '.' 開頭或對 `mimetypes.MimeTypes.add_type()` 為空字串。未加點的副檔名已被棄用，並將在 Python 3.16 中引發 `ValueError`。（由 Hugo van Kemenade 於 gh-75223 貢獻。）

- `shutil`：

  - 自 Python 3.14 起，`ExecError` 例外已被棄用。自 Python 3.4 以來，它尚未被 `shutil` 中的任何函式使用，現在是 `RuntimeError` 的別名。

- `symtable`：

  - 自 Python 3.14 起，`Class.get_methods` 方法已被棄用。

- `sys`：

  - 自 Python 3.13 起，`_enablelegacywindowsfsencoding()` 函式已被棄用。請改用 `PYTHONLEGACYWINDOWSFSENCODING` 環境變數。

- `sysconfig`：

  - 自 Python 3.14 起，`sysconfig.expand_makefile_vars()` 函式已被棄用。請改用 `sysconfig.get_paths()` 的 `vars` 引數。

- `tarfile`：

  - 自 Python 3.13 起，未以文件記錄和未被使用的 `TarFile.tarfile` 屬性已被棄用。

### Python 3.17 中待移除的項目

- `collections.abc`：

  - `collections.abc.ByteString` 預計在 Python 3.17 中移除。

    使用 `isinstance(obj, collections.abc.Buffer)` 來測試 `obj` 是否在 runtime 實作了緩衝區協定。在型別註解的使用中，請用 `Buffer` 或明確指定你的程式碼所支援型別的聯集（例如 `bytes | bytearray | memoryview`）。

    `ByteString` 最初被設計為一個抽象類別，以作為 `bytes` 和 `bytearray` 的超型別 (supertype)。然而由於 ABC 從未擁有任何方法，知道一個物件是 `ByteString` 的實例從未真正告訴你任何關於該物件的有用資訊。其他常見的緩衝區型別如 `memoryview` 也從未被理解為 `ByteString` 的子型別（無論是在 runtime 還是由靜態型別檢查器）。

    更多細節請見 PEP 688。（由 Shantanu Jain 於 gh-91896 貢獻。）

- `typing`：

  - 在 Python 3.14 之前，舊式聯集是使用私有類別 `typing._UnionGenericAlias` 實作的。這個類別不再被需要，但為了向後相容性而保留，並計劃將在 Python 3.17 中移除。使用者應該改用文件中記錄的內省輔助函式，例如 `typing.get_origin()` 和 `typing.get_args()`，或者依賴私有實作細節。

  - `typing.ByteString` 自 Python 3.9 起已被棄用，預計在 Python 3.17 中移除。

    使用 `isinstance(obj, collections.abc.Buffer)` 來測試 `obj` 是否在 runtime 實作了緩衝區協定。在型別註解的使用中，請用 `Buffer` 或明確指定你的程式碼所支援型別的聯集（例如 `bytes | bytearray | memoryview`）。

    `ByteString` 最初被設計為一個抽象類別，以作為 `bytes` 和 `bytearray` 的超型別 (supertype)。然而由於 ABC 從未擁有任何方法，知道一個物件是 `ByteString` 的實例從未真正告訴你任何關於該物件的有用資訊。其他常見的緩衝區型別如 `memoryview` 也從未被理解為 `ByteString` 的子型別（無論是在 runtime 還是由靜態型別檢查器）。

    更多細節請見 PEP 688。（由 Shantanu Jain 於 gh-91896 貢獻。）

### 未來版本中的待移除項目

以下 API 將在未來被移除，雖然目前尚未安排移除日期。

- `argparse`：

  - 巢狀引數群組和巢狀互斥群組已被棄用。

  - 將未以文件記錄的關鍵字引數 prefix_chars 傳遞給 `add_argument_group()` 的做法現在已被棄用。

  - `argparse.FileType` 型別轉換器已被棄用。

- `builtins`：

  - 產生器：`throw(type, exc, tb)` 和 `athrow(type, exc, tb)` 簽名已被棄用：請改用 `throw(exc)` 和 `athrow(exc)`，為單引數簽名。

  - 目前 Python 接受數值字面值後面立即接關鍵字，例如 `0in x`、`1or x`、`0if 1else 2`。它讓運算式模糊且容易混淆，如 `[0x1for x in y]`（可以解釋為 `[0x1 for x in y]` 或 `[0x1f or x in y]`）。如果數值字面值後立即接 `and`、`else`、`for`、`if`、`in`、`is` 和 `or` 之一的關鍵字，則會引發語法警告。在未來版本中，它將被更改為語法錯誤。(gh-87999)

  - `__index__()` 和 `__int__()` 方法回傳非 int 型別的支援：這些方法將需要回傳 `int` 的嚴格子類別實例。

  - 回傳 `float` 嚴格子類別 `__float__()` 方法的支援：這些方法將需要回傳 `float` 的實例。

  - 回傳 `complex` 嚴格子類別 `__complex__()` 方法的支援：這些方法將需要回傳 `complex` 的實例。

  - 將 `int()` 委派給 `__trunc__()` 方法。

  - 在 `complex()` 建構子中將複數作為 real 或 imag 引數傳遞現在已被棄用；它應該只作為單個位置引數傳遞。 (由 Serhiy Storchaka 於 gh-109218 貢獻。)

- `calendar`：`calendar.January` 和 `calendar.February` 常數已被棄用並被 `calendar.JANUARY` 和 `calendar.FEBRUARY` 取代。 (由 Prince Roshan 於 gh-103636 貢獻。)

- `codecs`：請改用 `open()` 而非 `codecs.open()`。(gh-133038)

- `codeobject.co_lnotab`：請改用 `codeobject.co_lines()` 方法。

- `datetime`：

  - `utcnow()`：請改用 `datetime.datetime.now(tz=datetime.UTC)`。

  - `utcfromtimestamp()`：請改用 `datetime.datetime.fromtimestamp(timestamp, tz=datetime.UTC)`。

- `gettext`：複數值必須是整數。

- `importlib`：

  - `cache_from_source()` debug_override 參數已被棄用：請改用 optimization 參數。

- `importlib.metadata`：

  - `EntryPoints` 元組介面。

  - 回傳值上的隱式 `None`。

- `logging`：自 Python 3.3 起，`warn()` 方法已被棄用，請改用 `warning()`。

- `mailbox`：已棄用 StringIO 輸入和文本模式，請改用 BytesIO 和二進位模式。

- `os`：在多執行緒行程中呼叫 `os.register_at_fork()`。

- `pydoc.ErrorDuringImport`：exc_info 參數的元組值已被棄用，請用例外實例。

- `re`：現在對正規表示式中的數值群組參照和群組名稱用了更嚴格的規則。現在只有 ASCII 數碼序列被接受作為數值參照。位元組模式和替換字串中的群組名稱現在只能包含 ASCII 字母、數碼和底線。（由 Serhiy Storchaka 於 gh-91760 貢獻。）

- `sre_compile`、`sre_constants` 和 `sre_parse` 模組。

- `shutil`：`rmtree()` 的 onerror 參數在 Python 3.12 中已被棄用；請改用 onexc 參數。

- `ssl` 選項和協定：

  - 不帶協定引數的 `ssl.SSLContext` 已被棄用。

  - `ssl.SSLContext`：`set_npn_protocols()` 和 `selected_npn_protocol()` 已被棄用：請改用 ALPN。

  - `ssl.OP_NO_SSL*` 選項

  - `ssl.OP_NO_TLS*` 選項

  - `ssl.PROTOCOL_SSLv3`

  - `ssl.PROTOCOL_TLS`

  - `ssl.PROTOCOL_TLSv1`

  - `ssl.PROTOCOL_TLSv1_1`

  - `ssl.PROTOCOL_TLSv1_2`

  - `ssl.TLSVersion.SSLv3`

  - `ssl.TLSVersion.TLSv1`

  - `ssl.TLSVersion.TLSv1_1`

- `threading` 方法：

  - `threading.Condition.notifyAll()`：請用 `notify_all()`。

  - `threading.Event.isSet()`：請用 `is_set()`。

  - `threading.Thread.isDaemon()`、`threading.Thread.setDaemon()`：請用 `threading.Thread.daemon` 屬性。

  - `threading.Thread.getName()`、`threading.Thread.setName()`：請用 `threading.Thread.name` 屬性。

  - `threading.currentThread()`：請用 `threading.current_thread()`。

  - `threading.activeCount()`：請用 `threading.active_count()`。

- `typing.Text` (gh-92332)。

- 內部類別 `typing._UnionGenericAlias` 不再用於實作 `typing.Union`。為了保持與此私有類別使用者的相容性，直到至少 Python 3.17 都將提供一個相容性 shim。（由 Jelle Zijlstra 於 gh-105499 貢獻。）

- `unittest.IsolatedAsyncioTestCase`：從測試案例中回傳非 `None` 的值已被棄用。

- `urllib.parse` 已棄用函式：請改用 `urlparse()`。

  - `splitattr()`

  - `splithost()`

  - `splitnport()`

  - `splitpasswd()`

  - `splitport()`

  - `splitquery()`

  - `splittag()`

  - `splittype()`

  - `splituser()`

  - `splitvalue()`

  - `to_bytes()`

- `wsgiref`：`SimpleHandler.stdout.write()` 不應該進行部分寫入。

- `xml.etree.ElementTree`：已棄用對 `Element` 的真值測試。在未來版本中，它將始終回傳 `True`。請改用明確的 `len(elem)` 或 `elem is not None` 測試。

- `sys._clear_type_cache()` 已被棄用：請改用 `sys._clear_internal_caches()`。

## 已移除

### asynchat 和 asyncore

- These two modules have been removed according to the schedule in PEP 594, having been deprecated in Python 3.6. Use `asyncio` instead. (Contributed by Nikita Sobolev in gh-96580.)

### configparser

- 根據 gh-89336，已移除了在 3.2 中被 `configparser` 棄用的幾個名稱：

  - `configparser.ParsingError` 不再具有 `filename` 屬性或引數。請改用 `source` 屬性和引數。

  - `configparser` 不再具有 `SafeConfigParser` 類別。請改用較短的 `ConfigParser` 名稱。

  - `configparser.ConfigParser` 不再具有 `readfp` 方法。請改用 `read_file()`。

### distutils

- Remove the `distutils` package. It was deprecated in Python 3.10 by PEP 632 "Deprecate distutils module". For projects still using `distutils` and cannot be updated to something else, the `setuptools` project can be installed: it still provides `distutils`. (Contributed by Victor Stinner in gh-92584.)

### ensurepip

- Remove the bundled setuptools wheel from `ensurepip`, and stop installing setuptools in environments created by `venv`.

  `pip (>= 22.1)` does not require setuptools to be installed in the environment. `setuptools`-based (and `distutils`-based) packages can still be used with `pip install`, since pip will provide `setuptools` in the build environment it uses for building a package.

  `easy_install`, `pkg_resources`, `setuptools` and `distutils` are no longer provided by default in environments created with `venv` or bootstrapped with `ensurepip`, since they are part of the `setuptools` package. For projects relying on these at runtime, the `setuptools` project should be declared as a dependency and installed separately (typically, using pip).

  （由 Pradyun Gedam 於 gh-95299 中貢獻。）

### enum

- 移除 `enum` 的 `EnumMeta.__getattr__`，對於列舉屬性的存取不再會需要它。

### ftplib

- 移除 `ftplib` 的 `FTP_TLS.ssl_version` 類別屬性：請改用 context 參數。（由 Victor Stinner 於 gh-94172 中貢獻。）

### gzip

- Remove the `filename` attribute of `gzip`'s `gzip.GzipFile`, deprecated since Python 2.6, use the `name` attribute instead. In write mode, the `filename` attribute added `'.gz'` file extension if it was not present. (Contributed by Victor Stinner in gh-94196.)

### hashlib

- Remove the pure Python implementation of `hashlib`'s `hashlib.pbkdf2_hmac()`, deprecated in Python 3.10. Python 3.10 and newer requires OpenSSL 1.1.1 (PEP 644): this OpenSSL version provides a C implementation of `pbkdf2_hmac()` which is faster. (Contributed by Victor Stinner in gh-94199.)

### importlib

- 現已完成清理 `importlib` 中許多過去已經棄用的東西：

  - 對 `module_repr()` 的參照和支援已刪除。（由 Barry Warsaw 在 gh-97850 中貢獻。）

  - `importlib.util.set_package`、`importlib.util.set_loader` 和 `importlib.util.module_for_loader` 已全部刪除。（由 Brett Cannon 和 Nikita Sobolev 在 gh-65961 和 gh-97850 貢獻。）

  - 對 `find_loader()` 和 `find_module()` API 的支援已被刪除。（由 Barry Warsaw 在 gh-98040 中貢獻。）

  - `importlib.abc.Finder`、`pkgutil.ImpImporter` 和 `pkgutil.ImpLoader` 已被刪除。（由 Barry Warsaw 在 gh-98040 中貢獻。）

### imp

- `imp` 模組已被移除。（由 Barry Warsaw 在 gh-98040 中貢獻。）

  要遷移的話請參考以下對應表：

  > imp | importlib
  > --- | ---
  > `imp.NullImporter` | 將 `None` 插入 `sys.path_importer_cache`
  > `imp.cache_from_source()` | `importlib.util.cache_from_source()`
  > `imp.find_module()` | `importlib.util.find_spec()`
  > `imp.get_magic()` | `importlib.util.MAGIC_NUMBER`
  > `imp.get_suffixes()` | `importlib.machinery.SOURCE_SUFFIXES`、`importlib.machinery.EXTENSION_SUFFIXES` 和 `importlib.machinery.BYTECODE_SUFFIXES`
  > `imp.get_tag()` | `sys.implementation.cache_tag`
  > `imp.load_module()` | `importlib.import_module()`
  > `imp.new_module(name)` | `types.ModuleType(name)`
  > `imp.reload()` | `importlib.reload()`
  > `imp.source_from_cache()` | `importlib.util.source_from_cache()`
  > `imp.load_source()` | 見下文

  用以下取代 `imp.load_source()`：

      import importlib.util
      import importlib.machinery

      def load_source(modname, filename):
          loader = importlib.machinery.SourceFileLoader(modname, filename)
          spec = importlib.util.spec_from_file_location(modname, filename, loader=loader)
          module = importlib.util.module_from_spec(spec)
          # 此模組都會被執行且不會被快取於 sys.modules。
          # 要快取模組的話可以把下面一行取消註解
          # sys.modules[module.__name__] = module
          loader.exec_module(module)
          return module

- 移除 `imp` 函式和屬性、沒有替代方案：

  - 未以文件記錄的函式：

    - `imp.init_builtin()`

    - `imp.load_compiled()`

    - `imp.load_dynamic()`

    - `imp.load_package()`

  - `imp.lock_held()`, `imp.acquire_lock()`, `imp.release_lock()`: the locking scheme has changed in Python 3.3 to per-module locks.

  - `imp.find_module()` 常數：`SEARCH_ERROR`、`PY_SOURCE`、`PY_COMPILED`、`C_EXTENSION`、`PY_RESOURCE`、`PKG_DIRECTORY`、`C_BUILTIN`、`PY_FROZEN`、`PY_CODERESOURCE`、`IMP_HOOK`。

### io

- Remove `io`'s `io.OpenWrapper` and `_pyio.OpenWrapper`, deprecated in Python 3.10: just use `open()` instead. The `open()` (`io.open()`) function is a built-in function. Since Python 3.10, `_pyio.open()` is also a static method. (Contributed by Victor Stinner in gh-94169.)

### locale

- Remove `locale`'s `locale.format()` function, deprecated in Python 3.7: use `locale.format_string()` instead. (Contributed by Victor Stinner in gh-94226.)

### smtpd

- 根據 PEP 594 的時間表移除 `smtpd` 模組，它在 Python 3.4.7 和 3.5.4 中已被棄用。請改用 PyPI 上的 aiosmtpd 模組或任何其他基於 `asyncio` 的伺服器。

### sqlite3

- 以下未以文件記錄的 `sqlite3` 功能已在 Python 3.10 中被棄用、現在已被移除：

  - `sqlite3.enable_shared_cache()`

  - `sqlite3.OptimizedUnicode`

  If a shared cache must be used, open the database in URI mode using the `cache=shared` query parameter.

  The `sqlite3.OptimizedUnicode` text factory has been an alias for `str` since Python 3.3. Code that previously set the text factory to `OptimizedUnicode` can either use `str` explicitly, or rely on the default value which is also `str`.

  （由 Erlend E. Aasland 於 gh-92548 中貢獻。）

### ssl

- Remove `ssl`'s `ssl.RAND_pseudo_bytes()` function, deprecated in Python 3.6: use `os.urandom()` or `ssl.RAND_bytes()` instead. (Contributed by Victor Stinner in gh-94199.)

- Remove the `ssl.match_hostname()` function. It was deprecated in Python 3.7. OpenSSL performs hostname matching since Python 3.7, Python no longer uses the `ssl.match_hostname()` function. (Contributed by Victor Stinner in gh-94199.)

- Remove the `ssl.wrap_socket()` function, deprecated in Python 3.7: instead, create a `ssl.SSLContext` object and call its `ssl.SSLContext.wrap_socket` method. Any package that still uses `ssl.wrap_socket()` is broken and insecure. The function neither sends a SNI TLS extension nor validates the server hostname. Code is subject to CWE 295 (Improper Certificate Validation). (Contributed by Victor Stinner in gh-94199.)

### unittest

- 移除許多 `unittest` 中被棄用已久的功能：

  - 許多 `TestCase` 方法別名：

    已棄用的別名 | 方法名稱 | 已棄用於
    --- | --- | ---
    `failUnless` | `assertTrue()` | 3.1
    `failIf` | `assertFalse()` | 3.1
    `failUnlessEqual` | `assertEqual()` | 3.1
    `failIfEqual` | `assertNotEqual()` | 3.1
    `failUnlessAlmostEqual` | `assertAlmostEqual()` | 3.1
    `failIfAlmostEqual` | `assertNotAlmostEqual()` | 3.1
    `failUnlessRaises` | `assertRaises()` | 3.1
    `assert_` | `assertTrue()` | 3.2
    `assertEquals` | `assertEqual()` | 3.2
    `assertNotEquals` | `assertNotEqual()` | 3.2
    `assertAlmostEquals` | `assertAlmostEqual()` | 3.2
    `assertNotAlmostEquals` | `assertNotAlmostEqual()` | 3.2
    `assertRegexpMatches` | `assertRegex()` | 3.2
    `assertRaisesRegexp` | `assertRaisesRegex()` | 3.2
    `assertNotRegexpMatches` | `assertNotRegex()` | 3.5

    你可以使用 https://github.com/isidentical/teyit 來自動現代化你的單元測試。

  - 未以文件記錄且已失效的 `TestCase` 方法 `assertDictContainsSubset`（自 Python 3.2 起已棄用）。

  - Undocumented `TestLoader.loadTestsFromModule` parameter use_load_tests (deprecated and ignored since Python 3.5).

  - 對 `TextTestResult` 類別的別名：`_TextTestResult`（自 Python 3.2 起已棄用）。

  （由 Serhiy Storchaka 於 gh-89325 中貢獻。）

### webbrowser

- Remove support for obsolete browsers from `webbrowser`. The removed browsers include: Grail, Mosaic, Netscape, Galeon, Skipstone, Iceape, Firebird, and Firefox versions 35 and below (gh-102871).

### xml.etree.ElementTree

- Remove the `ElementTree.Element.copy()` method of the pure Python implementation, deprecated in Python 3.10, use the `copy.copy()` function instead. The C implementation of `xml.etree.ElementTree` has no `copy()` method, only a `__copy__()` method. (Contributed by Victor Stinner in gh-94383.)

### zipimport

- Remove `zipimport`'s `find_loader()` and `find_module()` methods, deprecated in Python 3.10: use the `find_spec()` method instead. See PEP 451 for the rationale. (Contributed by Victor Stinner in gh-94379.)

### 其他

- Remove the `suspicious` rule from the documentation `Makefile` and `Doc/tools/rstlint.py`, both in favor of sphinx-lint. (Contributed by Julien Palard in gh-98179.)

- Remove the keyfile and certfile parameters from the `ftplib`, `imaplib`, `poplib` and `smtplib` modules, and the key_file, cert_file and check_hostname parameters from the `http.client` module, all deprecated since Python 3.6. Use the context parameter (ssl_context in `imaplib`) instead. (Contributed by Victor Stinner in gh-94172.)

- 移除數個標準函式庫模組與測試中的 `Jython` 相容性修補程式。（由 Nikita Sobolev 於 gh-99482 中貢獻。）

- 移除 `ctypes` 模組中的 `_use_broken_old_ctypes_structure_semantics_` 旗標。（由 Nikita Sobolev 於 gh-99285 中貢獻。）

## 移植至 Python 3.12

This section lists previously described changes and other bugfixes that may require changes to your code.

### Python API 的變更

- More strict rules are now applied for numerical group references and group names in regular expressions. Only sequence of ASCII digits is now accepted as a numerical reference. The group name in bytes patterns and replacement strings can now only contain ASCII letters and digits and underscore. (Contributed by Serhiy Storchaka in gh-91760.)

- Remove `randrange()` functionality deprecated since Python 3.10. Formerly, `randrange(10.0)` losslessly converted to `randrange(10)`. Now, it raises a `TypeError`. Also, the exception raised for non-integer values such as `randrange(10.5)` or `randrange('10')` has been changed from `ValueError` to `TypeError`. This also prevents bugs where `randrange(1e25)` would silently select from a larger range than `randrange(10**25)`. (Originally suggested by Serhiy Storchaka gh-86388.)

- `argparse.ArgumentParser` changed encoding and error handler for reading arguments from file (e.g. `fromfile_prefix_chars` option) from default text encoding (e.g. `locale.getpreferredencoding(False)`) to filesystem encoding and error handler. Argument files should be encoded in UTF-8 instead of ANSI Codepage on Windows.

- Remove the `asyncore`-based `smtpd` module deprecated in Python 3.4.7 and 3.5.4. A recommended replacement is the `asyncio`-based aiosmtpd PyPI module.

- `shlex.split()`: Passing `None` for s argument now raises an exception, rather than reading `sys.stdin`. The feature was deprecated in Python 3.9. (Contributed by Victor Stinner in gh-94352.)

- The `os` module no longer accepts bytes-like paths, like `bytearray` and `memoryview` types: only the exact `bytes` type is accepted for bytes strings. (Contributed by Victor Stinner in gh-98393.)

- `syslog.openlog()` and `syslog.closelog()` now fail if used in subinterpreters. `syslog.syslog()` may still be used in subinterpreters, but now only if `syslog.openlog()` has already been called in the main interpreter. These new restrictions do not apply to the main interpreter, so only a very small set of users might be affected. This change helps with interpreter isolation. Furthermore, `syslog` is a wrapper around process-global resources, which are best managed from the main interpreter. (Contributed by Donghee Na in gh-99127.)

- The undocumented locking behavior of `cached_property()` is removed, because it locked across all instances of the class, leading to high lock contention. This means that a cached property getter function could now run more than once for a single instance, if two threads race. For most simple cached properties (e.g. those that are idempotent and simply calculate a value based on other attributes of the instance) this will be fine. If synchronization is needed, implement locking within the cached property getter function or around multi-threaded access points.

- `sys._current_exceptions()` now returns a mapping from thread-id to an exception instance, rather than to a `(typ, exc, tb)` tuple. (Contributed by Irit Katriel in gh-103176.)

- When extracting tar files using `tarfile` or `shutil.unpack_archive()`, pass the filter argument to limit features that may be surprising or dangerous. See Extraction filters for details.

- The output of the `tokenize.tokenize()` and `tokenize.generate_tokens()` functions is now changed due to the changes introduced in PEP 701. This means that `STRING` tokens are not emitted any more for f-strings and the tokens described in PEP 701 are now produced instead: `FSTRING_START`, `FSTRING_MIDDLE` and `FSTRING_END` are now emitted for f-string "string" parts in addition to the appropriate tokens for the tokenization in the expression components. For example for the f-string `f"start {1+1} end"` the old version of the tokenizer emitted:

      1,0-1,18:           STRING         'f"start {1+1} end"'

  while the new version emits:

      1,0-1,2:            FSTRING_START  'f"'
      1,2-1,8:            FSTRING_MIDDLE 'start '
      1,8-1,9:            OP             '{'
      1,9-1,10:           NUMBER         '1'
      1,10-1,11:          OP             '+'
      1,11-1,12:          NUMBER         '1'
      1,12-1,13:          OP             '}'
      1,13-1,17:          FSTRING_MIDDLE ' end'
      1,17-1,18:          FSTRING_END    '"'

  Additionally, there may be some minor behavioral changes as a consequence of the changes required to support PEP 701. Some of these changes include:

  - The `type` attribute of the tokens emitted when tokenizing some invalid Python characters such as `!` has changed from `ERRORTOKEN` to `OP`.

  - Incomplete single-line strings now also raise `tokenize.TokenError` as incomplete multiline strings do.

  - Some incomplete or invalid Python code now raises `tokenize.TokenError` instead of returning arbitrary `ERRORTOKEN` tokens when tokenizing it.

  - Mixing tabs and spaces as indentation in the same file is not supported anymore and will raise a `TabError`.

- The `threading` module now expects the `_thread` module to have an `_is_main_interpreter` attribute. It is a function with no arguments that returns `True` if the current interpreter is the main interpreter.

  Any library or application that provides a custom `_thread` module should provide `_is_main_interpreter()`. (See gh-112826.)

## 建置變更

- Python no longer uses `setup.py` to build shared C extension modules. Build parameters like headers and libraries are detected in `configure` script. Extensions are built by `Makefile`. Most extensions use `pkg-config` and fall back to manual detection. (Contributed by Christian Heimes in gh-93939.)

- `va_start()` with two parameters, like `va_start(args, format),` is now required to build Python. `va_start()` is no longer called with a single parameter. (Contributed by Kumar Aditya in gh-93207.)

- CPython now uses the ThinLTO option as the default link time optimization policy if the Clang compiler accepts the flag. (Contributed by Donghee Na in gh-89536.)

- Add `COMPILEALL_OPTS` variable in `Makefile` to override `compileall` options (default: `-j0`) in `make install`. Also merged the 3 `compileall` commands into a single command to build .pyc files for all optimization levels (0, 1, 2) at once. (Contributed by Victor Stinner in gh-99289.)

- Add platform triplets for 64-bit LoongArch:

  - loongarch64-linux-gnusf

  - loongarch64-linux-gnuf32

  - loongarch64-linux-gnu

  （由 Zhang Na 於 gh-90656 中貢獻。）

- `PYTHON_FOR_REGEN` 現在需要 Python 3.10 或更新的版本。

- Autoconf 2.71 and aclocal 1.16.4 is now required to regenerate `configure`. (Contributed by Christian Heimes in gh-89886.)

- Windows builds and macOS installers from python.org now use OpenSSL 3.0.

## C API 變更

### 新增功能

- PEP 697: Introduce the Unstable C API tier, intended for low-level tools like debuggers and JIT compilers. This API may change in each minor release of CPython without deprecation warnings. Its contents are marked by the `PyUnstable_` prefix in names.

  程式碼物件建構函式：

  - `PyUnstable_Code_New()`（自 `PyCode_New` 重新命名）

  - `PyUnstable_Code_NewWithPosOnlyArgs()`（自 `PyCode_NewWithPosOnlyArgs` 重新命名）

  程式碼物件的額外儲存 (PEP 523)：

  - `PyUnstable_Eval_RequestCodeExtraIndex()`（自 `_PyEval_RequestCodeExtraIndex` 重新命名）

  - `PyUnstable_Code_GetExtra()`（自 `_PyCode_GetExtra` 重新命名）

  - `PyUnstable_Code_SetExtra()`（自 `_PyCode_SetExtra` 重新命名）

  原始名稱將可繼續使用，直到相應的 API 發生變更。

  （由 Petr Viktorin 於 gh-101101 中貢獻。）

- PEP 697: Add an API for extending types whose instance memory layout is opaque:

  - `PyType_Spec.basicsize` 可以為零或負數來指定繼承或擴充基底類別大小。

  - `PyObject_GetTypeData()` and `PyType_GetTypeDataSize()` added to allow access to subclass-specific instance data.

  - `Py_TPFLAGS_ITEMS_AT_END` and `PyObject_GetItemData()` added to allow safely extending certain variable-sized types, including `PyType_Type`.

  - `Py_RELATIVE_OFFSET` added to allow defining `members` in terms of a subclass-specific struct.

  （由 Petr Viktorin 於 gh-103509 中貢獻。）

- Add the new limited C API function `PyType_FromMetaclass()`, which generalizes the existing `PyType_FromModuleAndSpec()` using an additional metaclass argument. (Contributed by Wenzel Jakob in gh-93012.)

- API for creating objects that can be called using the vectorcall protocol was added to the Limited API:

  - `Py_TPFLAGS_HAVE_VECTORCALL`

  - `PyVectorcall_NARGS()`

  - `PyVectorcall_Call()`

  - `vectorcallfunc`

  The `Py_TPFLAGS_HAVE_VECTORCALL` flag is now removed from a class when the class's `__call__()` method is reassigned. This makes vectorcall safe to use with mutable types (i.e. heap types without the immutable flag, `Py_TPFLAGS_IMMUTABLETYPE`). Mutable types that do not override `tp_call` now inherit the `Py_TPFLAGS_HAVE_VECTORCALL` flag. (Contributed by Petr Viktorin in gh-93274.)

  The `Py_TPFLAGS_MANAGED_DICT` and `Py_TPFLAGS_MANAGED_WEAKREF` flags have been added. This allows extensions classes to support object `__dict__` and weakrefs with less bookkeeping, using less memory and with faster access.

- API for performing calls using the vectorcall protocol was added to the Limited API:

  - `PyObject_Vectorcall()`

  - `PyObject_VectorcallMethod()`

  - `PY_VECTORCALL_ARGUMENTS_OFFSET`

  This means that both the incoming and outgoing ends of the vector call protocol are now available in the Limited API. (Contributed by Wenzel Jakob in gh-98586.)

- Add two new public functions, `PyEval_SetProfileAllThreads()` and `PyEval_SetTraceAllThreads()`, that allow to set tracing and profiling functions in all running threads in addition to the calling one. (Contributed by Pablo Galindo in gh-93503.)

- Add new function `PyFunction_SetVectorcall()` to the C API which sets the vectorcall field of a given `PyFunctionObject`. (Contributed by Andrew Frost in gh-92257.)

- The C API now permits registering callbacks via `PyDict_AddWatcher()`, `PyDict_Watch()` and related APIs to be called whenever a dictionary is modified. This is intended for use by optimizing interpreters, JIT compilers, or debuggers. (Contributed by Carl Meyer in gh-91052.)

- Add `PyType_AddWatcher()` and `PyType_Watch()` API to register callbacks to receive notification on changes to a type. (Contributed by Carl Meyer in gh-91051.)

- Add `PyCode_AddWatcher()` and `PyCode_ClearWatcher()` APIs to register callbacks to receive notification on creation and destruction of code objects. (Contributed by Itamar Oren in gh-91054.)

- Add `PyFrame_GetVar()` and `PyFrame_GetVarString()` functions to get a frame variable by its name. (Contributed by Victor Stinner in gh-91248.)

- Add `PyErr_GetRaisedException()` and `PyErr_SetRaisedException()` for saving and restoring the current exception. These functions return and accept a single exception object, rather than the triple arguments of the now-deprecated `PyErr_Fetch()` and `PyErr_Restore()`. This is less error prone and a bit more efficient. (Contributed by Mark Shannon in gh-101578.)

- Add `_PyErr_ChainExceptions1`, which takes an exception instance, to replace the legacy-API `_PyErr_ChainExceptions`, which is now deprecated. (Contributed by Mark Shannon in gh-101578.)

- Add `PyException_GetArgs()` and `PyException_SetArgs()` as convenience functions for retrieving and modifying the `args` passed to the exception's constructor. (Contributed by Mark Shannon in gh-101578.)

- Add `PyErr_DisplayException()`, which takes an exception instance, to replace the legacy-api `PyErr_Display()`. (Contributed by Irit Katriel in gh-102755).

- PEP 683: Introduce Immortal Objects, which allows objects to bypass reference counts, and related changes to the C-API:

  - `_Py_IMMORTAL_REFCNT`：定義物件的參照計數

      as immortal.

  - `_Py_IsImmortal` Checks if an object has the immortal reference count.

  - `PyObject_HEAD_INIT` 這現在將初始化參照計數

      `_Py_IMMORTAL_REFCNT`（與 `Py_BUILD_CORE` 一起使用時）。

  - `SSTATE_INTERNED_IMMORTAL` 駐留的 (interned) unicode 物件的識別字

      那是不滅的。

  - `SSSTATE_INTERNED_IMMORTAL_STATIC` 駐留的 unicode 的識別字

      不滅且靜態的物體

  - `sys.getunicodeinternedsize` 這會回傳 unicode 的總數

      objects that have been interned. This is now needed for `refleak.py` to correctly track reference counts and allocated blocks

  （由 Eddie Elizondo 於 gh-84436 中貢獻。）

- PEP 684：新增新的 `Py_NewInterpreterFromConfig()` 函式和 `PyInterpreterConfig`，它們可用於建立具有自己的 GIL 的子直譯器。（有關更多資訊，請參閱 PEP 684：直譯器各別持有的 GIL。）（由 Eric Snow 在 gh-104110 中貢獻。）

- In the limited C API version 3.12, `Py_INCREF()` and `Py_DECREF()` functions are now implemented as opaque function calls to hide implementation details. (Contributed by Victor Stinner in gh-105387.)

### 移植至 Python 3.12

- Legacy Unicode APIs based on `Py_UNICODE*` representation has been removed. Please migrate to APIs based on UTF-8 or `wchar_t*`.

- Argument parsing functions like `PyArg_ParseTuple()` doesn't support `Py_UNICODE*` based format (e.g. `u`, `Z`) anymore. Please migrate to other formats for Unicode like `s`, `z`, `es`, and `U`.

- `tp_weaklist` for all static builtin types is always `NULL`. This is an internal-only field on `PyTypeObject` but we're pointing out the change in case someone happens to be accessing the field directly anyway. To avoid breakage, consider using the existing public C-API instead, or, if necessary, the (internal-only) `_PyObject_GET_WEAKREFS_LISTPTR()` macro.

- This internal-only `PyTypeObject.tp_subclasses` may now not be a valid object pointer. Its type was changed to void* to reflect this. We mention this in case someone happens to be accessing the internal-only field directly.

  To get a list of subclasses, call the Python method `__subclasses__()` (using `PyObject_CallMethod()`, for example).

- Add support of more formatting options (left aligning, octals, uppercase hexadecimals, `intmax_t`, `ptrdiff_t`, `wchar_t` C strings, variable width and precision) in `PyUnicode_FromFormat()` and `PyUnicode_FromFormatV()`. (Contributed by Serhiy Storchaka in gh-98836.)

- An unrecognized format character in `PyUnicode_FromFormat()` and `PyUnicode_FromFormatV()` now sets a `SystemError`. In previous versions it caused all the rest of the format string to be copied as-is to the result string, and any extra arguments discarded. (Contributed by Serhiy Storchaka in gh-95781.)

- Fix wrong sign placement in `PyUnicode_FromFormat()` and `PyUnicode_FromFormatV()`. (Contributed by Philip Georgi in gh-95504.)

- Extension classes wanting to add a `__dict__` or weak reference slot should use `Py_TPFLAGS_MANAGED_DICT` and `Py_TPFLAGS_MANAGED_WEAKREF` instead of `tp_dictoffset` and `tp_weaklistoffset`, respectively. The use of `tp_dictoffset` and `tp_weaklistoffset` is still supported, but does not fully support multiple inheritance (gh-95589), and performance may be worse. Classes declaring `Py_TPFLAGS_MANAGED_DICT` must call `_PyObject_VisitManagedDict()` and `_PyObject_ClearManagedDict()` to traverse and clear their instance's dictionaries. To clear weakrefs, call `PyObject_ClearWeakRefs()`, as before.

- The `PyUnicode_FSDecoder()` function no longer accepts bytes-like paths, like `bytearray` and `memoryview` types: only the exact `bytes` type is accepted for bytes strings. (Contributed by Victor Stinner in gh-98393.)

- The `Py_CLEAR`, `Py_SETREF` and `Py_XSETREF` macros now only evaluate their arguments once. If an argument has side effects, these side effects are no longer duplicated. (Contributed by Victor Stinner in gh-98724.)

- The interpreter's error indicator is now always normalized. This means that `PyErr_SetObject()`, `PyErr_SetString()` and the other functions that set the error indicator now normalize the exception before storing it. (Contributed by Mark Shannon in gh-101578.)

- `_Py_RefTotal` is no longer authoritative and only kept around for ABI compatibility. Note that it is an internal global and only available on debug builds. If you happen to be using it then you'll need to start using `_Py_GetGlobalRefTotal()`.

- The following functions now select an appropriate metaclass for the newly created type:

  - `PyType_FromSpec()`

  - `PyType_FromSpecWithBases()`

  - `PyType_FromModuleAndSpec()`

  Creating classes whose metaclass overrides `tp_new` is deprecated, and in Python 3.14+ it will be disallowed. Note that these functions ignore `tp_new` of the metaclass, possibly allowing incomplete initialization.

  Note that `PyType_FromMetaclass()` (added in Python 3.12) already disallows creating classes whose metaclass overrides `tp_new` (`__new__()` in Python).

  Since `tp_new` overrides almost everything `PyType_From*` functions do, the two are incompatible with each other. The existing behavior -- ignoring the metaclass for several steps of type creation -- is unsafe in general, since (meta)classes assume that `tp_new` was called. There is no simple general workaround. One of the following may work for you:

  - If you control the metaclass, avoid using `tp_new` in it:

    - If initialization can be skipped, it can be done in `tp_init` instead.

    - If the metaclass doesn't need to be instantiated from Python, set its `tp_new` to `NULL` using the `Py_TPFLAGS_DISALLOW_INSTANTIATION` flag. This makes it acceptable for `PyType_From*` functions.

  - Avoid `PyType_From*` functions: if you don't need C-specific features (slots or setting the instance size), create types by calling the metaclass.

  - If you know the `tp_new` can be skipped safely, filter the deprecation warning out using `warnings.catch_warnings()` from Python.

- `PyOS_InputHook` and `PyOS_ReadlineFunctionPointer` are no longer called in subinterpreters. This is because clients generally rely on process-wide global state (since these callbacks have no way of recovering extension module state).

  This also avoids situations where extensions may find themselves running in a subinterpreter that they don't support (or haven't yet been loaded in). See gh-104668 for more info.

- `PyLongObject` has had its internals changed for better performance. Although the internals of `PyLongObject` are private, they are used by some extension modules. The internal fields should no longer be accessed directly, instead the API functions beginning `PyLong_...` should be used instead. Two new unstable API functions are provided for efficient access to the value of `PyLongObject`s which fit into a single machine word:

  - `PyUnstable_Long_IsCompact()`

  - `PyUnstable_Long_CompactValue()`

- Custom allocators, set via `PyMem_SetAllocator()`, are now required to be thread-safe, regardless of memory domain. Allocators that don't have their own state, including "hooks", are not affected. If your custom allocator is not already thread-safe and you need guidance then please create a new GitHub issue and CC `@ericsnowcurrently`.

### 已棄用

- In accordance with PEP 699, the `ma_version_tag` field in `PyDictObject` is deprecated for extension modules. Accessing this field will generate a compiler warning at compile time. This field will be removed in Python 3.14. (Contributed by Ramvikrams and Kumar Aditya in gh-101193. PEP by Ken Jin.)

- 棄用全域配置變數：

  - `Py_DebugFlag`：請改用 `PyConfig.parser_debug`

  - `Py_VerboseFlag`：請改用 `PyConfig.verbose`

  - `Py_QuietFlag`：請改用 `PyConfig.quiet`

  - `Py_InteractiveFlag`：請改用 `PyConfig.interactive`

  - `Py_InspectFlag`：請改用 `PyConfig.inspect`

  - `Py_OptimizeFlag`：請改用 `PyConfig.optimization_level`

  - `Py_NoSiteFlag`：請改用 `PyConfig.site_import`

  - `Py_BytesWarningFlag`：請改用 `PyConfig.bytes_warning`

  - `Py_FrozenFlag`：請改用 `PyConfig.pathconfig_warnings`

  - `Py_IgnoreEnvironmentFlag`：請改用 `PyConfig.use_environment`

  - `Py_DontWriteBytecodeFlag`：請改用 `PyConfig.write_bytecode`

  - `Py_NoUserSiteDirectory`：請改用 `PyConfig.user_site_directory`

  - `Py_UnbufferedStdioFlag`：請改用 `PyConfig.buffered_stdio`

  - `Py_HashRandomizationFlag`：請改用 `PyConfig.use_hash_seed` 和 `PyConfig.hash_seed`

  - `Py_IsolatedFlag`：請改用 `PyConfig.isolated`

  - `Py_LegacyWindowsFSEncodingFlag`：請改用 `PyPreConfig.legacy_windows_fs_encoding`

  - `Py_LegacyWindowsStdioFlag`：請改用 `PyConfig.legacy_windows_stdio`

  - `Py_FileSystemDefaultEncoding`：請改用 `PyConfig.filesystem_encoding`

  - `Py_HasFileSystemDefaultEncoding`：請改用 `PyConfig.filesystem_encoding`

  - `Py_FileSystemDefaultEncodeErrors`：請改用 `PyConfig.filesystem_errors`

  - `Py_UTF8Mode`：請改用 `PyPreConfig.utf8_mode`（參見 `Py_PreInitialize()`）

  `Py_InitializeFromConfig()` API 應改為與 `PyConfig` 一起使用。（由 Victor Stinner 於 gh-77782 中貢獻。）

- Creating `immutable types` with mutable bases is deprecated and will be disabled in Python 3.14. (gh-95388)

- `structmember.h` 標頭已棄用，但仍可使用，且還沒有移除它的計畫。

  現在只需包含 `Python.h` 即可使用其內容，如果缺少，則新增 `Py` 前綴：

  - `PyMemberDef`、`PyMember_GetOne()` 和 `PyMember_SetOne()`

  - 型別巨集，如 `Py_T_INT`、`Py_T_DOUBLE` 等（以前為 `T_INT`、 `T_DOUBLE` 等）

  - `Py_READONLY`（先前為 `READONLY`）和 `Py_AUDIT_READ`（先前全大寫）旗標

  數個項目不再從 `Python.h` 中公開：

  - `T_OBJECT`（請改用 `Py_T_OBJECT_EX`）

  - `T_NONE`（先前未記錄於文件上，且相當古怪）

  - 不做任何事的巨集 `WRITE_RESTRICTED`。

  - `RESTRICTED` 和 `READ_RESTRICTED` 這兩個巨集，相當於 `Py_AUDIT_READ`。

  - In some configurations, `<stddef.h>` is not included from `Python.h`. It should be included manually when using `offsetof()`.

  The deprecated header continues to provide its original contents under the original names. Your old code can stay unchanged, unless the extra include and non-namespaced macros bother you greatly.

  （由 Petr Viktorin 在 gh-47146 中貢獻，其基於 Alexander Belopolsky 和 Matthias Braun 的前期工作。）

- `PyErr_Fetch()` and `PyErr_Restore()` are deprecated. Use `PyErr_GetRaisedException()` and `PyErr_SetRaisedException()` instead. (Contributed by Mark Shannon in gh-101578.)

- `PyErr_Display()` 已棄用，請改用 `PyErr_DisplayException()`。（由 Irit Katriel 於 gh-102755 中貢獻。）

- `_PyErr_ChainExceptions` 已棄用，請改用 `_PyErr_ChainExceptions1`。（由 Irit Katriel 於 gh-102192 中貢獻。）

- 使用 `PyType_FromSpec()`、`PyType_FromSpecWithBases()` 或 `PyType_FromModuleAndSpec()` 建立一個其元類別覆寫 `tp_new` 的類別已被棄用。請改為呼叫元類別。

#### Python 3.14 中待移除的項目

- `PyDictObject` 中的 `ma_version_tag` 欄位，用於擴充模組 (PEP 699；gh-101193)。

- 使用可變基底建立`不可變型別` (gh-95388)。

#### Python 3.15 中待移除的項目

- `PyImport_ImportModuleNoBlock()`：請改用 `PyImport_ImportModule()`。

- `PyWeakref_GetObject()` 和 `PyWeakref_GET_OBJECT()`：請改用 `PyWeakref_GetRef()`。可以使用 pythoncapi-compat 專案來為 Python 3.12 和更早版本取得 `PyWeakref_GetRef()`。

- `Py_UNICODE` 型別與 `Py_UNICODE_WIDE` 巨集：請改用 `wchar_t`。

- `PyUnicode_AsDecodedObject()`：請改用 `PyCodec_Decode()`。

- `PyUnicode_AsDecodedUnicode()`：請改用 `PyCodec_Decode()`；請注意某些編解碼器（例如 "base64"）可能會回傳非 `str` 的型別，例如 `bytes`。

- `PyUnicode_AsEncodedObject()`：請改用 `PyCodec_Encode()`。

- `PyUnicode_AsEncodedUnicode()`：請改用 `PyCodec_Encode()`；請注意某些編解碼器（例如 "base64"）可能會回傳非 `bytes` 的型別，例如 `str`。

- Python 初始化函式，自 Python 3.13 起已被棄用：

  - `Py_GetPath()`：請改用 `PyConfig_Get("module_search_paths")` (`sys.path`)。

  - `Py_GetPrefix()`：請改用 `PyConfig_Get("base_prefix")` (`sys.base_prefix`)。如果需要處理虛擬環境，請改用 `PyConfig_Get("prefix")` (`sys.prefix`)。

  - `Py_GetExecPrefix()`：請改用 `PyConfig_Get("base_exec_prefix")` (`sys.base_exec_prefix`)。如果需要處理虛擬環境，請改用 `PyConfig_Get("exec_prefix")` (`sys.exec_prefix`)。

  - `Py_GetProgramFullPath()`：請改用 `PyConfig_Get("executable")` (`sys.executable`)。

  - `Py_GetProgramName()`：請改用 `PyConfig_Get("executable")` (`sys.executable`)。

  - `Py_GetPythonHome()`：請改用 `PyConfig_Get("home")` 或 `PYTHONHOME` 環境變數。

  pythoncapi-compat 專案 可以用來為 Python 3.13 和更早版本取得 `PyConfig_Get()`。

- 用於配置 Python 初始化的函式，自 Python 3.11 起已被棄用：

  - `PySys_SetArgvEx()`：請改用 `PyConfig.argv`。

  - `PySys_SetArgv()`：請改用 `PyConfig.argv`。

  - `Py_SetProgramName()`：請改用 `PyConfig.program_name`。

  - `Py_SetPythonHome()`：請改用 `PyConfig.home`。

  - `PySys_ResetWarnOptions()`：請改為清除 `sys.warnoptions` 和 `warnings.filters`。

  應改用帶有 `PyConfig` 的 `Py_InitializeFromConfig()` API。

- 全域配置變數：

  - `Py_DebugFlag`：請改用 `PyConfig.parser_debug` 或 `PyConfig_Get("parser_debug")`。

  - `Py_VerboseFlag`：請改用 `PyConfig.verbose` 或 `PyConfig_Get("verbose")`。

  - `Py_QuietFlag`：請改用 `PyConfig.quiet` 或 `PyConfig_Get("quiet")`。

  - `Py_InteractiveFlag`：請改用 `PyConfig.interactive` 或 `PyConfig_Get("interactive")`。

  - `Py_InspectFlag`：請改用 `PyConfig.inspect` 或 `PyConfig_Get("inspect")`。

  - `Py_OptimizeFlag`：請改用 `PyConfig.optimization_level` 或 `PyConfig_Get("optimization_level")`。

  - `Py_NoSiteFlag`：請改用 `PyConfig.site_import` 或 `PyConfig_Get("site_import")`。

  - `Py_BytesWarningFlag`：請改用 `PyConfig.bytes_warning` 或 `PyConfig_Get("bytes_warning")`。

  - `Py_FrozenFlag`：請改用 `PyConfig.pathconfig_warnings` 或 `PyConfig_Get("pathconfig_warnings")`。

  - `Py_IgnoreEnvironmentFlag`：請改用 `PyConfig.use_environment` 或 `PyConfig_Get("use_environment")`。

  - `Py_DontWriteBytecodeFlag`：請改用 `PyConfig.write_bytecode` 或 `PyConfig_Get("write_bytecode")`。

  - `Py_NoUserSiteDirectory`：請改用 `PyConfig.user_site_directory` 或 `PyConfig_Get("user_site_directory")`。

  - `Py_UnbufferedStdioFlag`：請改用 `PyConfig.buffered_stdio` 或 `PyConfig_Get("buffered_stdio")`。

  - `Py_HashRandomizationFlag`：請改用 `PyConfig.use_hash_seed` 和 `PyConfig.hash_seed` 或 `PyConfig_Get("hash_seed")`。

  - `Py_IsolatedFlag`：請改用 `PyConfig.isolated` 或 `PyConfig_Get("isolated")`。

  - `Py_LegacyWindowsFSEncodingFlag`：請改用 `PyPreConfig.legacy_windows_fs_encoding` 或 `PyConfig_Get("legacy_windows_fs_encoding")`。

  - `Py_LegacyWindowsStdioFlag`：請改用 `PyConfig.legacy_windows_stdio` 或 `PyConfig_Get("legacy_windows_stdio")`。

  - `Py_FileSystemDefaultEncoding`、`Py_HasFileSystemDefaultEncoding`：請改用 `PyConfig.filesystem_encoding` 或 `PyConfig_Get("filesystem_encoding")`。

  - `Py_FileSystemDefaultEncodeErrors`：請改用 `PyConfig.filesystem_errors` 或 `PyConfig_Get("filesystem_errors")`。

  - `Py_UTF8Mode`：請改用 `PyPreConfig.utf8_mode` 或 `PyConfig_Get("utf8_mode")`。（請參閱 `Py_PreInitialize()`）

  應改用帶有 `PyConfig` 的 `Py_InitializeFromConfig()` API 來設定這些選項。或者也可以使用 `PyConfig_Get()` 在執行時取得這些選項。

#### Python 3.16 中待移除的項目

- `libmpdecimal` 的打包副本 (bundled copy)。

#### 未來版本中的待移除項目

下列 API 已被棄用並將會被移除，不過目前尚未訂定移除日期。

- `Py_TPFLAGS_HAVE_FINALIZE`：自 Python 3.8 起不再需要

- `PyErr_Fetch()`：請改用 `PyErr_GetRaisedException()`。

- `PyErr_NormalizeException()`：請改用 `PyErr_GetRaisedException()`。

- `PyErr_Restore()`：請改用 `PyErr_SetRaisedException()`。

- `PyModule_GetFilename()`：請改用 `PyModule_GetFilenameObject()`。

- `PyOS_AfterFork()`：請改用 `PyOS_AfterFork_Child()`。

- `PySlice_GetIndicesEx()`：請改用 `PySlice_Unpack()` 和 `PySlice_AdjustIndices()`。

- `PyUnicode_READY()`：自 Python 3.12 起不再需要

- `PyErr_Display()`：請改用 `PyErr_DisplayException()`。

- `_PyErr_ChainExceptions()`：請改用 `_PyErr_ChainExceptions1`。

- `PyBytesObject.ob_shash` 成員：請改為呼叫 `PyObject_Hash()`。

- 執行緒局部儲存 (Thread Local Storage, TLS) API：

  - `PyThread_create_key()`：請改用 `PyThread_tss_alloc()`。

  - `PyThread_delete_key()`：請改用 `PyThread_tss_free()`。

  - `PyThread_set_key_value()`：請改用 `PyThread_tss_set()`。

  - `PyThread_get_key_value()`：請改用 `PyThread_tss_get()`。

  - `PyThread_delete_key_value()`：請改用 `PyThread_tss_delete()`。

  - `PyThread_ReInitTLS()`：自 Python 3.7 起不再需要。

### 已移除

- 移除 `token.h` 標頭檔案。從未有任何公開的 tokenizer C API。`token.h` 標頭檔案的設計是僅限用於 Python 內部。（由 Victor Stinner 於 gh-92651 中貢獻。）

- Legacy Unicode APIs have been removed. See PEP 623 for detail.

  - `PyUnicode_WCHAR_KIND`

  - `PyUnicode_AS_UNICODE()`

  - `PyUnicode_AsUnicode()`

  - `PyUnicode_AsUnicodeAndSize()`

  - `PyUnicode_AS_DATA()`

  - `PyUnicode_FromUnicode()`

  - `PyUnicode_GET_SIZE()`

  - `PyUnicode_GetSize()`

  - `PyUnicode_GET_DATA_SIZE()`

- 移除 `PyUnicode_InternImmortal()` 函式巨集。（由 Victor Stinner 於 gh-85858 中貢獻。）